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

long var dump event gets truncated resulting in an empty payload when loading so the event is not displayed #218

Open
hanoii opened this issue Jun 28, 2024 · 1 comment
Assignees
Labels
bug Something isn't working module [var-dump]
Milestone

Comments

@hanoii
Copy link

hanoii commented Jun 28, 2024

It took me a lot of time to figure this out, although simple I thought the issue might be on my docker compose setup for some reason as I was testing a paralell instance and I saw the events persisting.

What I found is that when the event is really big, it is fully displayed browser, but once refresh the event is gone. I checked on the dotl database and the event is there, only the payload is truncated so the json is now invalid.

See https://pastebin.com/E1jTVS8k

That's the full html I get when I first see the event. Even just output that as a string performs the same behavior.

I saw the readme on VAR_DUMPER_PREVIEW_MAX_DEPTH but my understanding is that will help with the display, not the storing. I can perform a similar limit on my app, but if there is a hard set limit, I would expect some kind of either documentation, or maybe an error on the event page or maybe storing the payload with an error json or something.

If this is not the expected behavior, then this is a bug.

Using the latest version.

@butschster butschster self-assigned this Jun 28, 2024
@butschster butschster added bug Something isn't working module [var-dump] labels Jun 28, 2024
@butschster butschster added this to the 1.0 milestone Jun 28, 2024
@hanoii
Copy link
Author

hanoii commented Jun 28, 2024

Side note, I forked the project and attempted to run it to see if I could debug this myself but it wasn't as easy as I would have hoped. Spent a few hours but had a number of odd things I blindly try things out until the issue sorted but I never got to launching a proper server.

I did read all of the contrib notes in the documentation

Things I found (only to remind myself):

  • ./get-binaries.sh is hardcoded to linux, I did find the proper binaries for my osx on darwin_arm64 which I tried but then I had other issues with local ports running and some other stuff
  • I also found that the current .env.sample, when copying it as is, doesn't help running it properly as the cache driver is not longer there so that failed initially. I eventually commented everything related to the persistance and that seemed to work better
  • As I was having different local issues I then tried setting up a local docker dev instance. I personally use https://github.com/ddev/ddev and I think it could work nicely with it but also couldn't getting to run, I think what is now failing is the frontend build, which I tired to do it but I can't get past yarn install on the ddev instance with node 18 installed.

Maybe having something like ddev or some other dockerized kickstart for development can help with contributions or at least a more up to date notes or recipes into how to run this locally or steps needed to contibute to the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working module [var-dump]
Projects
Status: No status
Development

No branches or pull requests

2 participants