Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nyrkiö #1581

Merged
merged 2 commits into from
Feb 27, 2024
Merged

nyrkiö #1581

merged 2 commits into from
Feb 27, 2024

Conversation

matklad
Copy link
Member

@matklad matklad commented Feb 21, 2024

https://nyrk.io/ is a cloud CI benchmark tracking service.

It is very similar to what devhub is doing, except that it actually is a
real project, and not just me copy-pasting JavaScript from
https://deno.com/benchmarks.

Otherwise, it is very similar --- their data model is isomorphic to what
we already use.

In this PR, we duplicate data to both devhubdb and nyrk. I think we'll
continue in this mode for some time, but I can see us switching to nyrk
100% in the future.

In a follow up, I do want to switch to nyrk-shaped json for devhubdb as
well, as I like their version more (esp grouping attributes separately
from the timestamp, which is the primary key), but I don't want to
change stuff on our end right away.

As nyrk is a 3rd party service, I don't fail CI job if we fail to
upload.

One day we should go and just add proper quoting support, where "
interpolates and ' doesn't, but I am not ready to do that just yet.

Maybe one day `std.shlex` becomes a thing even!
@matklad matklad changed the title Matklad/nyrkiö nyrkiö Feb 21, 2024
https://nyrk.io is a cloud CI benchmark tracking service.

It is very similar to what devhub is doing, except that it actually is a
real project, and not just me copy-pasting JavaScript from
https://deno.com/benchmarks.

Otherwise, it is very similar --- their data model is isomorphic to what
we already use.

In this PR, we duplicate data to both devhubdb and nyrk. I think we'll
continue in this mode for some time, but I can see us switching to nyrk
100% in the future.

In a follow up, I do want to switch to nyrk-shaped json for devhubdb as
well, as I like their version more (esp grouping attributes _separately_
from the timestamp, which is the primary key), but I don't want to
change stuff on our end right away.

As nyrk is a 3rd party service, I don't fail CI job if we fail to
upload.
fn upload_nyrkio(shell: *Shell, run: NyrkioRun) !void {
const token = try shell.env_get("NYRKIO_TOKEN");
const payload = try std.json.stringifyAlloc(shell.arena.allocator(), [_]NyrkioRun{run}, .{});
try shell.exec(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No love for std.http.Client? 😉

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wait, we already have http.Client? Didn't realize that, thought that's the next release. But, given ziglang/zig#18955, I'd probably let it bake a bit more until we depend on it

@matklad matklad added this pull request to the merge queue Feb 27, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Feb 27, 2024
@matklad matklad added this pull request to the merge queue Feb 27, 2024
@matklad
Copy link
Member Author

matklad commented Feb 27, 2024

Failure feels like something's wrong with actions/checkpout?

Merged via the queue into main with commit 509564c Feb 27, 2024
25 checks passed
@matklad matklad deleted the matklad/nyrkiö branch February 27, 2024 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants