You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Schedule tables are now parsed into Python objects
Changed
The delay of schedule entries in the dictionary now have a floating point type and their unit
has been normalized to seconds
Fixed
Added missing UnassignFrameId command to JSON schema
Migration guide for 0.13.0
Any reference to ldf['schedule_tables'][id]['schedule'][entry]['delay'] that assumes that
milliseconds are used as the unit has to be updated to either multiply the current value by 1000
or somehow change the assumption about the unit to seconds.
All numeric values that have an associated unit have their SI prefix removed during parsing, for
example kbps is converted into bps. The schedule entry delay was one case where it wasn't
handled accordingly.
This discussion was created from the release v0.13.0.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Added
Changed
has been normalized to seconds
Fixed
UnassignFrameId
command to JSON schemaMigration guide for 0.13.0
ldf['schedule_tables'][id]['schedule'][entry]['delay']
that assumes thatmilliseconds are used as the unit has to be updated to either multiply the current value by
1000
or somehow change the assumption about the unit to seconds.
All numeric values that have an associated unit have their SI prefix removed during parsing, for
example
kbps
is converted intobps
. The schedule entry delay was one case where it wasn'thandled accordingly.
This discussion was created from the release v0.13.0.
Beta Was this translation helpful? Give feedback.
All reactions