Programmable Switches Lutron Pico

I read the thread on the hue switches, but what about the Lutron pico remotes and/or connected Bulb remotes? Any pathway to thoes working? They look som much nicer then the hue dimmer and can be mounted in a standard switch plate.

I'm unfamiliar with these.  Are they even available in Europe?
Note that homebridge-hue doesn't connect directly to any switch (or sensor, or light).  It connects to the Hue bridge, which, in turn, connects to the device over ZigBee wireless networking.
Looking at their web site, the Lutron connected bulb remote uses ZigBee as well.  In theory, you might be able to connect these to your Hue bridge, and I could add support in homebridge-hue.  In practice, Philips use vendor specific extentions to the ZigBee standard in connecting their dimmer switches and motion sensors.  I doubt you'll get the Hue bridge to work with any non-Philips switch or sensor.  The pico remotes use a different wireless technology altogether, still looking at the Lutron web site.  Connecting these to the Hue bridge is technically impossible.

@ajiuo666 Did you post this in the Hue developer forum?  If so, does the mentioned hack make the Lutron switch visible on the Hue bridge, or does it just pair the switch directly with the lights?  In the first case: could you please post a dump of your bridge state (see README).

You first have to pair the switch with the hue bridge, and then pair it with the bulb, manually. If you don't pair it with the bridge first it will just steel the bulbs from the bridge. You pair it with the bridge the same way you pair a Lutron dimmer... The Lutron Switch eventually detects that it's linked, but it never shows up in the bridge... at least on the UI end... I'm not sure if the bridge has some reference to it... I will see if I can get a dump when I get home.

I've got 6 of these around the house so far, with plans for more.  As you said, they are more attractive, and they fit into a standard US wallplate unlike the Hue dimmers.
You are not actually "pairing" the Lutron remote with the bridge, when you go through the light link process with the bridge, the remote just listens and sets itself to the correct Zigbee channel that your bridge is using.  The bridge is completely unaware of the remote as far as I know.  In fact, I only paired the first one with the bridge, the others have all been paired against one of the other Lutron remotes that is already working.  The reason why they steal the lights from the bridge, is that a new or factory reset remote is most likely on a different channel than you are using with your bridge, so unless you pair it with the bridge or another remote first to get the channel set correctly, it steals the bulb over to the channel the remote is using out of the package or from reset.
The Hue dimmers are nice because you can set specific button functions, but you are limited in the number of dimmers or taps you can have.  The Lutron remotes are nice because of the size, but you can't set button functions because the bridge is not aware of them, they talk directly to the lights you pair with.  On the plus side as far as I know there is no limit to the number you can have because they aren't defined to the bridge.  On the negative side, if you have a lot of these and ever have to change Zigbee channels, they will all have to be manually reset and re-paired to the correct channel and bulbs again.
This is my current understanding of how they work, hope that helps!

I currently use connected Bulb remotes for basic light control and pico remotes for scene triggering.
You can actualy use a Lutron lamp dimmer to trigger HomeKit scenes...  The dimmer doesn't even have to be plugged in once HomeKit has learned it.  You basically just set up a HomeKit trigger to activate a scene when the lamp dimmer it's a specific percentage that corresponds to the button on the pico remote...  and then you need another trigger to reset the lamp dimmer to a default value when any change takes place..  The response time is pretty quick...  it would be nice if they were officially supported though.  A little bit easier set up

Thanks, @toogle9, @ajiuo666

You are not actually "pairing" the Lutron Connected Bulb Remote with the bridge, when you go through the light link process with the bridge, the remote just listens and sets itself to the correct Zigbee channel that your bridge is using.

Also, the Hue bridge exchanges the ZigBee network key with the dimmer, and the dimmer joins the network.

The Lutron Switch eventually detects that it's linked, but it never shows up in the bridge... at least on the UI end... I'm not sure if the bridge has some reference to it

I don't think it has.  Joining the ZigBee network is separate from the bridge configuring the sensor resource.  When performing a touchlink with the bridge, "any" device might join the network; when searching for new devices, the bridge only configures devices it likes.

The reason why they steal the lights from the bridge, is that a new or factory reset remote is most likely on a different channel than you are using with your bridge, so unless you pair it with the bridge or another remote first to get the channel set correctly, it steals the bulb over to the channel the remote is using out of the package or from reset.

A factory-new dimmer actually creates a ZigBee network on the fly.  The light joins this network and is no longer in the Hue bridge network.

The Hue dimmers are nice because you can set specific button functions, but you are limited in the number of dimmers or taps you can have.

The number of dimmers that can be recognised/configured by the Hue bridge is limited by the number of sensor resources (63).  The Hue app limits this even further by creating Hue bridge rules for each dimmer.  The number of dimmers that can be on the same ZigBee network is "unlimited", just as for the Lutron remotes.

On the negative side, if you have a lot of these and ever have to change Zigbee channels, they will all have to be manually reset and re-paired to the correct channel and bulbs again.

Did you actually test this?  I think a channel change is broadcast, so each device on the network should pick it up, not only the ones known by the Hue bridge.

@ebaauw thanks for all the clarifications!  No, I hadn't tested the Lutron Connected Bulb Remote / channel change scenario, I was just assuming it would be a challenge because they weren't registered with the bridge.  I've had some random Hue "no response" issuses and was considering changing channels, but it seems to have stabilized more lately.
@ajiuo666 the Lutron lamp dimmer / Pico remote / HomeKit trigger thing sounds interesting, do you have any links on that with any additional setup details?  I did a quick Google and didn't get any interesting hits.  When you said they didn't have to remain plugged in once HomeKit has learned it, did you mean it didn't have to have a device/lamp connected to it, or the dimmer module itself no longer needed to be plugged in?  Not seeing how it could communicate it's status if it wasn't plugged in at all.  I'm considering getting one of the Caseta switches for a dining room light, where it would not be cost effective for the new Hue E14 bulbs.  I don't really need color there anyway, just want to be able control/dim.  Disappointed I would need another bridge though, but sounds like I would need that for the lamp dimmer setup anyway.

Did anyone ever get the Lutron pico switches to show up in homebridge-hue?

They would need to show up in the Hue bridge first, before homebridge-hue can do anything with them.

Ohhh!  I didn't understand that was the limitation.  Thanks.  So, is this even technically feasible?  Hue would need to update the Bridge firmware to support them via the app?  Then...  homebridge-hue would make them 'HomeKit compatible'?
As a sidenote, I have my Lutron Pico remotes working perfectly, I would recommend them to others.  Even when I change the channel in the Hue app for troubleshooting purposes, the remotes continued to work on the new channel.  Any idea how the Pico remotes learn the new channel??

Ohhh! I didn't understand that was the limitation.

Like any other Hue app, homebridge-hue has no access to the ZigBee network (you'd need ZigBee hardware for that), and uses the Hue bridge as a gateway to interact with ZigBee devices.

So, is this even technically feasible? Hue would need to update the Bridge firmware to support them via the app? Then... homebridge-hue would make them 'HomeKit compatible'?

I don't think Philips will update the Hue bridge to support non-Philips sensors and switches.  Ever.  It would be possible to add support for the Pico to deCONZ, and use homebridge-hue to expose it to HomeKit.

I have my Lutron Pico remotes working perfectly
Even when I change the channel in the Hue app for troubleshooting purposes, the remotes continued to work on the new channel. Any idea how the Pico remotes learn the new channel?

ZigBee isn't a standard for a single single protocol, but for a set of protocols, covering the entire OSI model, all the way down from the phisical layer all the way up through the application layer.  The Pico is connected at the lower network level, where the channel change is managed.  It's not compatible at the higher application level, where the Hue bridge provides the REST API.  The same holds for IKEA bulbs (on old firmware) and OSRAM bulbs (on US firmware) and any non-Hue sensors and switches.
To give an example: Both my iPhone and printer are connected to the same WiFi network, but still I cannot print from my iPhone, which only supports AirPrint, to my printer, which doesn't.  Yet both devices will handle a change of the WiFi channel.  Of course, in this example we use different names for the different levels (viz. "WiFi" for the network level vs "AirPrint" for the application level).  The confusing part is that "ZigBee" sometimes refers to all these levels at the same time, and sometimes not.  It's a bit like the early Bluetooth days, where two devices, both supporting Bluetooth would pair, but wouldn't connect, as they lacked a common profile.

There is a path to this. It would be nice if it was node.js to Hue Bridge, but for now it needs SmartThings AND since SmartThings needs the cloud, it doesn't communicate with SmartThings or the Hue Bridge if there's no access to the cloud. But, it does work and really well. Once configured, adding and configuring remotes is simple. Plus this opens up access to a lot of devices and interactions that are not possible with the Hue Bridge alone.
https://community.smartthings.com/t/how-to-control-anything-with-inexpensive-lutron-pico-remotes/117761

Was support for the Lutron Connected Bulb Remote ever added to homebridge-hue? It is supported in deCONZ, and I can pair it to my conbee ii, but it is only throwing up errors with the hue plugin.

Probably not.  Please attach the debug dump file, so I can see what the switch looks like.  What buttonevent values does it use?

Here are the logs:

12/7/2020, 8:28:36 AM Loaded plugin 'homebridge-hue'
12/7/2020, 8:28:36 AM [12/7/2020, 6:28:36 AM] Registering platform 'homebridge-hue.Hue'
12/7/2020, 8:28:36 AM Loading 1 platforms...
12/7/2020, 8:28:36 AM [Hue] Initializing Hue platform...
12/7/2020, 8:28:36 AM [Hue] config.json: warning: plugin_map: ignoring unknown key
12/7/2020, 8:28:36 AM [Hue] homebridge-hue v0.12.8, node v12.19.0, homebridge v1.1.6
12/7/2020, 8:28:36 AM [Hue] warning: not using recommended node version v14.15.1 LTS
12/7/2020, 8:28:36 AM [Hue] searching bridges and gateways
12/7/2020, 8:28:41 AM [Hue] Phoscon-GW: dresden elektronik deCONZ gateway v2.5.88, api v1.16.0
12/7/2020, 8:28:42 AM [Hue] Phoscon-GW: dresden elektronik deCONZ gateway v2.5.88, api v1.16.0
12/7/2020, 8:28:42 AM [Hue] Phoscon-GW: /sensors/3: warning: ignoring unknown ZHASwitch sensor {"config":{"on":true,"reachable":true},"ep":1,"etag":"cac068a2ca5d7a9642b72ff77e9f438b","lastseen":"2020-12-07T13:28Z","manufacturername":"Lutron","mode":4,"modelid":"LZL4BWHL01 Remote","name":"Connected Bulb Remote","state":{"buttonevent":null,"lastupdated":"none"},"swversion":"1.1","type":"ZHASwitch","uniqueid":"ff:ff:00:0f:e7:ff:43:c3-01-1000"}
12/7/2020, 8:28:42 AM [Hue] Phoscon-GW: error: /sensors/3: {"config":{"on":true,"reachable":true},"ep":1,"etag":"cac068a2ca5d7a9642b72ff77e9f438b","lastseen":"2020-12-07T13:28Z","manufacturername":"Lutron","mode":4,"modelid":"LZL4BWHL01 Remote","name":"Connected Bulb Remote","state":{"buttonevent":null,"lastupdated":"none"},"swversion":"1.1","type":"ZHASwitch","uniqueid":"ff:ff:00:0f:e7:ff:43:c3-01-1000"}
TypeError: Cannot read property 'addOptionalCharacteristic' of undefined
at new HueSensor (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueSensor.js:1728:16)
at HueAccessory.exposeSensorResource (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueAccessory.js:324:20)
at HueAccessory.exposeSensorResources (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueAccessory.js:314:12)
at HueAccessory.expose (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueAccessory.js:126:8)
at HueBridge.exposeResources (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueBridge.js:573:49)
at HueBridge.accessories (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueBridge.js:103:16)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async Promise.all (index 0)
at async HuePlatform.accessories (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HuePlatform.js:324:29)
12/7/2020, 8:28:42 AM [Hue] Phoscon-GW: 3 accessories
12/7/2020, 8:28:42 AM [Hue] Phoscon-GW: /sensors/3: warning: ignoring unknown ZHASwitch sensor {"config":{"on":true,"reachable":true},"ep":1,"etag":"cac068a2ca5d7a9642b72ff77e9f438b","lastseen":"2020-12-07T13:28Z","manufacturername":"Lutron","mode":4,"modelid":"LZL4BWHL01 Remote","name":"Connected Bulb Remote","state":{"buttonevent":null,"lastupdated":"none"},"swversion":"1.1","type":"ZHASwitch","uniqueid":"ff:ff:00:0f:e7:ff:43:c3-01-1000"}
12/7/2020, 8:28:42 AM [Hue] Phoscon-GW: error: /sensors/3: {"config":{"on":true,"reachable":true},"ep":1,"etag":"cac068a2ca5d7a9642b72ff77e9f438b","lastseen":"2020-12-07T13:28Z","manufacturername":"Lutron","mode":4,"modelid":"LZL4BWHL01 Remote","name":"Connected Bulb Remote","state":{"buttonevent":null,"lastupdated":"none"},"swversion":"1.1","type":"ZHASwitch","uniqueid":"ff:ff:00:0f:e7:ff:43:c3-01-1000"}
TypeError: Cannot read property 'addOptionalCharacteristic' of undefined
at new HueSensor (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueSensor.js:1728:16)
at HueAccessory.exposeSensorResource (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueAccessory.js:324:20)
at HueAccessory.exposeSensorResources (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueAccessory.js:314:12)
at HueAccessory.expose (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueAccessory.js:126:8)
at HueBridge.exposeResources (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueBridge.js:573:49)
at HueBridge.accessories (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueBridge.js:103:16)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async Promise.all (index 1)
at async HuePlatform.accessories (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HuePlatform.js:324:29)
12/7/2020, 8:28:42 AM [Hue] Phoscon-GW: 3 accessories
12/7/2020, 8:28:42 AM [Hue] masked debug info dumped to /home/hoobs/.hoobs/etc/homebridge-hue.json.gz
12/7/2020, 8:28:42 AM Initializing platform accessory 'Phoscon-GW'...
12/7/2020, 8:28:42 AM [Hue] Phoscon-GW: 2 services
12/7/2020, 8:28:42 AM Initializing platform accessory 'Daylight'...
12/7/2020, 8:28:42 AM Initializing platform accessory 'Connected Bulb Remote'...
12/7/2020, 8:28:42 AM Initializing platform accessory 'Phoscon-GW'...
12/7/2020, 8:28:42 AM [Hue] Phoscon-GW: 2 services
12/7/2020, 8:28:42 AM [Hue] homebridge: error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: 62afca17-a996-474f-8006-f5a85fecc7af

And I believe this is the button info in deCONZ:
+static const Sensor::ButtonMap lutronLZL4BWHLSwitchMap[] = {
+//    mode                          ep    cluster cmd   param button                                       name
+//  vendor specific
+    // top button
+    { Sensor::ModeDimmer,           0x01, 0x0008, 0x04, 0xfe,  S_BUTTON_1 + S_BUTTON_ACTION_SHORT_RELEASED, "on" },
+    // second button
+    { Sensor::ModeDimmer,           0x01, 0x0008, 0x06, 0x00,  S_BUTTON_2 + S_BUTTON_ACTION_HOLD,           "dimm up" },
+    { Sensor::ModeDimmer,           0x01, 0x0008, 0x03, 0x00,  S_BUTTON_2 + S_BUTTON_ACTION_LONG_RELEASED,  "dimm up release" },
+    // third button
+    { Sensor::ModeDimmer,           0x01, 0x0008, 0x02, 0x01,  S_BUTTON_3 + S_BUTTON_ACTION_HOLD,           "dimm down" },
+    { Sensor::ModeDimmer,           0x01, 0x0008, 0x03, 0x01,  S_BUTTON_3 + S_BUTTON_ACTION_LONG_RELEASED,  "dimm down release" },
+    // bottom button
+    { Sensor::ModeDimmer,           0x01, 0x0008, 0x04, 0x00,  S_BUTTON_4 + S_BUTTON_ACTION_SHORT_RELEASED,  "off" },
+
+    // end
+    { Sensor::ModeNone,             0x00, 0x0000, 0x00, 0,    0,                                           0 }
+};

There’s more going on than an unsupported switch.  Homebridge Hue seems to find your deCONZ gateway twice?

Yeah, I'm new to homebridge and did a quick and dirty setup. I'm about to do a fresh install that should fix that.

I fixed the duplication error on my end. Here is the cleaned up log:

12/7/2020, 11:10:53 AM Loaded plugin 'homebridge-hue'
12/7/2020, 11:10:53 AM Loading 1 platforms...
12/7/2020, 11:10:53 AM [12/7/2020, 9:10:53 AM] Registering platform 'homebridge-hue.Hue'
12/7/2020, 11:10:53 AM [Hue] Initializing Hue platform...
12/7/2020, 11:10:53 AM [Hue] config.json: warning: plugin_map: ignoring unknown key
12/7/2020, 11:10:53 AM [Hue] homebridge-hue v0.12.8, node v12.19.0, homebridge v1.1.6
12/7/2020, 11:10:53 AM [Hue] warning: not using recommended node version v14.15.1 LTS
12/7/2020, 11:10:54 AM [Hue] searching bridges and gateways
12/7/2020, 11:10:59 AM [Hue] Phoscon-GW: dresden elektronik deCONZ gateway v2.5.88, api v1.16.0
12/7/2020, 11:10:59 AM [Hue] Phoscon-GW: /sensors/1: warning: Daylight sensor not configured
12/7/2020, 11:10:59 AM [Hue] Phoscon-GW: /sensors/2: warning: ignoring unknown ZHASwitch sensor {"config":{"on":true,"reachable":true},"ep":1,"etag":"d9c6141565256719c57d3a28cae0a3a8","lastseen":"2020-12-07T15:34Z","manufacturername":"Lutron","mode":4,"modelid":"LZL4BWHL01 Remote","name":"Connected Bulb Remote","state":{"buttonevent":null,"lastupdated":"none"},"swversion":"1.1","type":"ZHASwitch","uniqueid":"ff:ff:00:0f:e7:ff:43:c3-01-1000"}
12/7/2020, 11:10:59 AM [Hue] Phoscon-GW: error: /sensors/2: {"config":{"on":true,"reachable":true},"ep":1,"etag":"d9c6141565256719c57d3a28cae0a3a8","lastseen":"2020-12-07T15:34Z","manufacturername":"Lutron","mode":4,"modelid":"LZL4BWHL01 Remote","name":"Connected Bulb Remote","state":{"buttonevent":null,"lastupdated":"none"},"swversion":"1.1","type":"ZHASwitch","uniqueid":"ff:ff:00:0f:e7:ff:43:c3-01-1000"}
TypeError: Cannot read property 'addOptionalCharacteristic' of undefined
at new HueSensor (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueSensor.js:1728:16)
at HueAccessory.exposeSensorResource (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueAccessory.js:324:20)
at HueAccessory.exposeSensorResources (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueAccessory.js:314:12)
at HueAccessory.expose (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueAccessory.js:126:8)
at HueBridge.exposeResources (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueBridge.js:573:49)
at HueBridge.accessories (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HueBridge.js:103:16)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async Promise.all (index 0)
at async HuePlatform.accessories (/home/hoobs/.hoobs/node_modules/homebridge-hue/lib/HuePlatform.js:324:29)
12/7/2020, 11:10:59 AM [Hue] Phoscon-GW: 3 accessories
12/7/2020, 11:10:59 AM [Hue] masked debug info dumped to /home/hoobs/.hoobs/etc/homebridge-hue.json.gz
12/7/2020, 11:10:59 AM Initializing platform accessory 'Phoscon-GW'...
12/7/2020, 11:10:59 AM [Hue] Phoscon-GW: 2 services
12/7/2020, 11:10:59 AM Initializing platform accessory 'Daylight'...
12/7/2020, 11:10:59 AM Initializing platform accessory 'Connected Bulb Remote'...
12/7/2020, 11:10:59 AM Bridge is running on port 51826.
12/7/2020, 11:11:00 AM [Hue] Daylight: set homekit dark from 1 to 0

In v0.10.12.

Is there anything special to do to get the Hue Bridge to recognize the switch? I've followed the steps that are posted everywhere [1], and while the dimmer will adjust the bulbs in the room on its own (after pairing them in step 5), I don't see any evidence of it, well.. anywhere. It's not showing up in the dump or in the verbose debugging log or anything.
Logs are attached if it's helpful. If you'd rather I start a new issue, I'm happy to do so. I also totally get it if this isn't really a question you can answer.
Thanks!
homebridge-hue.json.gz
homebridge.log.gz
[1] Steps:

1/Pair bulb and hub as normal, test functions of bulb with Hue app
2/unwrap the remote Hold On and Off on remote for 10s to factory reset
3/use Hue app to add a Hue Dimmer Switch, selecting Option 1, New Remote
4/Use the On button on the remote, hold it next to Hue Hub and hold on for about 4s. Watch the remote LED. You are looking for fast blinking of the remote LED to indicate pairing was successful. The Hue app will not display >any information about the pairing.
5/Go to the smart bulb and hold the remote to it, hold On for 10s, wait for the bulb to finish flashing, the remote to finish blinking fast indicating successful pairing. (keep holding it down until after the blink!)
6/Remote joined master network at Hue Hub, then made secondary network with bulb.

Is there anything special to do to get the Hue Bridge to recognize the switch?

Technically, there are two routes to this, but its probably easier and quicker just to move to deCONZ:

Get Signify to change the Hue bridge firmware.  As far as I know, they only do that for Friends-of-Hue switches, which are all ZGP devices, except for the Lutron Aurora.  That Aurora actually looks like its Zigbee part has been designed, or at least co-designed, by Signify/Philips;
Get Lutron to change the switch firmware, so it appears to be a (Friends-of-)Hue device to the Hue bridge.  I’m not sure what the legal implications would be, but technically it’s possible e.g. for non-Hue lights to expose the Manufacturer Code of Philips, so the Hue bridge exposes them to HomeKit.

Technically, there are two routes to this, but its probably easier and quicker just to move to deCONZ:

Ah, gotcha — it wasn’t super clear that deCONZ was required for it to work. Thanks!


List of suggestions from which-key is partially covered by status line

What did you expect to happen?
When pressing first key of a combo to see all possible following keys at the bottom of a frame, e.g. pressing g and waiting should show
# -> evil-ex-search-unbounded-wo..
$ -> evil-end-of-visual-line

and so forth.
What actually happened?
The last line of the list is almost completely "covered" by the status line. I only see few pixels of each character. See the screenshot.

It only happens when there are many lines. For example when pressing SPC f all options are visible.
Describe your attempts to resolve the issue
I tried ctrl-h j and ctrl-h k for paging, but it doesn't do anything.
Steps to reproduce

Open Emacs
Visit any buffer
Press g and wait
See the partially covered suggestions.

System Information
https://pastebin.com/5UFMGWWE

Happens to me too

Thanks @notevenaperson! Setting which-key-allow-imprecise-window-fit works for me too.


Added a link to troubleshooting guide

Very good idea, thanks! Added this via https://github.com/bkimminich/juice-shop/commit/725b41c8a461c4af9fc8d913f6d1c6f590d4df21.


[BUG] BSONObjectTooLarge when computing App statistics for video datasets

Users have reported getting BSONObjectTooLarge errors on fiftyone==0.16.5 as shown below when trying to load video datasets  with frame-level labels in the App:
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/fiftyone/server/decorators.py", line 33, in wrapper
    response = await func(endpoint, request, data, *args)
  File "/usr/local/lib/python3.9/dist-packages/fiftyone/server/routes/aggregations.py", line 46, in post
    return {"aggregations": await get_app_statistics(view, filters)}
  File "/usr/local/lib/python3.9/dist-packages/fiftyone/server/routes/aggregations.py", line 71, in get_app_statistics
    results = await view._async_aggregate(ordered)
  File "/usr/local/lib/python3.9/dist-packages/fiftyone/core/collections.py", line 7181, in _async_aggregate
    _results = await foo.aggregate(collection, pipelines)
  File "/usr/local/lib/python3.9/dist-packages/fiftyone/core/odm/database.py", line 319, in _do_async_pooled_aggregate
    return await asyncio.gather(
  File "/usr/local/lib/python3.9/dist-packages/fiftyone/core/odm/database.py", line 325, in _do_async_aggregate
    return [i async for i in collection.aggregate(pipeline, allowDiskUse=True)]
  File "/usr/local/lib/python3.9/dist-packages/fiftyone/core/odm/database.py", line 325, in <listcomp>
    return [i async for i in collection.aggregate(pipeline, allowDiskUse=True)]
  File "/usr/local/lib/python3.9/dist-packages/motor/core.py", line 1158, in next
    if self.alive and (self._buffer_size() or await self._get_more()):
  File "/usr/local/lib/python3.9/dist-packages/motor/core.py", line 1626, in _on_started
    pymongo_cursor = future.result()
  File "/usr/lib/python3.9/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.9/dist-packages/pymongo/collection.py", line 2502, in aggregate
    return self._aggregate(_CollectionAggregationCommand,
  File "/usr/local/lib/python3.9/dist-packages/pymongo/collection.py", line 2419, in _aggregate
    return self.__database.client._retryable_read(
  File "/usr/local/lib/python3.9/dist-packages/pymongo/mongo_client.py", line 1525, in _retryable_read
    return func(session, server, sock_info, secondary_ok)
  File "/usr/local/lib/python3.9/dist-packages/pymongo/aggregation.py", line 137, in get_cursor
    result = sock_info.command(
  File "/usr/local/lib/python3.9/dist-packages/pymongo/pool.py", line 710, in command
    return command(self, dbname, spec, secondary_ok,
  File "/usr/local/lib/python3.9/dist-packages/pymongo/network.py", line 161, in command
    helpers._check_command_response(
  File "/usr/local/lib/python3.9/dist-packages/pymongo/helpers.py", line 167, in _check_command_response
    raise OperationFailure(errmsg, code, response, max_wire_version)
pymongo.errors.OperationFailure: BSONObj size: 23974544 (0x16DD290) is invalid. Size must be between 0 and 16793600(16MB) First element: ok: 0.0, full error: {'ok': 0.0, 'errmsg': 'BSONObj size: 23974544 (0x16DD290) is invalid. Size must be between 0 and 16793600(16MB) First element: ok: 0.0', 'code': 10334, 'codeName': 'BSONObjectTooLarge'}

Duplicate of https://github.com/voxel51/fiftyone/issues/1607.


server crashes

I've been running a dedicated server with no problems for a while. a day or two ago i build a refined storage system and some time after i started using it my game started getting really laggy. now, for the first time, it actually crashed.
basically my game has been very unstable and when i right clicked my crafting grid the game just crashed. though the crash report blamed the disk drive so call me confuzzled.
Steps to reproduce:

to reproduce the lagginess all i have to do is play and it persists. ive not been able to reproduce the crash though.
and once i remove the controller to deactivate the network the lag pretty much stops.
but as long as the network is active so is the lag

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

Minecraft: 1.10.2
Forge: FTBserver-1.10.2-<IP_ADDRESS>5-universal
Refined Storage: 1.2.18

Does this issue occur on a server? yes
If a (crash)log is relevant for this issue, link it here:   http://pastebin.com/pcZma873

For lag issues we need a  profiling report:
https://refinedstorage.raoulvdberge.com/wiki/profiling

thanks for the info, ill remember that next time. fortunately, though i cant explain why. the lag has just vanished! If you like i can still submit a profiling report but I'm not sure it'd do much good now.

Not anymore I guess!


Error viewing mitochondrial chromosome reverse strand features

I think this is happening because there are no reverse strand mitochondrial chromosome features in Chado.

Yup, what should we do? can't you display an empty strand (this must be an issue for  other mitochindiral genomes.... what do SGD do?)

https://browse.yeastgenome.org/?loc=chrmt%3A8550..77172&tracks=DNA%2CAll Annotated Sequence Features%2CDoube_strand_break_hotspots%2CXrn1-sensitive_unstable transcripts_XUTs%2CScGlycerolMedia%2C3'UTRs%2CPolII_occupancy_WT&highlight=
that didn't help, they display all on the same strand (there is a reverse strand feature here the origin of replication)
Actually, that suggests a solution, revert to  "display  both strands on a single track view" for mitohondria?

Actually, that suggests a solution, revert to "display both strands on a single track view" for mitohondria?

We can't do it just for mitochondria.  It's all or nothing.
I'll double check the documentation then make a JBrowse issue about the error.
(Unless there are any reverse strand features you could add.  Like the origin of replication?  It kind of makes sense for that to have a forward and a reverse strand feature I think?)

Yes we could do that. The origin of replication is strand independent so it can go on either strand. We just need to find it ;)

I can't find the nucleotide sequence submission at EBI (I tried multiple ways)
but I don't think it must be known or I would have annotated it.
That said, I did spot that the  major and minoe promoters are available here:
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC140500/
could ask if anyone knows

in light of

but I don't think it must be known or I would have annotated it

this is a tangent, but the submission is easy to find at NCBI:
https://www.ncbi.nlm.nih.gov/nuccore/X54421

great we can add
misc_difference 2091
/note="conflict"
/citation=[3]
/replace="g"
 misc_difference 4102
                 /note="conflict"
                 /citation=[4]
                 /replace="g"

REFERENCE   3  (bases 1 to 2900)
AUTHORS   Lang,B.F., Cedergren,R. and Gray,M.W.
TITLE     The mitochondrial genome of the fission yeast, Schizosaccharomyces
pombe. Sequence of the large-subunit ribosomal RNA gene, comparison
of potential secondary structure in fungal mitochondrial
large-subunit rRNAs and evolutionary considerations
JOURNAL   Eur. J. Biochem. 169 (3), 527-537 (1987)
PUBMED   2446871
REFERENCE   4  (bases 3131 to 4580)
AUTHORS   Trinkl,H., Lang,B.F. and Wolf,K.
TITLE     Nucleotide sequence of the gene encoding the small ribosomal RNA in
the mitochondrial genome of the fission yeast Schizosaccharomyces
pombe
to make the bug go away

OK I added these 2  as reverse strand features
misc difference
complement(2091)
/note="conflict"
/replace="g"
/db_xref="PMID:2780299"
and
complement(4102)
/note="conflict"
/replace="g"
/db_xref="PMID:2780299"
(note that since these were originally reported on fwd strand I reverse complemented the conflict)
Let's see if the bug goes away.....

Let's see if the bug goes away.....

I need to add "misc_difference" the contig loader configration.  Which SO term should we use in Chado to represent those new features?  Options include "point_mutation" and "SNP.

Fixed.  Thanks Val!

Now we have a new mitochondrial config file we have this problem again.  The forward strand features look fine.
Val, your two reverse strand "misc_difference" features aren't there any more.  Are they still relevant?  Could you add them back if so?

I removed them, these were just discrepancies between different versions of the sequence. This sequence is the corrected version. At least it's a different version so I assumed no longer relevant (although I did not check this)
@lilindu can confirm.
That's a good check to have in place though- features disappearing !  I didn't know we had that.

The two "misc_difference" features in https://www.ncbi.nlm.nih.gov/nuccore/X54421 actually correspond to two of the 20 errors listed in Table 1 of Tao et al. 2019. I guess the authors who submitted X54421 to GenBank had suspected possible errors at these two positions but decided to only add a note of "conflict" because they were not absolutely certain about which nucleotide is correct.

Oh I see now. I did not realize that your comment was in this old ticket. I  only read the comment not the history- so that is why we had the conflicts flagged!
I guess this is really a JBrowse issue?

This is what I see in my default gene page view because of  the mitochondrial genome feature depth

Is it possible to default so that the  vertical scroll bar if it appears  is set to the top instead of the bottom?

Is it possible to default so that the vertical scroll bar if it appears is set to the top instead of the bottom?

I don't know how to fix that.  Have you seen it happen on pages without the JBrowse error?

I think it only occurs with the mito genome because the depth is bigger
see  cdc2
https://www.pombase.org/gene/SPBC11B10.09
https://www.pombase.org/gene/SPBC83.15
the scroll bar is there, and at the bottom, but it doesn't matter here.
but for mito
https://www.pombase.org/gene/SPMIT.09
there are ~ 30 features/genes in 10kb
I don't think we are likely to see thin in the nuclear genome (except when we add  @bahler s 15,000 ncRNA's it could be a problem....

At the centromere it happens
https://www.pombase.org/gene/SPCTRNAVAL.09
but it doesn't seem so bad because you don't see the error, you see at least some features.
I'm tempted to just create a dummy feature on the mito reverse strand..

This is probably due to the request for https://www.pombase.org/jbrowse/data/tracks/PomBase reverse strand features/mitochondrial/trackData.json returning a status 200 instead of a 404 error

Thanks for the diagnosis Colin.  I'll fix that.
Have a great weekend.

That fixed things.  Thanks Colin.

That's much better, we don't have the big error,
but  we still don't see the genes  for example here:
https://www.pombase.org/gene/SPRRNA.01
because the right hand scroll bar defaults to the bottom. Are we sure that there isn't a way to make it default to the top?

closing so I don't need to read the entire ticket again, I'll open a new ticket for the small outstanding issue to try to make the scroll bar default to the top on our gene pages.
https://www.pombase.org/gene/SPRRNA.01
because the right hand scroll bar defaults to the bottom. Are we sure that there isn't a way to make it default to the top?


"Note, that by providing native, Prisma Client automatically resolves rhel-openssl-1.0.x"

While trying to deploy an app using Prisma Client to Netlify I keep getting this error message:
{"errorType":"Error","errorMessage":"\nInvalid `prisma.()` invocation in\n/var/task/script.js:5:36\n\n\n\nQuery engine binary for current platform rhel-openssl-1.0.x could not be found.\nPrisma Client looked in<EMAIL_ADDRESS>but couldn't find it.\nMake sure to adjust the generator configuration in the schema.prisma file:\ngenerator client {\n  provider      = \"prisma-client-js\"\n  binaryTargets = [\"native\", \"rhel-openssl-1.0.x\", \"rhel-openssl-1.0.x\"]\n}\nPlease run prisma2 generate for your changes to take effect.\nNote, that by providing `native`, Prisma Client automatically resolves `rhel-openssl-1.0.x`.\nRead more about deploying Prisma Client: https://github.com/prisma/prisma2/blob/master/docs/core/generators/prisma-client-js.md","trace":["Error: ","Invalid `prisma.()` invocation in","/var/task/script.js:5:36","","","","Query engine binary for current platform rhel-openssl-1.0.x could not be found.","Prisma Client looked in<EMAIL_ADDRESS>but couldn't find it.","Make sure to adjust the generator configuration in the schema.prisma file:","generator client {","  provider      = \"prisma-client-js\"","  binaryTargets = [\"native\", \"rhel-openssl-1.0.x\", \"rhel-openssl-1.0.x\"]","}","Please run prisma2 generate for your changes to take effect.","Note, that by providing `native`, Prisma Client automatically resolves `rhel-openssl-1.0.x`.","Read more about deploying Prisma Client: https://github.com/prisma/prisma2/blob/master/docs/core/generators/prisma-client-js.md","    at PrismaClientFetcher.request (/var/task/node_modules/@prisma/client/index.js:62:23)"]}

What does "Note, that by providing native, Prisma Client automatically resolves rhel-openssl-1.0.x" mean here? Resolve to what?
(Why the duplicated rhel-openssl-1.0.x in binaryTargets btw?)

I think it refers to the binary name for the current target. But I agree we can improve this error and make it clear.

Thanks a lot for reporting 🙏
This issue is fixed in the latest alpha version of prisma2.
You can try it out with npm i -g prisma2@alpha.
In case it’s not fixed for you - please let us know and we’ll reopen this issue!


[FEATURE] full support for eventDefinition / CSCLSROZ-330

check components list in this user story for relevant types (status checked across all metadatatype files on 2020-11-19)

Duplicate of #609


Upgrade controller runtime to v0.10.3

Close. Because the resources-operator is using controller-runtime:v0.11.0.


-pw password is not working. Still asking for password with putty 0.71

-pw password is not working. Still asking for password with putty 0.71

I am also facing same issue after getting latest putty.

Check the options dialog  in superputty to ensure the checkbox to allow unsecure passwords on the command line is checked.
Jim

@jimradford  that for the help . It worked, i think upgrade might have reset the option.

Bumped into this problem with v<IP_ADDRESS>, It takes me a while to find the option mentioned above, it is located at Options > GUI > Security, how odd is that!


(ME Bridge) Cherry-Pick AE2 Things DISK Drive Support from 1.18 to 1.19.2/1.19.3

Describe your idea
A few friends and I are currently doing a playthrough of ATM 8 with AE2 Things. We ultimately decided to use DISK Drives. We're wanting to write a script to essentially show live the percentage space used in our system. Unfortunately, we're not able to due to the DISK Drives not being detected.
After a glance, it looks like support got added in 1.18 but it didn't get cherry-picked into the 1.19.x versions. Is there a way this could be cherry-picked in?
Describe alternatives you've considered if you've any
No response
Additional context
No response
Linked Issues
No response

AE2 Things does not seem to have a 1.19.2 version? https://www.curseforge.com/minecraft/mc-mods/ae2things/files/all
Is there another mod with these DISK drives?

The main mod is a Fabric mod though there is a Forge port which is in use and is updated to 1.19.2
https://beta.curseforge.com/minecraft/mc-mods/ae2-things-forge/files/4367610

I did not catch that, thanks

AdvancedPeripherals-0.7.25r.zip
If you want to test it, you're free to go.
Uploading it on the server only would be sufficient.
Unzip the file before using.

Looks like it's working now with that test jar, thanks for the quick response, appreciate it!

@SirEndii Apologies for the ping/reopen, though I found another part that wasn't cherry-picked in: https://github.com/SirEndii/AdvancedPeripherals/blob/327960be1a064a6b1e0074e49f485334db4889c6/src/main/java/de/srendi/advancedperipherals/common/addons/appliedenergistics/AppEngApi.java#L337
Could you take a look and cherry-pick whenever you get a chance? Thank you!


swo_notification resource webhook error

There is what looks like a typo on the documentation and somewhere in the provider
https://registry.terraform.io/providers/solarwinds/swo/latest/docs/resources/notification#auth_header_hame
when using the resource the following error is provided

│ An unexpected error was encountered trying to convert tftypes.Value into provider.notificationSettingsWebhook. This is always an error in the provider. Please report the following to the provider developer:
│
│ mismatch between struct and object: Struct defines fields not found in object: auth_header_name. Object defines fields not found in struct: auth_header_hame.

@jaimeviloria Thanks for pointing this out. Looks like a simple typo. We'll fix this and get it out in the next release.

Fixed in next release. Thanks!


Error adding domain!

I installed the postal, according to procedure, I added my organization and my mail server, when I add a domain is generating the following error https://snag.gy/qLJdoI.jpg! can anybody help me? already had set up another postal without problems.

You will have to check the files in /opt/postal/log to find out what the issue is.

@willpower232 Thanks for answering me!
I was already checking the logs but I could not locate this problem yet, I found it very strange, because the whole system is working, until the time to add the domain! I'll try to look for something, if you have any idea what I can do to guide me! Thank you.

@willpower232 I was able to solve it, it was some configuration in the dns part, I re-made the settings and it worked!
Can you tell me how to send an email to the user of an organization where I added it? It looks like it does not send the email to the user!

If you've added a user to an organisation, you'll have to communicate with them directly. Postal doesn't have welcome emails or anything like that. If you want Postal to send an email, you have to configure your application to send from it.

@willpower232 you mean it only sends the email with the verification url ?
@sidneydevelop is this what you meant? You could change the text ...

@willpower232 @navinp Yes, I'm talking about the verification URL, I was able to work with only the SMTP data from sendgrid, I'm not able to use the sending of the URL by the server itself.
I have done all the settings of SPF, DKIM, he is doing the shipments without problems, my question and when I create a mail server and I use the credentials inside the postal.yml he is not doing the sending.
I'm doing the configuration tests with this command postal test-app-smtp myemail

about adding domains I could fix by redoing the dns configuration in postal.yml


Location of setting has changed

The setting is now at File --> Preferences --> Color Theme

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

ID: 97e23c15-7abd-d973-48c0-e4b23e305c5c
Version Independent ID: 97329301-f6ac-4cba-8b85-a958a0bfc1a5
Content: Set color theme and fonts - Visual Studio
Content Source: docs/ide/quickstart-personalize-the-ide.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @jillre
Microsoft Alias: jillfra

Hi @orfeasa Could you be confusing Visual Studio Code, which does use File > Preferences > Color Theme, with Visual Studio IDE? The topic referenced in this issue is for VS IDE and changing the color theme is still done with the Tools > Options dialog as of release 16.3.

Ah yes, sorry about that 🙂
On Tue, 3 Dec 2019 at 17:42, Greg Van Liew<EMAIL_ADDRESS>wrote:

Hi @orfeasa https://github.com/orfeasa Could you be confusing Visual
Studio Code, which does use File > Preferences > Color Theme, with Visual
Studio IDE? The topic referenced in this issue is for VS IDE and changing
the color theme is still done with the Tools > Options dialog as of release
16.3.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/visualstudio-docs/issues/4419?email_source=notifications&email_token=ACLX6DMRHSX5A2Z2APDKPGLQWZ46VA5CNFSM4JUTPI3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFZZ5AQ#issuecomment-561225346,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACLX6DM7TC5S6HRXQEGKYBLQWZ46VANCNFSM4JUTPI3A
.

No worries. Closing.


Wrong (copy/pasted?) link

In https://learn.microsoft.com/en-us/azure/applied-ai-services/form-recognizer/managed-identities-secured-access?view=form-recog-3.0.0#prerequisites the last prerequisite (An Azure data science VM optionally deploy a data science VM in the virtual network to test the secure connections being established.) has the same link as the previous item.
Instead of https://portal.azure.com/#create/Microsoft.VirtualNetwork-ARM you probably want https://portal.azure.com/#create/microsoft-dsvm.ubuntu-20042004 and/or https://portal.azure.com/#create/microsoft-dsvm.dsvm-win-2019winserver-2019 (or the corresponding aka.ms if there are any).

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

ID: 65c735bc-8097-46e0-4b5f-f25f362d862e
Version Independent ID: 8972d0a3-5d9e-be28-2141-23a087380f10
Content: Configure secure access with managed identities and private endpoints - Azure Applied AI Services
Content Source: articles/applied-ai-services/form-recognizer/managed-identities-secured-access.md
Service: applied-ai-services
Sub-service: forms-recognizer
GitHub Login: @laujan
Microsoft Alias: vikurpad

Hi @sopelt, Thank you for your feedback. Per your suggestion, we've updated the link in the prerequisite section of the  Configure secure access with managed identities and private endpoints - Azure Applied AI Services | Microsoft Learn article. The change should be reflected later today. Thanks again! 🙂

#sign-off


refactor(e2e): stop using deprecated knuu methods

Attempts to address https://github.com/celestiaorg/celestia-app/issues/3779 by replacing usage of deprecated Knuu methods with their non-deprecated versions. Enables staticcheck in the e2e package so that linters can inform us if deprecated methods are used.
cc: @smuu for awareness

https://github.com/celestiaorg/knuu/blob/32b98ab58d4bd3b3141d95884f963d5da3167af2/pkg/knuu/knuu.go#L157-L159 exists on v0.14.0 but doesn't exist on main so I expect this error to go away when there is a new knuu release cut from main. cc: @smuu

Closing in favor of https://github.com/celestiaorg/celestia-app/pull/3873


PR: Don't load files twice at startup and remove multiple calls to document_did_open

This PR does the following:

Avoid opening files twice at startup (this problem has been present since the release of Spyder 3!).

That fixes code completion for languages other than Python for the first opened file of that language (linting was working fine, but code completion was not).
It also fixes the very strange order seen in the "Recent files" menu after Spyder is started.

Don't call document_did_open twice when opening a file. That was also messing with other LSP servers.
Perform a bit of refactoring to make clearer what several code completion methods do and unify names between codeeditor, editorstack and editor plugin.
Correctly register that an LSP client was started the first time.

TODO:

[x] Check if document_did_open is called after reloading a file that was changed outside Spyder (it is not, which is really good!).

@dalthviz, please help me to review this one.

@dalthviz, I implemented your suggestions, so this is ready for another review.


File Cache driver issue introduced in 5.5 when running seeds

Laravel Version: 5.5.19
PHP Version: 7.0.22
Database Driver & Version: MySQL 5.7.20

Description:
When the file cache driver is selected, I sporadically get the following error when running db:seed or migrate:refresh --seed:

error:Call to undefined method App\Role::firstOrCreate()

I'm quite certain this was introduced in Laravel 5.5. I've been using the same Role Seeder class on several Laravel 5.4 projects, and I first noticed it when I created a Laravel 5.5 project several weeks back.
See my Stack Overflow question for more details on the problem. After several hours, I realized after running cache:clear several times seemed to make the seeder run successfully sometimes. Then I realized switching the cache driver to redis resolved the issue completely.
Steps To Reproduce:
I found the original problem on Linux with the version information specified above, however I created the following Steps using PHP 7.1.10 on Windows 64 bit.

composer create-project --prefer-dist laravel/laravel laravel-bug
Follow Entrust Installation and Configuration steps.
When running the command: php artisan entrust:migration, you will get the following error:

Method Zizaco\Entrust\MigrationCommand::handle() does not exist

Edit vendor\zizaco\entrust\src\commands\MigrationCommand.php and change public function fire() to public function handle()
Run php artisan entrust:migration again.
Create a seeder: php artisan make:seeder RoleSeeder
Edit database/seeds/RoleSeeder.php to be the following:

<?php

use Illuminate\Database\Seeder;
use App\Permission;

class RoleSeeder extends Seeder
{
    /**
     * Run the database seeds.
     *
     * @return void
     */
    public function run()
    {

        //Application User: All users have this role be default
        $r = \App\Role::firstOrCreate(['name'=>'app-user'],
            [
                'name'         => 'app-user',
                'display_name' => 'All users of the application',
                'description'  => 'Uses the application',
            ]
        );

    }
}

run php artisan migrate
run php artisan db:seed --class=RoleSeeder
An error will be printed. If you do not see the error, try running the above commands a couple times:

  [BadMethodCallException]
  Call to undefined method App\Role::firstOrCreate()

In .env file, set CACHE_DRIVER=redis
run php artisan db:seed --class=RoleSeeder. The error will not appear.

I put code that demonstrates the problem here: https://github.com/TrieBr/laravel-bug
You should be able to just pull that code and then perform steps 8 through 12 above to demonstrate.

My first thought; does this occur on your own models? Entrust does not, like you've described, support Laravel 5.5 yet.

I was able to isolate the problem. Entrust is not the problem.
If I change the Role class to this:
flush();
        return $result;
    }
}
```

Since the `file` cache store does not handle tagging, the following exception is thrown:
```
  [BadMethodCallException]
  This cache store does not support tagging.
```

However, for some reason, the Exception handling system is catching the BadMethodCallException and and printing the wildly incorrect/misleading message:

```
  [BadMethodCallException]
  Call to undefined method App\Role::firstOrCreate()
```

As I mentioned, this is seems definitely new to Laravel 5.5, because I've seen the `This cache store does not support tagging` exception being reported  many times when working with Laravel 5.4/Entrust.

Handled in https://github.com/laravel/framework/pull/21929
Thanks


Add retryDelay option

resolve #24

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove assets-related dependencies in Lobsters benchmark

I'm not sure why we didn't see this problem earlier, including on literally the same host machine. I'm not seeing it with either yjit-bench or yjit-metrics, even after I remove the relevant gems. So: not sure exactly what's happening here.
I've removed the things that clearly depend on execJS -- I think that should get rid of the error we're currently getting in CI, where it can't find a JS runtime for execJS. We're already not building assets, nor serving them.

Can I ask why it needs a JS runtime? It's not executing JavaScript code, is it?

JS is used during asset builds. It's not executing JS during the benchmark. In fact for this benchmark, we're not even doing an asset build ahead of time. But we are running in prod mode, so it tried to make sure that it could build assets, even though we aren't using them here.

Thank you for taking the time to do this Noah 🙏


Contour._get_segments does not handle all off-curves contours

This is more a corner case issue than anything dramatic, but if you have a contour with only off-curves, the method returns an empty list.
I rewrote the method at https://github.com/madig/HTLetterspacer/blob/33b9291/src/htletterspacer/core.py#L432-L460 from the code in PointToSegmentPen and wrote a property test at https://github.com/madig/HTLetterspacer/blob/reduce-better/tests/test_segmentation.py. It ensures that all invariants hold no matter what point list you throw at it. Maybe you can think of more invariants?

should be a list with a single segment containing all the off curve points. (PR will follow)

This is fixed, closing


Weird detection responses

Hey, thank you for creating this library, I think it'll be at the core of the next app I'm building..
I tried to make this work alongside React-native-camera, the process was pretty straightforward but I ran into errors while logging out the output of the detection.
For any image, the On Device Response is either gibberish or empty. And the cloud response fails with a promise rejection.
Here's what it looks like:

Would appreciate some help with this. Thanks again!

Have you added google-service in the application to have your mlkit authentication? and the cloud method only works if you have the blaze package of the signed firebase in your account.

Ah! Yes, I do have google-services.json in my android/app folder. Didn't know about the Blaze package... I've compared the on-device text recognition to other RN npm packages which also use Google Vision, and even though this seems "simpler" to implement, I still see gibberish results for the same image. Is this because of a particular on-device model you're using? Would love to know more.


src: files centralized inside licenses directory

Connects to #186

Coverage increased (+1.2%) to 82.184% when pulling 0e92656cccf1911f95bafa7637f3de135f13ba35 on helio-frota:pr into 5ced1416d87c5ed33eb618698e76073390037fa7 on bucharest-gold:master.


drivers: audio: dmic_nrfx_pdm: Add multi-instance PDM and support for prescaler

Upstream PR: https://github.com/zephyrproject-rtos/zephyr/pull/79177

@anangl Please review


[bug]  Depracted warnings when installing @web3modal/wagmi@latest package

Link to minimal reproducible example
none since it occurs by only installing the package not using it
Summary
Describe the bug
When installing @web3modal/wagmi@latest with npm i @web3modal/wagmi@latest`
I got warnings about deprecated packages being used.
Expected Behavior
The package @web3modal/wagmi@latest is installed and no warnings are reported.
Current Behavior
The package @web3modal/wagmi@latest is installed and the following warnings are reported:
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained.
Please use @babel/plugin-transform-optional-catch-binding instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained.
Please use @babel/plugin-transform-numeric-separator instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained.
Please use @babel/plugin-transform-nullish-coalescing-operator instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained.
Please use @babel/plugin-transform-class-properties instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained.
Please use @babel/plugin-transform-optional-chaining instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained.
Please use @babel/plugin-transform-async-generator-functions instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained.
Please use @babel/plugin-transform-object-rest-spread instead.
npm WARN deprecated<EMAIL_ADDRESS>Motion One for Vue is deprecated.
Use Oku Motion instead https://oku-ui.com/motion
npm WARN deprecated<EMAIL_ADDRESS>This project has moved to @types/webextension-polyfill

Are there relevant warnings? If so would it be possible to replace the packages as suggested by npm.
Steps to reproduce
1.In a terminal install the package via  npm i @web3modal/wagmi@latest
Expected behavior
The package @web3modal/wagmi@latest is installed and no warnings are reported.
List of related npm package versions
    "@web3modal/wagmi": "^4.1.1"

These are coming from Wagmi I think


Implement cost_pie.py into the process package

https://github.com/ukaea/PROCESS/pull/2871

Fixed in #3266


Allow to remember password longer.

That would be nice to have the possibility to remember the password for like 5 or 8 hours. That's useful for people at work for example :)

Yes please! :v:

That seems reasonable.  I think an advanced option that lets you customize the period would work well.

Another option would be to implement something like enter the last 3 characters of the password after the database has closed automatically.  If the wrong characters are entered the entire password must be opened. Keepass2Android uses this feature


grpc,fabric-client,fabric-ca-client installation failed

Context
I did the following steps:
1.git clone the caliper source code to my server, then cd caliper folder
2.execute command "npm install". It is successful

3.execute command "npm run fabric-v1.1-deps". It is also successful.

4.use npm list to check the installation of grpc, fabric-client,fabric-ca-client. It seems that they are not successfully installed.

Expected Behavior
grpc, fabric-client,fabric-ca-client are successfully installed
Actual Behavior
npm list shows nothing
@houqinghui could you please help with this issue? Thank you!

After step 1~4, I executed "node benchmark/simple/main.js", and it failed.
Then I installed grpc,fabric-client,fabric-ca-client manually by the following command:
npm install<EMAIL_ADDRESS>--unsafe-perm
npm install<EMAIL_ADDRESS>--unsafe-perm
npm install<EMAIL_ADDRESS>--unsafe-perm
And then execute "node benchmark/simple/main.js" again. This time, the test is successful, and the test report is generated successfully.

So this result demonstrated that command "npm run fabric-v1.1-deps" actually didn't install grpc,fabric-client,fabric-ca-client successfully. And there is not any error log.

@CoreyLin The npm run script uses the --no-save flag, so the packages are not added to the package.json file. Probably that's why the npm ls command doesn't pick them up.
But if you execute ls node_modules/ | grep fabric then you should see the packages.

@aklenik Got it. Thanks. But why "--no-save" flag is used here? In this way, the grpc,fabric-client,fabric-ca-client are not installed. This will directly lead to testing failure.

Indeed, the npm install documentation shows that:
--no-save: Prevents saving to dependencies.
But this would require caliper user to manually install grpc,fabric-client,fabric-ca-client. It seems not so reasonable.

Don't forget that Caliper supports multiple blockchain platforms. Installing every dependency of every platform SDK would be confusing/wasteful for the users. So Caliper has some core dependencies (needed by the core code-base) added to the package.json and has scripts to install Fabric/Sawtooth/Burrow-specific dependencies.
The --no-save flag is used in these scripts, so they're not added to the package.json file after install and we won't commit/push them accidentally :)
But they're installed and are available during the execution of Caliper.
(N.B. I also don't like this solution, but couldn't come up with a better yet.)

OK, I can understand the design thought. The dependencies are categorized to two types: 1.core 2.platform specific. I think it is good.
However, you mentioned "But they're installed and are available during the execution of Caliper.". At least in my server it doesn't work, unless I manually install grpc,fabric-client,fabric-ca-client again...
So maybe in the documentation, this additional manual installation steps should be mentioned so that other users can prevent encountering such problem...

The Pre-requisites section states, that the additional blockchain SDKs must also be installed, and the platform-specific doc sites detail this install.
So for Fabric, the setup is the following:
git clone https://github.com/hyperledger/caliper.git
cd caliper
npm i
npm run fabric-v1.2-deps

If these steps work for you, then this issue can be closed.
(The issue of easy install is an other question of course :) )

OK, thanks very much. I will close this issue.


fix: bump mirror node in FST helm chart to 0.111.1

Description
This pull request changes the following:

bump mirror node in FST helm chart to 0.111.1

Related Issues

required by https://github.com/hashgraph/solo/pull/518

:tada: This PR is included in version 0.31.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


About contrast mode

What is the difference between all and one of the contrast modes?

Hi @HobbitLong ,
Thank you for your great contribution in this task. I was wondering the same question with @Hiiragi0107 . It seems in a supervised contrastive mode. It is not necessary to provide two views(crops) for each sample. Aligning features of the same class to be neighbors and distancing features from different classes should also improve the performance for supervised contrastive setting. So could you help to elaborate a littble bit on the experimental difference between 'contrasting with 1 view with labels' and  'contrasting with two views with labels' ?


Add service proc macro

The purpose of this PR is to simplify the process for defining services and characteristics in TrouBLE, as laid out in this issue: #130.
Services are defined as a struct decorated with the #[gatt_service(uuid = ...)] attribute and fields within the struct can be decorated with #[characteristic(<args>)] attributes to define them as characteristics.
In a similar way, the gatt server is defined as a struct with the #[gatt_server] attribute, where each of the fields is a service.
The server is then instantiated with the ::new() function which is generated by the attribute macro.
This PR lays the foundation for expanding the functionality of the server, services and characteristics such that all access to characteristics (e.g. set, get, notify, indicate) can be done through methods on the characteristics, accessed through the server.

@petekubiak Could you split out the uuid parser/generator macro as separate PR?
This would immensely improve implementing services with 128-bit Uuids:
    let mut uart_service = table
        // #[gatt_service(uuid = "6E400001-B5A3-F393-E0A9-E50E24DCCA9E")]
        .add_service(Service::new(Uuid::Uuid128([
                    0x9e, 0xca, 0xdc, 0x24,
                    0x0e, 0xe5, 0xa9, 0xe0,
                    0x93, 0xf3, 0xa3, 0xb5,
                    0x01, 0x00, 0x40, 0x6e,
            ])));

    // #[characteristic(uuid = "6E400002-B5A3-F393-E0A9-E50E24DCCA9E", write)]
    let _ = uart_service.add_characteristic(Uuid::Uuid128([
                    0x9e, 0xca, 0xdc, 0x24,
                    0x0e, 0xe5, 0xa9, 0xe0,
                    0x93, 0xf3, 0xa3, 0xb5,
                    0x02, 0x00, 0x40, 0x6e,
            ]),
            &[
                CharacteristicProp::Write,
            ],
            &mut rx,
        );

You can write .add_service(Service::new(Uuid::Uuid128(0x6E400001_B5A3_F393_E0A9_E50E24DCCA9Eu128.to_le_bytes()))). No macro needed.

Following on from that my hope is that you wouldn't even need to call .add_service() or .add_characteristic() as the attribute macro takes care of that for you when you call <Server name>::new() (Server name being the name of the struct you have decorated with the #[gatt_server] attribute).

Looks great, thanks the work on this! I've left a few inline comments.
I noticed a commend saying the pub server field would be non-public with additional changes. Do you wish to merge this now or make additional changes to it?

I think we'd like to merge this one first and then do further development in a new PR (avoids this one getting too large :) )

Looks great, thanks the work on this! I've left a few inline comments.
I noticed a commend saying the pub server field would be non-public with additional changes. Do you wish to merge this now or make additional changes to it?

I've decided to set the visibilities back to what they were and instead implement getter functions for the fields I need. At least that way they are immutable.

/test

The new integration test seems to be failing, does it pass locally? https://github.com/embassy-rs/trouble/actions/runs/11340899524/job/31538139912

The new integration test seems to be failing, does it pass locally? https://github.com/embassy-rs/trouble/actions/runs/11340899524/job/31538139912

Aha, we don't actually have a rig to run locally (I think I'll try to get one set up). We thought that the tests would run automatically once the PR was converted from a draft.

Thanks for the information, and thank you for adding me!
On Tue, 15 Oct 2024, 09:22 Ulf Lilleengen, @.***> wrote:

The new integration test seems to be failing, does it pass locally?
https://github.com/embassy-rs/trouble/actions/runs/11340899524/job/31538139912
Aha, we don't actually have a rig to run locally (I think I'll try to get
one set up). We thought that the tests would run automatically once the PR
was converted from a draft.
Ah, that's fine. So basically if you have 2 UART HCI dongles (could be
nrf52840 dongle with zephyr or picos, or esp32s), you can run them using
RUST_LOG=trace TEST_ADAPTER_ONE=/dev/ttyACM0 TEST_ADAPTER_TWO=/dev/ttyACM1
cargo test ... -- --nocapture
The reason it isn't run automatically is that the test rig is in my home
network, so for now it requires manual triggering and not anyone on github.
I've added 'petekubiak' to the list of users who can run the /test command,
so feel free to do that manually if you're not able to have a local setup
running.
—
Reply to this email directly, view it on GitHub
https://github.com/embassy-rs/trouble/pull/131#issuecomment-2413213515,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI6FGUCD4P47G24WTX62ZK3Z3TGFJAVCNFSM6AAAAABPMEVXLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJTGIYTGNJRGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Would it be possible to add @jamessizeland as well?

/test

/test

/test

Looks like I broke the bot config, I need to look into that. For now I've triggered it manually.

ok still an issue to fix looks like!

/test

/test


h264: add new encoder setting MaxBitRate.

@llyzs As mentioned in #2600, the iMaxBitrate should be UNSPECIFIED_BIT_RATE, otherwise if the encoded frame is bigger than this value, the frame will get skipped. I think the value UNSPECIFIED_BIT_RATE was just fine.

@llyzs if a frame gets skipped, the result (for example in a terminal if u wanna see the last command, the command may not be displayed if this frame got skipped) is that u dont see the changes on the client. But we need to send a frame we encode in any case, even its too big, then we wait a few frames (future bucket use) before we encode the next frame.

The iMaxBitrate has UNSPECIFIED_BIT_RATE(0) as default value, however when I set it to a larger value, my test result is that as long as I keep bEnableFrameSkip as 0, openh264 never drops a frame even the generated frame is very large. In fact our frontend does NOT allow frame drops.
However this seems to have no effect either. openh264 does not seem to try even a little harder to further compress the image. I set both iBitrate and iMaxBitrate to 60Mbps and use 30fps, the encoded result of a series of random pixel frame is 7xxK bytes per frame - that is 200Mbps already.


Manually setting advertised addresses not possible due to incorrect tpl

What happened?
Im currently trying to setup an HA cluster using Redpanda as a subchart to our chart (https://github.com/united-manufacturing-hub/united-manufacturing-hub).
Our cluster is running using 3 replicas and internal traffic to the redpanda pods works fine.
When i however try to connect externally, i get an error from sarama kafka, hinting that the advertised hosts are incorrect (it tries to connect to the kubernetes internal URL).
I therefore try to set the addresses in the values.yaml.
What did you expect to happen?
It should install and set the advertised hosts correctly.
How can we reproduce it (as minimally and precisely as possible)?. Please include values file.

Error:
Error: INSTALLATION FAILED: template: united-manufacturing-hub/charts/redpanda/templates/statefulset.yaml:120:23: executing "united-manufacturing-hub/charts/redpanda/templates/statefulset.yaml" at <include "advertised-host" (mustMerge $tmplVals (dict "port" $port))>: error calling include: template: united-manufacturing-hub/charts/redpanda/templates/_helpers.tpl:537:12: executing "advertised-host" at <tpl (.values.external.domain | default "") $>: error calling tpl: cannot retrieve Template.Basepath from values inside tpl function: : "BasePath" is not a value

Values:
  redpanda:
	statefulset:
	  replicas: 3
	  updateStrategy:
		type: RollingUpdate
	  budget:
		maxUnavailable: 1
	resources:
	  cpu:
		cores: 5
		overprovisioned: true
	  memory:
		enable_memory_locking: true
		container:
		  max: 8Gi

	storage:
	  persistentVolume:
		enabled: true
		size: 700Gi

	config:
	  cluster:
		auto_create_topics_enabled: true
		log_compression_type: zstd
	  tunable:
		default_topic_partitions: 6
		retention_bytes: None
		delete_retention_ms: 604800000
		default_topic_replications: 3
	external:
	  type: LoadBalancer
	  addresses:
		- <IP_ADDRESS>
		- <IP_ADDRESS>
		- <IP_ADDRESS>
		- <IP_ADDRESS>

Anything else we need to know?
No response
Which are the affected charts?
Redpanda
Chart Version(s)

Tested on redpanda-3.0.9 and redpanda-5.3.3

Cloud provider

 None, setup using k8s on bare-metal

This seems to be a known issue with helm:
https://github.com/helm/helm/issues/5979
https://github.com/helm/helm/issues/11168


Notation for non-traditional f-plane is obscure

Right now the "non-traditional" f-plane struct uses f and f' to denote what I presume are the z and y components of the rotation axis:
https://github.com/climate-machine/Oceananigans.jl/blob/f080635b93bdab9da7d1189ed21f27523c0ff810/src/Coriolis/f_plane.jl#L59
I think a better notation would be
struct NonTraditionalFPlane{T, T}
    fz :: T
    fy :: T
end

This is more explicit and follows the standard convention that the components of a vector are appended with direction.

The documentation is also incorrect as the rotation axis is not arbitrary. It must be in the y-z plane.

The dynamics functions are not tested, either because the functionality is not used in time-stepping. This is also a problem for BetaPlane.

I have a test case for beta-plane incoming.
Is there a way to test x_f_cross_U et al?

Is there a way to test x_f_cross_U et al?

Yes: construct a model with the given feature and then performing a time-step.
I guess ideally we would form a giant matrix representing all possible model configurations and time-step them all once. This would be expensive.
Maybe we should just loop over each physics specification individually and cross our fingers that there's no bad interactions (I can already tell this would be naive, for example, when a turbulence closure depends on buoyancy).

I'm going to close this, as the primary concern was addressed by #617. We can discuss better testing on another issue.


[Bug]: Responsiveness issue and Theme switcher not working

Bug Description
The website is not responsive for Mobile and tablets and Theme switcher not Working
Provide a detailed description of the bug
The navbar is not shown properly in the Mobile view and the registration/login container is not aligned properly.
The Theme switcher (Light Mode/ Dark Mode) is not working.
Expected Behavior
I would like to fix these two issues:

Responsiveness for other devices.
Theme switcher button functionality.
so the user can get a good experience on all devices.

What browsers are you seeing the problem on?
Chrome
Put here any screenshots or videos (optional)
Mobile View :

Theme Switch:

By submitting this issue, you agree to

[X] I agree to follow this project's Code of Conduct
[X] I’ve read all the issues in the issue section, and this has not been reported yet.

Other Information

[X] I'm a GSSoC '24 Extended contributor
[X] I'm a Hacktoberfest '24 contributor
[X] I am willing to work on this issue (optional)

@maniyaom Please assign me this issue


implement framework for site-specific fixes

Describe the solution you'd like
mozilla's readability is great, but it has a lot of issues where it's heurestics cause it to miss some paragraphs of text.
for example, here, the first paragraph isn't extracted
i've opened an issue on their repo a long time ago and it wasn't fixed. by the looks of it, they get a lot of similar issues.
i suggest creating an framework internally in the extension to accomodate site specific fixes:
this is how i did it for my web clipper, specifically the HTMLRewriter class, which is simple in nature but allows easy specifying of site-specific fixes.
feel free to use a similar approach, or a completely different one, if necessary.
another option could be forking the readability extension, but that just increases maintainance burden

There is already support to bypass readability in templates using {{fullHtml}} and {{selectorHtml}} so this doesn't seem necessary. In the long-term maybe we would change the {{content}} variable to something more clever and remove Readability altogether.


[SPARK-17124][SQL] RelationalGroupedDataset.agg should preserve order and allow multiple aggregates per column

What changes were proposed in this pull request?
This patch fixes a longstanding issue with one of the RelationalGroupedDataset.agg function. Even though the signature accepts vararg of pairs, the underlying implementation turns the seq into a map, and thus not order preserving nor allowing multiple aggregates per column.
How was this patch tested?
Added a test case in DataFrameAggregateSuite.

Test build #63978 has started for PR 14697 at commit bd64ade.

Test build #63978 has finished for PR 14697 at commit bd64ade.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63978/
Test PASSed.

@hvanhovell have time to take a look?

cc @cloud-fan too

Test build #64080 has started for PR 14697 at commit 5f8930e.

Test build #64080 has finished for PR 14697 at commit 5f8930e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64080/
Test PASSed.

Merged build finished. Test PASSed.

what do you mean by allow multiple aggregates per column in the title?

For example, run both count and sum for a column. Let me update the description.

I  updated the description.

thanks, merging to master/2.0!
@petermaxlee do you mind open another PR for 1.6? thanks!


Add support for CSV output

Fixes #3
Example of how it can work
aws-cct --output csv

To test:
go build
./aws-cct --output csv
# Pipe into CSV file
./aws-cct --output csv > test.csv

Kept the output away, although I confirmed it does not have any \ characters to escape the commas and properly replaces the thousand separator to "" so it doesn't have commas.

cc @mwarkentin

@rgoomar awesome, thanks!


fix typo in readme

Describe the change
What does this Pull Request do?
fixes interpolation typo on readme
Why are we doing this?
Any related context as to why is this is a desirable change.
Benefits
How will the library improve?
Drawbacks
Possible drawbacks applying this change.
Requirements
Put an X between brackets on each line if you have done the item:
[] Tests written & passing locally?
[] Code style checked?
[] Rebased with master branch?
[x] Documentation updated?

Coverage decreased (-0.3%) to 96.85% when pulling 42c24d140e3644d0e01895076c443e3b72ba32e5 on hai14894:fix-typo-in-readme into 65187af24f89dd15b6c7be67dff2fee381b647e0 on piotrmurach:master.

Thanks for spotting this issue. However, this should be the other way around. This is not string interpolation but variable substitution. So #{in} should become %{in},


Where filter doesn't work

Where filter doesn't apply with IncludeRef:
var issues = dbContext.Issues.Where(x => x.ApplicationId == Id).IncludeRef(x => x.Classification).ToList();

fixed


correct node, go, java versions

Node: v16.17.1
Go: 1.19.9
Java: 1.8.0-322
Go installation in <IP_ADDRESS> is broken: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/branch-ci-stackrox-stackrox-release-3.73-images/1660986067840405504.
In <IP_ADDRESS>, Node version is incorrect: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/39623/rehearse-39623-pull-ci-stackrox-stackrox-release-3.73-images/1660987468054269952.
After merge, this can be released as <IP_ADDRESS>.
Then mirror to OSCI, then update OSCI job config (and GHA, which actually work with <IP_ADDRESS> right now, but better to have same version everywhere).

$ docker run quay.io/rhacs-eng/apollo-ci:stackrox-build-<IP_ADDRESS>-4-g7bad9d4f80 go version
go version go1.19.9 linux/amd64
$ docker run quay.io/rhacs-eng/apollo-ci:stackrox-build-<IP_ADDRESS>-4-g7bad9d4f80 node --version
v16.17.1
$ docker run quay.io/rhacs-eng/apollo-ci:stackrox-test-<IP_ADDRESS>-4-g7bad9d4f80 java -version
openjdk version "1.8.0_322"
OpenJDK Runtime Environment (build 1.8.0_322-b06)
OpenJDK 64-Bit Server VM (build 25.322-b06, mixed mode)

Node version discussion: https://redhat-internal.slack.com/archives/C7ERNFL0M/p1684792225868969
Java version discussion: https://redhat-internal.slack.com/archives/C04Q0KQMEUV/p1684510086586749

Testing looks good. I'll go ahead and merge and tag.


How about providing c++/python version of wrapper of amx?

Thanks for your great work, but I am newer to rust, do you have idea to provide c++/python version of wrapper of amx?

I'm not strongly interested in this project anymore, so I'm leaving this up to community contribution.
PyO3 would be the easiest way to create a Python wrapper, but I don't see the point of doing that. An AMX emulator could be useful for experimentation, but amx-rs's emulation code is completely unimplemented at the moment.
https://github.com/yvt/amx-rs/blob/15767ea635567ab6b4fff757778de22a5c287d6d/src/emu.rs#L42-L45

@peyer There already exists a C++ version here: https://github.com/corsix/amx


Performance issue when records are too many

This is regarding performance. I am trying to load heavy data with 5000+ records. When i am doing select/de-select operations, page is going unresponsive. Please look into this.

If you are dealing with large amounts of data, you probably want to be using pagination, which this plugin does not support.
I would suggest using something like datatables.

Datatables is  a heavy library to use, hence i wanted to check if this supports. Anyways leveraged datatables' feature to implement pagination.  Thanks

Same issue here. I've chosen this because of the excel flavor filters. I can't find such a thing in datatables, there they search a string among all columns, that makes no sense in my scenario. I would be glad to help: is pagination so difficult to implement? Just to know, why doesn't this plugin support it? If you can clarify the reason, so that I can also make an informed decision: spend my time for a pagination enhancement here or try to reimplement this single column filters in another library like datatables. Thank you

Never mind found a plugin of datatables that is doing exactly this jus


Migrations to GitHub Discussions

Some of the issues are questions or feature requests. The issue page is not designed for this.
So I propose moving feature requests, community discussions, and q&a to GitHub Discussions.
Migration to GitHub Discussion is already here in this Pull Request.
But this PR requires @Andrewthe13th to enable GitHub Discussions.
here's documentation on how to enable Discussion tab: https://docs.github.com/en/discussions/quickstart

I have noticed that @Andrewthe13th has enabled GitHub Discussion. Thanks! 🤟
This PR is now safe to Merge. Please do so with other PR that I've sent.
This road is one step closer from making a community possible. I am so proud that I am part of this movement.


It just gets stuck on 0%

Tem alguma flag de debug?
O código travou assim que selecionei o curso em 0%, sem erros reportados...
Inicialmente estava por SSH em uma VM Ubuntu 22.04 rodando no Hyper-V com 4vcpu e 4GB de RAM, testei também em uma VM com Ubuntu Desktop 22.04 minimal. Ambos com o mesmo comportamento.
quando dou ctrl+C:
Cursos disponíveis:
1. CursoA
2. CursoB
3. CursoC
4. CursoD
Escolha um curso pelo número: 1
CursoA:   0%|                                                                                | 0/21 [00:00<?, ?it/s]CursoA:   0%|                                                                                | 0/26 [03:20<?, ?it/s]
Traceback (most recent call last):
  File "/home/lincoln/Hotm4rtei/main.py", line 134, in <module>
    redirect_club_hotmart(course_name, token)
  File "/home/lincoln/Hotm4rtei/main.py", line 130, in redirect_club_hotmart
    list_modules(course_name, filtered_modules)
  File "/home/lincoln/Hotm4rtei/main.py", line 114, in list_modules
    process_module(module_data, main_course_folder, course_name)
  File "/home/lincoln/Hotm4rtei/main.py", line 100, in process_module
    process_lessons_details(lessons, course_name)
  File "/home/lincoln/Hotm4rtei/main.py", line 91, in process_lessons_details
    download_video(processed_lessons, hotmartsession)
  File "/home/lincoln/Hotm4rtei/download.py", line 125, in download_video
    with ThreadPoolExecutor(max_workers=5) as executor:
  File "/usr/lib/python3.10/concurrent/futures/_base.py", line 649, in __exit__
    self.shutdown(wait=True)
  File "/usr/lib/python3.10/concurrent/futures/thread.py", line 235, in shutdown
    t.join()
  File "/usr/lib/python3.10/threading.py", line 1096, in join
    self._wait_for_tstate_lock()
  File "/usr/lib/python3.10/threading.py", line 1116, in _wait_for_tstate_lock
    if lock.acquire(block, timeout):
KeyboardInterrupt
^CException ignored in: <module 'threading' from '/usr/lib/python3.10/threading.py'>
Traceback (most recent call last):
  File "/usr/lib/python3.10/threading.py", line 1537, in _shutdown
    atexit_call()
  File "/usr/lib/python3.10/concurrent/futures/thread.py", line 31, in _python_exit
    t.join()
  File "/usr/lib/python3.10/threading.py", line 1096, in join
    self._wait_for_tstate_lock()
  File "/usr/lib/python3.10/threading.py", line 1116, in _wait_for_tstate_lock
    if lock.acquire(block, timeout):
KeyboardInterrupt:

O CursoA tem mais de 100 vídeos e suponho que o erro seja relacionado à quantidade de objetos a serem baixados...

Python 3.10.12
Requirement already satisfied: beautifulsoup4==4.12.2 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 1)) (4.12.2)
Requirement already satisfied: Brotli==1.1.0 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 2)) (1.1.0)
Requirement already satisfied: bs4==0.0.1 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 3)) (0.0.1)
Requirement already satisfied: certifi==2023.11.17 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 4)) (2023.11.17)
Requirement already satisfied: charset-normalizer==3.3.2 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 5)) (3.3.2)
Requirement already satisfied: colorama==0.4.6 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 6)) (0.4.6)
Requirement already satisfied: idna==3.6 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 7)) (3.6)
Requirement already satisfied: mutagen==1.47.0 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 8)) (1.47.0)
Requirement already satisfied: pycryptodomex==3.19.1 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 9)) (3.19.1)
Requirement already satisfied: requests==2.31.0 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 10)) (2.31.0)
Requirement already satisfied: setuptools==65.5.0 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 11)) (65.5.0)
Requirement already satisfied: soupsieve==2.5 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 12)) (2.5)
Requirement already satisfied: tqdm==4.66.1 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 13)) (4.66.1)
Requirement already satisfied: urllib3==2.1.0 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 14)) (2.1.0)
Requirement already satisfied: websocket-client==1.7.0 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 15)) (1.7.0)
Requirement already satisfied: websockets==12.0 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 16)) (12.0)
Requirement already satisfied: yt-dlp==2023.12.30 in ./.venv/lib/python3.10/site-packages (from -r requirements.txt (line 17)) (2023.12.30)

A url base do curso é completamente diferente do esperado no programa:
https://hotmart.com/pt-br/club//products/


translation of spellbook

I have merged my branch with the things you did (i just accepted all your changes and overwrote mine)

Are you sure you forked the right version? I see a lot of things that I changed over the last ~2 weeks that roll20 has not updated yet.
For example I removed cantrips for Paladin and Ranger, but I see them in your commits.
Also, make sure your tabbing is correct. For example tr should be tabbed in from thead and tbody.

Hm actually that might be true. Those things should be contained to the spellbook tab tho.
The translations are from one of my players who send them to me a couple of hours ago. I think he worked off of the old version.

There are thousands of changes all over, not just the spellbook.

Are you sure? I only see changes in spellbook-section.

I'll manually merge the changes, but for future things you guys should be on the latest code and update every day.

Ok, thanks for your efforts again. I will forward that.

Done. Please don't make me do this again. :(
I'm currently splitting the pages and will compile it all via Gulp so if you're working on other pages please wait until I finish that (likely today).

Yep that sounds like a good plan.

I've committed the split if you want to work on other pages.
Thanks again for your contributions.


Added code for plotting the graph for 5 more frequent violation code …

…with time.

Looks fine to me


500s on media requests

for head requests that error, respond with body containing json error message
find error containing "Audio generation failed: Could not create spectrogram using resque from request" and fix it (remove paths, give more information, might be raised incorrectly).
error emails are not being sent

Changes:

head requests that error will send a notification email
emails will not be sent for other request verbs that error and have a custom rescue_from in application_controller.rb
removed ls check, removed paths from error message


Add AllowCache option to MediaPlaylist

Added option prevents from disabling cache via EXT-X-ALLOW-CACHE tag
for Event playlists encodig.

Coverage decreased (-0.3%) to 75.091% when pulling 98f4e308c8d7ab63e69100a70a8946734c7424c5 on hilmekrhu:feature/allow-cache into 036100c52a87e26c62be56df85450e9c703201a6 on grafov:master.

Coverage decreased (-0.3%) to 75.091% when pulling 98f4e308c8d7ab63e69100a70a8946734c7424c5 on hilmekrhu:feature/allow-cache into 036100c52a87e26c62be56df85450e9c703201a6 on grafov:master.

Coverage decreased (-0.3%) to 75.091% when pulling 98f4e308c8d7ab63e69100a70a8946734c7424c5 on hilmekrhu:feature/allow-cache into 036100c52a87e26c62be56df85450e9c703201a6 on grafov:master.


Try to Join ValueReader and WriterValue

Try to Join ValueReader and WriterValue in just one interface.

Different of JPA, that we already have type information from field. We haven't here, that why the best solution is keep it split.


Add a "back to homepage" link

With the new header bar, a link to the homepage could be a nice improvement.
If you want, I can work on this easy issue next week.

You are talking about something like a "back link" when displaying a photo? So basically the same that is happening when clicking the photo? For that, maybe the title could become a clickable link in the detail view.
Consider creating a new fork or clone freshly when requesting a PR though. As per the BFG website:

At this point, you're ready for everyone to ditch their old copies of the repo and do fresh clones of the nice, new pristine data. It's best to delete all old clones, as they'll have dirty history that you don't want to risk pushing back into your newly cleaned repo.

For that, maybe the title could become a clickable link in the detail view.

Hmm, not as easy as that... because we need to change the javascript ...


Search and filtering update terms and image

Closes #206
PTAL

Made the image as large as I can without the buttons changing position. @sgray is there a way to increase the image size in the doc?

@stuartmoore1023 I think you need to take the screenshot on a HiDPI screen. I've got an image we can use. Do you mind if I push an update to this branch?

Not at all @sgray. Thanks!

Thanks @stuartmoore1023, I think it looks good now. Merging.


Fix save snapshot failures when using PersistOnEvent

fixes #194

No user-defined persistOnEvent handlers

Persisted events must be handler in event handler

Persistence failures throw PersistOnEventException

Re-implementation of PersistOnEvent

Composition with ConfirmedDelivery possible

redeliverUnconfirmed allowed in context of PersistOnEvent

LGTM


feat: upload file using an s3 client

Ticket https://phabricator.wikimedia.org/T343112

Leaving this a draft until there's a matching chart update.

Chart update here https://github.com/wbstack/charts/pull/125


[Bug] ./scripts/dev_setup.sh on Ubuntu 18.04: "protoc version is too old. Update protoc to 3.6.0 or above. Abort"

🐛 Bug
When running ./scripts/dev_setup.sh on Ubuntu 18.04 (Vagrant VM ubuntu/bionic64, which I think is representative for other Ubuntu 18.04 installs), the script fails with:
protoc version is too old. Update protoc to 3.6.0 or above. Abort

I would expect this to complete successfully on the latest Ubuntu LTS release.
To reproduce

Create a fresh Ubuntu 18.04 VM with Vagrant: vagrant init ubuntu/bionic64 && vagrant up
Follow instructions from https://developers.libra.org:
** git clone https://github.com/libra/libra.git && cd libra
** ./scripts/dev_setup.sh

** Stack trace/error message **
After successfully installing many components:
protoc version is too old. Update protoc to 3.6.0 or above. Abort

Expected Behavior
Script completes successfully
System information
Libra Version: latest version cloned from GitHub
Computer OS: Ubuntu 18.04 in a Vagrant VM ubuntu/bionic64

I had the same issue, you can manually install Protoc (As seen here: https://askubuntu.com/questions/1072683/how-can-i-install-protoc-on-ubuntu-16-04)
You may need to remove lines 120-129 in ./scripts/dev_setup.sh as after you install Protoc manually, the check error outs:
   120  if [[ -f /etc/debian_version ]]; then    121          PROTOC_VERSION=protoc --version | cut -d" " -f2    122          REQUIRED_PROTOC_VERSION="3.6.0"    123          PROTOC_VERSION_CHECK=dpkg --compare-versions $REQUIRED_PROTOC_VERSION "gt" $PROTOC_VERSION   124    125          if [ $? -eq "0" ]; then    126                  echo "protoc version is too old. Update protoc to 3.6.0 or above. Abort"    127                  exit 1    128          fi    129  fi

Unfortunately, apt-get only has protoc 3.0. Please follow the instructions from protobuf to update it to 3.6.0 or above. https://github.com/protocolbuffers/protobuf/tree/master/src

Here is a simple solution to solve this bug :
Mac OS :
brew install protobuf
brew upgrade protobuf
Linux :
PROTOC_ZIP=protoc-3.7.1-osx-x86_64.zip
curl -OL https://github.com/google/protobuf/releases/download/v3.7.1/$PROTOC_ZIP
sudo unzip -o $PROTOC_ZIP -d /usr/local bin/protoc
sudo unzip -o $PROTOC_ZIP -d /usr/local include/*
rm -f $PROTOC_ZIP
And finally run :
./scripts/dev_setup.sh
./scripts/cli/start_cli_testnet.sh

@maxb14 solution worked fine for me

With [this solution]( https://askubuntu.com/questions/1072683/how-can-i-install-protoc-on-ubuntu-16-04/1072684 i) was able to install it.

Thanks @maxb14. The updated version below (with corrected binary for Linux) works for me on Ubuntu 18.04.
PROTOC_ZIP=protoc-3.8.0-linux-x86_64.zip
curl -OL https://github.com/google/protobuf/releases/download/v3.8.0/$PROTOC_ZIP
sudo unzip -o $PROTOC_ZIP -d /usr/local bin/protoc
sudo unzip -o $PROTOC_ZIP -d /usr/local include/*
rm -f $PROTOC_ZIP

I suggest the Libra devs add detection the presence of the version of protoc and install the one for the correct architecture (32/64 bit) within dev_install.sh.

Works! Note that the last command should be sudo unzip -o $PROTOC_ZIP -d /usr/local 'include/*' if your shell is fish

Here is a simple solution to solve this bug :
Mac OS :
brew install protobuf
brew upgrade protobuf
Linux :
PROTOC_ZIP=protoc-3.7.1-osx-x86_64.zip
curl -OL https://github.com/google/protobuf/releases/download/v3.7.1/$PROTOC_ZIP
sudo unzip -o $PROTOC_ZIP -d /usr/local bin/protoc
sudo unzip -o $PROTOC_ZIP -d /usr/local include/*
rm -f $PROTOC_ZIP
And finally run :
./scripts/dev_setup.sh
./scripts/cli/start_cli_testnet.sh

The PROTOC_ZIP variable needs to be
PROTOC_ZIP=protoc-3.7.1-linux-x86_64.zip
the current variable is pointing to an OSX binary.

For Linux, the

Here is a simple solution to solve this bug :
Mac OS :
brew install protobuf
brew upgrade protobuf
Linux :
PROTOC_ZIP=protoc-3.7.1-osx-x86_64.zip
curl -OL https://github.com/google/protobuf/releases/download/v3.7.1/$PROTOC_ZIP
sudo unzip -o $PROTOC_ZIP -d /usr/local bin/protoc
sudo unzip -o $PROTOC_ZIP -d /usr/local include/*
rm -f $PROTOC_ZIP
And finally run :
./scripts/dev_setup.sh
./scripts/cli/start_cli_testnet.sh

The PROTOC_ZIP variable needs to be
PROTOC_ZIP=protoc-3.7.1-linux-x86_64.zip
the current variable is pointing to an OSX binary.

For Ubuntu 18.04 this is the solution. It's worked.

Few notes here:

The script doesn't give protoc version warnings on Fedora/yum-based distros (this may thoroughly confuse some people!)
The protoc version on Fedora is outdated anyway, so I had to use one of the solutions above. I'm closing #53 since this effectively makes it pointless.

I'd say we should just make this the default and grab protoc directly from Google's repository. The binary can be put into a gitignored local directory.

Thanks @maxb14.
Made a gist for deb 9 to upgrade to 3.7.1:
https://gist.github.com/richbodo/08974a4a818aa047cb0e3cb429c24b95

Hi folks, thanks for chiming in here. These issues should be resolved by code in master. If not, please tag me and I'll follow up.


Top bar has gaps on both sides on mobile

Brief Description
The sticky top bar leaves gaps open on each side.
Steps to reproduce the bug
Open ash HQ on mobile e.g. here
Context
I'm on an Asus Zenfone 10 using Firefox.
Screenshot:

Thank you for the report! This should be fixed now :)


React dojah is not compatible with React 18.2.0

When installing I get this error
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/react-dojah
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

I don't want to resolve issue by using --force or --legacy-peer-deps

Having same issues but --legacy-peer-deps resolves it. I think it's high time they update it. It breaks a lot of things.