-
Notifications
You must be signed in to change notification settings - Fork 99
Issues: gear-tech/gear
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Randomization of fuzzer configuration through Feature request
arbitrary
crate
C1-feature
#3988
opened May 29, 2024 by
playX18
rename Refactoring proposal
Q1-easy
code
to bytes
in gear_core::{Code, InstrumentedCode}
C2-refactoring
#3985
opened May 27, 2024 by
grishasobol
Send stuck inheritors' value to treasury
C1-feature
Feature request
#3979
opened May 20, 2024 by
ark0f
Introduce a proper gas allowance management in the Feature request
gtest
C1-feature
#3977
opened May 18, 2024 by
techraed
Provide more test cases for gas compensation on Refactoring proposal
Q1-easy
Externalities
methods failures
C2-refactoring
#3976
opened May 18, 2024 by
techraed
Fix Something isn't working
C2-refactoring
Refactoring proposal
Q2-moderate
gr_read
gas compensation on operation failure
C0-bug
#3975
opened May 18, 2024 by
techraed
Improve documentation and remove unnecessary generics in the userspace
C2-refactoring
Refactoring proposal
#3974
opened May 17, 2024 by
StackOverflowExcept1on
feat(gstd): Reimport some primitive types and implement
NonZeroU256
#3973
opened May 17, 2024 by
breathx
use real memory grow cost in Something isn't working
gtest
C0-bug
#3970
opened May 16, 2024 by
grishasobol
Consider options of redesigning building approach (deprecate Refactoring proposal
P4-consider
Lowest priority
gear-wasm-builder
)
C2-refactoring
#3945
opened May 6, 2024 by
breathx
Simplify/remove Issue is in progress or PR draft is not ready to be reviewed
C2-refactoring
Refactoring proposal
cost_*
macros
A1-inprogress
#3943
opened May 2, 2024 by
ByteNacked
Store Refactoring proposal
heap
interval as field in AllocationsContext
in order to skip useless panics
C2-refactoring
#3932
opened Apr 30, 2024 by
grishasobol
Charge for data section instantation
C1-feature
Feature request
#3931
opened Apr 30, 2024 by
ByteNacked
Move
allocations
and pages_with_data
to separate child storages.
#3928
opened Apr 29, 2024 by
grishasobol
wasm-builder
cause failures in vs-code rust analyser extensions
C0-bug
#3925
opened Apr 28, 2024 by
grishasobol
Proposal: programs' Refactoring proposal
frame_system::AccountInfo
permanent existence
C2-refactoring
#3924
opened Apr 26, 2024 by
breathx
13 tasks
gclient and gsdk does not compile on the nightly version
C0-bug
Something isn't working
#3915
opened Apr 23, 2024 by
StackOverflowExcept1on
Make it able to define Refactoring proposal
Q1-easy
wasm-gen
config in runtime-fuzzer
from caller side (i.e., fuzz target)
C2-refactoring
#3900
opened Apr 17, 2024 by
techraed
save_program_memory_dump_at
must dump static pages also
C0-bug
#3893
opened Apr 16, 2024 by
grishasobol
Use extractors in backend to avoid accidental memory registry creation
#3891
opened Apr 15, 2024 by
ark0f
Split Refactoring proposal
D1-core
Gear Core
ErrorReplyReason::InactiveActor
into short and long versions
C2-refactoring
#3890
opened Apr 15, 2024 by
ark0f
impl Environment for Ext
in atomic way
C0-bug
#3881
opened Apr 12, 2024 by
breathx
change return types for Feature request
insert
and remove
in numerated::IntervalsTree
C1-feature
#3879
opened Apr 12, 2024 by
grishasobol
Consider to remove code data section and stack overlap checking
C2-refactoring
Refactoring proposal
#3875
opened Apr 9, 2024 by
grishasobol
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.