Sinner: resolvers and updating db read functions #1514
Conversation
WalkthroughThe changes primarily revolve around the shift from using Changes
TipsChat with CodeRabbit Bot (
|
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## feat/sinner #1514 +/- ##
=====================================================
- Coverage 50.83841% 49.62568% -1.21274%
=====================================================
Files 369 366 -3
Lines 25465 24578 -887
Branches 268 268
=====================================================
- Hits 12946 12197 -749
- Misses 11257 11311 +54
+ Partials 1262 1070 -192
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review Status
Actionable comments generated: 2
Configuration used: CodeRabbit UI
Files selected for processing (17)
- services/sinner/api/resolver_test.go (2} hunks)
- services/sinner/contracts/origin/parser.go (1} hunks)
- services/sinner/db/event.go (1} hunks)
- services/sinner/db/mocks/event_db.go (2} hunks)
- services/sinner/db/model/model.go (3} hunks)
- services/sinner/db/read_test.go (2} hunks)
- services/sinner/db/sql/base/read.go (3} hunks)
- services/sinner/graphql/client/client.go (8} hunks)
- services/sinner/graphql/client/queries/queries.graphql (2} hunks)
- services/sinner/graphql/server/graph/helper.go (2} hunks)
- services/sinner/graphql/server/graph/model/models_gen.go (2} hunks)
- services/sinner/graphql/server/graph/queries.resolvers.go (1} hunks)
- services/sinner/graphql/server/graph/resolver/server.go (41} hunks)
- services/sinner/graphql/server/graph/schema/queries.graphql (1} hunks)
- services/sinner/graphql/server/graph/schema/types.graphql (3} hunks)
- services/sinner/graphql/server/graph/types.resolvers.go (1} hunks)
- services/sinner/service/indexer.go (1} hunks)
Files not summarized due to errors (1)
- services/sinner/graphql/server/graph/resolver/server.go: Error: Message exceeds token limit
Files skipped from review due to trivial changes (4)
- services/sinner/contracts/origin/parser.go
- services/sinner/db/sql/base/read.go
- services/sinner/graphql/server/graph/helper.go
- services/sinner/service/indexer.go
Additional comments: 50
services/sinner/graphql/server/graph/schema/queries.graphql (4)
7-8: The
getOriginInfofunction signature has been updated to takemessageHashas a parameter instead oftxHashandchainID. Ensure that all calls to this function throughout the codebase have been updated to match the new signature. Also, verify that themessageHashis being correctly generated and passed to this function.10-12: The
getDestinationInfofunction signature has been updated in a similar manner togetOriginInfo. The same considerations apply here.14-17: The new
getOriginInfosfunction retrieves multipleOriginInforecords based ontxHashandchainID. Ensure that the function implementation correctly handles the retrieval of multiple records and that the returned data is correctly processed by the caller.19-22: The new
getDestinationInfosfunction retrieves multipleDestinationInforecords based ontxHashandchainID. The same considerations as forgetOriginInfosapply here.services/sinner/db/model/model.go (3)
67-67: The
TxHashfield is no longer a primary key in theOriginSentstruct. This change is consistent with the PR summary, which mentions thatMessageHashis now the primary key. Ensure that this change is reflected in all related database operations and queries.79-79: The
MessageHashfield is now a primary key in theOriginSentstruct. This change is consistent with the PR summary. Ensure that this change is reflected in all related database operations and queries.117-121: The
TxHashfield is no longer a primary key in theExecutedstruct, andMessageHashis now the primary key. This change is consistent with the PR summary. Ensure that this change is reflected in all related database operations and queries.services/sinner/graphql/client/queries/queries.graphql (4)
14-37: The
GetOriginInfoquery has been updated to takemessageHashas a parameter instead oftxHashandchainID. This change aligns with the PR's goal of refactoring the handling of transaction and message hashes. Ensure that all calls to this query throughout the codebase have been updated to match the new signature.39-40: The
GetOriginInfosquery has been introduced to retrieve multiple records based ontxHashandchainID. This is a new addition and does not replace any existing functionality. Ensure that this new query is used appropriately in the codebase.66-77: The
GetDestinationInfoquery has been updated to takemessageHashas a parameter instead oftxHashandchainID. This change aligns with the PR's goal of refactoring the handling of transaction and message hashes. Ensure that all calls to this query throughout the codebase have been updated to match the new signature.80-81: The
GetDestinationInfosquery has been introduced to retrieve multiple records based ontxHashandchainID. This is a new addition and does not replace any existing functionality. Ensure that this new query is used appropriately in the codebase.services/sinner/graphql/server/graph/schema/types.graphql (4)
11-13: The comment for the
OriginInfotype has been updated to specify that it provides information on an origin sent event. This change is more descriptive and provides better context for the type.22-34: The types of several fields in the
OriginInfotype have been changed fromStringtoInt. This includesoriginChainID,destinationChainID,optimisticSeconds, andmessageFlag. This change is likely due to the underlying data for these fields being numerical. Ensure that these changes are reflected in the corresponding database schema and any code that interacts with these fields.35-36: Two new fields,
messageStatusanddestinationInfo, have been added to theOriginInfotype. These fields are linked to theMessageStatusandDestinationInfotypes respectively using the@goFielddirective. This change allows for more detailed information to be retrieved when querying forOriginInfo.51-52: Two new fields,
messageStatusandoriginInfo, have been added to theDestinationInfotype. These fields are linked to theMessageStatusandOriginInfotypes respectively using the@goFielddirective. This change allows for more detailed information to be retrieved when querying forDestinationInfo.services/sinner/graphql/server/graph/queries.resolvers.go (4)
26-33: The function signature for
GetOriginInfohas been updated to take amessageHashinstead oftxHashandchainID. Ensure that all calls to this function throughout the codebase have been updated to match the new signature. Also, verify that theRetrieveOriginSentfunction has been updated to handlemessageHashas an argument.36-43: The function signature for
GetDestinationInfohas been updated to take amessageHashinstead oftxHashandchainID. Ensure that all calls to this function throughout the codebase have been updated to match the new signature. Also, verify that theRetrieveExecutedfunction has been updated to handlemessageHashas an argument.46-56: The new function
GetOriginInfosretrieves multiple records based ontxHashandchainID. Ensure that theRetrieveOriginSentsfunction is implemented correctly to handle these parameters and return the expected results. Also, verify that thedbToGraphqlModelOriginfunction can handle multiple records.59-70: The new function
GetDestinationInfosretrieves multiple records based ontxHashandchainID. Ensure that theRetrieveExecutedsfunction is implemented correctly to handle these parameters and return the expected results. Also, verify that thedbToGraphqlModelDestinationfunction can handle multiple records.services/sinner/db/mocks/event_db.go (4)
26-45: The
RetrieveExecutedfunction has been updated to take amessageHashinstead ofchainIDandtxHash. This change aligns with the updated database schema whereMessageHashis now the primary key. Ensure that all calls to this function throughout the codebase have been updated to match the new signature.47-59: The
RetrieveExecutedsfunction is a new addition that retrieves multiple executed events based on the providedchainIDandtxHash. This function could be useful in scenarios where multiple events are associated with the same transaction. Ensure that the function is used appropriately in the codebase.112-130: The
RetrieveOriginSentfunction has been updated to take amessageHashinstead ofchainIDandtxHash. This change aligns with the updated database schema whereMessageHashis now the primary key. Ensure that all calls to this function throughout the codebase have been updated to match the new signature.133-145: The
RetrieveOriginSentsfunction is a new addition that retrieves multiple origin sent events based on the providedchainIDandtxHash. This function could be useful in scenarios where multiple events are associated with the same transaction. Ensure that the function is used appropriately in the codebase.services/sinner/graphql/server/graph/model/models_gen.go (2)
13-22: The
DestinationInfostruct has been updated with two new fields:MessageStatusandOriginInfo. These fields provide additional context about the status of a message and its origin, respectively. Ensure that these fields are populated correctly wherever this struct is used. Also, verify that the GraphQL schema has been updated to reflect these changes.35-55: The
OriginInfostruct has been significantly updated. The types ofOriginChainIDandDestinationChainIDhave been changed from*stringto*int. This change should be verified across the codebase to ensure compatibility. TheOptimisticSecondsandMessageFlagfields have also been changed from*stringto*int, which should be more appropriate for these fields.New fields
MessageStatusandDestinationInfohave been added. These fields provide additional context about the status of a message and its destination, respectively. Ensure that these fields are populated correctly wherever this struct is used. Also, verify that the GraphQL schema has been updated to reflect these changes.Lastly, the fields
SummitTip,AttestationTip,ExecutionTip, andDeliveryTiphave been added. Ensure that these fields are populated correctly wherever this struct is used.services/sinner/graphql/server/graph/types.resolvers.go (6)
16-23: The
MessageStatusresolver function retrieves the message status from the database using theMessageHashfield of theDestinationInfomodel. The error handling is done correctly, wrapping the original error with context. This is a good practice as it helps in debugging if an error occurs.26-32: The
OriginInforesolver function retrieves the origin sent data from the database using theMessageHashfield of theDestinationInfomodel. The error handling is done correctly, wrapping the original error with context. The functiondbToGraphqlModelOriginis used to convert the database model to the GraphQL model. Ensure that this function handles all necessary conversions and edge cases.34-42: The
MessageStatusresolver function for theOriginInfomodel retrieves the message status from the database using theMessageHashfield of theOriginInfomodel. The error handling is done correctly, wrapping the original error with context.44-51: The
DestinationInforesolver function retrieves the executed data from the database using theMessageHashfield of theOriginInfomodel. The error handling is done correctly, wrapping the original error with context. The functiondbToGraphqlModelDestinationis used to convert the database model to the GraphQL model. Ensure that this function handles all necessary conversions and edge cases.54-59: The
DestinationInfoandOriginInfofunctions return the corresponding resolver implementations. This is a standard practice in GraphQL to provide a way to resolve specific fields on types.61-62: The
destinationInfoResolverandoriginInfoResolvertypes are defined, embedding theResolvertype. This is a common pattern in Go and GraphQL to provide methods on these types that can resolve the corresponding fields.services/sinner/db/event.go (1)
- 34-41: The
RetrieveOriginSentandRetrieveExecutedmethods have been updated to retrieve records based onmessageHashinstead ofchainIDandtxHash. This change aligns with the updated database schema whereMessageHashis now the primary key.New methods
RetrieveOriginSentsandRetrieveExecutedshave been added to retrieve multiple records based onchainIDandtxHash. This could be useful in scenarios where multiple events are tied to a single transaction.Ensure that all calls to these methods throughout the codebase have been updated to match the new signatures and that the new methods are used appropriately.
---new hunk for review---
// //nolint:interfacebloat type EventDBWriter interface { 47: // StoreOriginSent stores an OriginSent event. 48: StoreOriginSent(ctx context.Context, event model.OriginSent) error 49: // StoreExecuted stores an Executed event. 50: StoreExecuted(ctx context.Context, event model.Executed) error 51: // UpdateMessageStatus updates the status of a message. 52: UpdateMessageStatus(ctx context.Context, messageHash string, status graphqlModel.MessageStatus) error 53: // StoreLastStoredBlock stores the last block stored in sinner. 54: StoreLastStoredBlock(ctx context.Context, chainID uint32, address common.Address, blockNumber uint64) error } // EventDB combines EventDBReader and EventDBWriter.---old hunk for context---
// //nolint:interfacebloat type EventDBWriter interface { // StoreOriginSent stores an OriginSent event. StoreOriginSent(ctx context.Context, event model.OriginSent) error // StoreExecuted stores an Executed event. StoreExecuted(ctx context.Context, event model.Executed) error // UpdateMessageStatus updates the status of a message. UpdateMessageStatus(ctx context.Context, messageHash string, status graphqlModel.MessageStatus) error // StoreLastStoredBlock stores the last block stored in sinner. StoreLastStoredBlock(ctx context.Context, chainID uint32, address common.Address, blockNumber uint64) error } // EventDB combines EventDBReader and EventDBWriter.---end hunk---
services/sinner/graphql/server/graph/resolver/server.go (9)
39-40: The
ResolverRootinterface has been extended with two new methods:DestinationInfo()andOriginInfo(). Ensure that all implementations of this interface have been updated to include these new methods.74-75: New functions
MessageStatusandOriginInfohave been added to theDestinationInfoandOriginInfointerfaces respectively. Make sure these functions are implemented wherever these interfaces are used.93-98: The
Querystruct has been extended with new functionsGetDestinationInfo,GetDestinationInfos,GetMessageStatus,GetOriginInfo, andGetOriginInfos. Ensure that these functions are implemented and used correctly.101-108: New interfaces
DestinationInfoResolverandOriginInfoResolverhave been introduced. Make sure these interfaces are implemented correctly wherever they are used.314-320: New cases have been added to handle
DestinationInfo.messageStatus,DestinationInfo.originInfo,OriginInfo.destinationInfo, andOriginInfo.messageStatus. Ensure that these cases are handled correctly in the switch statement.423-435: New cases have been added to handle
Query.getDestinationInfo,Query.getDestinationInfos,Query.getOriginInfo, andQuery.getOriginInfos. Ensure that these cases are handled correctly in the switch statement.542-557: The GraphQL schema has been updated with new queries
getOriginInfo,getDestinationInfo,getOriginInfos, andgetDestinationInfos. Make sure these queries are implemented and used correctly.580-605: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [572-598]
The
OriginInfoandDestinationInfotypes in the GraphQL schema have been updated with new fieldsmessageStatusanddestinationInfo/originInforespectively. Ensure that these fields are handled correctly in the GraphQL resolvers.
- 1103-1237: New resolvers have been added for
DestinationInfo.messageStatus,DestinationInfo.originInfo,OriginInfo.messageStatus, andOriginInfo.destinationInfo. Make sure these resolvers are implemented correctly and return the expected data.1672, 1713:
The return type of theOriginInfo.originChainIDandOriginInfo.destinationChainIDfields has been changed fromstringtoint. Ensure that this change is reflected in all places where these fields are used.services/sinner/api/resolver_test.go (2)
- 30-38: The test
TestGetOrigin()has been updated to test the newGetOriginInfo()function that takes amessageHashinstead oftxHashandchainID. It also tests the newGetOriginInfos()function. Ensure that themessageHashis correctly generated and used in these tests. Also, consider adding a check to verify the length of theresultsslice to ensure that theGetOriginInfos()function is returning the correct number of results.+ Equal(t.T(), txHash, *result.Response.OriginTxHash) + results, err := t.sinnerAPI.GetOriginInfos(t.GetTestContext(), txHash, int(chainID)) + Nil(t.T(), err) + NotNil(t.T(), results) + Equal(t.T(), txHash, *results.Response[0].OriginTxHash)Committable suggestion (Beta)
result, err := t.sinnerAPI.GetOriginInfo(t.GetTestContext(), messageHash) Nil(t.T(), err) NotNil(t.T(), result) Equal(t.T(), txHash, *result.Response.OriginTxHash) results, err := t.sinnerAPI.GetOriginInfos(t.GetTestContext(), txHash, int(chainID)) Nil(t.T(), err) NotNil(t.T(), results) Equal(t.T(), 1, len(results.Response)) Equal(t.T(), txHash, *results.Response[0].OriginTxHash)
- 59-67: The test
TestGetExecuted()has been updated to test the newGetDestinationInfo()function that takes amessageHashinstead oftxHashandchainID. It also tests the newGetDestinationInfos()function. Ensure that themessageHashis correctly generated and used in these tests. Also, consider adding a check to verify the length of theresultsslice to ensure that theGetDestinationInfos()function is returning the correct number of results.+ Equal(t.T(), txHash, *result.Response.TxHash) + results, err := t.sinnerAPI.GetDestinationInfos(t.GetTestContext(), txHash, int(chainID)) + Nil(t.T(), err) + NotNil(t.T(), results) + Equal(t.T(), txHash, *results.Response[0].TxHash)Committable suggestion (Beta)
result, err := t.sinnerAPI.GetDestinationInfo(t.GetTestContext(), messageHash) Nil(t.T(), err) NotNil(t.T(), result) Equal(t.T(), txHash, *result.Response.TxHash) results, err := t.sinnerAPI.GetDestinationInfos(t.GetTestContext(), txHash, int(chainID)) Nil(t.T(), err) NotNil(t.T(), results) Equal(t.T(), 1, len(results.Response)) Equal(t.T(), txHash, *results.Response[0].TxHash)services/sinner/graphql/client/client.go (7)
22-26: The
Querystruct has been updated to include two new fields:GetOriginInfosandGetDestinationInfos. These fields correspond to the new GraphQL queries for retrieving multiple records based on the chain ID and transaction hash. The types of these fields are slices of pointers tomodel.OriginInfoandmodel.DestinationInfo, respectively, indicating that the queries return multiple records.61-72: The
GetOriginInfoandGetOriginInfosstructs have been updated with new fields and type changes. TheOriginChainID,DestinationChainID,OptimisticSeconds,MessageFlag,Version, andGasLimitfields have been changed from*stringto*int. This change aligns the types with the expected data types in the GraphQL schema. TheMessageHashfield has been added to both structs, reflecting the change in the primary key fromTxHashtoMessageHashin theOriginSenttable.94-103: A new struct
GetDestinationInfoshas been added to handle the response from thegetDestinationInfosGraphQL query. This struct is similar toGetDestinationInfobut is designed to handle multiple records in the response.155-157: The
GetOriginInfofunction and the corresponding GraphQL query document have been updated to replace thetxHashandchainIDparameters withmessageHash. This change reflects the update in the primary key fromTxHashtoMessageHashin theOriginSenttable.193-196: New GraphQL query documents and functions have been added for the
getOriginInfosandgetDestinationInfosqueries. These queries retrieve multiple records from theOriginSentandExecutedtables based on the chain ID and transaction hash. The functions take a context, transaction hash, chain ID, and optional HTTP request options, and return the corresponding response struct.221-223: The
GetDestinationInfofunction and the corresponding GraphQL query document have been updated to replace thetxHashandchainIDparameters withmessageHash. This change reflects the update in the primary key fromTxHashtoMessageHashin theExecutedtable.248-251: New GraphQL query documents and functions have been added for the
getDestinationInfosqueries. These queries retrieve multiple records from theExecutedtable based on the chain ID and transaction hash. The functions take a context, transaction hash, chain ID, and optional HTTP request options, and return the corresponding response struct.
| // TxIndex is the index of the tx in a block. | ||
| TxIndex uint `gorm:"column:tx_index"` | ||
| // MessageHash is the message hash. | ||
| MessageHash string `gorm:"column:message_hash"` | ||
| MessageHash string `gorm:"column:message_hash;primaryKey"` |
There was a problem hiding this comment.
should be a foreign key constraint to message table
There was a problem hiding this comment.
Is this for data integrity if deleting from the db? currently the messagestatus table is updated concurrently w/origin/destination table insert while indexing.
An idea could be to do a has many relationship, but the idea of the message status table was to be a lite as possible on query side so it could be pinged a lot for quick updates.
type MessageStatus struct {
MessageHash string `gorm:"column:message_hash;uniqueIndex:idx_message_hash_status"`
OriginTxHash string `gorm:"column:origin_txhash"`
DestinationTxHash string `gorm:"column:destination_txhash"`
OriginSentMessages []OriginSent `gorm:"foreignKey:MessageHash;references:MessageHash;constraint:OnUpdate:CASCADE,OnDelete:SET NULL;"`
ExecutedMessages []Executed `gorm:"foreignKey:MessageHash;references:MessageHash;constraint:OnUpdate:CASCADE,OnDelete:SET NULL;"`
}There was a problem hiding this comment.
has many would be the idea yeah, this will also speed up joins, etc
There was a problem hiding this comment.
destination tx hash is many to may
There was a problem hiding this comment.
Review Status
Actionable comments generated: 2
Configuration used: CodeRabbit UI
Files selected for processing (1)
- services/sinner/db/sql/base/read.go (3} hunks)
Additional comments: 3
services/sinner/db/sql/base/read.go (3)
59-106: The
RetrieveOriginSent(),RetrieveOriginSents(),RetrieveExecuted(), andRetrieveExecuteds()functions have been updated to usemessageHashinstead ofchainIDandtxHash. This change aligns with the updated database schema whereMessageHashis now the primary key. Ensure that all calls to these functions throughout the codebase have been updated to match the new signatures. Also, verify that themessageHashis being correctly generated and used in the upstream code.72-83: The new function
RetrieveOriginSents()has been added to retrieve multipleOriginSentrecords based onchainIDandtxHash. This function can be useful when there are multipleOriginSentevents associated with a single transaction. However, it's important to note that this function may return a large number of records for transactions with many events, which could impact performance. Consider adding pagination or limiting the number of records returned if this becomes an issue.98-106: The new function
RetrieveExecuteds()has been added to retrieve multipleExecutedrecords based onchainIDandtxHash. Similar to theRetrieveOriginSents()function, this function may return a large number of records for transactions with many executed events. Consider adding pagination or limiting the number of records returned if this becomes an issue.
| // TxIndex is the index of the tx in a block. | ||
| TxIndex uint `gorm:"column:tx_index"` | ||
| // MessageHash is the message hash. | ||
| MessageHash string `gorm:"column:message_hash"` | ||
| MessageHash string `gorm:"column:message_hash;primaryKey"` |
There was a problem hiding this comment.
destination tx hash is many to may
There was a problem hiding this comment.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files ignored due to filter (1)
- services/sinner/go.mod
Files selected for processing (1)
- services/sinner/db/event.go (1 hunks)
Additional comments: 1
services/sinner/db/event.go (1)
- 33-46: The changes to the
EventDBReaderinterface look good. The new methodsRetrieveOriginSentsandRetrieveExecutedshave been added correctly and the existing methodsRetrieveOriginSentandRetrieveExecutedhave been updated to usemessageHashinstead ofchainIDandtxHash. Ensure that all implementations of this interface have been updated to reflect these changes.
There was a problem hiding this comment.
Review Status
Actionable comments generated: 1
Configuration used: CodeRabbit UI
Files selected for processing (1)
- services/sinner/api/server.go (2 hunks)
Additional comments: 8
services/sinner/api/server.go (8)
24-25: The introduction of
errNoPortis a good practice for error handling. It provides a clear and specific error message when the port is not specified.33-34: The use of
ginhelper.New(logger)to create a new router is good for maintainability and modularity. It abstracts the creation of a new router into a helper function, which can be reused in other parts of the code.2-8: > Note: This review was outside of the patch, but no patch was found that overlapped with it. Original lines [36-41]
The error handling here is well done. If there is an error initializing the database, the function returns immediately with a wrapped error message. This is a good practice as it provides more context about the error.
- 2-8: > Note: This review was outside of the patch, but no patch was found that overlapped with it. Original lines [43-44]
The use of
gqlServer.EnableGraphql(router, eventDB, cfg, handler)to enable GraphQL on the router is good for modularity. It abstracts the process of enabling GraphQL into a separate function, which can be reused in other parts of the code.
- 2-8: > Note: This review was outside of the patch, but no patch was found that overlapped with it. Original lines [46-47]
The creation of a new listener is well handled. If there is an error creating the listener, the function returns immediately with a wrapped error message. This is a good practice as it provides more context about the error.
- 2-8: > Note: This review was outside of the patch, but no patch was found that overlapped with it. Original lines [49-58]
The use of an error group to handle the serving of HTTP requests is a good practice. It allows for the handling of multiple goroutines that return an error. If any of the goroutines return an error, the error group will return that error.
- 2-8: > Note: This review was outside of the patch, but no patch was found that overlapped with it. Original lines [60-65]
The error handling here is well done. If there is an error with the server, the function returns immediately with a wrapped error message. This is a good practice as it provides more context about the error.
- 2-8: > Note: This review was outside of the patch, but no patch was found that overlapped with it. Original lines [67-130]
The
InitDBfunction is well structured and handles errors appropriately. It checks the database type and initializes the appropriate database accordingly. If there is an error at any point, it returns immediately with a wrapped error message. This is a good practice as it provides more context about the error.
| if cfg.HTTPPort == 0 { | ||
| return errNoPort | ||
| } |
There was a problem hiding this comment.
The check for cfg.HTTPPort == 0 is a good addition. It ensures that the server does not start without a valid port. However, it might be beneficial to also check if the port is within the valid range (1-65535). If the port is outside this range, it should also return an error.
if cfg.HTTPPort <= 0 || cfg.HTTPPort > 65535 {
return errNoPort
}* init * stashing at prev checkpoint to resolve build issues * updating graphql * live filling updates * stash prev changes before tests * update queries w/tests * update api and cli * stash before deploy * api tests * lint * lint * lint + gen * code cov * gen * adding code cov * lint + test + coderabbit suggestions * symlink * edits * hold * Update go.mod * sinner docker + main.go * sinner test flake, bytes -> hex string update, update assert use, lint * update logging * deprecate port flag * updating fetch ceil * adding concurrency during parse store * add comments * gen (stringer) * add build to .goreleaser.yml * build * Revert "build" [goreleaser] This reverts commit 8c61076. * fix goreleaser [goreleaser] * fix replacement issue * [sinner] add start readme (#1499) * add start readme * fix https://github.com/synapsecns/sanguine/pull/1380/files#r1371810612 --------- Co-authored-by: Trajan0x <[email protected]> * sinner strings for contract_type (#1498) Co-authored-by: Trajan0x <[email protected]> * trajan edits * nits * explorer update * Sinner: resolvers and updating db read functions (#1514) * init staging * add more db read functions * update model to where * update filters * hash * Revert "hash" This reverts commit 9b159df. * remove unused db mocks * handle invalid port --------- Co-authored-by: Trajan0x <[email protected]> * type fix * simplify w generics * add go error group to unified command + updated read.go * code rabbit nit * logger fix * Parser, API, and config updates * tests, sinner/indexer updates, db updates * lint + refactor graphql + db * Add log range asc to API * [goreleaser] * Update README.md * refactor indexer * exit 1 on fail * update scribe fetcher and pagination behavior * mysql context * mysql + refresh rate * update config and readme + [goreleaser] * update tests * typo + [goreleaser] * prom exporter gen * revert abi - [goreleaser] * [goreleaser] * specify varchar length for indexing [goreleaser] * update 64 to 66 to account for 0x [goreleaser] * update api * [goreleaser] * gen * update comment * [goreleaser] * add asc flag * [goroutine] * [goreleaser] --------- Co-authored-by: Trajan0x <[email protected]> Co-authored-by: trajan0x <[email protected]>
* init * stashing at prev checkpoint to resolve build issues * updating graphql * live filling updates * stash prev changes before tests * update queries w/tests * update api and cli * stash before deploy * api tests * lint * lint * lint + gen * code cov * gen * adding code cov * lint + test + coderabbit suggestions * symlink * edits * hold * Update go.mod * sinner docker + main.go * sinner test flake, bytes -> hex string update, update assert use, lint * update logging * deprecate port flag * updating fetch ceil * adding concurrency during parse store * add comments * gen (stringer) * add build to .goreleaser.yml * build * Revert "build" [goreleaser] This reverts commit 8c61076. * fix goreleaser [goreleaser] * fix replacement issue * [sinner] add start readme (#1499) * add start readme * fix https://github.com/synapsecns/sanguine/pull/1380/files#r1371810612 --------- Co-authored-by: Trajan0x <[email protected]> * sinner strings for contract_type (#1498) Co-authored-by: Trajan0x <[email protected]> * trajan edits * nits * explorer update * Sinner: resolvers and updating db read functions (#1514) * init staging * add more db read functions * update model to where * update filters * hash * Revert "hash" This reverts commit 9b159df. * remove unused db mocks * handle invalid port --------- Co-authored-by: Trajan0x <[email protected]> * type fix * simplify w generics * add go error group to unified command + updated read.go * code rabbit nit * logger fix * Parser, API, and config updates * tests, sinner/indexer updates, db updates * lint + refactor graphql + db * Add log range asc to API * [goreleaser] * Update README.md * refactor indexer * exit 1 on fail * update scribe fetcher and pagination behavior * mysql context * mysql + refresh rate * update config and readme + [goreleaser] * init * mod lint * omnirpc version bump * chart bump * Update values.yaml * lint * rm omnirpc dependacy * update op rpc (ratelimited) * rev --------- Co-authored-by: Trajan0x <[email protected]> Co-authored-by: trajan0x <[email protected]>
Summary by CodeRabbit
New Features:
GetOriginInfosandGetDestinationInfosfunctions to retrieve multiple origin and destination information respectively, enhancing data retrieval capabilities.Refactor:
txHashandchainIDwithmessageHashfor single record retrieval and vice versa for multiple records, improving the specificity of data queries.OriginSentandExecuteddatabase models, changing the primary key toMessageHashand adding an index toChainID, optimizing database operations.New Feature:
dbToGraphqlModelOriginanddbToGraphqlModelDestinationfunctions to convert database models to GraphQL models, improving data handling between different systems.Refactor:
DestinationInfoandOriginInfoGraphQL models, adding new fields and changing the types of several existing fields, enhancing the granularity of data representation.