tracing

Bug description

There is no fallback component when there is any unhandled Error in the React component

Please describe.
If this affects the front-end, screenshots would be of great help.

Expected behav

Is your feature request related to a problem? Please describe.

Useful for networking tracing to convert from network order to host order.

Describe the solution you'd like

int[8|16|32|64] bswap(int[8|16|32|64])

We can make bswap() infer the integer width and return the appropriate integer. Previous discussi

We can reproduce the memory leak problem as follows.

$ make clean
$ make ASAN=1

$ ./uftrace record -L. --force uptime
 19:40:08 up 13 days,  1:55,  2 users,  load average: 3.61, 1.21, 0.43

=================================================================
==1188721==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 888 byte(s) in 1 object(s) allocated from:
    #0 0xffff

Feature Request

Crates

• tracing-core

Motivation

The Collect trait currently has several methods with default implementations that return an Option or some other "empty" or "default" type. In many cases, this isn't because it makes sense for those methods to be optional, but because they were added after v0.1.0 was released and making them mandatory would have been a

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

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