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

Groovy to JSON script error #1264

Open
finglis opened this issue May 3, 2023 · 2 comments
Open

Groovy to JSON script error #1264

finglis opened this issue May 3, 2023 · 2 comments
Assignees
Labels

Comments

@finglis
Copy link
Contributor

finglis commented May 3, 2023

Bug report

Describe the bug
Error produced when groovy script is converted to JSON

To Reproduce
Steps to reproduce the behavior:

  1. Open specific groovy script in qupath
  2. Change the script to JSON via Language dropdown
  3. Will produce an error.

Expected behavior
No error, script changes to JSON

Screenshots

Desktop (please complete the following information):
Confirmed on Windows and Mac, both v0.4.3 QuPath

Additional context
See txt for error output. Original groovy script being kept private.
groovy to json script error.txt

@finglis finglis added the bug label May 3, 2023
@petebankhead
Copy link
Member

Adding link back to original discussion: https://forum.image.sc/t/potential-bug-with-load-pixel-classifier-show-as-text-qupath-v0-4-3/80470

Haven't figured out exactly what aspect of the script is troublesome, so haven't come up with a proper minimal non-working example yet :/

Even without that, we can assume that a proper solution involved removing use of regex from the styler classes... or at least handling styling errors more quietly, without having an exception pop up.

@petebankhead petebankhead self-assigned this Sep 11, 2023
@petebankhead petebankhead added this to the v0.5.0 milestone Sep 11, 2023
@petebankhead
Copy link
Member

I attempted to replicate this as a 'quickly fixable' bug.... but couldn't.

@petebankhead petebankhead removed this from the v0.5.0-rc1 milestone Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants