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

feat: use the deck name for the file #93

Merged
merged 1 commit into from
Sep 1, 2024
Merged

Conversation

aalemayhu
Copy link
Contributor

No description provided.

@aalemayhu aalemayhu force-pushed the feat/use-supplied-deck-name branch 3 times, most recently from a3df0ca to 1ff8e19 Compare September 1, 2024 18:10
Copy link

sonarcloud bot commented Sep 1, 2024

@aalemayhu aalemayhu merged commit 71b1727 into main Sep 1, 2024
4 of 5 checks passed
@aalemayhu aalemayhu deleted the feat/use-supplied-deck-name branch September 1, 2024 18:19
aalemayhu added a commit to 2anki/server that referenced this pull request Sep 1, 2024
Unfortunately the node worker threads cannot share buffers reliably with
the main thread. I learned this the hard way 😅
So I have move all of the read writes of the APKG payload to be be based
on file system access which is thread safe since we only read after
writes.

While reviewing the code path, I discovered that we actually do a lot of
wasteful reads and writes. Essentially for every APKG generation we make
2x calls due to the renaming to provide the uploader with friendly name.
I have not measured how long this takes but instead of double work we do
this one time and rely on the create_deck having the right name.

Revert of revert #1589
Reference: 2anki/create_deck#93
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant