cben
Repos
237
Followers
92
Following
282

Collaborative markdown with math

417
43

Experimenting to replace $math$ with formulas inside CodeMirror

19
2

A Ruby client for Kubernetes REST API

391
153

static API discovery GET outputs, from various versions of kubernetes

2
0

[WIP] inject forked dependencies into CI builds

WIP a stack language REPL for kids

Events

Created at 23 hours ago
Created at 23 hours ago
Created at 1 day ago
Created at 2 days ago
Created at 2 days ago
Created at 3 days ago
issue comment
[4.y] Watching resources not working in IPv6 cluster

Its not the builtin Net::HTTP, it sthe external http gem

Created at 3 days ago

informer test flakyness: try reporting problems earlier

Merge pull request #586 from grosser/grosser/flake

informer test flakyness: try reporting problems earlier

Created at 4 days ago
pull request closed
informer test flakyness: try reporting problems earlier

https://github.com/ManageIQ/kubeclient/issues/584 describes a few cases where the test got stuck and one looked like it watched twice ... one way that could happen if we retry the loop and log errors ... so let's make that explode instead so we see what the real underlying error is @cben

Created at 4 days ago
issue comment
informer test flakyness: try reporting problems earlier

another err seen locally:

  1) Failure:
RetryTest#test_can_watch_watches [/home/beni/kubeclient/test/test_informer.rb:121]:
Expected: [["ADDED"], ["ADDED"]]
  Actual: [[], ["ADDED"]]

OK, meanwhile I'll merge this and sooner or later it'll help get more info :shrug:

Created at 4 days ago
issue comment
informer test flakyness: try reporting problems earlier

I'm running this locally... But I think it's also looks good to merge.

Created at 5 days ago
issue comment
test_informer.rb fails sporadically

BTW I notice with_worker does this: sleep(0.03) # wait for worker to watch which (at least in theory) is not guaranteed. And one test does sleep(0.02) # wait for watch to finish. Generally all uses of sleep() are suspect. But I haven't dug into logic to say if any sleep race conditions are plausible explanations for any actual failure modes...

Created at 5 days ago
issue comment
test_informer.rb fails sporadically

(Yes, repo was moved under manageiq org when Alissa @abonas was leaving Red Hat so we don't depend on her for future maintainer handoffs, and in hope Adam @agrare would join or at least be backup maintainer as I'm having less and less time for it.)

Created at 5 days ago
issue comment
informer test flakyness: try reporting problems earlier

one failure in CI but not the one you modified here:

https://github.com/ManageIQ/kubeclient/actions/runs/3542843672/jobs/5948771586#step:6:247

   7) Failure:
RetryTest#test_restarts_on_error [/Users/runner/work/kubeclient/kubeclient/test/test_informer.rb:98]:
The request GET /\/v1\/pods/ was expected to execute at least 2 times but it executed 1 time

The following requests were made:

GET http://localhost:8080/api/v1/pods?resourceVersion=0 with headers {'Accept'=>'*/*', 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 'User-Agent'=>'Faraday v1.10.2'} was made 1 time
GET http://localhost:8080/api/v1/watch/pods?resourceVersion=1 with headers {'Connection'=>'close', 'Host'=>'localhost:8080', 'User-Agent'=>'http.rb/5.1.0'} was made 1 time
Created at 5 days ago
Created at 5 days ago
Created at 1 week ago
Created at 1 week ago
Created at 1 week ago

Update rake development dependency to version 13

Change http gem dependency requirement to allow version 5

Merge branch 'master' into httprb-update

Merge pull request #571 from nielsslot/httprb-update

Update HTTP gem requirement to allow version 5

Created at 1 week ago
pull request closed
Update HTTP gem requirement to allow version 5

I wanted to use kubeclient in a project and noticed it required me to downgrade the version of the http gem to version 4. Version 5.0.0 of the http gem was released more than a year ago. Their changelog notes some breaking changes, but none of them seem to impact the usage in kubeclient.

This pull request also updates the rake development dependency to version 13. It looks like version 13 was released almost three years ago. Updating it was the easiest way to use version 5 of the http gem in kubeclient since it is dependent on the llhttp-ffi gem, which apparently is dependent on rake 13. I very much doubt that llhttp-ffi actually needs rake at runtime, but it is what it is. And actually updating rake here does make sense after three years.

Created at 1 week ago
pull request reopened
Update HTTP gem requirement to allow version 5

I wanted to use kubeclient in a project and noticed it required me to downgrade the version of the http gem to version 4. Version 5.0.0 of the http gem was released more than a year ago. Their changelog notes some breaking changes, but none of them seem to impact the usage in kubeclient.

This pull request also updates the rake development dependency to version 13. It looks like version 13 was released almost three years ago. Updating it was the easiest way to use version 5 of the http gem in kubeclient since it is dependent on the llhttp-ffi gem, which apparently is dependent on rake 13. I very much doubt that llhttp-ffi actually needs rake at runtime, but it is what it is. And actually updating rake here does make sense after three years.

Created at 1 week ago
pull request closed
Update HTTP gem requirement to allow version 5

I wanted to use kubeclient in a project and noticed it required me to downgrade the version of the http gem to version 4. Version 5.0.0 of the http gem was released more than a year ago. Their changelog notes some breaking changes, but none of them seem to impact the usage in kubeclient.

This pull request also updates the rake development dependency to version 13. It looks like version 13 was released almost three years ago. Updating it was the easiest way to use version 5 of the http gem in kubeclient since it is dependent on the llhttp-ffi gem, which apparently is dependent on rake 13. I very much doubt that llhttp-ffi actually needs rake at runtime, but it is what it is. And actually updating rake here does make sense after three years.

Created at 1 week ago