Alex Watson

So I guess until this gets officially released, we can use it like this, correct? ``` [dependencies] askama = { git = "https://github.com/djc/askama.git", rev = "8142963", default-features = false, features...

Thank you for posting this solution. This was a serious problem for us. Almost made my own CRUD.

Having the same issue on ARM-64 MacOS with Python 3.11.0b3 ``` Traceback (most recent call last): File "/Users/alex/Code/Python/Flashcard/main.py", line 1, in from fastapi import FastAPI ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/alex/.pyenv/versions/3.11-dev/envs/notecards/lib/python3.11/site-packages/fastapi/__init__.py", line 7,...

After doing some research, it seems this memory leak has been an ongoing issue since 2019 (Jest 22) so wanted to consolidate some notes here for posterity. Past issues have...

Since this is a heap issue, maybe triggering garbage collection and de-referencing unused or global variables will also help fix? Look out for things that are leaving lots of memory...

Could the draft chapters live on their own feature branch? I am excited to continue reading based on the table of contents items.

 but in all seriousness, I have an easy workaround: First, `npm install --save-dev whatwg-fetch` .. then .. jest.config.js: ... setupFiles: ['/setupJest.js'], ... setupJest.js: ... import 'whatwg-fetch'; ... and then...

I had the same issue, while simply trying to connect. ``` Error: EISDIR: illegal operation on a directory, read at Object.fs.readSync (fs.js:656:19) at tryReadSync (fs.js:457:20) at Proxy.fs.readFileSync (fs.js:494:19) at Proxy.fs.readFileSync...