This website requires JavaScript.
Explore
Help
Sign In
maemachinebroke
/
hakurei
Watch
1
Star
0
Fork
0
You've already forked hakurei
forked from
security/hakurei
Code
Pull Requests
Activity
Files
69b1131d6622108f37c85014035f71cf4f2986e5
hakurei
/
internal
/
pipewire
History
Ophestra
69b1131d66
internal/pipewire: use type name in error strings
...
This provides more useful messages for protocol errors. Signed-off-by: Ophestra <
cat@gensokyo.uk
>
2025-12-04 02:29:27 +09:00
..
testdata
internal/pipewire: store sample iovec continuously
2025-11-28 00:35:10 +09:00
client_test.go
internal/pipewire: add json struct tags
2025-11-28 01:33:32 +09:00
client.go
internal/pipewire: collect non-protocol errors
2025-12-03 01:35:43 +09:00
core_test.go
internal/pipewire: use type name in error strings
2025-12-04 02:29:27 +09:00
core.go
internal/pipewire: collect non-protocol errors
2025-12-03 01:35:43 +09:00
header_test.go
internal/pipewire: implement Core::Error
2025-11-30 01:39:39 +09:00
header.go
internal/pipewire: implement client context
2025-12-02 06:03:21 +09:00
pipewire_test.go
internal/pipewire: relocate constants
2025-12-03 03:52:17 +09:00
pipewire.go
internal/pipewire: relocate constants
2025-12-03 03:52:17 +09:00
pod_test.go
internal/pipewire: benchmarks against Gob and JSON
2025-11-30 12:13:46 +09:00
pod.go
internal/pipewire: use type name in error strings
2025-12-04 02:29:27 +09:00
securitycontext_test.go
internal/pipewire: implement SecurityContext::Create
2025-11-29 16:46:39 +09:00
securitycontext.go
internal/pipewire: collect non-protocol errors
2025-12-03 01:35:43 +09:00
spa_test.go
internal/pipewire: use type name in error strings
2025-12-04 02:29:27 +09:00
spa.go
internal/pipewire: use type name in error strings
2025-12-04 02:29:27 +09:00