Leon Wilzer leon
  • I can use Markdown

  • Joined on 2022-03-06
leon commented on issue KomuSolutions/igot99issues#16 2024-02-16 17:42:06 +01:00
Drone CI-Containers on RL9 Arm Runner cannot resolve DNS

Ich hab den Artikel mal genau gelesen, das default network gilt für den Adapter netavark, der aber nur bei rootful containern default ist. Für rootless container ist slirp4netns default.…

leon commented on issue KomuSolutions/igot99issues#16 2024-02-16 17:28:57 +01:00
Drone CI-Containers on RL9 Arm Runner cannot resolve DNS

Ansonsten ist das hier meine Haupttheorie:

  • Podman hat per Default keine dns resolution
  • Man kann es aber aktivieren: https://github.com/containers/podman/blob/main/docs/tutorials/basic_network…
leon commented on issue KomuSolutions/igot99issues#16 2024-02-16 17:27:09 +01:00
Drone CI-Containers on RL9 Arm Runner cannot resolve DNS

Ich tendiere jedoch auch gegen Podman, da sich das problem ja sogar innerhalb des Containers fixen laesst.

leon commented on issue KomuSolutions/igot99issues#16 2024-02-16 17:26:22 +01:00
Drone CI-Containers on RL9 Arm Runner cannot resolve DNS

Ja, ich gehe auch von Podman aus, aber es scheint ja eine Kombination zwischen Podman's DNS und wie Drone den Container startet zu sein, schließlich sind keinerlei andere Probleme dieser Art…

leon commented on issue KomuSolutions/igot99issues#16 2024-02-16 17:19:50 +01:00
Drone CI-Containers on RL9 Arm Runner cannot resolve DNS

Ja, also generell, ist dir das Problem schonmal in irgendeiner anderen Art, die nicht mit Drone zu tun hat, aufgefallen? Weil mir noch nicht und ich würde gerne rausfinden, in wie fern RL9…

leon commented on issue KomuSolutions/igot99issues#16 2024-02-16 16:01:04 +01:00
Drone CI-Containers on RL9 Arm Runner cannot resolve DNS

Wie meinst du das genau:

  • Mit einer anderen CI-Solution, also gitea actions?
  • Mit dem Rust Docker image allgemein, unnabhaengig von jeglicher CI?
leon pushed to Logging at KomuSolutions/WANessa 2024-02-15 22:41:31 +01:00
dd5bfff7d2 replaced log_message with new log!
927a8d6d05 rustdoc adjustments
Compare 2 commits »
leon commented on pull request KomuSolutions/WANessa#26 2024-02-15 21:57:22 +01:00
Logging

See a787dd93e5

leon commented on pull request KomuSolutions/WANessa#26 2024-02-15 21:56:27 +01:00
Logging

See a787dd93e5

leon pushed to Logging at KomuSolutions/WANessa 2024-02-15 21:55:24 +01:00
502d3a7b2d Merge branch 'Logging' of git.libre.moe:KomuSolutions/WANessa into Logging
ba0a1fc641 migrated to reworked config crate
cb024af91a some syntactic sugar for Option enum
a787dd93e5 Split config crate into multiple modules
Compare 4 commits »
leon commented on issue KomuSolutions/WANessa#28 2024-02-15 20:50:42 +01:00
CI (Re-)Consideration

Bonus Points:

  • variable(s) for rust-image(s)
    • automatically update variables according to the current rust version of the server. If not feasible, use the current rust version of the…
leon commented on pull request KomuSolutions/WANessa#26 2024-02-15 20:36:33 +01:00
Logging

While not a read lock, the Arc Type has this, which seems to be at odds with the whole immutability thing. https://doc.rust-lang.org/std/sync/struct.Arc.html#method.get_mut The docs don't seem to…

leon commented on pull request KomuSolutions/WANessa#26 2024-02-15 20:10:18 +01:00
Logging

While not a read lock, the Arc Type has this, which seems to be at odds with the whole immutability thing. https://doc.rust-lang.org/std/sync/struct.Arc.html#method.get_mut The docs don't seem to…

leon commented on pull request KomuSolutions/WANessa#26 2024-02-15 19:59:26 +01:00
Logging

The error in this case is the inability to report about warnings. This edge-case happens, when there is absolutely no way of informing the sysadmin of other errors, including CLI and E-Mail,…

leon commented on pull request KomuSolutions/WANessa#26 2024-02-15 19:12:33 +01:00
Logging

Seems sensible. It is also probably a good idea to split the config struct into multiple parts.

leon pushed to Logging at KomuSolutions/WANessa 2024-02-15 19:06:46 +01:00
a36a8a8b76 expanded macro to optionally accept &Config
leon commented on pull request KomuSolutions/WANessa#26 2024-02-15 18:43:28 +01:00
Logging

See 6e73c2a7b7

leon pushed to Logging at KomuSolutions/WANessa 2024-02-15 18:41:50 +01:00
6e73c2a7b7 added explicit ordinals; See #26
leon commented on pull request KomuSolutions/WANessa#26 2024-02-15 18:34:43 +01:00
Logging

logging/src/lib.rs:102 will panic if any code requests write-lock on config::CONFIG and then panics. Consider using Arc to ensure immutability and accessibility to the configuration from any thread at any time