Nicholas Tsim

Got the same thing when running from inside IDEA on Ubuntu 16.04.2. Seems to run fine on the command line though.

Same as above - `middleman init` is throwing the same error for me

Seeing this as well, but with general Reakit components that use ids e.g. `Disclosure` (not sure if it's all of them or just some). Seems to only happen on the...

Taking the advice from the blog post, you can implement the fix using something like this: ```jsx const Carousel = () => { const swiperRef = useRef(); return ( {...

Ran into a bit of an issue with the `putStream` method, which I think is related to Node 18. With the following code: ```ts const stream = fs.createReadStream('the path'); await...

Not sure what the issue would be. Unfortunately I'm not planning on looking into this on Windows anytime soon either as this was originally just a proof-of-concept for Linux. Obviously...

@Giorgi yes I meant that the exception was only being thrown when using the debugger. However, I've just tested with 0.10.1.2 and seems like everything is fine now! Thank you...

Apologies @Giorgi, but I messed up my test. Looks like this is actually still happening :disappointed: Could you re-open this?

@JMcDanielFbn @Giorgi Apologies for the delay getting back to you on this! I had the `duckdb` CLI binary on my PATH, but I didn't expect this to affect anything. I...

Yes, these exceptions only occur whilst debugging with named parameters. They don't occur when debugging with the question mark parameter workaround outlined above. I've also been using this with Dapper,...