Intent to remove: _raw.log artifacts from test tasks March 31, 2023

[Joel Maher]

Some discussions in various channels have prompted a question about why do we have *_raw.log artifacts.  These are for the most part duplicates of the live_backlog.log but parsed up into a .json format.  It is a lot of space and there is no way to know if there is a consumer of these files.

In the past we used this for ActiveData, as it stands I am not aware of anything that uses these.  I would like to remove support for these and stop generating them.

Please reply to this thread if you are using these and for what purpose (so we could document this).

[Andrew Sutherland]

On 3/10/23 11:11 AM, Joel Maher wrote:
> Please reply to this thread if you are using these and for what
> purpose (so we could document this).

I've used the logs in the past to deal with misleading timestamps for
the "buffered messages" that the mochitest test frameworks output which
makes the log output very misleading.  I filed
https://bugzilla.mozilla.org/show_bug.cgi?id=1607255 on that. This use
case probably doesn't justify keeping the JSON structured logs around,
though.

Andrew

[Randell Jesup]

Mozilla intends to turn on WebTransport support by default around March 14th, 2023

Summary:
Support for the W3C standards-track WebTransport specification, including Datagrams.   This allows more options for direct performant data exchange between a browser and servers than WebSockets with multiple streams on a single HTTP3 connection, as well as support for unreliable datagrams and other features.

Bug:  Bug 1709355
Bug to turn on by default: Bug 1818754

Specification: https://w3c.github.io/webtransport/
Standards Body: WebTransport Working Group

GitHub repository: https://github.com/w3c/webtransport

Issue Tracker: https://github.com/w3c/webtransport/issues

Platform coverage: All platforms
Preference: network.webtransport.enabled, network.webtransport.datagrams.enabled
Other browsers:
    Blink: Shipping since Chrome 97
    WebKit: No public signals.   People from Apple have been active in the spec discussions. https://github.com/WebKit/standards-positions/issues/18
web-platform-tests: https://wpt.fyi/results/webtransport?label=master&label=experimental&aligned&view=subtest&q=webtransport

[Tom Ritter]

This is kind of a general question about HTTP/3, but what is the
browser behavior when you have different types of proxies set that
don't support UDP?

-tom

> --
> You received this message because you are subscribed to the Google Groups "dev-pl...@mozilla.org" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to dev-platform...@mozilla.org.
> To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/fe76d1e4-cd4c-be11-99d2-6a58550b39dd%40mozilla.com.

[Kershaw Jang]

Please see the code here,  we do not use HTTP/3 for any type of proxy currently.

Regards,

Kershaw

To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CADua4_tYEhwnom2xqTzE7uNhHcgQ5WjdQ2bRggQaN%2BdDbFgjoA%40mail.gmail.com.