7c7650b7c3
Add sufficient deadlines and countermeasures to handle hung node scenario ( #19688 )
...
Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
Signed-off-by: Harshavardhana <harsha@minio.io>
2024-05-22 16:07:14 -07:00
519dbfebf6
upgrade to go1.22.x
2024-05-09 01:36:00 -07:00
4e670458b8
fix: CI warnings ( #19380 )
2024-03-28 16:44:49 -07:00
763ff085a6
Add CI tests for next branch ( #18224 )
2023-10-12 06:15:10 -07:00
49c8e16410
update CI/CD to go1.21 ( #17828 )
2023-08-10 07:13:58 -07:00
7415e1aa56
Switch to go1.20 in CI ( #16743 )
2023-03-03 10:15:03 -08:00
52f4124678
Remove go1.18 from Github workflow tests ( #16180 )
2022-12-06 09:11:20 -08:00
433b6fa8fe
upgrade golang-lint to the latest ( #15600 )
2022-08-26 12:52:29 -07:00
4c6498d726
move all CI/CD to go1.18 ( #15401 )
2022-07-25 15:27:20 -07:00
879de20edf
Set permissions for GitHub actions ( #14693 )
...
- Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions
https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs
[Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ )
> Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much.
https://www.legitsecurity.com/blog/github-privilege-escalation-vulnerability
Signed-off-by: naveensrinivasan <172697+naveensrinivasan@users.noreply.github.com>
2022-04-11 02:45:59 -07:00
3970204009
ci: Check for new go-version. Bump setup-go to v3 ( #14598 )
2022-03-25 08:56:04 -07:00
4f3290309e
Revert "disable CI/CD for draft PRs ( #13784 )"
...
This reverts commit 5a22f2cf0b
2021-11-30 09:22:17 -08:00
5a22f2cf0b
disable CI/CD for draft PRs ( #13784 )
2021-11-29 23:35:07 -08:00
c791de0e1e
re-implement pickValidInfo dataDir, move to quorum calculation ( #13681 )
...
dataDir loosely based on maxima is incorrect and does not
work in all situations such as disks in the following order
- xl.json migration to xl.meta there may be partial xl.json's
leftover if some disks are not yet connected when the disk
is yet to come up, since xl.json mtime and xl.meta is
same the dataDir maxima doesn't work properly leading to
quorum issues.
- its also possible that XLV1 might be true among the disks
available, make sure to keep FileInfo based on common quorum
and skip unexpected disks with the older data format.
Also, this PR tests upgrade from older to a newer release if the
data is readable and matches the checksum.
NOTE: this is just initial work we can build on top of this to do further tests.
2021-11-21 10:41:30 -08:00
Shubhendu
Harshavardhana
Aditya Manthramurthy
Klaus Post
Anis Elleuch
Naveen
Sergey Zhuk
Krishnan Parthasarathi