Clarity Wasm WG: Mtg Min Thread

[obycode]

October 09, 2023

📝 Status Updates & Blockers, by IC

Anthony

• Finished sha256 in Wasm - just pushed
• Need to include it in WasmGenerator
• Will work on ripe160

Kris

• Working through the codebase - removing more code
• Finding more things he's not happy with and fixing them up as he goes
• Removing unwraps and other things like that
• Hit some unexpected issues when starting with the define- functions
• Still in "cleanup mode"
• PR today!

Cyle

• Working on A-B tester
• Using the existing production chainstate as baseline, then run the interpreter, eventually the Wasm (and extensible to others)
• Making it generic/modular so that the logic is nicely isolated
• Thinking of how this can be useful in various scenarios and making it flexible enough to do all of those
• Walking through all of the contract calls is working
• Ran into an issue with maps
  • Not sure how to iterate over keys in a map (without knowing the keys ahead of time)
  • Instead reading all of the values and comparing, which guarantees they are the same, even if we don't know the keys
• Timeline for a deliverable?
  • Hopefully in 2 weeks should have something demoable, not yet fully deliverable
• Well update the commitizen PR

Brice

• contract-call? testing almost functional - will try to finish today
  • Discuss with Cyle if can't get remaining issues resolved
• Working on print next
• Also tackling the remaining simpler expressions in between
  • Will have help in writing the unit tests from Chris

🚘 Parking Lot Topics

• Is the MARF changing with the Nakamoto update?
  • Cyle will verify in the stacks-core-devs Discord
• Epoch 3.0 PR
  • Cyle will update tonight
  • Brice will review

[obycode]

Meeting Date (Oct 16, 2023)

📝 Status Updates & Blockers, by IC

Chris:

• Status Updates:

  • Intro to the team
  • Wrote tests for some of the missing expressions
  • Implementing expressions, starting with not

• Blockers:

  • Stuck on getting the new function called, needs some pointers

Cyle:

• Status Updates:

  • A-B Tester going well - roughly 50%
  • Hitting issues with borrow checker
  • Optimistic - demoable next Monday (with interpreter)
  • Will take a look at the stacks-blockchain for integration

• Blockers:

Anthony:

• Status Updates:

  • Finished sha256 - Add sha256 function clarity-wasm#117
    • Would like help for property testing - explanation in PR
      • Chris will take a look when he finishes current work
    • Hack in property-testing - needs some investigation
    • Could postpone until after hash160 if no one is able to take it before
  • Working on hash160
    • Should finish today, then testing
  • Interested in taking remaining comparison operators

• Blockers:

Kris:

• Status Updates:
  • Frustrating issue trying to do testing
    • Might need some help to move past
    • Looking for something to take clarity, compile to wasm, and run it
    • Needs more testing to be comfortable with refactorizations
    • Question about define-private

-Blockers:

Hugo:

• Status Updates:

  • Ready to join us next week

• Blockers:

  • Waiting for changes to clarity::clarity_wasm to integrate with clarinet

Brice:

• Status Updates:

  • Finished contract-call?
    • First version doesn’t yet support traits or have the proper host-side checks
  • Working on print

• Blockers:

🚘 Parking Lot Topics

Walkthroughs

• Chris looking for walkthrough for implementation
• Kris looking for walkthrough for testing
• Completed both of these walkthroughs and answered questions at the end of the meeting.

[obycode]

Meeting Date (Oct 23, 2023)

📆 Agenda

• Status updates
• Demo from Cyle on A-B testing framework
• Walkthrough from Anthony on sha256 and hash160 implementations
• If time allows:
  • Cyle can share the “rustref” solution he worked on
  • Cyle can share a clarity lexer+parser implementation using logos (lexing) + chumsy (parsing) + ariadne (error reporting)
• Two requests coming from other teams:
  • 256-bit arithmetic
  • p256k1 library wrapper

📝 Status Updates & Blockers, by IC

Chris:

• Status Updates:
  • Conference last week
  • Will review PR comments and update
  • Need to review the refactoring from Kris

Cyle:

• Status Updates:
  • Need a couple more days for A/B tester demo
    • Could show on Wednesday
    • Will ad-hoc schedule a time
  • Will demo the other things today still

Kris:

• Status Updates:
  • Some work on conditionals
    • Paused to finish the refactoring, so we’re not half-way in between
  • Finished the refactoring! PR merged
  • Work to keep in mind for later
    • Use methods for accessing the generator fields instead of making them all public
    • Review duplicated code
    • Will incorporate small improvements like this while doing the implementations

Anthony:

• Status Updates:
  • Added property testing for buffers
  • Fixed an error in the sha256 algorithm
  • Working on buff-to-[u]int
  • Comparison operators next

Brice:

• Status Updates:
  • print is finished update and expand upon overview document #64
  • Tuple functions finished Package #68
  • In progress sequence functions added details on list generation #63
  • Need to spend some time this week digging into a trait issue

Hugo

• Status Updates:
  • Will be able to join us this week, pending Clarinet 2.0 release

🚘 Parking Lot Topics

None

[obycode]

Meeting Date (Oct 30, 2023)

📆 Agenda

• Status updates

📝 Status Updates & Blockers, by IC

Kristoffer:

• Status Updates:
  • Finishing up conditional if, filter
  • Will submit PR today
  • Next: will pick another issue, not sure which yet

Chris:

• Finished optional and response type functions, is-some, is-none, is-ok, is-err
• Added TypeError
• Next: implement default-to, split up tests file

Anthony:

• Finished buffer functions: buff-to-[u]int-[bl]e
• Finished comparisons for buffers and ascii strings
• Found a bug in int division
• Next: is-eq for remaining types, string-utf8

Brice:

• Finished sequence functions: append, as-max-len?, concat, element-at, len, replace-at?, slice?
• Implemented let
• Discussions about p256k1 functions
• Nakamoto PR reviews
• Next: review remaining functions, categorize and create issues for all

Cyle:

• Stuck on duplicate contract ID issue
  • Has an open question in stacks-core-devs channel
  • Need to figure out how to determine if a tx succeeded or failed

Hugo:

• Still working on Clarinet 2 release and some Clarinet issues
• Experimented with Wasm runtime via node
• Summary of Node.js experimentation for the rest of the team
• Should be able to focus on this this week

🚘 Parking Lot Topics

• Lisp to Wasm compiler from Spritely Institute (link)
  • Could be interesting to replace our compiler and then we focus on the runtime integration
  • Kristoffer interested to investigate this further
  • Need to investigate stability

[obycode]

Meeting Date (Nov 6, 2023)

📆 Agenda

• Status updates (all)
• Discuss issue with prefixing sodlib functions (Chris)
• Notice - Brice is out next week
• Team Game!

📝 Status Updates & Blockers, by IC

Hugo:

• PoC for Wasm in Node.js (wasm-in-wasm)
• Clarity-vm needs to expose the runtime with both modes
• Clar2wasm should be able to be used in wasm (no developer-mode)
• Mirror of clarity_wasm.rs with Node.js interface
• Shared context about why this work is necessary
  • Clarinet
  • SDK

Cyle:

• Still making progress on the A/.B tester
• Lots of digging into the various contexts in the node
• Found and fixed an issue with looking up burnchain info
• Need to load up the missing info that is not stored in the stacks-node
  • Only blocks exist, but we don’t know about in between
  • E.g. transaction results
• Replay the interpreter and replay on Wasm, store all info, then compare

Chris:

• Working on the no-op functions, mostly finished
• Was waiting for some functions in the trait PR (now merged)
• Stdlib prefixing - discussions in PR, now hitting a problem
  • Need to change the function name, not the exported name
  • This is due to the way we’re adding to the standard.wat when compiling a contract instead of linking with it

Anthony:

• Working on is-eq for more complex types - just lists left
• Should be done in next 2 days

Kristoffer:

• Working on and implementation
• PR reviews and updates
• Hit some issues with setup

Brice:

• Finished trait implementations
• Also finished dynamic contract call support
• Finishing remaining host function
• Reviewing Nakamoto PRs and other core blockchain issues

🚘 Parking Lot Topics

• Brice will be out next week
  • Brice will post Sprint Sync discussion before leaving, and requests updates from the team on Tuesday morning
  • Kris volunteered to represent the Clarity Wasm WG at next week's Sprint Sync
  • Cyle volunteered to host the WG internal meeting

[obycode]

Meeting Date (Nov 13, 2023)

📆 Agenda

• Status updates (all)

📝 Status Updates & Blockers, by IC

Hugo:

• Implemented new clarity vm in clarity
• Next step to move the logic from the clarinet repo to the clarity vm
• This area of clarinet needs a bit of refactoring so has spent some time writing unit tests for these more “shady” areas.
• Blocker: Would like epoch 3 available in the clarity branch

Cyle:

• Updated epoch 3 PR according to Aarons comments
• Got slightly distracted in unsafe argumentations with Jude etc.
• Chugging along with a/b tester, I had just broken it prior to the meeting so wasn’t able to run it, but will toss up a commit that works so primarily Kristoffer can check it out as a learning tool.

Chris:

• Finish contract-of impl in noops
• Working on adding stdlib prefix to user-defined functions
• Organize the type definitions on standard.wat
• Lost a few days due to Hiro Platform needs

Anthony:

• Mostly working on is-eq
• Some refactoring to do
• Working on str-to-int and int-to-str

Kristoffer:

• Stuck in duplicates issue
• and and or are finished
• Working on unwrap/try (needs to short-circuit even harder, thinks he has it sorted out)
• match coming up this week

Brice (async):

• Finished remaining host functions
  • get-burn-block-info?
  • at-block
• Cleaned up read/write Wasm memory functions and added unit tests
• Implemented remaining host interface functions via host-interface functions
  • keccak256
  • sha512
  • sha512/256
  • secp256k1-recover?
  • secp256k1-verify
• Implemented principal functions
  • is-standard
  • principal-construct?
  • principal-destruct?
• Off this week

🚘 Parking Lot Topics

[obycode]

Meeting Date (Nov 20, 2023)

📆 Agenda

• Status updates (all)

📝 Status Updates & Blockers, by IC

Chris:

• Finished "noop" functions
• Added "stdlib." prefix to imported functions
• Type definitions reorg
• Looking for next good task

Hugo:

• Clarinet CI work last week
  • Fixing coverage and other issues
  • Will check for similar issues in clarity-wasm repo
• Back to clar2wasm work this week

Kris:

• Working on match and other conditional functions
• Got clarinet up, running and usable for local testing

Hamza:

• Working on sha512 implementation
  • Starting with Rust implementation, then will take on Wasm implementation

Anthony:

• Two PRs waiting for reviews
  • int-to-ascii
  • is-eq
• Will add property tests for is-eq in a separate PR

Brice:

• Started principal-of; will finish today
• Will review PRs and update wiki with latest status

🚘 Parking Lot Topics

[obycode]

Meeting Date (Nov 27, 2023)

📆 Agenda

• Status updates (all)

📝 Status Updates & Blockers, by IC

Chris (async):

• Continued work on function implementations
• Should finish up index-of today

Kristoffer:

• Working on the early exit functions
  • Everything is done now, just need to put it all together
  • Discussed the issue with restoring the stack pointer and it is clear now
• Should finish up by tomorrow and grab another item

Hugo:

• Big refactor on clarinet last week
  • Improves the interface with the interpreter
  • Will have a PR for clarinet and for clarity-wasm
• Blocked by Brice rebasing the stacks-core branch on top of latest (with epoch 3.0)

Anthony:

• Writing prop-test strategy for type signatures and values to make it easy to write additional property tests
  • Found some missing implementations in the code (write_to_memory)
• Started to-consensus-buff? and from-consensus-buff? (est. ~1 week)

Cyle:

• Got past genesis block in A/B tester!
• Identifying additional missing chain state information to get past next issue

Hamza:

• Working on sha512
  • Explored the implementation in Rust
  • Identified the differences with sha256 for comparison
  • PR this week hopefully

Brice:

• Finished principal-of?
• Reviewed and organized remaining tasks
• Started to rebase feat/clarity-wasm-runtime on top of next (mainly to get epoch 3.0 and unblock Hugo)

🚘 Parking Lot Topics

[obycode]

Meeting Date (Dec 4, 2023)

📆 Agenda

• Status updates (all)

📝 Status Updates & Blockers, by IC

Chris:

• Finished implementation of index-of?
  • Ready for re-review
• Started working on map implementation
  • 80% done
  • Pull request later today

Hugo:

• Using the latest clarity VM in Clarinet
  • Will be really nice to get this merged to avoid these headaches
• Found bug in Clarinet
  • Code coverage - small part broke causing if branches not marked as hit when it should be
• Want to complete the clarinet integration done ASAP

Anthony:

• to-consensus-buff? completed
• Refactored list serialization to be more efficient
• Started filling remaining types in WasmGenerator “write_to_memory”
• Property testing framework for wasm generation
  • Finding bugs while writing these tests
  • Should be done with that today/tomorrow

Cyle:

• Got first 10,000 blocks processed in the A/B tester (not processing transactions yet)
• Structure to implement and compare needs some more work
  • Struggling with lifetimes from existing structures

Hamza:

• Studied memory management in sha256 and understands changes needed for sha512
• Created several issues related to readability and clarity in WAT code while reviewing and learning

Brice:

• Re-visited contract-call? and local calls to ensure all of the appropriate checks are in place
• Adjusted epoch gating for initializing a contract and calling a function
• Worked with Hugo on getting our stacks-core branch compilable in wasm

Kris (async):

• Mostly dealt with a plethora of technical issues around upgrading rustc and macos
• Made some progress on the final word try but need a debug session still.
  • Will have more relevant updates tomorrow

🚘 Parking Lot Topics

• Team building game!

[obycode]

Meeting Date (Dec 11, 2023)

📆 Agenda

• Status updates (all)

📝 Status Updates & Blockers, by IC

Anthony:

• PR #204 - property testing from generated values
  • Lots of fixes, workarounds, etc.

Kristoffer:

• System back up and working again (dependencies, Mac issues, etc.)
• Implemented unwrap-err!
• Need some help with try!

Chris:

• Working on addressing issues with index-of
  • Discussing with Anthony to fix comparison issue
  • Should be finished up today
• Will take map next

Cyle:

• Refactoring blockchain core to introduce some traits to make it possible to tie in with the instrumented DBs
• Avoid the raw sqlite connections that are passed around everywhere
• Has clarity crate working now
• Should finish this this week

Hugo:

• Updated Clarity VM and Clarinet to work with epoch 3
• Helped Brice with getting devnet started
• Clarinet needs enhancements to stack in pox-4 and to setup
• Setup console to run interpreter and wasm VM in parallel for all contracts
  • Compare the result and timing
  • Interpreter is faster that clarity-wasm in basic contracts
    • Likely due to setup/tear-down that is required
    • Should be able to optimize some more
• Focus this week on epoch3 handling and handling clarity-wasm properly in clarinet
  • E.g. eval equivalent in clarity-wasm

Hamza:

• Solved issues on sha512 PR, waiting for re-review
• Next, will implement sha512 for ints
• Notes for new devs
  • More comments in wat would be helpful
  • 8-byte words vs 4-byte words, block sizes in sha256 vs sha512

Brice:

• Merged latest changes from next into our stacks-core branch
• Renamed submodule from stacks-blockchain to stacks-core
• Began testing running a devnet using our code
  • Worked with Hugo and Ludo to make progress
  • Hit a wall waiting for further changes from stacks-core
• Reviewed PRs in clarity-wasm and stacks-core

🚘 Parking Lot Topics

[obycode]

Meeting Date (Dec 18, 2023)

📆 Agenda

• Celebrate 100% function implementation!! 🥳
• Status updates (all)

📝 Status Updates & Blockers, by IC

Hamza:

• SHA512 merged
• Documented SHA256 and SHA512

Cyle:

• Switching back to handle things at the block level instead of trying to refactor in stacks-core
• Made good progress and should have some news soon!

Hugo:

• Able to run the devnet with epoch 3
  • Reach the point where pox-4 is deployed
  • Won’t boot once config is switched to Nakamoto Neon
  • Will talk to Matt today

Chris:

• Fixed some issues in wasm-generator
• Started digging into neon-node
• Issue with Chainhook

Kris:

• Worked on map implementation
• Technical debt in setup

Anthony:

• Property testing framework merged
• String-utf8/int conversion
• Integer division bug fixed
• Next step: robustness, property testing

Brice:

• Implemented from-consensus-buff?
• Finished up map
• Fixed issues with errors from top-level expressions

🚘 Parking Lot Topics

[obycode]

Meeting Date (Jan 2, 2024)

📆 Agenda

• Happy new year! 🎆
• Status updates (all)

📝 Status Updates & Blockers, by IC

Kristoffer:

• Handling builtins in map, fold, and filter turned out to be more complex than anticipated, but initial implementation is done and in review
  • “Simple” words evaluate all args at once, then act on them
  • “Complex” words do unique things with the args (e.g. conditionally evaluate)
  • Finished classifying all of the words, and all works, with the exception of and/or
  • Doesn’t yet support iterating over buffers or strings with builtins

Anthony:

• Attempted to add wasm-opt pass to our compiler
  • Ran into some failures and investigating further
  • Really good results when it does work – significant reduction in binary size and huge optimizations
• Testing is-eq with property tests
  • Found some issues with complex types and fixing those

Chris:

• Working with benchmarks
• Helped Hamza to get the benchmarks running
• Will start working on bug #205 - accessing constant during initialization

Brice:

• Worked with Hugo to get the devnet functioning and released before Christmas
• Focused on stacks-core work over the holidays
• Will review Kris’s PR, then investigate reported bugs

🚘 Parking Lot Topics

[obycode]

Meeting Date (Jan 8, 2024)

📆 Agenda

• Status updates (all)

📝 Status Updates & Blockers, by IC

Anthony

• Debugging and writing property tests
  • is-eq and default-to
• Ideas for testing tuples and lists functions
• Will share some details to get help on this later

Hugo

• No big updates
• Seeing some issues on devnet not reliably switching to epoch 3.0
  • Seems like it might be an issue with stacking txs not making it in time (before prepare phase)
• Working on adding some UI to show pox info in devnet
• Should we rebase our devnet branch on the latest?

Kristoffer

• Got the remaining fixes for filter/fold/map implemented and merged
• Could use some better documentation around the limitations for which builtins can be used
• Starting with rehaul of testing
  • Run tests with both interpreter and clarity-wasm pipeline and compare the results

Chris

• Bug fixes in progress
• Benchmarking and profiling
  • Streamline the approach
  • Looking into improvements
  • Preparing a document

Hamza

• Working on issue update to simplify community #110
• Clarified some questions about error handling

Brice

• Found and fixed issue that arose from the managed testnet
• Found and fixed a clarinet issue
• Investigating another error found by devops when trying to run the node

🚘 Parking Lot Topics

-Anthony walked everyone through the property testing so that others can help

[obycode]

Meeting Date (Jan 16, 2024)

📆 Agenda

• Status updates (all)

📝 Status Updates & Blockers, by IC

Anthony

• Property tests: define-data-var, get-var
  • Found several bugs and fixed
  • One remaining issue, that seems to be a type-checker bug
• Spoke with Chris and Hamza about sharing the property testing work
  • Chris will write up issues summarizing the functions to test
• Met with Nikos (property test master)
  • Discussed model-based testing

Chris

• Discussed property testing with Anthony
• Started opening issues on GH
  • Trying to group them reasonably to make it easier to work on property tests within groups
• Working on property testing of index-of
• These issues will provide good metrics to share

Cyle

• Back from holidays
• Problem with long startup times
  • Implementing snapshots to be able to restart from some point

Kristoffer

• Finished up cross-checking
  • Found and fixed one bug (use of builtinnames)
• Will try to run old-school tests in cross-checker

Hugo

• Working on other Clarinet stuff at the moment
  • Devnet stops at some block height (64 or 65)
  • Not Nakamoto specific
  • Chainhook might be a suspect
• Goal to release Clarinet 2.2 this week and setup the Hiro Platform to use it

Hamza

• Error-handling and property tests
• Used cross-check method in property tests
• Working on missing types in property test framework (utf8 and principals)

Brice

• SIP review and discussion
• Stacks node work
• Node which is supposed to be booting from genesis using clarity-wasm has reached tip, but there must be an issue (given the issues that we are aware of which have been solved in the last week)
  • Will investigate and restart

🚘 Parking Lot Topics

[obycode]

Meeting Date (Jan 22, 2024)

📆 Agenda

• Status updates (all)

📝 Status Updates & Blockers, by IC

Anthony

• Fixed a bunch of bugs relating to reading/writing values from memory
• Fixed a bug with constant values
• Fixed an issue with types of if expression
• Next will choose an issue from the list of property testing

Hugo

• Still working on Clarinet v2.2 release
  • Revamping a bit how clarity-wasm will work in the console
  • Make it so that you can optionally run with only interpreter
  • Add details when there is an error to encourage user to open an issue
  • Issue when deploying the same contract twice (once with interpreter and once with clarity-wasm)

Kristoffer

• Running tests through crosscheck
• Found some minor issues
  • Will write up any minor issues found after submitting the PR
• Fixing major issues in between

Cyle

• Documentation and cleanup
• Implement the instrumentation of the databases to create a changelog of values added/updated/deleted

Brice

• Got always-wasm node running
  • Failed on genesis block due to errors in compiling bns.clar
  • Fixed an issue and opened another issue
• Removed unimplemented! usage from clar2wasm (ensured that things that need to be implemented are and otherwise replaced with proper errors)

🚘 Parking Lot Topics

[obycode]

Meeting Date (Jan 29, 2024)

📆 Agenda

• Status updates (all)

📝 Status Updates & Blockers, by IC

Kristoffer

• PR with converted tests and some other changes
• Setup the ignore of the crossprop tests - should setup the separate runner for this to speed up our CI testing
  • Reach out to Jesse for this

Anthony

• Writing more property tests and fixing type-checker issues
• Starting to think that we should’ve fixed the type-checker instead
  • Could we write a separate pass to fill in these types?
• concat has the same issue
• Needs help with writing these property tests
• Could there be an issue with introducing a new type that is out of range?

Cyle

• Looking into performance issues around oracle-v1 contract
  • Implemented tracing for the Clarity to help track down
  • Background - running into slow speeds when trying to run through the chainstate
  • Performance gains here will benefit testing and could benefit the chain

Hugo

• Releasing Clarinet 2.2 tomorrow
  • Two PRs in review
  • Includes clarity-wasm in devnet by changing the docker image and in simnet in clarinet console
  • Wasm on by default in console, shows error with link to open issue
  • Not on in clarinet check

Chris

• Focused on crossprop tests
• Finished 3 or 4 words and will open a PR soon
• Should bitwise functions be crossprop tested, given that they are already covered in the standard library tests

Hamza

• PR to fix use of expect and unwrap
• Issue with utf8 was a misunderstanding, resolved with help from Matt
  • Discrepancy in from-consensus-buff? method - issue from-consensus-buff? returns none when compiled  clarity-wasm#313
• Will continue work on Can't compile a clarity snippet with multiple principals clarity-wasm#274, related to issue A top level tuple triggers a panic clarity-wasm#305

Brice

• Still trying to get always-wasm and nakamoto-2 networks running smoothly
  • Fixed issues with boot contracts locally, but still seeing an issue in devnet
  • Often seeing errors that are unrelated to any clarity-wasm changes in these nodes’ logs
• Trying to get the cost-tracking work going, but it is more complicated than initially expected and haven’t been able to dedicate the time to it
  • Would like to schedule a meeting to discuss ideas and get help
• I’ll be needed for pox-4 work starting today
  • Will still be available for wasm support, but will need to focus on that for a bit

🚘 Parking Lot Topics

• Discuss property testing with Jesse - @csgui
• Schedule a meeting about cost-tracking for anyone interested - @obycode

[obycode]

Meeting Date (Feb 5, 2024)

📆 Agenda

• Status updates (all)

📝 Status Updates & Blockers, by IC

Hugo

• Clarinet released
  • Not really tested with devnet for clarity-wasm yet
  • Will setup a stable branch for this, based off of devnet-wasm
  • Have a stable branch for next
  • We should keep the “stable” image unchanged until we define a procedure to test it

Kristoffer

• Found a way to solve the issue with variadic functions that should be working
  • Not yet passing tests, but working on it
  • Should be able to wrap this up today
  • Adding tests to ensure the tricky cases are covered

Anthony

• PR merged about adding cross-property testing for sequence functions
• Took over tasks about principals and UTF-8
  • Finished with principals, PR waiting for review on stacks-core #4338
  • Will open PR on our repo after this one is merged

Chris

• Working with cross-prop testing
• PR Crossprop tests for bitwise and blockinfo clarity-wasm#309 to be finalized
  • Issue with two datastores (one for interpreter and one for clarity-wasm) causing differences in results
  • This is because of the block time that is simulated in these environments
  • We should either create one and deep clone it, or provide some way to pass the time in as a parameter

Hamza

• Working on dynamically growing wasm pages
  • Adding instructions using Walrus to grow the memory
  • Hitting an error before reaching the instructions to grow the memory
  • Will writeup the current strategy and the errors he is hitting for further discussion

Brice

• Reviewing PRs but otherwise focused on other Nakamoto tasks

🚘 Parking Lot Topics

[obycode]

Meeting Date (Feb 12, 2024)

📆 Agenda

• Status updates (all)

📝 Status Updates & Blockers, by IC

Anthony

• Fixes for principal merged
• Started adding support for string-utf8 property-testing values
• PR reviews and assisting others

Kristoffer

• Looking at the cost-tracking
  • Noticed there is not much testing (any?)
  • Refactoring to make it more testable (use a reference)
  • Remove the free cost tracker and instead use the trait
  • Thinking of basing these changes on the next branch
    • Maybe it should be develop

Chris

• Working on devops tasks to schedule property testing and update CI
  • This is now merged!
• More work to do for the cross-prop testing
• Question: should we increase the amount of property testing during normal CI? What is the target time?
• Can we increase the number of tests so that it runs for the majority of the time?

Cyle

• Working with DB testing and performance enhancements
• Working on merging a flag from next into clarity-wasm-next, but ran into some issues where it was unclear
• Will open some PRs to develop

Hamza

• Working on growing the wasm memory
  • Found a bug with the runtime memory growth (stack size)
  • Will continue to work on this and get input from Brice and Anthony

Hugo

• Stuck to update the clarity package until we get the clarity-wasm-next branch updated

🚘 Parking Lot Topics