Skip to content

Symlink Error Does Not Mention Filesystem Dependency #423

Description

@bug5654

Before you start

  • I have read the Roadmap and this is not already planned there.
  • I have read the FAQ.
  • I have searched existing issues and found no duplicate.

Applies to

Desktop app

What problem does this solve

The user-visible error for no symlink creation on import makes no mention of filesystem type.
exFAT/FAT32 don't support symlinks. Had to reformat my underlying drive to NTFS before it would import.

Proposed solution

Change user-visible error from:
import failed: failed to link model into place: Incorrect function. (os error 1); the symlink fallback failed too: Incorrect function. (os error 1) (creating a symlink needs Windows Developer Mode or an elevated app) (Note: hand copied, not copy-pasted so may have transcription errors)

To:
Import failed: failed to link model into place: Incorrect function. (os error 1); the symlink fallback failed too: Incorrect function. (os error 1) (creating a symlink needs Windows Developer Mode or an elevated app on an NTFS partition, FAT partitions do not support symlinks)

Alternatives considered

I did clone the repo but any string literal searches came up with nothing. Tried PyTorch too with similar lack of success. Maybe I just need practice using SublimeText's Find In Files... but Ornith 1.5 was convinced it's in FreeToken's code around ft serve Ran into other issues post-linking but at least the linking worked once the underlying filesystem was compatible.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Desktopproblem related to FreeToken DesktopfeatureNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions