- 
                Notifications
    You must be signed in to change notification settings 
- Fork 748
Prune redundant traceback item at start of all traces #6589
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
Conversation
| The latest updates on your projects. Learn more about Vercel for GitHub. 
 | 
030c0a5    to
    f00b35c      
    Compare
  
    | @yairchu - can you run  | 
| 
 Sure:  | 
| @yairchu it looks like there is still an error with: unsure if it is because of different tracebacks for different python versions | 
| I'll have a look | 
| Locally I get same results in  | 
| can you try:  | 
| if it is just 3.9 causing issues, you can just ignore that version for this test | 
| nvm its just flakiness, i will merge this | 
📝 Summary
Fixse #6576
🔍 Description of Changes
When sending tracebacks to the front-end, the backend prunes the first redundant traceback item in marimo's own engine
📋 Checklist