3.0.0 & 3.0.1 not gettign data

Hi love the intergration, I was doing this manually before but so much easier now, thank you.
2.0.0 worked perfectly and was downloading data each day. Since 3.0.0 no data is ever downloaded and sensors stay at 0
Rolling back to 2.0.0 gets data again upgrading to 3.0.1 (or 3.0.0) breaks the intergration
I'm not sure they are relevant but her are the only log entries I can see that are related
  File "/config/custom_components/octopus_energy/__init__.py", line 89, in async_update_data     hass.data[DOMAIN][DATA_RATES] = await client.async_get_rates(tariff_code, period_from, period_to)   File "/config/custom_components/octopus_energy/api_client.py", line 107, in async_get_rates     return await self.async_get_standard_rates(product_code, tariff_code, period_from, period_to)   File "/config/custom_components/octopus_energy/api_client.py", line 49, in async_get_standard_rates     data = await response.json(content_type=None)   File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 1119, in json     return loads(stripped.decode(encoding))   File "/usr/local/lib/python3.9/json/__init__.py", line 346, in loads     return _default_decoder.decode(s)   File "/usr/local/lib/python3.9/json/decoder.py", line 337, in decode     obj, end = self.raw_decode(s, idx=_w(s, 0).end())   File "/usr/local/lib/python3.9/json/decoder.py", line 355, in raw_decode     raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
May be relevant that i'm an octopus energy UK customer and don't have a varible tarrif.
With 3.0.1 (and 3.0.0) the intergration is getting the following;
sensor.octopus_energy_electricity_XXXXXXXXX_latest_consumption = Unavailable
sensor.octopus_energy_electricity_XXXXXXXXX_previous_accumulative_consumption = 0
sensor.octopus_energy_electricity_XXXXXXXXX_previous_accumulative_consumption_cost = 0.0
sensor.octopus_energy_electricity_XXXXXXXXX_previous_accumulative_cost = 0
sensor.octopus_energy_electricity_current_rate = 0.187845 (always the same)
sensor.octopus_energy_electricity_previous_rate = 0.187845 (always the same)
sensor.octopus_energy_gas_XXXXXXXXX_latest_consumption = Unavailable
sensor.octopus_energy_gas_XXXXXXXXX_previous_accumulative_consumption = 0
sensor.octopus_energy_gas_XXXXXXXXX_previous_accumulative_consumption_cost = 0.0
sensor.octopus_energy_gas_XXXXXXXXX_previous_accumulative_cost = 0
With 2.0.0 the intergraion get the following:
sensor.octopus_energy_electricity_XXXXXXXXX_latest_consumption = 0
sensor.octopus_energy_electricity_XXXXXXXXX_previous_accumulative_consumption = 16.962
sensor.octopus_energy_electricity_XXXXXXXXX_previous_accumulative_consumption_cost = 0.0
sensor.octopus_energy_electricity_XXXXXXXXX_previous_accumulative_cost = Unavailable
sensor.octopus_energy_electricity_current_rate = 0.187845 (always the same)
sensor.octopus_energy_electricity_previous_rate = 0.187845 (always the same)
sensor.octopus_energy_gas_XXXXXXXXX_latest_consumption = 0
sensor.octopus_energy_gas_XXXXXXXXX_previous_accumulative_consumption = 2.781
sensor.octopus_energy_gas_XXXXXXXXX_previous_accumulative_consumption_cost = 0.0
sensor.octopus_energy_gas_XXXXXXXXX_previous_accumulative_cost = Unavailable
Happy to test anything that might help.

Hello. Sorry to see you're having issues.
The latest_consumption sensors have been removed as part of this release (as indicated in the release notes), as they were always zero due to Octopus Energy never having live data.
I have seen errors crop up when requesting data from Octopus Energy, but this is usually the result either the Octopus Energy API failing or the Home Assistant instance losing internet connection. However, the integration should stabilize itself once a connection has been re-established.
I'll try and do an update which tries to get a better error message.
I also removed some logic around falling back to a variable tariff if an active tariff couldn't be found, however I'd expect a different error message in the logs.

Thanks, understood about the sensors. I just included everything that might be helpful. Other than reboots for hacs updates I don't think I've had any internet issues. 3.0.1 was running for I think 3/4 days before I rolled back, previous consumption always read 0.
I'll reinstall (Inc any updates) and monitor the logs.

Hi, I installed 3.0.2 as soon as i saw it but didn't get any results, look this morning and found some log entries.
There appears to be 2, one for the usage and 1 for the rates but I have noticed that the rates have registered a change in home assisatant since i updated. do the rates poll more than the usage?
I do notice in both results;

502 Bad Gateway

nginx

But I don't have Nginx add-on installed?
`Hi, I installed 3.0.2 as soon as i saw it but didn't get any results or log entries for the first
502 Bad Gateway
nginx

Traceback (most recent call last):
  File "/config/custom_components/octopus_energy/api_client.py", line 302, in __async_read_response
    return json.loads(text)
  File "/usr/local/lib/python3.9/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
  File "/usr/local/lib/python3.9/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/local/lib/python3.9/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 147, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/octopus_energy/__init__.py", line 81, in async_update_data
    tariff_code = await async_get_current_agreement_tariff_code(client, config)
  File "/config/custom_components/octopus_energy/__init__.py", line 54, in async_get_current_agreement_tariff_code
    account_info = await client.async_get_account(config[CONFIG_MAIN_ACCOUNT_ID])
  File "/config/custom_components/octopus_energy/api_client.py", line 25, in async_get_account
    data = await self.__async_read_response(response, url)
  File "/config/custom_components/octopus_energy/api_client.py", line 304, in __async_read_response
    raise Exception(f'Failed to extract response json: {url}; {text}')
Exception: Failed to extract response json: https://api.octopus.energy/v1/accounts/[AccountNumber];
502 Bad Gateway

502 Bad Gateway
nginx

2021-12-29 05:00:39 ERROR (MainThread) [custom_components.octopus_energy.api_client] Failed to extract standard rates: https://api.octopus.energy/v1/products/[TARRIF]/electricity-tariffs/[TARRIF]/standard-unit-rates?period_from=2021-12-29T00:00:00Z&period_to=2021-12-31T00:00:00Z
2021-12-29 05:00:39 ERROR (MainThread) [custom_components.octopus_energy] Unexpected error fetching rates data: Failed to extract response json: https://api.octopus.energy/v1/products/[TARRIF]-21-05-29/electricity-tariffs/[TARRIF]/standard-unit-rates?period_from=2021-12-29T00:00:00Z&period_to=2021-12-31T00:00:00Z;
502 Bad Gateway

502 Bad Gateway
nginx

Traceback (most recent call last):
  File "/config/custom_components/octopus_energy/api_client.py", line 302, in __async_read_response
    return json.loads(text)
  File "/usr/local/lib/python3.9/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
  File "/usr/local/lib/python3.9/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/local/lib/python3.9/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 147, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/octopus_energy/__init__.py", line 89, in async_update_data
    hass.data[DOMAIN][DATA_RATES] = await client.async_get_rates(tariff_code, period_from, period_to)
  File "/config/custom_components/octopus_energy/api_client.py", line 104, in async_get_rates
    return await self.async_get_standard_rates(product_code, tariff_code, period_from, period_to)
  File "/config/custom_components/octopus_energy/api_client.py", line 48, in async_get_standard_rates
    data = await self.__async_read_response(response, url)
  File "/config/custom_components/octopus_energy/api_client.py", line 304, in __async_read_response
    raise Exception(f'Failed to extract response json: {url}; {text}')
Exception: Failed to extract response json: https://api.octopus.energy/v1/products/[TARRIF]/electricity-tariffs/[TARRIF]/standard-unit-rates?period_from=2021-12-29T00:00:00Z._to=2021-12-31T00:00:00Z;
502 Bad Gateway

502 Bad Gateway
nginx

`
Rolling back to 2.0.0 instanly pulls down todays (yesterdays) data.
I hope this sheds some light on what is going on and it helps you debug it. Again happy to try anythign or collect data you might need. I don't think there is anything out of the ordinary in my setup and my internet is rock solid. HA is running in a Proxmox VM.
Thanks for looking at this though, I do appreciate it.

do the rates poll more than the usage?

Both poll within HA every minute to make sure they have some data. However at the moment rates do poll more frequently than usage (although there's no real reason why they should as they don't update that frequently). For rates I try and get two days worth of data (today and tomorrow), as this is as far Octopus publishes them for their agile tariffs.
Because I can only get historic data for usage, I poll Octopus less frequently (unless the data is out of date).

But I don't have Nginx add-on installed?

This is the response from Octopus's APIs as they must be using Nginx.
I can't see anything in those logs around consumption, so not sure what's causing that to not populate.

I'll keep 3.0.2 installed for a few days and see if I can find logs for consumption. It's just weird that 2.0.0 always works :)
i'll update when I find something, thanks for looking

Intrestingly installing 3.0.2 resets the todays data (previously got by 2.0.0) but there are no log events,
i'll keep watchign the logs and update if I find anything

Same kind of error showed up for consumption, again I've stripped out the HTML around the bad gateway.
2021-12-30 03:30:16 ERROR (MainThread) [custom_components.octopus_energy.sensor] Unexpected error fetching rates data: Failed to extract response json: https://api.octopus.energy/v1/electricity-meter-points/[ID]/meters/[ACCOUNT]/consumption?period_from=2021-12-29T00:00:00Z&period_to=2021-12-30T00:00:00Z; 502 Bad Gateway 502 Bad Gateway nginx Traceback (most recent call last):   File "/config/custom_components/octopus_energy/api_client.py", line 302, in __async_read_response     return json.loads(text)   File "/usr/local/lib/python3.9/json/__init__.py", line 346, in loads     return _default_decoder.decode(s)   File "/usr/local/lib/python3.9/json/decoder.py", line 337, in decode     obj, end = self.raw_decode(s, idx=_w(s, 0).end())   File "/usr/local/lib/python3.9/json/decoder.py", line 355, in raw_decode     raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) During handling of the above exception, another exception occurred: Traceback (most recent call last):   File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh     self.data = await self._async_update_data()   File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 147, in _async_update_data     return await self.update_method()   File "/config/custom_components/octopus_energy/sensor.py", line 60, in async_update_data     data = await client.async_electricity_consumption(identifier, serial_number, period_from, period_to)   File "/config/custom_components/octopus_energy/api_client.py", line 115, in async_electricity_consumption     data = await self.__async_read_response(response, url)   File "/config/custom_components/octopus_energy/api_client.py", line 304, in __async_read_response     raise Exception(f'Failed to extract response json: {url}; {text}') Exception: Failed to extract response json: https://api.octopus.energy/v1/electricity-meter-points/[ID]/meters/[ACCOUNT]/consumption?period_from=2021-12-29T00:00:00Z&period_to=2021-12-30T00:00:00Z;  502 Bad Gateway 502 Bad Gateway nginx

I've released a new version v3.0.3 which will hopefully supress the 502 bad gateway errors and help us get to the root cause of the issue.

I've released a new version v3.0.3 which will hopefully supress the 502 bad gateway errors and help us get to the root cause of the issue.

Thanks, i'll update and let you know what it does.

Thanks, i'll update and let you know what it does.

First impressions don't look good. It cleared the sensors down on install but left them at zero on reboot. 2.0.0 always gets the last figures on install and reboot. I'll leave running and see if there are any log entries.

First impressions don't look good. It cleared the sensors down on install but left them at zero on reboot. 2.0.0 always gets the last figures on install and reboot. I'll leave running and see if there are any log entries.

Ok I'll continue to investigate. Out of interest, if you view the details of the accumulative sensor that is not being picked up, I assume it's still associated with the integration (if not, HA will indicate that it has been orphaned and give you the option to remove the entity)

Ok I'll continue to investigate. Out of interest, if you view the details of the accumulative sensor that is not being picked up, I assume it's still associated with the integration (if not, HA will indicate that it has been orphaned and give you the option to remove the entity)

The only thing I can see that might be effecting you is if you are missing any 30 minute blocks in your consumtion data. This can be confirmed by going to your energy dashboard on Octopus Energy (https://octopus.energy/dashboard/new/accounts/A-XXXXXXXX/consumption/home), switching to day view and seeing if you have any 30 minute periods that are zero?

The only thing I can see that might be effecting you is if you are missing any 30 minute blocks in your consumtion data. This can be confirmed by going to your energy dashboard on Octopus Energy (https://octopus.energy/dashboard/new/accounts/A-XXXXXXXX/consumption/home), switching to day view and seeing if you have any 30 minute periods that are zero?

Sensors are not orphaned and show updates to both 'Last Changed' and 'Last Updated' of the upgrade time but value is always 0. I've had no log entries today since installing 3.0.3 but I'll keep monitoring. I had a WiFi sensor drop out of DNS so the log got a bit full today.
I don't have any missing blocks for electricity but gas is very patchy, with only 6 blocks over the 24hrs having data but I believe thisto be normal.
But again if I install 2.0.0 it downloads the data fine and I get values for electricity and gas. Fresh installs with 2.0.0 always return data, upgrading to anything newer then resets the values to 0. Somethign i haven't done yet but will today is to reset and fresh install 3.0.0+ with no instance of 2.0.0 already running, I'll try that with 3.0.3.
If i'm the only person experiencing this I'll continue to run 2.0.0 but I fear I'll miss out on any advancements you make :)

Sensors are not orphaned and show updates to both 'Last Changed' and 'Last Updated' of the upgrade time but value is always 0. I've had no log entries today since installing 3.0.3 but I'll keep monitoring. I had a WiFi sensor drop out of DNS so the log got a bit full today.
I don't have any missing blocks for electricity but gas is very patchy, with only 6 blocks over the 24hrs having data but I believe thisto be normal.
But again if I install 2.0.0 it downloads the data fine and I get values for electricity and gas. Fresh installs with 2.0.0 always return data, upgrading to anything newer then resets the values to 0. Somethign i haven't done yet but will today is to reset and fresh install 3.0.0+ with no instance of 2.0.0 already running, I'll try that with 3.0.3.
If i'm the only person experiencing this I'll continue to run 2.0.0 but I fear I'll miss out on any advancements you make :)

and again, thank you for your time spent looking at this.

and again, thank you for your time spent looking at this.

So we might have a bit of good news. I uninstalled 3.0.3 completely and rebooted the server. Removed the left over sensors and rebooted again. Installed 3.0.3 and I have data?! :)
Only log entries are;
/config/custom_components/octopus_energy/sensor.py:65: RuntimeWarning: coroutine 'async_get_active_tariff_code' was never awaited   if async_get_active_tariff_code(point["agreements"], client) != None: RuntimeWarning: Enable tracemalloc to get the object allocation traceback /config/custom_components/octopus_energy/sensor.py:73: RuntimeWarning: coroutine 'async_get_active_tariff_code' was never awaited   if async_get_active_tariff_code(point["agreements"], client) != None: RuntimeWarning: Enable tracemalloc to get the object allocation traceback
I continue to monitor and see if it continues to get data over the next few days. It would seem it was the upgrade process from 2.0.0 to 3+ at the root of it?
If I can provide anythign that might help diagnose then please let me know.

So we might have a bit of good news. I uninstalled 3.0.3 completely and rebooted the server. Removed the left over sensors and rebooted again. Installed 3.0.3 and I have data?! :)
Only log entries are;
/config/custom_components/octopus_energy/sensor.py:65: RuntimeWarning: coroutine 'async_get_active_tariff_code' was never awaited   if async_get_active_tariff_code(point["agreements"], client) != None: RuntimeWarning: Enable tracemalloc to get the object allocation traceback /config/custom_components/octopus_energy/sensor.py:73: RuntimeWarning: coroutine 'async_get_active_tariff_code' was never awaited   if async_get_active_tariff_code(point["agreements"], client) != None: RuntimeWarning: Enable tracemalloc to get the object allocation traceback
I continue to monitor and see if it continues to get data over the next few days. It would seem it was the upgrade process from 2.0.0 to 3+ at the root of it?
If I can provide anythign that might help diagnose then please let me know.

So we might have a bit of good news. I uninstalled 3.0.3 completely and rebooted the server. Removed the left over sensors and rebooted again. Installed 3.0.3 and I have data?! :)

Not sure why that would have happened, but glad you're getting some data now.

Only log entries are;

Those logs look like something from the old version of the integration, so are probably safe to ignore.
Hopefully we'll have solved this issue.

So we might have a bit of good news. I uninstalled 3.0.3 completely and rebooted the server. Removed the left over sensors and rebooted again. Installed 3.0.3 and I have data?! :)

Not sure why that would have happened, but glad you're getting some data now.

Only log entries are;

Those logs look like something from the old version of the integration, so are probably safe to ignore.
Hopefully we'll have solved this issue.

I also made an incorrect assumption that we should wait for an entry for each 30 minute slot to be available before making the consumption available, which by the sounds of it will never be true for you with gas. Therefore I'm in the process of removing this assumption.

I also made an incorrect assumption that we should wait for an entry for each 30 minute slot to be available before making the consumption available, which by the sounds of it will never be true for you with gas. Therefore I'm in the process of removing this assumption.

(All installs/upgrades were done through HACS) So just for kicks and giggles, i cleanly removed 3.0.3 and did an extra reboot then installed 2.0.0 (all working) again, upgraded to 3.0.3 and  . . . no data! Stripped everything off again, extra reboot and installed 3.0.3 and DATA?!
So (for me at least) it's somethign about the upgrade process. I'll try an upgrade from a working 3.0.3 with the next release but if that fails to then I'll just cleanly install each time. Hopefully this is somethign unique to my setup and others won't see it BUT if they do then hopefully they will come across this.
So again thank you, I'll give it a couple of days and check the logs but if all keeps working I'll close of the issue as user error ;)
If you ever need data exports or anythign like that I might be able to help with then just ask.

(All installs/upgrades were done through HACS) So just for kicks and giggles, i cleanly removed 3.0.3 and did an extra reboot then installed 2.0.0 (all working) again, upgraded to 3.0.3 and  . . . no data! Stripped everything off again, extra reboot and installed 3.0.3 and DATA?!
So (for me at least) it's somethign about the upgrade process. I'll try an upgrade from a working 3.0.3 with the next release but if that fails to then I'll just cleanly install each time. Hopefully this is somethign unique to my setup and others won't see it BUT if they do then hopefully they will come across this.
So again thank you, I'll give it a couple of days and check the logs but if all keeps working I'll close of the issue as user error ;)
If you ever need data exports or anythign like that I might be able to help with then just ask.

2 days of data for both electricity and gas with 3.0.4.
No idea why upgrading from 2.0.0 was breaking it?! Thanks again for looking at the issue.

Glad that it's now working for you, and hopefully everything will go smoother in the future.


Publishupdates to Atmosphere

After recent improvements, we can publish a new version to Atmosphere. Determine version number and publish the new version.

I think 0.4.0 is good to go based on your PR:
https://github.com/apinf/restivus-swagger/pull/16
In the readme future it would be nice to have some jump to anchor links in the future with sections about features and subsections for the features. Example of the jump to:
https://github.com/kadirahq/flow-router

In the readme future it would be nice to have some jump to anchor links in the future with sections about features and subsections for the features. Example of the jump to:
https://github.com/kadirahq/flow-router

Good idea. Since this issue is about the 0.40 release, would you consider adding that suggestion as a new issue? That way we can track it independently.

Closing this issue, since we have made the 0.40.0 release and published on Atmosphere.


plex no media shows in add channel view

After seemingly adding my plex server successfully I go to the channels section and click add channel. It shows my server name in the drop-down but no media is shown :(
Using docker setup

I have the same issue no docker just using windows .exe.
I do have a huge library.
At this point I have tried to tweak a few things with no luck.

Ok I think I have fixed that issue with no media. I disabled IP6 on my nic protocols and was able to see all my media

I likewise have this problem. Running dizque on docker on my Synology NAS with Plex running outside of Docker.

I tested running the previous psuedotv itself and it seemed to work fine, just worth a note. I realize the server addition logic is different in dizuetv so perhaps something there.

@krohrsb I bet you tested in 0.0.51 pseudotv. The new Plex authentication was added in Pseudotv 0.0.53

It looks like there are two things possibly going on here.
To get Synology to work correctly with dizquetv:
(This assumes you are running dizquetv on Docker and Plex outside of it)

Stop the container
Click Edit
Go to "Environment"
Click the "+" to add a line
For variable put "add-host"
For value put the address shown under dizque's plex settings for the correct Plex server. Omit any "https://" or ":#####" port switches. It should be just the base url.
Add a ":" and the IP of the Plex server directly after what you pasted in the value field. In the end it should be something like "###-##-#-##.xxxxxxxx.plex.direct:###.#.##.###".
Click "Apply"
Start the container

The second issue I'm seeing is there appears to be a small window of time where I can pull down my library and set a channel schedule but after a few minutes I can't pull it and Chrome's dev tools show the network traffic getting no response. I get a 401 when pinging the URL manually. Is there an authentication issue in play as well?

I am seeing the same problem. I have both plex and dizquetv running as docker containers on the same host and docker network.

I was able to get around this problem by manually editing plex-servers.json.
Just changing the address & uri to my local address seems to do the trick.
I am also running plex and dizquetv as containers on the same host.

I also successfully got around this problem by modifying the plex-server.json file.
Its worth noting that these requests to plex happen in the browser. When running docker-based applications many things are abstracted/hidden and configured differently.
Knowing it was browser-based helped me choose the correct URI to connect to plex with.

@krohrsb @dreamcasting @blake1029384756 @killnfield @vexorian
Should this Question/Bug be reworked into an Enhancement Request for making it easier to edit the address and URI in plex-servers.json?
Is there any other part of Issue #5 that needs to be addressed as an Issue/Bug, Question or Enhancement Request?  (If you have a new Issue/Bug, Question or Enhancement Request, please submit a new Issue with that information.)

Having the same problem even after manual editing the plex-servers.json and replacing all the address with my local IP of the plex server which is the same machine running dizquetv container. Maybe I am missing something...

@krohrsb @dreamcasting @blake1029384756 @killnfield @vexorian
Should this Question/Bug be reworked into an Enhancement Request for making it easier to edit the address and URI in plex-servers.json?
Is there any other part of Issue #5 that needs to be addressed as an Issue/Bug, Question or Enhancement Request? (If you have a new Issue/Bug, Question or Enhancement Request, please submit a new Issue with that information.)

Likely yes, a feature request.
I now understand a bit better how things are working with dizquetv.

Uses plex auth, which retrieves a list of connections one can use. The main connection is automatically used in dizquetv.
The connection retrieved from plex may not be optimal in all situations (so yes, adding the ability to modify it would be useful)
I now know that the requests to plex happen Client (browser) side. This may dictate which url of plex people will use, depending on their setup.

I was able to get around this problem by manually editing plex-servers.json.
Just changing the address & uri to my local address seems to do the trick.
I am also running plex and dizquetv as containers on the same host.

Can anyone provide an example of an altered file?  I've tried making changes and can't seem to get it to work.
No content appearing when trying to add programming.
Can't figure it out.

Hello all. Work for version 63 is focusing in making it easier to deal with this problem. It will be possible to edit the server values from the web UI instead of touching a json. And you won't have to remake the channels after editing them. Then in 64 it will be easier to configure this stuff correctly.

When I made my changes the ip of plex in my docker network didn't work. I had to port forward to the host and use its ip.

Ok great, I will wait on future versions and retry.  Thanks for the response.
Project looks promising - thank you!

I haven't seen this reported in a while, I think the server stuff in 0.0.63+ has actually made people more aware of when their plex can't be accessed in  the UI. Closing it for the time being.


Add retry operator

Current coverage is 97.43%

Merging #10 into master will increase coverage by +0.77% as of 3c77751

@@            master     #10   diff @@
======================================
  Files            7       7
  Stmts          150     156     +6
  Branches         0       0
  Methods
======================================
+ Hit            145     152     +7
  Partial          0       0
+ Missed           5       4     -1

Review entire Coverage Diff as of 3c77751

Powered by Codecov. Updated on successful CI builds.


Mongo filter responses include 'null.' in namespace names

The response for the service call '/api/connector-types/mongodb/validation/filters' is including 'null.' in the namespace names.  See below for an example payload and the response.
payload:
{
"mongodb.hosts":"dbzui-db-mongo:27017",
"mongodb.members.auto.discover":true,
"mongodb.poll.interval.ms":30000,
"mongodb.user":"debezium",
"mongodb.password":"***",
"mongodb.name":"inventory",
"connector.name":"mongoTest",
"mongodb.connect.timeout.ms":10000,
"connect.backoff.initial.delay.ms":1000,
"connect.backoff.max.delay.ms":120000,
"mongodb.authsource":"admin",
"connect.max.attempts":16,
"mongodb.server.selection.timeout.ms":30000,
"mongodb.socket.timeout.ms":0
}
response:
{ "matchedCollections":[
{"name":"products","namespace":"null.inventory"},
{"name":"customers","namespace":"null.inventory"},
{"name":"orders","namespace":"null.inventory"},
{"name":"system.sessions","namespace":"null.config"},
{"name":"transactions","namespace":"null.config"}],
"propertyValidationResults":[],"status":"VALID"
}

Hey, sorry for the late reply! Because of other things fall behind because of my sickness in January I had different topics and missed replying on time. Sorry, sorry!
The structure is: replicaSet.databaseName.collectionName. When you get this as null it means you don't have a replicaSet configured for your MongoDB instance. But a replicaSet is needed when using the MongoDB connector.
I have to think about if we can validate this in the main Debezium code. @gunnarmorling WDYT?

Yeah, replicaSet should never be null really. Not sure how the connector
would even work in that case?

It doesn't work. But it validates in Connector#validate which allows the connector setup process in the UI to continue and then we see invalid output in the Filters step.

Ah, gotcha. Yeah, that shouldn't be accepted input then.

@mdrillin that is the Jira task for this issue: https://issues.redhat.com/browse/DBZ-3029


Lock libsass to the last known good version

The latest libsass has some problems with interpolation, etc. For example, the neat package cannot be compiled anymore.
This PR locks the libsass to the latest known good version.

Thanks, but a PR like this is never going to be merged. If you check the docs you can provide a specific version of node-sass using the nodeSass option at runtime.

If it just was that easy :) Consider this - our ember app depends on ember-cli-sass, which in turn depends on broccoli-sass-source-maps, which in turn depends on node-sass. So for locking this to a good version, we had to fork two repos. I don't know any other way of accomplishing this, as it stands.

That's what I'm saying. You can add nodeSass: require('node-sass') to the sassOptions in ember-cli-build.js and it will use whatever version of node-sass is in your package.json. No forking required :)


Load report archive

Load a report from an archive file.  Follows from #4
Assuming that the given path is valid, the function signature could look something like this:
@classmethod
def load(self, path: str) -> cls: ...

Closed by #11


updated dropshare (4-3802)

Can I use cask-repair again to update the issues?

Can I use cask-repair again to update the issues?

Nope, I guess. There is no --force flag present in git push commands anywhere in the cask-repair script. I'm not sure, though, but it's better to make fixes manually when commit was already done by the script.

Could you please squash your commits?

Can I use cask-repair again to update the issues?

No, but you can close and resubmit if that’s easier for you.

I squash the two commits.

Thank you for the contribution. It was merged directly as 1d2aaed2bf9ba1da00e9945c756de3165216701b to keep commit history cleaner. Your contribution is still credited to you.

Now I see there is one more issue with the cask.
Error: It seems the symlink source is not there: '/opt/homebrew-cask/Caskroom/dropshare/4-3802/Dropshare.app'

The problem is the app name. This should be app 'Dropshare 4.app' instead of app 'Dropshare.app'.
What is the best way to resolve this? Should I create a new pull request or use this?

You should create a new PR.


Test go1.22 on Github Action Matrix

The PR https://github.com/redis/rueidis/pull/553 brings go1.22 dependencies to rueidis, so we need to test it with go1.22 as well and Github Action Matrix can help us.
We should add a new go-version variable with values including 1.21 and 1.22 to the matrix:
https://github.com/redis/rueidis/blob/37fc75f938f5dae2eeda4771cb9f68f50aab9bf0/.github/workflows/build.yml#L19-L22

Hey @rueian , can I work on this one?

Hey @rueian , can I work on this one?

can i do this with you?

Hey @mahiro72,
I am currently working on this. If I encounter any issues, can we collaborate on it together? Alright?

@JayChavan-23 Yes, sure!

@rueian @mahiro72 @SoulPancake
I’m having some trouble getting started since I’m a beginner. Can you help me by explaining where I should start and the flow I should follow? I want to try working on it by myself, but if I can't make progress in the next couple of days, I’m open to collaboration. A little heads-up would be appreciated.
Thank you!

@rueian @mahiro72 @SoulPancake I’m having some trouble getting started since I’m a beginner. Can you help me by explaining where I should start and the flow I should follow? I want to try working on it by myself, but if I can't make progress in the next couple of days, I’m open to collaboration. A little heads-up would be appreciated.
Thank you!

Hi @JayChavan-23, I think the following changes are required to be made.
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 1234567..89abcde 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -14,6 +14,7 @@ jobs:
       matrix:
         module: ${{fromJson(needs.prepare-matrix.outputs.matrix)}}
+        go-version: ['1.21.0', '1.22.0']
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
@@ -22,7 +23,7 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v5
         with:
-          go-version: '1.21.0'
+          go-version: ${{ matrix.go-version }}

       - name: Test Module
         run: |

These changes are generated by ChatGPT.

Thanks for the heads-up. I'm working on it

Resolved by https://github.com/redis/rueidis/pull/563


PDF does not show images from online

Hi ,
I use Angular 5 and this is used for my Angular method.
        var element = document.getElementById('document');
        var opt = {
            margin:       [10, 0, 10, 0],
            filename:     'document.pdf',
            image:        { type: 'jpeg', quality: 0.98 },
            html2canvas:  { scale: 2 },
            jsPDF:        { unit: 'mm', format: 'letter', orientation: 'portrait' }
        };
        html2pdf().from(element).set(opt).save();

After exporting a pdf, I am unable to see any images from online but it shows locally stored images.
Here is the example of image online.
https://s3.amazonaws.com/images.anterasoftware.com/5b6c5886622d5Screen_Shot_2018-06-27_at_10.37.03_AM.png
Please help, @eKoopmans
Regards.

I am trying to render cross-domain image which is exactly stored in amazon s3.  Please find the attached screenshot , any advice would be appreciated.

I got the same issue. But it's quite different. PDF created but it show empty space, not image.

It's not the best solution, But if you can convert your Image to Base64.

I have the same issue as solomondn on React and can't work around it since I can't store the images locally.

printDocuments() {         var opt = {             margin: 1,             pagespilt: true,             filename: 'download.pdf',             image:{type:'png'},             // html2canvas: {scale: 2},             // jsPDF:{ unit: 'in', format: 'letter', orientation: 'portrait' }         }         var input = document.getElementById("pdfContainer");         console.log(input)         html2pdf(input, opt)     }
this being my code

//this is my code for it
printDocuments() {
var opt = {
margin: 1,
pagespilt: true,
filename: 'download.pdf',
image:{type:'png'},
html2canvas: {scale: 2},
// jsPDF:{ unit: 'in', format: 'letter', orientation: 'portrait' }
}
var input = document.getElementById("pdfContainer");
console.log(input)
html2pdf(input, opt)
}

I am also having a similar issue. Wont detect any external images at all.
As a workaround you can convert your images to Base64.

I am also having a similar issue. Wont detect any external images at all.
As a workaround you can convert your images to Base64
For example.
Using
<template>

Hello

  <button click.delegate="download()">Download</button>
</template>

Yields
489ms html2canvas: Finished loading 0 images []

Using Base64

Hello

272ms html2canvas: Added image data:image/gif;base64,...........

@axiom88-guru Does this do anything for you?

Once again, You can only retrieve images with servers that have CORS enabled.

@PhilipTKC  thanks for your response.
I already solved this problem by enabling CORS on S3.  Thanks.

I got the same issue. But it's quite different. PDF created but it show empty space, not image.

I got the exact same issue with solomondn, have you fix it?

@bdwellons can u share me the code u used to convert images to base64?

@bdwellons +1 to the code. I tried in JS doing img.src=, the html page showed the image correctly, but it still wouldn't show in the generated PDF.

@bdwellons +1 to the code. I tried in JS doing img.src=, the html page showed the image correctly, but it still wouldn't show in the generated PDF.

Hi! do you have the code that can be used to convert images to base64?

Try to specify "allowTaint" parameter to "true" in html2canvas object
opt = {
margin: 0,
filename: "myfile.pdf",
image: { type: "jpeg", quality: 0.98 },
html2canvas: {
allowTaint: true,
scale: 2
},
jsPDF: {
unit: "in",
format: "a4",
orientation: this.setup.orientation
}
};

Thank you @PrasanthPerumalsamy

function exportToPDF() {
let elem = document.getElementById('pdf')
let opt = {
filename: 'sold_products.pdf',
image: { type: 'jpeg' },
html2canvas: { useCORS: true, scale: 2 }
}
html2pdf().from(elem).set(opt).save()
}

To anyone wondering how to enable CORS (Cross-origin resource sharing) on Firebase storage so your app can access photos saved there using this plugin by simply writing something like , follow these instructions to enable CORS. You will need to create a cors.json file with the contents in the provided example (or replace the * in "origin": ["*"] with the path to your app's domain. From what I understand specifying the specific domain is more secure because otherwise any domain, including malicious ones, can access data from your firebase storage). You can keep the cors.json file in your project's root directory. Then after installing the gsutil command line tool, you can run gsutil cors set cors.json gs://<your-cloud-storage-bucket> like the instructions say. You can find what <your-cloud-storage-bucket> is for your specific project by logging into your project on console.firebase.google.com and navigating to Storage>Files and copying what should look similar to gs://exampleproject.appspot.com.

Here's a link to an additional resource you may find useful: https://stackoverflow.com/a/37765371/17246058

I had the same issue and the following configs work with me just fine
// @ts-ignore
import("html2pdf.js").then(html2pdf => {
html2pdf
.default()
.from(wrapper)
.set({
filename: "analytics.pdf",
html2canvas: { dpi: 300, letterRendering: true, useCORS: true, scale: 2, },
jsPDF: { unit: "in", format: "letter", orientation: "portrait" },
pagebreak: { mode: "avoid-all", before: "#page2el" },
image: { type: "jpeg", quality: 1 },
})
.save()


Geocoding France gives polygons for French Guiana and Corsica also

@rafatower @iriberri
Ref S/B 6703448
Expected: Only France polygon will appear when georef by Admin Region with country column containing string "France"
Happening:

Steps:

Create empty dataset with country column, and add row containing "France"
Edit > Georeference > Admin. Regions
In Which Column Are Your Region Names Stored? = country; leave 2nd pulldown blank
(I also tried writing in "France" in 2nd pulldown but that caused no rows to be geocoded)

My test: http://cdb.io/1Ls1ZpO

Arguably that's not an issue. I'd say we should also include Nouvelle-Calédonie if not done.

How can I get rid of French Guiana?

that's the real issue we should solve (not in the platfor nor in the geocoder datasets) and I'm afraid this is not the place to fix.

Indeed, we have this: https://github.com/CartoDB/data-services/blob/master/geocoder/admin0/sql/subdivide_polygons.sql
That don't know why is not applied anymore :/
I'll manage.

Fixed :-)


Add Tests

We currently don't have any tests, but it would be nice to. Not being able to include a .argostranslate file in the tests easily will make this more difficult but at least having some tests would be good.

Thanks @JakeRoggenbuck!


Bug introduced by terser

I'm hitting a bug which is very hard to debug, since it only appears when rollup-plugin-terser is enabled. When running the minified JS, I get
Uncaught TypeError: (intermediate value).next is not a function
    n import-map-overrides.js:2
    c import-map-overrides.js:2
    value import-map-overrides.js:2
    le import-map-overrides.js:2
    Z import-map-overrides.js:2
    le import-map-overrides.js:2
    pe import-map-overrides.js:2
    value import-map-overrides.js:2
    value import-map-overrides.js:2

However when running the JS built with build:dev (or deleting the terser() part of the webpack config) the import-map-overrides load just fine.
We're running into this when attempting to upgrade to React 18, and changing to use WMF rather than SystemJS for loading modules (SystemJS is still used for the import map).
https://user-images.githubusercontent.com/1031876/182486847-0ce00248-17ab-4572-ae6c-5961c9e26d79.mp4

I've lost the ability to reproduce it in my project. I'm not sure what changed. I guess I'll close this.


IncludeImage doesn't work in Microsoft Teams message action sample.

Github issues for C#
Sample information

Sample type: Teams samples
Sample language: csharp_dotnetcore
Sample name: Messaging extensions - action

Describe the bug
When choosing the 'Share Message' command in Microsoft Teams channels and choosing the 'Include image in Hero Card' toggle button,no image is included in the returned HeroCard. In sample codes, the comparison between two strings should ignore case. Please check Screenshots below for more details.
To Reproduce
Steps to reproduce the behavior:

Deploy the sample "Messaging extensions - action" into Microsoft Teams
Click on "Share Message" command from any message in a Teams channel
Click on "Include image in Hero Card" toggle button
See error

Expected behavior
An image should be included in the returned HeroCard.
Screenshots

[bug]

Thank you for the PR!


Update README.md

Sendgrid updated their url. Previous http://blog.sendgrid.com/receiving-email-in-your-rails-app-with-griddler/ always show 404 page.

Oops, I merged #20 first. Thanks for your PR!


drivers: flash: Generic SPI Flash driver

Merged #5456.
Update spi api.
Independent of spi flash config.

This will need some patches split.
first patch: add your modification to get it running with latest spi API. Add your signed-off-by in the commit message
Then the second patch: add the CS/gpio logic you did, rework the Kconfig as you did etc...
Add a 3rd patch: creating the Kconfig.w25qxxdv etc..

Codecov Report

Merging #7532 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7532      +/-   ##
==========================================
+ Coverage   55.25%   55.25%   +<.01%
==========================================
  Files         467      467
  Lines       51638    51638
  Branches     9887     9887
==========================================
+ Hits        28531    28532       +1
+ Misses      19198    19197       -1
  Partials     3909     3909

Impacted Files
Coverage Δ

lib/posix/pthread.c
69.84% <0%> (+0.5%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4b0b65c...db8a154. Read the comment docs.


fix: upgrade esm version

修改内容
升级 esm 版本，解决 node 的编译问题

Codecov Report

Merging #126 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #126   +/-   ##
=======================================
  Coverage   25.87%   25.87%
=======================================
  Files          84       84
  Lines        1913     1913
  Branches      506      506
=======================================
  Hits          495      495
  Misses       1158     1158
  Partials      260      260

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8061a78...c317197. Read the comment docs.


Migrate elixir from protobuf to JSON Schema based messages

Ruby, JS, JVM and other implementation have migrated from protobuf to JSON Schema based messages.
Refs. https://github.com/cucumber/common/issues/1386

@WannesFransen1994 I guess you already started working on that. Did you already push some code to the server? Is it possible to open a PR?

Sorry for the delay, the PR is https://github.com/cucumber/common/pull/1952/. I'll be working on it in the upcoming weeks.

See https://github.com/cucumber/messages/pull/29


Create NCNCA 2017 Calendar

Move if from draft to a real thing.
Don't forget about #263.

For historical reasons make sure it's up to date with NCNCA.org


Update to latest ztunnel

Please provide a description of this PR:
The ztunnel was from 2/14, didn't have the latest few changes, including @ymesika 's L4 metrics change.
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[x ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@linsun: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
35d06094bb3cf5083d33af64d951f67d36a31eff
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes

I think auto would be nice, at least weekly


Off status

Hello,
First of all, congratulation for the good work, it is a very impressive piece of work.
Everything is working smoothly for me except for one thing.
If I turn off my TV with the remote control, the status remains on.
That's a problem for my Goodnight scenario.
Did I missed something or is it a bug?
Thanks

Well, this was already explained multiply times. I guess that you have an OLED TV. The LG OLED TVs do a pixel refresh every 4 hours of runtime. The pixel refresh takes around 8 minutes to run and in that time the TV seems to be off but actually it is still on, just the display is off. Unfortunately I did not find a way to detect this state, so when the pixel refresher is running the tv will appear as on until it finishes. This should not be a big deal but hopefully someday i find a way to fix this.

Thank you for your explanation. This is a very precious feedback I was not aware of, sorry for the dummy question. Congrats again for the good work, amazing.

I hope that i can fix this someday... This is not easy to debug because i have only a 8 minutes window to do my tests and after that i need to wait a long time again...


feat: add two phase refresh token algorithm

Many clients that use GoTrue have virtually no reliability guarantees that they will be able to receive or process results from requests. This is especially challenging for the refresh token flows.
Suppose the following scenario:

A client (browser tab) begins refreshing a session with a refresh token. It sends out a request.
While the request is being processed, the browser tab is closed.
GoTrue will successfully process the refresh token request, by issuing a new access token, revoking the old refresh token and issuing a new one.
Since the tab is closed, it is unable to receive the new refresh token and thus its local storage state is inconsistent.
When the client comes back, it will use an already used refresh token which will kick the user out.

(This has been observed and confirmed in the wild. It's actually more common than you may think, since people usually first make a tab visible -- which starts the refresh token flow -- and then quickly close it.)
This change allows the client to choose whether the refresh token flow will be immediate, or with a two-step process.
In the two step process, the client sends out a refresh token request with the phase property set to pre-commit. A new refresh and access token is generated, but the token being refreshed is not marked as revoked.
Once the client receives and more importantly saves the result from the pre-commit phase, it sends the same refresh token request but with the phase property set to commit which finally marks the refresh token as revoked.

Closing in favor of a different approach.


Documentation --- Location and Region

In the documentation, list all the valid options for:

Location
Region

Setting

Location=Oregon
Region=us-east-1
Puts the pin around Chicago.

Setting

Location=Virginia
Region=us-east-1
Puts the pin in Brazil -- Rio De Janeiro

Why not do an IP Address lookup to determine what the actual location is?  And have an override if necessary.

We will work on this and update you.

This will be addressed as part of the feature https://itrac.eur.ad.sag/browse/WF-29241.


With chunked uploads

Description (required)
Fixes #3854

Working fine for me on Pixel 2, Thanks for the PR @maskaravivek


The runner thread which was running the jobs raised an exeception. Read the traceback above to debug it. You can also pass raise_exceptions=False incase you want to show only a warning message instead ( For Ragas Version 0.1.10)

Description:
Hi,
I am currently using the latest version of Ragas (version 0.1.10) and encountering an error when using Ragas with local LLMs from Ollama. Here is my code:
from datasets import load_dataset
import ragas

from ragas.metrics import (
    answer_relevancy,
    faithfulness,
    context_recall,
    context_precision,
)
from langchain_community.chat_models import ChatOllama
from ragas import evaluate
from langchain_community.embeddings import OllamaEmbeddings

# Loading the V2 dataset
amnesty_qa = load_dataset("explodinggradients/amnesty_qa", "english_v2", trust_remote_code=True)
amnesty_subset = amnesty_qa["eval"].select(range(2))

df = amnesty_subset.to_pandas()

langchain_llm = ChatOllama(model="moondream")
langchain_embeddings = OllamaEmbeddings(model="moondream")

result = evaluate(
    amnesty_subset,
    metrics=[context_precision, faithfulness, answer_relevancy, context_recall],
    llm=langchain_llm,
    embeddings=langchain_embeddings
)

The Error Message:
ExceptionInRunner: The runner thread which was running the jobs raised an exception. Read the traceback above to debug it. You can also pass raise_exceptions=False in case you want to show only a warning message instead.
Current Solution
However, if I downgrade the Ragas version from 0.1.10 to 0.1.7, the error is resolved. I thought I should report this issue, thus I reported it here.
Thank you for your assistance.

Add the following lines in your code
It worked for me
import nest_asyncio
nest_asyncio.apply()

@mb16biswas can you try out @devblend360 method or update to v0.1.11 which basically does the same behind the scenes and let us know if that fixes it?
thanks for the heads up 🙂 !


fmriprep 1.5.0rc1 defaults to $HOME/work as working directory

In HPC and other shared machine situations where $HOME is on a network mount, HPC admins often request (or enforces) that no data or processing happens in $HOME, since /scratch or some related filesystem is designed to be high performance (and sufficient storage size) and does not interfere with interactive usage of other people.
Deploying fmriprep on a small cluster today via singularity I was surprised to find that it defaults to storing in-process work at $HOME/work, rather than the more sensible options of

$PWD
output_dir

I think either of those choices are more appropriate.

Related to #1735

Well, these are all my machines, I'm the HPC guy :)
This is with singularity at 1.5.0rc1.
With this run command:
> singularity run --cleanenv -B work:/work fmriprep-latest.simg /work/ds000003-download/ /work/output-test/ participant --fs-license-file /work/license.txt

It looks like the $PWD of a singularity container is the home directory of the user, and then run.py container then defaults to making "work" the default working directory, which ends up being "~/work"
This is therefore related to #1504 where we have a pitfall of how singularity handles paths.


FRI session drops during joint torque control

Hi,
Thanks for the work! We are doing joint torque control via FRI with this repo and it works well most of time. However we find the FRI session gets disposed when we have some physical interaction with the robot (like doing some small handguiding motions). From the log it seems like the connection quality drops to "poor" and hence get disconnected (please see the screenshot below).

Any idea on what could be the cause?
Btw I think here should be "FRI command mode" instead of control
https://github.com/KCL-BMEIS/lbr_fri_ros2_stack/blob/0d2cc6e2f6bcfbff860fa87ecb87a64520f55181/server/fri_ros2/LBRServer.java#L94
Thanks for your help!

hi @MrstupidJ and thanks for the feedback! Not exactly sure why the connection quality drop, sorry.
We are currently working on a major re-work, which should be live end of this week. I hope this fixes all connection issues.
May I ask what branch you are working on?

Thanks for your reply. We are using the foxy branch.
For the torque control we just choose Joint impedance control mode and toque command mode when running the Java app from KUKA smartPad.

that's the correct way to do it. When using the torque command mode a communication rate of at least 5ms is to be maintained, see below.

when launching the java app, you'll have to select <=5ms, maybe that solves the issue

sorry for the late response! Been busy moving this to humble. It will become a whole lot easier to use this stack. It will also become possible to bypass ros2_control. There will be a /lbr_state topic and a /lbr_command. Very straight forward

i wasn't able to work on this code for half a year but am now fully commited to making this repository a good experience. Thanks for the understanding

re foxy: we will try to move the changes made for humble to all other branches as well ASAP

Thank you so much for your hard work! I will have a try and let you know how it goes.

you can find the changes in the foxy branch.
Could you please try that and report if your issue persists? Thanks!

Hi, We've tried the latest commit in foxy branch, and the basic function looks fine for now.
For the connection dropping issue, we are suspecting it is caused by the real-time ubuntu kernel. Would you mind checking which version of ubuntu you are using? You can get it by typing uname -r in terminal.

we are using ubuntu 20 / 22 right now

Thanks for your work and reply, and happy new year!
I kind of think the real-time kernel matters when we use FRI. We tried two ubuntu 20.04 machines, and the one without real-time kernel gets disconnection error much more often (You can see "Quality change signalled POOR" from KUKA Smartpad). The robot cannot take any command with poor connection quality.


Restore r->write_event_handler after reading request body

Closes #130.
Tests included.

@zimmerle @victorhora this one is ready for review. Latest failures are caused by libmodsecurity compilation errors, it works just fine with a snapshot as of https://github.com/SpiderLabs/ModSecurity/commit/662fe63a47d012b89175ea7da5be1a8f7e76014c.

I initiated rebuild after
https://github.com/SpiderLabs/ModSecurity/commit/18cdffdbca75e6b9f790f6df2807a32cd805c0a0, and it worked fine again.

@victorhora I'd consider this one as bugfix, not enhancement, YMMV :) Have you had a chance to review / test / verify?

Indeed @defanator hehe. It seems like we need to create more tags here :)
Sorry, we didn't had the time to look at this yet. Will have a look and let you know! Thanks! :)

Merged! Thanks!


Reshard Error in RN-50 for b20

Config is mentioned here
Tensor Details: --> shape=Shape([1, 1, 62720, 64]), dtype=DataType::BFLOAT16, layout=Layout::ROW_MAJOR
Input Config: tt::tt_metal::MemoryConfig(memory_layout=TensorMemoryLayout::HEIGHT_SHARDED,buffer_type=BufferType::L1,shard_spec=tt::tt_metal::ShardSpec(grid={[(x=0,y=0) - (x=7,y=7)]}, shape={980, 64}, orientation=ShardOrientation::ROW_MAJOR, halo=false))
Output Config
tt::tt_metal::MemoryConfig(memory_layout=TensorMemoryLayout::HEIGHT_SHARDED,buffer_type=BufferType::L1,shard_spec=tt::tt_metal::ShardSpec(grid={[(x=0,y=0) - (x=7,y=6)]}, shape={1120, 64}, orientation=ShardOrientation::ROW_MAJOR, halo=false))
Error detals.
E           RuntimeError: TT_THROW @ ../tt_metal/impl/kernels/kernel.cpp:220: tt::exception
E           info:
E           1760 Bytes unique+common runtime args targeting kernel reshard_reader on (x=0,y=0) are too large. Cannot be written as they will run into memory region reserved for result. Max allowable size is 1024 Bytes

@shwetankTT do you want to try cherry-picking this commit and seeing if it works? (I haven't looked into optimizing perf much for this, but this should be performant unless there are congestion issues)
bf4ebf8db39b7136dc2a8b3af4a0533cbe7e6f7e

@tt-aho Yeah your commit seems good. Can you please merge it.

@shwetankTT this is merged now

Closing issue, thanks @tt-aho


App positioning is off

Since update 0.6.11 the app positioning is off and setting is cut off

Hi, thanks for creating an issue. Sorry, but i'm unable to view your attached screenshot. Could you upload it to imgur?

https://i.imgur.com/HWhKxru.jpg

https://i.imgur.com/HWhKxru.jpg

Okay, does retabbing into the game fixes it?

Nope i think something broke into the positioning usually it's centered but now its cut off notice the version of the app is also different before it was at the very bottom left of the screen.

The overlay normally takes the same position as the game. But these seems way of in your screenshots. Just as a test - Could you try normal windowed mode?

 Still same issue in windowed mode
here's a screenshot to show the issue more clearly

A little update when price checking an item around this area where it cuts off. Still same issue in windowed mode
here's a screenshot to show the issue more clearly

I'll release a new version soon but i'll be marked as pre release. So you need to update it yourself. If everything works i'll remove the prerelease tag.

Where do i find the pre release version?

It'll be visible here: https://github.com/Kyusung4698/PoE-Overlay/releases but it's not released yet.

Having the exact same issue. Positioning of the overlay is just shifted upwards

I have exactly the same issue, using windowed fullscreen and switching to fullscreen has the same cropping issue. Was fine in the previous version.

0.6.12 (2020-03-24)

fix not covering the game correctly

Hi, i've provide a pre-release. Please let me know if it's working now and i'll release it.

Seems to be working for me

Perfect. Thanks for your feedback.


Implement Non-Volatile Key-Value store

Add key value store that enables to save keys with any length to nvs.

Taken over by #188


updating contributing guidelines and the site yaml for new branch

@joaedwar please review the contributing guidelines.

Fixes issue #77

Fixed Joan. Going ahead and merging this.


Always reset the response message when hitting an error

Pull Request Test Coverage Report for Build 113

0 of 4 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 51.376%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

driver.go
0
4
0.0%

Totals

Change from base Build 112:
-0.1%

Covered Lines:
1008

Relevant Lines:
1962

💛  - Coveralls


How to configure Ribbon to be Hystrix aware?

I cannot find the documentation about how to configure Ribbon to be Hystrix aware(in a video one of the netflix engineers mentioned this option) so that the instance will be take off the load balancer when the circuit is open. Can anyone help?
Also, if above is possible, what is the default behavior when all instances' circuits are open?

Here is one way https://github.com/Netflix/ribbon/tree/master/ribbon#ribbon-annotations

Thanks for quick response. Is there a way to do it with spring cloud configurations?


Properly detect partition id for 3-nodes layout as well

The validated-architecture-1.yml file has a way to detect what partition
has to be grown depending on the OS. This was missing from the
3-nodes.yml.
As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running

/approve


Unable to pick a color on Windows 8

When I select the color in my code, and press Alt+c p, it doesn't do anything. Even if I try opening the command palette, and typing "Pick color", the same result.

Hi @Abhirajshri-programmer, thank you for the comment.
Could you explain more?
Copy this template:
https://raw.githubusercontent.com/anseki/vscode-color/master/.github/ISSUE_TEMPLATE.md

Extension Version: 0.4.5
VS Code Version: 1.56.2
OS Version: Windows 8.1

Steps to Reproduce:

When I press Alt+c p, nothing happens.
Even if I do the same by using the command palette.

Please copy all of this template:
https://raw.githubusercontent.com/anseki/vscode-color/master/.github/ISSUE_TEMPLATE.md

Extension Version: 0.4.5
VS Code Version: 1.56.2
OS Version: Windows 8.1
Node.js Version: 14.17.0
NPM Version: 6.14.13

Steps to Reproduce:

When I press Alt+c p, nothing happens.
Even if I do the same by using the command palette.
Log: no log.

Sorry, what does "no log" mean?

Sorry, what does "no log" mean?

Meaning I didn't have any log.

If really nothing was output in the log list, your VS Code may be broken, because many log lines are output from almost extensions and VS Code itself even if Color Picker is not installed.
VS Code might be restored by re-installing.

No reply came, then this abandoned issue is closed.


[9.4.x] ISPN-11101 Purge on JDBC shared stores can cause deadlocks

https://issues.jboss.org/browse/ISPN-11101

@ryanemerson I added a commit to add the flag in the other handleInStoreExpiration method as well

Thanks @danberindei


Cannot use Dates as query params

[x] I have checked that the SDK documentation doesn't solve my issue.
[x] I have checked that the API documentation doesn't solve my issue.
[x] I have searched the Box Developer Forums and my issue isn't already reported (or if it has been reported, I have attached a link to it, for reference).
[x] I have searched Issues in this repo and my issue isn't already reported.

Description of the Issue
Trying to use getEvents functionality:
  const events = await client.events.getEvents({
    streamType: 'admin_logs' as GetEventsQueryParamsStreamTypeField,
    limit: 10,
    eventType: ['UPLOAD'],
    createdAfter: { value: new Date('2024-06-09T10:53:43-08:00') },
  });

I am getting:
{
    "type": "error",
    "status": 400,
    "code": "bad_request",
    "help_url": "http://developers.box.com/docs/#errors",
    "message": "Invalid created_after parameter",
    "request_id": "du1a5ehqkfz86qkm"
}

Tried to do the same with CURL I am getting the same for created_after with + in the timestamp, BUT - it does work with a -.
example:
created_after: 2024-06-10T01:31:53-01:00 - WORK
created_after: 2024-06-10T01:31:53+01:00 - DOES NOT WORK
In this SDK I saw you have this function:
dateTimeToString(dateTime: DateTime): string {
return dateTime.value.toISOString().match(/^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}/)![0] + '+00:00';
}
That adds this +, which always failing the usage of it.
Versions Used
Typescript SDK: 1.0.0
Platform: typescript v4.8.4

Hi @omri-benarye-cyera
As you pointed out, it looks like this endpoint have some problem with positive offsets. Let me reach out to service owners to confirm it

After further investigation it looks like this could be matter of encoding. + sign is interpreted as white space when used in the URL. You should encode it to the form of %2B. Then the cURL request works. I guess the SDK should do the same.

Tried using %2B with CURL and it does work!
So I guess dateTimeToString should be edited - to have '%2B00:00' instead of '+00:00'.
(Tried to open PR for it but I do not have permissions)

Actually the root cause is a bit different in the SDK. In case datetime was used as query param, it included quotes that caused a problem with the request.
This SDK is actually generated based on our custom codegen engine which is currently private. I just submitted a fix for it, so it should be downstreamed to this repo soon.

Fixed by #255. Fix should be released with the new version of the SDK.

Thank you @mwwoda for the fast resolve!


SD Card / SPI for Badger 2040 W

Is it possible to connect an SD Card to Badger 2040 W using the microSD card module and the SPI interface? If so, which pins can I use?

It looks like GPIO 0, 1, 2 and 3 are available which according to https://pico.pinout.xyz/ is a complete SPI bus, which should work with the micropython-lib SDCard driver (https://github.com/micropython/micropython-lib/blob/master/micropython/drivers/storage/sdcard/sdcard.py). This bus would be shared by the screen, though.
I don't know if there are any gotchas that might stop it from working, but it's worth a try.


Added binary_clock.py

@Gadgetoid and @IDF31 here's mine, please test and let me know, it works great on my phat (4x8)

@Pyroseza @IDF31 the string method of converting a number to binary and stepping through each bit is actually unnecessary, since a bitwise AND operator (&) can check if a specific bit in a number is set.
def draw_binary(value, y, color):

    # Our value will be a number <= 59
    # It takes 6 binary digits (bits) to represent all possible values
    # For example: 17 minutes = 0b10001
    # If we step through these binary digits from right to left,
    # this results in the first and fifth pixels being lit.
    for x in range(8):

        # The & operator gives us a result containing all the bits that
        # are set in both values, for example:
        #
        # 1 & 1 = 1 (ie: 0b1 & 0b1 = 0b1)
        # 2 & 1 = 0 (ie: 0b10 & 0b01 = 0b00)
        # 7 & 27 = 3 (ie: 0b00111 & 0b11011 = 0b00011
        if value & 1:
            # Light pixel at x, y if least significant bit is set.
            unicornhat.set_pixel(x, y, color)

        # Shift number right one place, placing the next bit at 1
        # EG: 0b00010 becomes 0b00001
        value >>= 1

This steps through the individual binary digits in a number and draws them least-significant-bit first from left to right.

Elegant I like it, I’ll make the change in a few minutes

@Gadgetoid I have a slight problem with this. By using the fixed width I can set and unset the LEDs correctly, no flashing effect.
If I use your method method, I’d have to run an additional for-loop just to clear all the values. If use unicorn_hat.clear or unicorn_hat.reset it creates a flashing effect. Maybe you can advise another workaround for this? I’m thinking of just setting the LEDs to be off as the loop starts just before the condition check...
Also I don’t know if you’ve run my version of it? I don’t use full 8-bit width. I have a variable length and pass it in as a parameter. I.e On the first row I have 2 4-bit values for month and day, then I have 3 6-bit values for normal right-aligned binary values. The 6 left over LEDs on the left are reserved for the “alarm”. I personally don’t like left aligned binary but I can change my script to cater for that.
Anyway I will update my pull request when it’s working the way I want without a flashing effect

You don't have to run the full bit-width with my example, you can step through any number of bits and set/clear accordingly:
for x in range(bit_width):
    if value & 1:
        # Set pixel
    else:
        # Clear pixel

    value >>= 1

This will step from right-to-left through the bits of a number and stop when it reaches bit_width.
So March, 03, would be 0b0011 and a 4 bit loop would set the first two pixels on that row, and clear the last two pixels.

doh! okay, making changes now

Alrighty @Gadgetoid and @IDF31 have looky now, I've tested and it works fine

Looks good, works for me in both Python 2 and 3. Thank you both for your joint effort!


18.7 captive portal and vouchers doesn't work

Hi.
After upgrading to 18.7 my exisiting vouchers are gone...
OK. Now when I'm creating new vouchers I get the *.csv for download.
But the list is still empty.
After this checkup I deleted the voucher server and created a new one.
But still doesn't work.
Is there a log file int the cli for the voucher server?

Sounds like the database was damaged. I'm not sure what is where, maybe @AdSchellevis has a bit of time to explain.

I have exactly the same problem. It started after upgrading from 18.1.11 to 18.1.13. I tried to track down the changes and apparently the problem is related to https://github.com/opnsense/core/commit/fbca4bf4cc36a9dff4d89d9564cb595de92d6be1
For 18.1.13 reverting the changes make the vouches visible again.

@frank499 thanks for pinning this down, officially handing this over now

at my end the vouchers look normal

@frank499 If this page is empty on your end, could you gather some network responses from the webbrowser? maybe one of the endpoints fails in some scenario.

Soo.
I played around with the voucher server.
Yesterday I told you that I deleted my old and created a new voucher server and nothing works.
Today I created a new server again but now with another name of the server.
Now I'm a surprised... it works fine.

@advcron same question, when inspecting the network traffic in your browser, are there failed requests, if so, what does the response look like.

Sorry but how can I " inspecting the network traffic in your browser" ?

When I enter to voucher menu:

When I click generate voucher:

@advcron ok, got it, can you try to add a voucher group without a space in it? I'm guessing that's the issue.

There isnn't any space in voucher gorup

"Capative Voucher"?

I can reproduce this here, no further actions needed.

This is it !!!
It works on 18.1.13 and 18.7.
Thank you very much!

@advcron I'm still going to fix the issue, it should work with the space in between

Hi,
Could it be that there is an similar issue when you use ä,ö,ü in the groupnames?
Since i addet a groupname with some umlauts, i see also no vouchers for this group, and the login page does not apere on the devices...
Thx
Paul

After up to 18.1 also umlauts ar working in groupnames

@peysche have you even tried the supplied patch?

hi, yes latest release fixes the problem!
thx
paul


generate json and png

To run, please follow this command https://github.com/cartesi/dave/tree/feature/dave-rollups/prt/lua_poc#run-doom-showcase-with-graphics-on
2 json files (current-state.json and hero-claims.json) are generated under prt/lua_poc/utils/
2 PNG files (the agreed one.png and the disagreed two.png) are under prt/lua_poc/snapshots/pixels/

There are some malformed values like {"value":"äØF²(Å/+l\u0014HzBé±\u0013}WÏà¾d\u001fï","key":"digest"}], can you make sure they are proper hex strings?

I'd also suggest we remove snapshot feature at:

https://github.com/cartesi/dave/blob/feature/gen-data/prt/lua_poc/computation/machine.lua#L67-L82
https://github.com/cartesi/dave/blob/feature/gen-data/prt/lua_poc/computation/commitment.lua#L42
https://github.com/cartesi/dave/blob/feature/gen-data/prt/lua_poc/computation/commitment.lua#L64

what about the file view.sh, do we still need it

since we have removed app/snapshots folder, now the command to run becomes
mkdir -p pixels
docker run --rm \
    --env MACHINE_PATH="/app/lua_poc/program/doom-compute-machine" \
    --env DEPLOY_TO_ANVIL="true" \
    --mount type=bind,source="$(pwd)/pixels",target=/app/pixels \
    dave:latest graphics

what about the file view.sh, do we still need it

I think it can be removed as well.

I took an easy path and detect "digest" key and convert its value, during the flatenning phase. So I don't need to mess around with the merkle tree itself

This is looking great @ZzzzHui ! @jplgarcia is there anything else you'd like to add or change?


Update url: TropicalNumbers

Package has been migrated to
https://github.com/TensorBFS/TropicalNumbers.jl


Problems building due to cbor

Hi,
I'm very new to AWS & Free RTOS. I've done quite a bit of work with ESP32 on Arduino but none with native compiler etc. I came across this demo when researching how to get into AWS IoT Core and found the instructions excellent thank you. However I have hit a brick wall in terms of my understanding and was wondering if someone more knowledgable than me could help out please?
Followed instructions as far as https://github.com/FreeRTOS/iot-reference-esp32c3/blob/main/GettingStartedGuide.md#3-build-and-flash-the-demo-project
Initially had a problem building due to the cbor component not being found. Followed instructions here to try and resolve this.
https://components.espressif.com/components/espressif/cbor by running:
idf.py add-dependency "espressif/cbor^0.6.0"

The above fixed that problem but now build seems to have multiple issues and the build output ends with:
_HINT: The issue is better to resolve by replacing format specifiers to 'PRI'-family macros (include <inttypes.h> header file).
ninja failed with exit code 1, output of the command is in the /home/jason/esp/iot-reference-esp32c3/build/log/idf_py_stderr_output_26098 and /home/jason/esp/iot-reference-esp32c3/build/log/idf_py_stdout_output_26098_

The output of the build is in build.txt attached below.
System information

Hardware board: ESPRESSIF ESP32-C3-DevKitC-02
IDE used: Command Line
Operating System: Ubuntu 20.04.5 LTS
Code version: v202212.00-2-ged74af2
Project/Demo: iot-reference-esp32c3

Steps to reproduce bug
idf.py -p /dev/ttyUSB0 flash monitor > build.txt
build.txt
Many thanks...

@cloisterbell42 Hello. Try using another ESP-IDF version. In my case it was fixed by using ESP-IDF v4.4.3
When I used the latest 5.1-dev-3025-g49551cc48c I was struggling with the same issue you mention.

Hi @cloisterbell42,
As @Yoimer pointed out, it's most likely an issue with your ESP-IDF version. This repo has been mainly tested on 4.4.x. That said, what version of ESP-IDF are you using that is not working? @Yoimer, did you try with the release version of 5.0 or just the dev version?
Best,
Jason Carroll

Thank you @Yoimer :)

Hi @Yoimer & @jasonpcarroll
Thank you so much for your advice. You were both right, I was using the dev version of ESP-IDF. I hadn't realised that the master branch was the latest dev version.
Have switched to tags/v5.0 and it seems to be working now.
Thanks again,
Jason


Add fingerprint token filter #7982

Description
Add fingerprint token filter
Issues Resolved
Closes https://github.com/opensearch-project/documentation-website/issues/7982
Version
all
Checklist

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

@varun-lodaya The documentation is awaiting tech review and approval, which is delaying progress. Could you please suggest alternative reviewers who can assist with this task in a timely manner? We're eager to move this forward. Thank you.

@varun-lodaya The documentation is awaiting tech review and approval, which is delaying progress. Could you please suggest alternative reviewers who can assist with this task in a timely manner? We're eager to move this forward. Thank you.

@varun-lodaya This is over a month old. We need tech review approval to move it forward in the documentation process. Please review this week or provide a peer who can review it. Thank you.


[cluster-test] Add --wait-on-failure

This clause allows to keep cluster test(for a short duration, up to 20 minutes) alive on the issue, allowing some time to debug.
We need to be cautions about using it, but it's a good last resort measure.
cc @runtian-zhou

@bors-libra r+

:pushpin: Commit ef35bc5 has been approved by snakech

@bors-libra retry

:hourglass: Testing commit ef35bc56dea4d0d59069e66123b8969915c86074 with merge d8cdff02e71a64c5a2c1820f3b7c06b71d94063e...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: snakech
Pushing d8cdff02e71a64c5a2c1820f3b7c06b71d94063e to master...


Can't retrieve player bitrate

Hi,
I'm using clappr to read some HLS streams. I need to get player bitrate. To do so, i'm using this piece of code :
player.listenTo(player.core.getCurrentContainer(), Clappr.Events.CONTAINER_BITRATE, function(bitrate)
		{ console.log(' container bitrate changed... '+ bitrate);
	});

But the callback method is never called.
However i do receive events such as Events.CONTAINER_SEEK.
Thanks.

@wholegrn are you using Safari for your tests?
I tested your snippet on http://cdn.clappr.io and received the events correctly using this code on both Chrome and Firefox:
var playerElement = document.getElementById("player-wrapper");
var player = new Clappr.Player({
  source: 'http://www.streambox.fr/playlists/test_001/stream.m3u8',
  poster: 'http://clappr.io/poster.png',
  mute: true,
  height: 360,
  width: 640
});
player.attachTo(playerElement);
player.listenTo(player.core.getCurrentContainer(), Clappr.Events.CONTAINER_BITRATE, function(bitrate) { console.log(' container bitrate changed... ', bitrate); });

If you are using Safari, we use it's native HLS implementation, which doesn't expose bitrate change events.

@towerz Indeed, i used Safari for my tests.
I tested my code on Chrome and it worked !
Thank you.


Dead clicks on side bar - Desktop web app - Portrait Monitors

Describe the bug
In portrait mode the sidebar collapses. When opened, clicking on the following items result in no actions:

Profile Image
Display Name
User Handle
Follower Count
Follows Count
'Profile' navigation button

Portrait desktop in use is 1080x1920
To Reproduce
Steps to reproduce the behavior:

Open up bsky.app on Portrait monitor
Open the collapsed side bar
Click on the items laid out in bug description to observe lack of behavior

Expected behavior

Clicking on the profile image, display name, user handle, or "Profile" navbar item should navigate to the user's profile (bsky.app/porfile/[user]
Clicking on the 'Followers' item should navigate to the user's followers list (bsky.app/profile/[user]/followers)
Clicking on the "Follows" item should navigate to the user's follows list (bsky.app/profile/[user]/follows)

Screenshots
Dead click areas boxed in red
Details

Platform: Desktop Windows, Chromium browsers (Edge and Chrome tested), Firefox, Assuming all browsers are affected
Platform versions:

Firefox: V116.0.2 64-bit
Edge: Version 115.0.1901.203 (Official build) (64-bit)
Chrome: Version 115.0.5790.173 (Official Build) (64-bit)

App version: Bsky Build V 1.45.0

Yeah we basically don't have responsive styling in yet

This should be fixed by #1437


Authenticator does not allow PUBLIC_ACCESS role

Checklist

[X] I have looked into the Readme and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Description
Hi, i am using stateful auth. The usecase is like this - i have page, that should be accessible by both unauthenticated (anonymous) and authenticated users.
I am unable to achieve this, because every time unauthenticated user access the page, it gets redirected to login.
I have step debugged, and i believe that somehow \Auth0\Symfony\Security\Authenticator is missing check forPUBLIC_ACCESS role - if it is allowed for the request and session is missing, it should allow user to access the page.
Reproduction
return static function (SecurityConfig $securityConfig): void {
    $securityConfig
        ->provider('auth0_provider')
        ->id(\Auth0\Symfony\Security\UserProvider::class);

    $securityConfig->firewall('main')
        ->provider('auth0_provider')
        ->customAuthenticators(['auth0.authenticator']);

    $securityConfig->accessControl()
        ->path('^/some-public-page$')
        ->roles('PUBLIC_ACCESS');
};

With such config, create controller with route to url /some-public-page, access it as anonymous user (anonymous tab in browser etc) and instead of accessing the site, you will get redirected to login.
Additional context
If i tweaked \Auth0\Symfony\Security\Authenticator::supports() method, to return false, when PUBLIC_ACCESS role is required for the request, it worked as expected -> $this->getUser() in controller returns user for authenticated users and null for anonymous.
Other option that worked for me was tweaking \Auth0\Symfony\Security\Authenticator::onAuthenticationFailure() - check for PUBLIC_ACCESS access control, if there it is, return null, then it worked as intended.
The key for my workaround was to replace \Auth0\Symfony\Security\Authenticator in DIC with my own implementation - it got injected \Symfony\Component\Security\Http\AccessMapInterface and then line this:
[$attributes] = $this->map->getPatterns($request);
if ($attributes && [AuthenticatedVoter::PUBLIC_ACCESS] !== $attributes) {
    return null;
}

jwt-auth-bundle version
not-relevant
Symfony version
6.3.7
PHP version
8.2.12

Hi @JanMikes, thanks for reporting this.
The Authenticator guard is not designed to support anonymous access on routes it's applied to. While this change would be beneficial in cases like this, changing it within the SDK would be a breaking change. We'll need to wait to make such a change until the next major. I have backlogged your suggestion in the meantime for the next major-work opportunity.

Thank you.
I appreciate confirming that it is not error on my side :-).

In case anyone interested, here is how i solved the situation: https://github.com/JanMikes/auth0-symfony/commit/0c98d088750c938d2c40d9f4bca99d5f24ad7f11
I am using this fork in my app.
My security.php config:
return static function (SecurityConfig $securityConfig): void {
    $securityConfig
        ->provider('auth0_provider')
        ->id(UserProvider::class);

    $securityConfig->firewall('dev')
        ->pattern('^/(_(profiler|wdt)|css|images|js)/')
        ->security(false);

    $securityConfig->firewall('main')
        ->pattern('^/')
        ->provider('auth0_provider')
        ->customAuthenticators(['auth0.authenticator']);

    $securityConfig->accessControl()
        ->path('^/(url1|url2)')
        ->roles([AuthenticatedVoter::IS_AUTHENTICATED_FULLY]);

    $securityConfig->accessControl()
        ->path('^/')
        ->roles([AuthenticatedVoter::PUBLIC_ACCESS]);
};


Ignore data from localhost

Hi !
Thanks for your very nice plugin.
By developing a React project, I've seen that the http://localhost:8080 is included in the analysis.
Maybe the plugin should ignore such cases because there is no internet bandwith usage associated with localhost project (exept API resquests or network images for example).

Hi Thibaud. The addon is for a large public, not only developers.
We, developers do not use only localhost url, but also something.localhost, something.dev, etc
Feel free to contribute to the code by adding a condition on the domain here: https://github.com/supertanuki/Carbonalyser/blob/master/script.js#L26


Undefined method to_prepare

Hi. For the first time trying your gem and here is what I get on rails 5.1.3 and react-rails 2.2.1

It seems there is no server running or you are not in a rails project root directory
=> Booting Puma
=> Rails 5.1.3 application starting in development on http://localhost:3000
=> Run rails server -h for more startup options
Exiting
/home/glaux/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/react-rails-hot-loader-0.8.0/lib/hot_loader/railtie.rb:14:in block in <class:Railtie>' : undefined method to_prepare' for ActionDispatch::Reloader:Class (NoMethodError)

@Seybo Have you got the solution?

@HardikUPurohit Nope. It's not worth it anyway. Just forgot it. Too many problems with this hot reloading thing AFAIS

same thing

It's because of deprecated code.
As hotfix add this patch to config/initializers/patches.rb
ActionDispatch::Reloader.class_eval do

  def self.to_prepare &block
    ActiveSupport::Reloader.to_prepare &block
  end

end


chore(Topology): move homeomorph

Move Topology.Homeomorph to Topology.Homeomorph.Basic for the future split of this file.

Mathlib.Topology.Homeomorph -> Mathlib.Topology.Homeomorph.Basic

[ ] depends on: #18689

Created at a wrong time this PR is deprecated


Add repos collaborators

What is the purpose of the change
Add repos collaborators
Checklist

[x] I have read the Contributing Guidelines on pull requests.
[ ] I have explained the need for this PR and the problem it solves
[ ] I have explained the changes or the new features added to this PR
[ ] I have added tests corresponding to this change
[ ] I have updated the documentation to reflect this change
[ ] I have verified that this change is backward compatible (If not, please discuss on the Linkis mailing list first)
[ ] If this is a code change: I have written unit tests to fully verify the new behavior.

LGTM.


Fix engines version specification

Fixes #156

Coverage remained the same at 94.276% when pulling b8fefb886c55ee3401406aa4ede9b9f129e3547f on no23reason:master into 41a5a8f82c4a4842fdbb3dc26e93e2037dd9c70c on patw0929:master.


Restore a specific backup, not just last one

Hi there,
I have a question about the backup feature mentioned in the docs. It says we can restore a backup by deleting the data directory. But, how do we see all the backups we have and choose a specific one to restore?
For example, if we make a mistake in the database and then make another backup, we would want to go back to the backup before the mistake, not the very last one.
Is there a way to do this right now? If not, could this be something you can add? It would be really helpful.
Thanks for looking into this!

You are right, the point-in-time recovery is currently a little bit under-documented.
The docker image with the postgresql instance will react on the environment variable DB_RESTORE_PITR. If this is set it will be used as content for the --target of pgBackrest (https://pgbackrest.org/command.html#command-restore) which will then restore up to this point.
You can get infos about available backups from the backup-info.sh within the container (https://pellepelster.github.io/solidblocks/rds/usage/index.html).
You are right this needs to be wired together and better documented in the Hetzner postgres module, I will see what I can do.

v0.2.4 now has the option to specify a a time for PITR, see also https://pellepelster.github.io/solidblocks/hetzner/rds/#input\_restore\_pitr


session.create_tmp has slightly surprising behavior

How would this feature be useful?
I'm in the middle of diagnosing some build instability (files appearing in a directory which I don't expect to be there) and in the process noticed something about .create_tmp -- I'm not sure it's related to my specific issue yet, but to me it seems worth addressing independently. Filing to see what others think.
Specifically... session.create_tmp is documented as "create and return a temporary directory" -- but it actually seems to always use a fixed directory path, tmp, and one that may exist "accidentally" if some other thing happened to create a directory named that, or get polluted accidentally if some other process starts writing to that path.
More surprisingly I think is if someone does this:
@session()
def foo(session):
    one = session.create_tmp()
    two = session.create_tmp()

they actually are unlikely to realize that they've gotten the same exact path twice there, one and two are going to be the same tmp/ directory.
Describe the solution you'd like
I'd personally definitely expect behavior more like tempfile.TemporaryDirectory and os.mkdtemp, namely that creating temporary directories gives me a path to a directory I can be sure:

didn't exist beforehand
isn't going to be being used by some other process
is going to differ if I call it twice

Describe alternatives you've considered
Certainly just ignoring session.create_tmp is an option, but filing this as it seems a bit like a small footgun as-is.
Anything else?
No response

It was pointed out to me that create_tmp also sets TMPDIR (which indeed explains my original issue) -- that seems like even more surprising behavior than the first part to me. It now seems worth avoiding this function entirely to me, so going to close this, but obviously if someone agrees with my assessment (on both being quite surprising behavior) and thinks there's some way to nudge it to have less surprising behavior, let me know.

if someone agrees with my assessment (on both being quite surprising behavior) and thinks there's some way to nudge it to have less surprising behavior, let me know.

Since you asked :) I was expecting create_tmp to be a simple wrapper around https://docs.python.org/3/library/tempfile.html#tempfile.TemporaryDirectory that does not do anything fancy like setting TMPDIR. As it stands, create_tmp is an attractive nuisance. It appears useful, but has multiple important caveats.


Memgraph platform

Add memgraph-platform chart.
Upgrade memgraph chart default version to 2.13.0

Hi @tewnut, thanks a lot for opening a PR 🚀 . I will look into this in the next few days!

Been using this somewhat successfully the last week or so. I am not knowledgeable enough in Helm charts to give a proper review, but here are some pointers as a user:

Deploying this from IaC, it would be nice to (optionally) provide existing volume claims for storage
I didn't manage to get the ingress to work properly. Haven't spent too much time debugging the issue.
See review comment regarding nodeSelector, tolerations and affinity

Hello @CarlEkerot, thanks so much for the review! @antejavor is currently on his AL, but he'll get back to you as soon as he's back. I'm glad to hear that it's going successfully for you. Could you tell us what you are working on? :)

Hello @CarlEkerot, thanks so much for the review! @antejavor is currently on his AL, but he'll get back to you as soon as he's back. I'm glad to hear that it's going successfully for you. Could you tell us what you are working on? :)

Mostly poking around with memgraph and a few other graph DBs :) Looking forward to using this chart once it's in a stable state :+1:

Nice to hear that you're exploring Memgraph, @CarlEkerot  :) Feel free to ask if you have more questions, and don't hesitate to reach out on our discord or book an office hours call !

Been using this somewhat successfully the last week or so. I am not knowledgeable enough in Helm charts to give a proper review, but here are some pointers as a user:

Deploying this from IaC, it would be nice to (optionally) provide existing volume claims for storage
I didn't manage to get the ingress to work properly. Haven't spent too much time debugging the issue.
See review comment regarding nodeSelector, tolerations and affinity

can you share the ingress section of your values.yaml file?

Hi @tewnut, thank you so much for providing the chart for the Memgraph Platform. With the Memgraph Lab image being available on the Docker hub now, we have been working on a new way of running the Memgraph Platform that should ease the deployment process, and that's why we still need to review this. With Memgraph 2.15, we will make these changes public, and then we'll see what to do with Helm Charts (how to approach the Memgraph Platform deployment properly).
@CarlEkerot thank you for the review as well! 👏  Stay tuned for the updates 😄

Hi @tewnut, thank you so much for providing the chart for the Memgraph Platform. With the Memgraph Lab image being available on the Docker hub now, we have been working on a new way of running the Memgraph Platform that should ease the deployment process, and that's why we still need to review this. With Memgraph 2.15, we will make these changes public, and then we'll see what to do with Helm Charts (how to approach the Memgraph Platform deployment properly).
@CarlEkerot thank you for the review as well! 👏 Stay tuned for the updates 😄

Thanks, looking forward to the new release...

Yeah, I think this is altogether better approach. Thanks for the update.
Let me try creating the charts for my k8s cluster. When things are in good shape, I will create a PR in this repo, should be a couple of days...

Yeah, I think this is a better approach altogether. Thanks for the update.
Let me try creating the charts for my k8s cluster. When things are in good shape, I will create a PR in this repo, should be a couple of days...

Keep in mind we updated the contribution guide a bit: https://github.com/memgraph/helm-charts/commit/c1cc60603a8ea2f3572e5f5685190b65b60b7c7b
If you are going to create a new PR, please use the latest release branch and create a PR on a specific release branch.
If you are going to use this PR it is also fine.

Hi @tewnut can we close this PR now?


Does Vapid support switching languages?

I'm now the process of testing Vapid and I'm very impressed by how easy we I can set up (I'm a designer) However, my clients would like to have 2 languages on her site. The dashboard is ok to be one language but the site should be able to support 2 languages.

@srobbin is looking at it, we are currently drafting the spec here: #19

@gadd-ferreira thank you