search for: issuing

...SK-27217 <https://issues.asterisk.org/jira/browse/ASTERISK-27217>] - chan_sip: Asterisk crashing when subscription doesn't get set (Reported by Bryan Walters) - [ASTERISK-17540 <https://issues.asterisk.org/jira/browse/ASTERISK-17540>] - SDP origin attribute modified when issuing re-INVITE because of directmedia=yes (Reported by saghul) - [ASTERISK-27254 <https://issues.asterisk.org/jira/browse/ASTERISK-27254>] - alembic: prune_on_boot fix erroneous (Reported by Florian Floimair) - [ASTERISK-27232 <https://issues.asterisk.org/jira/browse/ASTERISK-272...

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

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

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:

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:

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:

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:

...(Reported by Jacek Konieczny) * ASTERISK-24066 - res_smdi: convert to astobj2 (Reported by Corey Farrell) * ASTERISK-27217 - chan_sip: Asterisk crashing when subscription doesn't get set (Reported by Bryan Walters) * ASTERISK-17540 - SDP origin attribute modified when issuing re-INVITE because of directmedia=yes (Reported by saghul) * ASTERISK-27254 - alembic: prune_on_boot fix erroneous (Reported by Florian Floimair) * ASTERISK-27232 - When in queue on g722 with interruptions, music on hold can get stuck and no longer play (Reporte...

We held a round-table at the llvm dev conference about what other pieces of Github infrastructure we may want to use. This thread in particular is about switching to github issue tracking. Use of other parts of Github functionality was also discussed -- but that should be for other email threads. Most of the ideas here were from other people. I *believe* this proposal represents the overall

Dear all, Over the last few weeks with the help of GH folks I've been exploring the options of Bugzilla migration. I believe finally we came to the viable solution which is detailed below. It turned out that GitHub has an 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

> 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 "extra" pull request or

On Thu, Jan 30, 2020 at 1:21 PM Tom Stellard via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > On 10/24/2019 07:54 PM, James Y Knight via llvm-dev wrote: > > We held a round-table at the llvm dev conference about what other pieces of Github infrastructure we may want to use. This thread in particular is about switching to github issue tracking. Use of other parts of Github

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 a time, in order. That would preserve the existing bug numbering and all existing bugs,

Hi LLVM community, As discussed earlier, we in the clangd land feel that buganizer does not address the clangd'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,

Would it make sense to wait until 10.0.0 is released, in order to keep all the blockers in one place? On Thu, Jan 30, 2020 at 1:32 PM Tom Stellard via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On 01/30/2020 10:24 AM, Aaron Ballman wrote: > > On Thu, Jan 30, 2020 at 1:21 PM Tom Stellard via cfe-dev > > <cfe-dev at lists.llvm.org> wrote: > >> >

Hi, I wanted to continue discussing the plan to migrate from Bugzilla to Github. It was suggested that I start a new thread and give a summary of the proposal and what has changed since it was originally proposed in October. == Here is the original proposal: http://lists.llvm.org/pipermail/llvm-dev/2019-October/136162.html == What has changed: * You will be able to subscribe to notifications

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

On 02/10/2020 07:40 PM, Tom Stellard wrote: > On 01/30/2020 12:47 PM, David Major wrote: >> Would it make sense to wait until 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

On 03/16/2020 08:00 AM, James Henderson wrote: > > > On Mon, 16 Mar 2020 at 14:44, Tom Stellard via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote: > > On 02/10/2020 07:40 PM, Tom Stellard wrote: > > On 01/30/2020 12:47 PM, David Major wrote: > >> Would it make sense to wait until 10.0.0 is released, in order to

On 03/16/2020 07:53 AM, Aaron Ballman wrote: > On Mon, Mar 16, 2020 at 10:44 AM Tom Stellard via cfe-dev > <cfe-dev at lists.llvm.org> wrote: >> >> On 02/10/2020 07:40 PM, Tom Stellard wrote: >>> On 01/30/2020 12:47 PM, David Major wrote: >>>> Would it make sense to wait until 10.0.0 is released, in order to keep all the blockers in one place?