racket / racket/drracket

DrRacket internal error for default save file location taken

Open
#798 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
516
Forks
103
PR merge metrics
No merged PRs in 30d

Description

On Racket v9.0 [cs], on a MacOS 14.3 (23D56) machine, if it matters, I encountered the following when autosave attempted:

copy-file: destination exists
  source path: /Users/jhemann/Library/Preferences/PLT-autosave-toc.rktd
  destination path: /Users/jhemann/Library/Preferences/PLT-autosave-toc-save.rktd
  context...:
   /Applications/Racket v9.0/share/pkgs/gui-lib/framework/private/autosave.rkt:57:6: notify method in autosave-timer%
   /Applications/Racket v9.0/share/pkgs/gui-lib/mred/private/wx/common/timer.rkt:34:38
   /Applications/Racket v9.0/share/pkgs/gui-lib/mred/private/wx/common/queue.rkt:436:6
   /Applications/Racket v9.0/share/pkgs/gui-lib/mred/private/wx/common/queue.rkt:487:32
   /Applications/Racket v9.0/share/pkgs/gui-lib/mred/private/wx/common/queue.rkt:639:3

The proximate cause is, as it says, that copy-file throws an error when the PLT-autosave-toc-save.rktd file already exists. But I don't believe I've done anything that an ordinary user wouldn't've done. It seems like we were prevented from clobbering an autosave list, but it surprises me that the autosave feature is limited to one list, or that the lists aren't addable, or that we aren't forced to dispense with the existing autosave list before trying to autosave the next one. IIUC.

I tried to look around, but I couldn't find where the prefixed k:copy-file is coming from in racket/private/pre-base.rkt.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at framework/private/autosave.rkt:57, the autosave-timer% notify method named in the stack trace, and inspect how the existing PLT-autosave-toc-save.rktd destination is handled. Reproduce autosave with that destination already present. Done means the reported internal error no longer occurs and the intended handling of the existing autosave list is covered.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.