[GitHub] [qpid-dispatch] jiridanek merged pull request #1576: Bump actions/download-artifact from 2 to 3
jiridanek merged PR #1576: URL: https://github.com/apache/qpid-dispatch/pull/1576 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] jiridanek merged pull request #1577: Bump docker/build-push-action from 2 to 3
jiridanek merged PR #1577: URL: https://github.com/apache/qpid-dispatch/pull/1577 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-proton] jiridanek opened a new pull request, #373: NO-JIRA - Upgrade from Catch v2.13.7 to v2.13.9
jiridanek opened a new pull request, #373: URL: https://github.com/apache/qpid-proton/pull/373 This is last release before the jump to Catch v3, https://github.com/catchorg/Catch2/releases/tag/v3.0.1 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2346) Change PN_WEAKREF usage to PN_VOID usage to continue compiling with Proton
[ https://issues.apache.org/jira/browse/DISPATCH-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552876#comment-17552876 ] ASF subversion and git services commented on DISPATCH-2346: --- Commit db24732de7b0143428d2359c4ad8af6e842a57e4 in qpid-dispatch's branch refs/heads/dependabot/github_actions/actions/download-artifact-3 from Andrew Stitcher [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=db24732d ] DISPATCH-2346: Change PN_WEAKREF usage to PN_VOID PN_VOID is what should have been used initially as the context type in this record is not a proton PN_OBJECT class type anyway. Moreover PN_WEAKREF will soon not be exported as it probably can't be used correctly outside Proton's own libraries. > Change PN_WEAKREF usage to PN_VOID usage to continue compiling with Proton > -- > > Key: DISPATCH-2346 > URL: https://issues.apache.org/jira/browse/DISPATCH-2346 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: 1.20.0, 2.0.0 > > > Qpid Proton is changing (removing) some of the exported symbols that are > really internal to Proton and should not be used (or even cannot be correctly > used) outside Proton's own libraries. > The PN_WEAKREF class is one such example - it seems to be the wrong class for > the purpose it is being used for in dispatch. PN_VOID is the correct class in > this usage and PN_WEAKREF will stop being exported soon. So to keep dispatch > compiling PN_WEAKREF has been changed to PN_VOID. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2347) Console tests failing with 'Update your lock file with 'npm install' message
[
https://issues.apache.org/jira/browse/DISPATCH-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552874#comment-17552874
]
ASF subversion and git services commented on DISPATCH-2347:
---
Commit a193f7b2f2fdbe1a847f7429610b235dc277fc1f in qpid-dispatch's branch
refs/heads/dependabot/github_actions/docker/build-push-action-3 from Valerio
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=a193f7b2 ]
DISPATCH-2347: updates package-lock json
> Console tests failing with 'Update your lock file with 'npm install' message
>
>
> Key: DISPATCH-2347
> URL: https://issues.apache.org/jira/browse/DISPATCH-2347
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.20.0
>
>
> {noformat}
> npm ERR! code EUSAGE
> npm ERR!
> npm ERR! `npm ci` can only install packages when your package.json and
> package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock
> file with `npm install` before continuing.
> npm ERR!
> npm ERR! Invalid: lock file's type-fest@0.21.3 does not satisfy
> type-fest@0.13.1
> npm ERR! Missing: type-fest@0.21.3 from lock file
> npm ERR!
> npm ERR! Clean install a project
> npm ERR!
> npm ERR! Usage:
> npm ERR! npm ci
> npm ERR!
> npm ERR! Options:
> npm ERR! [--no-audit] [--foreground-scripts] [--ignore-scripts]
> npm ERR! [--script-shell ]
> npm ERR!
> npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
> npm ERR!
> npm ERR! Run "npm help ci" for more info
> npm ERR! A complete log of this run can be found in:
> npm ERR! /home/runner/.npm/_logs/2022-06-09T21_11_13_314Z-debug-0.log
> Error: Process completed with exit code 1. {noformat}
>
> https://github.com/apache/qpid-dispatch/runs/6821003726?check_suite_focus=true#step:3:7
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2347) Console tests failing with 'Update your lock file with 'npm install' message
[
https://issues.apache.org/jira/browse/DISPATCH-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552877#comment-17552877
]
ASF subversion and git services commented on DISPATCH-2347:
---
Commit a193f7b2f2fdbe1a847f7429610b235dc277fc1f in qpid-dispatch's branch
refs/heads/dependabot/github_actions/actions/download-artifact-3 from Valerio
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=a193f7b2 ]
DISPATCH-2347: updates package-lock json
> Console tests failing with 'Update your lock file with 'npm install' message
>
>
> Key: DISPATCH-2347
> URL: https://issues.apache.org/jira/browse/DISPATCH-2347
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.20.0
>
>
> {noformat}
> npm ERR! code EUSAGE
> npm ERR!
> npm ERR! `npm ci` can only install packages when your package.json and
> package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock
> file with `npm install` before continuing.
> npm ERR!
> npm ERR! Invalid: lock file's type-fest@0.21.3 does not satisfy
> type-fest@0.13.1
> npm ERR! Missing: type-fest@0.21.3 from lock file
> npm ERR!
> npm ERR! Clean install a project
> npm ERR!
> npm ERR! Usage:
> npm ERR! npm ci
> npm ERR!
> npm ERR! Options:
> npm ERR! [--no-audit] [--foreground-scripts] [--ignore-scripts]
> npm ERR! [--script-shell ]
> npm ERR!
> npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
> npm ERR!
> npm ERR! Run "npm help ci" for more info
> npm ERR! A complete log of this run can be found in:
> npm ERR! /home/runner/.npm/_logs/2022-06-09T21_11_13_314Z-debug-0.log
> Error: Process completed with exit code 1. {noformat}
>
> https://github.com/apache/qpid-dispatch/runs/6821003726?check_suite_focus=true#step:3:7
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2346) Change PN_WEAKREF usage to PN_VOID usage to continue compiling with Proton
[ https://issues.apache.org/jira/browse/DISPATCH-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552873#comment-17552873 ] ASF subversion and git services commented on DISPATCH-2346: --- Commit db24732de7b0143428d2359c4ad8af6e842a57e4 in qpid-dispatch's branch refs/heads/dependabot/github_actions/docker/build-push-action-3 from Andrew Stitcher [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=db24732d ] DISPATCH-2346: Change PN_WEAKREF usage to PN_VOID PN_VOID is what should have been used initially as the context type in this record is not a proton PN_OBJECT class type anyway. Moreover PN_WEAKREF will soon not be exported as it probably can't be used correctly outside Proton's own libraries. > Change PN_WEAKREF usage to PN_VOID usage to continue compiling with Proton > -- > > Key: DISPATCH-2346 > URL: https://issues.apache.org/jira/browse/DISPATCH-2346 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: 1.20.0, 2.0.0 > > > Qpid Proton is changing (removing) some of the exported symbols that are > really internal to Proton and should not be used (or even cannot be correctly > used) outside Proton's own libraries. > The PN_WEAKREF class is one such example - it seems to be the wrong class for > the purpose it is being used for in dispatch. PN_VOID is the correct class in > this usage and PN_WEAKREF will stop being exported soon. So to keep dispatch > compiling PN_WEAKREF has been changed to PN_VOID. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2345) Compilation failure against main branch of qpid-proton
[
https://issues.apache.org/jira/browse/DISPATCH-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552875#comment-17552875
]
ASF subversion and git services commented on DISPATCH-2345:
---
Commit 93ad2d1ab84ca3ff2b2b81c626bc87da52f99587 in qpid-dispatch's branch
refs/heads/dependabot/github_actions/actions/download-artifact-3 from Ganesh
Murthy
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=93ad2d1a ]
DISPATCH-2345: Fixed compilation failure by adding proton's object.h to 2
affected files
> Compilation failure against main branch of qpid-proton
> --
>
> Key: DISPATCH-2345
> URL: https://issues.apache.org/jira/browse/DISPATCH-2345
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.20.0
>
>
> {noformat}
> ../src/remote_sasl.c:162:1: error: return type defaults to ‘int’
> [-Wimplicit-int]
> 162 | PN_HANDLE(REMOTE_SASL_CTXT)
> | ^
> ../src/remote_sasl.c: In function ‘PN_HANDLE’:
> ../src/remote_sasl.c:165:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 165 | {
> | ^
> ../src/remote_sasl.c:175:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 175 | {
> | ^
> ../src/remote_sasl.c:189:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 189 | {
> | ^
> ../src/remote_sasl.c:196:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 196 | {
> | ^
> ../src/remote_sasl.c:231:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 231 | {
> | ^
> ../src/remote_sasl.c:247:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 247 | {
> | ^
> ../src/remote_sasl.c:257:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 257 | {
> | ^
> ../src/remote_sasl.c:268:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 268 | {
> | ^
> ../src/remote_sasl.c:279:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 279 | {
> | ^
> ../src/remote_sasl.c:289:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 289 | {
> | ^
> ../src/remote_sasl.c:299:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 299 | {
> | ^
> ../src/remote_sasl.c:308:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 308 | {
> | ^
> ../src/remote_sasl.c:316:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 316 | {
> | ^
> ../src/remote_sasl.c:334:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 334 | {
> | ^
> ../src/remote_sasl.c:375:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 375 | {
> | ^
> ../src/remote_sasl.c:392:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 392 | {
> | ^
> ../src/remote_sasl.c:404:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 404 | {
> | ^
> ../src/remote_sasl.c:423:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 423 | {
> | ^
> ../src/remote_sasl.c:434:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 434 | {
> | ^
> ../src/remote_sasl.c:447:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 447 | {
> | ^
> ../src/remote_sasl.c:458:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 458 | {
> | ^
> ../src/remote_sasl.c:463:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 463 | {
> | ^
> ../src/remote_sasl.c:467:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 467 | {
> | ^
> ../src/remote_sasl.c:471:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 471 | {
> | ^
> ../src/remote_sasl.c:476:38: error: storage class specified for parameter
> ‘remote_sasl_impl’
> 476 | static const pnx_sasl_implementation remote_sasl_impl = {
> | ^~~~
> ../src/remote_sasl.c:476:1: error: parameter ‘remote_sasl_impl’ is initialized
> 476 | static const pnx_sasl_implementation remote_sasl_impl = {
> | ^~
> ../src/remote_sasl.c:477:5: error: ‘remote_sasl_free’ undeclared (first use
> in this function); did you mean ‘remote_sasl_impl’?
> 477 | remote_sasl_free,
> | ^~~~
> | remote_sasl_impl
>
[jira] [Commented] (DISPATCH-2345) Compilation failure against main branch of qpid-proton
[
https://issues.apache.org/jira/browse/DISPATCH-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552872#comment-17552872
]
ASF subversion and git services commented on DISPATCH-2345:
---
Commit 93ad2d1ab84ca3ff2b2b81c626bc87da52f99587 in qpid-dispatch's branch
refs/heads/dependabot/github_actions/docker/build-push-action-3 from Ganesh
Murthy
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=93ad2d1a ]
DISPATCH-2345: Fixed compilation failure by adding proton's object.h to 2
affected files
> Compilation failure against main branch of qpid-proton
> --
>
> Key: DISPATCH-2345
> URL: https://issues.apache.org/jira/browse/DISPATCH-2345
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.20.0
>
>
> {noformat}
> ../src/remote_sasl.c:162:1: error: return type defaults to ‘int’
> [-Wimplicit-int]
> 162 | PN_HANDLE(REMOTE_SASL_CTXT)
> | ^
> ../src/remote_sasl.c: In function ‘PN_HANDLE’:
> ../src/remote_sasl.c:165:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 165 | {
> | ^
> ../src/remote_sasl.c:175:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 175 | {
> | ^
> ../src/remote_sasl.c:189:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 189 | {
> | ^
> ../src/remote_sasl.c:196:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 196 | {
> | ^
> ../src/remote_sasl.c:231:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 231 | {
> | ^
> ../src/remote_sasl.c:247:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 247 | {
> | ^
> ../src/remote_sasl.c:257:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 257 | {
> | ^
> ../src/remote_sasl.c:268:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 268 | {
> | ^
> ../src/remote_sasl.c:279:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 279 | {
> | ^
> ../src/remote_sasl.c:289:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 289 | {
> | ^
> ../src/remote_sasl.c:299:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 299 | {
> | ^
> ../src/remote_sasl.c:308:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 308 | {
> | ^
> ../src/remote_sasl.c:316:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 316 | {
> | ^
> ../src/remote_sasl.c:334:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 334 | {
> | ^
> ../src/remote_sasl.c:375:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 375 | {
> | ^
> ../src/remote_sasl.c:392:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 392 | {
> | ^
> ../src/remote_sasl.c:404:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 404 | {
> | ^
> ../src/remote_sasl.c:423:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 423 | {
> | ^
> ../src/remote_sasl.c:434:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 434 | {
> | ^
> ../src/remote_sasl.c:447:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 447 | {
> | ^
> ../src/remote_sasl.c:458:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 458 | {
> | ^
> ../src/remote_sasl.c:463:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 463 | {
> | ^
> ../src/remote_sasl.c:467:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 467 | {
> | ^
> ../src/remote_sasl.c:471:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 471 | {
> | ^
> ../src/remote_sasl.c:476:38: error: storage class specified for parameter
> ‘remote_sasl_impl’
> 476 | static const pnx_sasl_implementation remote_sasl_impl = {
> | ^~~~
> ../src/remote_sasl.c:476:1: error: parameter ‘remote_sasl_impl’ is initialized
> 476 | static const pnx_sasl_implementation remote_sasl_impl = {
> | ^~
> ../src/remote_sasl.c:477:5: error: ‘remote_sasl_free’ undeclared (first use
> in this function); did you mean ‘remote_sasl_impl’?
> 477 | remote_sasl_free,
> | ^~~~
> | remote_sasl_impl
>
[GitHub] [qpid-dispatch] jiridanek commented on pull request #1576: Bump actions/download-artifact from 2 to 3
jiridanek commented on PR #1576: URL: https://github.com/apache/qpid-dispatch/pull/1576#issuecomment-1152575815 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] jiridanek commented on pull request #1577: Bump docker/build-push-action from 2 to 3
jiridanek commented on PR #1577: URL: https://github.com/apache/qpid-dispatch/pull/1577#issuecomment-1152575643 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2348) traffic is not shown along whole path
[ https://issues.apache.org/jira/browse/DISPATCH-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwin Dondorp updated DISPATCH-2348: Description: The below setup is a 'simple' setup consisting of 4 interior routers and 6 edge routers. On the left side an ActiveMQ Artemis broker and on the right side 2 simple AMQP clients in java. In the picture below, messages are produced on the broker (left hand side) and are consumed by the client (right hand side). QPID properly shows the "Link utilization" from end-to-end (not shown in this picture) But the "Message path by address" is only shown for the last 2 hops, where also this information is expected for the whole path. !image-2022-06-10-17-35-02-115.png|width=1000! was:!image-2022-06-10-17-35-02-115.png! > traffic is not shown along whole path > - > > Key: DISPATCH-2348 > URL: https://issues.apache.org/jira/browse/DISPATCH-2348 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 1.19.0 >Reporter: Erwin Dondorp >Priority: Minor > Attachments: image-2022-06-10-17-35-02-115.png > > > The below setup is a 'simple' setup consisting of 4 interior routers and 6 > edge routers. On the left side an ActiveMQ Artemis broker and on the right > side 2 simple AMQP clients in java. > In the picture below, messages are produced on the broker (left hand side) > and are consumed by the client (right hand side). > QPID properly shows the "Link utilization" from end-to-end (not shown in this > picture) > But the "Message path by address" is only shown for the last 2 hops, where > also this information is expected for the whole path. > > !image-2022-06-10-17-35-02-115.png|width=1000! -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2348) "Message path by address" animation is not shown along whole path
[ https://issues.apache.org/jira/browse/DISPATCH-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwin Dondorp updated DISPATCH-2348: Summary: "Message path by address" animation is not shown along whole path (was: traffic is not shown along whole path) > "Message path by address" animation is not shown along whole path > - > > Key: DISPATCH-2348 > URL: https://issues.apache.org/jira/browse/DISPATCH-2348 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 1.19.0 >Reporter: Erwin Dondorp >Priority: Minor > Attachments: image-2022-06-10-17-35-02-115.png > > > The below setup is a 'simple' setup consisting of 4 interior routers and 6 > edge routers. On the left side an ActiveMQ Artemis broker and on the right > side 2 simple AMQP clients in java. > In the picture below, messages are produced on the broker (left hand side) > and are consumed by the client (right hand side). > QPID properly shows the "Link utilization" from end-to-end (not shown in this > picture) > But the "Message path by address" is only shown for the last 2 hops, where > also this information is expected for the whole path. > > !image-2022-06-10-17-35-02-115.png|width=1000! -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2348) traffic is not shown along whole path
Erwin Dondorp created DISPATCH-2348: --- Summary: traffic is not shown along whole path Key: DISPATCH-2348 URL: https://issues.apache.org/jira/browse/DISPATCH-2348 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 1.19.0 Reporter: Erwin Dondorp Attachments: image-2022-06-10-17-35-02-115.png !image-2022-06-10-17-35-02-115.png! -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2347) Console tests failing with 'Update your lock file with 'npm install' message
[
https://issues.apache.org/jira/browse/DISPATCH-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2347.
-
Fix Version/s: 1.20.0
Resolution: Fixed
> Console tests failing with 'Update your lock file with 'npm install' message
>
>
> Key: DISPATCH-2347
> URL: https://issues.apache.org/jira/browse/DISPATCH-2347
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.20.0
>
>
> {noformat}
> npm ERR! code EUSAGE
> npm ERR!
> npm ERR! `npm ci` can only install packages when your package.json and
> package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock
> file with `npm install` before continuing.
> npm ERR!
> npm ERR! Invalid: lock file's type-fest@0.21.3 does not satisfy
> type-fest@0.13.1
> npm ERR! Missing: type-fest@0.21.3 from lock file
> npm ERR!
> npm ERR! Clean install a project
> npm ERR!
> npm ERR! Usage:
> npm ERR! npm ci
> npm ERR!
> npm ERR! Options:
> npm ERR! [--no-audit] [--foreground-scripts] [--ignore-scripts]
> npm ERR! [--script-shell ]
> npm ERR!
> npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
> npm ERR!
> npm ERR! Run "npm help ci" for more info
> npm ERR! A complete log of this run can be found in:
> npm ERR! /home/runner/.npm/_logs/2022-06-09T21_11_13_314Z-debug-0.log
> Error: Process completed with exit code 1. {noformat}
>
> https://github.com/apache/qpid-dispatch/runs/6821003726?check_suite_focus=true#step:3:7
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2347) Console tests failing with 'Update your lock file with 'npm install' message
[
https://issues.apache.org/jira/browse/DISPATCH-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552764#comment-17552764
]
ASF subversion and git services commented on DISPATCH-2347:
---
Commit a193f7b2f2fdbe1a847f7429610b235dc277fc1f in qpid-dispatch's branch
refs/heads/main from Valerio
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=a193f7b2 ]
DISPATCH-2347: updates package-lock json
> Console tests failing with 'Update your lock file with 'npm install' message
>
>
> Key: DISPATCH-2347
> URL: https://issues.apache.org/jira/browse/DISPATCH-2347
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Reporter: Ganesh Murthy
>Priority: Major
>
> {noformat}
> npm ERR! code EUSAGE
> npm ERR!
> npm ERR! `npm ci` can only install packages when your package.json and
> package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock
> file with `npm install` before continuing.
> npm ERR!
> npm ERR! Invalid: lock file's type-fest@0.21.3 does not satisfy
> type-fest@0.13.1
> npm ERR! Missing: type-fest@0.21.3 from lock file
> npm ERR!
> npm ERR! Clean install a project
> npm ERR!
> npm ERR! Usage:
> npm ERR! npm ci
> npm ERR!
> npm ERR! Options:
> npm ERR! [--no-audit] [--foreground-scripts] [--ignore-scripts]
> npm ERR! [--script-shell ]
> npm ERR!
> npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
> npm ERR!
> npm ERR! Run "npm help ci" for more info
> npm ERR! A complete log of this run can be found in:
> npm ERR! /home/runner/.npm/_logs/2022-06-09T21_11_13_314Z-debug-0.log
> Error: Process completed with exit code 1. {noformat}
>
> https://github.com/apache/qpid-dispatch/runs/6821003726?check_suite_focus=true#step:3:7
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] ganeshmurthy merged pull request #1578: fix(Console): audit package.json
ganeshmurthy merged PR #1578: URL: https://github.com/apache/qpid-dispatch/pull/1578 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2347) Console tests failing with 'Update your lock file with 'npm install' message
Ganesh Murthy created DISPATCH-2347:
---
Summary: Console tests failing with 'Update your lock file with
'npm install' message
Key: DISPATCH-2347
URL: https://issues.apache.org/jira/browse/DISPATCH-2347
Project: Qpid Dispatch
Issue Type: Bug
Components: Console
Reporter: Ganesh Murthy
{noformat}
npm ERR! code EUSAGE
npm ERR!
npm ERR! `npm ci` can only install packages when your package.json and
package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock
file with `npm install` before continuing.
npm ERR!
npm ERR! Invalid: lock file's type-fest@0.21.3 does not satisfy type-fest@0.13.1
npm ERR! Missing: type-fest@0.21.3 from lock file
npm ERR!
npm ERR! Clean install a project
npm ERR!
npm ERR! Usage:
npm ERR! npm ci
npm ERR!
npm ERR! Options:
npm ERR! [--no-audit] [--foreground-scripts] [--ignore-scripts]
npm ERR! [--script-shell ]
npm ERR!
npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
npm ERR!
npm ERR! Run "npm help ci" for more info
npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2022-06-09T21_11_13_314Z-debug-0.log
Error: Process completed with exit code 1. {noformat}
https://github.com/apache/qpid-dispatch/runs/6821003726?check_suite_focus=true#step:3:7
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-proton] jiridanek merged pull request #372: Revert "NO-JIRA Workaround Travis CI package installation issues (#311)"
jiridanek merged PR #372: URL: https://github.com/apache/qpid-proton/pull/372 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8581) [Broker-J] Broker-J Query REST API improvements
[ https://issues.apache.org/jira/browse/QPID-8581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552595#comment-17552595 ] ASF subversion and git services commented on QPID-8581: --- Commit beeedc527ed24ce572cc0f3aecf4833503731f3c in qpid-broker-j's branch refs/heads/main from Daniil Kirilyuk [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=beeedc527e ] QPID-8581: [Broker-J] Broker-J Query REST API improvements (#121) Co-authored-by: vavrtom > [Broker-J] Broker-J Query REST API improvements > --- > > Key: QPID-8581 > URL: https://issues.apache.org/jira/browse/QPID-8581 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-8.0.6 >Reporter: Daniil Kirilyuk >Priority: Minor > > Existing broker REST API (including broker query API) doesn’t support such > functions as aggregation, grouping and using nested logical operators, which > could be useful for gathering broker statistics and reporting. > We suggest to add a new POST method for the endpoint /api/latest/querybroker > and supply search criteria using JSON body. (Existing GET method > implementation should stay without changes for keeping backwards > compatibility and because of difficulties of parsing complicated search > conditions from URI parameters when using GET request method). > The new functionality should add > * logical OR operator (absent in current API) > * aggregation operators AVG, CNT, MAX, MIN, SUM > * grouping aggregation > * new numeric / datetime / string functions -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8581) [Broker-J] Broker-J Query REST API improvements
[ https://issues.apache.org/jira/browse/QPID-8581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552594#comment-17552594 ] ASF GitHub Bot commented on QPID-8581: -- vavrtom merged PR #121: URL: https://github.com/apache/qpid-broker-j/pull/121 > [Broker-J] Broker-J Query REST API improvements > --- > > Key: QPID-8581 > URL: https://issues.apache.org/jira/browse/QPID-8581 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-8.0.6 >Reporter: Daniil Kirilyuk >Priority: Minor > > Existing broker REST API (including broker query API) doesn’t support such > functions as aggregation, grouping and using nested logical operators, which > could be useful for gathering broker statistics and reporting. > We suggest to add a new POST method for the endpoint /api/latest/querybroker > and supply search criteria using JSON body. (Existing GET method > implementation should stay without changes for keeping backwards > compatibility and because of difficulties of parsing complicated search > conditions from URI parameters when using GET request method). > The new functionality should add > * logical OR operator (absent in current API) > * aggregation operators AVG, CNT, MAX, MIN, SUM > * grouping aggregation > * new numeric / datetime / string functions -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-broker-j] vavrtom merged pull request #121: QPID-8581: [Broker-J] Broker-J Query REST API improvements
vavrtom merged PR #121: URL: https://github.com/apache/qpid-broker-j/pull/121 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
