Edit last page of setup wizard

I know that you're not fond of colors, but in this case I think it's worth it -- if somebody loses their key file, their backups are useless.
Questions:

do you feel strongly about that "If you have multiple machines..." info?  I think that could be removed without losing anything vital for 99% of people.
I'm not certain we want to keep the final bit about "The same encryption...".  I think it's appropriate on the website, since people may be reading it before they sign up with Tarsnap (and that reinforces the notion that Tarsnap is very secure), but once somebody reaches this point in the GUI, they've already signed up.  Also, at the moment the final page of setup is a bit "busy" -- ignoring the logo, there's 5 different fonts/colors in use (title, normal text, link text, warning text, final aside).  We can't change the title or normal text, and I think it's worth keeping the different font/colors for the link and the warning.

EDIT: I just added a commits which make these changes.  If you prefer it without them, I'll rebase the history so that they were never added.
Old version:

New version:

Revised 2:

Oh, I forgot to add: one reason I put the URL as a separate QLabel is that %1 doesn't update if you visit that page twice.  i.e. if we used %1 and somebody registered with Tarsnap, saw the "setup complete" page, then clicked back to a previous page and used different registration info, they would still see the first keyfile.
I agree this is an extremely unlikely scenario, but I figured that I might as well move the URL into a separate QLabel just in case.  :)

I like these updates. Merged with squash.


Update for 1.21.1

Could you update the mod to 1.21.1? What would be really nice!
And btw great work, keep it up!

When I get home, I'll update it :)

The update should be available on Modrinth in a few minutes :)


Green version

Would you be open to a green dominate version of the scheme?
Campo Santo released a similar wallpaper:

Will happily make a pull request.

Really great idea! So unfortunately it's not possible to have settings for syntax themes. We probably need to push a second theme. I forked the red theme here. If you want, you can open a pr and add the green colors, otherwise I will look into it on the weekend! 🚀

🚢 https://atom.io/themes/firewatch-green-syntax


homekit status fault from 0 to 1

my log is filled with this
Apr 03 00:29:27 hbridge2 homebridge[30397]: [2018-4-3 00:29:27] [Hue] Hue color light 2: set homekit status fault from 0 to 1
Apr 03 00:29:47 hbridge2 homebridge[30397]: [2018-4-3 00:29:47] [Hue] Hue color light 2: set homekit status fault from 1 to 0
Apr 03 00:29:52 hbridge2 homebridge[30397]: [2018-4-3 00:29:52] [Hue] Hue color light 1: set homekit status fault from 1 to 0
Apr 03 00:31:02 hbridge2 homebridge[30397]: [2018-4-3 00:31:02] [Hue] Hue color light 1: set homekit status fault from 0 to 1
how can i get over this

See #187 or #214.

HI @ebaauw
I get those messages as well since some days, might have been to do with update to node.js LTS 16.13.2 and update of homebridge to 1.4.0 and homebridge hue to 0.13.35. other than that I did not change anything. any ideas why this is popping up on a minute base?
As recommended, I started HB in debug mode and this I get minute by minute:
[Hue] Bad LED Leiste: attr changed event: {"id":"3","lastannounced":null,"lastseen":"2022-01-23T12:00Z","manufacturername":"Philips","modelid":"5112.80","name":"Bad LED Leiste","swversion":"2.5.3_r55","type":"Dimmable light","uniqueid":"80:4b:50:ff:fe:b7:30:3e-01"}
[Hue] Bad LED Leiste: attr changed event: {"id":"3","lastannounced":null,"lastseen":"2022-01-23T12:01Z","manufacturername":"Philips","modelid":"5112.80","name":"Bad LED Leiste","swversion":"2.5.3_r55","type":"Dimmable light","uniqueid":"80:4b:50:ff:fe:b7:30:3e-01"}
And btw: thanks for your AMAZING work - all your HB plugins were insanely good & stable so far.

might have been to do with update to node.js LTS 16.13.2 and update of homebridge to 1.4.0 and homebridge hue to 0.13.35.

I seriously doubt that.

As recommended, I started HB in debug mode and this I get minute by minute:

There should be a state changed event with reachable becoming false or true, just before Homebridge Hue sets or clears Status Fault.

after going back from debug to normal mode, its not every minute but looking like this:

That’s because Status Fault is not linked to anything in the attr change event.

@ebaauw thanks for your support.
I just don't understand why I now get those messages, I did not add new accessories, I just updated the bridge and (I forgot to mention I updated to the latest stable deconz package & firmware).
Here another log with -d (and it continues like that):
[24/01/2022, 09:31:29] [Hue] Phoscon-GW: request 25: GET /sensors
[24/01/2022, 09:31:29] [Hue] Phoscon-GW: request 25: 200 OK
[24/01/2022, 09:31:29] [Hue] Phoscon-GW: request 26: GET /lights
[24/01/2022, 09:31:29] [Hue] Phoscon-GW: request 26: 200 OK
[24/01/2022, 09:31:34] [Hue] Phoscon-GW: request 27: GET /sensors
[24/01/2022, 09:31:34] [Hue] Phoscon-GW: request 27: 200 OK
[24/01/2022, 09:31:34] [Hue] Phoscon-GW: request 28: GET /lights
[24/01/2022, 09:31:34] [Hue] Phoscon-GW: request 28: 200 OK
[24/01/2022, 09:31:39] [Hue] Phoscon-GW: request 29: GET /sensors
[24/01/2022, 09:31:39] [Hue] Phoscon-GW: request 29: 200 OK
[24/01/2022, 09:31:39] [Hue] Phoscon-GW: request 30: GET /lights
[24/01/2022, 09:31:39] [Hue] Phoscon-GW: request 30: 200 OK
[24/01/2022, 09:31:44] [Hue] Phoscon-GW: request 31: GET /sensors
[24/01/2022, 09:31:44] [Hue] Phoscon-GW: request 31: 200 OK
[24/01/2022, 09:31:44] [Hue] Phoscon-GW: request 32: GET /lights
[24/01/2022, 09:31:44] [Hue] Phoscon-GW: request 32: 200 OK
[24/01/2022, 09:31:49] [Hue] Phoscon-GW: request 33: GET /sensors
[24/01/2022, 09:31:49] [Hue] Phoscon-GW: request 33: 200 OK
[24/01/2022, 09:31:49] [Hue] Phoscon-GW: request 34: GET /lights
[24/01/2022, 09:31:49] [Hue] Phoscon-GW: request 34: 200 OK
[24/01/2022, 09:31:54] [Hue] Phoscon-GW: request 35: GET /sensors
[24/01/2022, 09:31:54] [Hue] Phoscon-GW: request 35: 200 OK
[24/01/2022, 09:31:54] [Hue] Phoscon-GW: request 36: GET /lights
[24/01/2022, 09:31:54] [Hue] Phoscon-GW: request 36: 200 OK
[24/01/2022, 09:31:59] [Hue] Phoscon-GW: request 37: GET /sensors
[24/01/2022, 09:31:59] [Hue] Phoscon-GW: request 37: 200 OK
[24/01/2022, 09:31:59] [Hue] Phoscon-GW: request 38: GET /lights
[24/01/2022, 09:31:59] [Hue] Phoscon-GW: request 38: 200 OK
[24/01/2022, 09:32:04] [Hue] Phoscon-GW: request 39: GET /sensors
[24/01/2022, 09:32:04] [Hue] Phoscon-GW: request 39: 200 OK
[24/01/2022, 09:32:04] [Hue] Phoscon-GW: request 40: GET /lights
[24/01/2022, 09:32:04] [Hue] Phoscon-GW: request 40: 200 OK
[24/01/2022, 09:32:09] [Hue] Phoscon-GW: request 41: GET /sensors
[24/01/2022, 09:32:09] [Hue] Phoscon-GW: request 41: 200 OK
[24/01/2022, 09:32:09] [Hue] Phoscon-GW: request 42: GET /lights
[24/01/2022, 09:32:09] [Hue] Phoscon-GW: request 42: 200 OK
[24/01/2022, 09:32:14] [Hue] Phoscon-GW: request 43: GET /sensors
[24/01/2022, 09:32:14] [Hue] Phoscon-GW: request 43: 200 OK
[24/01/2022, 09:32:14] [Hue] Phoscon-GW: request 44: GET /lights
[24/01/2022, 09:32:14] [Hue] Phoscon-GW: request 44: 200 OK
[24/01/2022, 09:32:19] [Hue] Phoscon-GW: request 45: GET /sensors
[24/01/2022, 09:32:19] [Hue] Phoscon-GW: request 45: 200 OK
[24/01/2022, 09:32:19] [Hue] Phoscon-GW: request 46: GET /lights
[24/01/2022, 09:32:19] [Hue] Phoscon-GW: request 46: 200 OK
[24/01/2022, 09:32:20] [Hue] Bad LED Leiste: attr changed event: {"id":"3","lastannounced":null,"lastseen":"2022-01-24T08:32Z","manufacturername":"Philips","modelid":"5112.80","name":"Bad LED Leiste","swversion":"2.5.3_r55","type":"Dimmable light","uniqueid":"80:4b:50:ff:fe:b7:30:3e-01"}
[24/01/2022, 09:32:24] [Hue] Phoscon-GW: request 47: GET /sensors
[24/01/2022, 09:32:24] [Hue] Phoscon-GW: request 47: 200 OK
[24/01/2022, 09:32:24] [Hue] Phoscon-GW: request 48: GET /lights
[24/01/2022, 09:32:24] [Hue] Phoscon-GW: request 48: 200 OK
[24/01/2022, 09:32:29] [Hue] Phoscon-GW: request 49: GET /sensors
[24/01/2022, 09:32:29] [Hue] Phoscon-GW: request 49: 200 OK
[24/01/2022, 09:32:29] [Hue] Phoscon-GW: request 50: GET /lights
[24/01/2022, 09:32:29] [Hue] Phoscon-GW: request 50: 200 OK
[24/01/2022, 09:32:34] [Hue] Phoscon-GW: request 51: GET /sensors
[24/01/2022, 09:32:34] [Hue] Phoscon-GW: request 51: 200 OK
[24/01/2022, 09:32:34] [Hue] Phoscon-GW: request 52: GET /lights
[24/01/2022, 09:32:34] [Hue] Phoscon-GW: request 52: 200 OK
[24/01/2022, 09:32:39] [Hue] Phoscon-GW: request 53: GET /sensors
[24/01/2022, 09:32:39] [Hue] Phoscon-GW: request 53: 200 OK
[24/01/2022, 09:32:39] [Hue] Phoscon-GW: request 54: GET /lights
[24/01/2022, 09:32:39] [Hue] Phoscon-GW: request 54: 200 OK
[24/01/2022, 09:32:44] [Hue] Phoscon-GW: request 55: GET /sensors
[24/01/2022, 09:32:44] [Hue] Phoscon-GW: request 55: 200 OK
[24/01/2022, 09:32:44] [Hue] Phoscon-GW: request 56: GET /lights
[24/01/2022, 09:32:44] [Hue] Phoscon-GW: request 56: 200 OK
[24/01/2022, 09:32:49] [Hue] Phoscon-GW: request 57: GET /sensors
[24/01/2022, 09:32:49] [Hue] Phoscon-GW: request 57: 200 OK
[24/01/2022, 09:32:49] [Hue] Phoscon-GW: request 58: GET /lights
[24/01/2022, 09:32:49] [Hue] Phoscon-GW: request 58: 200 OK
[24/01/2022, 09:32:54] [Hue] Phoscon-GW: request 59: GET /sensors
[24/01/2022, 09:32:54] [Hue] Phoscon-GW: request 59: 200 OK
[24/01/2022, 09:32:54] [Hue] Phoscon-GW: request 60: GET /lights
[24/01/2022, 09:32:54] [Hue] Phoscon-GW: request 60: 200 OK
[24/01/2022, 09:32:59] [Hue] Phoscon-GW: request 61: GET /sensors
[24/01/2022, 09:32:59] [Hue] Phoscon-GW: request 61: 200 OK
[24/01/2022, 09:32:59] [Hue] Phoscon-GW: request 62: GET /lights
[24/01/2022, 09:32:59] [Hue] Phoscon-GW: request 62: 200 OK
[24/01/2022, 09:33:04] [Hue] Phoscon-GW: request 63: GET /sensors
[24/01/2022, 09:33:04] [Hue] Phoscon-GW: request 63: 200 OK
[24/01/2022, 09:33:04] [Hue] Phoscon-GW: request 64: GET /lights
[24/01/2022, 09:33:04] [Hue] Phoscon-GW: request 64: 200 OK
[24/01/2022, 09:33:09] [Hue] Phoscon-GW: request 65: GET /sensors
[24/01/2022, 09:33:09] [Hue] Phoscon-GW: request 65: 200 OK
[24/01/2022, 09:33:09] [Hue] Phoscon-GW: request 66: GET /lights
[24/01/2022, 09:33:09] [Hue] Phoscon-GW: request 66: 200 OK
[24/01/2022, 09:33:14] [Hue] Phoscon-GW: request 67: GET /sensors
[24/01/2022, 09:33:14] [Hue] Phoscon-GW: request 67: 200 OK
[24/01/2022, 09:33:14] [Hue] Phoscon-GW: request 68: GET /lights
[24/01/2022, 09:33:14] [Hue] Phoscon-GW: request 68: 200 OK
[24/01/2022, 09:33:19] [Hue] Phoscon-GW: request 69: GET /sensors
[24/01/2022, 09:33:19] [Hue] Phoscon-GW: request 69: 200 OK
[24/01/2022, 09:33:19] [Hue] Phoscon-GW: request 70: GET /lights
[24/01/2022, 09:33:19] [Hue] Phoscon-GW: request 70: 200 OK
[24/01/2022, 09:33:21] [Hue] Bad LED Leiste: attr changed event: {"id":"3","lastannounced":null,"lastseen":"2022-01-24T08:33Z","manufacturername":"Philips","modelid":"5112.80","name":"Bad LED Leiste","swversion":"2.5.3_r55","type":"Dimmable light","uniqueid":"80:4b:50:ff:fe:b7:30:3e-01"}
[24/01/2022, 09:33:24] [Hue] Phoscon-GW: request 71: GET /sensors
[24/01/2022, 09:33:24] [Hue] Phoscon-GW: request 71: 200 OK
[24/01/2022, 09:33:24] [Hue] Phoscon-GW: request 72: GET /lights
[24/01/2022, 09:33:24] [Hue] Phoscon-GW: request 72: 200 OK
[24/01/2022, 09:33:29] [Hue] Phoscon-GW: request 73: GET /sensors
[24/01/2022, 09:33:29] [Hue] Phoscon-GW: request 73: 200 OK
[24/01/2022, 09:33:29] [Hue] Phoscon-GW: request 74: GET /lights
[24/01/2022, 09:33:29] [Hue] Phoscon-GW: request 74: 200 OK
[24/01/2022, 09:33:34] [Hue] Phoscon-GW: request 75: GET /sensors
[24/01/2022, 09:33:34] [Hue] Phoscon-GW: request 75: 200 OK
[24/01/2022, 09:33:34] [Hue] Phoscon-GW: request 76: GET /lights
[24/01/2022, 09:33:34] [Hue] Phoscon-GW: request 76: 200 OK
[24/01/2022, 09:33:39] [Hue] Phoscon-GW: request 77: GET /sensors
[24/01/2022, 09:33:39] [Hue] Phoscon-GW: request 77: 200 OK
[24/01/2022, 09:33:39] [Hue] Phoscon-GW: request 78: GET /lights
[24/01/2022, 09:33:39] [Hue] Phoscon-GW: request 78: 200 OK
[24/01/2022, 09:33:44] [Hue] Phoscon-GW: request 79: GET /sensors
[24/01/2022, 09:33:44] [Hue] Phoscon-GW: request 79: 200 OK
[24/01/2022, 09:33:44] [Hue] Phoscon-GW: request 80: GET /lights
[24/01/2022, 09:33:44] [Hue] Phoscon-GW: request 80: 200 OK
[24/01/2022, 09:33:49] [Hue] Phoscon-GW: request 81: GET /sensors
[24/01/2022, 09:33:49] [Hue] Phoscon-GW: request 81: 200 OK
[24/01/2022, 09:33:49] [Hue] Phoscon-GW: request 82: GET /lights
[24/01/2022, 09:33:49] [Hue] Phoscon-GW: request 82: 200 OK
[24/01/2022, 09:33:54] [Hue] Phoscon-GW: request 83: GET /sensors
[24/01/2022, 09:33:54] [Hue] Phoscon-GW: request 83: 200 OK
[24/01/2022, 09:33:54] [Hue] Phoscon-GW: request 84: GET /lights
[24/01/2022, 09:33:54] [Hue] Phoscon-GW: request 84: 200 OK
[24/01/2022, 09:33:59] [Hue] Phoscon-GW: request 85: GET /sensors
[24/01/2022, 09:33:59] [Hue] Phoscon-GW: request 85: 200 OK
[24/01/2022, 09:33:59] [Hue] Phoscon-GW: request 86: GET /lights
[24/01/2022, 09:33:59] [Hue] Phoscon-GW: request 86: 200 OK
[24/01/2022, 09:34:04] [Hue] Phoscon-GW: request 87: GET /sensors
[24/01/2022, 09:34:04] [Hue] Phoscon-GW: request 87: 200 OK
[24/01/2022, 09:34:04] [Hue] Phoscon-GW: request 88: GET /lights
[24/01/2022, 09:34:04] [Hue] Phoscon-GW: request 88: 200 OK
[24/01/2022, 09:34:09] [Hue] Phoscon-GW: request 89: GET /sensors
[24/01/2022, 09:34:09] [Hue] Phoscon-GW: request 89: 200 OK
[24/01/2022, 09:34:09] [Hue] Phoscon-GW: request 90: GET /lights
[24/01/2022, 09:34:09] [Hue] Phoscon-GW: request 90: 200 OK
[24/01/2022, 09:34:14] [Hue] Phoscon-GW: request 91: GET /sensors
[24/01/2022, 09:34:14] [Hue] Phoscon-GW: request 91: 200 OK
[24/01/2022, 09:34:14] [Hue] Phoscon-GW: request 92: GET /lights
[24/01/2022, 09:34:14] [Hue] Phoscon-GW: request 92: 200 OK
[24/01/2022, 09:34:19] [Hue] Phoscon-GW: request 93: GET /sensors
[24/01/2022, 09:34:19] [Hue] Phoscon-GW: request 93: 200 OK
[24/01/2022, 09:34:19] [Hue] Phoscon-GW: request 94: GET /lights
[24/01/2022, 09:34:19] [Hue] Phoscon-GW: request 94: 200 OK
[24/01/2022, 09:34:21] [Hue] Bad LED Leiste: attr changed event: {"id":"3","lastannounced":null,"lastseen":"2022-01-24T08:34Z","manufacturername":"Philips","modelid":"5112.80","name":"Bad LED Leiste","swversion":"2.5.3_r55","type":"Dimmable light","uniqueid":"80:4b:50:ff:fe:b7:30:3e-01"}
[24/01/2022, 09:34:24] [Hue] Phoscon-GW: request 95: GET /sensors
[24/01/2022, 09:34:24] [Hue] Phoscon-GW: request 95: 200 OK
[24/01/2022, 09:34:24] [Hue] Phoscon-GW: request 96: GET /lights
[24/01/2022, 09:34:24] [Hue] Phoscon-GW: request 96: 200 OK
[24/01/2022, 09:34:29] [Hue] Phoscon-GW: request 97: GET /sensors
[24/01/2022, 09:34:29] [Hue] Phoscon-GW: request 97: 200 OK
[24/01/2022, 09:34:29] [Hue] Phoscon-GW: request 98: GET /lights
[24/01/2022, 09:34:29] [Hue] Phoscon-GW: request 98: 200 OK
[24/01/2022, 09:34:34] [Hue] Phoscon-GW: request 99: GET /sensors
[24/01/2022, 09:34:34] [Hue] Phoscon-GW: request 99: 200 OK
[24/01/2022, 09:34:34] [Hue] Phoscon-GW: request 100: GET /lights
[24/01/2022, 09:34:34] [Hue] Phoscon-GW: request 100: 200 OK
[24/01/2022, 09:34:39] [Hue] Phoscon-GW: request 101: GET /sensors
[24/01/2022, 09:34:39] [Hue] Phoscon-GW: request 101: 200 OK
[24/01/2022, 09:34:39] [Hue] Phoscon-GW: request 102: GET /lights
[24/01/2022, 09:34:39] [Hue] Phoscon-GW: request 102: 200 OK
[24/01/2022, 09:34:44] [Hue] Phoscon-GW: request 103: GET /sensors
[24/01/2022, 09:34:44] [Hue] Phoscon-GW: request 103: 200 OK
[24/01/2022, 09:34:44] [Hue] Phoscon-GW: request 104: GET /lights
[24/01/2022, 09:34:44] [Hue] Phoscon-GW: request 104: 200 OK
[24/01/2022, 09:34:49] [Hue] Phoscon-GW: request 105: GET /sensors
[24/01/2022, 09:34:49] [Hue] Phoscon-GW: request 105: 200 OK
[24/01/2022, 09:34:49] [Hue] Phoscon-GW: request 106: GET /lights
[24/01/2022, 09:34:49] [Hue] Phoscon-GW: request 106: 200 OK
[24/01/2022, 09:34:54] [Hue] Phoscon-GW: request 107: GET /sensors
[24/01/2022, 09:34:54] [Hue] Phoscon-GW: request 107: 200 OK
[24/01/2022, 09:34:54] [Hue] Phoscon-GW: request 108: GET /lights
[24/01/2022, 09:34:54] [Hue] Phoscon-GW: request 108: 200 OK
[24/01/2022, 09:34:59] [Hue] Phoscon-GW: request 109: GET /sensors
[24/01/2022, 09:34:59] [Hue] Phoscon-GW: request 109: 200 OK
[24/01/2022, 09:34:59] [Hue] Phoscon-GW: request 110: GET /lights
[24/01/2022, 09:34:59] [Hue] Phoscon-GW: request 110: 200 OK
[24/01/2022, 09:35:04] [Hue] Phoscon-GW: request 111: GET /sensors
[24/01/2022, 09:35:04] [Hue] Phoscon-GW: request 111: 200 OK
[24/01/2022, 09:35:04] [Hue] Phoscon-GW: request 112: GET /lights
[24/01/2022, 09:35:04] [Hue] Phoscon-GW: request 112: 200 OK
[24/01/2022, 09:35:09] [Hue] Phoscon-GW: request 113: GET /sensors
[24/01/2022, 09:35:09] [Hue] Phoscon-GW: request 113: 200 OK
[24/01/2022, 09:35:09] [Hue] Phoscon-GW: request 114: GET /lights
[24/01/2022, 09:35:09] [Hue] Phoscon-GW: request 114: 200 OK
[24/01/2022, 09:35:14] [Hue] Phoscon-GW: request 115: GET /sensors
[24/01/2022, 09:35:14] [Hue] Phoscon-GW: request 115: 200 OK
[24/01/2022, 09:35:14] [Hue] Phoscon-GW: request 116: GET /lights
[24/01/2022, 09:35:14] [Hue] Phoscon-GW: request 116: 200 OK
[24/01/2022, 09:35:19] [Hue] Phoscon-GW: request 117: GET /sensors
[24/01/2022, 09:35:19] [Hue] Phoscon-GW: request 117: 200 OK
[24/01/2022, 09:35:19] [Hue] Phoscon-GW: request 118: GET /lights
[24/01/2022, 09:35:19] [Hue] Phoscon-GW: request 118: 200 OK
[24/01/2022, 09:35:22] [Hue] Bad LED Leiste: attr changed event: {"id":"3","lastannounced":null,"lastseen":"2022-01-24T08:35Z","manufacturername":"Philips","modelid":"5112.80","name":"Bad LED Leiste","swversion":"2.5.3_r55","type":"Dimmable light","uniqueid":"80:4b:50:ff:fe:b7:30:3e-01"}
[24/01/2022, 09:35:24] [Hue] Phoscon-GW: request 119: GET /sensors
[24/01/2022, 09:35:24] [Hue] Phoscon-GW: request 119: 200 OK
[24/01/2022, 09:35:24] [Hue] Phoscon-GW: request 120: GET /lights
[24/01/2022, 09:35:24] [Hue] Phoscon-GW: request 120: 200 OK
[24/01/2022, 09:35:29] [Hue] Phoscon-GW: request 121: GET /sensors
[24/01/2022, 09:35:29] [Hue] Phoscon-GW: request 121: 200 OK
[24/01/2022, 09:35:29] [Hue] Phoscon-GW: request 122: GET /lights
[24/01/2022, 09:35:29] [Hue] Phoscon-GW: request 122: 200 OK
[24/01/2022, 09:35:34] [Hue] Phoscon-GW: request 123: GET /sensors
[24/01/2022, 09:35:34] [Hue] Phoscon-GW: request 123: 200 OK
[24/01/2022, 09:35:34] [Hue] Phoscon-GW: request 124: GET /lights
[24/01/2022, 09:35:34] [Hue] Phoscon-GW: request 124: 200 OK

I just don't understand why I now get those messages

You would have to ask deCONZ; as I said above, Homebridge Hue just copies the state reported by deCONZ.  deCONZ marks a light's reachable as false when it hasn't received any messages from the light for too long.  There could be a number of reasons for that:

Because the light has been powered down;
Because the light's firmware hangs and it no longer sends messages;
Because the coordinator has no route to the light;
Because the light has no route to the coordinator;
Because of radio interference (think WiFi, USB-3, DECT, Bluetooth, microwaves, ...).

For 2-4, power-cycling the light usually fixes the situation.  For 5, you should see Zigbee errors in the deCONZ log (see their Wiki).

thanks a lot I will investigate @ebaauw


Linter Fails

Bug description
I am just getting started with this repo and have identified a "clean up" task. I might just fix it myself, but since it's a cyclomatic complexity issue, is might not be a trivial fix.
To Reproduce

make dev
Fails

golangci-lint run --fix --timeout 10m
oidc.go:134:1: Function name: OIDCCallback, Cyclomatic Complexity: 22, Halstead Volume: 4757.77, Maintainability Index: 19 (maintidx)
func (h *Headscale) OIDCCallback(ctx *gin.Context) {
^
poll.go:34:1: Function name: PollNetMapHandler, Cyclomatic Complexity: 18, Halstead Volume: 5318.34, Maintainability Index: 19 (maintidx)
func (h *Headscale) PollNetMapHandler(ctx *gin.Context) {
^
poll.go:272:1: Function name: PollNetMapStream, Cyclomatic Complexity: 20, Halstead Volume: 6635.19, Maintainability Index: 16 (maintidx)
func (h *Headscale) PollNetMapStream(

Context info
No context required.

Hi, this is a new linter that was added to golangci-lint, I have disabled it in #366 , so should be gone soon, until we have time to fix the complexity.

great! closing in favor of https://github.com/juanfont/headscale/pull/366


Add headers (license & generated) to zz_setup

Description of your changes
adds the generated and license (from boilerplate.go.txt) to zz_setup.go.
The code to set these template variables already existed: https://github.com/upbound/upjet/blob/a41bb83a48292e9bacb85bc1e409a7fe3595c9e7/pkg/pipeline/setup.go#L89-L90
This PR only updates the template to also use these values.
I have:

[x] Read and followed Crossplane's [contribution process].
[ ] Run make reviewable to ensure this PR is ready for review.
[x] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested
evaluated with a custom boilerplate.go.txt for a custom provider.

@Henni, thanks for your contribution. We are in the process of moving the repo to the https://github.com/crossplane org and a fix for this issue has been implemented in this PR: https://github.com/upbound/upjet/pull/279/files#diff-e92c3fbe5e87809841306b1fcff7f01b0306e7ecbb3dbb0e323db188dad29b2c
I'll close this PR in favor of the above mentioned one.


Add WifiDirect Discovery and Connectivity

Allow you to view content hosted locally through wifi direct

Thanks! (I'll take a look tomorrow)

@cco3 fixed

OK, LGTM...passing on to @nondebug

@nondebug fixed

@nondebug fixed

lgtm once you make the above changes


Proposal: Disable the lstn in command in favor of lstn scan for now

It looks like the lstn in command is giving headhaches to some of our users.

Initially we thought about the lstn in command as our main entrypoint for repositories, that command is very interesting to execute because it goes in-depth with the scan by analysing all the transitive dependencies directly.
However to make it working properly we need to complete the work on https://github.com/listendev/erborist.
So I'm proposing to disable lstn in and suggest users to use lstn scan instead.
lstn scan gives the same kind of result of lstn in and takes the same input, the only difference is that it will not directly require all the transitive dependencies to the analysis request.
Once we finish the work on erborist we can re-enable the command and advise users on using it.
What do you all think?

Thanks for making this proposal @fntlnz! I was thinking over it last night - maybe in the documentation we can just add "coming soon" to lstn in? That way our users can see what we're actively working on. However, this can also signal to competitors what is coming next for us, if we wanted to keep it hidden. What does everyone else think?


Deploy addon as Firefox extension

Do you might want to upload this extension to the Firefox Addon Repository?
I can confirm this extension works with Firefox Version 66.0.1.
Firefox does only complain about a part of the manifest.json,
but it does not break the functionality and performance:
https://github.com/iamdiogo/DarkCloud/blob/eecaa000977dbbfcf971b93e65e6c22b0da69c42/manifest.json#L9
The warning is:
Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page.

EDIT: Also you would need to add an add-on id for the gecko engine, which Chrome should simply ignore:
  "applications": {
    "gecko": {
      "id": "{444a63a7-2655-4de6-828e-c4d9b194d54f}"
    }
  },

Thank you for all your great suggestions. I'll check this out later today and see what problems I might encounter while adding Firefox support.

Hey @Zocker1999NET , I've just added Firefox support by completely removing the persistent key.
It's published here: https://addons.mozilla.org/en-US/firefox/addon/darkcloud-original/
Thank you for pointing it out.

Thank you for uploading your addon for Firefox :)


Change Ignored Prototypes remove upstream chem combinations

About the PR
Removed upstream chemical combinations; this may cause issues; please report them.
Why / Balance
Admin Issues
Changelog
:cl:

remove: Removed upstream chemical combinations

Mess Tech needs the drinks.yml reactions as many of them are shared between upstream and CM13

This section should be removed. Most of our drinks are not upstream drinks. They are custom RMC drinks, so someone must add custom options for RMC if they need to be included, we should not be using the upstream ones.

Probably not a good idea unless someone wants to recreate the ENTIRE baystation chef content because I'm fairly certain they're just using their upstream's content for that

TLDR this will result in an extremely long delay for mess tech release if we don't make a compromise

We could keep the drinks; the only issue is that many of those recipes don't work anyway, and if they did, we should probably copy them out and put them in a separate rmc-controlled drinks.yml file. I didn't want to go through and remove each recipe individually and then check to see if it worked, mostly because I do not like screwing around with upstream files.

I was also working on mess-tech, but someone else took it over. I'm not sure who it was, but they should definitely be auditing this list then.


swift build -c release crashes on Linux

I haven't been able to dig deeper into this yet but it appears that building the package with -c release crashes the compiler:
# swift build -c release
swift: /home/buildnode/jenkins/workspace/oss-swift-5.0-package-linux-ubuntu-18_04/swift/lib/AST/Type.cpp:4079: swift::SILBoxType::SILBoxType(swift::ASTContext &, swift::SILLayout *, swift::SubstitutionMap): Assertion `Substitutions.isCanonical()' failed.
Stack dump:
0.	Program arguments: /usr/bin/swift -frontend -c /host/.build/checkouts/swift-gen/Sources/Gen/AnyRandomNumberGenerator.swift /host/.build/checkouts/swift-gen/Sources/Gen/Gen.swift /host/.build/checkouts/swift-gen/Sources/Gen/LCRNG.swift /host/.build/checkouts/swift-gen/Sources/Gen/UIKit.swift /host/.build/checkouts/swift-gen/Sources/Gen/Zip.swift -supplementary-output-file-map /tmp/supplementaryOutputs-dc6044 -target x86_64-unknown-linux -disable-objc-interop -sdk / -I /host/.build/checkouts/swift-gen/.build/x86_64-unknown-linux/release -module-cache-path /host/.build/checkouts/swift-gen/.build/x86_64-unknown-linux/release/ModuleCache -swift-version 5 -O -D SWIFT_PACKAGE -color-diagnostics -parse-as-library -module-name Gen -num-threads 4 -o /host/.build/checkouts/swift-gen/.build/x86_64-unknown-linux/release/Gen.build/AnyRandomNumberGenerator.swift.o -o /host/.build/checkouts/swift-gen/.build/x86_64-unknown-linux/release/Gen.build/Gen.swift.o -o /host/.build/checkouts/swift-gen/.build/x86_64-unknown-linux/release/Gen.build/LCRNG.swift.o -o /host/.build/checkouts/swift-gen/.build/x86_64-unknown-linux/release/Gen.build/UIKit.swift.o -o /host/.build/checkouts/swift-gen/.build/x86_64-unknown-linux/release/Gen.build/Zip.swift.o
1.	While running pass #25445 SILFunctionTransform "GenericSpecializer" on SILFunction "@globalinit_33_037C8324581EFD9286D2C4467C9955FB_func4".
 for declaration 0x7f51e30 (at /host/.build/checkouts/swift-gen/Sources/Gen/Gen.swift:508:10)
/usr/bin/swift[0x42420c4]
/usr/bin/swift[0x423fe4e]
/usr/bin/swift[0x4242282]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f10e53a3890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f10e3806e97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f10e3808801]
/lib/x86_64-linux-gnu/libc.so.6(+0x3039a)[0x7f10e37f839a]
/lib/x86_64-linux-gnu/libc.so.6(+0x30412)[0x7f10e37f8412]
/usr/bin/swift[0x18b8b0a]
/usr/bin/swift[0x17634d5]
/usr/bin/swift[0x18b9645]
/usr/bin/swift[0x18b6136]
/usr/bin/swift[0x18b4671]
/usr/bin/swift[0x18b4fa7]
/usr/bin/swift[0x12e4b58]
/usr/bin/swift[0x12debce]
/usr/bin/swift[0x12dec93]
/usr/bin/swift[0x122598d]
/usr/bin/swift[0x1228166]
/usr/bin/swift[0x1228eca]
/usr/bin/swift[0x12278ac]
/usr/bin/swift[0x1225bee]
/usr/bin/swift[0x12256ae]
/usr/bin/swift[0xfe57f9]
/usr/bin/swift[0xfe5588]
/usr/bin/swift[0xfe6d34]
/usr/bin/swift[0xf3f0a9]
/usr/bin/swift[0xe9a372]
/usr/bin/swift[0xe9b0e2]
/usr/bin/swift[0xe9c1ff]
/usr/bin/swift[0x5b5008]
/usr/bin/swift[0xea3fba]
/usr/bin/swift[0x4c19f1]
/usr/bin/swift[0x4bd809]
/usr/bin/swift[0x46e670]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f10e37e9b97]
/usr/bin/swift[0x46ca8a]
<unknown>:0: error: unable to execute command: Aborted
<unknown>:0: error: compile command failed due to signal 6 (use -v to see invocation)

# swift build
[1/1] Compiling Swift Module 'Gen' (5 sources)
#

Posting it here but I wonder if that's not something for the swift bug reporter instead? What do you think?

This is revision b5e9f0130dcf1ba3dcbb2a64c322e1556ca71eca

Oof, that looks bad. Are you able to still reproduce this? There have been a lot of changes to Swift/Linux lately that hopefully it's good now!

Unfortunately I can't test this in the project where it occurred right now, because one of my other dependencies keeps me on 5.0 on Linux.
I'll have a look to try and reproduce it with this project here itself.

I've just opened a PR showing the issue: https://github.com/pointfreeco/swift-gen/pull/9
Not a PR in the sense that it fixes it, I'm afraid :)

Think we're good to finally close this. Thanks Sven!


[Bug]: Cloudflare tunnels option unavailable on localhost

Error Message and Logs
None
Steps to Reproduce

View server options on localhost server

Example Repository URL
No response
Coolify Version
V4.0.0-beta-360
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian bookworm 12.7
Additional Information
I don’t know if this is a bug, I run coolify on my RPI 4 and have local ssh access. I want to have ability to generate a domain powered by cloudflare tunnels automatically. I can’t do port forwarding.

@brrock not sure what your issue is here:
create cf tunnel
point your domains/wildcard to the tunnel
in coolify
add cf tunnel template and add cf token to env variables
set wildcard domain to be your apex domain

Could this be added to docs?

And does it work when I click generate domain in coolify

@brrock if you have added a wildcard tunnel + dns entry, as well as set your wildcard domain in coolify, then yes any url you generate would just automatically work

Thanks so much appreciate


Syntax for shaders

Some time ago, when I tried vulkano, the way to define shaders was just inside glsl files.
The way to write them now using the Dummy struct seems a bit weird.
Why can't you just use a macro like this:
vulkano_shader!("compute"
#version 450
void main() {})

There's no way to provide this syntax in stable Rust today.

I thought so. I hope this will become available some time.

@tomaka Have you seen https://github.com/dtolnay/proc-macro-hack ?

Fixed by https://github.com/vulkano-rs/vulkano/commit/494a0c30c87e1362fc5e4dce8a403016e5ad4e0a


Async methods with @method

Am I missing something or is it not possible to decorate async methods with @method? The wrapped method here is not marked async:
https://github.com/altdesktop/python-dbus-next/blob/master/dbus_next/service.py#L90
Should be easy to check, whether fn is a coroutine or not and then either provide an async or normal version of wrapped. Want a PR?

It is already possible using the aio MessageBus. If you are curious why: https://github.com/altdesktop/python-dbus-next/blob/ab566e16a71bfc9d7e0d29676aa459ec060e72c5/dbus_next/aio/message_bus.py#L345


feat(plugin-git): add collect of co-authors

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Provide a description in this PR that addresses what the PR is solving. If this PR is going to solve an existing issue, please reference the issue (e.g. close #123).

What is the purpose of this pull request?

[ ] Bug fix
[x] New feature
[ ] Other

Description

The commit body may include co-author information:
Co-authored-by: xxxx<EMAIL_ADDRESS>Co-authored-by: xxxx<EMAIL_ADDRESS>
They should also be collected as contributors and changlog.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 58.438%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
1207

Relevant Lines:
1853

💛  - Coveralls


"Revert to using default colors" doesn't change summary table colors back

After switching to "accessible colors" in a search result page summary table doesn't revert to colors by clicking "default colors", but other tables do.

The summary table was removed recently due to bugginess, though it's re-enabled on the new beta site (https://beta.caniuse.com) where this issue does not exist.


Add CLI option to customize name of outputted build folder [Feature Request]

While using this tool, I have noticed that the name of the outputted build folder is always "build" and cannot be customized by regular means (i.e. through command options), as a result, I was wondering if a new CLI option could be added to modify the name of the outputted build folder?

Since issue #178 has been resolved, this issue is pretty much redundant, as a result, I will be closing it.
Thanks for taking a look at these issues and resolving them.


NAS-124274 / 24.04 / add 2nd -s to show interface errors

Adding a 2nd -s also reports the error statistics for the network interfaces. This has proven to be useful information on a customer system.

Jira URL: https://ixsystems.atlassian.net/browse/NAS-124274

Sorry, manipulated the wrong PR.


Missing contactPickerView parameter in all delegate methods

A parameter that contains a reference to a sender (an instance of THContactPickerDelegate) is missing in all delegate methods. This violates both the best practice for delegate pattern and makes it difficult to handle multiple THContactPickerView instances in one single delegate.
For example when you have multiple contact pickers on one screen and all of them have the same delegate which is a view controller.
Proposed THContactPickerDelegate protocol should look like this:
@protocol THContactPickerDelegate <NSObject>

- (void)contactPicker:(THContactPickerView *)contactPickerView textViewDidChangeToText:(NSString *)text;
- (void)contactPicker:(THContactPickerView *)contactPickerView didRemoveContact:(id)contact;
- (void)contactPickerDidResize:(THContactPickerView *)contactPickerView;
- (BOOL)contactPicker:(THContactPickerView *)contactPickerView textFieldShouldReturn:(UITextField *)textField;

@end

Hi @tomaskraina, I am in agreement with these recommendations and what you bring up in #34. If you have the time to create a Pull Request with these updates that would be great! Otherwise, it will take some time for me to get to this. Thanks


Bug (0.6): Adding subusers fails

Pretty self-explanatory. I'm trying to add a sub-user for a specific Minecraft server. I select every single permission available and use an email address of a user that already exists as a user (this also fails when I select a user that doesn't exist) and receive the following error: An unknown error occured while attempting to add a new subuser.

Already resolved by https://github.com/Pterodactyl/Panel/commit/3240601d036817fcc83729a7f48eea2b28fc1a67


Trailing comment after suppression

It would be helpful for migrations to be able to identify a new batch of nulls that need suppressing with the auto-suppresser until they can be addressed. It would be useful to be able to add a trailing line comment with a configurable message
@SuppressWarnings("NullAway") // T1234567
public void doSomething() {
  foo.bar();
}

@jbarr21 How does this look? https://github.com/uber/NullAway/pull/213/files#diff-7f652d10adf0edc2f1c37da1eb1ee9cbR36 (See test case)
It will actually look like:
@SuppressWarnings("NullAway") /* T1234567 */ public void doSomething() {
  foo.bar();
}

Or:
@SuppressWarnings("NullAway") /* T1234567 */
public void doSomething() {
  foo.bar();
}

After Google Java Format (using /*...*/ because matching indentation was a pain otherwise).

Landed. Let me know if you want us to cut a release. We will likely do so anyways in a few days to incorporate some JarInfer changes, but if it helps you guys to have it sooner, it wouldn't be hard to do another release with just this change.

that timeframe sounds good to me

Closing as I think this is done


News Feed plugin does not display tweets

Type
Incorrect behavior
Operating System
Linux
OS Version
Manjaro Linux
Bug description
I would guess this is due to a change on Twitter's side. They've made breaking changes to search and API access several times over the past few months.
Screenshots or videos

RuneLite version
RuneLite version: <IP_ADDRESS>
Launcher version: 2.6.3
Logs
No response

Elon made the Twitter API cost money.

Twitter has revoked our API key. We have decided to just remove the panel completely, since it is now only useful for RL and OSRS news, but both have separate/better sources.


placeholder: use case enabling/disabling intra-EVC and inter-EVC but without links convergence yet

This is just a placeholder to inform when these use cases would be ready, just so they can be incrementally used.

This one here will be available by the next week or so.


Failed to run openssl test after revision 22cef4e (Split test/recipes/03_test_internal.t into individual tests) on Windows.

Hi,
I tried to build openssl using VS2015 update 3 on Windows. I noticed that openssl test failed to run after revision 22cef4e (Split test/recipes/03_test_internal.t into individual tests). The following is the steps I used to build and run test for openssl:

git clone https://github.com/openssl/openssl D:\openssl\src
cd D:\openssl\src
perl Configure VC-WIN32
nmake clean
where cl.exe
nmake
nmake test

Here is the error message:
[executing command] nmake test
Microsoft (R) Program Maintenance Utility Version 14.10.25113.0
Copyright (C) Microsoft Corporation.  All rights reserved.
set SRCTOP=.
set BLDTOP=.
set PERL=C:\Perl\bin\perl.exe
set OPENSSL_DEBUG_MEMORY=on
"C:\Perl\bin\perl.exe" ".\test\run_tests.pl"
test\recipes\01-test_abort.t ............... ok
test\recipes\01-test_sanity.t .............. ok
test\recipes\01-test_symbol_presence.t ..... ok
test\recipes\02-test_ordinals.t ............ ok
test\recipes\03-test_exdata.t .............. ok
Bailout called.  Further testing stopped:  Must run setup() first
FAILED--Further testing stopped: Must run setup() first
NMAKE : fatal error U1077: 'C:\Perl\bin\perl.exe' : return code '0xff'
Stop.
Could you please take a look at this? Thanks!

I've ran into it yesterday and it's not addressed in b3068d0ac48c827403115a3b5cbc3655243e2cf0. Thanks for report.


Add members to a group: remove duplicates before posting the edit

Otherwise the API doesn't let you send repeated members.

Does this refer to add_members_to_group? Because we remove duplicates here: https://github.com/openreview/openreview-py/blob/ea7ae8dc08d7ffec267a92e0ce996cf28a1c8e45/openreview/api/client.py#L1619
Is the error in the else? In which scenarios do groups do not have invitations?


"error generating report" when Grafana API exceed 30 seconds to respond

as mentioned in the title i have some dashboards that takes time to get the time series. when the request exceed 30 seconds "error generating report" occur with 500 internalserver error.
grafana logs : level=error msg="error generating report" err="error rendering PNGs in parallel for dashboard X : error executing request for Y : net/http: request canceled (Client.Timeout exceeded while awaiting headers)
i tried to increase the timeout in "pkg/plugin/config/settings.go"
HTTPClientOptions: httpclient.Options{
			Timeouts: &httpclient.TimeoutOptions{
				Timeout: 120 * time.Second,
			},
			TLS: &httpclient.TLSOptions{
				InsecureSkipVerify: false,
			},

but the moment i edit the plugin and install it, it stop working.

Hello @chiheb22
An error like level=error msg="error generating report" err="error rendering PNGs in parallel for dashboard X : error executing request for Y : net/http: request canceled (Client.Timeout exceeded while awaiting headers) means that your plugin is not able to reach Grafana API. Can you post me logs to see at which address that the plugin is trying to reach Grafana API? If you did not configure anything, it will attempt to reach on localhost:3000 on bare-metal deployments. If your Grafana is not reachable on this address, you need to set appUrl where Grafana API is reachable

Ok, I see. If it fails in the step where it fetches PNGs of panels, a quick fix would be to set timeout: 120 in the provisioning config file of plugin and restart Grafana. So, a basic provisioning file would be as follows:
apiVersion: 1

apps:
  - type: mahendrapaipuri-dashboardreporter-app
    org_id: 1
    org_name: Main Org.
    disabled: false
    jsonData:
     timeout: 120 # in seconds

and it would set timeout as 120 seconds to HTTP client. This is not documented but I will do it as it can be useful. Could you try this approach and see if it works for your case?

yes it worked. thank you


Destructors not being linked correctly to RS networks.

Issue description:
Before getting my crash (problem has been posted in a separate issue), I was unable to add destructors to the network, even though they were all connected.
What happens:
Inserting a lot of destructors do not work, you have to insert them either one-by-one or in small amounts.
What you expected to happen:
Adding destructors to work correctly.
Steps to reproduce:

Make a long array of connected destructors (in my case it was around 64 destructors)
Link these destructors to a RS network (in my case, I used a cable).
Destructors should not work at all in this step (they won't be breaking any block, I mean.)

Version (make sure you are on the latest version before reporting):

Minecraft: 1.12.2
Forge: <IP_ADDRESS>15
Refined Storage: 1.6.12

Does this issue occur on a server? [yes/no] not tested.
I believe it has a connection to the https://github.com/raoulvdberge/refinedstorage/issues/2221 issue. Maybe breaking the destructors that were not correctly linked causes the crash? I'll look into that soon when I have time.

I guess it is linked to your linked issue.


"Work with Intrastat reporting" article - "Fixed assets reporting" section typo

There is probably typo in Work with Intrastat reporting, section Fixed assets reporting (link).
In both of points, there is the text:

The FA Posting Type in the VAT Ledger Entry field is....

Shouldn't that be something like:
The FA Posting Type field in the FA Ledger Entry is...??

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 783e169b-4554-816f-2a7d-7165277419d4
Version Independent ID: 783e169b-4554-816f-2a7d-7165277419d4
Content: Work with Intrastat reporting - Business Central
Content Source: business-central/finance-how-report-intrastat.md
Service: dynamics-365-business-central
GitHub Login: @altotovi
Microsoft Alias: altotovi

Thanks, we changed that.
From: RadoArvay @.>
Sent: Monday, April 8, 2024 9:32 AM
To: MicrosoftDocs/dynamics365smb-docs @.>
Cc: Mention @.***>
Subject: [MicrosoftDocs/dynamics365smb-docs] "Work with Intrastat reporting" article - "Fixed assets reporting" section typo (Issue #954)
There is probably typo in Work with Intrastat reporting, section Fixed assets reporting (link)https://learn.microsoft.com/en-us/dynamics365/business-central/finance-how-report-intrastat#fixed-assets-reporting.
In both of points, there is the text:
The FA Posting Type in the VAT Ledger Entry field is....
Shouldn't that be something like:
The FA Posting Type field in the FA Ledger Entry is...??

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 783e169b-4554-816f-2a7d-7165277419d4
Version Independent ID: 783e169b-4554-816f-2a7d-7165277419d4
Content: Work with Intrastat reporting - Business Centralhttps://learn.microsoft.com/en-us/dynamics365/business-central/finance-how-report-intrastat
Content Source: business-central/finance-how-report-intrastat.mdhttps://github.com/MicrosoftDocs/dynamics365smb-docs/blob/main/business-central/finance-how-report-intrastat.md
Service: dynamics-365-business-central
GitHub Login: @altotovihttps://github.com/altotovi
Microsoft Alias: altotovi

—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/dynamics365smb-docs/issues/954 or unsubscribehttps://github.com/notifications/unsubscribe-auth/APYZX4IJR53ZY7G6YEEQPUDY4JBVZBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJLJONZXKZNENZQW2ZNLORUHEZLBMRPXI6LQMWBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTLDTOVRGUZLDORPXI6LQMWSUS43TOVS2M5DPOBUWG44SQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKBZGE2DKNRTGAYIFJDUPFYGLJLJONZXKZNFOZQWY5LFVIZDEMZQGQ3TINRXGGTXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Dev-8923 Markup Include Memory Leak

Scenario: In Cove Editor running on your local environment, Select Dashboard, Select some Data set, drag and drop a markup include section onto the visualization panel. Open the Editor.

Open the browser console and find the file packages/dashboard/CdcDashboardComponent.
put a breakpoint in the updateChildConfig function.

Expected you should not be on an infinite loop.

This one has been closed. A different PR is being used.


Proxy server?

Is there any way to make this work with a proxy server that requires authentication?

I found this while searching for a way to do it.  I know very little about java so please excuse my ignorance.

When a proxy server requires authentication, it responds to connection requests with a credential request.  In Java, this is handled by setting a default authenticator.  There are numerous authentication types that are supported by Java.  In this example, we will be using a simple username and password authenticator.
Add the following code to your client and initialize the proxy authenticator before creating any connections:

private void initializeProxyAuthenticator() {
    final String proxyUser = System.getProperty("http.proxyUser");
    final String proxyPassword = System.getProperty("http.proxyPassword");

    if (proxyUser != null && proxyPassword != null) {
        Authenticator.setDefault(
          new Authenticator() {
            public PasswordAuthentication getPasswordAuthentication() {
              return new PasswordAuthentication(
                proxyUser, proxyPassword.toCharArray()
              );
            }
          }
        );
    }
}

Finally, set the following Java system properties:

-Dhttp.proxyUser=<proxy user>
-Dhttp.proxyPassword=<proxy password>

https://blogs.oracle.com/wssfc/handling-proxy-server-authentication-requests-in-java
https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html

Hmm. I was about to write "just set your system properties for your proxy and you should be all set" but in this case, SSLTest isn't using Http(s)URLConnection which would use these proxy system properties. SSLTest uses direct sockets, so a proxy isn't directly-supported.
This will take some thinking. I'm not excited about the prospect of implementing the proxy protocol in SSLTest, even though it is a fairly simple protocol.

Could you please check the section on "SOCKS" here and let me know if setting those system properties works for you? https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html

Were you ever able to check out the use of SOCKS proxy from Java, Eric?

It's been a year with no response. Closing this issue.


[sw, rom_ext_signer] Add minimal rustfmt configuration file

This PR makes sure that lines over 80 characters are split.
Please note that toolchain removal commit is a duplicate of another PR, and one of them will have to be rebased dependent on which lands first.

Are all of the source file changes a result of applying the formatting rules?

Are all of the source file changes a result of applying the formatting rules?

Yes, just cargo fmt

Could you also open an issue (and/or attempt to address it directly) to add a rust lint check to CI?

Can do both, thanks!


fix: security issue with yaml v3

@antonioiubatti93  The link is broken

@RemiMattheyDoret don't know if you've got access (now you should), it's basically the one under the Security in the top window bar

Thanks for the screenshot!


We are looking to get the #EXT-X-PROGRAM-DATE-TIME  item from the playlist.  And seem to be able to get them from the "FRAG_LOADED" event.
Having a hard time seeing where to get them from the-
 const hlsInstance = this.player.getInternalPlayer();

thanks
MJD

Hey @MDrooker, you’re almost there..
I would wait for onReady, then use getInternalPlayer and manually attach to the events:
class App extends Component {
  onPlayerReady = () => {
    const hlsInstance = this.player.getInternalPlayer()
    // Note that we can assume we have the `Hls` global here
    // as the player should be ready at this point
    hlsInstance.on(window.Hls.Events.FRAG_LOADED, data => {
      console.log('FRAG_LOADED', data))
    })
  }
  ref = player => {
    this.player = player
  }
  render() {
    return (
      <div>
        <ReactPlayer
          ref={this.ref}
          url='http://example.com/stream.m3u8'
          playing
          controls
          onReady={this.onPlayerReady}
        />
      </div>
    );
  }
}

I've just taken the on event binding syntax from the example in the hls.js readme. Not entirely sure if this will work as is but hopefully points you in the right direction?

Thanks @CookPete for the response-
It seems the hlsInstance variable points to the  DOM element.  Not the actual HLSJS instance.
const hlsInstance = this.player.getInternalPlayer()

Has the value of -
<video preload="auto" controls="" style="width: 100%; height: 100%;" src="blob:http://localhost:5051/bc703f06-e741-48d9-a9c1-aeaa3d31b710"></video>

So 'on' isnt available.
Could there be some option I am missing?

Sorry @MDrooker, you're right. Instead of
const hlsInstance = this.player.getInternalPlayer()

it should be
const hlsInstance = this.player.player.player.hls

Yes, player.player.player is ridiculous, but you are going through 3 internal levels of player components ReactPlayer > Player > FilePlayer to get to the instance of FilePlayer which has hls set on it. I should probably make this nicer.

@CookPete-
Worked like a champ!
Seeing the events flow.
BTW-
In your sample app-
If you do use this syntax-
onError={(e, data) => this.onError(e, data)}

the data return from HLS gives you the actual error from the library.  That may help someone else.

Note that you can now use
const hlsInstance = this.player.getInternalPlayer('hls')

instead of
const hlsInstance = this.player.player.player.hls

@cookpete the onReady callback is invoked after some HLS events have already occurred (e.g. FRAG_CHANGED). Could an onHlsInit callback be added that would run immediately after new Hls(hlsOptions) ? I am happy to make the PR.
Or is there already a way to do this?


python27Packages.dash-core-components: 1.10.2 -> 1.12.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python27Packages.dash-core-components is: "A dash component starter pack"
meta.homepage for python27Packages.dash-core-components is: "https://dash.plot.ly/dash-core-components"
meta.changelog for python27Packages.dash-core-components is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.12.1 with grep in /nix/store/wrwf0yb7dg48wpyshcxgx4m8rj7c3c3a-python2.7-dash_core_components-1.12.1

directory tree listing: https://gist.github.com/a918c546bcf7eaffbbe270c60b3f64c6

du listing: https://gist.github.com/f8ff3a24c2857af0f3925fd113a1c753

Rebuild report (if merged into master) (click to expand)

24 total rebuild path(s)

6 package rebuild(s)

6 x86_64-linux rebuild(s)
6 i686-linux rebuild(s)
6 x86_64-darwin rebuild(s)
6 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python27Packages.dash
python27Packages.dash-core-components
python37Packages.dash
python37Packages.dash-core-components
python38Packages.dash
python38Packages.dash-core-components

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wrwf0yb7dg48wpyshcxgx4m8rj7c3c3a-python2.7-dash_core_components-1.12.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python27Packages.dash-core-components https://github.com/r-ryantm/nixpkgs/archive/d0c688a5ffc3df36e0462a4226d7c210b1fe9feb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wrwf0yb7dg48wpyshcxgx4m8rj7c3c3a-python2.7-dash_core_components-1.12.1
ls -la /nix/store/wrwf0yb7dg48wpyshcxgx4m8rj7c3c3a-python2.7-dash_core_components-1.12.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

3 packages failed to build:

python27Packages.dash
python37Packages.dash
python38Packages.dash

3 packages built:

python27Packages.dash-core-components
python37Packages.dash-core-components
python38Packages.dash-core-components

Maintainer pings
cc @antoinerg for testing.

superseded by #99031


Fixed markdown violations.

Purpose
Fixed markdown violations for better readability in accordance with markdown linter/best-practices.
Does this introduce a breaking change?

[ ] Yes
[X ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[X ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code
N/A

Test the code
N/A

What to Check
Verify that the following are valid

Markdown formatting.

Other Information

thanks for the improvements


Change Arrow extension type and metadata prefixes

We now register extension types as tenzir.ip, tenzir.subnet, and tenzir.enumeration instead of vast.address, vast.subnet, and vast.enumeration, respectively. Type metadata now has a Tenzir: prefix instead of a VAST: prefix.
The change is mostly backwards compatible. The old type names and prefixes are still supported. However, reading old Apache Feather V2 and Apache Parquet inside the database directory files using the Python bindings will not work until a tenzir-ctl rebuild --all was run.

I talked with @tobim about the need of a full rebuild. Is this really needed?

If you want to read the files using our Python Arrow extension types, then yes, otherwise no.


Updated CI image to include JDK-8/11/17 distributions, kept JDK-14 as the default one

Signed-off-by: Andriy Redko<EMAIL_ADDRESS>Description
Updated CI image to include JDK-8/11/17 distributions, kept JDK-14 as the default one so the 1.x branches will continue to build properly.
declare -x JAVA11_HOME="/opt/java/openjdk-11"
declare -x JAVA14_HOME="/usr/lib/jvm/adoptopenjdk-14-hotspot"
declare -x JAVA17_HOME="/opt/java/openjdk-17"
declare -x JAVA8_HOME="/opt/java/openjdk-8"
declare -x JAVA_HOME="/usr/lib/jvm/adoptopenjdk-14-hotspot"

Issues Resolved
Closes https://github.com/opensearch-project/opensearch-build/issues/732, part of https://github.com/opensearch-project/OpenSearch/issues/1351
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@peterzhuamazon could you please take a look? Thank you!
@dblock sadly we cannot cut off JDK-14 in one shot (we will break 1.x builds due to https://bugs.openjdk.java.net/browse/JDK-8209058) but with new CI images we could set JAVA_HOME from build manifests.

Next question, why aren't we installing the other JDKs with yum install adoptopenjdk-... as well? Does it not support side-by-side installations?

A bit relates to previous comments, Adoptium at this moment does not have CentOS repositories (I didn't find any) and the recommended way to install distributions is to use archives.

Next question, why aren't we installing the other JDKs with yum install adoptopenjdk-... as well? Does it not support side-by-side installations?

A bit relates to previous comments, Adoptium at this moment does not have CentOS repositories (I didn't find any) and the recommended way to install distributions is to use archives.

Thanks, makes sense.

@dblock just played with sdk-man, sadly there is no JDK-14 distributions anymore (AdoptOpenJDK is gone as a source) available. So we could only install JDK 8/11/17 from Adoptium. I will prepare the change and wait for @peterzhuamazon @bbarani feedback regarding their preferences.


Update default output of nuget spec command

licenseUrl is deprecated, and other changes were made recently to how nuget spec works (available as of 5.3)

Docs Build status updates of commit 5c328a7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/quickstart/create-and-publish-a-package-using-visual-studio-net-framework.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


add updateMax method

There were a problem when updating the Max value for the gauge, the function updateMax()  which call the setMaxValue() function in gauge-svg was missed.

Sadly, this will not fix the issue, because gauge-svg method for updating max value doesn't update gauge itself. I have created pull request to fix that (https://github.com/naikus/svg-gauge/pull/61). Afterwards, i will create also pull request to fix it here (along with tests)


Optional blue line request

I wish it was possible to disable the blue line pointing to the given track. I find it rather distracting. Maybe you could make it an optional setting?

Added this as a setting in a pull request, you can download the file from there for now and test if everything´s ok and potentially give feedback.

Hi,
Yes, perfect!
If I should nitpick, the text box size could be reduced by 50%. But that's
my personal opinion. People might like how it is right now.
Thank you!
Best regards,
Jonny Jorgensen
On Fri, Dec 13, 2024 at 8:05 PM T3M8029 @.***> wrote:

Added this as a setting in a pull request
https://github.com/Banjobeni/DVDispatcherMod/pull/7, you can download
the file from there for now and test if everything´s ok and potentially
give feedback.
—
Reply to this email directly, view it on GitHub
https://github.com/Banjobeni/DVDispatcherMod/issues/8#issuecomment-2542075346,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3DIERPT7Z7GBWQK6M36BL2FMVWBAVCNFSM6AAAAABTRVYTYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBSGA3TKMZUGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Strip trailing dot

Strip tailing dot from input email address and update remadme to contain the correct amount of domains. See RFC 1034 for info regarding domain trailing dot

Thank you for contributing and providing the comments. It all make sense and will be published into new version soon.


OpenComputers can't completely rotate (Advanced) Info Panels

Rotating an info panel manually sets it to 56, according to OpenComputers, but the function to rotate it via OpenComputers only accepts a value of 1 through 16, thus only allowing for a small amount of rotation via computer vs doing it manually

How does OpenComputers rotate things?

First, you need to hook up an Info Panel via an OC Adapter like so:

Note how it's rotated all the way? I did that manually via the Info Panel's rotation settings tab.
Now, see here, how I've called getRotationHorizontally() which should return the value that the panel is currently rotated at:

But if you look at the function info, it only accepts a value of 1-16, which means I can only rotate it the equivalent of two notches on the settings tab, and I can only rotate it in a positive manner, since it won't take a negative number for the rotation settings:

Closing since it's been nearly 2 years with no comment/resolution


Add support for modmail muting

Adds features necessary for modmail muting:

Subreddit.add_mute and Subreddit.remove_mute for muting arbitrary redditors (uses the /friend endpoint)
Message.mute_modmail_author and Message.unmute_modmail_author for muting the sender of a particular message (uses dedicated endpoints)
Subreddit.get_muted (via ModOnlyMixin)

Note! The list returned from Subreddit.get_muted is of the form [{'id': 't2_6c1xj', 'date':<PHONE_NUMBER>.0, 'name': 'PyAPITestUser3'}], as opposed to the usual [Redditor(user_name='PyAPITestUser3')].

Note! The list returned from Subreddit.get_muted is of the form [{'id': 't2_6c1xj', 'date':<PHONE_NUMBER>.0, 'name': 'PyAPITestUser3'}], as opposed to the usual [Redditor(user_name='PyAPITestUser3')].

Is there a reason you used get_content() instead of the usual _get_userlist() of get_banned()?

Oops. I didn't actually know that was a thing. The copy-pasting I did here was from get_mod_queue since it was conveniently close.

<3
So now it will return the reddittor objects I presume?

Yeah, using the default value of user_only=True, the list will contain redditor objects like get_banned. I just assumed the reddit API was sending different info for this endpoint for some reason :clap:

:+1:

Looks great!

Thanks!


[Bug]: I downloaded the microsoft playwright cli and it downloads the wrong versions of chrome

Playwright version
1.12.0
Operating system
Windows
What browsers are you seeing the problem on?
Chromium
Other information
On windows 10
What happened? / Describe the bug
trying running playwright install but when I would run playwright it could never find Chrome. If I blew away my cached browsers it would download them but the wrong versions.
If I rename the version of the folder it works but if I ever reinstall browsers I have to go do it again.
Code snippet to reproduce your bug
using System;
using Microsoft.Playwright;
using System.Threading.Tasks;

namespace PlaywrightDemo
{
	class Program
	{
    public static async Task Main()
    {
        using var playwright = await Playwright.CreateAsync();
        await using var browser = await playwright.Chromium.LaunchAsync();
        var page = await browser.NewPageAsync();
        await page.GotoAsync("https://playwright.dev/dotnet");
        await page.ScreenshotAsync(new PageScreenshotOptions { Path = "screenshot.png" });
    }
	}
}

Relevant log output
D:\Source\playwright_sharp\PlaywrightTests> playwright install
Removing unused browser at C:\Users\user\AppData\Local\ms-playwright\chromium-907428
Downloading Playwright build of chromium v888113 - 97.7 Mb [================] 100% 0.0s
Playwright build of chromium v888113 downloaded to C:\Users\aleth\AppData\Local\ms-playwright\chromium-888113

Unhandled exception. Microsoft.Playwright.PlaywrightException: Executable doesn't exist at C:\Users\user\AppData\Local\ms-playwright\chromium-907428\chrome-win\chrome.exe
╔═════════════════════════════════════════════════════════════════════════╗
║ Looks like Playwright Test or Playwright was just installed or updated. ║
║ Please run the following command to download new browsers:              ║
║                                                                         ║
║     npx playwright install                                              ║
║                                                                         ║
║ <3 Playwright Team                                                      ║
╚═════════════════════════════════════════════════════════════════════════╝
   at Microsoft.Playwright.Transport.Connection.SendMessageToServerAsync[T](String guid, String method, Object args)
   at Microsoft.Playwright.Core.BrowserType.LaunchAsync(BrowserTypeLaunchOptions options)
   at PlaywrightDemo.Program.Main() in D:\Source\playwright_sharp\PlaywrightDemo\Program.cs:line 12
   at PlaywrightDemo.Program.<Main>()

This is caused by https://github.com/microsoft/playwright/issues/7741
executing playwright install without the npx should fix it.

I didn't run npx, you can see in the first line of my traces from my powershell i was running, playwright install without npx.
This should have been using the playwright cli  installed through dotnet tools. We are running into the same behavior in windows docker containers.

Whats your output of Get-Command playwright in PowerShell? Seems like its using the wrong Playwright CLI.

Thank you for your help. Yes It was pointed at a previous python version of playwright.
I moved my environment variable up to put dotnet ahead of python and it works now. Closing as it was my error due to other language cli taking precedence.

@mxschmitt I'm reopening this as I'm trying to upgrade to v1.17 and no matter what I do it doesn't download the correct chromium version.
My Tools installation

I cleaned the ms-playwright folder and is still downloading the older version

My apologies, after reading this again carefully I remembered that I was upgrading from .net 5 to .net 6 and I forgot to clear previous builds if anyone has the same issue, just run this command from the repo root folder to clear all bin and obj folders:
Get-ChildItem .\ -include bin,obj -Recurse | foreach ($_) { remove-item $_.fullname -Force -Recurse }


Error pulling from dvc

When I run dvc pull -f I get the following output:
WARNING: No file hash info found for 'backend/unsplash-dataset'. It won't be created.
WARNING: No file hash info found for 'backend/story_generator/downloaded'. It won't be created.
WARNING: No file hash info found for 'backend/outputs'. It won't be created.
3 files failed
ERROR: failed to pull data from the cloud - Checkout failed for following targets:
backend/unsplash-dataset
backend/story_generator/downloaded
backend/outputs
Is your cache up to date?
<https://error.dvc.org/missing-files>

In my case, when i run dvc pull -f i get:
ERROR: failed to pull data from the cloud - config file error: no remote specified. Create a default remote with     dvc remote add -d <remote name> <remote url>

Thank you for the details, as for issue #5 .dvc/config was added to solve this issue.
Please let us know if you have further issues.


proposal for improvement to have a better split between data and code

with this patch, you have only to call the class bind, alls subclasses will be called and the data is sourced via hiera keys all appeded with 's' (see below)
few examples:
bind::configs:
'named.conf.servers':
content: |
server <IP_ADDRESS> {
keys { dns-axfr; };
};
bind::acls:
primaries:
address_match_list:
- <IP_ADDRESS> comment: powerdns
bind::keys:
dns-axfr:
algorithm: hmac-sha512 base64_secret: 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa=='
bind::zone::secondarys:
example.net:
masters:
- <IP_ADDRESS>
I'm hope this will make this module a bit more convinent and handy
Best greetings from Berlin
/holm

Good morning Stefan,
I did some small changes and think with my last commit, this is now ready to merge, if you don't mind.
Best regaeds
/holm


Implement process to retrieve updated metadata rather than using local cached

Use the same code that was implemented in student dashboard to retrieve remote metadata.
Will need changes on
https://github.com/tl-its-umich-edu/student-dashboard-django/pull/116
and
https://github.com/tl-its-umich-edu/student-dashboard-django/pull/130

This may need to be in a release earlier than 3.0 if we do a 2.5 release.


PR tree shows ‘No GitHub repositories found’ when not authenticated

Run sign out command of extension
Reload VS Code
Click on activity bar icon

Message says that there are no github repositories, when in fact there are, but auth has not been completed. Should show a ‘Sign in’ instead.

Any insight into a workaround until this fix goes out with a release? I've attempted to fully remove the extension and reinstall but that does not appear to help. Thank you!

I think the following should work

Run sign in command and complete sign in process
Reload/restart VS Code

Sometimes it takes a bit for the tree to load and it still shows the ‘No GitHub repositories found’ message, I’d like to improve this even more to show ‘Initializing…’ then


lv_chart_set_type() - invalid conversion from int to lv_chart_type_t

Hi,
I found a minor issue, when trying the Chart example, with this line:
lv_chart_set_type(chart, LV_CHART_TYPE_POINT | LV_CHART_TYPE_LINE);

Error: invalid conversion from 'int' to 'lv_chart_type_t' [-fpermissive]

Hi,
Thank you!
With my settings it didn't cause warning.
Introducing an LV_CHART_TYPE_LINE_AND_POINT type should solve it. What do you think?

Hi Gabor,
I think the OR operation isn't the issue here, as the toolchain complains about the conversion from 'int' to 'lv_chart_type_t'.
It seems I just can't pass an int to the function.
I tried casting using (lv_chart_type_t), but same result.
I'm a bit puzzled, about this one... :-)
Just modifying the function so it can pass an int or enum could possibly be a solution, do you think?

Hi,
It's strange. I googled on this warning and found some C++ related topics. are you using C++?

Yes, I'm using C++. I will try to figure this out.

I found this: https://stackoverflow.com/questions/11452920/how-to-cast-int-to-enum-in-c
So maybe it works:
    static_cast<lv_chart_type_t>(LV_CHART_TYPE_LINE | LV_CHART_TYPE_POINT);

Hi Gabor, you are awesome! This works!
I saw something similar on stackoverflow, but didn't test it yet, as I'm quite busy these days.
Because you have put your effort in finding a solution for me, I wanted to thank you and give you giveback :-)
So this worked, I do now have the dots in the graph:
lv_chart_type_t type = static_cast<lv_chart_type_t>(LV_CHART_TYPE_POINT | LV_CHART_TYPE_LINE);
lv_chart_set_type(chart, type);   /*Show lines and points too*/

Or just:
lv_chart_set_type(chart, static_cast<lv_chart_type_t>(LV_CHART_TYPE_POINT | LV_CHART_TYPE_LINE));   /*Show lines and points too*/

I hope, I don't bother you too much, though... :-)

Awesome!
Bother? The opposite! I'm always happy to see so enthusiastic people like you! Keep this great work! :)
As the issue seems solved I close this issue.


[MB] If hoster search returns None crawljob is still created

If the search for hoster returns None  title should not be added to dB and crawljob should not be created

Closed by https://github.com/rix1337/RSScrawler/commit/21650170217f0d304e22d5e6f7a63017d41174f2


[pyspark] sort qid for SparkRanker

To fix #8491

@WeichenXu123 @trivialfis please help to review it.

@hcho3 please help to merge it. thx

@wbo4958 Could you please change the tests to NOT use hardcoded results?

https://github.com/dmlc/xgboost/pull/8497#discussion_r1035757638

#8497 (comment)

Hi @trivialfis, For this case, the test I added is to check if the pyspark application will be crashed, so it's ok, I think, to hardcode the data. Since I think the data is so straightforward to show the scenario which can crash the process.


Transactions FireFly wallet

Issue description
Hi, under the menu "latest transactions" in the firefly wallet i have 2 transactions with grey background. Before this happened, i tried to start staking.
Now, nothing happens and i can not start staking. But i have no problem with the nodes.
Is it because of the overloaded network?  I have the problem since yesterday.
Sorry, but i posted my problem under "discussions", too. But i am afraid, i could loose my tokens.
Kind regard
Stefan

Firefly version
1.3.0
OS details
Windows 10
Can the issue be reliably reproduced?
No
Steps to reproduce the issue
1.---?---
2.
3.
...
Expected behaviour
please solve my problem
Actual behaviour
??
Errors
No response

When you originally tried to stake, the nodes must have been crashing and did not process this staking message to add it to the tangle. Firefly still thinks that this is a pending message as it has not received a response from the node. The nodes must have cleared their message queue and since restarting they don't know this message exists.
Creating a new profile with same seed, the pending message will not exist so firefly is not waiting for a response, and you can freely issue a staking transaction to the now working nodes.

Thank you very much, now it works.

Okay great. Issue can be closed


Add new meeting minutes + update releases + snapshot pages

What it says in the title

I addressed the changes that I requested and I am also happy with the other changes that @louise-davies made.


Only allow admin to change the config on the server

install assembly line,
list sessions, and
scan all packages

Alternate version of #82, added to a few more interviews

Didn't realize that nav.yml was included in everything, #82  is the better PR, sorry


Question: how can I use prev_sibling_element?

Is there a way to access method prev_sibling_element()?
It seems to be defined inside a private module so it is not accessible.
I need to traverse HTML where the elements are organized in a long list, pairs of <h4> with title and <div> with content, both of which I need to read.

You mean this method? It's part of a public trait of selectors so you need to use selectors::Element;.

Thanks for the pointers! I was a bit confused by trying to use scraper::selectors. Now after adding separate dependency on selectors = "0.20.0" it works exactly as you describe.
Troubles of RUST beginner... thank you again!


About training questions

How to train easyanimate with multi machines multi gpus?

to use accelerate and deepspeed config.
PAI-DLC is our recommend ^_^.


Add --strip-atomic-counter-memory

Adds an optimization pass to remove usages of AtomicCounterMemory
bit. This bit is ignored in Vulkan environments and outright forbidden
in WebGPU ones.
Fixes #2242

I have added in proper test coverage. The build failure is due to something unrelated to my PR. Something using SpvCapabilitySubgroupAvcMotionEstimationINTEL which doesn't exist.

Looks like everything is working correctly. @s-perron PTAAL


metrics_msgs: 0.1.0-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository metrics_msgs to 0.1.0-1:

upstream repository: https://github.com/MetroRobots/metrics_msgs
release repository: https://github.com/ros2-gbp/metrics_msgs-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.2
previous version for package: null

benchmark_msgs
* benchmark_msgs, benchmark_utils, collision_msgs
* Contributors: David V. Lu!!

benchmark_utils
* Fix Compiler Warning (#2 <https://github.com/MetroRobots/metrics_msgs/issues/2>)
* benchmark_msgs, benchmark_utils, collision_msgs
* Contributors: David V. Lu!!

collision_msgs
* benchmark_msgs, benchmark_utils, collision_msgs
* Contributors: David V. Lu!!

This pull request has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/discussion-standardizing-ros-interfaces/33693/1

I am relenting. Closing for #38670


Custom WMS imagery

A custom background imagery URL template can now include WMS tokens like {bbox}. A new button in the Custom Background Settings dialog generates a URL template from a WMS GetCapabilities URL.

The WMS GetCapabilities UI and the logic for converting the GetCapabilities document into a URL template are rather crude for now, and I’m also not wedded to the idea of a separate dialog. Should the Custom Background Settings dialog just accept the GetCapabilities URL in its main text field and asynchronously fetch the GetCapabilities XML when clicking OK? Should that dialog have a separate tab for WMS, to keep the instructions from getting unwieldy? Whatever the case, the JavaScript prompt() will need to be replaced by a proper custom dialog, since some WMS servers require the user to choose from among multiple named layers.
Fixes #4977.

I gave it a try on https://deploy-preview-6915--ideditor.netlify.com/ (preview is pretty cool btw!) on  the first WMS service I could find on the web: link
Unfortunately, Firefox won't let me use that site due to same origin policy - CORS header ‘Access-Control-Allow-Origin’ missing. The error popup reports a: TypeError: NetworkError when attempting to fetch resource.

 One possibility would be to fall back to an upload form (or text area) where the user can provide the contents of the GetCapabilities XML file.
This PR does make it possible to take the wms: URL that JOSM generates and use it as a standard custom background imagery URL template, {bbox} and all. The WMS button doesn’t do a whole lot with the GetCapabilities file; it just uses it to detect MIME types and layer names, and potentially projections. But if we create a dedicated custom dialog for WMS, then all that can be entered manually anyways.

It looks like a good start, but I can't merge it as-is, so this might have to sit for a while.

Yeah, I’m not ready to call it done either. Say, I only went down the path of trying to support GetCapabilities URLs because I wasn’t sure if people could be comfortable deriving the WMS URL templates manually. But what if we land support for WMS URL parameters (9fbf0c30558adafcda1b3ccf5380eb11e1c81e06) first, then figure out the UI for GetCapabilities separately?

I ended up including a limited version of this in #7428..
For now, iD can support custom wms templates but we will assume EPSG:3857 for the projection.  (I didn't have time to add an input field for the user to type in some different projection or validate it against the limited list of projections iD actually supports)


Storing steamid in mysql

is there any way i can get the steamid of a user and store it in my mysql database as soon as he logs in?

Uhm... the $_SESSION['steamid'] variable is accessable at any time a user is logged in.
It should be fairly easy to store them in your db.
Just a quick reminder: This is a libarary for steam-logins, not a general php-questionboard

As BlackCetha has said, you can use $_SESSION['steamid'] once a user has logged in. It should be quite easy to add a function in steamauth.php to store/check the users steam ID. But that is not the purpose of this project.
Issue closed.


Be a good RabbitMQ 3.7.x plugin citizen: depend on the rabbit app

Starting with 3.7.x plugins must depend on the rabbit app (see Breaking Changes: apparently I cannot link to a section, sorry) or else they won't appear in rabbitmq-plugins list output.
This is not an issue if the plugin is "pre-enabled" (was enabled previously or the node uses a generated enabled_plugins file) but it is a major problem for beginners.

Hey, thanks for pointing out but I don't get what 'depend' means, I have rabbit listed there https://github.com/deadtrickster/prometheus_rabbitmq_exporter/blob/master/src/prometheus_rabbitmq_exporter.app.src#L9. Could you please elaborate.

Oh, so there is a hand crafted .app.src file. Fair enough, sorry about the noise.


useFakeTimers does not run as expected with node 7.4.0.

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Timer example tests fail to pass on node v7.4.0
▶ node -v
v7.4.0

jest-master/examples/timer
▶ npm test -- --no-cache

> @ test /jest-master/examples/timer
> jest "--no-cache"

 FAIL  __tests__/infiniteTimerGame-test.js
  ● schedules a 10-second timer after 1 second

    TypeError: Cannot read property 'calls' of undefined

      at Object.<anonymous> (__tests__/infiniteTimerGame-test.js:15:25)
      at process._tickCallback (internal/process/next_tick.js:103:7)

 FAIL  __tests__/timerGame-test.js
  ● timerGame › waits 1 second before ending the game

    TypeError: Cannot read property 'calls' of undefined

      at Object.<anonymous> (__tests__/timerGame-test.js:12:27)
      at process._tickCallback (internal/process/next_tick.js:103:7)

  ● timerGame › calls the callback after 1 second via runAllTimers

    expect(jest.fn()).toBeCalled()

    Expected mock function to have been called.

      at Object.<anonymous> (__tests__/timerGame-test.js:29:22)
      at process._tickCallback (internal/process/next_tick.js:103:7)

  ● timerGame › calls the callback after 1 second via runTimersToTime

    expect(jest.fn()).toBeCalled()

    Expected mock function to have been called.

      at Object.<anonymous> (__tests__/timerGame-test.js:46:22)
      at process._tickCallback (internal/process/next_tick.js:103:7)

Test Suites: 2 failed, 2 total
Tests:       4 failed, 4 total
Snapshots:   0 total
Time:        2.117s
Ran all test suites.
npm ERR! Test failed.  See above for more details.

What is the expected behavior?
Expect example tests to pass on Node 7.4.0. After upgrading to Node 7.6.0, timers run and tests pass as expected.
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
Fresh npm install from https://github.com/facebook/jest/tree/master/examples/timer
▶ node -v
v7.4.0
▶ npm -v
4.0.5

OS X 10.11.6
The example tests successfully passed with node 7.4.0 and jest 19.0.2. It appears to be an issue with Jest 20.

For some reason when I call useFakeTimers twice, the example work 😕

I think the issue was introduced in jest 20... I ran the example with Jet 19 and it seems to work... cc @dmitriiabramov

I think it's specific to Node 7.4, works on every other Node version.


fix: replace url_for_current with url_for

Upgrade to fava 1.20 breaks the extension, as it depends on the url_for_current function, that was apparently removed. This PR replaces the url_for_current shorthand with the more verbose url_for, allowing an upgrade to fava 1.20.

can you please also update the pypi version of the package? pip install fava fava-envelope is currently not working due to this...
I'm going with pip install git+https://github.com/polarmutex/fava-envelope.git for now

Unfortunately, I don't know how to update the package / version. Might be related to Bug #30 ?


Default data directory path

The default data directory path puts everything in the user's home directory.  It might cause less problems for newby users to create a pysatData directory at the home directory level and use this as the default if nothing is specified.

Should this be created during setup?  Or the first time data is downloaded?

I believe the code that sets up the directory now is in the main init for pysat. It sets up a couple things the first time pysat is run.
On Mar 5, 2019, at 5:40 PM, Jeff Klenzing <notifications<EMAIL_ADDRESS>wrote:
Should this be created during setup? Or the first time data is downloaded?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/rstoneback/pysat/issues/163#issuecomment-469904479, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADbdeZKQ5I5kva-emTWkQiT_-G4KDT-4ks5vTwBYgaJpZM4bDvU3.

I've got a version working on my local computer (branch is default_directory), but Travis apparently will not let me create a directory under the /home/travis directory, and the instrument downloads error out.  The quick solution is to put in a check for travis and send the data somewhere else.  Thoughts?

You can create directories but those probably have to be within the user home.
The Travis.yml used to make some directories. May still have some examples.
On Mar 6, 2019, at 7:30 AM, Jeff Klenzing <notifications<EMAIL_ADDRESS>wrote:
I've got a version working on my local computer (branch is default_directory), but Travis apparently will not let me create a directory under the /home/travis directory, and the instrument downloads error out. The quick solution is to put in a check for travis and send the data somewhere else. Thoughts?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/rstoneback/pysat/issues/163#issuecomment-470107434, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADbdefmtbTGONFv6nVMgmG8unwX3n-Rcks5vT8L_gaJpZM4bDvU3.

Closed with merge of #197


Load Addon won't disappear

When I add dofile("../addons/enhancedcollection/enhancedcollection.lua"); to addonloader.lua and start up the game, then press Load Addon, it stays on the screen.

Please install v1.1.0 which is a simple IPF file copy, no more file editing needed!
Instructions are in the readme file.


Why the validator node is 100?

❓ Questions and Help
The validator node is 100, I wonder to know, why?  why not 21 or another number?
Someone can answer me?

100 is perfect score.

@fxsjy  so naughty 😄

it's easier to calculate 51% attacks

The system doesn't depend on having exactly 100 -- it's simply an estimate of how many validators might participate in the system initially.


x/tools/gopls: completions work in some directories and not in others

What did you do?
I created a simple go program:
package main

import (
	"fmt"
)

func main() {
	fmt.
}

If I put the source code in the path ~/git/vendor/enigmacurry/go-play/hello.go, using gopls to complete on line 8 directly after fmt. it does not yield valid candidates for completion of fmt. Instead, it gives me these completions:

However, if I put the same source code in a different directory, ~/git/go-play/hello.go, completion is working correctly:

I have created two gopls debug logs:

This is the debug log for the broken session of  ~/git/vendor/enigmacurry/go-play/hello.go (see lines 309-314)
This is the debug log for the working session of  ~/git/go-play/hello.go (see lines 211-216)

I have tested in a total of three environments:

Emacs 28 lsp-mode (config here)
Emacs 28 eglot mode
VS Code (vscodium 1.68.1 with golang/vscode-go extension v0.34.1 and default settings)

All environments showed the same result. I have replicated the problem on two separate machines (Arch Linux and Manjaro).
What did you expect to see?
I expected to see valid completions of fmt in both files in both sessions in both directories.
What did you see instead?
The source in ~/git/vendor/enigmacurry/go-play/hello.go does not offer valid completions.
The parent directory ~/git/vendor hosts many other repositories totaling 18GB, which may be a factor as this bug appears to be directory specific.
Build info
gopls is installed directly from the Arch Linux repository:
$ pacman -Qo gopls
/usr/bin/gopls is owned by gopls 0.8.4-1

golang.org/x/tools/gopls v0.8.4
    golang.org/x/tools/gopls@(devel)
<EMAIL_ADDRESS>h1:dtDWrepsVPfW9H/4y7dDgFc2MBUSeJhlaDtK13CxFlU=
<EMAIL_ADDRESS>h1:81/ik6ipDQS2aGcBfIN5dHDB36BwrStyeAQquSYCV4o=
<EMAIL_ADDRESS>h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=
<EMAIL_ADDRESS>h1:qyrTQ++p1afMkO4DPEeLGq/3oTsdlvdH4vqZUBWzUKM=
<EMAIL_ADDRESS>h1:6zppjxzCulZykYSLyVDYbneBfbaBIQPYMevg0bEwv2s=
<EMAIL_ADDRESS>h1:5KslGYwFpkhGh+Q16bwMP3cOontH8FOep7tGV86Y7SQ=
<EMAIL_ADDRESS>h1:rm+CHSpPEEW2IsXUib1ThaHIjuBVZjxNgSKmBLFfD4c=
<EMAIL_ADDRESS>h1:olpwvP2KacW1ZWvsR7uQhoyTYvKAupfQrRGBFM352Gk=
<EMAIL_ADDRESS>h1:CJwk4qG1fov4WP7/DWhhb7OQVZlQKAl1rEMnDF+ceGU=
<EMAIL_ADDRESS>h1:jokAF1mfylAi1iTQx7C44B7vyXUcSEMw8eDv0PzNu8s=
<EMAIL_ADDRESS>h1:2LdYUZ7CIxnYgskbUZfY7FPggmqnh6shBqfWa8Tn3XU=
<EMAIL_ADDRESS>h1:kTojdZo9AcEYbQYhGuLf/zszYthRdhDNDUi2JKTxas4=
<EMAIL_ADDRESS>h1:tzxjVAj+wSBmDcF6zBB7/myTy3gX9xvi8Tyr28AuQgc=
go: go1.18.2

If I rename ~/git/vendor to ~/git/vendor2 it works.

Just looked into this.
I don't think this ever worked. Or at least I reproduced it and tried to bisect all the way back to gopls/v0.7.0 (approximately as far back as one can go without running into build problems), and it seems to have always been a problem.
We should and will still fix, though perhaps with less urgency than if this were a recent regression.

Have to move on for now, but https://go.dev/cl/419111 contains a sketch of a solution: when checking if a file is "vendored" (generally used to detect that we don't care about it), consider paths relative to workspace root. This makes the included regression test pass, and might be sufficient, but it requires some analysis (and we'll see if other tests pass).
It seems quote possible that this CL is insufficent though. Perhaps we want to consider paths relative to module root, not workspace root.


Bumping go version to 1.21

[x] I have looked at the documentation here first?
[x] I have looked at the examples provided that may showcase my question here?

Package version eg. v9, v10:
v1.10
Issue, Question or Enhancement:
Hey there 👋
Curious to see if there is a reason why the go version in go.mod is still on 1.18?
The go versions in other spots of the repo, mainly github actions, are on 1.21. If this was an oversight I'll gladly push up a PR to bump the version 🙂 !

@ddymko this was not an oversight and changing it would be a breaking change.

The go directive is the minimum version supported and states:

The go directive sets the minimum version of Go required to use this module.

The go directive also, since Go 1.21, also is no longer advisory, but mandatory. This means that by changing it as of this version has become a breaking change for anyone importing packages below this version and needs to be handled just like making a breaking change to the package now.

I highly recommend everyone read carefully through the last few Go releases and the Go Mod Reference as dependencies management and managing packages has become much harder; it's easier to make an unintended breaking change than ever before. Also watch out as the Go tooling, I've caught it automatically changing this information without me asking for it.
For other package maintainers that may read this I highly recommend using go build directives to support newer functionality introduced in newer go versions as well as maintaining backward compatibility with older versions, bumping the go.mod Go version is not the solution and is a breaking change, an example can be found here in one of my other packages.

@deankarn thanks for detailed response


Question about fetching timestamp offset

First of all thank you for your great lib. I almost switch from sarama my kafka lag prom exporter. So far it's a great experience and performance are really better (ok I was maybe not using sarama the good way making many many multiple request where big one seems more efficient).
Anyway the last part I need to migrate is my calculation of the timestamp of the oldest offset and the lag calculated in time.
One function I wrote with Sarama is something like
func GetTimestamp(broker *sarama.Broker, topic string, partition int32, offset int64) (time.Time, error) {
	request := &sarama.FetchRequest{Version: 4}
	request.AddBlock(topic, partition, offset, 1)

	fr, err := broker.Fetch(request)
	// error handling

        block := fr.GetBlock(topic, partition)
        // error handling

	return block.Records.RecordBatch.MaxTimestamp, nil
}

I struggle to find the equivalent in franz-go. Any pointer appreciated.

That looks like the equivalent with running ConsumePartitions with a given offset, fetching once, and then returning the timestamp on the record. Is it not?
If possible, though, I'd recommend checking out kadm.Lag, although this is specifically for groups.

Yes what I want is "fetching" one or many records at given offsets.
something like
los, err = cadmin.ListStartOffsets(context.Background())

cli, err := kgo.NewClient(kgo.SeedBrokers("<IP_ADDRESS>:9092"), kgo.ConsumePartitions(los.KOffsets()))

fetches := cli.PollRecords(context.Background(), 1)

    for _, fetch := range fetches {
        for _, ft := range fetch.Topics {
            for _, fp := range ft.Partitions {
                for _, rec := range fp.Records {
                    fmt.Printf("   %s %d %s \n", rec.Topic, rec.Partition, rec.Timestamp.Format(time.RFC850))
                }
            }
        }
    }

give me one timestamp for one partition ok. So I can play with PollRecord to fetch record by record.
but actually I wanted something more low level, don't want to poll. Either the record exist at the given offset either not.
and possibly fetching many record at once.
don't know if I'm clear?

OK so I've read a bit further the kafka protocol. So what I need is surely to craft a fetchRequest(). Actually I played a bit with kmsg ; succeed making one request and having a correct response. But struggle to 1) set the correct version of the protocol (don't want dealing with topic-id ; working but add complexity), and 2) don't succeed to have multiple records in the response when adding more partitions/topics to the request ?!
what I want to avoid is making one request foreach timestamp I want to retrieve. From what I read from the protocol it should be doable but no luck for now.

So you basically want to:

10: Get offsets at timestamp
20: SetOffsets
30: PollRecords
40: goto 10

Is that right?
re: setting correct protocol version -- usually you shouldn't need to worry about it, but also the client isn't setup today to handle manually created fetch requests (this is so rare and unexpected that well, I just don't expect anybody to ever do it).
(2), they should succeed when having multiple records in a request.
ListOffsets only supports a single topic/partition once. You cannot duplicate the input topic partition, the request will unfortunately fail, this is coded on the broker. If you want to request the same partition with two timestamps / etc, it will fail.

So you basically want to:

10: Get offsets at timestamp
20: SetOffsets
30: PollRecords
40: goto 10

Is that right?
re: setting correct protocol version -- usually you shouldn't need to worry about it, but also the client isn't setup today to handle manually created fetch requests (this is so rare and unexpected that well, I just don't expect anybody to ever do it).
(2), they should succeed when having multiple records in a request.
ListOffsets only supports a single topic/partition once. You cannot duplicate the input topic partition, the request will unfortunately fail, this is coded on the broker. If you want to request the same partition with two timestamps / etc, it will fail.

Hmm no.
What I want is to get timestamp of records at specific offeset.
Particularly get the timestamps of oldest offsets of each partition.
The timestamps of newest one. And timestamps of particular offsets (those were consumer group are) to calculate LAG but in time.

kadm.ListStartOffsets to get the start,
kadm.ListEndOffsets to get the end,
and then for all commits, kgo.NewClient(kgo.ConsumePartitions(...)) to specify the offset to consume at, consume a single record, and close the client.


Add Delete  REST API support

New WebAPI controller "DelowRSController.cs" has been added to the project with the following routes fully implemented:
[HttpDelete]
[Route("delowrs/studies/{studyInstanceUID}")]
[Route("delowrs/studies/{studyInstanceUID}/series/{seriesInstanceUID}")]
[Route("delowrs/studies/{studyInstanceUID}/series/{seriesInstanceUID}/instances/{sopInstanceUID}")]

Deleteing a DICOM dataset is not a service defined by the DICOM standard, but it is useful for a DICOMweb server.


Gift name

Hello everyone,
I have found the following gift which is unfortunately not recognized. Is there a way to supplement this?
Gift

More info please


When Wikidata has no decription, show class label instead

Using the app to upload a picture, search for 潮騒
Only the caption shows up, as item https://www.wikidata.org/wiki/Q60985286 has no description in any language.

In such cases, it would be great to show the label of the Wikidata item that Q60985286 is an instance of (https://www.wikidata.org/wiki/Q105543609 "musical work/composition").
It would be a great help in this case as there are many homonyms (novels, movies, bridges, sculptures, etc).

@nicolas-raoul Because of the server-side response, We can't get the name of the instance of depicts directly from the response. It will show only the IDs. It will be better if we can directly get the name from the response. Otherwise, to implement it we have to search for the name by the ID for each item.

@nicolas-raoul Can I work on it?

@Ayan-10 It is yours, thanks! :-)


e0308 during compiling with rust on windows

There is an error appears during building MeiliSearch with Rust on Windows 10 (cargo build --release):
Compiling meilisearch-core v0.19.0 (C:\Users\Lenovo\github\MeiliSearch\meilisearch-core)
error[E0308]: mismatched types
  --> meilisearch-core\src\store\facets.rs:51:47
   |
51 |         let first_size = usize::from_be_bytes(size_buf);
   |                                               ^^^^^^^^ expected an array with a fixed size of 4 elements, found one with 8 elements
error: aborting due to previous error
For more information about this error, try 'rustc --explain E0308'.
error: could not compile 'meilisearch-core'
To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed

Rust version
rustup --version --verbose
rustup 1.23.1 (3df2264a9 2020-11-30)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active 'rustc' version is 'rustc 1.50.0 (cb75ad5db 2021-02-10)'

Rustc version
rustc --version --verbose
rustc 1.50.0 (cb75ad5db 2021-02-10)
binary: rustc
commit-hash: cb75ad5db02783e8b0222fee363c5f63f7e2cf5b
commit-date: 2021-02-10
host: i686-pc-windows-msvc
release: 1.50.0

Fixed by https://github.com/meilisearch/MeiliSearch/pull/1438. WIll be available in v0.21.0