go.mod: github.com/cilium/ebpf v0.4.0#2875
Conversation
|
Seems they've renamed |
|
Argh; will probably have to redo this from my case-sensitive partition. I saw they mentioned breaking changes; doesn't look to be in the parts we use, but thought it would be good to at least test in some repositories if we can update |
|
ok, looks like |
|
Of course; that fixed it locally for me, but not in CI; added a commit that adds a |
.gitconfig
Outdated
| @@ -0,0 +1,2 @@ | |||
| [core] | |||
| ignorecase = false | |||
There was a problem hiding this comment.
Hmm... wonder why this needs to be set to false explicitly, if this is the default; git-config(1) says:
The default is false, except git-clone(1) or git-init(1) will probe and set core.ignoreCase true if appropriate when the repository is created.
There was a problem hiding this comment.
Could the "where appropriate" be the issue when it detects a case-insensitive platform?
There was a problem hiding this comment.
I could try reverting the commit to see if it was just coincidence that it passed after I added it? idk
There was a problem hiding this comment.
If this helps devs using Mac OS X I'm fine with the change as it is.
There was a problem hiding this comment.
No it didn't change my local configuration, and I'm even in doubt now if GitHub actually uses the file, or that it was sheer luck that pushing again solved the Windows linter; I rebased, and removed the commit to confirm that suspicion
|
Needs a rebase @thaJeztah |
full diff: cilium/ebpf@v0.2.0...v0.4.0 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
full diff: cilium/ebpf@v0.2.0...v0.4.0