tracing

I've seen this one failing sporadically:

=== RUN   TestHotReloadUIConfigTempFile
    static_handler_test.go:279: 
        	Error Trace:	static_handler_test.go:279
        	Error:      	"" does not contain "About a new Jaeger"
        	Test:       	TestHotReloadUIConfigTempFile
        	Messages:   	[{Entry:{Level:info Time:2022-05-25 20:44:07.707232055 +0000 UTC m=+2.677106569 LoggerNam

Bug description

When the backend API responds with 500 error code then the loader on charts section loads infinitely

Expected behavior

Charts should show No Data like in trace table.

Version information

Seems we have some language features not fully documented (like bitshift operators in #1322).

Would be good to go through language grammar and make sure everything is in the reference guide.

Sometimes it is useful to know where a function was called from. We currently don't display this information.

Feature Request

tokio-rs/valuable#88 came because I realized that tracing-subscriber, specifically the json formatter, missed some of the logged events.

Crates

tracing-subscriber

Motivation

Logs, and traces, carry information. It is good to know that some of it was lost. In my case what failed to serialize was the error which caused abnormal

$ make ASAN=1
$ cd tests
$ ./runtest.py -vdp -O0 220
Start 1 tests with 1 worker
Test case                 pg
------------------------: O0
build command: gcc -o t-abc -fno-inline -fno-builtin -fno-ipa-cp -fno-omit-frame-pointer -D_FORTIFY_SOURCE=0  -pg -O0  s-abc.c
test command: /home/honggyu/work/uftrace/git/uftrace/uftrace live --no-pager --no-event --libmcount-path=/home/honggyu/wor

Out of scope during Twitch Series but a nice to have feature that can be implemented

Booking is not currently using Subscription, and it could be done by leveraging parametrized Subscriptions.

Tasks to complete in order to implement this feature:

• Modify onUpdateBooking Subscription to include customer and status
• Implement onUpdateBooking subscription in the Fron

The recently added flags in timescale/promscale#578 are yet to be updated in prom-migrator's readme which can be found here.

It seems to me that UTC is selected for on the wire representation of time as well as in the database (jaegertracing/jaeger#712), which sort of makes sense, at least with a somewhat naive handling of timezones. However, I think that the Jaeger UI should support displaying times in the timezone local to the user, i.e. of the browser as to reduce the mental load when viewing