fix(proto)!: Change execution API to use primitive RollupId#1291
fix(proto)!: Change execution API to use primitive RollupId#1291ethanoroshiba merged 15 commits intomainfrom
Conversation
| repo: ghcr.io/astriaorg/astria-geth | ||
| tag: 0.13.0 | ||
| devTag: latest | ||
| devTag: pr-38 |
There was a problem hiding this comment.
Just double-checking -- is this tag for all of development intentional?
There was a problem hiding this comment.
Was intentional since this PR is dependent on astria-geth #38. @joroshiba suggested waiting until this PR merges, updating geth PR with latest protos and merging, then making a monorepo cleanup PR to update devTag to latest.
There was a problem hiding this comment.
Yeah, because we have proto changes here that needs geth update, it gets a little weird here:
- get this pr submitted which pushes prod proto changes
- update pr-38 of geth to utilize new main proto libraries, update and submit.
- update mono repo back to latest.
A bit of chicken/egg problem here. My preference is to keep astria-geth main from relying on non-main protos. We should wait to submit PR here until pr-38 is reviewed and approved though so we don't end up out of sync.
Co-authored-by: Jordan Oroshiba <jordan@astria.org>
Co-authored-by: Jordan Oroshiba <jordan@astria.org>
There was a problem hiding this comment.
Looks great. Nothing to add to @joroshiba's review. Just a small nit in an error message.
| ); | ||
| Self::Raw { | ||
| rollup_id: Bytes::copy_from_slice(rollup_id.as_ref()), | ||
| rollup_id: Some(rollup_id.to_raw()), |
There was a problem hiding this comment.
Note that there is also into_raw. They do the same thing here, so it doesn't matter. But sometimes taking owernship allows some optimizations (like avoiding another allocation... if one remembers to implement it that way).
There was a problem hiding this comment.
Got it! So for future reference if something is not a shared object then into_raw() may be a better choice?
There was a problem hiding this comment.
I'll note that this is within a to_raw function. I have generally tried to keep the to_raw calling other to_raw and vice versa.
Co-authored-by: Richard Janis Goldschmidt <github@aberrat.io>
## Summary PR in tandem with astriaorg/astria#1291. Adjusts `GetGenesisInfo` to utilize primitive type `RollupId` instead of `bytes`. ## Changes - Updated grpc and protobuf SDKs. - Changed `GetGenesisInfo` to use primitive `RollupId`. - Updated sever tests to run correctly with `RollupId`.
## Summary Update EVM-Rollup Geth `devTag` after #1291 and astria-geth [#38](astriaorg/astria-geth#38). ## Background #1291 relied on astria-geth PR [#38](astriaorg/astria-geth#38) for `evm-rollup` chart. Now that both PRs have been merged, the `devTag` can be updated to `latest`. ## Changes - Updated geth `devTag` to `latest` in `evm-rollup` `values.yaml`. - Updated `evm-rollup` and `evm-stack` versions. ## Testing Passing e2e tests.
* main: release: cut bridge withdrawer release (#1303) release: version cuts for dusk-9 (#1299) chore(core): remove ed25519_consensus from public API (#1277) chore: remove spurious entry in gitignore (#1276) chore(chart): Update EVM-Rollup Geth devTag (#1300) fix(proto)!: Change execution API to use primitive RollupId (#1291) refactor(core, proto)!: define bridge memos in proto (#1285) chore(sequencer-relayer)!: minimize resubmissions to Celestia (#1234)
Summary
Changed execution API
rollup_idto use primitiveRollupIdinstead of bytes.Background
RollupIdis defined in primitives protobuf specs, butastria.execution.v1alpha2.GenesisInfo.rollup_idwas still using type bytes instead of the primitive type.Changes
rollup_idto be of typeRollupId.RollupIdinstead of bytes.evm-stackandevm-rollupversions.Testing
With changes in
astria-geth, passes smoke-test.Breaking Changelist
astria-gethchanges to function properly.devTagtolatestonce geth PR is merged.Related Issues
With
astria-geth#38, closes #1287