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: only send/receive core keys with permission #783

Merged
merged 13 commits into from
Aug 28, 2024

Conversation

EvanHahn
Copy link
Contributor

@EvanHahn EvanHahn commented Aug 27, 2024

Partly addresses #268.

EvanHahn and others added 13 commits August 27, 2024 15:32
)

Our "too many files" config import test fails on case-insensitive file
systems, such as macOS by default.

Our fixture folder had a bunch of files that would get removed on these
file systems. For example, one of `0a` and `0A` would get removed. That
meant that there were fewer than 10,001 files (as expected), and the
test would fail.

We could fix this by renaming the files, but I chose to fix this by
re-creating the fixture each time we run the test. That avoids creating
a folder with 10,001 files inside, and prevents you from having to run
`npm run test:buildConfigs`.
@EvanHahn EvanHahn changed the title WIP: Only send/receive core keys with permission feat: only send/receive core keys with permission Aug 28, 2024
@EvanHahn EvanHahn marked this pull request as ready for review August 28, 2024 16:03
@EvanHahn EvanHahn merged commit ca9b7d4 into main Aug 28, 2024
7 checks passed
@EvanHahn EvanHahn deleted the cores-only-if-permissioned branch August 28, 2024 16:06
* @param {CoreManager} cmToReceive
* @returns {Promise<void>}
*/
async function addWriterCores(cmToAdd, cmToReceive) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit @EvanHahn the naming is slightly confusing, because this is actually adding the cores "owned" by one instance to another instance, but as "read" cores, not writer cores. But I'm not sure what a better naming would be.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renamed in #795.

EvanHahn added a commit that referenced this pull request Aug 28, 2024
This is just a simple rename for clarity. See [this comment][0].

[0]: #783 (review)
gmaclennan pushed a commit that referenced this pull request Aug 29, 2024
This is just a simple rename for clarity. See [this comment][0].

[0]: #783 (review)
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.

2 participants