Skip to content

Fix map changing order in OTP26#135

Open
onno-vos-dev wants to merge 2 commits into
masterfrom
fix-map-changing-order-in-otp-26
Open

Fix map changing order in OTP26#135
onno-vos-dev wants to merge 2 commits into
masterfrom
fix-map-changing-order-in-otp-26

Conversation

@onno-vos-dev

Copy link
Copy Markdown
Member
  • Small fix for Task.await/2 to wait for :infinity to avoid timeouts
  • Ignore new protocol: rpcv2Cbor for now until we add support for it
  • Handle odd shapename in healthlake which does not use com.amazonaws but com.amazon

@onno-vos-dev
onno-vos-dev force-pushed the fix-map-changing-order-in-otp-26 branch from 7a8b36e to a612987 Compare July 26, 2026 16:55
- Small fix for Task.await/2 to wait for :infinity to avoid timeouts
- Ignore new protocol: rpcv2Cbor for now until we add support for it
- Handle odd shapename in healthlake which does not use com.amazonaws but com.amazon
@onno-vos-dev
onno-vos-dev force-pushed the fix-map-changing-order-in-otp-26 branch 2 times, most recently from d1b00a7 to c011a83 Compare July 26, 2026 18:36
…wshealthlakedatatransformationfrontendservice wrapped in the same spec file
@onno-vos-dev
onno-vos-dev force-pushed the fix-map-changing-order-in-otp-26 branch from c011a83 to 1a4c62e Compare July 27, 2026 06:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant