search for: issues

The Asterisk Development Team would like to announce the release of Certified Asterisk 16.3-cert1. This release is available for immediate download at https://downloads.asterisk.org/pub/telephony/certified-asterisk The release of Certified Asterisk 16.3-cert1 resolves several issues reported by the community and would have not been possible without your participation. *Thank you!* The following issues are resolved in this release: *Security bugs fixed in this release:* ----------------------------------- - [ASTERISK-28589 <https://issues.asterisk.org/jira/browse/A...

I''m just getting into RoR, coming from a long PHP background. So far I LOVE IT! I''m hitting a roadblock with updating my mysql database. For simplicities sake, I have 2 tables and here are the relevant columns. Table Users id name email Table Issues id createdby assignedto reportedby In my models I have everything mapped properly I believe. When I try to update the Issues table @issue = Issue.find(:id) @issue.update_attributes(params[:issue]) I get an error, "User expected, got String" So my question is, should I be updating...

List, Over the last few months we have managed to bring the total number of issue on the tracker from 610+ to 537 (as of writing). While this is good news, we still have a number of open issues that require testers to help move them along. Below, I have posted the oldest 50 issues that are in the 'Ready for Testing' state. Basically, we are looking for more people to step-up and test theses patches. Each issue below _should_ have an existing patch attached to it. Simply downloa...

The Asterisk Development Team would like to announce the release of Asterisk 14.4.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 14.4.0 resolves several issues reported by the community and would have not been possible without your participation. *Thank you!* The following issues are resolved in this release: *New Features made in this release:* ----------------------------------- - [ASTERISK-26878 <https://issues.asterisk.org/jira/browse/ASTERISK-2...

The Asterisk Development Team would like to announce the release of Asterisk 13.15.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 13.15.0 resolves several issues reported by the community and would have not been possible without your participation. *Thank you!* The following issues are resolved in this release: *New Features made in this release:* ----------------------------------- - [ASTERISK-26878 <https://issues.asterisk.org/jira/browse/ASTERISK-2...

The Asterisk Development Team has announced the release of Asterisk 1.8.2. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.8.2 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following is a sample of the issues resolved in this release: * 'sip notify clear-mwi' needs terminating CRLF. (Closes issue #18275. Reported, patched by klaus3000) * Patch for deadlo...

The Asterisk Development Team has announced the release of Asterisk 1.8.2. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ The release of Asterisk 1.8.2 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following is a sample of the issues resolved in this release: * 'sip notify clear-mwi' needs terminating CRLF. (Closes issue #18275. Reported, patched by klaus3000) * Patch for deadlo...

The Asterisk Development Team would like to announce the release of Asterisk 16.0.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 16.0.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following issues are resolved in this release: Security bugs fixed in this release: ----------------------------------- * ASTERISK-28013 - res_http_websocket: Crash when reading HTTP Upgr...

...;we" represents, other than myself. Just assume all the good ideas here were from others, and all the bad parts I misremembered or invented. Background ---- Our bugzilla installation is...not great. It's been not-great for a long time now. Last year, I argued against switching to github issues. I was somewhat optimistic that it was possible to improve our bugzilla in some incremental ways...but we haven't. Additionally, the upstream bugzilla project was supposed to make a new release of bugzilla ("harmony"), based on bugzilla.mozilla.org's fork, which is much nicer. I t...

...internal project rehydration tool that could be used to populate the empty repo contents from the simple serialized format. There is a big advantage of this approach as compared to using GH API as we are not bound to various thresholds and throttling limits (remember, that we need to import 35k+ bz issues). The downside is that such rehydration requires the empty repo and we cannot delete the current llvm-project: this way we will lose releases, fork connections, stars and watches. Unfortunately, there is no way to recreate releases while keeping the origins dates, so this is a no-go for us. Losing...

> If we are reasonably certain that no one would be opening new issues on GitHub while the migration is running... And pull requests (the numbering is common for issues and pull requests) as well. And we cannot disable pull requests at all. And I'm afraid the issues will need to be opened as well during the migration. And now the real problem: should an "extr...

...e good ideas here were from others, and all the bad parts I misremembered or invented. > > > > > > Hi, > > I want to restart this discussion. There seemed to be support for this, > but we got held up trying to decide on the appropriate set of tags to > use to classify issues. > > I propose that we move forward with this proposal and disable creation of > new bugs in bugzilla on Feb 11, and require all new bugs be filed via GitHub > issues from that date forward. > > I think that for choosing the tags to use, we should just take requests > from the...

210 issues have been filed on github so far. That's negligible compared to the total number we have, so a minor additional effort for those seems acceptable if we can't actually clean them out and reuse the numbers. So suppose we start with bugzilla issue #211 and migrate the issues to github one at...

...#39;s needs as a bug-tracking system. In our previous attempt to raise this on llvm-dev [1] we shared our idea to put the clangd issue tracker on GitHub. The participants raised multiple concerns, including the migration costs, whether GitHub is the right choice as an issue tracker, whether moving issues for clangd only will result in unwanted community fragmentation and others These are all valid concerns, but a big portion of the thread was focused on migration of the existing bugs, community fragmentation issues, etc. We feel it would also be useful to ask a more focused question on whether usi...

...red or invented. > >>> > >>> > >> > >> Hi, > >> > >> I want to restart this discussion. There seemed to be support for this, > >> but we got held up trying to decide on the appropriate set of tags to > >> use to classify issues. > >> > >> I propose that we move forward with this proposal and disable creation > of > >> new bugs in bugzilla on Feb 11, and require all new bugs be filed via > GitHub > >> issues from that date forward. > >> > >> I think that for choos...

...sts.llvm.org/pipermail/llvm-dev/2019-October/136162.html == What has changed: * You will be able to subscribe to notifications for a specific issue labels. We have a proof of concept notification system using github actions that will be used for this. * Emails will be sent to llvm-bugs when issues are opened or closed. * We have the initial list of labels: https://github.com/llvm/llvm-project/labels == Remaining issue: * There is one remaining issue that I don't feel we have consensus on, and that is what to do with bugs in the existing bugzilla. Here are some options that we have di...

I have been doing some testing with Samba and using MYSQL as the passdb backend (no it is not the security issue mentioned in the samba how-to) I found what I believe is is a serious security issue and I am not sure if this security issue is an operating system issue or a Samba issue that should be looked at by the Samba team. Is there such a place as to report such security concerns to the

...ntil 10.0.0 is released, in order to keep all the blockers in one place? >> > > Yes, I think this makes sense, let's postpone until then. > Hi, 10.0.0-rc4 was just released, and I think we are at the point in the release cycle where it is safe to begin the migration to GitHub issues. I would like to propose doing the migration in one week (March 23). This means making the existing bugzilla read-only, and updating the documentation to tell users to file issues at GitHub. We are still trying to figure out the best way to import bugs from bugzilla into GitHub, so this step wil...

...? > >> > > > > Yes, I think this makes sense, let's postpone until then. > > > > Hi, > > 10.0.0-rc4 was just released, and I think we are at the point in the release cycle > where it is safe to begin the migration to GitHub issues. > > I would like to propose doing the migration in one week (March 23). This means > making the existing bugzilla read-only, and updating the documentation to tell users > to file issues at GitHub. > > > Don't forget to update the URL used in crash message...

...>>>> >>> >>> Yes, I think this makes sense, let's postpone until then. >>> >> >> Hi, >> >> 10.0.0-rc4 was just released, and I think we are at the point in the release cycle >> where it is safe to begin the migration to GitHub issues. >> >> I would like to propose doing the migration in one week (March 23). This means >> making the existing bugzilla read-only, and updating the documentation to tell users >> to file issues at GitHub. We are still trying to figure out the best way to import bugs >>...