| commit | 308ed671fba4ddb5c56cf0f7f74f828f7c1c1b85 | [log] [tgz] |
|---|---|---|
| author | shahan <shahan@google.com> | Thu Feb 03 10:22:10 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Feb 03 10:23:38 2022 -0800 |
| tree | 183668f1b7429b5826ffbeafdcd4e308491419f0 | |
| parent | c5a1f8eb2e970c018c530e14c50918bee58618f8 [diff] |
Automated rollback of commit 382b187d4df664e555608c895716172d96e092c5. *** Reason for rollback *** Roll forward with fix. Added a unit test. The underlying culprit is that unsafe offsets unstable between JVMs. Ordering serialization by offsets in the previous CL caused completely broken non-deterministic serialization. *** Original change description *** Automated rollback of commit 9998c6361d3d7c22184ea07e363f38e88a345701. *** Reason for rollback *** Suspected cause of b/217386541 *** Original change description *** Minor DynamicCodec simplifications. Serialization order is now based on field offset instead of field name. It's possible to create dependencies on serialization order, but it seems to be accidental. PiperOrigin-RevId: 426179122
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
