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

fix: bettering lint and avoiding floating promises #31

Merged
merged 1 commit into from
Jun 17, 2023

Conversation

Farenheith
Copy link
Member

Some floating promises could make semaphores to be released before the work as done. We bettered lint and fixed the weak spots to prevent it from happening

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 2 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

entries: new Map([[redisKey, [realTtl, resultCopy]]]),
},
redisKey.replace(/:/g, '/'),
);
Copy link
Member Author

Choose a reason for hiding this comment

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

This points allow us to keep the s3 file with the same name of the redis key if there is no maxSavingDelay, for a better refarencing

@Farenheith Farenheith merged commit cd0577c into master Jun 17, 2023
codibrebot pushed a commit that referenced this pull request Jun 17, 2023
## [1.8.4](v1.8.3...v1.8.4) (2023-06-17)

### Bug Fixes

* bettering lint and avoiding floating promises ([#31](#31)) ([cd0577c](cd0577c))
@codibrebot
Copy link

🎉 This PR is included in version 1.8.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants