Set Value not working after Update to 1.67.0 Version

I agree to the following

[X] I have read the documentation right now
[X] I have read the FAQs right now
[X] I am aware of the latest release notes
[X] I am aware that an integration that was installed via HACS also needs to be updated via HACS
[X] The Backend (CCU/Homegear/...) is working as expected, devices are taught in and are controllable by its own UI.
[X] I am running the latest version of the custom_component (and Home Assistant)

The problem
After Changing Target Temperatur  via Locelace UI Thermostat widget homematicIP Local is crashing and reporting following error
2024-10-17 18:14:29.713 ERROR (SyncWorker_32) [pyhomematic.devicetypes.generic] HMGeneric.setValue: SET_POINT_TEMPERATURE on 000CA0C9A72EC0:1 Exception: <Fault -1: 'Generic error (TIMEOUT)'>
What version of HomematicIP (local) has the issue?
1.67.0
What was the last working version of HomematicIP (local)?
1.66.0
What type of installation are you running?
Home Assistant OS
What type of installation are you running for your homematic backend?
RaspberryMatic Standalone
Which version of your homematic backend are you running?
No response
What hardware are you running for your system?
No response
Which config details do you use

[ ] TLS
[ ] callback data (see)

Which interfaces do you use?

[X] Homematic IP
[X] Homematic (Bidcos-RF)
[ ] Groups (Heating-Group)
[ ] BidCos-Wired (HM-Wired)

Diagnostics information (no logs here)
No response
Log file extract. Anything in the logs that might be useful for us? The log (Setting/System/Logs -> load full log) is the best source to support trouble shooting!
2024-10-17 18:06:03.055 DEBUG (MainThread) [hahomematic.central] check_connection: Checking connection to server Raspimatic
2024-10-17 18:06:03.057 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Increase pending PING count: Raspimatic-HmIP-RF - 1 for ts: 2024-10-17 18:06:03.056298
2024-10-17 18:06:03.057 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('ping', ("Raspimatic-HmIP-RF#17.10.2024 18:06:03.056298'",))
2024-10-17 18:06:03.073 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Increase pending PING count: Raspimatic-BidCos-RF - 1 for ts: 2024-10-17 18:06:03.072283
2024-10-17 18:06:03.074 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('ping', ("Raspimatic-BidCos-RF#17.10.2024 18:06:03.072283'",))
2024-10-17 18:06:03.080 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = Raspimatic-HmIP-RF, channel_address = CENTRAL:0, parameter = PONG, value = Raspimatic-HmIP-RF#17.10.2024 18:06:03.056298'
2024-10-17 18:06:03.081 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Reduce pending PING count: Raspimatic-HmIP-RF - 0 for ts: 2024-10-17 18:06:03.056298
2024-10-17 18:06:03.087 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = Raspimatic-BidCos-RF, channel_address = CENTRAL, parameter = PONG, value = Raspimatic-BidCos-RF#17.10.2024 18:06:03.072283'
2024-10-17 18:06:03.088 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Reduce pending PING count: Raspimatic-BidCos-RF - 0 for ts: 2024-10-17 18:06:03.072283
2024-10-17 18:06:12.374 DEBUG (MainThread) [hahomematic.client.json_rpc] DO_RENEW_LOGIN: method: Session.renew [DZvcsAlc7k]
2024-10-17 18:06:12.521 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: Program.getAll
2024-10-17 18:06:12.525 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_ALL_PROGRAMS: Getting all programs
2024-10-17 18:06:12.525 DEBUG (MainThread) [hahomematic.platforms.hub] UPDATE_PROGRAM_ENTITIES: 3 programs received for Raspimatic
2024-10-17 18:06:12.690 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: SysVar.getAll
2024-10-17 18:06:12.690 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_ALL_SYSTEM_VARIABLES: Getting all system variables
2024-10-17 18:06:12.861 DEBUG (MainThread) [hahomematic.client.json_rpc] POST_SCRIPT: method: ReGa.runScript [get_system_variables_ext_marker.fn]
2024-10-17 18:06:12.861 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_SYSTEM_VARIABLES_EXT_MARKERS: Getting system variables ext markers
2024-10-17 18:06:12.862 DEBUG (MainThread) [hahomematic.platforms.hub] UPDATE_SYSVAR_ENTITIES: 9 sysvars received for Raspimatic
2024-10-17 18:06:12.863 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Sysvar changed event fired for Sv_Alarmzone 1
2024-10-17 18:06:12.863 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Sysvar changed event fired for Sv_Servicemeldungen
2024-10-17 18:06:12.864 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Sysvar changed event fired for Sv_WatchDog: no-internet
2024-10-17 18:06:18.091 DEBUG (MainThread) [hahomematic.central] check_connection: Checking connection to server Raspimatic
2024-10-17 18:06:18.092 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Increase pending PING count: Raspimatic-HmIP-RF - 1 for ts: 2024-10-17 18:06:18.091540
2024-10-17 18:06:18.092 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('ping', ("Raspimatic-HmIP-RF#17.10.2024 18:06:18.091540'",))
2024-10-17 18:06:18.102 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Increase pending PING count: Raspimatic-BidCos-RF - 1 for ts: 2024-10-17 18:06:18.102465
2024-10-17 18:06:18.103 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('ping', ("Raspimatic-BidCos-RF#17.10.2024 18:06:18.102465'",))
2024-10-17 18:06:18.108 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = Raspimatic-HmIP-RF, channel_address = CENTRAL:0, parameter = PONG, value = Raspimatic-HmIP-RF#17.10.2024 18:06:18.091540'
2024-10-17 18:06:18.109 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Reduce pending PING count: Raspimatic-HmIP-RF - 0 for ts: 2024-10-17 18:06:18.091540
2024-10-17 18:06:18.113 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = Raspimatic-BidCos-RF, channel_address = CENTRAL, parameter = PONG, value = Raspimatic-BidCos-RF#17.10.2024 18:06:18.102465'
2024-10-17 18:06:18.114 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Reduce pending PING count: Raspimatic-BidCos-RF - 0 for ts: 2024-10-17 18:06:18.102465
2024-10-17 18:06:27.502 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = Raspimatic-HmIP-RF, channel_address = 000CA0C9AB23B8:0, parameter = UNREACH, value = True
2024-10-17 18:06:27.504 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.508 ERROR (SyncWorker_12) [pyhomematic.devicetypes.generic] HMGeneric.setValue: SET_POINT_TEMPERATURE on 000CA0C9AB23B8:1 Exception: <Fault -1: 'Generic error (TIMEOUT)'>
2024-10-17 18:06:27.510 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.511 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.512 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.513 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.513 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.514 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.515 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.516 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8 Humidity
2024-10-17 18:06:27.517 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.518 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.519 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.519 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.526 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.526 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8 Actual Temperature
2024-10-17 18:06:27.527 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.528 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8
2024-10-17 18:06:27.528 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for HmIP-BWTH 000CA0C9AB23B8 State ch9
2024-10-17 18:06:33.119 DEBUG (MainThread) [hahomematic.central] check_connection: Checking connection to server Raspimatic
2024-10-17 18:06:33.120 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Increase pending PING count: Raspimatic-HmIP-RF - 1 for ts: 2024-10-17 18:06:33.119436
2024-10-17 18:06:33.120 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('ping', ("Raspimatic-HmIP-RF#17.10.2024 18:06:33.119436'",))
2024-10-17 18:06:33.130 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Increase pending PING count: Raspimatic-BidCos-RF - 1 for ts: 2024-10-17 18:06:33.129657
2024-10-17 18:06:33.130 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('ping', ("Raspimatic-BidCos-RF#17.10.2024 18:06:33.129657'",))
2024-10-17 18:06:33.138 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = Raspimatic-HmIP-RF, channel_address = CENTRAL:0, parameter = PONG, value = Raspimatic-HmIP-RF#17.10.2024 18:06:33.119436'
2024-10-17 18:06:33.139 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Reduce pending PING count: Raspimatic-HmIP-RF - 0 for ts: 2024-10-17 18:06:33.119436
2024-10-17 18:06:33.143 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = Raspimatic-BidCos-RF, channel_address = CENTRAL, parameter = PONG, value = Raspimatic-BidCos-RF#17.10.2024 18:06:33.129657'
2024-10-17 18:06:33.144 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Reduce pending PING count: Raspimatic-BidCos-RF - 0 for ts: 2024-10-17 18:06:33.129657
2024-10-17 18:06:42.310 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: Program.getAll
2024-10-17 18:06:42.311 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_ALL_PROGRAMS: Getting all programs
2024-10-17 18:06:42.311 DEBUG (MainThread) [hahomematic.platforms.hub] UPDATE_PROGRAM_ENTITIES: 3 programs received for Raspimatic
2024-10-17 18:06:42.466 DEBUG (MainThread) [hahomematic.client.json_rpc] POST method: SysVar.getAll
2024-10-17 18:06:42.466 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_ALL_SYSTEM_VARIABLES: Getting all system variables
2024-10-17 18:06:42.634 DEBUG (MainThread) [hahomematic.client.json_rpc] POST_SCRIPT: method: ReGa.runScript [get_system_variables_ext_marker.fn]
2024-10-17 18:06:42.635 DEBUG (MainThread) [hahomematic.client.json_rpc] GET_SYSTEM_VARIABLES_EXT_MARKERS: Getting system variables ext markers
2024-10-17 18:06:42.635 DEBUG (MainThread) [hahomematic.platforms.hub] UPDATE_SYSVAR_ENTITIES: 9 sysvars received for Raspimatic
2024-10-17 18:06:42.636 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Sysvar changed event fired for Sv_Alarmzone 1
2024-10-17 18:06:42.637 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Sysvar changed event fired for Sv_Servicemeldungen
2024-10-17 18:06:42.638 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Sysvar changed event fired for Sv_WatchDog: no-internet
2024-10-17 18:06:48.145 DEBUG (MainThread) [hahomematic.central] check_connection: Checking connection to server Raspimatic
2024-10-17 18:06:48.146 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Increase pending PING count: Raspimatic-HmIP-RF - 1 for ts: 2024-10-17 18:06:48.145671
2024-10-17 18:06:48.146 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('ping', ("Raspimatic-HmIP-RF#17.10.2024 18:06:48.145671'",))
2024-10-17 18:06:48.158 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Increase pending PING count: Raspimatic-BidCos-RF - 1 for ts: 2024-10-17 18:06:48.157731
2024-10-17 18:06:48.158 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('ping', ("Raspimatic-BidCos-RF#17.10.2024 18:06:48.157731'",))
2024-10-17 18:06:48.165 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = Raspimatic-HmIP-RF, channel_address = CENTRAL:0, parameter = PONG, value = Raspimatic-HmIP-RF#17.10.2024 18:06:48.145671'
2024-10-17 18:06:48.165 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Reduce pending PING count: Raspimatic-HmIP-RF - 0 for ts: 2024-10-17 18:06:48.145671
2024-10-17 18:06:48.172 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = Raspimatic-BidCos-RF, channel_address = CENTRAL, parameter = PONG, value = Raspimatic-BidCos-RF#17.10.2024 18:06:48.157731'
2024-10-17 18:06:48.174 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Reduce pending PING count: Raspimatic-BidCos-RF - 0 for ts: 2024-10-17 18:06:48.157731
2024-10-17 18:06:53.676 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = Raspimatic-HmIP-RF, channel_address = 001F5F298D8857:0, parameter = DUTY_CYCLE_LEVEL, value = 0.0
2024-10-17 18:06:53.676 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device refreshed event fired for RPI-RF-MOD 001F5F298D8857 Duty Cycle Level
2024-10-17 18:06:53.788 DEBUG (MainThread) [hahomematic.central] EVENT: interface_id = Raspimatic-HmIP-RF, channel_address = 001F5F298D8857:0, parameter = CARRIER_SENSE_LEVEL, value = 3.5
2024-10-17 18:06:53.788 DEBUG (MainThread) [custom_components.homematicip_local.generic_entity] Device updated event fired for RPI-RF-MOD 001F5F298D8857 Carrier Sense Level
2024-10-17 18:07:03.172 DEBUG (MainThread) [hahomematic.central] check_connection: Checking connection to server Raspimatic
2024-10-17 18:07:03.173 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Increase pending PING count: Raspimatic-HmIP-RF - 1 for ts: 2024-10-17 18:07:03.173194
2024-10-17 18:07:03.174 DEBUG (MainThread) [hahomematic.client.xml_rpc] __ASYNC_REQUEST: ('ping', ("Raspimatic-HmIP-RF#17.10.2024 18:07:03.173194'",))
2024-10-17 18:07:03.189 DEBUG (MainThread) [hahomematic.caches.dynamic] PING PONG CACHE: Increase pending PING count: Raspimatic-BidCos-RF - 1 for ts: 2024-10-17 18:07:03.187351

Additional information
No response

SET_POINT_TEMPERATURE on 000CA0C9A72EC0:1 Exception: <Fault -1: 'Generic error (TIMEOUT)'>

TIMEOUT -> Du hast ein Problem mit deinem System (CCU, Netzwerk, ....), oder die CCU mit dem Gerät.
Das ist kein Problem der Integration.

danke, ich habe jetzt nochmal alles neu gestartet, es scheint jetzt zu funktionieren, tut mir leid für die Fehlmeldung!!

Kein Problem


(maint) fix AIX fact test for AIX 7.2

Add the kernel_release and kernel_major_version vars for AIX 7.2

The following was a result of a manual run of AIX 7.2:
      Test Suite: tests @ 2017-02-08 22:03:37 -0800
      - Host Configuration Summary -
              - Test Case Summary for suite 'tests' -
       Total Suite Time: 207.26 seconds
      Average Test Time: 3.77 seconds
              Attempted: 55
                 Passed: 45
                 Failed: 0
                Errored: 0
                Skipped: 10
                Pending: 0
                  Total: 55
      - Specific Test Case Status -
Failed Tests Cases:
Errored Tests Cases:
Skipped Tests Cases:
    Test Case tests/ticket_1164_win32ole_custom_fact.rb
    Test Case tests/verify_mountpoints.rb
    Test Case tests/facts/debian.rb
    Test Case tests/facts/el.rb
    Test Case tests/facts/fedora.rb
    Test Case tests/facts/macosx.rb
    Test Case tests/facts/sles.rb
    Test Case tests/facts/solaris.rb
    Test Case tests/facts/ubuntu.rb
    Test Case tests/facts/windows.rb
Pending Tests Cases:
                                                  No tests to run for suite 'post_suite'
  No tests to run for suite 'pre_cleanup'
  Cleanup: cleaning up after successful run
  ssh connection to aix72-POWER-1 has been terminated
  You can reproduce this run with:
  /home/sean/.rvm/gems/ruby-2.3.3/bin/beaker --options-file merged_options.rb --hosts=hosts.yaml
  Important ENV variables that may have affected your run:
      GEM_HOME          /home/sean/.rvm/gems/ruby-2.3.3
      GEM_PATH          /home/sean/.rvm/gems/ruby-2.3.3:/home/sean/.rvm/gems/ruby-2.3.3@global
      RUBYLIB           /home/sean/.rvm/gems/ruby-2.3.3/gems/bundler-1.13.7/lib
      PATH              /home/sean/.rvm/gems/ruby-2.3.3/bin:/home/sean/.rvm/gems/ruby-2.3.3@global/bin:/home/sean/.rvm/rubies/ruby-2.3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/sean/.rvm/bin:/mnt/c/Program Files/Misc Tools/:/mnt/c/ProgramData/chocolatey/bin:/opt/puppetlabs/bin
      home              /home/sean
Beaker completed successfully, thanks.
cp hosts.yaml log/latest/config.yml
{"HOSTS"=>{"unknown"=>{"roles"=>["agent"], "platform"=>"aix-7.2-power"}}}
mv merged_options.rb log/latest

👍


Little issue, transfer rate is too slow :/

So, I'm playing on Sky Factory 3. I Am getting power from my Big Reactor, and sending towards a draconic energy core with Flux-Networks. My Big Reactor makes over 107k RF a tick, but for some reason, it is only transferring 10k a tick? When I look in my core, it isn't receiving ANY energy. It just stays at 0 RF a tick. when I disconnect it, It becomes -10k rf a tick. (From my machines) The max was default, but even if I spam nines in the Max rate bar, doesn't work. It should be transferring all the energy. I'm not sure what the issue is, as it was working perfectly yesterday. Please help? not sure if it is flux networks, draconic evolution, or big reactors, but I think flux-networks in the culprit here, I'm not sure. Help would be nice!
Thanks!
(Playing 1.10.2)

Try putting cryo-stabilized fluxduct between reactor tap and plug

no longer support for 1.10.2


WaveformToFbankConverter does not work as expected for channels > 1

Describe the bug:
While the AudioDecoder can read a stereo wav file, the output of WaveformToFbankConverter is always num_frames x num_mel_bins.
Describe how to reproduce:
audio_wav_path, device, dtype = ...
audio_decoder = AudioDecoder(dtype=torch.float32, device=device)
fbank_converter = WaveformToFbankConverter(
    num_mel_bins=80,
    waveform_scale=2**15,
    channel_last=True,
    standardize=True,
    device=device,
    dtype=dtype,
)
with Path(audio_wav_path).open("rb") as fb:
    block = MemoryBlock(fb.read())

decoded_audio = audio_decoder(block) # for stereo waveform shape is (num_samples x num_channels=2)
fbank_features = fbank_converter(decoded_audio)['fbank']
# shape is always (num_frames x num_mel_bins) irrespective of num_channels

Describe the expected behavior:
WaveformToFbankConverter should handle stereo/multi-channel audio and return (num_channels x num_frames x num_mel_bins)
Environment:
Installed with following command:
pip install fairseq2 --pre --extra-index-url https://fair.pkg.atmeta.com/fairseq2/whl/nightly/pt2.2.0/cu118

@cbalioglu Thanks for adding it, also the following feature might be good to have:

extend it to BxCxT tensors to enable batch processing, I understand the computation still happens on the cpu in a loop, but a native loop is faster than a python loop.


Pdb reader test

Adding test for the pdb reader topology reader.

/home/votca/votca/csg/src/tests/test_pdbreader.cc(123): error: in "pdbreader_test/test_topologyreader": check ceil_(v.getX(), 3) == ceil_(x.at(i), 3) has failed [-0.53800000000000003 != -0.53900000000000003]
/home/votca/votca/csg/src/tests/test_pdbreader.cc(124): error: in "pdbreader_test/test_topologyreader": check ceil_(v.getY(), 3) == ceil_(y.at(i), 3) has failed [0.0030000000000000001 != -0.002]
/home/votca/votca/csg/src/tests/test_pdbreader.cc(125): error: in "pdbreader_test/test_topologyreader": check ceil_(v.getZ(), 3) == ceil_(z.at(i), 3) has failed [0.079000000000000001 != -0.079000000000000001]
/home/votca/votca/csg/src/tests/test_pdbreader.cc(125): error: in "pdbreader_test/test_topologyreader": check ceil_(v.getZ(), 3) == ceil_(z.at(i), 3) has failed [0.0060000000000000001 != -0.0050000000000000001]
/home/votca/votca/csg/src/tests/test_pdbreader.cc(125): error: in "pdbreader_test/test_topologyreader": check ceil_(v.getZ(), 3) == ceil_(z.at(i), 3) has failed [0.047 != -0.045999999999999999]
/home/votca/votca/csg/src/tests/test_pdbreader.cc(125): error: in "pdbreader_test/test_topologyreader": check ceil_(v.getZ(), 3) == ceil_(z.at(i), 3) has failed [0.050999999999999997 != -0.050000000000000003]

Looks like a float round off error!


Preparing for Spring 2022 biannual survey

(Please do not merge just yet, I will request a review when ready to merge into master)

Extend continuous integration to cover fall 2021 to spring 2022 transition
Create blank 2022 data form
Create blank Spring 2022 raw-data form for collecting data
Update spring workflow instructions

Hey @jess-shue I just tagged you for a review but let's discuss in-person at our meeting on Thursday


SQL cell stopped executing replacement scans properly with DuckDB 1.10

Describe the bug

At first I thought the problem occurred only when I run uv run marimo edit, but then I realized the difference is actually what DuckDB version I have installed. After upgrading my global installation, I got the bug again with uv.
Environment
marimo env: (no bug)
{
  "marimo": "0.8.13",
  "OS": "Darwin",
  "OS Version": "23.6.0",
  "Processor": "arm",
  "Python Version": "3.8.13",
  "Binaries": {
    "Browser": "119.0.6045.123",
    "Node": "v18.17.0"
  },
  "Dependencies": {
    "click": "8.1.7",
    "importlib-resources": "6.1.1",
    "jedi": "0.19.1",
    "markdown": "3.5.2",
    "pygments": "2.17.2",
    "pymdown-extensions": "10.7",
    "ruff": "0.5.5",
    "starlette": "0.36.1",
    "tomlkit": "0.12.3",
    "typing-extensions": "4.12.2",
    "uvicorn": "0.27.0",
    "websockets": "12.0"
  },
  "Optional Dependencies": {
    "altair": "5.4.0",
    "duckdb": "0.9.2",
    "pandas": "2.0.3",
    "polars": "0.20.6",
    "pyarrow": "15.0.0"
  }
}

uv run marimo env: (bug occurs)
{
  "marimo": "0.8.13",
  "OS": "Darwin",
  "OS Version": "23.6.0",
  "Processor": "arm",
  "Python Version": "3.12.4",
  "Binaries": {
    "Browser": "119.0.6045.123",
    "Node": "v18.17.0"
  },
  "Dependencies": {
    "click": "8.1.7",
    "importlib-resources": "missing",
    "jedi": "0.19.1",
    "markdown": "3.7",
    "pygments": "2.18.0",
    "pymdown-extensions": "10.9",
    "ruff": "0.6.4",
    "starlette": "0.38.5",
    "tomlkit": "0.13.2",
    "typing-extensions": "4.12.2",
    "uvicorn": "0.30.6",
    "websockets": "12.0"
  },
  "Optional Dependencies": {
    "altair": "5.4.1",
    "anywidget": "0.9.13",
    "duckdb": "1.1.0",
    "pandas": "2.2.2",
    "polars": "1.6.0",
    "pyarrow": "17.0.0"
  }
}

marimo env: (after DuckDB upgrade, bug occurs)
{
  "marimo": "0.8.13",
  "OS": "Darwin",
  "OS Version": "23.6.0",
  "Processor": "arm",
  "Python Version": "3.8.13",
  "Binaries": {
    "Browser": "119.0.6045.123",
    "Node": "v18.17.0"
  },
  "Dependencies": {
    "click": "8.1.7",
    "importlib-resources": "6.1.1",
    "jedi": "0.19.1",
    "markdown": "3.5.2",
    "pygments": "2.17.2",
    "pymdown-extensions": "10.7",
    "ruff": "0.5.5",
    "starlette": "0.36.1",
    "tomlkit": "0.12.3",
    "typing-extensions": "4.12.2",
    "uvicorn": "0.27.0",
    "websockets": "12.0"
  },
  "Optional Dependencies": {
    "altair": "5.4.0",
    "duckdb": "1.1.0",
    "pandas": "2.0.3",
    "polars": "0.20.6",
    "pyarrow": "15.0.0"
  }
}

Code to reproduce
import marimo

__generated_with = "0.8.13"
app = marimo.App(width="medium")

@app.cell
def __():
    import marimo as mo
    import pandas as pd
    return mo, pd

@app.cell
def __(pd):
    recruitment_text_conversations = pd.DataFrame([{"a": 1}, {"a": 2}])
    return recruitment_text_conversations,

@app.cell
def __(mo, recruitment_text_conversations):
    _df = mo.sql(
        f"""
        SELECT * FROM recruitment_text_conversations
        """
    )
    return

if __name__ == "__main__":
    app.run()

I can repro this. What is odd is that duckdb.sql directly works, but mo.sql does not, which just calls duckdb.sql. My guess is it has something to do with python globals() that it normally picks up

This is fixed by #2279 — thanks for reporting. It'll be up on PyPI within 20 minutes as 0.8.14.


Gate keeping of web services via NFT subscriptions

Description
Adds a flow allowing to:

Publish a new type of service asset for representing Web Services
Provides an e2e test to gate keep these web services via a proxy

Is this PR related with an open issue?
Related to Issue #
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] Follows the code style of this project.
[ ] Tests Cover Changes
[ ] Documentation

Funny gif

Some notes on the poc so far:
DDO schema and encryption of sensitive fields
I think something like this adds extra complexity. Also I don't think we should re-use the files field
authentication: {
  type: 'basic',
  token: ''
}

We should at least for now work only with headers:
this is what we define in the metadata
metadata: {
    main: {
        type: 'service'
        webService: {
            type: 'RESTful',
            endpoints: [
                {
                    GET: 'http://localhost:3000'
                }
            ],
            headers: [
                {
                    Authorization: 'Bearer xxxxxx'
                }
            ]
        }
    }
}

the headers get encrypted in the ddo (similar to what we do with files)
metadata: {
    main: {
        webService: {
            type: 'RESTful',
            endpoints: [
                {
                    GET: 'http://localhost:3000'
                }
            ],
            encryptedHeaders: 'jkhfdbgiqweruiodfdvdfjhjkdsfb'
        }
    }
}

The jwt tokens are encrypted instead of signed
Here I assume that the node is generating the tokens that way it can decrypt the headers
{
  did: 'did:nv:hjfghfd'
  endpoints: [
    {
      GET: 'http://localhost:3000'
    }
  ],
  headers: [
    {
      Authorization: 'Bearer xxxxxx'
    }
 ]
}

The proxy decodes the encrypted token, validates the endpoints and sets the headers before forwarding the request to the web service.
Endpoints
I don't think there is a need to specify the verb of the endpoints. I think it should be something like:
endpoints: ['http://localhost:3000/abc', 'http://localhost:3000/def']

As a added feature we support regular expressions on the endpoints. We can do the same thing that express does https://expressjs.com/en/guide/routing.html#route-paths.
Under the hood express is using https://github.com/pillarjs/path-to-regexp which we can use to validate that the subscriber is calling a valid endpoint

Use X-NVM-Authentication header


add CODEOWNERS, automatically manage waiting-for-author/review labels

This would automatically set some of the labels I currently always manually test, and often forget to set (but then again rely on them being set :) )
First of all it would add a CODEOWNERS file so a review gets requested from @rust-lang/docs-rs . I would understand if this it too much noise for the team and we could also limit the reviewers.
Also this would:

set the "waiting for review" label when a review is requested
set the "waiting for author" (and remove "review") when changes are requested (a review with just a comment wouldn't do this)
remove both labels when the PR is approved.

Based on the feedback I got I decided for a less intrusive way, and created a new team for reviewers: https://github.com/rust-lang/team/pull/1107
When the team is merged & deployed, we can continue with this PR.

Hm... thinking about this a little longer, I'm thinking about actually dropping the labels and the logic.
The idea:

"waiting for review" -> request review from docs-rs gh team
"waiting for author" -> when a review was sent

Incorporating the draft-status this would mean the only useful status label (for me personally) would be "waiting for deploy".
Will revisit this when https://github.com/rust-lang/team/pull/1107 is merged

I'll merge as-is for now, the new GH team was merged.
Potentially we could get rid of the labels and replace it with better searches.


adding base_model to ArbitrationProfile

Purpose or Intent

Solves the following problem (undefined method arbitration_records) that was happening on the ArbitrationProfile page after submitting a new arbitration profile

@miq-bot service broker, darga/no
cc: @chriskacerguis

@miq-bot add_label service broker, darga/no

I'm not sure I understand how this solves the issue in question.
Additionally, base_model's purpose is for where we have multiple abstract base models that share one base class, so from an STI perspective we just want to know that secondary level.
For example,
VmOrTemplate
  Vm
    VmVmware  # base_model here resolves to Vm, but base_class should resolve to VmOrTemplate
  MiqTemplate
    TemplateVmware  # base_model here resolves to MiqTemplate, but base_class should resolve to VmOrTemplate

I'm just curious if this applies to ArbitrationRecord as well.  Do you have that kind of structure?

[----] F, [2016-08-23T11:36:54.178636 #7783:557baac] FATAL -- : Error caught: [NoMethodError] undefined method `arbitration_records' for #<ManageIQ::Providers::Openstack::CloudManager:0x000000063d1f20> Did you mean? arbitration_profiles /home/hkataria/.rvm/gems/ruby-2.3.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/attribute_methods.rb:433:in `method_missing' /home/hkataria/dev/manageiq/app/models/miq_report/search.rb:68:in `get_parent_targets' /home/hkataria/dev/manageiq/app/models/miq_report/search.rb:93:in `paged_view_search' /home/hkataria/dev/manageiq/app/controllers/application_controller.rb:1564:in `get_view' /home/hkataria/dev/manageiq/app/controllers/application_controller/ci_processing.rb:858:in `show_details' /home/hkataria/dev/manageiq/app/controllers/ems_common.rb:544:in `fetch_arbitration_profiles_list' /home/hkataria/dev/manageiq/app/controllers/ems_common.rb:534:in `arbitration_profiles' Here is the stacktrace provided from Harpreet if it helps. We do have a similar structure that was causing an issue

I see...the call dynamically calls a method that looks like the base_model.
https://github.com/ManageIQ/manageiq/blob/master/app/models/miq_report/search.rb#L67-L68
@jntullo Can you move this method near the top of the file?  The other places we use it keep it at the top on purpose so it jumps out.

LGTM :+1: @chriskacerguis you good?

👍


Pre-training on the source domain

Hi, I have some question. In the processing of pre-training on the source domain, there are two lines codes in the PreTrainer of Trainer:
s_features, s_cls_out = self.model(s_inputs)
# target samples: only forward
t_features, _ = self.model(t_inputs)
        # backward main #

        loss_ce, loss_tr, prec1 = self._forward(s_features, s_cls_out, targets)
        loss = loss_ce + loss_tr

I think that the first line code is necessary for the overall optimization process and the three line code is not necessaty, which is not related to the overall loss. However, the third line code can boost the performance on target dataset. As you pointed out, this is only forward. I don't understand it. Can you give me help? Thank you.

Please refer to https://github.com/yxgeee/MMT/issues/17

I see. Thanks.


Build the project with latest source before publishing project.

The issue:
I modified some code and I forgot to "Save"  and I do a new publish.
Now when I open the page, I see the old web page.
The proposed fix:
Force to save the unsaved  before publishing.
Alternatively, prompt to developer to ask a confirmation.

The extension should invoke the "File.SaveAll" command before starting the publish process. Similar to what the build or F5 process does.


[ESP32] CLI option to set delayed action time in OTA Provider app and restart OTA Requestor once ApplyUpdate is successful

Problem

No option to set delayed action time in ESP32 OTA Provider application
We had to manually restart the ESP32 device once the ApplyUpdate is successful

Change overview

Added an cli option to set delayed action time in ESP32 OTA Provider application
Modified the Linux OTA Provider help for delayed action time cli option
Schedule the restart for ESP32 once apply update is successful
Also, Apply suggestion from #13484 in lighting-app
Minor changes in readme files

Testing

Linux OTA provider and ESP32 OTA requestor app
ESP32 OTA provider and tried OTA in ESP32 lighting app

@shubhamdp Please resolve the merge conflicts

/rebase

/rebase


MRG: Deprecate frequencies -> freqs

I actually hit this case today, so I figured I'd start a PR to fix #4116.
WIP because I've only fixed one, and haven't updated any tests.
Closes #4116.

Okay this one should be good to go now

Codecov Report

Merging #4561 into master will increase coverage by <.01%.
The diff coverage is 89.47%.

@@            Coverage Diff             @@
##           master    #4561      +/-   ##
==========================================
+ Coverage   87.04%   87.04%   +<.01%
==========================================
  Files         349      349
  Lines       65677    65691      +14
  Branches    10190    10191       +1
==========================================
+ Hits        57169    57182      +13
- Misses       5628     5629       +1
  Partials     2880     2880

Rebased, comments, addressed, and fixed a couple unnecessary general FFT -> RFFT uses

appveyor is not happy

Latest commit should make CIs happy, and it fixes a bug in our multitaper PSD computations having to do with DC and Nyquist terms.

thx @larsoner


Feature Request: Indeterminate Progress Bars

Hi Will
first - absolutely great library! Really makes working in the CLI a joy.
One thing I was missing are progress bars that do not show a progress, but are basically a waiting indicator (Example). I was able to build a version of it by having the bar go to 99% and then reverse back in a loop. Ideally, however, the progress bar would move, i.e. the startValue would change together with the endValue and the completed part would stay the same width.

Hi,
Glad you like Rich.  I've had some thoughts along those lines myself. I'll consider it for a future update...

Made some progress...

Looks smoother than in the gif.

That future update came early!
Wonderful, that's exactly what I was looking for. Is the gradient automatically based on the selected color for the bar?

Wonderful, that's exactly what I was looking for. Is the gradient automatically based on the selected color for the bar?

Yep.
It's in master if you would like to play with it. progress -m rich.progress now displays an indeterminate bar.

I just tried it - it is great. However, for me it was kind of difficult to see the bar (especially when using a shorter width, e.g. 40). I had a pulse_style = 'cyan' It became easier once I changed the style color to white.

Can you send me a screenshot? Mine is dark and I find it quite clear.

What is the intended way of stopping an indeterminate bar?

The intermediate bar shows when the task hasn't been 'started', to handle the common case where there is a delay in getting the number of steps. You could go direct from an intermediate bar to a 0% bar by calling stop_task. Added some docs

indeterminate bars are in v1.2.3

Nothing dramatic, and everyone is able to change it themselves anyway.


Visual artifacts / lag when resizing window

I'm running the latest iced examples on Ubuntu 20.04, and when I'm resizing the window, the framerate drops below 60 fps (it's visually distinguishable, sometimes visual artifacts - black bars - appear in the portions of the window that couldn't update in time).
This doesn't seem like a big issue, however, I'd like to know if it can be dealt with.
Is there a way to work around it, or solve it in the app implementation?
Is there a way to solve this on the iced side?

Do you run in release mode? (cargo run --release)


[BUG] Font MatrixChunky6.ttf is missing 1 glyph error

Bug report
Describe the bug
Installing the default install/ulanzi-easy.yaml file results in "missing glyph" error:
Failed config

font: [source /config/esphome/ulanzi-easy.yaml:79]

  Font MatrixChunky6.ttf is missing 1 glyph:

   (b'\\n').
  - file: MatrixChunky6.ttf
    id: px6_font
    size: 6
    glyphs: |-
      ! "#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz°

Additional information

used Hardware:

ESP32
EspHoMaTriXv2 version: 2024.12.0

To Reproduce

Deploy fresh install/ulanzi-easy.yaml file
Run install

Expected behavior
Should compile fine.
Fix:
Turns out the base config syntax seems invalid and can be fixed on line 82 with:
     size: 6
-    glyphs:  |
+    glyphs:  |-
       ! "#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz°

Yeah, it's an ESPHome change.
Came up last week, some discussion: https://github.com/lubeda/EspHoMaTriXv2/issues/254
...need the - to avoid adding a new line.


dotnet-provider

Enhancement for .Net provider for analyzer lsp

@djzager would you like to keep this open for further changes, or do you think its close to state we can merge?
I see @shawn-hurley had a suggestion to consider, not sure if it's been addressed yet.

I think it should stay open so that we can modify/update it if it's something we want to target for release-0.4.


filenames starting with ./ or a number don't work as expected

Setup
entangled --version 1.2.4
entangle daemon running on folder
Working test (file block with identifer)
Contents of working source code foo.md
This is a small script
``` {.python #bar file=./src/bar.py}
Hello there!
```
Resulting target bar.py
# ~~ language=Python filename=./src/bar.py
# ~~ begin <<lit/foo.md|bar>>[0]
Hello there!
# ~~ end
Result: If any of above files is modified, the corresponding is updated.
Not working test (file block without identifer)
Contents of NOT (no identifier) working source code foo.md
This is a small script
``` {.python #bar file=./src/bar.py}
Hello there!
```
Resulting target bar.py
# ~~ language=Python filename=./src/bar.py
# ~~ begin <<lit/foo.md|./src/bar.py>>[0]
Hello there!
# ~~ end
Result: bar.py is updated  when foo.md modified, but foo.md is not updated when bar.py is modified.

Thanks for your bug report; I'm a bit confused though, in both instances your input script is the same? How did you get the resulting target bar.py in the second instance?

Thanks for your quick reply. Sorry, the report was incorrect; I didn't copy the relevant one. I've update the foo.md (basically without the block identifier)

Please finethe daemon output here
[error] stitching: src/bar.py:2:1:
|
2 | "# ~\~ begin <<lit/foo.md|./src/bar.py>>[0]"
| ^
unexpected "# ~\~ begin <<lit/foo.md|./src/bar.py>>[0]" :| []
• [14:02:51] tangling after stitch src/bar.py
• Writing './src/bar.py'

Ok, it seems I never tested filenames starting with ./. Without the dot-slash in front your example should work fine. I will have to fix this though.

A related error: when switching between directories prefixed with ./ or not entangled doesn't recognize that they're the same.

Yes! Thank you.

on a related note, if the path contains a dot it produces a similar error.
Output of entangled daemon:
❯ entangled daemon
entangled:
Error: Invalid input

(input):1:56:
  |
1 | (/home/charlie/JD/30-39 resources/34 sharpen the saw/34.03 scripts/entangled.dhall).entangled.version
  |                                                        ^
unexpected '.'
expecting "@", "→", "∧", "≡", "⩓", "⫽", ), ->, //, //\\, /\, :, ===, operator, or whitespace


Executing AQL using java driver on an index returns null

Hi,
I am using the Java driver 4.0.0 and DB version 3.1. When I try to query, using FILTER on any of the index, the ArangoCursor returns with a  null element. Tried using Vpack and POJO. Neither of them work.

duplicate of https://github.com/arangodb/arangodb-java-driver/issues/66


Bump the version to 0.9.0

The release notes are available in #178 and will be added to the GitHub release, thank you @saik0 for the notes again!

bors merge


updates for sidecar patches and 3scale version

Signed-off-by: rcernich<EMAIL_ADDRESS>

@knrc, fyi, updates for the sidecar patches and 3scale version update (0.5.0).  Note, updating an Installation results in the same configuration being installed, as the ConfigMap used by the installer does not get update.  I tested with 0.9 and it exhibits the same behavior (fails when trying to create the new ConfigMap).  I left this alone, as it was an existing bug (i.e. not new to the 0.10 operator).

@rcernich Updating the installation has worked in previous releases, how are you reproducing this?


feat: Add useUx4iot convenience hook

This is just syntax sugar, I guess. I feel like most react libraries provide this sort of hook to provide access to internals.
Examples:

formik: useFormik
react-hook-form: useFormContext

It just feels more convenient. We could also just add useContext(Ux4iotContext) to the Readme. Otherwise one has to look through the source code to find the Context Type.
We need this because we want to imperatively send direct messages for many devices...
We've currently come up with something like this after digging through the source:
const ux4iot = await Ux4iot.create(options)
for (const device of devices) {
    await ux4iot.invokeDirectMethod(device.id, ..., ...)
}

Do you have alternative suggestions on how to achieve this (without doing this on the back-end)?

As discussed, we're closing this and try solving this with a new hook.


Guidelines how to autoformat the code

As preparation to transfer slddb to orsopy I have looked into the usage of black and ran it on the project. In the same spirit I found that isort would also be a good addition for us to keep the import section tidy and equivalent for the whole package.
I have therefore added a description how to run this to the contributing section of the documentation. The code is also updated to what it would looks like after running these commands.
One additional thing I changed might need some discussion here. I removed the author comments that have been in several files for the following reasons:

Most files are touched by many of us, so they don't really have an Author in that sense.
We do have author information in a separate file now so that everyone get's the credit they deserve.
The git repository itself is a better indication of who contributed what to the project (and whom to ask about it, potentially)

Any comments are welcome. Black doesn't have any configuration parameters, so we will have to live with the look of the results, but for me the changes mostly looked reasonable.

And please ignore the coverage decrease, that's just the result of the change of the number of lines in the same untested code sequence.

How come the force push is needed?

I'm gonna merge the changes, if we want to modify the test to be complete we can still to it at a later stage.


Error when calling hiding again immediately after showing

I have a loading state that sometimes only exists for a very short time (under one frame as far as I can tell), causing the following exception:
======== Exception caught by widgets library =======================================================
The following assertion was thrown building XXX:
Hide called, but not showing!
'package:declarative_refresh_indicator/declarative_refresh_indicator.dart':
Failed assertion: line 122 pos 12: '_showing'

The relevant error-causing widget was:
  RefreshDataIndicator RefreshDataIndicator:file:///xxx/lib/something.dart:50:12
When the exception was thrown, this was the stack:
#2      _DeclarativeRefreshIndicatorState._hide (package:declarative_refresh_indicator/declarative_refresh_indicator.dart:122:12)
#3      _DeclarativeRefreshIndicatorState.didUpdateWidget (package:declarative_refresh_indicator/declarative_refresh_indicator.dart:149:7)
#4      StatefulElement.update (package:flutter/src/widgets/framework.dart:5142:55)
#5      Element.updateChild (package:flutter/src/widgets/framework.dart:3660:15)
#6      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4993:16)
#7      StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:5133:11)
#8      Element.rebuild (package:flutter/src/widgets/framework.dart:4690:5)
#9      StatefulElement.update (package:flutter/src/widgets/framework.dart:5156:5)
#10     Element.updateChild (package:flutter/src/widgets/framework.dart:3660:15)
#11     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4993:16)
#12     StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:5133:11)
#13     Element.rebuild (package:flutter/src/widgets/framework.dart:4690:5)
#14     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2743:19)
#15     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:863:21)
#16     RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:381:5)
#17     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1289:15)
#18     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1218:9)
#19     SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:1076:5)
#20     _invoke (dart:ui/hooks.dart:145:13)
#21     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:338:5)
#22     _drawFrame (dart:ui/hooks.dart:112:31)
(elided 2 frames from class _AssertionError)
====================================================================================================

I think this is caused by _hide() being executed before the asynchronously called _onRefresh() can set the completer.

#2 seems to fix this bug

Are you calling setState in initState? If so, this should not be done. If not, are you able to provide a minimal reproduction of the issue?

No, I'm using this together with riverpod. I refresh a provider when clicking a button and provide refreshing: ref.watch(dataProvider).isLoading to the DeclarativeRefreshIndicator.
It is possible that the refresh is very fast (under 1ms) and therefore that the future completes before the next frame.


Should Opower work for all Evergy customers?

I was pleased to see my provider Evergy in the list of supported providers, but even though I have authenticated with my Evergy details no power consumption has appeared. Evergy was formed by the merger of Westar with Kansas Power and Light - I’m a former Westar customer. Should this integration work for me, or does it only work for the former Kansas Power and Light customers?
When it was Westar I was able to download data about my consumption in the ‘Blue Button’ format, but that feature was removed post merger and I’ve not found a way to view/analyze my data on anything less than a week/day, wherea previously I could see it for every 15 mins of the day.
many thanks,
ourstanley

No idea. Try it by running the following:
pip install opower
python -m opower

OK, so after posting this I realized that as well as installing the integration and authenticating to Evergy that I needed to define some entities. So I did that and I seem now to be seeing data -

I’ll monitor this and see how it changes over time. Doesn’t look like I’ll get the consumption by time of day view that came with the Blue Button data, but it might still be useful.

Read the documentation. You need to add the statistics to the energy dashboard. Not these sensors.


Add optional retainLineSeparators argument.

also switches to AVA and xo

Just curious, what do you need this for?

Could you remove these lines as well?

16 comments in 9 minutes. On a project that hasn't seen an update in almost 2 years.
LOL.

s/LOL/Awesome/! 😀

It's important that if someone does improvements to a module, everything is covered at once :).

OK! Should be done!

Just curious, what do you need this for?

https://github.com/sindresorhus/refined-github/pull/195

Some extra improvements

Remove .jshintrc
Remove iosjs in .travis.yml and add 6 and 4

@SamVerschueren I'll do it when merging ;)

d090205 already has @SamVerschueren suggested fix

Nice work @jamestalmage !

Thanks @jamestalmage :)


Lower accuracy with version 6

Hello,
Version 6 of flutter-geolocator gets lower accuracy than version 5.3 in all my test devices.
I'm using
desiredAccuracy: LocationAccuracy.best
distanceFilter: 10
Never goes down 65 meters of precision on a iPhone 6, 411 meters on an iPhone11 (most common value 1414 m.), 16 meters on a Samsung A50. Previous version was < 15 m. in all the phones.

I'm having simular issues

@FrancisRuiz, @vicenterusso , thank you for reporting this issue, I will be looking into this. Just a few questions that might help me out to get started:

Are you testing on iOS 14 or also other versions ( I believe iPhone 6 doesn't support anything higher then iOS 12.4.8, but just wanted to make sure)?
Have you tried if this could be related to the distanceFilter (e.g. have you tried setting it to 0)? If not could you give it a try?

Hello,
I hace tested on both IOS 13.7 on an iphone 6 and IOS 14 on an iphone 11
with similar results. I will check with different distance filters but I
think I tried with zero meters.
Thank you,
Francis
El El mar, 29 sept 2020 a las 13:09, Maurits van Beusekom <
<EMAIL_ADDRESS>escribió:

@FrancisRuiz https://github.com/FrancisRuiz, @vicenterusso
https://github.com/vicenterusso , thank you for reporting this issue, I
will be looking into this. Just a few questions that might help me out to
get started:

Are you testing on iOS 14 or also other versions ( I believe iPhone
6 doesn't support anything higher then iOS 12.4.8, but just wanted to make
sure)?

Have you tried if this could be related to the distanceFilter (e.g.
have you tried setting it to 0)? If not could you give it a try?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Baseflow/flutter-geolocator/issues/531#issuecomment-700659881,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPLM7NAZS5QIAFU7J7W3BTSIHE75ANCNFSM4RZH7GHA
.

Same problem here, my tests was on iPhone X and iPhone 11, iOS 13 and 14.
Using Flutter 1.20 and 1.22 and Geolocator 6.x.x

Hello,
Version 6 of flutter-geolocator gets lower accuracy than version 5.3 in all my test devices.
I'm using
desiredAccuracy: LocationAccuracy.best
distanceFilter: 10
Never goes down 65 meters of precision on a iPhone 6, 411 meters on an iPhone11 (most common value 1414 m.), 16 meters on a Samsung A50. Previous version was < 15 m. in all the phones.

i'a

I got also a very low accuracy in my real device "Huawei honor 8x" even though I used  desiredAccuracy: LocationAccuracy.bestForNavigation   and the distance I got between my real position and what geolocation gave me is about [450-460] meters, I hope you fix this issue as soon as possible (geolocator: ^6.1.0 used )

I have located a bug in the where the accuracy parameter is send in the wrong format from Dart to the native iOS implementation. I have solved this in version 6.1.3 of the geolocator.

Nice! I will test it on Monday. Thank you very much.
El El vie, 30 oct 2020 a las 17:52, Maurits van Beusekom <
<EMAIL_ADDRESS>escribió:

I have located a bug in the where the accuracy parameter is send in the
wrong format from Dart to the native iOS implementation. I have solved this
in version 6.1.3 of the geolocator.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Baseflow/flutter-geolocator/issues/531#issuecomment-719704840,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPLM7NFCERPVP4ZQF4H2PTSNL4PRANCNFSM4RZH7GHA
.

Hi @FrancisRuiz, did you have a change to test it out? I am curious about your findings.

Hello Maurits,
It’s working fine now. No issue found around accuracy at iphone 6, iphone
XS, Samsung A50, and a very old huawey.
Good job and thank you very much.
Francis
El El mié, 11 nov 2020 a las 11:28, Maurits van Beusekom <
<EMAIL_ADDRESS>escribió:

Hi @FrancisRuiz https://github.com/FrancisRuiz, did you have a change
to test it out? I am curious about your findings.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Baseflow/flutter-geolocator/issues/531#issuecomment-725370091,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPLM7OZ57CDCT7KZMSFTGTSPJYODANCNFSM4RZH7GHA
.

That is great news, thank you for testing and taking the time to let us know.


Feature lc 332 inactive to active

Just adding a comment about what we discussed yesterday.
please change the call to check if token person to use the identity service iswhitelisted endpoint.
this has now been done


Docs outdated?

The docs on http://ncollide.org/ seem to be outdated. For example, there seems to be no GeomGeomDispatcher in the project, while the docs clearly mention it here: http://ncollide.org/contact_determination/narrow_phase.html

Yes, the hand-written documentation is very outdated, I did not have the time to update it since the last major change of ncollide's infrastructure. The core mathematical concepts remain the same but the types and/or their type parameters changed a lot since then.
The cargo-generated doc is up-to-date (but a bit incomplete), though : http://ncollide.org/doc/ncollide/

Are there any examples anywhere that can replace the hand-written documentation for the time being?

Well unfortunately all the existing examples are those from the documentation and are outdated as well. You will find them all there. Though I am almost done updating nrays to the latest version of rust, so I should be able to start fixing ncollide-related documentation soon. I will use this thread to give updates about my progress on updating the docs.
In the mean time, you can dig into nrays or nphysics. However they both use advanced features of ncollide so they might not be of much help if you need something concise about one specific feature.
You may also open "issues" like #88 . In the future I might just end up creating a forum for this kind of queries.

I think I'll wait for the time being, fortunately I can work on other sides of the game engine before I implement collision detection.
As a note, it might be useful to add a note on the website that the docs are outdated, I spent quite some time trying to figure out if I was dumb, the generated rustdoc was broken, or the examples were out of date, then I found this issue :panda_face:

Are the user docs version controlled anywhere? I'm sure myself and others would be happy to submit pull requests to keep them updated if we find they're out of date or lacking in a particular area.

Yes, the documentation (written in markdown) is versioned on the gh-pages branch in this repository. Also, the corresponding web pages are generated using GitBook. Contributions are very welcome !

Closing this in favor of #93.


JBEHAVE-1320 Expand DelegatingStepMonitor to accept collection of delegates

The changes have been added to master branch: 2614f6e5b55aa83be1c93de6356e1c4028179125


Remove access to extenal website for Discover NFT and Crypto

it is not used and we cannot maintain the website

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

@HugoNDO what do we do with the empty space?


Plugin returns error: gzip: stdin: not in gzip format

Since this morning our builds are failing. The tar.gz seems not to exist?
Downloading and installing helm-mapkubeapis v0.4.1 ...
https://github.com/helm/helm-mapkubeapis/releases/download/v0.4.1/helm-mapkubeapis_0.4.1_linux_amd64.tar.gz
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Error: plugin install hook for "mapkubeapis" exited with error
We install the plugin via:
helm plugin install https://github.com/helm/helm-mapkubeapis

Its only being built. Wait until its available.

Its should be available now.

That was it indeed, builds are working again! Thanks!


Increasing IMU hz to 1000

Hi,
By decreasing the delay from 20ms to 1, I am able to receive the IMU data at about 123hz, Is it possible to increase the IMU output rate to 1khz?
Regards,

hello,  were you able to do it? I want he same thing


The table "issue"

A very useful piece of code to combine the power of tabulary (self-adjusting column width with LCR instead of lcr) and longtable: https://tex.stackexchange.com/a/197808
Then, from I understand, we will need a \tableCell macro, that may take as a parameter the colspan and rowspan (and translate into \multicolumn and \multirow if needed), to be close to the traditional HTML syntax.
To protect table, instead of using minipage (my initial idea), the adjustbox package seems more promising to include arbitrary environement (like, for example, lists, code or other things). The idea being to embed it in the previous command.

I’m working on it. The most difficult thing is the code management. If someone has a killer idea...

At which level ?

We're ready on our side. Keep us posted on your progress here :)

At which level ?

We can’t use minted in an array. verbatim can’t be used in tabu, longtable, etc. (but it can be used in tabu*).

We're ready on our side. Keep us posted on your progress here :)

I don’t have really usable code. Could a first iteration use \multicolumn and \multirow ?

We can’t use minted in an array. verbatim can’t be used in tabu, longtable, etc. (but it can be used in tabu*).

Even in minipage or adjustbox ?

Even in minipage or adjustbox ?

Nope, see that https://tex.stackexchange.com/questions/119842/how-to-use-fancyvrb-verbatim-in-tabularx

Oh. I thought about that and my conclusion was that length_of_text/number_of_column - 2*margin_of_tabular was a "good" width, since we cannot know in advance the width. But I didn't check if it was possible to get the number of column easily.

Here informations about arrays packages (french).

Any news?

In a PM (MP), @artragis told us that he was working on something :-°

By the way, @artragis, were you able to fix all of those issues on rebber side with the command already provided?

yep, in rebber, when you have code inside a table, we move the code.

Ok, nice. I will do some tests in the future :)

Ok, I think we are good here (still need to think about #93, though)


Make BPF optional again

What type of PR is this?
/kind feature

What this PR does / why we need it:
Some distributions insist on building from distribution packages only.
This means we can't use the built-in BPF recorder at least not on
RHEL/CentOS until all the needed package versions catch up.
This patch re-adds the no_bpf build tag triggered by the BPF_ENABLED
environment variable if set to 0. A developer can then build SPO without the
built-in BPF support by running:
BPF_ENABLED=0 make
Which issue(s) this PR fixes:
None

Does this PR have test?
implicitly tested by UBI build

Special notes for your reviewer:
@saschagrunert - I used your fork of libbpfgo that supports the
nobpf build tag. I'm unsure if this is a good thing long-term,
in general forks are not. Have you considered sending the patches
upstream to see if they'd accept them? Or can you think about
a better solution?
Does this PR introduce a user-facing change?

This patch re-adds the no_bpf build tag triggered by the BPF_ENABLED=0 tag
environment variable if set to 0. A developer can then build SPO without the
built-in BPF support by running:
    BPF_ENABLED=0 make
This is useful to build SPO in environments with older dependencies
that don't allow building the in-tree BPF-based recorder.

/test pull-security-profiles-operator-verify

/retest

/override pull-security-profiles-operator-verify

/retest-required

The only test that fails is the kubectl run one:
 I1129 15:28:13.452171   51132 suite_test.go:529]  "msg"="Creating bpf recording for kubectl run test"
profilerecording.security-profiles-operator.x-k8s.io/test-recording created
I1129 15:28:13.858298   51132 suite_test.go:529]  "msg"="Creating test pod"
pod "fedora" deleted
I1129 15:28:18.850526   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (0)"
I1129 15:28:22.184743   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (1)"
I1129 15:28:25.419408   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (2)"
I1129 15:28:28.605808   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (3)"
I1129 15:28:31.763879   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (4)"
I1129 15:28:35.041517   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (5)"
I1129 15:28:38.180722   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (6)"
I1129 15:28:41.409464   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (7)"
I1129 15:28:44.623186   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (8)"
I1129 15:28:47.833437   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (9)"
I1129 15:28:50.968909   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (10)"
I1129 15:28:54.123912   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (11)"
I1129 15:28:57.272136   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (12)"
I1129 15:29:00.450537   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (13)"
I1129 15:29:03.604249   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (14)"
I1129 15:29:06.755145   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (15)"
I1129 15:29:09.904360   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (16)"
I1129 15:29:13.097990   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (17)"
I1129 15:29:16.325007   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (18)"
I1129 15:29:19.466301   51132 suite_test.go:529]  "msg"="Waiting for resource to be available (19)"

I'm seeing the following in the logs:
I1129 21:09:56.550661   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=0
I1129 21:09:56.560416   53063 bpfrecorder.go:667] bpf-recorder "msg"="Container ID not yet available"  "containerName"="fedora" "podName"="fedora"
I1129 21:09:56.661112   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=1
I1129 21:09:56.673908   53063 bpfrecorder.go:667] bpf-recorder "msg"="Container ID not yet available"  "containerName"="fedora" "podName"="fedora"
I1129 21:09:56.704716   53063 bpfrecorder.go:263] bpf-recorder "msg"="Getting syscalls for profile test-recording-fedora-1638220192"
I1129 21:09:56.704775   53063 bpfrecorder.go:279] bpf-recorder "msg"="Looking up PID for profile"  "profile"="test-recording-fedora-1638220192" "try"=0
I1129 21:09:56.794956   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=2
I1129 21:09:56.949796   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=3
I1129 21:09:57.143503   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=4
I1129 21:09:57.359244   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=5
I1129 21:09:57.615697   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=6
I1129 21:09:57.954607   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=7
I1129 21:09:58.335841   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=8
I1129 21:09:58.774352   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=9
I1129 21:09:59.319122   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=10
I1129 21:09:59.949610   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=11
I1129 21:10:00.700192   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=12
I1129 21:10:01.602133   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=13
I1129 21:10:02.680442   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=14
I1129 21:10:03.971651   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=15
I1129 21:10:05.522107   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=16
I1129 21:10:07.377134   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=17
I1129 21:10:09.606516   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=18
I1129 21:10:12.277181   53063 bpfrecorder.go:650] bpf-recorder "msg"="Looking up in-cluster container ID"  "id"="fd7acefbfc302476ca06a8f262947548a68adb0086ef0e271ac9e86827752f09" "try"=19
E1129 21:10:12.297854   53063 bpfrecorder.go:570] bpf-recorder "msg"="unable to find container ID in cluster" "error"="find container ID: wait on retry: timed out waiting for the condition"
I1129 21:10:12.802427   53063 bpfrecorder.go:279] bpf-recorder "msg"="Looking up PID for profile"  "profile"="test-recording-fedora-1638220192" "try"=1
I1129 21:10:13.553403   53063 bpfrecorder.go:279] bpf-recorder "msg"="Looking up PID for profile"  "profile"="test-recording-fedora-1638220192" "try"=2
I1129 21:10:14.678795   53063 bpfrecorder.go:279] bpf-recorder "msg"="Looking up PID for profile"  "profile"="test-recording-fedora-1638220192" "try"=3
I1129 21:10:16.366575   53063 bpfrecorder.go:279] bpf-recorder "msg"="Looking up PID for profile"  "profile"="test-recording-fedora-1638220192" "try"=4

All in all, I'm tempted to ignore the test failure as it's not related, but I don't dare do it myself on my PR..

No changes, just rebased to trigger tests..which made me lose the lgtm label. I thought GH was smarter. Doh.

/override pull-security-profiles-operator-verify

/retest

/test pull-security-profiles-operator-test-e2e


No stack-trace and direction to file doesn't work

On error I can't see the stack trace and the link to the file doesn't open the file and line. It opens on a new tab, which doesn't work.
https://www.dropbox.com/s/q9zphsr5whmkrpv/Screenshot 2015-06-04 14.12.48.png?dl=0

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/20377693-no-stack-trace-and-direction-to-file-doesn-t-work?utm_campaign=plugin&utm_content=tracker%2F195817&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F195817&utm_medium=issues&utm_source=github).

Fixed in 0.10.2


Update for PowerStig 3.2

Update support for PowerStig 3.2 release.

Completed on PowerStigScan <IP_ADDRESS>


Add Show Ast options for the ASTs we want to show

Searching for Typed Ast will probably tell you where to make changes.

I would like to have it for phases instead of asts. is this okay?

Seems reasonable. Do we just give them the name of the phase?

Maybe just Typer creates TyperAst etc


schema(ticdc): query the primary key column names in an easier way

What problem does this PR solve?

Issue Number: close #11063
What is changed and how it works?

fetch the primary key column information by using tidb table info provided method.
add more unit test case to cover non integer primary key.

Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`

/retest

/cherry-pick release-8.1


Update doc comment to match type Option<Signal>

This has previously been done for killpg, but not kill it seems.

bors r+


fix(errors): log error when it occurs

add an extra error handler for logging
Fixes #37

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Expandable cards

Hi! I have a question.
I want to have cards as items. When ItemView is clicked they sould expand / collapse animated in terms of showing / hiding more inner views.
What would be the best way to achieve that with your great library?
I already tried it the IExpandable and IHeader way but i want to keep all content in the layout (card).
Thanks!

Thank you for that hint! I managed to implement the expand/collapse feature and your setAutoScrollOnExpand(true) feature.
Do you have an idea how to get setAutoCollapseOnExpand(true) functionality working here?
itemView.setOnClickListener(new View.OnClickListener() {
                @Override
                public void onClick(View v) {
                    AutoTransition autoTransition = new AutoTransition();
                    autoTransition.setDuration(100);
                    autoTransition.addListener(new Transition.TransitionListener() {
                        @Override
                        public void onTransitionStart(@NonNull Transition transition) {
                        }

                        @Override
                        public void onTransitionEnd(@NonNull Transition transition) {
                            if (more.getVisibility() == View.VISIBLE) {
                                adapter.smoothScrollToPosition(getFlexibleAdapterPosition());
                            }
                        }

                        @Override
                        public void onTransitionCancel(@NonNull Transition transition) {

                        }

                        @Override
                        public void onTransitionPause(@NonNull Transition transition) {

                        }

                        @Override
                        public void onTransitionResume(@NonNull Transition transition) {

                        }
                    });
                    TransitionManager.beginDelayedTransition((ViewGroup) itemView.getParent(), autoTransition);
                    if (more.getVisibility() == View.VISIBLE) {
                        more.setVisibility(View.GONE);
                    } else {
                        more.setVisibility(View.VISIBLE);
                    }
                }
            });

@10erlosh, itemView already has the click listener set, check what the original implementation is doing in ViewHolder.onClick.
setAutoCollapseOnExpand is for the adapter, it automatically collapse all others items. Check ExpandableViewHolder.


Simplify internal Buffer allocations

Motivation:
There are two concerns addressed here:

The use of UntetheredMemory outside of the pooling allocator was more complexity than was strictly necessary, and also created an awkward API dance where the memory and its drop had to be combined again.
MemoryManager instances may want to create Buffers and their baseline Drop instance together, yet the allocator need to adapt or decorate the drop.

Modification:
Change the ensureWritable implementations to no longer rely on UntetheredMemory, but instead allocate a new Buffer instance and cannibalise its insides.
Move the UntetheredMemory interface into the buffer/api/pool package.
Remove the MemoryManager.drop method and change the MemoryManager.allocateShared to take an adaptor function.
The memory managers can then create per-Buffer drop instances if they so desire.
Simplify how the PooledBufferAllocator uses AllocatorControl; the PooledAllocatorControl is now just a reference to the parent allocator.
Result:
More general internal APIs and simpler implementation.

Once this is merged, I'll push a matching update to https://github.com/netty/netty-incubator-buffer-api/pull/77


Bench: possibility to pass frontend address using env

What changed?
Providing "expand" option to config library.
Small changes:

Use 5s context for creating bench domains
Stop bench if failed to create bench domain

Why?
This will allow to point to different cadence cluster without changing config files.

How did you test it?

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 01867931-491d-4103-ab4d-e48097ae1308

2 of 5 (40.0%)  changed or added relevant lines in 2 files are covered.
67 unchanged lines in 10 files lost coverage.
Overall coverage increased (+0.07%) to 57.235%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

bench/lib/client.go
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

service/history/queue/transfer_queue_processor_base.go
1
77.62%

common/task/parallelTaskProcessor.go
2
92.75%

common/task/weightedRoundRobinTaskScheduler.go
2
89.64%

service/history/execution/mutable_state_builder.go
2
68.82%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
59.1%

common/task/fifoTaskScheduler.go
4
85.57%

service/history/task/transfer_standby_task_executor.go
4
86.4%

common/persistence/nosql/nosqlplugin/cassandra/workflowParsingUtils.go
14
79.09%

service/history/execution/mutable_state_task_refresher.go
15
62.03%

service/history/task/task_util.go
20
70.57%

Totals

Change from base Build 01867537-d02a-426c-8fc1-b9baf20eb662:
0.07%

Covered Lines:
85133

Relevant Lines:
148743

💛  - Coveralls


[RFC] PEP 526: class member annotations in 3.6

I just played around and got:
>>> import attr

>>> @attr.s
... class C:
...     x: int
...     y: int = attr.ib(default=42)

>>> C(1)
C(x=1, y=42)

>>> C("1", 23)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<attrs generated init<PHONE_NUMBER>47d4e148358419a9dd355e479f9105>", line 5, in __init__
    __attr_validator_x(self, __attr_x, self.x)
  File "/Users/hynek/Projects/attrs/src/attr/validators.py", line 33, in __call__
    attr, self.type, value,
TypeError: ("'x' must be <class 'int'> (got '1' that is a <class 'str'>).", Attribute(name='x', default=NOTHING, validator=<instance_of validator for type <class 'int'>>, repr=True, cmp=True, hash=None, init=True, convert=None, metadata=mappingproxy({})), <class 'int'>, '1')
("'x' must be <class 'int'> (got '1' that is a <class 'str'>).", Attribute(name='x', default=NOTHING, validator=<instance_of validator for type <class 'int'>>, repr=True, cmp=True, hash=None, init=True, convert=None, metadata=mappingproxy({})), <class 'int'>, '1')

working within five minutes (biggest “challenge” was to ignore the counter on _CountingAttr).
I think this is really neat because it saves us from fiddling with the class body and makes much more sense conceptually.

Now, obviously we can’t just start harvesting class annotations, we need an option or even a new decorator.
I also see this as a chance to get rid of the slots/non-slots dichotomy that fell a few times on our feet and always go the slots way (= create new class).
So I hereby ask for:

feedback/opinions
suggestions for decorator/option name
other warts we could fix while doing this

Over on https://github.com/ericvsmith/dataclasses/issues/19 Guido made a very good point; if we want the type checker to work, the type field needs to have nothing but a type in it.  So: x: int, but y = attr.ib(); possibly y: int = attr.ib().

(thanks, I’ve updated the comment so people don’t see the wrong version first thing)

Cool! I take it you got that working as well, without issue :)

y: int = attr.ib() doesn't work well with pylint (pylint will use the type of ib not int). For the common use case of setting a default I would like something like:
>>> import attr

>>> @attr.s
... class C:
...     x: int
...     y: int = 42

>>> C(1)
C(x=1, y=42)

y: int = attr.ib() doesn't work well with pylint (pylint will use the type of ib not int).

IMHO the solution here is to fix pylint; it's just doing the wrong thing.  This idea of defaults = cvars seems like a good idea until (as the participants in the dataclasses repo did) you realize that you will almost immediately want

x: list = []

and now nothing makes sense any more.  If you do

x: list = new(list)

it's still the wrong type.

FTR, I consider #215 a prerequisite for working on this.  In the end, this is just syntactic sugar for it.

PEP 526 support has been merged in #239!


Consideratrion for not using filesize when generating filekeys (or, sorta-more-permanent-links)

Currently, from what I can tell, filekeys are generated using salt, fspath, fsize, and inode. They are also regenerated on file edit (?).
What this means is that if a text file is edited, the filekey is regenerated, and any links to it break permanently.
Now, this may be intentional as a "if I edit this file/delete it and upload a new unrelated one with the same name, link breaks", but it would be cool if links to files remained 'more-static' until the file is deleted/moved.
Use cases:

I send notes to people, kinda like a pastebin, then edit the note cause I e.g. missed a word and now have to re-send because the link they already opened is now broken. Wish I could just say "oh ops refresh I updated it"
I cannot have a nice <a href="path/to/shopping.md">🛒 Shopping List </a> quicklink in my README.md
because the file key changes every time I edit the file...

Perhaps instead of filesize, file creation timestamp or something can be used? (to prevent irrelevant re-uploads from having the same key). Or perhaps always generate a new filekey with size like normal, just don't regen if existing file is edited (idk how the code works to know if this is feasible).

hey o/
yep you're right; that's how the filekeys are generated, and it was also intentional that they would be replaced if the file contents are modified, since you might forget sharing the link some time down the road and then edit the file, adding something that was not intended to be public. Not saying this was necessarily the best choice however :>
but I'm wondering if filekeys may be just an inconvenience for this purpose, and you'd be better off with a separate volume that just has directory listing disabled, and not enabling filekeys for that volume? maybe with a bit more unique filenames for any files you don't want bruteforced?
thinking about it more -- since part of the filekeys are the salt, they wouldn't be completely pointless if we were to remove the filesize and lastmodified... but it would remove the benefit of automatically generating a new key if the file is deleted and re-uploaded, like you mentioned. It should be possible to add this as an option however, if this is preferable in some scenarios.
the alternative filekey type would probably be just salt and filename, since not all filesystems support the file-creation timestamp, and because it would also  recreate the filekey if you were to copy the same files into a public folder twice.
and i guess another alternative would be to generate a truly random key when a file is indexed, storing it in the db, and delete it from the db when the file is deleted -- but that would result in more database activity when listing files, reducing performance, so I'd like to avoid that if possible. Unless there's a reason to consider this of course!
so maybe just add an option to make the filekey only care about filename and salt, and default to the old filekey type since that's safer?

I'd like to add my thoughts to this conversation. Please track them as alternative point of view:

you might forget sharing the link some time down the road and then edit the file, adding something that was not intended to be public

Regenerating filekeys to solve this problem looks to me as not the best solution: making a choice on the system background instead of the user is always a bad idea, as it creates surprisingly unexpectable behavior of the system for the user: if he\she might forget about the sharing, the same could happen in opposite. Yes, it is safer, but much better to ask the user at the file update time whether the sharing has to be removed or not. There are cases of non-interactive file updates (by some software on the host system) - here I'd say that the user has to own all the responsibility of sharing such files, so if the decision was made by the user to share, the system has to respect that and follow it.

the alternative filekey type would probably be just salt and filename, since not all filesystems support the file-creation timestamp

When I design some software solution, I try to follow a general rule to not re-invent a bicycle and not re-implement the logic or the implementation of dependencies or integrations while it doesn't bring significant restrictions or limitations into the designed solution. In this particular case, a file is an object of a filesystem. All filesystems, used in commonly used OSs are well-tested and maintained, which means that all solutions, built on top of them should rely on the FS logic and use its interfaces. So, as FS addresses a file by the file descriptor, file path (full or relative), we need to follow the same logic and use these keys to build a filekey. It is better to rely on the file descriptor, as it is unique for each file on the volume even if it is updated, moved, or renamed.

Thanks for your input kkovaletp :>
just to explain the issue for anyone else who might be interested -- we're talking about the per-file access-keys / "passwords" (automatically generated) which can be enabled as an optional feature per-volume. While the g (get) access permission disables directory listings and makes it impossible to see what files exist in a folder, the filekeys feature further enhances this by making URLs to files 404 unless you append the correct filekey (passphrase) to the URL, making it harder to bruteforce-guess filenames in a folder. A practical example is available. Trusted users with the r (read) access permission are able to list directory contents, and also see the valid filekeys of that volume, for sharing with someone who only has the g (get) permission.

much better to ask the user at the file update time whether the sharing has to be removed or not

this speaks in favor of tracking the filekeys in the database, with the resulting performance impact that would have, and also a fair amount of work to extend the APIs with functionality to selectively keep or update an existing filekey... so I'd still prefer to avoid this if possible.

It is better to rely on the file descriptor, as it is unique for each file on the volume even if it is updated, moved, or renamed

true, this would have been a good approach, but there are two reasons we'll have to pick something else for our purpose:

ntfs unfortunately uses FileID instead of inode numbers, which are less trivially accessible, causing too much of a performance hit --

and more importantly, copyparty's textfile editor does not update files in-place, but it instead deletes the file with the old contents and then creates a new file with the updated text. This is because copyparty also supports deduplicating files by hardlinking them, which would cause any implace file edits to also affect the deduplicated copies.

path/name - moving or renaming the file breaks links immediately, but editing does not
just name - moving ('organizing') the file does not break links, but renaming it does

oh neat, I didn't consider using just the filename. This might be fine now that the salt is 18 bytes large, rather than the measly 4 bytes until v1.7.6, but then it would be a great idea to add a warning on startup if you're using an insufficiently large seed to make that a safe setup.
So that sounds like a plan -- keep the current filekey calculation default, but add one or two alternatives -- one would be using just the filename and salt, and possibly a second which uses the full path instead :+1:

Thanks a lot for the clear and detailed description. Now it is more clear to me.
However, from the user's perspective, the logic of re-generation of the filekey in the background every time the file is modified looks not intuitive: if I, as an owner of a file share, configure guest access and provide some URL to the file to someone, I don't expect it to break after the file modification - other file sharing software does not behave like this.

copyparty's textfile editor does not update files in-place, but it instead deletes the file with the old contents and then creates a new file with the updated text

And this is 1 more surprise for me. I didn't use that editor before and I don't rely on file descriptors or creation time now for files on my shared volume, but I see some cases, where such unexpected file re-creation would have a negative impact on other software or data consistency policy. For me (and I guess, for most users) editing doesn't mean recreation. But this is not the topic of this thread anyway...

So that sounds like a plan -- keep the current filekey calculation default, but add one or two alternatives -- one would be using just the filename and salt, and possibly a second which uses the full path instead 👍

I like that :)
A small note - if you use just salt+name for the key, would any two files with the same name have the same key, right? I don't know if it's used as a seed for an rng generator, and then every file pulls a new key from it, or if it's just hashed or something.
cause so if somebody uploads an empty password.txt anywhere
sees the key for it
and now goes around trying to access that file in random folders
bad times

yeeeah that's exactly what would happen :p
there really is no winning here huh...
so maybe we should only provide filesystem-path as an option, and not offer using just the filename at all to avoid any accidents like that? or could there still be a usecase for doing just the filename, maybe with an appropriate warning in the --help?

oh eheh
Yeah, I think that at least using path+name is better. It breaks when you move the file, sure, but at least it doesn't break if you edit a typo or your shopping list, so that's already an improvement. And all password.txt's won't have the same key.
As for name-only - considering how easy it was to figure out to do that, and considering that ppl tend to miss help warnings - probably good idea to hold off on that until somebody goes "hey I really really want this and I have a good case for it pls"?

this has been added to v1.9.8; all of the following are equivalent:

-v /mnt/nas:nas:g:c,fk,fka
-v /mnt/nas:nas:g:c,fka
-v /mnt/nas:nas:g:c,fk=4,fka
-v /mnt/nas:nas:g:c,fka=4

the default filekey generator uses the old approach (salt+filepath+filesize+inode), and there's a new warning on startup if the salt is considered too weak to be safe.
seems to work, but let me know if something doesn't work as expected :+1:

Just tried it, all works great - thank you so much !!


Major additions to the HoTT library

This pull requests adds:

truncated 2-quotients
groupoid quotients
Eilenberg MacLane spaces K(G,n) (no proof of uniqueness of such spaces yet)
Chain complexes
The long exact sequence of homotopy groups
The Freudenthal Suspension Theorem
Whitehead's principle
The computation of homotopy groups of almost all spheres which are known in HoTT. (Only Guillaume's proof of π₄(S²) is missing (but that has also not been formalized anywhere else yet).

Also various changes and fixes to the HoTT library.
@avigad: I added the induction principle for image, so if you have v : image f b you can use the tactic induction v with a p to get a : A and p : f(a) = b (as long as you're proving a mere proposition).

Added a commit which updates book.md


Error: failed to compress TLS assets: NotFoundException: Invalid arn

Following steps here https://coreos.com/kubernetes/docs/latest/kubernetes-on-aws-render.html
I got:
Error: failed to compress TLS assets: NotFoundException: Invalid arn
	status code: 400, request id:

kube-aws version v0.8.2

Aplogies for the dumb questions, but:

Did you create the KMS key?
Since this is a 4xx error, did you create it in the correct region?
Did you swap out the ARN code in this section?

I got back to this today and got it working, not sure was the problem was. Thanks


Sets Window Issue when Extended Transmog Sets is also loaded

With both EST and MPS loaded at the same time, no mattter how long I've been logged in/transmog window is open, there is visual wierdness happening. Please see https://drive.google.com/file/d/1_SU6-w7_ZQydA2DtBWWbRzX2-s1pHHO-/view?usp=sharing for reference.

Hi, which addon is "EST"?

Sorry, that should have been ETS (Extended Transmog Sets)

It should be fixed in 2.1.2, thanks for the report.
I can't guarantee these 2 addons will work 100% well together though 🙂


Clean up debug output

fetchsep_prep_obs generates a tremendous amount of detailed output that makes it difficult to understand what the code has done.  Most of it seems to be details that were used to debug issues during development, and can hopefully be removed now, or optionally enabled with a --debug argument.
For example, when running from a clean state with the default configuration using
python bin/fetchsep_prepare_obs --Experiment GOES --FluxType integral --StartDate 2023-01-01 --EndDate 2023-09-01 2>&1|tee fetchsep.log
The resulting fetchsep.log contained 21708 lines for processing 19 SEPs.  Some of the more tiresome lines are:
There is a data gap for time...  (6088 lines)
ndates: 12167, i: 3190
The first good value previous to gap is on 2023-01-24 17:20:00 with value 0.6361699104309082
The first good value after to gap is on 2023-01-24 17:30:00 with value 0.6214172840118408
Filling gap at time 2023-01-24 17:25:00 with interpolated flux 0.6287935972213745

(3648 blocks)

Noted. The identified "tiresome" lines were kept for traceability. In those places, the OpSEP code filled in missing data values with interpolated values with the idea that this would lead to an improved fluence estimate. Because those were not the original input data, they are recorded in the output. There could be a better way to track these changes/decisions made by the code.


etcd watch can miss changes

This applies to, at least, etcd backends. I'm not familiar enough with other use-cases to comment on them - at a cursory glance it seems that some might be okay.
The core of the issue is that a watch triggers a fetch/update sequence, after which a watch is reestablished at the "current" index. If - for any reason - the fetch/update sequence fails, the error is simply logged via the errChan. The lastIndex has already been incremented here, but that doesn't matter because the new watch always establishes with index 0 - that is to say, "the current index, whatever that may be". So the change that was previously picked up and failed is never applied, and the new watch skips right past it.
I have actively observed this happening. It's easy to repro, too - just randomly return an error inside template.process() and change your key a few times. confd will miss changes that error out.
There's actually another issue related to this. Any changes that happen between the first watch firing and the second watch being established are completely missed (again, due to the fact that the watch is established at "0"). There's a gap in time that isn't accounted for due to not using the correct index.
I hope I'm misunderstanding something, because it seems to make the watch very liable to miss changes. A tiny network blip when fetching from etcd, or a filesystem that takes too long to respond can cause it to get out of sync.
Let me know if I need to be more clear or provide examples!

I'm creating a new implementation for etcdv3. It uses the etcd revision for waitIndex. The watch request is always processing in the background, and the latest revision seen from watch responses are stored. When WatchPrefix is called, the latest revision is checked against the waitIndex to determine whether there are changes after last call. If the latest revision is not changed, the call waits until it is updated. Multiple resources with the same prefix shares the same watch.
When process() fails (template executing failed, check failed, reload failed), I think it should be OK to ignore this revision because we do not have other choices. We cannot afford to retry this revision until it succeeds because there may be errors in templates or stored values. The template will always be processed again when stored values are updated later.
For temporary failures in template processing like DNS lookup, maybe we can add an optional parameter to the template resource to allow it retry for some times, but it should be another issue.

And I'm making some changes in the new implementation:

The new implementation creates watches on each key specified instead of the prefix (usually '/'). When auth is enabled in etcd, it is not always possible to watch the common prefix of all keys. Also this helps reducing received events.
I'm planing to use Txn request in GetValues to retrieve all keys together. This ensures all values are from the same revision, so when multiple keys are changed together (e.g. del --prefix), we always get them all or none.

@trystanj @okushchenko want some opinions.

@trystanj thanks for reporting an issue! Restart with index 0 is definitely a bug and should be easily fixed.
Missed updates are a bigger issue though. If the waitIndex can be used to fix it for Etcd and Consul, other backends, e.g. Zookeeper have no such mechanism. I have a couple of ideas on how it can be addressed, will update the PR #568 in the context of this issue.


feat(build): bump min go version to 1.14

This PR moves us up to node 14 to support the new v18 of semantic-release.

I've added an additional commit to bump up our min supported go version to 1.14.
This is needed because a few of our dependencies require a go version newer than 1.12 (our previous min version).


How can i write text at the panel

can you let me now how to write text into the panel

Use the Adafruit GFX library...
https://github.com/adafruit/Adafruit-GFX-Library

@DarrylStrong  could you please post an example .....

https://github.com/mrfaptastic/ESP32-HUB75-MatrixPanel-DMA/blob/master/examples/1_SimpleTestShapes/1_SimpleTestShapes.ino


Ab#1870 add user client roles

Please update and test the UMC? Or is that a different task.

UMC Changes added


Add gotpm read pcr.

Adds new command and subcommands for read and read pcr.
Adds misc.go to store oddball wrappers for commands like tpm2.ReadPCRs.

Two quick things,

Rebase this onto master (to get rid of the conflict)
Can you make it so that if no --pcrs flag is provided, we just read them all?

Can you make it so that if no --pcrs flag is provided, we just read them all?
(In the future it's probably easier to have changes be threaded conversations or whatever github calls them, so we can make sure everything is resolved)

I've done this (and I think it improves usability), but I'm a little weary, since this leads to inconsistent defaults for flags.


[macOS, 3.x] Workaround Xcode 15 linker bug.

Same as https://github.com/godotengine/godot/pull/81968 for 3.x

Thanks!

Cherry-picked for 3.5.3.


Add option includeEmptyRows, defaults to false #120

Coverage remained the same at 100.0% when pulling 15d8f60094b407f8f9ee1b179df28fc565ec0851 on glutentag:include_empty_rows into afce53cb337a272c59fa710ddb14a259a97411ff on zemirco:master.

Coverage remained the same at 100.0% when pulling 70da97447bfb3cbbdd7d33c25f4903c3f27daee2 on glutentag:include_empty_rows into afce53cb337a272c59fa710ddb14a259a97411ff on zemirco:master.

Beautiful

Released as 3.5.0


Add create option

Add create option to determine, whether to create a vpc or not

It's great having you contribute to this project Welcome to the community :nerd_face: :rocket:Soon one of our maintainers will review it and provide you with feedback/suggestions. If you think it's something urgent, feel free to reach out Md Shamim on LinkedIn. Please star ⭐ this repo to show us support.Happy, Open Source!

closes #7


Startup script needs a rework

The startup script currently always recreates all configuration files. It would be nice to skip them if setup was already done once.
Also, the safe_formata_and_mount command no longer exists so we need o update it to setup the home drive only once and add it to /etc/fstab.
It would be nice to include etckeeper package to keep track of config changes!
Some packages may need a rework too to the new Debian 9 stable release.

Somewhat no longer useful as we now have better maintained options like Cloud Shell, Google Cloud Workspaces, Github Workspaces and others.


Support AWS SDK 2.0

Thanks for the suggestion - this is already a high priority in the backlog and will be addressed soon. :)

+1

Hi, we were wondering if there are any updates on this issue? We'd like to use this client, but we have to use the AWS Java SDK 2.x.
Thanks!

Any news?
Is the backlog mentioned above publicly available?