SDK / exoplayer

In favor of setting the cause in the constructor, which allows
some code simplifications.

PiperOrigin-RevId: 387062636

PiperOrigin-RevId: 386970718

#minor-release

PiperOrigin-RevId: 386966219

The inference is used when nesting DataSourceExceptions. It is removed because
nesting does not add additional value in surfacing the exceptions, and it is
better to assign an error code at the throw site (in the "leaf" or the bottom
most data source).

PiperOrigin-RevId: 386919118

Doclava outputs an error when handling the javadoc where the `@see` clause is an anchor but also has other content.

PiperOrigin-RevId: 386875722

Issues: #771 and #7654
PiperOrigin-RevId: 386850707

* @Flags is not a TYPE_USE annotation, so should appear before any modifiers and after Javadocs.
  (see go/java-style#s4.8.5-annotations)

This CL looks good? Just LGTM and Approve it!
This CL doesn’t look good? This is what you can do:
* Suggest a fix on the CL (go/how-to-suggest-fix).
* Revert this CL, by replying "REVERT: <provide reason>"
* File a bug under go/error-prone-bug for category ErrorProneStyle if the change looks generally problematic.
* Revert this CL and not get a CL that cleans up these paths in the future by
replying "BLOCKLIST: <provide reason>". This is not reversible! We recommend to
opt out the respective paths in your CL Robot configuration instead:
go/clrobot-opt-out.

This CL was generated by CL Robot - a tool that cleans up code findings
(go/clrobot). The affected code paths have been enabled for CL Robot in //depot/google3/java/com/google/android/libraries/media/METADATA which is reachable following include_presubmits from //depot/google3/third_party/java_src/android_libs/media/METADATA.
Anything wrong with the signup? File a bug at go/clrobot-bug.

#codehealth

PiperOrigin-RevId: 386849198

PiperOrigin-RevId: 386841818

PiperOrigin-RevId: 386836747

PiperOrigin-RevId: 386521255

The reason this was not an IO error code is that before other
IOExceptions were classified, this catch would grab non-IO error
codes, like ParserException. Now that we are getting closer to
the final state, we can assume IOExceptions are ok to classify
as IO error codes (unlike, for example, ParserExceptions or
DrmSessionExceptions).

PiperOrigin-RevId: 386496752

PiperOrigin-RevId: 386453305

PiperOrigin-RevId: 386442542

*** Original commit ***

Migrate /-as-division to math.div

If google3 is the source-of-truth for this third_party code (or if this is legacy code that is no longer synced with an external source), just LGTM this CL and Rosie will submit it. If not, you should patch the upstream source of these files, since we will be disabling support for /-as-division in google3 before support is formally removed from the language.

See go/lsc-slash-as-division-deprecation.

Tested:
    TAP found no affected targets. No targets were b...

***

PiperOrigin-RevId: 386432441

PiperOrigin-RevId: 386428758

PiperOrigin-RevId: 386401066

PiperOrigin-RevId: 386232697

PiperOrigin-RevId: 386227630

Using all lower case RTSP headers is perfectly valid, as the spec mandates case
insensitively. However, some RTSP servers do not implement the RTSP spec
closely and does not recognize the lower case headers. This change aims
at using the header names as defined in the RTSP spec to maximize compatibility.

Issue: #9182
PiperOrigin-RevId: 386224566

PiperOrigin-RevId: 386207381

PiperOrigin-RevId: 386206960

PiperOrigin-RevId: 386194874

PiperOrigin-RevId: 386194496

PiperOrigin-RevId: 386185285

PiperOrigin-RevId: 386177945

r2.14.2

#minor-release

PiperOrigin-RevId: 386048024

#minor-release

PiperOrigin-RevId: 386048024

This also deletes several files that should have been deleted as part
of the 2.14.0 release - both javadoc for classes that were removed in
that release and all the *-frame.html files that no longer seem
to be produced by the javadoc compiler. Also a jquery file
(jquery-1.10.2.js) that's no longer produced by the compiler.

#minor-release

PiperOrigin-RevId: 385997294

PiperOrigin-RevId: 385996618

PiperOrigin-RevId: 385995740

This URL no longer resolves.

#minor-release

Issue: #9205
PiperOrigin-RevId: 385772688

PiperOrigin-RevId: 385736588

This also deletes several files that should have been deleted as part
of the 2.14.0 release - both javadoc for classes that were removed in
that release and all the *-frame.html files that no longer seem
to be produced by the javadoc compiler. Also a jquery file
(jquery-1.10.2.js) that's no longer produced by the compiler.

#minor-release

PiperOrigin-RevId: 385997294

#minor-release

PiperOrigin-RevId: 385996618

PiperOrigin-RevId: 385995740

FileDataSourceException subclasses DataSourceException and can be handled
in the same fashion.

PiperOrigin-RevId: 385983103

In some DataSources, it is not easy to assign an error code at the throw site.
For example, CronetDataSource.readInternal() throws SocketTimeoutException
on L1033, and is caught at L754 as IOException and is thrown.

We need the logic to assign error code for the actual type of the error cause.
While we can certainly do in individual DataSources, IMO there's value in
making this logic generic at a higher level (like what is in this CL).

The catch and translation logic is borrowed from EPII:L646.

PiperOrigin-RevId: 385789629

PiperOrigin-RevId: 385783671