Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Flatland Flatland
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Flatland
  • FlatlandFlatland
  • Issues
  • #320

Closed
Open
Created Jun 03, 2020 by hagrid67@hagrid67Owner

msgpack loads agent data as garbage bytes

When loading an env with msgpack we seem to get binary garbage in the agent data. We know that msgpack doesn't handle typing.NamedTuple - it recreates a (unnamed) tuple. See #282. There is a workaround in agent_utils for this. But the data loaded still appears as garbage.

I haven't been able to reproduce this in a standalone test case (saving a named tuple etc) but can reproduce in flatland.

I believe this this did work at some point (no thanks to me).

More details to follow.

Edited Jun 03, 2020 by hagrid67
Assignee
Assign to
Time tracking