No Branch/Tag Specified
main
renovate/github.com-charmbracelet-lipgloss-2.x
renovate/github.com-charmbracelet-bubbletea-2.x
renovate/otel-weaver-0.x
renovate/tonistiigi-xx-1.x
renovate/alpine-3.x
renovate/github.com-charmbracelet-log-2.x
chore-deps
fix/492
fix/deps
fix/613
0.13.0-beta
0.13.0-rc2-beta
0.13.0-rc1-beta
0.12.0-beta
0.11.0-beta
0.10.1-beta
0.10.0-beta
0.10.0-rc2-beta
0.10.0-rc1-beta
0.9.0-beta
0.8.1-beta
0.8.0-beta
0.8.0-rc2-beta
0.8.0-rc1-beta
0.7.0-beta
0.7.0-rc3-beta
0.7.0-rc2-beta
0.6.0-beta
0.5.1-beta
0.5.0-alpha
0.4.1-alpha
0.4.0-alpha
0.4.0-alpha-rc8
0.4.0-alpha-rc7
0.4.0-alpha-rc6
0.4.0-alpha-rc5
0.4.0-alpha-rc4
0.4.0-alpha-rc3
0.4.0-alpha-rc2
0.4.0-alpha-rc1
0.3.1-alpha-rc2
0.3.1-alpha-rc1
0.3.1-rc1
0.3.0-alpha
0.2.2-alpha
0.2.1-alpha
0.2.0-alpha
0.1.8-alpha
0.1.7-alpha
0.1.6-alpha
0.1.5-alpha
0.1.4-alpha
0.1.3-alpha
0.1.2-alpha
0.1.1-alpha
0.1.0-alpha
10.0.5
10.0.3
10.0.2
10.0.1
10.0.0
9.0.0
8.0.1
8.0.0
0.7.4
0.7.3
0.7.2
0.7.1
0.7.0
checkout
0.6.0
0.5.0
0.4.1
0.4.0
0.3.1
0.3.0
0.2.0
0.1.2
0.1.1
0.1.0
Labels
Clear labels
bug
build
ci/cd
critical fix
design
documentation
duplicate
easy-first-issue
enhancement
help wanted
i10n
i18n
installer
invalid
question
release
release-candidate
security
tech-debt
test
wontfix
Something is not working
go build related issues
Building things with CI/CD
https://docs.coopcloud.tech/federation/resolutions/passed/010/
UI/UX
Documenting all the things
This issue or pull request already exists
Something for new people to get stuck into. We hope it's easy!
New feature
Need some help
Everything to do with localisation
Everything to do with internationalisation
Everything to do with the install script.
Something is wrong
More information is needed
Release management
Related to the new release candidate
Security related
Unit/integration testing
This won't be fixed
No Label
bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Abra "next"
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (decentral1se)
dede
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2
joe-irving
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/abra#875
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
while running
abra app logsfor a monitoring-ng recipe, i found that logs lines seem to be out of order. i can see lines from 2026-06-28, then 2026-06-29, then 2026-06-28 again. i thought the two containers may have different timezones, but runningdateon them show they are sharing the same time.docker service logs -fdoesn't seem to have this problem.not sure where the characters at the start of each line are coming from
The
�2026-06-28T21:35:06.626178948Z ts=2026-06-28T21:35:06.625889672Zis usually coming from the fact your docker daemon is hooked intosystemd? However, I think we also configure this by default inabra:Timestamps: truecould be the issue? I can't remember where they're coming from either 🙃As far as I remember, the
abracode just calls "show me your logs" in parallel and they all throw their logs to stdout at the same time. So everything can arrive in a weird order. I thought that was also thedocker logsbehaviour.this isn't a systemd server, but yeah docker is configured to send logs to syslog. these are two different services so i had to run two
docker service logs. the issue is that they are out of order within the same service, you can see alloy starting and then stopping, when the order was stop and then start.Ah, I see. So, we need to sort the output by timestamp on a per-service level 🤔 I guess a dip back into the source of how
docker service logsworks might be warranted. I had tried also wanted to have a kind of "mini-ui" for being able to flick between logs of each service but I never got around to it... thanks for the report!new logs arrive correctly, with the occasional message from another dimension (!):