mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5866] [bug]: Errors in post-request script persist #2305
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2305
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @waquner on GitHub (Feb 11, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5866
Originally assigned to: @jamesgeorge007 on GitHub.
Is there an existing issue for this?
Platform
Desktop App
Browser
Chrome
Operating System
Windows
Bug Description
What happened
When adding a post-request script which results in an error (e.g.
foo();), after fixing the error or sometimes even after clearing the script, the test results pane says that there was an error. Sometimes closing an re-opening the request tab helps, most of the times only a restart of the app helpsConsole error messages
Steps to reproduce
https://echo.hoppscotch.io)foo();)Deployment Type
Hoppscotch Cloud
Version
v2026.1.1
https://github.com/user-attachments/assets/82567b3f-d0f7-4c1e-b70b-417848d49afb
@jamesgeorge007 commented on GitHub (Feb 11, 2026):
Thanks for reporting and for the reproduction steps. We'll be investigating. This could be related to #5810. Please try opting out of the Experimental scripting sandbox, as mentioned here.
@jamesgeorge007 commented on GitHub (Feb 24, 2026):
Quick update: This has been addressed in #5874 and is scheduled for the upcoming major release.
@jamesgeorge007 commented on GitHub (Feb 26, 2026):
Closing since this is addressed in the v2026.2.0 release.