Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Reading Leap ship data #171

Closed
cc32d9 opened this issue May 20, 2024 · 2 comments
Closed

Reading Leap ship data #171

cc32d9 opened this issue May 20, 2024 · 2 comments
Labels
triage

Comments

@cc32d9
Copy link

cc32d9 commented May 20, 2024

The Spring node should either be able to read the Leap state history directly, or there needs to be a utility to decompress it.
@enf-ci-bot enf-ci-bot moved this to Todo in Team Backlog May 20, 2024
@cc32d9
Copy link
Author

cc32d9 commented May 20, 2024

also, what happens to the ship archive continuity if the node is upgraded to Spring?

@spoonincode
Copy link
Member

log format hasn't changed from Leap4 through Spring1; you can even write to the logs in Spring1 and then use those logs in Leap4 or Leap5.

@github-project-automation github-project-automation bot moved this from Todo to Done in Team Backlog May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage
Projects
Team Backlog
Status: Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@spoonincode @cc32d9 @enf-ci-bot