-
Notifications
You must be signed in to change notification settings - Fork 2
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
Reverse names for S3 sort #2
Conversation
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.
one question to answer
e639b2d
to
f7ed1ca
Compare
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.
unit tests are broken due to Babel transforming the BigInt exponentiation operator to Math.pow
, which is incompatible with most BigInt implementations in Node. Consider either avoiding BigInts altogether, or somehow reworking babel.config.cjs
so that it knows to avoid the use of the offending Babel plugin.
Thanks, I'll run the tests and work through that |
f7ed1ca
to
d4cbe6c
Compare
d4cbe6c
to
e259898
Compare
I removed base 36 usage to focus only on correct behavior for the filename reversal. I have not yet run tests. I see that it uses docker and I'll test that when I have time to configure that setup. I'll let you know when I'm able to run tests. |
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.
lgtm - I'll merge this at a later point
Use base 36 filenames, reverse names for S3 sort
Fyi, this does not seek to fix likely pagination problems with delete