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.

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

Sereal corruption redux? #12

Open
dasyurid opened this issue Aug 6, 2021 · 2 comments
Open

Sereal corruption redux? #12

dasyurid opened this issue Aug 6, 2021 · 2 comments

Comments

@dasyurid
Copy link

dasyurid commented Aug 6, 2021

  • Plugin version: 1.17
  • Perl version: 5.32.1
  • Operating system: Ubuntu 20.04.2 LTS

Repeated (multiple / s) errors from Sereal (4.018) of the same type as issue #6.

Example:
Mojo::Reactor::Poll: I/O watcher failed: Sereal: Error: Unexpected tag SRL_HDR_ARRAYREF_4 while expecting a stringish type at offset 2503 of input at srl_decoder.c line 1118 at /opt/perlbrew/perls/perl-5.32.1/lib/site_perl/5.32.1/Mojo/MemoryMap/Writer.pm line 19, line 960.

There are are variety of details in the errors, but all are of the same general form and all trace back to MemoryMap::Writer line 19. "Bad tag", "unexpected end of packet", "bad COPY tag", "unexpected end of input stream", 'No THAW method defined for class 'åE/4#Áªzù�&'', etc. Happy to supply further details if it will be helpful, but this seems to be more effect than cause.

@nicomen
Copy link

nicomen commented Jun 2, 2022

For us in 5.34.0 and Ubuntu 22.04 LTS the problem seemed to go away when we removed an addiitonal route that was matching the route set up with the Status-plugin. The conflicting route was fetched a lot and the expected route was shown, but maybe the plugin one was triggered too?

Unsure if there was some kind of loop going on or too many parallell requests, or if it was a too big stash (with cyclic references) or something like that was causing this.

@nicomen
Copy link

nicomen commented Jun 21, 2022

Seems we suddenly got the error back after all :-/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants