-
Notifications
You must be signed in to change notification settings - Fork 11
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
Latest update adds extra " characters around string objects logged #48
Comments
Yeah sorry about that - seems like it may be related to changes for #42… |
Can you give v0.3.25 a try, and see if that works for you? |
I just had a chance to try, it still seems to be broken |
Hmm, ok - looks like we’ll need to roll the entire feature back for now. Thanks. |
Published v0.3.26. It seems to work as far as I've been able to test it, but I don't have access to my old Seq instance so have had to rely on somewhat more theoretical testing than usual 🙂 |
It's looking much better now on the master branch. Sorry for the hastiness in my stack_info issue. 😬 |
All good - thanks for the improvements! |
Description
The latest update seems to have added extra " characters around string objects.
vs. before (tested 0.3.20):
This of course breaks signals and json parsing and more...
What I Did
I noticed the change because we haven't touched anything logging related, but also haven't fixed the version in our requirements.txt - so the new deploys just pulled in the latest version.
The text was updated successfully, but these errors were encountered: