-
As a first step for getting property testing in place for boot contracts, I think using the known-issues from PoX-2 (which precipitated the 2.1-2.4 forks) forms a quantifiable target for baseline prop…
-
Hey everyone, thanks in advanced for the help.
So I wanted to use some of the instrument detection models, and was not impressed by the results. I fed it a wav file that just had saxophone playing …
-
It's not obvious on where and how to access the `lcov.info` and `costs-reports.json` files after running `npm run test:report` in Clarinet.
This is what I would see currently after running the comm…
ECBSJ updated
2 months ago
-
I do have very large string values in my documents, so this is probably expected. Do I have any way of avoiding this ( I think some of the nodes could be > 64M, I know it sounds strange but basically …
-
### Description
Consider the following contract where I use `try!` as a variable name:
```clarity
(define-public (call-this (fail bool))
(let (
(try! (try-me fail))
)
(ok true)
…
-
Currently, Clarinet can add a project contract requirement by passing a principal contract in the cli like so:
`clarinet requirements add SP2PABAF9FTAJYNFZH93XENAJ8FVY99RRM50D2JG9.nft-trait`
Wha…
-
While testing out a new implementation of our VRF contract I ran into an error while testing, but `clarinet check` passes without issue. I could also reproduce the error in the console, but it's not c…
-
Hello! Thank you for your amazing remarkable job!
A little question here :) Sometimes I get this error:
```
{ statusCode: undefined,
body: undefined,
jsonBody: undefined,
thrown:
[Error: M…
-
**Describe the bug**
Calling the `getMapEntry` function in the Clarinet SDK for an entry that doesn't exist returns an error with the message "value not found" instead of returning `Cl.none`, as ex…
-
When running clarinet on Windows in a bash terminal (Git Bash), I am seeing the escape codes instead of the colors:
```
$ clarinet check
←[1;31merror←[0m: use of unresolved function 'addx'
←[1;3…