[GitHub] [qpid-dispatch] dependabot[bot] commented on pull request #1565: Bump typescript from 4.6.2 to 4.7.2 in /console/react
dependabot[bot] commented on PR #1565: URL: https://github.com/apache/qpid-dispatch/pull/1565#issuecomment-1147675053 Superseded by #1572. -- 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] dependabot[bot] opened a new pull request, #1572: Bump typescript from 4.6.2 to 4.7.3 in /console/react
dependabot[bot] opened a new pull request, #1572: URL: https://github.com/apache/qpid-dispatch/pull/1572 Bumps [typescript](https://github.com/Microsoft/TypeScript) from 4.6.2 to 4.7.3. Release notes Sourced from https://github.com/Microsoft/TypeScript/releases;>typescript's releases. TypeScript 4.7.3 For release notes, check out the https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/;>release announcement. For the complete list of fixed issues, check out the https://github.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.7.0%22+;>fixed issues query for Typescript 4.7.0 (Beta). https://github.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.7.1%22+;>fixed issues query for Typescript 4.7.1 (RC). https://github.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.7.2%22+;>fixed issues query for Typescript 4.7.2 (Stable). https://github.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.7.3%22+;>fixed issues query for Typescript 4.7.3 (Stable). Downloads are available on: https://www.npmjs.com/package/typescript;>npm https://marketplace.visualstudio.com/items?itemName=TypeScriptTeam.TypeScript-473;>Visual Studio 2022/2019 (https://github.com/Microsoft/TypeScript/wiki/Updating-TypeScript-in-Visual-Studio-2017;>Select new version in project options) https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild;>NuGet package TypeScript 4.7.2 For release notes, check out the https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/;>release announcement. For the complete list of fixed issues, check out the https://github.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.7.0%22+;>fixed issues query for Typescript 4.7.0 (Beta). https://github.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.7.1%22+;>fixed issues query for Typescript 4.7.1 (RC). https://github.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.7.2%22+;>fixed issues query for Typescript 4.7.2 (Stable). Downloads are available on: https://www.npmjs.com/package/typescript;>npm https://marketplace.visualstudio.com/items?itemName=TypeScriptTeam.TypeScript-472;>Visual Studio 2022/2019 (https://github.com/Microsoft/TypeScript/wiki/Updating-TypeScript-in-Visual-Studio-2017;>Select new version in project options) https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild;>NuGet package TypeScript 4.7 RC For release notes, check out the https://devblogs.microsoft.com/typescript/announcing-typescript-4-7-rc/;>release announcement. For the complete list of fixed issues, check out the https://github.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.7.0%22+;>fixed issues query for Typescript 4.7.0 (Beta). https://github.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.7.1%22+;>fixed issues query for Typescript 4.7.1 (RC). Downloads are available on: https://www.npmjs.com/package/typescript;>npm https://marketplace.visualstudio.com/items?itemName=TypeScriptTeam.TypeScript-47rc;>Visual Studio 2022/2019 (https://github.com/Microsoft/TypeScript/wiki/Updating-TypeScript-in-Visual-Studio-2017;>Select new version in project options) https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild;>NuGet package TypeScript 4.7 Beta For release notes, check out the https://devblogs.microsoft.com/typescript/announcing-typescript-4-7-beta/;>release announcement. For the complete list of fixed issues, check out the ... (truncated) Commits https://github.com/microsoft/TypeScript/commit/e5050bb405548a127b0a48a264bade6fd662ce06;>e5050bb Bump version to 4.7.3 and LKG https://github.com/microsoft/TypeScript/commit/4c4c80322a1512391d2708a9008e910401c16ca1;>4c4c803 烙 Pick PR https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/49360;>#49360 (Expose import mode calculation func...) into release-4.7 (#... https://github.com/microsoft/TypeScript/commit/3ce08c6ba14eb6f9062f29462bd0ac2d5bada5c5;>3ce08c6 fix(49223): checker.getTypeAtLocation for ExpressionWithTypeArguments returns... https://github.com/microsoft/TypeScript/commit/3bf0d30686e81c8f91c954eb0bd18a19b0a544b2;>3bf0d30 Pick PR https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/49356;>#49356 (Add nightly-only error on ImportType resolution mode assertio... https://github.com/microsoft/TypeScript/commit/5f7f0b1d57fdbc166c3969a3dd3f19f15ba0388e;>5f7f0b1 Cherry-pick PR https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/49361;>#49361 into release-4.7 (https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/49364;>#49364) https://github.com/microsoft/TypeScript/commit/c07d883428845a321c7379c7d326e13f7aad8974;>c07d883 Cherry-pick PR
[GitHub] [qpid-dispatch] dependabot[bot] closed pull request #1565: Bump typescript from 4.6.2 to 4.7.2 in /console/react
dependabot[bot] closed pull request #1565: Bump typescript from 4.6.2 to 4.7.2 in /console/react URL: https://github.com/apache/qpid-dispatch/pull/1565 -- 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] (PROTON-2554) [proton-j] CompositeReadableBuffer read string API not advancing position index
[ https://issues.apache.org/jira/browse/PROTON-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550581#comment-17550581 ] ASF subversion and git services commented on PROTON-2554: - Commit c0927ce8e2212d6f4b49cdbcc7d31d46c15f8c80 in qpid-proton-j's branch refs/heads/main from Timothy Bish [ https://gitbox.apache.org/repos/asf?p=qpid-proton-j.git;h=c0927ce8 ] PROTON-2554 Fix composite buffer read string APIs position updates The API indicates the read string methods should advance the position to the limit but the composite is not doing that. > [proton-j] CompositeReadableBuffer read string API not advancing position > index > --- > > Key: PROTON-2554 > URL: https://issues.apache.org/jira/browse/PROTON-2554 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: proton-j-0.33.10 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: proton-j-0.34.0 > > > The ReadableBuffer API provides methods for reading a string from the > remaining readable bytes in the buffer and documents these methods should > advance the read index to the limit on return. The composite readable buffer > isn't advancing the position as it passes the bytes off to a CharsetDecoder > as a raw array and doesn't complete the operation with a position(limit) > call. This is masked in proton-j currently as all string decodes are done > from slices of a buffer or in some cases a duplicate and the buffer slice is > cast off afterwards without care for any remaining bytes. -- 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] (PROTON-2554) [proton-j] CompositeReadableBuffer read string API not advancing position index
[ https://issues.apache.org/jira/browse/PROTON-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish updated PROTON-2554: Summary: [proton-j] CompositeReadableBuffer read string API not advancing position index (was: [proton-j] CompositeReadableBuffer read string API no advancing position index) > [proton-j] CompositeReadableBuffer read string API not advancing position > index > --- > > Key: PROTON-2554 > URL: https://issues.apache.org/jira/browse/PROTON-2554 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: proton-j-0.33.10 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: proton-j-0.34.0 > > > The ReadableBuffer API provides methods for reading a string from the > remaining readable bytes in the buffer and documents these methods should > advance the read index to the limit on return. The composite readable buffer > isn't advancing the position as it passes the bytes off to a CharsetDecoder > as a raw array and doesn't complete the operation with a position(limit) > call. This is masked in proton-j currently as all string decodes are done > from slices of a buffer or in some cases a duplicate and the buffer slice is > cast off afterwards without care for any remaining bytes. -- 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] (PROTON-2554) [proton-j] CompositeReadableBuffer read string API no advancing position index
Timothy A. Bish created PROTON-2554: --- Summary: [proton-j] CompositeReadableBuffer read string API no advancing position index Key: PROTON-2554 URL: https://issues.apache.org/jira/browse/PROTON-2554 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: proton-j-0.33.10 Reporter: Timothy A. Bish Assignee: Timothy A. Bish Fix For: proton-j-0.34.0 The ReadableBuffer API provides methods for reading a string from the remaining readable bytes in the buffer and documents these methods should advance the read index to the limit on return. The composite readable buffer isn't advancing the position as it passes the bytes off to a CharsetDecoder as a raw array and doesn't complete the operation with a position(limit) call. This is masked in proton-j currently as all string decodes are done from slices of a buffer or in some cases a duplicate and the buffer slice is cast off afterwards without care for any remaining bytes. -- 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] [Assigned] (PROTON-2553) Hang in proactor thread waiting for PN_PROACTOR_INTERRUPT
[ https://issues.apache.org/jira/browse/PROTON-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-2553: -- Assignee: Clifford Jansen > Hang in proactor thread waiting for PN_PROACTOR_INTERRUPT > - > > Key: PROTON-2553 > URL: https://issues.apache.org/jira/browse/PROTON-2553 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.37.0 >Reporter: Ken Giusti >Assignee: Clifford Jansen >Priority: Major > > Recently changed (~2 weeks) the Skupper-router project's CI to help diagnose > very occasional timeout error that appear to be happening during router > shutdown. The CI test infrastructure now sends a SIGABORT to a router that > has not exited within 60 seconds of receiving a SIGTERM. > This resulted in a weird test failure - only captured once so far - that > appears as if the router is stuck in proactor. > See > [https://github.com/skupperproject/skupper-router/runs/6698510074#step:29:84] > for the gdb crash traceback. > And the related skupper-router issue: > [https://github.com/skupperproject/skupper-router/issues/535] > Unable to reproduce. -- 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] (PROTON-2553) Hang in proactor thread waiting for PN_PROACTOR_INTERRUPT
Ken Giusti created PROTON-2553: -- Summary: Hang in proactor thread waiting for PN_PROACTOR_INTERRUPT Key: PROTON-2553 URL: https://issues.apache.org/jira/browse/PROTON-2553 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: proton-c-0.37.0 Reporter: Ken Giusti Recently changed (~2 weeks) the Skupper-router project's CI to help diagnose very occasional timeout error that appear to be happening during router shutdown. The CI test infrastructure now sends a SIGABORT to a router that has not exited within 60 seconds of receiving a SIGTERM. This resulted in a weird test failure - only captured once so far - that appears as if the router is stuck in proactor. See [https://github.com/skupperproject/skupper-router/runs/6698510074#step:29:84] for the gdb crash traceback. And the related skupper-router issue: [https://github.com/skupperproject/skupper-router/issues/535] Unable to reproduce. -- 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
