chore(test): update sample for danish

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Linux kernel updates 2022-05-25

Description of changes
New versions available (see history).
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@Ma27 updated patch for 5.17.11 - 5.17.11-hardened2

@Izorkin would you mind linking the PR?


Missing three ids: 69449, 69450, 69451 (likely the closed beta rewards?)

Thank you for this package!
My collection contains the three closed beta reward cards, and when I used https://github.com/kelesi/mtga-utils to try to scrape my collection, these three ids were not found in the pool, so they probably pertain to those cards!
I don't know which is which, but these are the names:
'As a thank you, every player who participated in the Closed Beta will receive one digital copy each of three cards from Guilds of Ravnica: Mythic Edition: Teferi, Hero of Dominaria; Ral, Izzet Viceroy; and Vraska, Gorgon Queen.'

Thanks for the report! We're also tracking this issue here https://github.com/mtgatracker/mtgatracker/issues/307 and hope to have it resolved by the end of the day.

fixed in https://pypi.org/project/MTGA/0.4.1/ :)


[9.x] Add AWS S3 delete multiple files using deleteObjects method

Hi,
I needed to delete 100+ files on AWS s3. the Storage::disk('s3')->delete() delete a single file so if i loop through the 100+ files and do the Storage::disk('s3')->delete($file) it will do 100+ request to s3 for 100+ files.
So I searched and I find out that AWS s3 allows you to delete multiple files using the AWS client deleteObjects method which accepts an array of object paths e.g ['path/to/file1', 'path/to/file2']. using this it just took 2 secs to delete 100+ files.
more info: https://docs.aws.amazon.com/AmazonS3/latest/userguide/example_s3_DeleteObjects_section.html
I first implemented this as a macro on the Storage facade in my projects. but I think this should be in laravel by default :)
Thanks,
Anees

I think this should added here instead
https://github.com/thephpleague/flysystem-aws-s3-v3

We should wrap the api call in try/catch and all
throw_if($this->throwsExceptions(), $e);


NIFI-4774: Allow user to choose which write-ahead log implementation …

…should be used by the WriteAheadFlowFileRepository
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

I tested this and I was able to switch back and forth between MinimalLockingWriteAheadLog and SequentialAccessWriteAheadLog. +1 from me.
It's best to make this switch while there are 0 flowfiles in the repository.  With flowfiles in the system, going from MinimalLockingWAL to SequantialAccessWAL worked, but the opposite had some issues.

@mattyb149 and @markap14 with the 1.6.0 release approaching, do you think we've allowed enough time for review and testing?  Is this good to go?  Thanks.

+1 LGTM, I tested switching back and forth and everything looks good. Thanks for the improvement! Merging to master


Stats stopped on 11th September

Looks like there is a 400 error request to the stats API

Now they seem to be working?


Difficulties installing goldair_climate in home assistant running in docker

Ubuntu 18.04.2 LTS
Docker image: homeassistant/home-assistant
Home Assistant version 0.97.2
Error loading custom_components.goldair_climate. Make sure all dependencies are installed
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/loader.py", line 355, in _load_file
    module = importlib.import_module(path)
  File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/config/custom_components/goldair_climate/__init__.py", line 16, in <module>
    from homeassistant.components.climate import ATTR_OPERATION_MODE
ImportError: cannot import name 'ATTR_OPERATION_MODE' from 'homeassistant.components.climate' (/usr/src/app/homeassistant/components/climate/__init__.py)

I have tried the following "fix"
I download pytuya-7.0.2.zip
I extracted the file called pytuya-7.0.2.zip\pytuya-7.0.2\pytuya__init__.py
then copied it to \custom_components\pytuya\__init__.py
then i edited \custom_components\goldair_climate\__init__.py
and changed line 139 from import pytuya to import custom_components.pytuya as pytuya
This did not work.

Hi kiwijunglist
HA version 0.96 and later implements a new version of the Climate component (Climate 1.0). So Nik's component won't work without an update.
I have my own fork (version 1.0) of Nik's project (based on his version 0.01, not his latest 0.03) which I made my own modifications to, which essentially made the same required operational updates as he later did in his updated version 0.03.
My Goldair component stopped working when I upgraded HA, so I have updated my fork for the changes to the Climate component so that it works with HA 0.96+
While you wait for Nik to update his, you could try mind here:
https://github.com/SmbKiwi/homeassistant-goldair-heater/tree/v2.0
Hope that helps you out.
SmbKiwi

That's great. i'll switch over to yours and see how I go.  Might try it
now.  Thanks!
I'll need to change back over to goldair app because I also tried to get it
going unsuccessfully with the tuya app.
On Sun, Sep 22, 2019 at 5:05 PM Shane<EMAIL_ADDRESS>wrote:

Hi kiwijunglist
HA version 0.96 and later implements a new version of the Climate
component (Climate 1.0). So Nik's component won't work without an update.
I have my own fork (version 1.0) of Nik's project (based on his version
0.01, not his latest 0.03) which I made my own modifications to, which
essentially made the same required operational updates as he later did in
his updated version 0.03.
My Goldair component stopped working when I upgraded HA, so I have updated
my fork for the changes to the Climate component so that it works with HA
0.96+
While you wait for Nik to update his, you could try mind here:
https://github.com/SmbKiwi/homeassistant-goldair-heater/tree/v2.0
Hope that helps you out.
SmbKiwi
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nikrolls/homeassistant-goldair-climate/issues/20?email_source=notifications&email_token=AAOFVF3OM4XTTYKGMOFLVFTQK34KHA5CNFSM4IR6IT3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7I6R7I#issuecomment-533850365,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOFVF3SUKK5JJRJSZRC4CDQK34KHANCNFSM4IR6IT3A
.

Hi
I still am unable to use your version.
I get the following problems / errors:
climate.alex (goldair heater) is listed as unavailable in the states page.
2019-09-22 17:35:04 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for goldair_heater which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-09-22 17:36:08 ERROR (SyncWorker_24) [custom_components.goldair_heater] Failed to refresh device state.
2019-09-22 17:37:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.alex is taking over 10 seconds
The heater works fine in the app.
I'm running the latest firmware on the heater (1.0.2)
When I check device information in goldair app it states the IP address is external IP address, however for the configuration I am using the local IP address of the heater.
goldair_heater:

name: alex
host: <IP_ADDRESS>
device_id: xxxxxxx
local_key: xxxxxxxx
sensor: true
display_light: true

Hi
You must not be running the Goldair app when using HA as only one can connect to the heater at a time.
I have not updated my firmware. So if you have then you will need to use a different version of the Tuya api. If you have installed newer firmware, then try the following instructions at the link below but update the code in both the goldair_heater.py file as well as the init.py file:
https://www.geekzone.co.nz/forums.asp?forumid=141&topicid=214631&page_no=3#2272645
I don't think you need to install the code from belzedaar as pytuya has been updated see here: https://github.com/clach04/python-tuya

Thanks, unfortunately editing intit.py does not solve the problem
Line 29: REQUIREMENTS = ['pytuya==7.0.4']
Line 140-142
        import pytuya
        self._name = name
        self._api = pytuya.Device(dev_id, address, local_key, 'device')
        self._api.set_version(3.3)

Homeassistant error log:
ERROR: No matching distribution found for pytuya==7.0.4,
(SyncWorker_21) [homeassistant.util.package] Attempting install of pytuya==7.0.4,
(MainThread) [homeassistant.loader] Loaded goldair_heater from custom_components.goldair_heater,
(SyncWorker_21) [homeassistant.util.package] Unable to install package pytuya==7.0.4: ERROR: Could not find a version that satisfies the requirement pytuya==7.0.4 (from versions: 1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 7.0.1, 7.0.2),
(MainThread) [homeassistant.config] Package goldair setup failed. Integration goldair_heater Requirements for goldair_heater not found: ['pytuya==7.0.4']. (See /config/packages/goldair.yaml:0). ,
(MainThread) [homeassistant.loader] You are using a custom integration for goldair_heater which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.

Hi
It looks like you need to install the latest version of pytuya from https://github.com/clach04/python-tuya (using pip3).  Version 7.0.2 is the latest version that your docker image contains.
Try these methods:

Not sure if installing first on Ubuntu will work - maybe HASSIO can get it from linux phyton environment? Not sure, but you could try in Ubuntu:  pip3 install 'path to the pytuya folder that you have copied from github'/pytuya==7.0.4

You can also try putting the pytuya folder that you have copied from github into the deps subfolder in the HA Config folder.

Install in your python environment in docker image. I think you can do this when installing the dockerfile as follows:
RUN pip3 install --no-cache-dir -r requirements_all.txt &&
pip3 install --no-cache-dir 'path to the pytuya folder that you have copied from github'/pytuya

I use docker compose.
Hopefully I can try #2 because #1/#3 might be too hard / take me a long time. I'm a bit time poor BC had a baby.

I got it sort of working.
custom_components/goldair_heater/init.py
REQUIREMENTS = ['pytuya==7.0.2']
custom_components/goldair_heater/goldair_heater.py
25: REQUIREMENTS = ['pytuya==7.0.2']
136: import custom_components.pytuya as pytuya
137: self._name = name
138: self._api = pytuya.Device(dev_id, address, local_key, 'device')
139: self._api.set_version(3.3)
custom_components\pytuya_init_.py
Downloaded pytuya latest version and placed the init.py file here:
It still has some issues though:
I can turn it on and off.
It correctly shows the current temperature and target temperature and 'swing level'.
The problem is that when I try to change the temperature I am getting this error:
Failed to call service climate/set_temperature. None
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 130, in handle_call_service
    connection.context(msg),
  File "/usr/src/homeassistant/homeassistant/core.py", line 1234, in async_call
    await asyncio.shield(self._execute_service(handler, service_call))
  File "/usr/src/homeassistant/homeassistant/core.py", line 1259, in _execute_service
    await handler.func(service_call)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
    self._platforms.values(), func, call, service_name, required_features
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 349, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 373, in _handle_service_platform_call
    await func(entity, data)
  File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 529, in async_service_temperature_set
    await entity.async_set_temperature(**kwargs)
  File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 390, in async_set_temperature
    ft.partial(self.set_temperature, **kwargs)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/goldair_heater/climate.py", line 116, in set_temperature
    self._device.set_target_temperature(kwargs.get(ATTR_TEMPERATURE))
  File "/config/custom_components/goldair_heater/__init__.py", line 239, in set_target_temperature
    limits = self._TEMPERATURE_LIMITS[preset_mode]
KeyError: None

I also got this log error:
Failed to call service climate/set_temperature. None

The other weird thing is there is no 7.0.4 ???
I can put 7.0.2 and it works, if i put 7.0.4 in requirements then the component will not load.

I've also tried this version of pytuya:
https://github.com/belzedaar/python-tuya/blob/master/pytuya/__init__.py
It seems a bit more stable, but if I issue multiple commands I will get errors, such as:
4:56 PM components/websocket_api/http.py (WARNING)
Disconnected: Did not receive auth message within 10 seconds
4:58 PM custom_components/goldair_heater/init.py (ERROR) - message first occured at 4:57 PM and shows up 7 times
Failed to refresh device state.
4:59 PM custom_components/goldair_heater/init.py (ERROR) - message first occured at 4:57 PM and shows up 3 times
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 130, in handle_call_service
    connection.context(msg),
  File "/usr/src/homeassistant/homeassistant/core.py", line 1234, in async_call
    await asyncio.shield(self._execute_service(handler, service_call))
  File "/usr/src/homeassistant/homeassistant/core.py", line 1259, in _execute_service
    await handler.func(service_call)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
    self._platforms.values(), func, call, service_name, required_features
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 349, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 373, in _handle_service_platform_call
    await func(entity, data)
  File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 529, in async_service_temperature_set
    await entity.async_set_temperature(**kwargs)
  File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 390, in async_set_temperature
    ft.partial(self.set_temperature, **kwargs)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/goldair_heater/climate.py", line 116, in set_temperature
    self._device.set_target_temperature(kwargs.get(ATTR_TEMPERATURE))
  File "/config/custom_components/goldair_heater/__init__.py", line 239, in set_target_temperature
    limits = self._TEMPERATURE_LIMITS[preset_mode]
KeyError: None

Hi
REQUIREMENTS = ['pytuya==7.0.2'] is just a check that the python component is available and installs it in the python environment if it is not already installed. Since version 7.0.2 is already available the check passes. Since version 7.0.4 is not officially available (see https://pypi.org/project/pytuya/) it can't find it. But that doesn't matter since you are importing the updated one, so leaving the requirements set to 7.0.2 works. You could take that line out and it should still work.
Good idea to import it from the custom components folder. Best practice using this method is to put the updated pytuya folder from Github into HA as /custom_components/pytuya/init.py and that will work with "import custom components.pytuya as pytuya" line.
KeyError: None means that when the set_temperature method attempts to run line 239 [specifically _TEMPERATURE_LIMITS[preset_mode] function)] it can't find a match for the preset_mode value in the _TEMPERATURE_LIMITS function. Have you got Preset drop down in the GUI? (see pic below). That function is checking the temperature limits where preset is set to either Comfort or Eco. So it is saying that whatever is stored in preset_mode (the currently set preset as long as it's not Anti-freeze) is not either Comfort or Eco because it can't find a match in the dictionary in the _TEMPERATURE_LIMITS function. I don't get that error using my custom component with older API. But the error doesn't seem to relate to that - it seems to relate to preset value being something other than Comfort, Eco, or Anti-freeze, or it's getting no preset value from preset_mode attribute.

I'm not great at python just learning as I try to understand the code and adapt it, but that's my understanding of what the KeyError indicates.
Of course it could be that the updated firmware doesn't use C, ECO, and AF any longer to indicate those modes. If you change the preset mode in the GUI do you get an error? If something has changed on the heater firmware, you would get a 'Failed to update device state" error when you try to change preset value. And when the preset_value updates from the heater properties it would get no valid result, if the heater doesn't use C, ECO, and AF value for those modes. Again that's based on my basic understanding of what the codes does.
You could also try "self._api.set_version(3.1)" and see if that works better. Unsure what version of API firmware 1.0.2 uses.

Thanks. It felt more like it was an intermittent error, but maybe with that
additional information I'll be able to pin it down to specific situations.
I'll try out v3.1 and do some more testing!
On Tue, 24 Sep 2019, 11:02 Shane<EMAIL_ADDRESS>wrote:

Hi
REQUIREMENTS = ['pytuya==7.0.2'] is just a check that the python component
is available and installs it in the python environment if it is not already
installed. Since version 7.0.2 is already available the check passes. Since
version 7.0.4 is not officially available (see
https://pypi.org/project/pytuya/) it can't find it. But that doesn't
matter since you are importing the updated one, so leaving the requirements
set to 7.0.2 works. You could take that line out and it should still work.
Good idea to import it from the custom components folder. Best practice
using this method is to put the updated pytuya folder from Github into HA
as /custom_components/pytuya/init.py and that will work with "import
custom components.pytuya as pytuya" line.
KeyError: None means that when the set_temperature method attempts to run
line 239 [specifically _TEMPERATURE_LIMITS[preset_mode] function)] it can't
find a match for the preset_mode value in the _TEMPERATURE_LIMITS function.
Have you got Preset drop down in the GUI? (see pic below). That function is
checking the temperature limits where preset is set to either Comfort or
Eco. So it is saying that whatever is stored in preset_mode (the currently
set preset as long as it's not Anti-freeze) is not either Comfort or Eco
because it can't find a match in the dictionary in the _TEMPERATURE_LIMITS
function. I don't get that error using my custom component with older API.
But the error doesn't seem to relate to that - it seems to relate to preset
value being something other than Comfort, Eco, or Anti-freeze, or it's
getting no preset value from preset_mode attribute.
[image: image]
https://user-images.githubusercontent.com/47836318/65468441-37060180-deb8-11e9-8881-7879aa198ecb.png
I'm not great at python just learning as I try to understand the code and
adapt it, but that's my understanding of what the KeyError indicates.
Of course it could be that the updated firmware doesn't use C, ECO, and AF
any longer to indicate those modes. If you change the preset mode in the
GUI do you get an error? If something has changed on the heater firmware,
you would get a 'Failed to update device state" error when you try to
change preset value. And when the preset_value updates from the heater
properties it would get no valid result, if the heater doesn't use C, ECO,
and AF value for those modes. Again that's based on my basic understanding
of what the codes does.
You could also try "self._api.set_version(3.1)" and see if that works
better. Unsure what version of API firmware 1.0.2 uses.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nikrolls/homeassistant-goldair-climate/issues/20?email_source=notifications&email_token=AAOFVF4YS7Q2UVH2QP2DICDQLFDITA5CNFSM4IR6IT3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7MQWQQ#issuecomment-534317890,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOFVF6PMZCMFXY52T6XPMLQLFDITANCNFSM4IR6IT3A
.

So, I tried v3.1 and it is similar, intermittently unavailable heater.
All the functions work on the heater when I set them from the HA GUI.
Operation: Heat / off
Preset: Comfort / Eco / Antifreeze
Swing mode: 1,2,3,4,5,Auto
Target Temperature: X
When I change values on the heater directly it sometimes updates the GUI and it sometimes doesn't.  I think if I send a couple of commands in a row this is when it fails (usually).
When the current temperature  on the heater changes it usually updates the GUI.
I am not currently using the goldair app.
I use Unifi AC Lite AP.  Signal strength = 69% (-63dB).  Wife Experience = 78%.  It has a green leaf which means it is using wifi power save mode.
My theory is that the heater becomes unavailable because it can't handle multiple commands in quick session in a row.  This is triggered when you drag the temperature slider in the app as it sends multiple commands and spams the device.  If I send 1 or 2 commands it is ok.  It seems to fail if I send around 3-5 commands within 5 seconds or something like that.
Maybe the component needs a rate limiter / delay function??

I've also think I've been able to trigger the heater to become unavailable by changing the settings on the heater multiple times in a row.  I notice that HA doesn't always update with changes in the settings.  Then i did multiple changes on the heater and it became unavailable for 2 minutes.  After that I did one change on the heater and it became available and updated itself to the correct state.  I think it's possible to spam in the other direction as well with multiple changes on the heater, but I'm not 100% sure.

[quote]Since you have it as custom_components\pytuya_init_.py maybe it is still using version 7.0.2 since that is in the requirements in the init file (your errors relate to init.py file)? So for BOTH init.py and goldair_heater.py using REQUIREMENTS = ['pytuya==7.0.4'], putting the updated file in /custom_components/pytuya/init.py and then using import custom components.pytuya as pytuya and self._api.set_version(3.3) may make it work better. You could try this as a first step to see if this improves it.[/quote]
I can't get the component to load with requirements = 7.0.4 in both goldair/init.py and goldair/goldair.py when i use the custom init.py from either version of pytua (https://github.com/clach04/python-tuya or https://github.com/belzedaar/python-tuya/blob/master/pytuya/init.py)

I've got a bit further.
goldair/init.py ; requirements = 7.0.2
goldair/goldair.py ; requirements = 7.0.4
that works... will see if it's fixed.

sill having issues, intermittent unavailable, intermittent command not seen, all functions work intermittently.
So what I've tried is:
importing both versions of pytuya 7.0.4 (clach04 and belzedaar as a custom_component
I'm using requirements = 7.0.4 inside the goldair.py file and I'm using requirements = 7.0.2 inside the init.py
I've tried self._api.set_version(3.3) and self._api.set_version(3.1)
Everytime I've made changes I've deleted both of the pycache folders before restarting home assistant.

The heater does have a limitation; you should only send one call at a time because it takes a few seconds to action it. Also is is asynchronous and non-blocking. So making more than one change quickly is not a good idea while its still processing the last call, and HA needs to wait before requesting an update that the change has occurred because the old state will be retrieved until the heater has finishing processing the call. This wait for an update after you make a single change is already built into the code - the status info is based on what was changed (is faked) until an update can be requested from the heater. So as long as you wait a few seconds between making a change of single setting in HA that will keep the intermittent unavailability to a minimum. It is strange that I don't experience any intermittent issues, given that the update to the firmware and API should be aimed at improving the experience.
When writing automations you can add a delay between each service request.
In practice the heater will still have the same settings as last time when you turn it on, so generally all you need to do is turn it on and don't often need to change the other settings. When you do need to change a setting after turning it on, just wait a little between each change.
So go with whichever settings for version and api seems to be the most stable and don't make changes too close together.

The weird thing is that it goes unavailable when I'm not sending any commands.

Sorry to hear you get these problems. Sounds like you are just a bit unlucky and have a heater that's got minor operating issues.

perhaps you are right.  I'll try return/exchange it at mitre10 for a different one.
the different one will be on older firmware, which i won't be changing.
the only way to know would be to update the firmware on the exchanged heater, but I don't want to do that.

anyone got this working on v0.109.5, I can't even add the custom repo to HASS?
20-05-09 09:36:48 INFO (MainThread) [supervisor.store] Load add-ons from store: 66 all - 0 new - 0 remove
20-05-09 09:36:51 INFO (MainThread) [supervisor.store.git] Remove custom add-on repository https://github.com/nikrolls/homeassistant-goldair-climate.git
20-05-09 09:36:51 ERROR (MainThread) [supervisor.utils.json] Can't read json from /data/addons/git/d1047675/repository.json: [Errno 2] No such file or directory: '/data/addons/git/d1047675/repository.json'
20-05-09 09:36:51 WARNING (MainThread) [supervisor.store.data] Can't read repository information from /data/addons/git/d1047675/repository.json

This is an Integration, not an AddOn. It's confusing, but HomeAssistant has a number of ways to extend it:
AddOns: completely separate apps for HomeAssistant OS which can run alongside HomeAssistant Core.  HomeAssistant OS comes with an "AddOn Store" for these out of the box.
Integrations (custom components): Enable HomeAssistant Core to talk to various devices.  Out of the box there is no way to add new integrations from the UI. But you can install HACS and use that to manage Integrations and Plugins from the community, as well as Python scripts for the AppDaemon AddOn.
Plugins (custom cards): Extend the UI.
Currently the main repository here is being actively maintained, so the advice above to use other repositories and zipfiles is outdated.

Thanks @make-all.
There is one small issue with HACS and the latest beta, because HACS doesn't support symlinks. Future releases (including the one going up shortly) will remove symlinks until they're supported by HACS.

Cool I might jump in and retry this using hacs after you do that update.

This is an Integration, not an AddOn. It's confusing, but HomeAssistant has a number of ways to extend it:
AddOns: completely separate apps for HomeAssistant OS which can run alongside HomeAssistant Core. HomeAssistant OS comes with an "AddOn Store" for these out of the box.
Integrations (custom components): Enable HomeAssistant Core to talk to various devices. Out of the box there is no way to add new integrations from the UI. But you can install HACS and use that to manage Integrations and Plugins from the community, as well as Python scripts for the AppDaemon AddOn.
Plugins (custom cards): Extend the UI.
Currently the main repository here is being actively maintained, so the advice above to use other repositories and zipfiles is outdated.

Appreciate it, I've got HACS installed now!

I think this particular problem can be closed now.

Thanks @kiwijunglist! It all seems to be working from my end as well so I'll make the new release public.

also this issue:
https://user-images.githubusercontent.com/7436784/81162183-dcea2480-8fe0-11ea-95b6-d178e70486dc.png
has been solved for me too with latest HACS install from this afternoon.


How is the right way with row function and multi parameters ?

i try:
$db->row("SELECT * FROM customers WHERE email = ? AND actkey = ?",array($email,$actkey));
but it don't work. Error comes up :  Only one-dimensional arrays are allowed,
what did i wrong ?

- $db->row("SELECT * FROM customers WHERE email = ? AND actkey = ?",array($email,$actkey))
+ $db->row("SELECT * FROM customers WHERE email = ? AND actkey = ?", $email, $actkey))

https://github.com/paragonie/easydb/commit/abe995bb8a24961ca4dbd027f344321c4704f028
I've updated the README to make these details easier to find: https://github.com/paragonie/easydb/blob/master/README.md#fetch-a-single-row-from-a-table

Thank You!
There is a way to debug ? can i show the complete query from $db->row ?

I don't understand your question.
If you're asking what I suspect you're asking...
EasyDB doesn't build a query string. It sends the query string to the database, then sends the parameters in a separate packet. This process is called prepared statements, and is a provably secure way to prevent the query parameters (data) from mutating the query string (code).
There is no "debug" feature because we're not doing any string manipulation. The string you pass EasyDB is the string that gets passed to your database.

thank you very much!!! your're right, my fail. it works very good.
i have another question to the update function
$db->update('comments', [
    'approved' => true
], [
    'commentid' => $_POST['comment']
]);

i dont know what is which field?
if i do in mysql:
UPDATE Customers
SET ContactName = 'Max Muster', City= 'Berlin'
WHERE CustomerID = 1;

what is it in easyDB ?
$db->update('Customers', ['ContactName' => "1"], ['City' => 'Berlin']);
And where must i place "WHERE CustomerID=1" ?

The API is update($table, $fieldsToUpdate, $conditions).
So you'd want to do this:
$db->update(
    'Customers',
    ['ContactName' => "1", 'City' => 'Berlin']
    ['CustomerID' => 1]
);

https://github.com/paragonie/easydb/commit/0ac58c947070f2fd6ab4dc01a097c23a12581c20
The README explains this more clearly. Thanks for opening the issue.


Checks do not run

Hello!
Thanks for providing this GH action :)!
Unfortunately, it seems that no checks are running.
{:check_external_hash=>false, :checks=>[], :ignore_empty_alt=>false, :enforce_https=>true, :hydra=>{:max_concurrency=>50}, :parallel=>{:in_processes=>3}, :typhoeus=>{:connecttimeout=>30, :followlocation=>true, :headers=>{"User-Agent"=>"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"}, :ssl_verifypeer=>false, :ssl_verifyhost=>0, :timeout=>120}, :ignore_urls=>["https://fonts.gstatic.com/"], :url_swap=>{/^\/error-prone-support/=>""}}
Running 0 checks () in ["./_site"] on *.html files...

This is my definition
- name: Validating HTML output
  uses: athackst/htmlproofer-action@main
  with:
    check_external_hash: false

Thanks.

Thanks for the heads up!  Should work now

Thanks for the quick follow-up!


config.session.cookie.rolling not work when session is not modified during a request

Sails version: 0.12.14
Node version: v9.2.0
NPM version: 3.10.10 (npm3)
DB adapter name: sails-mysql for model storage and connect-redis for session storage
DB adapter version: 0.11.5 (sails-mysql) and 3.3.2 (connect-redis)
Operating system: CentOS 7 x86-64

What happened to my app?
Dear developers,
I was configuring the session of my app and found the auto rolling feature for sessions seems to not work, that is, the session.maxAge of the corresponding request will not be auto reseted if session is not modified.
I have read https://github.com/expressjs/session#cookie carefully but I still can not figure out what is wrong with my config/local.js and my app :( .
For some political reason I cannot access to http://bit.ly/sails-issue-repro so I am not sure whether my issue reproducing repo meets your requirements :( .
My configurations
Session storage adapter: connect-redis
Redis version: 4.0.6
config/local.js:
module.exports = {
  port: 80,
  session: {
    adapter: 'connect-redis',
    host: '<IP_ADDRESS>',
    ttl: 7 * 24 * 3600, // One week
    db: 0,
    prefix: 'sess:',
    cookie: {
      resave: false,
      maxAge: 7 * 24 * 3600 * 1000, // One week
      rolling: true,
      saveUninitialized: false
    },
    routesDisabled: ['GET /js/*', 'GET /css/*', 'GET /images/*']
  },
  models: {
    migrate: 'safe',
    connection: 'localDiskDb'
    // connection: 'mysql'
  }
}

Issue reproducing repository
sails-issue-repro-session-rolling
Issue reproducing steps

Run app.
Visit http://localhost/test/wr?str=rua and check the expiration date of the session cookie on a browser. This request will modify session and therefore the session is initialized and will be saved.
Wait for some time, say, 1 minute.
Visit http://localhost/test/rd and check the expiration date of the session cookie on a browser again. This request will not modify session.

You will find the expiration date of the session cookie will not be reset until you modify session by visiting http://localhost/test/wr?str=someDifferentString again.
Finally
The following configurations cannot help, too.
// config/local.js
module.exports = {
  port: 80,
  session: {
    adapter: 'connect-redis',
    host: '<IP_ADDRESS>',
    ttl: 7 * 24 * 3600, // One week
    db: 0,
    prefix: 'sess:',
    cookie: {
      resave: true, // Hey, there
      maxAge: 7 * 24 * 3600 * 1000, // One week
      rolling: true,
      saveUninitialized: false
    },
    routesDisabled: ['GET /js/*', 'GET /css/*', 'GET /images/*']
  },
  models: {
    migrate: 'safe',
    connection: 'localDiskDb'
    // connection: 'mysql'
  }
}

or
// config/local.js
module.exports = {
  port: 80,
  session: {
    adapter: 'connect-redis',
    host: '<IP_ADDRESS>',
    ttl: 7 * 24 * 3600, // One week
    db: 0,
    prefix: 'sess:',
    cookie: {
      resave: true, // Hey, there
      maxAge: 7 * 24 * 3600 * 1000, // One week
      rolling: true,
      saveUninitialized: true // Hey, there
    },
    routesDisabled: ['GET /js/*', 'GET /css/*', 'GET /images/*']
  },
  models: {
    migrate: 'safe',
    connection: 'localDiskDb'
    // connection: 'mysql'
  }
}

That's all. I suspect this is a bug, probably. I hope some would help me with this issue very soon XD.

Ok, fixed!

Ok, fixed!

HI @Luluno01, thanks for the detailed post and the repo.  We're trying to wrap up the 1.0 release so it may take a little bit to check this out.  In the meantime, seems like a workaround would be a policy or custom hook that runs before every route and sets a key in the session to a random value, since it sounds like you're saying that as long as the session is modified, the expiration will be reset?

@sgress454 Thanks for your reply! The solution you provide sounds like a "quick patch" that could not tackle the root problem but would work with me.
Yes, I will try this out to fix my app temporarily. Please let me know if you great developers have any further information about this issue in the future!
Looking forward to your 1.0 release version :) . I hope this issue would not be found in the brand new version XD.

@sgress454 Alright, here is my custom session fixing middleware:
sessionFix: (req, res, next) => {
  if(req.session) {
    let keys = Object.keys(req.session); // ['cookie', '_sessionFix', ...]
    let fixKeyIndex = keys.indexOf('_sessionFix');
    if(fixKeyIndex != -1) { // Key found
      keys.splice(fixKeyIndex, 1);
    }
    if(keys.length > 1) { // Initialized session
      req.session._sessionFix = Math.random(); // Force the `maxAge` property to be reseted
    }
  }
  next();
},

I have tested this, works fine for now :) .

Still waiting for a patch XD.

@sailsbot seems like there seems to be something to be done here yet

Still waiting ( ͡° ͜ʖ ͡°)✧

@Luluno01 thanks for your patience!
So to be honest, I doubt I'm going to be able to justify the development hours to patch this on the v0.12 version of Sails unless we have that need come up on a project.
That said, if you notice that this is an issue on v1.0 of Sails, I'll look into it personally.

@mikermcneil Thank you for your reply! Actually I can't wait to try out the latest version of Sails but I am afraid of not being able to have enough time to check this out on v1.0 of Sails recently. So should I close this issue and open a new issue if I find the same issue on v1.0 of Sails, or just leave this issue open?
Thanks for your help once again!

@Luluno01, I believe you have a problem in the configuration. The property rolling, as well as resave and saveUninitialized, should all be in sails.config.session and not in sails.config.session.cookie.
At least that's how it works in Sails v1. Took me a time debugging express-session package to realize I had made the same mistake.


Add 'cosmwasm' feature to juno

The old frontier frontend is on v0.9.12-rc.3 of @keplr-wallet, and it only requires wasmd_0.24+ as seen here to query contract balances with correct URL.
However we're running ^0.10.4 of @keplr-wallet, and it requires cosmwasm feature as well to query with the correct URL, seen here. Is it a problem elsewhere to enable cosmwasm feature? It seems Keplr should be using || logic there.

Merging for now, will undo if @Thunnini raises concerns with enabling cosmwasm feature for Juno


Will you make a version for shipping games?

Header! I'm curious, I always wanted to develop my own launcher! (Not to be forced, But to play games that won't be released in steam.)

I don't plan on doing it because it's much more work than what I did for this launcher. It would need to support the other launcher, automatically import games, etc.. There are launchers out there like Playnite that should do the trick. You can definitely use this as a starting point if you want though!


Update DesignSystemDetector.kt

Added handling to ignore lint checking inside design system package

Why do we want to ignore lint checks for designsystem?

Closing due to inactivity. If you still want to submit this change create a new PR


[RFC] make the public API stricter

Description
Since this library is still in development and breaking changes are not too disruptive, I think it's worth making the public API stricter right now.
Through some mix of the following:

requiring keyword-only arguments wherever possible
using __all__ entries in modules to limit what is exported (affects * imports and things like sphinx autodoc)
prefixing private functions, classes, methods, constants, etc. with _

Benefits of this work
Clarifies the boundary between the private and public API for users of the library.
Expands the set of implementation details that could be changed in the future without worrying about breaking users.
Reduces the risk of naming conflicts wherever * imports are used.
Acceptance Criteria

every non-testing module in the Python package has an __all__ list containing only its public attributes
keyword-only arguments are required wherever possible
every object that is not intended to be public is prefixed with a _

Approach
See these related issues for reference:

https://github.com/rapidsai/dependency-file-generator/issues/76
https://github.com/dmlc/xgboost/issues/6172
https://github.com/microsoft/LightGBM/pull/5655

Make changes in this project to implement these things.
Notes
N/A

I missed this somehow, but this definitely a great idea.


[Menu][Joy] Fix closing of Menu in demos

closes https://github.com/mui/material-ui/issues/36821

[ ] I have followed (at least) the PR section of the contributing guide.

@sai6855 Thanks for looking into this but I think it is not fixed because onMouseDown the popup is closed and then click event fires which will open the popup again.
https://user-images.githubusercontent.com/18292247/234159055-54c52d70-e164-4470-8300-a5a6a16b2841.mov

@siriwatknp updated logic, can you verify now.
Right now
Menu will be closed when you perform below actions
          **A**

click on Button which opens Menu
Again clicking Button closes Menu

(Or)
         **B**

Click on Button which opens Menu
Click on area outside of Menu and Button

(Or)
          **C**

onMouseDown on Button which opens Menu and relese the mouse (Here mouse should be opened)
perform same action as 1, now Menu will be closed

Right now on master  only B case is working as expected

Please add a brief description of breaking changes along with instructions how to update existing codebases to the first comment of this PR.

As suggested added Keyboard and FocusEvent types to event here but there is a catch here,Keyboard event type doesn't have relatedTarget property, so had to cast event type here to make typescript happy when accessing event.relatedTarget in demos.
Alternatively instead of casting event type, we can add a check demos like below.

const handleClose = (
    event:
      | React.MouseEvent<Element, Event>
      | React.FocusEvent
      | null
      | React.KeyboardEvent<Event>,
  ) => {
    if (event && 'relatedTarget' in event && event.relatedTarget !== anchorEl) {
      setAnchorEl(null);
    }
  };

I'd appreciate your view here. cc @michaldudak @siriwatknp

@sai6855 I have another idea (non-breaking change) for the fix. If my understanding is correct, the problem is

when the menu is open
mouse down on the button triggers blur event which change the open to false in menuReducer
mouse up triggers click event which set the state from to true again.

I wonder if it makes sense to not change open to false if the relatedTarget has aria-controls the same id as the listbox.
diff --git a/packages/mui-base/src/useMenu/menuReducer.ts b/packages/mui-base/src/useMenu/menuReducer.ts
index 9a0ac7b240..ac383e102d 100644
--- a/packages/mui-base/src/useMenu/menuReducer.ts
+++ b/packages/mui-base/src/useMenu/menuReducer.ts
@@ -35,6 +35,11 @@ export default function menuReducer(

   if (action.type === ListActionTypes.blur) {
     if (!action.context.listboxRef.current?.contains(action.event.relatedTarget)) {
+      const listboxId = action.context.listboxRef.current?.getAttribute('id');
+      const controlledBy = action.event.relatedTarget?.getAttribute('aria-controls');
+      if (listboxId && controlledBy && listboxId === controlledBy) {
+        return newState;
+      }
       return {
         ...newState,
         open: false,

This seems to work on my side.

Looks fine to me! I'd only add a comment to explain what is this for as it's not obvious at first glance.
Also, it doesn't work on Joy demos when I apply this change on the latest master as id is not set there.

@siriwatknp added description here https://deploy-preview-36917--material-ui.netlify.app/joy-ui/react-menu/#introduction


Milestone 4 - Frontend Templates & zkSync CLI

Created other issues to track MS4 and split up the tasks.


tinybox benchmark with HSA

This blocked on anything?

#3608 resource error if torch also uses the device. I will test this again and merge it first with the caveat that torch only uses cpu in benchmark

Hmm, I don't really like losing that functionality, think we should block until we fix. Curious why it breaks, I wouldn't expect it to.

yea i don't like that either so did not merge. It looks like if tinygrad inits HSA, torch cuda_init would fail, and if torch already inited, tinygrad HSA init would fail. @nimlgen could it be related to how the device was inited?

Uh, that's seems to be the way that we have 2 libhsa-runtime64.so libraries, one from PyTorch, one ours. Like kernel does not allow to init runtime twice for the same task_struct, but since state of this libhsa-runtime64.so is different they try to do this.
Like the same way this:
from tinygrad import Tensor
a = Tensor([1])
print(a.numpy())

import torch
print(f"{torch.__version__=}")
a = Tensor([1])
b = torch.tensor([1]).to("cuda")
print(a.numpy(), b)

does not work for HIP, according to gdb we got 2 different libhsa-runtime64.so (I believe we call one, torch calls other).

Oh can add LD_PRELOAD="/opt/rocm/lib/libhsa-runtime64.so" to ci, bad?

eh that makes sense, and thanks for the suggestions. Benchmark looks good now and time is similar to latest HIP one (I reran both).


Don't create account if AwsAccountID exists

This PR will add logic to kip creating an aws account if .Spec.AwsAccountID already exists. This is to support reusing failed accounts.

/lgtm


[Bug] SQLSTATE[HY000] [2002]  (trying to connect via (null))

Describe the bug
init billing in docker compose:
version: "3.9"
services:
  fossbilling:
    container_name: fossbilling_server
    image: fossbilling/fossbilling
    restart: always
    ports:
      - 8088:80
    volumes:
      - fossbilling:/var/www/html
    networks:
      - net
      - webproxy
    depends_on:
      - mysql

  mysql:
    container_name: fossbilling_db
    image: mysql:8.0.34-debian
    restart: always
    environment:
      - MYSQL_DATABASE
      - MYSQL_USER
      - MYSQL_PASSWORD
      - MYSQL_RANDOM_ROOT_PASSWORD
    volumes:
      - mysql:/var/lib/mysql
    networks:
      - net

volumes:
  fossbilling:
  mysql:

networks:
  net:
  webproxy:
    external: true

How to reproduce
first step - all ok, info page is all green,
second step - i enter all db creds and no error,
third step - i see warning "FOSSBilling installer will create database. It may take some time. Do not close this window. Continue?",
click Ok and wait, but 3-4 seconds i see error "SQLSTATE[HY000] [2002]  (trying to connect via (null))".
second click on Next generated error: "SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'activity_admin_history' already exists"
if del dir "install" and go to https://ip - i see too "SQLSTATE[HY000] [2002]  (trying to connect via (null))"
Expected behavior
installed
Screenshots
No response
FOSSBilling version
0.5.6
Module version
No response
Device
No response
Information
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
Docker version 24.0.6, build ed223bc
Additional context
No response

Hi @vasyakrg
Have you tried freshly setting up the docker instance and trying it again?

Hi @BelleNottelling
I tried just today, fresh reinstall of a VPS with Ubuntu 22.04 and docker.
Below is the compose file I used (referred from documentation)
version: "3.9"
services:
  fossbilling:
    image: fossbilling/fossbilling
    restart: always
    ports:
      - 49343:80
    volumes:
      - fossbilling:/var/www/html
  mysql:
    image: mysql:8.0
    restart: always
    environment:
      MYSQL_DATABASE: fossbilling
      MYSQL_USER: fossbillinguser
      MYSQL_PASSWORD: fossbillingpassword
      MYSQL_RANDOM_ROOT_PASSWORD: '123456'
    volumes:
      - mysql:/var/lib/mysql

volumes:
  fossbilling:
  mysql:

On opening, it first asked to delete the /install directory, which I did on the docker volume.
After that, presented with this screen

Very similar to OP's bug, so did not open a new issue.

What hostname did you use?

I was using IP:port to access it at first. But on removing the /install I started receiving SSL errors. So I used Cloudflare tunnel, pointing to localhost:49343 - which was showing the above screen.

For the database it should be   'mysql' instead of localhost

@su-haris do you mean that you didn't run through the installer and that on a fresh installation it told you to delete the /install folder?

@jaapmarcus Oh, I thought the FOSSBilling container would automatically be connecting to the SQL container. I might have missed something, but I could not find anything for a manual connect.
@BelleNottelling that is correct. Once the containers had spun up, the first page which I saw was asking to delete the /install file.

@BelleNottelling that is correct. Once the containers had spun up, the first page which I saw was asking to delete the /install file.

0.5.6 was briefly published with a dummy config file by accident, it sounds like that mistake made it into the docker image and it wasn't corrected. I've pushed to the docker image to make it re-build without the mistake.
Please try deleting the container you have and then freshly pulling in the current version of the latest tag. That should resolve the issue you are seeing, although it seems unrelated to the OP's issue as they actually did go through the installer.

@BelleNottelling thank you for the quick resolution. the new image works perfectly!

the new image works perfectly!

For the database it should be 'mysql' instead of localhost

Trying to install with MySQL instead of localhost I get:
SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for mysql. failed: Name or service not known


[BUG] Case Blowing Only ---> invalid payload

Hello team
There is an issue with the remote climate set mode blowingOnly. I had issue with it and decided to dig into the code
and
in the mqtt_gateway.py file
there is a switch case condition for all modes
and the switch is based on  msg.payload.decode().strip().lower()
which will always be lowercase
and the case
case 'blowingOnly':                             LOG.info('A/C will be set to blowing only')                             self.saic_api.start_ac_blowing(self.vin_info)
Can never happen in fact
;)

I can confirm the problem:


Increase the stable node version in installation script

In the dev branch the current instalaltion script is using the 6.x as the stable Debian node branch. This is very out dated and should be changed to 9.x.
Here is the line.
	NODE_STABLE_BRANCH="6.x"

That is:
curl -sL https://deb.nodesource.com/setup_9.x | sudo -E bash -

Could you please send a PR?

Ah, just noticed you did :)


fix #4948 part of #3397

Fix for #4948 that is part of #3397
A platformcontroller command is added as subcommand of kamel; it runs an operator like the operator subcomand does, but platformcontroller would just handle IntegrationPlatform CRs. All the other CRDs are handled by operator as before.
These installation methods have been amended accordingly:

install command
olm bundle
helm charts

e2e  tests has been ran locally as well.

Release Note
NONE

What about these tests:
❌ TestMetrics (3m0.27s)
❌ TestMetrics/reconciliation_duration_metric (10ms)
they seems flaky to me, first run they were passing, they are passing locally, but now failing in CI :/

What about these tests:
❌ TestMetrics (3m0.27s) ❌ TestMetrics/reconciliation_duration_metric (10ms)
they seems flaky to me, first run they were passing, they are passing locally, but now failing in CI :/
They are also marked as "problematic" but CI runs without the skip problematic config? :/

No, I don't think they are flaky. It fails at line:
Expect(platformReconciled).NotTo(BeNil())

I suspect that the operator perform and provide metrics which we may have lost if running the reconciliation loop outside the main process.

@valdar @rinaldodev mind rebasing ?

The main concern I have is about code duplication (maintainability) and performance loss. About the first, I think it would be a matter of abstracting the code from the operator and be able to call it from different places.

I have abstracted as much code as I could in the cmd/controller/manager.go interface and implementations. Hope it is a suitable solution.

About performances I guess it's a bit more complicated. IIUC, so far we're having two separate Pods with 2 separate caches. I honestly don't think that the platform controller has to watch at any resource at all, but only owns the IntegrationPlatform resource. If it requires to watch all those resources for any reason, then, we should understand if we can share the cache somehow.

All not needed resources have been removed from watching in cache.

Additionally, I wonder if instead of having a new deployment, we can simply have a sidecar container to take care of controlling this part.

@rinaldodev is already working on follow ups of this PR that requires the platform controller to be a separate operator, in fact the one that will bootstrap the camel k operators. So I think that is not worth to explore a sidecar option for the relative short time needed to complete that chunk of work.

@valdar I don't have enough context to review this one, sorry. The immediate impression I have is that from community perspective it would be good to have some design diagram and some user documentation to illustrate how this new model works, above all what it implies in terms of resources, monitoring and in general any operational aspect that it would be required as we move to a new approach with multiple Deployments. Also some explanation on the "why" this work is beneficial may be helpful to be eventually welcomed by any user that may not agree with this new approach and such a change that is going to happen on a minor release version.

I've enabled Quarkus Native tests. However it's very likely they fail due to some infrastructure problem that we have not yet tackled. In such circumstances, please, run the Quarkus Native test manually in your local environment and report result here.

@christophd @squakez I guess this is now in a good shape to be merged

@christophd @squakez I guess this is now in a good shape to be merged

I haven't received any feedback about my last 2 comments. We need to run manually the native checks and it would be nice some documentation or explanation that the final user will require for sure when moving to a new deployment model. Thanks.

Also, several tests have failed and they don't seem to be the usual flaky ones. I've restarted them.

Also, several tests have failed and they don't seem to be the usual flaky ones. I've restarted them.

The native tests seems to be failing constantly on OSX, can't we skip testing native images on OSX ? given not everyone has an OXS I wonder how actually one could run them locally

Also, several tests have failed and they don't seem to be the usual flaky ones. I've restarted them.

The native tests seems to be failing constantly on OSX, can't we skip testing native images on OSX ? given not everyone has an OXS I wonder how actually one could run them locally

They can run on any OS. The Macos is only on github actions. We are executing in our local machines while we don't have a fix on the GH infra.

Also, several tests have failed and they don't seem to be the usual flaky ones. I've restarted them.

The native tests seems to be failing constantly on OSX, can't we skip testing native images on OSX ? given not everyone has an OXS I wonder how actually one could run them locally

They can run on any OS. The Macos is only on github actions. We are executing in our local machines while we don't have a fix on the GH infra.

Can we maybe disable native OSX tests on CI till we have a fix ?

@lburgazzoli the problem is not the failure of the checks per se. As we've done in other PR, everything that may affect the Quarkus native has to be validated manually in order to make sure we don't introduce any regression. Please, have a look at this PR for instance: https://github.com/apache/camel-k/pull/5234#issuecomment-1985493127
If the folks have any problem running the native tests, you or I can run them and publish here the results, although, as suggested to some other contributor, it would be good to be able to do it on their own as it's should be a normal practice to do when doing some development. Running locally it is as easy as running any other integration test [1], it is only taking a bit of time more.
Beside, that normal test have failed and I've restarted, so, we need common to finish and be green.
Beside, as mentioned in [2] my personal feeling is that these kind of changes would require some documentation and some rationale explanation as the users that will move from 2.2 to 2.3 will have the surprise of a multi deployment that may require them to adjust monitoring and other operational aspects. To me this is a breaking change, but if you want to proceed, at least it has to be clearly explained to the final users.
[1] https://camel.apache.org/camel-k/2.2.x/contributing/e2e.html#testing-e2e-structure
[2] https://github.com/apache/camel-k/pull/5119#issuecomment-1976919321

@lburgazzoli the problem is not the failure of the checks per se. As we've done in other PR, everything that may affect the Quarkus native has to be validated manually in order to make sure we don't introduce any regression. Please, have a look at this PR for instance: #5234 (comment)
If the folks have any problem running the native tests, you or I can run them and publish here the results, although, as suggested to some other contributor, it would be good to be able to do it on their own as it's should be a normal practice to do when doing some development. Running locally it is as easy as running any other integration test [1], it is only taking a bit of time more.

I'm not complaining about having to run them locally, I'm just noticing the OSX build is almost always failing so I wonder what is the value of such test. Now I can run the test locally on my linux box and reporting them as ok but, what I've testes is not what has failed so people may spend time waiting and trying to find out why things are not working on OSX whereas it is an environment issue.

Beside, as mentioned in [2] my personal feeling is that these kind of changes would require some documentation and some rationale explanation as the users that will move from 2.2 to 2.3 will have the surprise of a multi deployment that may require them to adjust monitoring and other operational aspects. To me this is a breaking change, but if you want to proceed, at least it has to be clearly explained to the final users.

I agree that we need some docs but since this PR is part of a larger issue and the rationale was briefly explained in https://github.com/apache/camel-k/issues/3397#issuecomment-1735525398, then I wonder if the doc could be something we do as a separate PR.

I agree that we need some docs but since this PR is part of a larger issue and the rationale was briefly explained in #3397 (comment), then I wonder if the doc could be something we do as a separate PR.

In theory we want to release 2.3 by the end of the month. If we ends up merging this we'd include in 2.3 which, IIUC would not be either complete as still missing pieces (beside documentation). My suggestion would be to wait the release of 2.3 then, and to merge right after so you can focus on the rest of development to be ready for 2.4. Or, if you want to push this in 2.3 complete with the required documentation.

I think this is more for 3.x than 2.x, wonder if we should branch 2.x now and move main toward 3.x

I agree that we need some docs but since this PR is part of a larger issue and the rationale was briefly explained in #3397 (comment), then I wonder if the doc could be something we do as a separate PR.

In theory we want to release 2.3 by the end of the month. If we ends up merging this we'd include in 2.3 which, IIUC would not be either complete as still missing pieces (beside documentation). My suggestion would be to wait the release of 2.3 then, and to merge right after so you can focus on the rest of development to be ready for 2.4. Or, if you want to push this in 2.3 complete with the required documentation.

I think this is more for 3.x than 2.x, wonder if we should branch 2.x now and move main toward 3.x

No problem for me. Mind that there may be some work to perform on the actions as well (nightly upgrades, releases, etc...) and likely this has to be communicated and accepted by the community before.

@valdar please rebase against main again. The Quarkus native checks have been fixed, so you won't need to run them manually any longer. Thanks.

This work has been moved to a branch under camel-k project: https://github.com/apache/camel-k/tree/issue/3397 and another PR has been opened https://github.com/apache/camel-k/pull/5701


https system proxy is not used on mojave

Expected Behavior
chronos uses the proxy server configured in system preferences
Actual Behavior
chronos tries to directly connect to specified jira server
verified with wireshark
Steps to Reproduce the Problem

Try to login

Specifications

Chronos-timetracker version: 2.8.6
OS: OSX Mojave

@mteske Hi!
Could you try please 3.0.0-beta, it should be fixed

yes, thanks, this works fine for me now.


Add result callback invocation for subcommands

As mentioned in https://github.com/pallets/click/issues/1178 this behavior is actually desired. I believe that the changes to the comments seem to do the job but I am not 100%. Apart from that the simple code fix I made I'm not too sure if more changes are needed else where where result callbacks are referenced.
Added a simple test to show the functionality with my addition.

Rebased commits and added changelog entry

Changed so regular groups invoke the result callback with None, while chained groups invoke it with []. Parametrized the test to test both cases.


Picovoice Documentation Issue (/docs/quick-start/console-signup/)

What is the URL of the doc?
https://console.picovoice.ai/
What's the nature of the issue? (e.g. steps do not work, typos/grammar/spelling, etc., out of date)
Hi, am trying to signup using Enterprise Console, but am not receiving confirmation code mail. I did checked in junked mail folder but didn't receive. Please check.
Thanks

most probably you entered the wrong email address (a typo). I suggest trying again and seeing if the issue persists. if yes,  send an email to<EMAIL_ADDRESS>with the email address you used and we look into it.


[!] No `Podfile' found in the project directory.

To run the example project, clone the repo, and run pod install from the Example directory first.
And we have:
/FDTake/iOS Example/ (master) pod install [!] NoPodfile' found in the project directory.`

I believe the pod install step is no longer necessary.
Are you able to clone the repo and open the workspace directly?

I believe this solves the problem. Please reopen if this is still an issue.


plus symbol in query string fails orderby desc

The following fails:
http://localhost/api/Services/Widgets?$orderby=Created+desc
Whereas the following succeeds:
http://localhost/api/Services/Widgets?$orderby=Created desc
Only difference is a space between the Created and desc.

+1 running into the same issue myself.


Tiktoken dependency : ModuleNotFoundError: No module named 'regex._regex'

When I try to emport Tiktoken, import fails. The problem is coming from regex library. I saw that many libraries that rely on regex have similar issues, but I didn't find a solution for this. I tried to force reinstall regex, but it didn't work.
I am using python 3.8 and I installed tiktoken through pip
File "C:/Users/TOSHIBA/AppData/Roaming/JetBrains/PyCharmCE2020.2/scratches/Programmation architecturale/Constitution du Programme/web-qa.py", line 171, in
import tiktoken
File "C:\ProgramData\Anaconda3\envs\EnvPy38\lib\site-packages\tiktoken_init_.py", line 1, in
from .core import Encoding as Encoding
File "C:\ProgramData\Anaconda3\envs\EnvPy38\lib\site-packages\tiktoken\core.py", line 7, in
import regex
File "C:\Users\TOSHIBA\AppData\Roaming\Python\Python36\site-packages\regex_init_.py", line 1, in
from .regex import *
File "C:\Users\TOSHIBA\AppData\Roaming\Python\Python36\site-packages\regex\regex.py", line 437, in
import regex._regex_core as _regex_core
File "C:\Users\TOSHIBA\AppData\Roaming\Python\Python36\site-packages\regex_regex_core.py", line 21, in
import regex._regex as _regex
ModuleNotFoundError: No module named 'regex._regex'

This isn't an issue with tiktoken and I can't reproduce. Note that it's suspicious that both EnvPy38 and Python36 is on your python path.

Solved.
I found that there was a folder named regex and that contained a _regex.py file in App/Roaming/... . I deleted it, and it worked.


FieldComparison.field_label should pick up labels from InlinePanel

For ParentalKey relations (which don't have a verbose_name property), FieldComparison creates a verbose_name from the field name:
https://github.com/wagtail/wagtail/blob/7ad79c9a4a7ec89a7d353db442268f24d08064c6/wagtail/admin/compare.py#L26-L28
This isn't ideal, particularly when related_query_name has been set on the relation - see https://github.com/wagtail/wagtail/pull/4579#issuecomment-412932533. It would be better to have InlinePanel pass its own label (if one is supplied) to FieldComparison as part of InlinePanel.get_comparison.

Is this still open? Can I work on it?

Go for it @sandilsranasinghe - please be sure to include unit tests with any PR and reach out if you need a hand.

Just a couple of questions, is it okay to add a new default argument to ChildRelationComparison init method? Also should I add new unit tests to test_compare or test_edit_handlers if changing the InlinePanel.get_comparison method?

@sandilsranasinghe
The default Arg should be ok - if it can be done in a way that won't break existing usage without it.
Good call on adding those extra unit tests.
Thanks


Proper solution does not register as complete when tested

Challenge Make Unique Objects by Passing Parameters to our Constructor has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
var Car = function(wheels, seats, engines) {
  //Change this constructor
  this.wheels = 4;
  this.seats = 1;
  this.engines = 1;
};

//Try it out here
var myCar = new Car(3, 1, 2);

This is not the correct solution. Please visit the Help Chat for challenge help.

this.wheels = wheels;
this.seats = seats;
this.engines = engines;


[fix] Prevent agent access to logs directory

This PR addresses the vulnerability related to agent access to the logs folder. The proposed fix is straightforward and appears to be secure. However, this solution doesn't cover the agent log folder specifically.
I've conducted some testing (e.g. doing task runs;  and ls -la /app/logs in the executing command section) with the current implementation and haven't encountered any issues.

@Joey-Ji I opted to remove the mounting and used docker cp. Lmk if approach seems reasonable to you.
The files chat_chain.dump and agent.log are artifacts but I updated the directory in which they're saved so we don't leak via the -v "$(pwd)/agent":/app/agent \ mount.

@Joey-Ji I opted to remove volume mounting in favor of docker cp. This way we limit host filesystem exposure and remove the need for a temporary directory. I also added docker rm for cleanup as we removed the --rm flag (see 8623408)
Additionally, chat_chain.dump and agent.log have been relocated from agent/logs → logs to prevent information leakage via the /app/agent mount. (see cd15da6)
Please review and lmk if this approach is reasonable.

I'm getting this error docker cp "${container_name}:/app/logs/." "$(pwd)/logs/" when i'm doing test runs. Can you fix it or am i missing sth.?

@Joey-Ji I opted to remove volume mounting in favor of docker cp. This way we limit host filesystem exposure and remove the need for a temporary directory. I also added docker rm for cleanup as we removed the --rm flag (see 8623408)
Additionally, chat_chain.dump and agent.log have been relocated from agent/logs → logs to prevent information leakage via the /app/agent mount. (see cd15da6)
Please review and lmk if this approach is reasonable.

This approach looks great to me! I did some testing and didn't notice any issues. Thanks!


ModuleNotFoundError: No module named 'triton.language'

Hi,
I got the following issue when testing this library
Installing collected packages: triton
Successfully installed triton-0.4.2
shi@genesis-shi:~$ python3
Python 3.8.10 (default, Jun  2 2021, 10:49:15)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import triton.language as tl
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'triton.language'
>>>

Does anyone know how can I solve it?
Thanks

Oh that's strange. I wonder why your system installed triton-0.4.2. Can you try pip install triton==1.0.0 and tell me what you see?

Hi @ptillet
It seems that it doesn't work with ``:
shi@genesis-shi:~$ pip install triton==1.0.0
Looking in indexes: http://mirrors.aliyun.com/pypi/simple
ERROR: Could not find a version that satisfies the requirement triton==1.0.0 (from versions: 0.1, 0.1.1, 0.1.2, 0.1.3, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.3.0, 0.4.1, 0.4.2, 1.0.0.dev20210502, 1.0.0.dev20210506, 1.0.0.dev20210508, 1.0.0.dev20210509, 1.0.0.dev20210510, 1.0.0.dev20210515, 1.0.0.dev20210516, 1.0.0.dev20210520, 1.0.0.dev20210521, 1.0.0.dev20210525, 1.0.0.dev20210601, 1.0.0.dev20210611, 1.0.0.dev20210614, 1.0.0.dev20210621, 1.0.0.dev20210622, 1.0.0.dev20210625, 1.0.0.dev20210720, 1.0.0.dev20210722, 1.0.0.dev20210723)
ERROR: No matching distribution found for triton==1.0.0

I just moved to China recently, here's a different gateway than the US, maybe it's because the VPN cannot determine which server to connect to?
However, the nightly release has no problem:
shi@genesis-shi:~$ pip install triton==1.0.0
Looking in indexes: http://mirrors.aliyun.com/pypi/simple
ERROR: Could not find a version that satisfies the requirement triton==1.0.0 (from versions: 0.1, 0.1.1, 0.1.2, 0.1.3, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.3.0, 0.4.1, 0.4.2, 1.0.0.dev20210502, 1.0.0.dev20210506, 1.0.0.dev20210508, 1.0.0.dev20210509, 1.0.0.dev20210510, 1.0.0.dev20210515, 1.0.0.dev20210516, 1.0.0.dev20210520, 1.0.0.dev20210521, 1.0.0.dev20210525, 1.0.0.dev20210601, 1.0.0.dev20210611, 1.0.0.dev20210614, 1.0.0.dev20210621, 1.0.0.dev20210622, 1.0.0.dev20210625, 1.0.0.dev20210720, 1.0.0.dev20210722, 1.0.0.dev20210723)
ERROR: No matching distribution found for triton==1.0.0

Anyway, maybe I should stick with the nightly release for a while.
Thanks

Congratulations on this great work! it seems that in most of cases, triton runs faster
vector-add-performance:
size      Triton       Torch
0        4096.0   15.999999   15.999999
1        8192.0   24.000000   31.346940
2       16384.0   48.000000   48.000000
3       32768.0   92.390982   96.000000
4       65536.0  127.999995  148.048195
5      131072.0  192.000000  192.000000
6      262144.0  241.533161  236.307695
7      524288.0  279.272725  279.272725
8     1048576.0  307.200008  307.200008
9     2097152.0  320.338891  321.912406
10    4194304.0  329.188778  327.679984
11    8388608.0  332.108094  332.108094
12   16777216.0  334.367350  334.367350
13   33554432.0  335.454864  335.598015
14   67108864.0  335.938503  336.082067
15  134217728.0  336.082067  336.369531

Hi @ptillet It seems that it doesn't work with pip install triton==1.0.0:
shi@genesis-shi:~$ pip install triton==1.0.0
Looking in indexes: http://mirrors.aliyun.com/pypi/simple
ERROR: Could not find a version that satisfies the requirement triton==1.0.0 (from versions: 0.1, 0.1.1, 0.1.2, 0.1.3, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.3.0, 0.4.1, 0.4.2, 1.0.0.dev20210502, 1.0.0.dev20210506, 1.0.0.dev20210508, 1.0.0.dev20210509, 1.0.0.dev20210510, 1.0.0.dev20210515, 1.0.0.dev20210516, 1.0.0.dev20210520, 1.0.0.dev20210521, 1.0.0.dev20210525, 1.0.0.dev20210601, 1.0.0.dev20210611, 1.0.0.dev20210614, 1.0.0.dev20210621, 1.0.0.dev20210622, 1.0.0.dev20210625, 1.0.0.dev20210720, 1.0.0.dev20210722, 1.0.0.dev20210723)
ERROR: No matching distribution found for triton==1.0.0

I just moved to China recently, here's a different gateway than the US, maybe it's because the VPN cannot determine which server to connect to? However, the nightly release has no problem (the same server):
shi@genesis-shi:~$ pip install -U --pre triton
Looking in indexes: http://mirrors.aliyun.com/pypi/simple
Collecting triton
  Downloading http://mirrors.aliyun.com/pypi/packages/40/6c/43b8660e0b0323b3b91aa6e182ffdc28e11b180c4869aff756f2e3b12c44/triton-1.0.0.dev20210723-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (15.2 MB)
     |████████████████████████████████| 15.2 MB 17 kB/s
Requirement already satisfied, skipping upgrade: torch in ./.local/lib/python3.8/site-packages (from triton) (1.9.0+cu111)
Requirement already satisfied, skipping upgrade: numpy in ./.local/lib/python3.8/site-packages (from triton) (1.21.0)
Requirement already satisfied, skipping upgrade: typing-extensions in ./.local/lib/python3.8/site-packages (from torch->triton) (<IP_ADDRESS>)
Installing collected packages: triton
  Attempting uninstall: triton
    Found existing installation: triton 0.4.2
    Uninstalling triton-0.4.2:
      Successfully uninstalled triton-0.4.2
Successfully installed triton-1.0.0.dev20210723

Anyway, maybe I should stick with the nightly release for a while. Thanks

Hi, I am tring to install triton by "pip install -U --pre triton" . But report
ERROR: Could not find a version that satisfies the requirement triton (from versions: none) ERROR: No matching distribution found for triton
Is there any other setting ?


GetHostname() function

...
urlTest := "https://example.com/something/"
hostname, err := urlutil.GetHostname(urlTest)
if err != nil {
	panic(err)
}
fmt.Println(hostname)
...

Output:
example.com

The function was created for internal integration into this task https://github.com/projectdiscovery/uncover/issues/122
in particular for the new field to integrate "url"

Supported field

host (existing)
url (new)

putting it inside utils can also be useful for future use

This seems very specific to uncover only. Did you find other projects where the same code snippet is reused?


WIP - Begin refactoring redux docs

Hey Tim! As @markerikson mentioned in https://github.com/reduxjs/redux/issues/2590 we chatted a bunch at ReactRally and I told him I'd give refactoring the docs a try. This PR is gonna be very in flux for a while, I just figured a PR was the easiest way for you to keep track of what I'm doing.
Feel free to reach out here or message me on twitter @MatthewGerstman to talk more.

Since this has gotten pretty out of date with master, I'm going to close it out for now. If you want to give updating things a shot, I can reopen it for you.


[secrets] The secret key needs to be shared between all instances

Since our current secret key is generated randomly over here https://github.com/pyronear/pyro-api/blob/master/src/app/config.py#L27, if we were to scale our architecture we would get a problem. All scaled instances of the API need to share the same secret key.
cc @Thibault-Daccord

Closing since the JWT_SECRET env variable is able to achieve just that


[modify] mail_page : start_line and terminate_line settings

coverage: 82.852%. first build when pulling eec32b97a23596498b617ce1c002137342a2ea6e on fix-mail-page into f76bb680c5062ece8d0420b1a873f06b1f43fc4c on master.


add Pagination.Custom dot animation

I'm adding Paging.Custom dot animation, it is for my personal project but I contribute here since I think it may helps someone.
By default, it will takes width, height, borderRadius and backgroundColor from dotStyle and activeDotStyle and create animation from them.
I also provide a function that user can use to add custom animated style:
customReanimatedStyle?: (
    progress: number,
    index: number,
    length: number,
  ) => DefaultStyle

Below is the example how we use it (The 2 last paging dots):

Please take a look, thank you!

Hello, first of all, thanks to your code, I was able to customize the indicator animation.
But when I tried again today, I got this error during npm install.
I'm trying to fix this ploblem. Is there any expected solution to this?
Reanimated version
3.15.0
React Native version
0.75.1
Platforms
Android
npm error code 1
npm error git dep preparation failed
npm error command<EMAIL_ADDRESS><EMAIL_ADDRESS>install --force --cache=/Users/i/.npm --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run
npm error ><EMAIL_ADDRESS>prepare
npm error > bob build
npm error
npm error ℹ Building target commonjs
npm error ℹ Cleaning up previous build at lib/commonjs
npm error ℹ Compiling 45 files in src with babel
npm error ✔ Wrote files to lib/commonjs
npm error ℹ Building target module
npm error ℹ Cleaning up previous build at lib/module
npm error ℹ Compiling 45 files in src with babel
npm error ✔ Wrote files to lib/module
npm error ℹ Building target typescript
npm error ℹ Cleaning up previous build at lib/typescript
npm error ℹ Generating type definitions with tsc
npm error src/components/Pagination/Custom/index.tsx:6:35 - error TS2307: Cannot find module 'react-native-reanimated/lib/typescript/hook/commonTypes' or its corresponding type declarations.
npm error
npm error 6 import type { DefaultStyle } from "react-native-reanimated/lib/typescript/hook/commonTypes";
npm error                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm error
npm error src/components/Pagination/Custom/PaginationItem.tsx:14:35 - error TS2307: Cannot find module 'react-native-reanimated/lib/typescript/hook/commonTypes' or its corresponding type declarations.
npm error
npm error 14 import type { DefaultStyle } from "react-native-reanimated/lib/typescript/hook/commonTypes";
npm error                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm error
npm error src/components/Pagination/Custom/PaginationItem.tsx:96:12 - error TS2322: Type 'AnimatableNumericValue | undefined' is not assignable to type 'number'.
npm error   Type 'undefined' is not assignable to type 'number'.
npm error
npm error 96           [activeBorderRadius, borderRadius, borderRadius],
npm error               ~~~~~~~~~~~~~~~~~~
npm error
npm error src/components/Pagination/Custom/PaginationItem.tsx:96:32 - error TS2322: Type 'AnimatableNumericValue | undefined' is not assignable to type 'number'.
npm error   Type 'undefined' is not assignable to type 'number'.
npm error
npm error 96           [activeBorderRadius, borderRadius, borderRadius],
npm error                                   ~~~~~~~~~~~~
npm error
npm error src/components/Pagination/Custom/PaginationItem.tsx:96:46 - error TS2322: Type 'AnimatableNumericValue | undefined' is not assignable to type 'number'.
npm error   Type 'undefined' is not assignable to type 'number'.
npm error
npm error 96           [activeBorderRadius, borderRadius, borderRadius],
npm error                                                 ~~~~~~~~~~~~
npm error
npm error src/components/Pagination/Custom/PaginationItem.tsx:102:14 - error TS2322: Type 'ColorValue' is not assignable to type 'string | number'.
npm error   Type 'OpaqueColorValue' is not assignable to type 'string | number'.
npm error
npm error 102             [activeBackgroundColor, backgroundColor, backgroundColor],
npm error                  ~~~~~~~~~~~~~~~~~~~~~
npm error
npm error src/components/Pagination/Custom/PaginationItem.tsx:102:37 - error TS2322: Type 'ColorValue' is not assignable to type 'string | number'.
npm error
npm error 102             [activeBackgroundColor, backgroundColor, backgroundColor],
npm error                                         ~~~~~~~~~~~~~~~
npm error
npm error src/components/Pagination/Custom/PaginationItem.tsx:102:54 - error TS2322: Type 'ColorValue' is not assignable to type 'string | number'.
npm error
npm error 102             [activeBackgroundColor, backgroundColor, backgroundColor],
npm error                                                          ~~~~~~~~~~~~~~~
npm error
npm error
npm error Found 8 errors in 2 files.
npm error
npm error Errors  Files
npm error      1  src/components/Pagination/Custom/index.tsx:6
npm error      7  src/components/Pagination/Custom/PaginationItem.tsx:14
npm error ✖ Failed to build definition files.
npm error npm warn using --force Recommended protections disabled.
npm error npm warn ERESOLVE overriding peer dependency
npm error npm warn ERESOLVE overriding peer dependency
npm error npm warn ERESOLVE overriding peer dependency
npm error npm warn ERESOLVE overriding peer dependency
npm error npm warn While resolving<EMAIL_ADDRESS>npm error npm warn Found<EMAIL_ADDRESS>npm error npm warn node_modules/@types/react
npm error npm warn   dev<EMAIL_ADDRESS>from the root project
npm error npm warn   1 more (@types/react-test-renderer)
npm error npm warn
npm error npm warn Could not resolve dependency:
npm error npm warn peerOptional<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm error npm warn node_modules/@testing-library/react-hooks
npm error npm warn   dev<EMAIL_ADDRESS>from the root project
npm error npm warn
npm error npm warn Conflicting peer dependency<EMAIL_ADDRESS>npm error npm warn node_modules/@types/react
npm error npm warn   peerOptional<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm error npm warn   node_modules/@testing-library/react-hooks
npm error npm warn     dev<EMAIL_ADDRESS>from the root project
npm error npm warn ERESOLVE overriding peer dependency
npm error npm warn While resolving<EMAIL_ADDRESS>npm error npm warn Found<EMAIL_ADDRESS>npm error npm warn node_modules/react
npm error npm warn   dev<EMAIL_ADDRESS>from the root project
npm error npm warn   5 more (@testing-library/jest-native, react-native, ...)
npm error npm warn
npm error npm warn Could not resolve dependency:
npm error npm warn peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm error npm warn node_modules/@testing-library/react-hooks
npm error npm warn   dev<EMAIL_ADDRESS>from the root project
npm error npm warn
npm error npm warn Conflicting peer dependency<EMAIL_ADDRESS>npm error npm warn node_modules/react
npm error npm warn   peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm error npm warn   node_modules/@testing-library/react-hooks
npm error npm warn     dev<EMAIL_ADDRESS>from the root project
npm error npm warn ERESOLVE overriding peer dependency
npm error npm warn While resolving<EMAIL_ADDRESS>npm error npm warn Found<EMAIL_ADDRESS>npm error npm warn node_modules/react-test-renderer
npm error npm warn   dev<EMAIL_ADDRESS>from the root project
npm error npm warn   2 more (@testing-library/jest-native, @testing-library/react-native)
npm error npm warn
npm error npm warn Could not resolve dependency:
npm error npm warn peerOptional<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm error npm warn node_modules/@testing-library/react-hooks
npm error npm warn   dev<EMAIL_ADDRESS>from the root project
npm error npm warn
npm error npm warn Conflicting peer dependency<EMAIL_ADDRESS>npm error npm warn node_modules/react-test-renderer
npm error npm warn   peerOptional<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm error npm warn   node_modules/@testing-library/react-hooks
npm error npm warn     dev<EMAIL_ADDRESS>from the root project
npm error npm warn ERESOLVE overriding peer dependency
npm error npm warn While resolving<EMAIL_ADDRESS>npm error npm warn Found<EMAIL_ADDRESS>npm error npm warn node_modules/react
npm error npm warn   dev<EMAIL_ADDRESS>from the root project
npm error npm warn   5 more (@testing-library/jest-native, react-native, ...)
npm error npm warn
npm error npm warn Could not resolve dependency:
npm error npm warn peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm error npm warn node_modules/react-test-renderer
npm error npm warn   dev<EMAIL_ADDRESS>from the root project
npm error npm warn   2 more (@testing-library/jest-native, @testing-library/react-native)
npm error npm warn
npm error npm warn Conflicting peer dependency<EMAIL_ADDRESS>npm error npm warn node_modules/react
npm error npm warn   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm error npm warn   node_modules/react-test-renderer
npm error npm warn     dev<EMAIL_ADDRESS>from the root project
npm error npm warn     2 more (@testing-library/jest-native, @testing-library/react-native)
npm error npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm error npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.
npm error npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.
npm error npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
npm error npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.
npm error npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm error npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm error npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm error npm warn deprecated<EMAIL_ADDRESS>this library is no longer supported
npm error npm warn deprecated<EMAIL_ADDRESS>Use @eslint/config-array instead
npm error npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.
npm error npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm error npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
npm error npm warn deprecated<EMAIL_ADDRESS>Use @eslint/object-schema instead
npm error npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm error npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm error npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
npm error npm warn deprecated<EMAIL_ADDRESS>You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm error npm warn deprecated
npm error npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm error npm warn deprecated<EMAIL_ADDRESS>babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm error npm warn deprecated<EMAIL_ADDRESS>Package renamed to https://github.com/unjs/ofetch
npm error npm warn deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm error npm warn deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm error npm warn deprecated<EMAIL_ADDRESS>support for ECMAScript is superseded by `uglify-js` as of v3.13.0
npm error bob build
npm error
npm error build files for publishing
npm error
npm error Options:
npm error   --help     Show help                                                 [boolean]
npm error   --version  Show version number                                       [boolean]
npm error
npm error Error: Failed to build definition files.
npm error     at build (/Users/i/.npm/_cacache/tmp/git-cloneRyeB64HUIdyK/node_modules/react-native-builder-bob/lib/targets/typescript.js:112:11)
npm error     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
npm error     at async Object.handler (/Users/i/.npm/_cacache/tmp/git-cloneRyeB64HUIdyK/node_modules/react-native-builder-bob/lib/index.js:379:9)
npm error npm error code 1
npm error npm error path /Users/i/.npm/_cacache/tmp/git-cloneRyeB64HUIdyK
npm error npm error command failed
npm error npm error command sh -c bob build
npm error
npm error npm error A complete log of this run can be found in: /Users/i/.npm/_logs/2024-09-09T10_29_58_651Z-debug-0.log

npm error A complete log of this run can be found in: /Users/i/.npm/_logs/2024-09-09T10_29_42_554Z-debug-0.log

Hi @xogus7 ,
Thank you for checking and confirm that my code is working.
Regarding your question, from what you shared, I see that you are using react<EMAIL_ADDRESS><EMAIL_ADDRESS>and node@20.15.0,... they are new and have many changes. So In my experience, we need to wait at least 6 months (or even 1 year) to use them, to giving time for packages that depend on them are updated and stable, in this case is react-native-reanimated.
From my side, I'm still using<EMAIL_ADDRESS>react-native-reanimated-carousel from my fork<EMAIL_ADDRESS>and<EMAIL_ADDRESS>And it is working just fine.
I'm using my fork for my own project, it still also not reviewed by package owner, so for now, I cannot update or change anything to help you.

@bdtren WOW Thank you for your quick comment, I think so, too. probably it a problem caused by a sudden dependency update. your comment helped me to catch the direction of solution. Thank you!


Disallow double bracket initialization

Addresses https://github.com/trinodb/trino-gateway/issues/155.

@ebyhr ?


Add support for using impersonate service account with gcloud cli

This PR allow user to login as a impersonate service account using gcloud cli

Can you point me to docs that explain the impersonate values?

I can't find the docs for that but other client like Java already implemented this, you can check here.
When you run this command: gcloud auth application-default login<EMAIL_ADDRESS>it generate a file called application_default_credentials.json with the following content like below, and this PR just use the right value if type is impersonated_service_account
{
  "service_account_impersonation_url": "",
  "source_credentials": {
    "client_id": "",
    "client_secret": "",
    "refresh_token": "",
    "type": "authorized_user"
  },
  "type": "impersonated_service_account"
}

@rebaz94 – is there an issue open for this?

@rebaz94 – is there an issue open for this?

yes here #454


rez-env with PYTHONHOME set.

Hey guys,
I just came across a "bug?" i never experienced before:
It seems that a package can't set a PYTHONPATH if PYTHONHOME is set.
error message: ImportError: No module named site
How to reproduce it on Centos 7.5:
export PYTHONHOME="/usr/lib64"
rez-env myPackage -- python
Where you package have to set PYTHONPATH
i.e: env.PYTHONPATH.append("{root}/rez_myTool")
Same commands without setting PYTHONHOME work.
Same commands with a package who is not setting PYTHONPATH work.
Cheers,
Clement

The problem is probably that PYTHONHOME doesn't contain a site.py file, which python expects to be in the PYTHONHOME directory, as it is automatically imported on python startup.
I would expect you to get the exact same error if you just ran python without the rez command
$ export PYTHONHOME="/usr/lib64"
$ python

That is true.
So it is not an issue related to rez then, sorry for that.
export PYTHONHOME="/usr" fixes the issue.
Even though site.py is inside /usr/lib64/python2.7
Probably some dependencies..
Thanks for the help!


Run fmriprep-docker as user (-u) by default?

This would allow users who are not in the docker group to run their workflows more conveniently without elevated privileges (provided they can run docker without sudo).

This seems reasonable to me, and pretty easy to auto-detect. We could check whether the scratch and output directories will be writable before dropping into Docker, too.

Been looking at this, and correctly handling Windows users is going to be a pain. I guess we could leave them as root and default to -u for posix users...


workflows: Add staticcheck

Effectively the same change done in stboot because staticcheck is nice.

Codecov Report

Merging #29 (db85223) into main (e56c17e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #29   +/-   ##
=======================================
  Coverage   11.49%   11.49%
=======================================
  Files          13       13
  Lines         844      844
=======================================
  Hits           97       97
  Misses        745      745
  Partials        2        2

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

Sure. However it looks like we forgot to pin the golangci-lint version. let me fix this in #30 first.


PLATUI-2755 poc showing what I meant about play way

didn't make it totally multi-project, just as a demo
we don't have vnu anymore so some scripted tests fail, I fixed e2e-with-defaults as a demonstration.
this should pass:
sbt "scripted sbt-accessibility-linter/e2e-with-defaults"

the play way is that the play sbt plugin adds all your play deps for you (for the correct play version) for example:
https://github.com/playframework/play-scala-seed.g8/blob/3.0.x/src/main/g8/project/plugins.sbt
is enough, no direct dep is needed in build.sbt because it adds it for you
the way that play does this is using a little bit of code gen in the plugin to add some constants
https://github.com/playframework/playframework/blob/main/project/Tasks.scala#L10
added via Compile / sourceGenerators
https://github.com/playframework/playframework/blob/97147f1af1399fb8393ff83e22a376326d6f6048/build.sbt#L232-L248
so that was my thinking originally on this (vs just asking people to add the dep now), have multi-project build with a different source generator that added the play suffix for scalatest library that can be used like:
"uk.gov.hmrc" %% s"scalatest-accessibility-linter-${uk.gov.hmrc.SbtAccessibilityLinter.playVersion}" % "1.0.0" % Test

Closing stale PR before archiving


[BUG]  lose getter/setter method after compile

Describe the bug
using @Getter or @Setter annotation, when similary but not same word defined as field in Java class, it loses some getter/setter methods after compile
To Reproduce
@Setter
@Getter
public class Test {

    private JSONObject jCReturnedData;

    private JSONObject jcreturnedData;

    private String mQType;

    private String mqtype;
}

after compiled, it loses the getter and setter methods of field of 'jcreturnedData' and 'mqtype'
Expected behavior
should retain all the getter/setter methods
Version info (please complete the following information):

Lombok version 1.18.14
Java version 1.8.0_101

This is a duplicate of #2590. The problem is that lombok searches for existing methods without case sensitivity.

Duplicate of #2130: We won't fix this, for reasons, see that issue.

Duplicate of #2130: We won't fix this, for reasons, see that issue.


Update to latest simconnect (bump release)

Thanks, I'll have a look!
I'm no longer using ForeFlight, so I can't test this, but if it looks good I'll merge.


Reduce plots mod 2pi

Reduce plots in isothermal, toroidal-poloidal, and 2D Cartesian by 2*pi.

Introduced plotwrapped.m