-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lazy
: Account for key size in fallible storage ops
#1962
Conversation
Signed-off-by: Cyrill Leutwiler <bigcyrill@hotmail.com>
Signed-off-by: Cyrill Leutwiler <bigcyrill@hotmail.com>
🦑 📈 ink! Example Contracts ‒ Changes Report 📉 🦑
Link to the run | Last update: Mon Nov 6 16:51:56 CET 2023 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@mutantcornholio gitspiegel is failing, looks related to #1959? |
@xermicus yeah, I'm on it already. For some reason, doesn't reproduce in other repositories |
gitspiegel sync is failing on some already existing PRs, because the token from secrets isn't passed: #1962 This PR tests if new PRs are also affected
@xermicus seems that restarting a job doesn't update the secrets inside, could you try adding a commit, or rebasing please? |
Signed-off-by: Cyrill Leutwiler <bigcyrill@hotmail.com>
a97046d
to
13f980e
Compare
@mutantcornholio just pushed again |
Turned out, that we've never tested this feature for PRs from forks... |
Alright, thanks @mutantcornholio 👍 |
Followup to #1910. The on-chain engine encodes the key and the value into the scoped buffer, so we need to account for both (same as
Mapping
).