mdebray/tvl-depot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
tvl-depot/users/Profpatsch/alacritty-change-color-scheme/package.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

21 lines
580 B
JSON
Raw Normal View History

feat(pkgs/Profpatsch/alacritty): init dark mode dbus daemon A simple dbus daemon that writes the alacritty config to `~/.config/alacritty/alacritty-colors-autogen.toml` on startup and whenever a change between dark/light mode is requested. Alacritty only implements an config file isync watcher, no SIGHUP handler or similar, so we have to actually write the config file lol. This is all a little glue-y, but idk, whatever. Further reading & inspo: https://github.com/alacritty/alacritty/issues/5999 https://www.christianfosli.com/posts/2024-on-colorscheme-changed/ https://github.com/christianfosli/on-colorscheme-changed Change-Id: Iac4eb9d85679dc87e28e57d68384645b3b91d08a Reviewed-on: https://cl.tvl.fyi/c/depot/+/12870 Tested-by: BuildkiteCI Reviewed-by: Profpatsch <mail@profpatsch.de>
2024-12-05 19:11:34 +01:00
{
"name": "alacritty-change-color-scheme",
"version": "1.0.0",
"main": "alacritty-change-color-scheme.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"bin": "alacritty-change-color-scheme.js",
"author": "",
"license": "ISC",
"description": "",
"dependencies": {
feat(users/Profpatsch): Implement initial otel-dbus proxy For simplicity’s sake this puts everything into the alacritty-change-color-scheme script for now. This implements a simple dbus-opentelemetry proxy adapter, which allows services to record otel traces without having to depend on the quite complex otel libraries. Instead, they just send their traces to the dbus tracing interface, and the service that binds against that interface forwards the spans to the OTLP collector. First you create a new Tracer for your service via the `TracerFactory` interface: ``` > busctl --user call \ de.profpatsch.otel.Tracer \ /de/profpatsch/otel/TracerFactory \ de.profpatsch.otel.TracerFactory CreateTracer \ s hello s "/de/profpatsch/otel/tracers/hello" ``` (this corresponds to setting up a tracer with properties in OTEL) Then, you can use the returned object path to call the `Tracer` interface proper: ``` < busctl --user call \ de.profpatsch.otel.Tracer \ /de/profpatsch/otel/tracers/hello \ de.profpatsch.otel.Tracer \ StartSpan \ s '{"spanId": "111", "name": "111"}' ``` This will create the spans. You can also set their timestamps on the sending side via `startTime`/`endTime`, but make sure it’s a hrtime tuple. Prefer batching multiple spans vie the `BatchSpans` call. Change-Id: Ie6cfdcb0dc3e2398316a2c1763bc72c1118168b0 Reviewed-on: https://cl.tvl.fyi/c/depot/+/12885 Tested-by: BuildkiteCI Reviewed-by: Profpatsch <mail@profpatsch.de> Reviewed-by: benjaminedwardwebb <benjaminedwardwebb@gmail.com>
2024-12-09 21:10:01 +01:00
"@opentelemetry/api": "^1.9.0",
"@opentelemetry/context-async-hooks": "^1.29.0",
"@opentelemetry/core": "^1.29.0",
"@opentelemetry/exporter-trace-otlp-http": "^0.56.0",
"@opentelemetry/sdk-trace-base": "^1.29.0",
feat(pkgs/Profpatsch/alacritty): init dark mode dbus daemon A simple dbus daemon that writes the alacritty config to `~/.config/alacritty/alacritty-colors-autogen.toml` on startup and whenever a change between dark/light mode is requested. Alacritty only implements an config file isync watcher, no SIGHUP handler or similar, so we have to actually write the config file lol. This is all a little glue-y, but idk, whatever. Further reading & inspo: https://github.com/alacritty/alacritty/issues/5999 https://www.christianfosli.com/posts/2024-on-colorscheme-changed/ https://github.com/christianfosli/on-colorscheme-changed Change-Id: Iac4eb9d85679dc87e28e57d68384645b3b91d08a Reviewed-on: https://cl.tvl.fyi/c/depot/+/12870 Tested-by: BuildkiteCI Reviewed-by: Profpatsch <mail@profpatsch.de>
2024-12-05 19:11:34 +01:00
"dbus-native": "^0.4.0"
}
}
Reference in a new issue Copy permalink