Robert Gabriel Jakabosky

aah. They rollback to the previous library version if the reload fails. Also they validate the library file sections and reload data in the sections. Seems it would be easier...

I might look into wrapping `cr.h` in a crate later. For now, versioning the library copy on each reload, hash checks, and leaking/forgetting the previous instance would help a lot.

@Boscop I ran into those same TLS destructor issues over a year ago https://github.com/fungos/cr/issues/35 while making a Rust binding for `cr.h: A Simple C Hot Reload Header-only Library`. See my...

@Ryan1729 @emoon Fixed in PR #14. The issue is that inotify is watching the file's `inode`. When the file is deleted the `inode` is gone. When a new file is...

FYI, the `cr-sys` crate can now build/run basic host & guest side code. Missing: - userdata pointer. Maybe change `cr-sys::Plugin` to `cr-sys::Plugin` - enums. Right now they are just raw...

Publish the first version of `cr-sys` (raw bindings) and `cr` (safe bindings). Reloading is working. Both crates have example host/guest. @fungos Rollback worked after a crash (de-reference null pointer). Be...

FYI, fixed the rollback + reload issue. Also Rust panics are caught and trigger a rollback. It seems setjmp/longjmp can work to recover from segfaults from unsafe Rust code, since...

I had this problem too and found a solution. The problem is caused by the default `date format` in `freetds`. The default format uses a ':' between the seconds and...

The permissions cli now correctly parse permissions from the docs.

We have our own Polkadot.js webapp here: https://mainnet-app.polymesh.network/#/explorer/query/4921857 The error you are seeing is with how the webapp tries to summarize POLYX transfer. We had added some extra fields to...