Skip to content

v0.6.0 — RELAY spec v0.2 conformance

Choose a tag to compare

View all tags
@SoundMatt SoundMatt released this 17 Jun 00:29
· 20 commits to main since this release
v0.6.0
9325d62
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's new

Full conformance with RELAY spec v0.2 across all three priority tiers.

P0 — Breaking renames

  • MessageType constants now use the MsgType prefix: MsgTypeRequest, MsgTypeResponse, MsgTypeNotification, MsgTypeError, MsgTypeRequestNoReturn, and all TP variants
  • ReturnCode constants now use the Ret prefix: RetOK, RetNotOK, RetUnknownService, etc.
  • SubscribeConfig/Option/ApplySubscribeOpts renamed to SubscriberConfig/Option/ApplySubscriberOpts (now type aliases for relay.SubscriberConfig/Option)
  • ErrNotReady renamed to ErrNotConnected

P1 — RELAY conformance (spec §5, §10, §14, §15, §17)

  • Error sentinels wrap relay.ErrClosed/ErrTimeout/ErrNotConnected/ErrPayloadTooLarge so errors.Is(err, relay.ErrXxx) works across the stack
  • New ErrPayloadTooLarge wrapping relay.ErrPayloadTooLarge
  • BackPressurePolicy with DropNewest/DropOldest/Block and WithBackPressure option
  • SOMEIPProtocolVersion = 0x01; codec.Decode rejects frames with a different version
  • JSON tags on Message fields
  • Message.ToMessage() / FromMessage() envelope conversion
  • Adapt(Service) relay.Caller — protocol-agnostic application interface
  • SpecVersion = "0.2"
  • cmd/go-someip: version, capabilities, status CLI commands

P2 — Optional interfaces (spec §9)

  • HealthProvider, MetricsProvider, Drainer

FuSa

  • 112 atomic SEOOC requirements in .fusa-reqs.json (up from 71)

Fixes

  • Closes #30, #31, #32
  • RELAY issue #12 filed documenting the Subscribe EventID gap in relay.Node

Full Changelog: v0.5.0...v0.6.0

Assets 2
Loading