sequence-contract violation in test
Open
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 68
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
http://drdr.racket-lang.org/54316/cs/racket/share/pkgs/gui-test/framework/tests/frame.rkt
sequence-contract-violation: negative: method delete cannot be called, except in states (unlocked), args 0 1
context...:
do-error
.../wxme/undo.rkt:68:4: !undo method in insert-record%
.../wxme/editor.rkt:954:8: loop
.../wxme/editor.rkt:950:2: !perform-undos method in editor%
.../wxme/editor.rkt:835:2: !undo method in editor%
.../tests/frame.rkt:107:5
.../common/queue.rkt:435:6
call-in-empty-metacontinuation-frame
[repeats 1 more time]
.../common/queue.rkt:486:32
.../private/more-scheme.rkt:148:2: call-with-break-parameterization
call-in-empty-metacontinuation-frame
.../common/queue.rkt:374:13: loop
call-in-empty-metacontinuation-frame
call-with-empty-metacontinuation-frame-for-swap
cc @racket/ci
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with gui-test/framework/tests/frame.rkt, especially the failing location at line 107, and trace the undo path through wxme/undo.rkt and wxme/editor.rkt. Reproduce the sequence-contract violation and determine why delete is called while the editor is not unlocked. Done means the test no longer raises this violation.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100