JohnHay

Results 10 comments of JohnHay

Any chance of a release coming out with Django 3.2 or higher support? FreeBSD already removed graphite-web from its ports/packages because of a lack of newer Django support.

I see I neglected to specify the browsers I used. I used firefox 91.0.1 and chromium 91.0.4472.164. Here are screenshots of their debug consoles: ![graphite-firefox](https://user-images.githubusercontent.com/10042088/130390628-f59a48ff-1af4-4e4f-ae3e-78e51adbb321.png) ![graphite-chrome](https://user-images.githubusercontent.com/10042088/130390630-7861ea6d-aada-42fd-8f55-ef9f53e0b4a6.png)

> **EDIT** > > I'm getting better results when I bypass the multi-auth loop by changing line 283 of ssh2.py to call on auth_password intead of auth_none. This seems like...

I also see it on FreeBSD with python 3.8.12: ``` Starting carbon. Starting carbon-cache (instance a) /usr/local/lib/python3.8/os.py:1023: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size...

Thank you. :-) Currently my driver compare them in the attach routine and print a message to the console if there is a difference.

I have now loaded the version 9 LitePcie firmware and still see a version mismatch on the SMA Selector. It is not an issue for me, so you do not...

Thank you. :-) I'm using it in the FreeBSD driver I'm busy with. I also have it working with the LitePCIe firmware. Adding support for that also made me wonder...

BTW It looks like the LitePcie TimeCardOS.bit was missed in the update.

I agree with the modular driver approach. But for that you need to get to the CoreList. :-) So my current understanding is roughly this: All the cards have a...

One thing I noticed in the updated linux driver is that the PCI_REVISION_ID can be used to distinguish between the LitePCIe and non-LitePCIe firmware. I did not realise that changed....