-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backwards compatibility for time using msgpack encoding and decoding #269
Labels
Comments
@Trial97 That commit didn't make any changes to time encoding for msgpack. |
Sorry for the inconveniences the commit that the change happened is: debb8e2, not the one mentioned before. |
That flag is only to migrate the data? |
This the best I can do. You might have to read with one handle configured one way, and write back out with another handle configured the other way. This allows you migrate. |
zhsj
added a commit
to zhsj/aptly
that referenced
this issue
Apr 13, 2019
zhsj
added a commit
to zhsj/aptly
that referenced
this issue
Apr 13, 2019
zhsj
added a commit
to zhsj/aptly
that referenced
this issue
Apr 13, 2019
smira
pushed a commit
to smira/aptly-fork
that referenced
this issue
Jul 12, 2019
smira
pushed a commit
to smira/aptly-fork
that referenced
this issue
Jul 15, 2019
smira
pushed a commit
to aptly-dev/aptly
that referenced
this issue
Jul 15, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can you please recommend some backwards compatibility :
If you encode the time in a version before the commit 5a66da2, how can we decode it in the commits after it? The used encoder is msgpack.
The error is : Error executing command: msgpack decode error [pos 131]: invalid length of bytes for decoding time - expecting 4 or 8 or 12, got 15
The text was updated successfully, but these errors were encountered: