Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ofek
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
61.
▲
by
ofek
3y ago
This workflow has historically worked for us quite well. We merge in features rapidly so having GitHub be the source of truth for activity that needs to be tested is beneficial for never accidentally missing items. FYI we used to use Trello
62.
▲
by
ofek
3y ago
We install the tool and run the documented actions for the Agent repo. Example command: https://datadoghq.dev/ddqa/actions/status/
63.
▲
by
ofek
3y ago
A candidate is a commit between 2 Git references https://datadoghq.dev/ddqa/actions/create/
64.
▲
Show HN: Datadog QA – TUI for Jira users to perform QA of future GitHub releases
(github.com)
40 points
by
ofek
3y ago
|
10 comments
65.
▲
by
ofek
3y ago
Does this mean it will not be implemented?
66.
▲
by
ofek
3y ago
Update: attribution has been added to the readme file https://github.com/GoogleCloudPlatform/gcs-fuse-csi-driver/c...
67.
▲
by
ofek
3y ago
I'm not sure if you thoroughly read what I wrote but I did respond to them. This is not a false accusation as you are claiming, you can check the contents of the repo in the current state. Per the licenses they can copy but they must m
68.
▲
by
ofek
3y ago
Are you of the opinion that because a behavior is legal that necessarily makes it right in all cases? If so, I suppose that is where I disagree.
69.
▲
by
ofek
3y ago
Yes, copying the code without following up to actually collaborate or even forking to show attribution I think is bad practice for such a large organization, or any entity for that matter.
70.
▲
by
ofek
3y ago
Either, the choice is up to you. edit: as I express in a sibling comment this act is legally allowed of course, but is bad practice
71.
▲
by
ofek
3y ago
I do appreciate that Google is now officially supporting gcsfuse because it genuinely is a great project. However, their Kubernetes CSI driver seems to have in large part copied code from the one I and a co-maintainer have been working on f
72.
▲
Ask HN: Why is the first command invocation on GitHub Actions Windows image slow
1 points
by
ofek
4y ago
|
1 comments
73.
▲
Writing a CLI in Rust
(ofek.dev)
3 points
by
ofek
4y ago
|
0 comments
74.
▲
Show HN: Hatch 1.6.0 – improved build environments and support for VS Code
(hatch.pypa.io)
2 points
by
ofek
4y ago
|
0 comments
75.
▲
by
ofek
4y ago
This is also an interesting writeup by Valve: https://developer.valvesoftware.com/wiki/Latency_Compensatin...
76.
▲
Show HN: Kubernetes driver for mounting Google Cloud Storage buckets
(ofek.dev)
1 points
by
ofek
4y ago
|
0 comments
77.
▲
by
ofek
4y ago
Quick update: Hatch will likely be adopted by PyPA in the next week - https://mail.python.org/archives/list/pypa-committers@python... - https://mail.python.org/archives/list/pypa-committe
78.
▲
by
ofek
4y ago
Thanks for the kind words!
79.
▲
by
ofek
4y ago
https://peps.python.org/pep-0643/ will help the situation eventually
80.
▲
by
ofek
4y ago
Hatch is the CLI, Hatchling is the minimalist build backend
81.
▲
by
ofek
4y ago
> How does hatch compare to poetry? Poetry is mainly used for managing an _application_ and its dependencies whereas Hatch is more agnostic to the project type and offers plugin-based functionality for the entire workflow (versioning, to
82.
▲
Show HN: Hatch 1.0.0 – Modern, extensible Python project management
(github.com)
69 points
by
ofek
4y ago
|
44 comments
83.
▲
by
ofek
5y ago
For those desiring a GUI interface around VapourSynth and other advanced A/V processing tools, I strongly recommend StaxRip: https://github.com/staxrip/staxrip
84.
▲
by
ofek
5y ago
Pretty neat! I wrote and now co-maintain a library that has similar ease-of-use for Bitcoin: https://github.com/ofek/bit Even fewer LoC :)
85.
▲
by
ofek
6y ago
Well when it becomes production-ready, feel free to open a PR or issue to https://github.com/ofek/csi-gcs I'd prefer to use a memory-safe version :)
86.
▲
by
ofek
6y ago
Is your rewrite available?
87.
▲
by
ofek
7y ago
Good read! This sounds similar to the work I did [1] on the Datadog Agent, especially regarding the concept of each resource having its own circuit breaker. My implementation is a bit different though, instead based on exponential decay lik
88.
▲
Show HN: Kubernetes CSI Driver for Google Cloud Storage
(github.com)
3 points
by
ofek
7y ago
|
1 comments
89.
▲
Kubernetes CSI Driver for Google Cloud Storage
(github.com)
5 points
by
ofek
7y ago
|
0 comments
90.
▲
by
ofek
7y ago
It used to be a slightly modified fork of FFmpeg/libav. Is that no longer the case?
More ›