[jira] [Commented] (DISPATCH-1214) Valgrind finds invalid reads and many leaks during the unit tests
[ https://issues.apache.org/jira/browse/DISPATCH-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720815#comment-16720815 ] ASF subversion and git services commented on DISPATCH-1214: --- Commit 09c59f23cbfd29f0d5a09ebe24b00f883d625ec0 in qpid-dispatch's branch refs/heads/master from [~ganeshmurthy] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=09c59f2 ] DISPATCH-1214 - Fix a set of valgrind issues. More to come > Valgrind finds invalid reads and many leaks during the unit tests > - > > Key: DISPATCH-1214 > URL: https://issues.apache.org/jira/browse/DISPATCH-1214 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.4.1 >Reporter: Ken Giusti >Priority: Major > Fix For: 1.5.0 > > Attachments: grinder-report.txt > > > See the attached grinder report -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1216) [tools] Scraper should sort links by source/target address
[ https://issues.apache.org/jira/browse/DISPATCH-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720559#comment-16720559 ] ASF subversion and git services commented on DISPATCH-1216: --- Commit b7f7b13c71b82e744aec941e2de0638999283047 in qpid-dispatch's branch refs/heads/master from [~chug] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=b7f7b13 ] DISPATCH-1216: Scraper improve --split performance and display * use lightweight parser for attach lines * sort address tables alphabetically * show/hide gizmos for address tables > [tools] Scraper should sort links by source/target address > -- > > Key: DISPATCH-1216 > URL: https://issues.apache.org/jira/browse/DISPATCH-1216 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Tools >Affects Versions: 1.5.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1222) coverity static analysis reports several issues
[ https://issues.apache.org/jira/browse/DISPATCH-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720526#comment-16720526 ] ASF subversion and git services commented on DISPATCH-1222: --- Commit 16674f44b0cdf037614e8e4378e24e9af0eb7ab9 in qpid-dispatch's branch refs/heads/master from Kenneth Giusti [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=16674f4 ] DISPATCH-1222: clean up various issues reported by coverity > coverity static analysis reports several issues > --- > > Key: DISPATCH-1222 > URL: https://issues.apache.org/jira/browse/DISPATCH-1222 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.4.1 >Reporter: Ken Giusti >Priority: Major > Fix For: 1.5.0 > > Attachments: errors.txt > > > Analysis summary report: > > Files analyzed : 93 > Total LoC input to cov-analyze : 70993 > Functions analyzed : 1597 > Paths analyzed : 21 > Time taken by analysis : 00:00:36 > Defect occurrences found : 157 Total >4 ATOMICITY >1 CONSTANT_EXPRESSION_RESULT >4 DC.WEAK_CRYPTO >2 DEADCODE >8 FORWARD_NULL >5 MISSING_LOCK >1 NEGATIVE_RETURNS >1 OVERLAPPING_COPY > 16 PRINTF_ARGS > 110 RESOURCE_LEAK >1 STRING_NULL >1 UNUSED_VALUE >3 USE_AFTER_FREE -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1222) coverity static analysis reports several issues
Ken Giusti created DISPATCH-1222: Summary: coverity static analysis reports several issues Key: DISPATCH-1222 URL: https://issues.apache.org/jira/browse/DISPATCH-1222 Project: Qpid Dispatch Issue Type: Bug Components: Router Node Affects Versions: 1.4.1 Reporter: Ken Giusti Fix For: 1.5.0 Attachments: errors.txt Analysis summary report: Files analyzed : 93 Total LoC input to cov-analyze : 70993 Functions analyzed : 1597 Paths analyzed : 21 Time taken by analysis : 00:00:36 Defect occurrences found : 157 Total 4 ATOMICITY 1 CONSTANT_EXPRESSION_RESULT 4 DC.WEAK_CRYPTO 2 DEADCODE 8 FORWARD_NULL 5 MISSING_LOCK 1 NEGATIVE_RETURNS 1 OVERLAPPING_COPY 16 PRINTF_ARGS 110 RESOURCE_LEAK 1 STRING_NULL 1 UNUSED_VALUE 3 USE_AFTER_FREE -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton pull request #146: NO-JIRA: [c] prefer linking with static libra...
Github user jdanekrh closed the pull request at: https://github.com/apache/qpid-proton/pull/146 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #146: NO-JIRA: [c] prefer linking with static library in f...
Github user jdanekrh commented on the issue: https://github.com/apache/qpid-proton/pull/146 out of date, see https://github.com/apache/qpid-proton/pull/172 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #143: NO-JIRA: [c] link fuzzing binaries using CXX linker
Github user jdanekrh commented on the issue: https://github.com/apache/qpid-proton/pull/143 out of date, see https://github.com/apache/qpid-proton/pull/172 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton pull request #143: NO-JIRA: [c] link fuzzing binaries using CXX ...
Github user jdanekrh closed the pull request at: https://github.com/apache/qpid-proton/pull/143 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton pull request #172: NO-JIRA: c/test/fuzz patches from oss-fuzz
GitHub user jdanekrh opened a pull request: https://github.com/apache/qpid-proton/pull/172 NO-JIRA: c/test/fuzz patches from oss-fuzz * NO-JIRA: [c] prefer linking with static library in fuzz tests * NO-JIRA: [c] link fuzzing binaries using CXX linker this supersedes https://github.com/apache/qpid-proton/pull/146 and https://github.com/apache/qpid-proton/pull/143 You can merge this pull request into a Git repository by running: $ git pull https://github.com/jdanekrh/qpid-proton jd_oss-fuzz-patch Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/172.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #172 commit a0d2345bec4e7538ad7df535323a8acd8bec2d36 Author: Jiri Danek Date: 2018-12-13T13:52:09Z NO-JIRA: c/test/fuzz patches from oss-fuzz * NO-JIRA: [c] prefer linking with static library in fuzz tests * NO-JIRA: [c] link fuzzing binaries using CXX linker --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
Everyone who replied is agreed on migrating now, so per the original mail I will raise the request shortly (once this mail is archived) to get things under way. Robbie On Mon, 10 Dec 2018 at 16:10, Robbie Gemmell wrote: > > Hi Folks, > > Per the below mail sent by the ASF Infrastructure team (to dev@), our Git > repositories will be migrated from the original/old git-wip-us service on to > the newer gitbox.apache.org service by February 7th. > > This is definitely happening, but we have some say over when/how it does: > 1. Document consensus on list and voluntarily request to move by Jan 9th. > 2. Wait for mandated move between Jan 9th and Feb 6th, coordinate with infra >to proceed once it has been. > 3. Do nothing, ignore the mandate, and be forcibly moved on Feb 7th. > > I'm in favour of volunteering and doing it sooner than later, so to > that end here is my lazy consensus statement: > > Unless there is discussion here resulting in decision to delay, I will > raise the migration request JIRA with Infra on Thursday 13th Dec, > hopefully allowing completion of the process by the end of this week > if they have bandwidth to do so. > > Robbie > > On Fri, 7 Dec 2018 at 16:52, Daniel Gruno wrote: > > > > [NOTICE] Mandatory relocation of Apache git repositories on > > git-wip-us.apache.org > > > > > > [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE > > DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] > > > > Hello Apache projects, > > > > I am writing to you because you may have git repositories on the > > git-wip-us server, which is slated to be decommissioned in the coming > > months. All repositories will be moved to the new gitbox service which > > includes direct write access on github as well as the standard ASF > > commit access via gitbox.apache.org. > > > > ## Why this move? ## > > The move comes as a result of retiring the git-wip service, as the > > hardware it runs on is longing for retirement. In lieu of this, we > > have decided to consolidate the two services (git-wip and gitbox), to > > ease the management of our repository systems and future-proof the > > underlying hardware. The move is fully automated, and ideally, nothing > > will change in your workflow other than added features and access to > > GitHub. > > > > ## Timeframe for relocation ## > > Initially, we are asking that projects voluntarily request to move > > their repositories to gitbox, hence this email. The voluntary > > timeframe is between now and January 9th 2019, during which projects > > are free to either move over to gitbox or stay put on git-wip. After > > this phase, we will be requiring the remaining projects to move within > > one month, after which we will move the remaining projects over. > > > > To have your project moved in this initial phase, you will need: > > > > - Consensus in the project (documented via the mailing list) > > - File a JIRA ticket with INFRA to voluntarily move your project repos > >over to gitbox (as stated, this is highly automated and will take > >between a minute and an hour, depending on the size and number of > >your repositories) > > > > To sum up the preliminary timeline; > > > > - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) > >relocation > > - January 9th -> February 6th: Mandated (coordinated) relocation > > - February 7th: All remaining repositories are mass migrated. > > > > This timeline may change to accommodate various scenarios. > > > > ## Using GitHub with ASF repositories ## > > When your project has moved, you are free to use either the ASF > > repository system (gitbox.apache.org) OR GitHub for your development > > and code pushes. To be able to use GitHub, please follow the primer > > at: https://reference.apache.org/committer/github > > > > > > We appreciate your understanding of this issue, and hope that your > > project can coordinate voluntarily moving your repositories in a > > timely manner. > > > > All settings, such as commit mail targets, issue linking, PR > > notification schemes etc will automatically be migrated to gitbox as > > well. > > > > With regards, Daniel on behalf of ASF Infra. > > > > PS:For inquiries, please reply to us...@infra.apache.org, not your > > project's dev list :-). > > > > - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
