Skip to content

golangci-lint in ci#105

Merged
faddat merged 9 commits intosei-protocol:masterfrom
notional-labs:golangci-lint
Jul 12, 2022
Merged

golangci-lint in ci#105
faddat merged 9 commits intosei-protocol:masterfrom
notional-labs:golangci-lint

Conversation

@faddat
Copy link
Contributor

@faddat faddat commented Jul 12, 2022

This gives Sei the same golang-ci lint settings that I used for ibc-go.

cosmos/ibc-go#1418

They are pretty strict and this may initially fail.

@faddat faddat merged commit a337a70 into sei-protocol:master Jul 12, 2022
alg747 pushed a commit to UXDProtocol/sei-chain that referenced this pull request Jul 20, 2022
* golangci-lint in ci
* linting per .golangci.yml
masih pushed a commit that referenced this pull request Sep 29, 2025
## Describe your changes and provide context
Since external packages like wasmd and ibc depends on cosmos's store
interface, we cannot introduce interface-breaking changes. This makes
passing custom cache limit impossible, so here we change it to be a
default value for now (1 million).

We would likely need to fork wasmd and ibc if we want the ability to
specify custom cache limit, or introduce any change that breaks
interface in general.

## Testing performed to validate your change
built with sei-chain
masih pushed a commit that referenced this pull request Sep 30, 2025
## Describe your changes and provide context
Since external packages like wasmd and ibc depends on cosmos's store
interface, we cannot introduce interface-breaking changes. This makes
passing custom cache limit impossible, so here we change it to be a
default value for now (1 million).

We would likely need to fork wasmd and ibc if we want the ability to
specify custom cache limit, or introduce any change that breaks
interface in general.

## Testing performed to validate your change
built with sei-chain
masih pushed a commit that referenced this pull request Oct 9, 2025
masih pushed a commit that referenced this pull request Oct 9, 2025
#118)

This reverts commit c35c30a, reversing
changes made to 302e86d.

## Describe your changes and provide context
- Revert surfacing errors from db layer since the rpc / keeper / store
layer hard codes a lot of handling of record not found and there needs
to be a larger refactor
- Can re introduce this error after a redesign and consideration of
impact

## Testing performed to validate your change
- Verified in unit tests and on node
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants