Glenn Matthys

I wasn't aware this was an actual security issue, my bad, I apologize.

I'm new to Netbox but I think I just came across this issue myself. Fresh install of version 4.4.4. API data for rear port: ```json HTTP 200 OK Allow: GET,...

I deleted the cable connections and redid it via Connections > Cables > Add: API data rear port: ```json HTTP 200 OK Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS Content-Type:...

The theory of operation of this library has completely changed between version 1 and 2... I downgraded back to 1.6.2 in the meantime.

Upgrade to the latest version and try again?

Any workaround without having to install a canvas renderer? Update, was able to unceremoniously work around this: ```javascript import * as scenegraph from 'vega-scenegraph'; import {View, parse} from 'vega'; function...

It's a common pattern for me to do something like ``` CREATE TABLE "test" ( ... "user_id" integer NOT NULL DEFAULT current_user_id(), ... ); ``` Often these are things that...

This worked for me: ```html ``` ```javascript import {nextTick} from 'vue'; export default { methods: { async fixFocus() { await nextTick(); this.$refs.select.$el.children[0].children[0].children[0].children[0].children[0].focus(); } } } ```

If I may add my 2 cents, if these callouts are developed, please make them more straightforward... I can barely wrap my head around the auth callout, the JWT inside...

This is an error from Firefox, not MediaMTX? I don't think MediaMTX can solve that. This is an error from Firefox, MediaMTX can't solve that: https://bugzilla.mozilla.org/show_bug.cgi?id=831926