Fixed an timing issue with near cache clear #74
Merged
Oracle GitHub Guidelines / guidelines/oracle
succeeded
Mar 11, 2024 in 10m 55s
PR meets Oracle’s guidelines for GitHub repositories
Thank you for your pull request. Congratulations, this PR meets all guidelines for Oracle's repositories on GitHub! In detail:
| Category | Messages |
|---|---|
| repo | ⚫ The check regarding repository naming standards was skipped because repository settings checks only run on the default branch of Oracle repositories. |
| license | ✅ The file LICENSE.txt exists at the top level. ✅ The file LICENSE.txt is plain-text and has UNIX line endings. |
| readme | ✅ The file README.md exists at the top level. ✅ The file README.md does not contain a level one heading with the title. ✅ The file README.md contains the required section "installation", "getting started", "documentation" or "how to run". ✅ The file README.md contains the required section "contributing". ✅ The file README.md contains the required section "security". ✅ The file README.md contains the required section "license". ✅ The file README.md contains a reference to Contributing. |
| contributing | ✅ The file CONTRIBUTING.md exists at the top level. ✅ The file CONTRIBUTING.md does not contain a level one heading with the title. ✅ The file CONTRIBUTING.md contains the required section "opening issues". ✅ The file CONTRIBUTING.md contains the required section "contributing code". ✅ The file CONTRIBUTING.md contains the required section "pull request process". ✅ The file CONTRIBUTING.md contains the required section "code of conduct". ✅ The file CONTRIBUTING.md contains a reference to Oracle Contributor Agreement Application. |
| security | ✅ The file SECURITY.md exists at the top level. ✅ The file SECURITY.md contains Oracle's instructions for reporting security vulnerabilities. |
| default branch | ⚫ The default branch check was skipped due to the audited branch not being the default. |
Thank you for your contribution!