-
Notifications
You must be signed in to change notification settings - Fork 1
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
Conversation
) 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`.
* @param {CoreManager} cmToReceive | ||
* @returns {Promise<void>} | ||
*/ | ||
async function addWriterCores(cmToAdd, cmToReceive) { |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Renamed in #795.
This is just a simple rename for clarity. See [this comment][0]. [0]: #783 (review)
This is just a simple rename for clarity. See [this comment][0]. [0]: #783 (review)
Partly addresses #268.