Skip to content

Conversation

@bharath-123
Copy link
Contributor

Summary

PR #1707 involved renaming protos from optimistic_block to optimistic which caused some unused generated optimisticblock protos to be merged. This PR removes unused optimistic block proto generated files and updates the mod.rs to use the optimistic generated proto files.

Changes

  • Remove crates/astria-core/src/generated/astria.sequencerblock.optimisticblock.v1alpha1.rs and crates/astria-core/src/generated/astria.sequencerblock.optimisticblock.v1alpha1.serde.rs
  • Update crates/astria-core/src/generated/mod.rs to use optimistic instead of optimisticblock

Testing

Codebase compiles and all the tests run

Related Issues

closes #1823

@bharath-123 bharath-123 requested a review from a team as a code owner November 19, 2024 12:19
@github-actions github-actions bot added the proto pertaining to the Astria Protobuf spec label Nov 19, 2024
@SuperFluffy
Copy link
Contributor

Closing this PR in favor of #1825 which is a more general fix.

@bharath-123 bharath-123 deleted the bharath/remove-optimisticblock-protos branch November 20, 2024 06:00
github-merge-queue bot pushed a commit that referenced this pull request Dec 5, 2024
…c match (#1825)

## Summary
Deletes and regenerates all code in `astria-core/src/generated`. Fixes
bad imports by nesting generated Astria APIs under a new `astria`
module. Fixes badly named modules.

## Background
#1236 noticed that some protobuf
files were skipped during code generation because of a
`tonic_build::Builder::extern_path` statement. This showed up again when
reworking the protobuf compilation tool to first clear the target
directory for storing the generated rust files, where now an `include!`
statement in `astria_core::generated` failed because the file was not in
fact generated. This was not detected because the file was still
committed to the repository at an earlier point.

#1707 then added new generated
code under a wrongly named `optimistic_block` module, which should have
been named `optimistic` to be in line with its protobuf package
counterpart.

The present change is primarily to the `tools/protobuf-compiler` binary,
which first purges the output directory (minus the handwritten `mod.rs`)
before generating new code.

## Changes
- Update `tools/protobuf-compiler` to clear `astria-core/src/generated`
prior to repopulating it from `proto/`
- Remove the module `sequencerblock::optimisticblock`
- Add module `sequencerblock::optimistic`
- Update all services that import Astria APIs from
`astria_core::generated` to `astria_core::generated::astria`.

## Testing
This is just code organization. Import paths were updated, code still
compiles and tests pass.

## Changelogs
Changelogs updated.

## Breaking Changelist
- This is a breaking change for all consumers of `astria_core` that now
need to import many items from `astria_core::generated::astria` that
were directly under `astria_core::generated` before.

## Override Freeze
This code touches services by changing their imports
(`astria_core::generated -> astria_core::generated::astria`) but does
change any implementation details.

## Related Issues
Fixes and amends #1707.
Supersedes #1824
Closes #1823
sgranfield4403-3 added a commit to sgranfield4403-3/astria that referenced this pull request Oct 2, 2025
…c match (#1825)

## Summary
Deletes and regenerates all code in `astria-core/src/generated`. Fixes
bad imports by nesting generated Astria APIs under a new `astria`
module. Fixes badly named modules.

## Background
astriaorg/astria#1236 noticed that some protobuf
files were skipped during code generation because of a
`tonic_build::Builder::extern_path` statement. This showed up again when
reworking the protobuf compilation tool to first clear the target
directory for storing the generated rust files, where now an `include!`
statement in `astria_core::generated` failed because the file was not in
fact generated. This was not detected because the file was still
committed to the repository at an earlier point.

astriaorg/astria#1707 then added new generated
code under a wrongly named `optimistic_block` module, which should have
been named `optimistic` to be in line with its protobuf package
counterpart.

The present change is primarily to the `tools/protobuf-compiler` binary,
which first purges the output directory (minus the handwritten `mod.rs`)
before generating new code.

## Changes
- Update `tools/protobuf-compiler` to clear `astria-core/src/generated`
prior to repopulating it from `proto/`
- Remove the module `sequencerblock::optimisticblock`
- Add module `sequencerblock::optimistic`
- Update all services that import Astria APIs from
`astria_core::generated` to `astria_core::generated::astria`.

## Testing
This is just code organization. Import paths were updated, code still
compiles and tests pass.

## Changelogs
Changelogs updated.

## Breaking Changelist
- This is a breaking change for all consumers of `astria_core` that now
need to import many items from `astria_core::generated::astria` that
were directly under `astria_core::generated` before.

## Override Freeze
This code touches services by changing their imports
(`astria_core::generated -> astria_core::generated::astria`) but does
change any implementation details.

## Related Issues
Fixes and amends astriaorg/astria#1707.
Supersedes astriaorg/astria#1824
Closes astriaorg/astria#1823
AngieD101 added a commit to AngieD101/astria that referenced this pull request Oct 10, 2025
…c match (#1825)

## Summary
Deletes and regenerates all code in `astria-core/src/generated`. Fixes
bad imports by nesting generated Astria APIs under a new `astria`
module. Fixes badly named modules.

## Background
astriaorg/astria#1236 noticed that some protobuf
files were skipped during code generation because of a
`tonic_build::Builder::extern_path` statement. This showed up again when
reworking the protobuf compilation tool to first clear the target
directory for storing the generated rust files, where now an `include!`
statement in `astria_core::generated` failed because the file was not in
fact generated. This was not detected because the file was still
committed to the repository at an earlier point.

astriaorg/astria#1707 then added new generated
code under a wrongly named `optimistic_block` module, which should have
been named `optimistic` to be in line with its protobuf package
counterpart.

The present change is primarily to the `tools/protobuf-compiler` binary,
which first purges the output directory (minus the handwritten `mod.rs`)
before generating new code.

## Changes
- Update `tools/protobuf-compiler` to clear `astria-core/src/generated`
prior to repopulating it from `proto/`
- Remove the module `sequencerblock::optimisticblock`
- Add module `sequencerblock::optimistic`
- Update all services that import Astria APIs from
`astria_core::generated` to `astria_core::generated::astria`.

## Testing
This is just code organization. Import paths were updated, code still
compiles and tests pass.

## Changelogs
Changelogs updated.

## Breaking Changelist
- This is a breaking change for all consumers of `astria_core` that now
need to import many items from `astria_core::generated::astria` that
were directly under `astria_core::generated` before.

## Override Freeze
This code touches services by changing their imports
(`astria_core::generated -> astria_core::generated::astria`) but does
change any implementation details.

## Related Issues
Fixes and amends astriaorg/astria#1707.
Supersedes astriaorg/astria#1824
Closes astriaorg/astria#1823
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

proto pertaining to the Astria Protobuf spec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

proto: remove optimistic block generated proto files

2 participants