Starting HELICS-Example with helics run does not work, seperate calling does

When trying to run the osmses example via the helics run command, the execution cannot find the helics package:

This is although helics is clearly installed with pip:

But when running the example with the 3 separate starts as in
$ python battery_cosim_complete.py & (or launch in its own shell)
$ python charger_cosim_complete.py & (or launch in its own shell)
$ helics_broker -f 2  (or launch in its own shell)
it seems to work:

Nonetheless, the broker prints out a warning at the end:

The "Debugging Command" prints out the following:

If you need additional information, let me know!

This issue came up during a tutorial I gave earlier this week and the fact that the co-simulation will run when the federates are launched individually but fail when using the runner makes me think something might be up with the runner re-work the two of you have been doing (but not completed?). Note that I haven't had this problem on macOS (ARM-based). This bug was manifesting when starting from a clean virtual environment.

@carwegka, the error you're seeing at the end of the co-simulation is somewhat expected (depending on variation in the OS scheduler). It happens on the very last time step when one of the federates ends early enough that it exits the co-simulation before the other federate has published its final value. When this happens, HELICS throws this warning to indicate that there is nobody to receive the sent publication (which is generally not good). Since it is the last time step, there will be no new calculations even if the federate was there to receive the publication.
I usually add a function that I call on the last step to advance the federates to infinite time (well, the maximum time HELICS can track) and doing so outside the main simulation loop means all the federates will be granted that time and receive an pending publications prior to exiting the co-simulation.  I've made this change and pushed it up into the "complete" version of the example.

@nightlark and @josephmckinsey, the example I was using can be found at HELICS-Examples/unmaintained/python/osmses_2024_battery_charger using the "osmses_2024_runner.json" which runs the "complete" version of the example.

This issue came up during a tutorial I gave earlier this week and the fact that the co-simulation will run when the federates are launched individually but fail when using the runner makes me think something might be up with the runner re-work the two of you have been doing (but not completed?). Note that I haven't had this problem on macOS (ARM-based). This bug was manifesting when starting from a clean virtual environment.

The pull requests for the re-work of the web UI/CLI haven’t been merged to main yet (or pushed to PyPI). Unless the pyhelics you used is from one of those branches, this is a pre-existing bug and was not introduced by those changes.

Could the runner be launching the scripts outside of the virtual environment?

The pull requests for the re-work of the web UI/CLI haven’t been merged to main yet (or pushed to PyPI). Unless the pyhelics you used is from one of those branches, this is a pre-existing bug and wasn’t introduced by those changes.

They were just pulling from PyPI so whatever the latest released version that's out there publicly.

@nightlark We (a colleague also had the same problem) tried it with global python interpreter (outside of virtual environment) and it also didn't work

Yea... the runner code hasn't changed in over 2 years, so it's likely a very long standing bug (@kdheepak is the most familiar with this area) or maybe a change in recent Python versions on some operating systems.
For a minimal reproduction, the runner appears to just be spawning subprocesses: https://github.com/GMLC-TDC/pyhelics/blob/main/helics/cli.py#L260-L266
You could try writing a Python script that just hardcodes those subprocess calls, replacing f["exec"] with a string consisting of the command to run, and env=env with env=dict(os.environ)

I've also been unable to reproduce the error using fresh virtual environments on macOS (M2, Python 3.9 and 3.12), and RHEL 8 Linux (x64, Python 3.9) -- this may be a Windows-only issue, but I don't have a Windows system to test on.

I think the problem here is that the runner spawns subprocesses that don't have the same environment has the parent process, and import helics doesn't seem to be present in that? Which is weird. Printing out the environment print(os.environ) in the individual federates before any import helics might give a clue as to what is going on there.
Add the following for good measure at the top of each python file and share the output here again:
import sys
import os

print("Environment: ", os.environ)

print("Python Version:", sys.version)

print("Python Interpreter Location:", sys.executable)

For the battery file:
Environment: environ({'ALLUSERSPROFILE': 'C:\ProgramData', 'APPDATA': 'C:\Users\wegkamp\AppData\Roaming', 'CHROME_CRASHPAD_PIPE_NAME':
'\\.\pipe\crashpad_1548_BGSIWXYCAKBRIEMZ', 'COMMONPROGRAMFILES': 'C:\Program Files\Common Files', 'COMMONPROGRAMFILES(X86)': 'C:\Program Files (x86)\Common Files', 'COMMONPROGRAMW6432': 'C:\Program Files\Common Files', 'COMPUTERNAME': 'ELENIANB59', 'COMSPEC': 'C:\WINDOWS\system32\cmd.exe', 'DRIVERDATA': 'C:\Windows\System32\Drivers\DriverData', 'FPS_BROWSER_APP_PROFILE_STRING': 'Internet Explorer', 'FPS_BROWSER_USER_PROFILE_STRING': 'Default', 'GUROBI_HOME': 'C:\gurobi1001\win64', 'HOMEDRIVE': 'U:', 'HOMEPATH': '\', 'HOMESHARE': '\\<IP_ADDRESS>\_Users$\wegkamp', 'LOCALAPPDATA': 'C:\Users\wegkamp\AppData\Local', 'LOGONSERVER': '\\ELENIAAD02V', 'NUMBER_OF_PROCESSORS': '4', 'ONEDRIVE': 'C:\Users\wegkamp\OneDrive', 'ORIGINAL_XDG_CURRENT_DESKTOP': 'undefined', 'OS': 'Windows_NT', 'PATH': 'c:\Users\wegkamp\.vscode\extensions\ms-python.python-2024.12.3-win32-x64\python_files\deactivate\powershell;C:\Users\wegkamp\Dokumente_lokal\helics_example\.venv\Scripts;c:\Users\wegkamp\.vscode\extensions\ms-python.python-2024.12.3-win32-x64\python_files\deactivate\powershell;C:\Users\wegkamp\Dokumente_lokal\helics_example\.venv\Scripts;C:\gurobi1001\win64\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Users\wegkamp\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\wegkamp\AppData\Local\Programs\Git\cmd', 'PATHEXT': '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.CPL', 'PROCESSOR_ARCHITECTURE': 'AMD64', 'PROCESSOR_IDENTIFIER': 'Intel64 Family 6 Model 158 Stepping 9, GenuineIntel', 'PROCESSOR_LEVEL': '6', 'PROCESSOR_REVISION': '9e09', 'PROGRAMDATA': 'C:\ProgramData', 'PROGRAMFILES': 'C:\Program Files', 'PROGRAMFILES(X86)': 'C:\Program Files (x86)', 'PROGRAMW6432': 'C:\Program Files', 'PSMODULEPATH': '\\<IP_ADDRESS>\_Users$\wegkamp\Eigene Dateien\WindowsPowerShell\Modules;C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules', 'PUBLIC':
'C:\Users\Public', 'SESSIONNAME': 'Console', 'SYSTEMDRIVE': 'C:', 'SYSTEMROOT': 'C:\WINDOWS', 'TEMP': 'C:\Users\wegkamp\AppData\Local\Temp', 'TMP': 'C:\Users\wegkamp\AppData\Local\Temp', 'WINDIR': 'C:\WINDOWS', 'ZES_ENABLE_SYSMAN': '1', 'PYTHONSTARTUP': 'c:\Users\wegkamp\.vscode\extensions\ms-python.python-2024.12.3-win32-x64\python_files\pythonrc.py', 'TERM_PROGRAM': 'vscode', 'TERM_PROGRAM_VERSION': '1.92.2', 'LANG': 'en_US.UTF-8', 'COLORTERM': 'truecolor', 'GIT_ASKPASS': 'c:\Users\wegkamp\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\git\dist\askpass.sh', 'VSCODE_GIT_ASKPASS_NODE': 'C:\Users\wegkamp\AppData\Local\Programs\Microsoft VS Code\Code.exe', 'VSCODE_GIT_ASKPASS_EXTRA_ARGS': '', 'VSCODE_GIT_ASKPASS_MAIN': 'c:\Users\wegkamp\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\git\dist\askpass-main.js', 'VSCODE_GIT_IPC_HANDLE': '\\.\pipe\vscode-git-a83ddf38b9-sock', 'VIRTUAL_ENV': 'C:\Users\wegkamp\Dokumente_lokal\helics_example\.venv', 'VIRTUAL_ENV_PROMPT': '.venv', 'VSCODE_INJECTION': '1'})
Python Version: 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)]
Python Interpreter Location: C:\Users\wegkamp\Dokumente_lokal\helics_example.venv\Scripts\python.exe
For the charger file:
Environment: environ({'ALLUSERSPROFILE': 'C:\ProgramData', 'APPDATA': 'C:\Users\wegkamp\AppData\Roaming', 'CHROME_CRASHPAD_PIPE_NAME': '\\.\pi
pe\crashpad_1548_BGSIWXYCAKBRIEMZ', 'COMMONPROGRAMFILES': 'C:\Program Files\Common Files', 'COMMONPROGRAMFILES(X86)': 'C:\Program Files (x86)\Common Files', 'COMMONPROGRAMW6432': 'C:\Program Files\Common Files', 'COMPUTERNAME': 'ELENIANB59', 'COMSPEC': 'C:\WINDOWS\system32\cmd.exe', 'DRIVERDATA': 'C:\Windows\System32\Drivers\DriverData', 'FPS_BROWSER_APP_PROFILE_STRING': 'Internet Explorer', 'FPS_BROWSER_USER_PROFILE_STRING': 'Default', 'GUROBI_HOME': 'C:\gurobi1001\win64', 'HOMEDRIVE': 'U:', 'HOMEPATH': '\', 'HOMESHARE': '\\<IP_ADDRESS>\_Users$\wegkamp', 'LOCALAPPDATA':
'C:\Users\wegkamp\AppData\Local', 'LOGONSERVER': '\\ELENIAAD02V', 'NUMBER_OF_PROCESSORS': '4', 'ONEDRIVE': 'C:\Users\wegkamp\OneDrive', 'ORIGINAL_XDG_CURRENT_DESKTOP': 'undefined', 'OS': 'Windows_NT', 'PATH': 'c:\Users\wegkamp\.vscode\extensions\ms-python.python-2024.12.3-win32-x64\python_files\deactivate\powershell;C:\Users\wegkamp\Dokumente_lokal\helics_example\.venv\Scripts;c:\Users\wegkamp\.vscode\extensions\ms-python.python-2024.12.3-win32-x64\python_files\deactivate\powershell;C:\Users\wegkamp\Dokumente_lokal\helics_example\.venv\Scripts;C:\gurobi1001\win64\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Users\wegkamp\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\wegkamp\AppData\Local\Programs\Git\cmd', 'PATHEXT': '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.CPL', 'PROCESSOR_ARCHITECTURE': 'AMD64', 'PROCESSOR_IDENTIFIER': 'Intel64 Family 6 Model 158 Stepping 9, GenuineIntel', 'PROCESSOR_LEVEL': '6', 'PROCESSOR_REVISION': '9e09', 'PROGRAMDATA': 'C:\ProgramData', 'PROGRAMFILES': 'C:\Program Files', 'PROGRAMFILES(X86)': 'C:\Program Files (x86)', 'PROGRAMW6432': 'C:\Program Files', 'PSMODULEPATH': '\\<IP_ADDRESS>\_Users$\wegkamp\Eigene Dateien\WindowsPowerShell\Modules;C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules', 'PUBLIC': 'C:\Users\Public', 'SESSIONNAME': 'Console', 'SYSTEMDRIVE': 'C:', 'SYSTEMROOT': 'C:\WINDOWS', 'TEMP': 'C:\Users\wegkamp\AppData\Local\Temp', 'TMP': 'C:\Users\wegkamp\AppData\Local\Temp', 'WINDIR': 'C:\WINDOWS', 'ZES_ENABLE_SYSMAN': '1', 'PYTHONSTARTUP': 'c:\Users\wegkamp\.vscode\extensions\ms-python.python-2024.12.3-win32-x64\python_files\pythonrc.py', 'TERM_PROGRAM': 'vscode', 'TERM_PROGRAM_VERSION': '1.92.2', 'LANG': 'en_US.UTF-8', 'COLORTERM': 'truecolor', 'GIT_ASKPASS': 'c:\Users\wegkamp\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\git\dist\askpass.sh', 'VSCODE_GIT_ASKPASS_NODE': 'C:\Users\wegkamp\AppData\Local\Programs\Microsoft VS Code\Code.exe', 'VSCODE_GIT_ASKPASS_EXTRA_ARGS': '', 'VSCODE_GIT_ASKPASS_MAIN': 'c:\Users\wegkamp\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\git\dist\askpass-main.js', 'VSCODE_GIT_IPC_HANDLE': '\\.\pipe\vscode-git-a83ddf38b9-sock', 'VIRTUAL_ENV': 'C:\Users\wegkamp\Dokumente_lokal\helics_example\.venv', 'VIRTUAL_ENV_PROMPT': '.venv', 'VSCODE_INJECTION': '1'})
Python Version: 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)]
Python Interpreter Location: C:\Users\wegkamp\Dokumente_lokal\helics_example.venv\Scripts\python.exe
PS: I deleted some of the domain part of the environment, which I think is not important, but I don't want to have published. I hope this is not that important.

It seems to be using the correct interpreter, i.e. C:\Users\wegkamp\Dokumente_lokal\helics_example.venv\Scripts\python.exe.
Can you open a new command prompt, and without activating your .venv, run C:\Users\wegkamp\Dokumente_lokal\helics_example.venv\Scripts\python.exe -c "import helics" and see if that works?

So if I do that and afterwards run helics run --path=HELICS-Examples\unmaintained\python\osmses_2024_battery_charger\osmses_2024_runner.json
This then also gives different interpreters for the two files:
Python Version: 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)]
Python Interpreter Location: C:\Users\wegkamp\AppData\Local\Programs\Python\Python310\python.exe
Nonetheless, the error occurs

I can, yes. And it doesn't throw back any error/warning.

If I am in the venv, I get
Python Interpreter Location: C:\Users\wegkamp\AppData\Local\Programs\Python\Python310\python.exe
for helics run and
Python Interpreter Location: C:\Users\wegkamp\Dokumente_lokal\helics_example\.venv\scripts\python.exe
for python HELICS-Examples\unmaintained\python\osmses_2024_battery_charger\battery_cosim_complete.py.

Do you have both C:\Users\wegkamp\Dokumente_lokal\helics_example.venv and
C:\Users\wegkamp\Dokumente_lokal\helics_example\.venv directories? I
noticed that your interpreter is located in the former, but the VIRTUAL_ENV
variable is pointing to the latter (along with an entry in PATH). If both
exist, I wonder if both have helics installed.
On Thursday, September 5, 2024, carwegka @.***> wrote:

If I am in the venv, I get
Python Interpreter Location: C:\Users\wegkamp\AppData
Local\Programs\Python\Python310\python.exe
for helics run and
Python Interpreter Location: C:\Users\wegkamp\Dokumente_
lokal\helics_example.venv\scripts\python.exe
for python HELICS-Examples\unmaintained\python\osmses_2024_battery_
charger\battery_cosim_complete.py.
—
Reply to this email directly, view it on GitHub
https://github.com/GMLC-TDC/pyhelics/issues/104#issuecomment-2331284152,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6JBZYJQXRR776TOIXXSNDZVA6HHAVCNFSM6AAAAABNUFKQASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZRGI4DIMJVGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Do you have both C:\Users\wegkamp\Dokumente_lokal\helics_example.venv and
C:\Users\wegkamp\Dokumente_lokal\helics_example\.venv directories? I
noticed that your interpreter is located in the former, but the VIRTUAL_ENV
variable is pointing to the latter (along with an entry in PATH). If both
exist, I wonder if both have helics installed.

If I am in the venv, I get Python Interpreter Location: C:\Users\wegkamp\AppData\Local\Programs\Python\Python310\python.exe for helics run

This is the reason you are getting the import error.
How have you installed Python? How did you create the .venv virtual environment to begin with? Can you uninstall this version of Python?

C:\Users\<account>\AppDAta\Local\Programs is one of the default install locations for Python on Windows. I'm wondering if the underlying issue was something like the helics_example\.venv folder getting renamed to helics_example.venv, since the "activate" scripts created by venv have some memory of their original location (which would no longer exist, leading to the default Python executable running). It might be interesting to see a copy of whichever script was used to activate the virtual environment.

@carwegka, is this issue closed out as far as you're concerned or do we need to keep digging into it?

Hi @trevorhardy  and @nightlark. I recently had another academic user report a similar issue where the helics run command is not properly using the python virtual environment python executable on windows. I can also confirm this is still an issue. A work around seems to be to explicity specify the python executable for your virtual env in the "exec" string in your runner configuration file. for example:
{
"name": "gldHelicsTestRunner",
"broker": true,
"federates": [
{
"directory": "C:\Users\username\workspace\gldHelicsTesting",
"exec": "C:\Users\username\workspace\gldHelicsTestings\.venv\Scripts\python.exe helicsFederate.py python_config.json 10",
"host": "localhost",
"name": "python_federate"
}
]
}
When doing this I can confirm it's using the correct python environment. However, I am running into another issue. If I attempt to run this little test python federate and a helics_broker explicitly it runs successfully. if I try to run using helics run --path=
I get the following error in both a Windows PowerShell and cmd prompt.
helics run --path=gldHelicsTestRunner.json
[warn] helics-cli's web interface is not installed. You may want to run pip install "helics[cli]".
[warn] helics-cli's observer functionality is not installed. You may want to run pip install "helics[cli]".
[info] Running federation: gldHelicsTestRunner
[info] Adding auto broker (i.e. helics_broker -f1) to helics-cli subprocesses.
[info] Running federate python_federate as a background process
Error: FileNotFoundError: [WinError 2] The system cannot find the file specified

Are you escaping the backslashes correctly?

@afisher1 are you escaping the backslashes correctly?

Ok GitHub keeps executing the escape lol. I've tried with 2, 3, and 4 backslashes all with the same result.

To rule out crazy escaping issues, I'd highly recommend using / even on Windows.

You can also add a call to breakpoint() in the helics/cli.py file you have installed just before the call to spawn a subprocess, to inspect what the actual values loaded from the config file look like.

Ok I must've missed an escaping backslash somewhere. My subsequent error was due to unescaped backslash. And yes it also works correctly with a /. So no additional issues besides helics runner not using the virtual env it was executed under when starting the federate processes in windows. So current workaround solution on windows with the helics runner is to use the full path the virtual env python executable in the "exec" key.

Sorry for the delayed answer, I completely got lost of this thread!
So to me it seems that there is a different python version in the venv compared to the global python version. And with the two different calls of the helics example (1 via helics run and 2 via separate calling) they might use the different version (maybe 2 does not use the venv python?). So one of the two does fail because the python version is "wrong" and thus cannot find helics in the global environment?
But why does the second version (separate calling in different terminals) not fail no matter if I activate the environment before or not?
And to answer at least some of your questions, the environment was created using python -m venv .venv and then .venv\scripts\activate.
The .venv folder probably was never renaming, maybe this was a copying issue.

@nightlark. After looking into this more this appears to be a known issue with python's subprocess.run and windows OS. The "official" fix is to use the result of sys.executable rather than 'python' in the exec command passed into subprocess. So in our runner configurations. Please note that you should not use sys.exectuable in the python runner configuration file. It needs to be used in place of the 'python' in the exec string internally in the subprocess.run() function call. see here. @carwegka this is the underlying issue causing it to use the system installed python executable rather than the one created with your virtual environment regardless of whether you called helics run under the virtual environment or not.  So giving the full file path to your desired virtual env python executable in the exec key should fix your issues. Even with the proper fix implemented on our end you would still need to make sure you executed helics run in the activated virtual env.

Right now the HELICS CLI just passes the exec string verbatim to subprocess.run as-is with no further processing. I think adding special treatment for occurrences of python in the "exec" field would be baking in an assumption that the venv/executable used for the helics runner is the right one for the federate to use, which at minimum breaks when using helics CLI installed by pipx. shutil.which() to resolve the full path to the executable based on PATH seems a bit better since most commands and not just python could be run through it as a preprocessing step. (The Python binary is also not guaranteed to just be "python" -- I've seen "python3", "python3.9" etc depending on how it was installed).
I think this gets at an underlying issue of managing what environment a command should run in, with the ability to support multiple Python federates that are installed in their own venvs to avoid dependency conflicts with each other.
I guess we sort of already support that right now in the form of specifying the full path to the python interpreter -- though that's not really portable if you're sharing a config file with others. I'm not sure we have a way to make a fully portable config file, since the location/creation of a venv would be dependent on a user creating it in the right place for the example/demo they are trying to run...

Thanks for the help and explanations, this clarifies the general problem to me (although I'm probably not that much into the topic). Real thanks!

A change that should help address this issue will be in the 3.6 release of pyhelics.


request rate of host & cluster only of half of the actual value

I use turbine to monitor a cluster of tow instance, the request rate of host & cluster in turbine dashboard just equal to the value in the hystirx dashboard of a single instance. It means that when I sum the value of two instance, the request rate of host & cluster in turbine dashboard is only half of the acture value.

the full context of aplication.yml:
management:
  security:
    enabled: false
spring:
  application:
    name: turbine
server:
  port: 9386
turbine:
  app-config: xxx
  cluster-name-expression: aSGName
  instanceUrlSuffix:
    xxx: xxx/hystrix.stream
  aggregator:
      cluster-config: xxx

eureka:
  client:
    service-url:
      defaultZone: http://eurekahost:9396/eureka/
  instance:
    lease-expiration-duration-in-seconds: 30
    lease-renewal-interval-in-seconds: 10
    prefer-ip-address: true

Any help will be welcome!

This issue is probably related to this bug: https://github.com/Netflix/Hystrix/issues/1697


Fix/telemetry

coverage: 67.716%. remained the same
when pulling c9a7125c11523adc160e3885f17395af902b7e4e on fix/telemetry
into f79c7e130f191900b6c1e139dfedcada8474e01b on main.


Enhancement - Recursive Folders for each Anime

Anime-DL currently downloads shows in the main folder and then moves objects to a subfolder named "Output".  How much effort would it take to send episodes to Output[Anime Title]?
The function which moves objects to Output would need modified to check/verify folder [Anime Title] existed, and then send objects to the respective recursed folder.
As an example:
http://www.crunchyroll.com/naruto/episode-220-departure-535236 would be sent to "\Output\naruto[episode]"
while
http://www.crunchyroll.com/darling-in-the-franxx/episode-10-the-city-of-eternity-759593 would be sent to "\Output\darling-in-the-franxx[episode]"
To improve efficiency, Anime-DL could also check the respective show's folder for the episode(s) so that it does not download a show that already exists.  I believe it does this with the Output folder now, except it downloads before the verification and leaves the downloaded file in folder "\Anime-DL" if "\Output" already contains the file.
If I ever had time, I would consider looking into doing this modification as most of it only requires optimizing/modifying existing code.  Unfortunately, real life gets in the way.

It is easy to do, but like you mentioned, real life gets in the way. I'm currently a little too busy to give my attention to this. But, I'll try to get something done soon.


Release 0.4.9 / 1.0 ?

I see a major 1.0 release coming, but in the meantime what I could really use is a version that is compatible with the rest of my requirements.txt, without having to pin to old versions of pip for --use-deprecated=legacy-resolver.
Is there any way the 0.4.7 branch could get 33fa2490714954b189e24963e4586f86ce4f99c2 cherry-picked into it, have the version bumped, and then released to pypi?

Hi. I've checked, and there is a v0.4.8 tag already. I think the best thing to do is a new release, yes.

Please @jazzband release a new version :pray: of auditlog to pypi

@hramezani : I think we can make a release (v1.0), now that Django 4.0 is supported. What do you think ?

@Linkid sure we can make a new release but I am not sure about the v1.0.

Is there another blocker for the v1.0 ?

I am not sure as I am a lead for this package. it up to you to decide.

FWIW, I've been using this package for 2+ years and had zero troubles. Looks pretty stable to me and worthy of being v1.0. Open issues can be tackled later anyways

@Linkid Yes, I can help :)

@hramezani : nice :). Feel free to  open a project lead issue ;). I'll vote for you, for sure !

@hramezani : if you need help to lead this project, I can make an issue to be co-leader with you. Tell me if you need it, or I will just be a helper in reviewing and triage (which is ok for me) :).

@Linkid That would be great if you can help!

@Linkid can we prepare a new release now?

Yep, let's go :).

The new release is available on PyPI, thanks to @hramezani. This issue can be closed :).


Add --header-file and/or --header-lines (WIP/TBD)

This is an experimental feature only available on master. The decision is not final.
fzf --header-file <(echo the world is yours) --reverse

--header-file is useful if you want to display free-form information about the context while --header-lines should be more suitable for tabular data.


Support for Asus ROG GU502GU

Fan control doesn't work on Asus ROG GU502GU. Kindly enable support for custom fan control on Asus Zephyrus M GU502GU

I'm pretty sure the developers put "ONLY WORKS ON G14 2020 (For the time being)"


Docker Installation Failure

While i'm attempting to install this docker image i'm getting this error:
databasename.us-east-1.rds.amazonaws.com (<IP_ADDRESS>:3306) open
time="2023-08-30T05:13:26Z" level=info msg="load configuration from file" file=/etc/supervisord.conf
time="2023-08-30T05:13:26Z" level=info msg="create process:shopware-empty-cache"
time="2023-08-30T05:13:26Z" level=info msg="create process:php-fpm"
time="2023-08-30T05:13:26Z" level=info msg="create process:nginx"
time="2023-08-30T05:13:26Z" level=info msg="stop listening"
time="2023-08-30T05:13:26Z" level=info msg="try to start program" program=php-fpm
time="2023-08-30T05:13:26Z" level=info msg="try to start program" program=nginx
time="2023-08-30T05:13:26Z" level=info msg="try to start program" program=shopware-empty-cache
time="2023-08-30T05:13:26Z" level=info msg="success to start program" program=shopware-empty-cache
time="2023-08-30T05:13:26Z" level=info msg="program stopped with status:exit status 0" program=shopware-empty-cache
2023/08/30 05:13:26 [notice] 22#22: using the "epoll" event method
2023/08/30 05:13:26 [notice] 22#22: nginx/1.24.0
2023/08/30 05:13:26 [notice] 22#22: OS: Linux 5.10.0-17-cloud-amd64
2023/08/30 05:13:26 [notice] 22#22: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2023/08/30 05:13:26 [notice] 22#22: start worker processes
2023/08/30 05:13:26 [notice] 22#22: start worker process 23
2023/08/30 05:13:26 [notice] 22#22: start worker process 24
[30-Aug-2023 05:13:26] NOTICE: fpm is running, pid 20
[30-Aug-2023 05:13:26] NOTICE: ready to handle connections
time="2023-08-30T05:13:27Z" level=info msg="success to start program" program=php-fpm
time="2023-08-30T05:13:27Z" level=info msg="success to start program" program=nginx
<IP_ADDRESS> -  30/Aug/2023:05:13:56 +0000 "GET /index.php" 500
<IP_ADDRESS> - - [30/Aug/2023:05:13:56 +0000] "GET /admin HTTP/1.1" 500 5 "-" "curl/8.2.1"
2023/08/30 05:13:56 [info] 23#23: *1 client <IP_ADDRESS> closed keepalive connection
I'm not even getting a migration to the database yet.
i've redacted my database actual url and IP address
Any assistance would be greatly appreciated.

What are the container arguments?

thats the thing when running the docker container through portainer i entered .env variables but they aren't showing up in the local .env in the shopware root directory. How to go about migrating that data into my database?

here are my .env variables in the portainer docker container
INSTALL_ADMIN_USERNAME=example
INSTALL_ADMIN_PASSWORD=example
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PHPIZE_DEPS=autoconf 		dpkg-dev dpkg 		file 		g++ 		gcc 		libc-dev 		make 		pkgconf 		re2c
PHP_INI_DIR=/usr/local/etc/php
PHP_CFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
PHP_CPPFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
PHP_LDFLAGS=-Wl,-O1 -pie
GPG_KEYS=1729F83938DA44E27BA0F4D3DBDB397470D12172 BFDDD28642824F8118EF77909B67A5C12229118F 2C16C765DBE54A088130F1BC4B9B5F600B55F3B4
PHP_VERSION=8.0.29
PHP_URL=https://www.php.net/distributions/php-8.0.29.tar.xz
PHP_ASC_URL=https://www.php.net/distributions/php-8.0.29.tar.xz.asc
PHP_SHA256=14db2fbf26c07d0eb2c9fab25dbde7e27726a3e88452cca671f0896bbb683ca9
APP_ENV=prod
LOCK_DSN=flock
MAILER_URL=null://localhost
DATABASE_PORT=3306
SHOPWARE_ES_INDEX_PREFIX=
COMPOSER_HOME=/tmp/composer
SHOPWARE_HTTP_CACHE_ENABLED=1
SHOPWARE_HTTP_DEFAULT_TTL=7200
SHOPWARE_AUTOMATICALLY_EMPTY_CACHE_ENABLED=false
SHOPWARE_EMPTY_CACHE_INTERVAL=86400
BLUE_GREEN_DEPLOYMENT=0
INSTALL_LOCALE=en-GB
INSTALL_CURRENCY=EUR
CACHE_ADAPTER=default
REDIS_CACHE_HOST=redis
REDIS_CACHE_PORT=6379
REDIS_CACHE_DATABASE=0
SESSION_ADAPTER=default
REDIS_SESSION_HOST=redis
REDIS_SESSION_PORT=6379
REDIS_SESSION_DATABASE=1
FPM_PM=dynamic
FPM_PM_MAX_CHILDREN=5
FPM_PM_START_SERVERS=2
FPM_PM_MIN_SPARE_SERVERS=1
FPM_PM_MAX_SPARE_SERVERS=3
PHP_MAX_UPLOAD_SIZE=128m
PHP_MAX_EXECUTION_TIME=300
PHP_MEMORY_LIMIT=512m
PHP_ERROR_REPORTING=E_ALL
RUN_NGINX=1
LD_PRELOAD=/usr/lib/preloadable_libiconv.so php
SHOPWARE_ES_ENABLED=0
SHOPWARE_ES_INDEXING_ENABLED=0
APP_SECRET=example
INSTANCE_ID=example
DATABASE_HOST=example.us-east-1.rds.amazonaws.com
DATABASE_URL=mysql://example:example@example.us-east-1.rds.amazonaws.com:3306/example
SHOPWARE_ES_HOSTS=

or have a docker compose file, docker commands you did run. I am not sure if you had set some cmd/entrypoint

i used your docker hub install
https://hub.docker.com/r/shyim/shopware

the entry point is the default /entrypoint.sh

are there migration commands to run within the docker, i see that the information i placed in the docker's .env variables didn't appear in the .env file in the root directory. So once I add the details to the local .env file how do i get shopware to then migrate the data to the database?

The docker entrypoint should run the migrations. Tested right now with docker playground it works for me weird. see README example docker compose

the docker-compose.yml works from Readme works, thank you.


Allowing users to write N$ in fo formulas to denote integer variable N

Closes #59

Actually,
integer_variable  = ${ (unsorted_variable ~ "$" ~ integer_sort) | !(unsorted_variable ~ "$" ~ sort) ~ (unsorted_variable ~ "$") }
would be better - more elaboration tolerant


Add message registry benchmarks

Just like the title says
The way I run them is that I run atom in spec runner mode in package root, then open it's dev console and paste this
require('/home/steel/.atom/packages/linter/benchmarks/message-registry.js')

These benchmarks show that our message registry is as optimized as it could ever be (accidentally I may add). Even changing that for...of into a foreach results in a performance regression


Remove opEquals et.all. from default class in object.d

s.t. they can be @safe and @nogc

An alternative to this is implementing Andrei's Proto base type.


Custom README.md for public

I am working on readme file for the organization. Kindly review the same and provide your feedback.

yeah it looks good but other team members must review it and can give their feedbacks what to add or subtract


[Capacitor Plugin Error] - createDynamicLink

I'm not getting the long link, using capacitor 4
[Capacitor Plugin Error] - CapacitorFirebaseDynamicLinks - createDynamicLink - Unable to serialize plugin response as JSON.Ensure that all data passed to success callback from module method is JSON serializable!
despite having the log from xcode
⚡  To Native ->  CapacitorFirebaseDynamicLinks createDynamicLink 65776433 The long URL is: {show the link here}
It works fine on android

Thank you for submitting the issue.
Can you share, what data you're passing to the plugin? You can change your specific IDs in strings, of course.

const config: LinkConfig = {       domainUriPrefix: 'https://example.page.link',       uri: 'https://example.page.link/sharing',    };
only passing domainUriPrefix and uri
@NLueg

Thanks for your fast response! I just published the version 4.0.2 which should solve the issue.
Could you check this in your app? Thanks!

@NLueg I confirm that it works now, Thank you.


Add truncation to status reporting

similar to https://github.com/solo-io/solo-kit/issues/523
we should protect etcd from gloo mesh as a potentially buggy or erroneous client. if resources get too large, we can take down their k8s cluster itself and put GM into a state where it cannot start.
the proposed solution:

try to truncate status before writing
if that fails and still too large, don't write the status

cc @Sodman @ilackarms @EItanya (I'm told this may not be an issue for GM, but not sure why we are so confident)
@nrjpoddar as part of stability effort

The design for Gloo Mesh statuses was that the entire status would be written to and held in redis, but the status written back to the actual CRs in k8s would be truncated/trimmed to a reasonable size, eg max 10 entities. For large statuses, users can get more information via the UI, and we also plan to add tooling to meshctl to help with this.
Looking at the code however, I'm not sure this has been implemented yet, at least I'm not seeing the truncation logic where I'd expect it.


Fix reconnects not being recognized

If we reconnect too quickly, the signalling server won't have the time to add our information to the database yet and the reconnect won't recognize us. This can be fixed by waiting a little bit before we reconnect.
When we only disconnect for shortly it will take the signaling server longer to notice the disconnect than to reconnect. In which case the reconnect isn't recognized as a disconnect.
This is still not a perfect solution and best-effort only. But from my testing where I noticed this happening it was fixed this way for now.

I think that will be slightly more complicated in some cases. You'll have a connection on the server but you don't want to do anything with it yet. Might result in some if statements here and there, while on the client it's simple.


Provide an option to delete scaled images when original is deleted

It would be really useful to have the following functionality: be able to delete the scaled images when the original has been deleted. Right now in order to achieve this, one has to retrieve the ID of the scaled image and make an additional request (deleteFile). This can be simplified by having some configuration property (see below) which is then evaluated by Fine Uploader and the scaled image is deleted as well. See https://github.com/FineUploader/fine-uploader/issues/1457 for more info
scaling: {
    sizes: [
        {name: "small", maxSize: 100},
        {name: "medium", maxSize: 300}
    ],
    deleteWithOriginal: true
}

Thanks for the request. We'll consider this for a future release.
On Sat, Oct 3, 2015 at 5:02 AM Anton Sarov<EMAIL_ADDRESS>wrote:

It would be really useful to have the following functionality: be able to
delete the scaled images when the original has been deleted. Right now in
order to achieve this, one has to retrieve the ID of the scaled image and
make an additional request (deleteFile). This can be simplified by having
some configuration property (see below) which is then evaluated by Fine
Uploader and the scaled image is deleted as well. See #1457
https://github.com/FineUploader/fine-uploader/issues/1457 for more info
scaling: {
sizes: [
{name: "small", maxSize: 100},
{name: "medium", maxSize: 300}
],
deleteWithOriginal: true
}
—
Reply to this email directly or view it on GitHub
https://github.com/FineUploader/fine-uploader/issues/1478.


Showing Local Addresses in Node Window

This change adds one line to the Node Window (debugwindow.ui)
under the Network section and shows the LocalAddresses there.
fixes #564

There hasn't been much activity lately. What is the status here?
Finding reviewers may take time. However, if the patch is no longer relevant, please close this pull request. If the author lost interest or time to work on this, please close it and mark it 'Up for grabs' with the label, so that it can be picked up in the future.

qt/rpcconsole.cpp: In member function ‘void RPCConsole::updateNetworkState()’:
qt/rpcconsole.cpp:965:61: error: ‘const class CNetAddr’ has no member named ‘ToString’; did you mean ‘ToStringAddr’?
         local_addresses += QString::fromStdString(it->first.ToString()) + ":" + QString::number(it->second.nPort);
                                                             ^~~~~~~~
                                                             ToStringAddr

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Reviews
See the guideline for information on the review process.

Type
Reviewers

ACK
shaavan, jarolrod

If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

Concept ACK, kinda works.
Minor nit noticed - could avoid adding ":0" as a port for I2P addresses.

Another thing - list is currently comma separated, without wrapping. Wouldn't it be too long if somebody has IPv4, IPv6, DJDNS, Tor and I2P addresses at the same time?

This PR still have a couple of unaddressed comments: https://github.com/bitcoin-core/gui/pull/626#discussion_r915334998 and https://github.com/bitcoin-core/gui/pull/626#discussion_r1274077350.
@jadijadi Are you still working on this?

This PR still have a couple of unaddressed comments: #626 (comment) and #626 (comment).
@jadijadi Are you still working on this?

Will check and comment soon

Concept ACK, kinda works.
Minor nit noticed - could avoid adding ":0" as a port for I2P addresses.

thanks for the suggestion, did this.

Another thing - list is currently comma separated, without wrapping. Wouldn't it be too long if somebody has IPv4, IPv6, CJDNS, Tor and I2P addresses at the same time?

Thanks for this point, it is fixed and the widget worswraps and extends when needed.

This PR still have a couple of unaddressed comments: #626 (comment) and #626 (comment).

Dear @hebasto , addressed all issues, updated the code & replied to queries. Thanks for the follow up.

Also, please split the interfaces changes into a different commit than the GUI changes.

Might be a good improvement to cherry-pick e4fddc9f395819d0bdf74003676aa563929756fa and use it to update; in testing, I found myself watching for None to change, but it never did because the string isn't updated.

Also, please split the interfaces changes into a different commit than the GUI changes.

did that. cleaner and atomic. thanks.

did that. cleaner and atomic. thanks.

Hmm, it's not that way in your new push tho

Somehow you introduced a typo in the commit message >_<

Somehow you introduced a typo in the commit message >_<

Oh.. sorry. fixed and added a spellchecker.

@luke-jr May I kindly ask for a review on this PR?

cc @furszy

utACK
Maybe add a QLabel hint describing what "local addresses" are for GUI users? (and/or use another term for them).

utACK
Maybe add a QLabel hint describing what "local addresses" are for GUI users? (and/or use another term for them).

Any suggestion? English is not my first language. Something like "Addresses where Bitcoin Core binds to"? On DataDir we have the tooltip on the value column. I'll also keep it like that.

Maybe add a QLabel hint describing what "local addresses" are for GUI users? (and/or use another term for them).

Any suggestion? English is not my first language. Something like "Addresses where Bitcoin Core binds to"? On DataDir we have the tooltip on the value column. I'll also keep it like that.

Perhaps any of these (or a combination):

Each local address broadcast by this node.

IP addresses of your local machine or network interface that the node uses to connect to the Bitcoin network

Network addresses that your Bitcoin node is currently using to communicate with other nodes.

Network addresses that your Bitcoin node is currently using to communicate with other nodes.

Thanks @pablomartin4btc . Added this as the tooltip & thanks for the tACK


Add Nix OS/package-manger installation to readme

Thanks to @ByteSudoer @r-ryantm  chess-tui already available on Nix (Commits History)
Nix is an universal package-manager and can be installed on any operating system.
Add instructions for the users about how to install for NixOS (linux distributionn) or via Nix package-manager (any OS)
BTW it should also work on android on Termux or Nix-on-Droid via nix package-manager. I've tried other TUI packages before but not yet chess-tui.

Nice I didn't know that. Do you want to make the pr for that issue ? Else I will do it

Actually it doesn't look good on Readme page. IMO all the documentation, installation instructions etc should be moved to GitHub's Wiki page (maybe to a dedicated website in future). Simple markdown based, GitHub hosted site should be good enough with the help of https://github.com/squidfunk/mkdocs-material. What do you think?
Instead of all installation instructions on Readme page show this image/hyperlink : https://repology.org/project/chess-tui/badges (idea from Calibre)

Actually it doesn't look good on Readme page. IMO all the documentation #94, installation instructions, changelogs, project specific news/blogs? etc should be moved to GitHub's Wiki page (maybe to a dedicated website in future). Simple markdown based, GitHub hosted site should be good enough with the help of https://github.com/squidfunk/mkdocs-material. What do you think?

Great idea, as you saw it in #94 it is planned to document chess tui as part of a big refactor of the code I am starting. Improving the readability and spliting in more files. Putting the installation instructions here could be great.

Instead of all installation instructions on Readme page show this image/hyperlink : https://repology.org/project/chess-tui/badges (idea from Calibre)

Perfect, I was wondering how we could still have a good way for users to quickly see if they can install the project with their package manager. This solves it

https://thomas-mauran.github.io/chess-tui/docs/Installation/NixOS
Closing...thankyou :)

True gonna be improving that thanks @shuvashish76 !


Missing some Lenovo Drivers for Windows 10 21H2

Hey Guys,
since we want to change our sccm deployment to Win10 21H2, i want to upgrade our Driver Packages in SCCM.
Some drivers are missing, like L15, E15, P51s or T570.
I use the Driver Automation Tool Version 7.0.1.
Can someone help me or has the same problem?
Thank you.

Yes. I have the same problem. I think Lenovo must have changed the xml file.

I was in version 7.0.4. I switched back to version 6.5.6, it works.
Resolved by Jabbaxx
https://github.com/maurice-daly/DriverAutomationTool/issues/308


Setting the value of a slider doesn't update the thumb

If the value property is changed in a component the slider resets the value (componentWillReceiveProps) but doesn't update the thumb position.

Here's a PR to fix this issue:
https://github.com/xinthink/react-native-material-kit/pull/201

Thanks for the fix. It'll be released in the next version

For some reason, when I'm adding onChange to MKSlider, it stops the thumb from moving.
Without the onChange it works. Sorry if it's a n00b question...
Here's the code:
export default class JobOfferSlider extends React.Component {

  constructor (props) {
    super(props)
    this.state = {
      curValue: 25
    }
  }

  render () {
    return (
      <View style={styles.container}>
        <View style={styles.row}>
          <View style={styles.col}>
            <MKSlider
              min={10}
              max={100}
              value={25}
              style={styles.slider}
              onChange={(newValue) => this.setState({curValue: newValue.toFixed(0)})}
              />
            <Text style={styles.textNormal}>
              {this.state.curValue}
            </Text>
          </View>
        </View>
      </View>
    )
  }
}

@projoneftw even i facing the same issue, did u find any solution to this?

@jinxac yeah, you're right, that works :)
I did a work around with ref to the text.


SmokeSensor Bug

after updating to version 0.1.8 it does not work anymore, I have configured a smoke sensor in config.json

Sorry, some code lost. Must be restored in 0.1.9.


New Monterey Application Creation Dialog

Intention

I'm submitting a feature discussion request

Jeroen proposes this approach:

this is what I have in mind

this is what I have in mind

Yes, I know (as you just wrote that in Gitter). My article that I want to write is not finished - I just put the first screenshot, to anchor the discussion that should start soon 😄

Nik's comments and alterations


Swift Compatibility

is this calendar implementation compatible with swift?
If so will adding a bridging header suffice?

This component is not supported anymore. I believe it there's no problem in using it from a swift code, but I didn't try it myself.


register page generates 500 error

Hey Patrick,
I don't see a record of this anywhere in your issues list.
When someone registers as a new user, the https connection appears to timeout and generates a 500 error.
Looking at the securitymonkey-deploy.log file, I can see the following errors (note: this is two different registrations with second being a repro)
2015-02-25 13:37:20,244 ERROR: Exception on /register [POST] [in /usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py:1423]
  File "/usr/local/lib/python2.7/dist-packages/Flask_Security-1.7.4-py2.7.egg/flask_security/views.py", line 122, in register
2015-02-25 14:35:46,660 ERROR: Exception on /register [POST] [in /usr/local/lib/python2.7/dist-packages/Flask-0.10.1-py2.7.egg/flask/app.py:1423]
  File "/usr/local/lib/python2.7/dist-packages/Flask_Security-1.7.4-py2.7.egg/flask_security/views.py", line 122, in register

Line 122 in views.py refers to the login function -
            login_user(user)

with the login function being
def login():
    """View function for login view"""

    form_class = _security.login_form

    if request.json:
        form = form_class(MultiDict(request.json))
    else:
        form = form_class()

    if form.validate_on_submit():
        login_user(form.user, remember=form.remember.data)
        after_this_request(_commit)

        if not request.json:
            return redirect(get_post_login_redirect(form.next.data))

    if request.json:
        return _render_json(form, include_auth_token=True)

    return _security.render_template(config_value('LOGIN_USER_TEMPLATE'),
                                     login_user_form=form,
                                     **_ctx('login'))

nginx configuration looks ok -
    location /register {
        proxy_read_timeout 120;
        proxy_pass  http://<IP_ADDRESS>:5000;
        proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
        proxy_redirect off;
        proxy_buffering off;
        proxy_set_header        Host            $host;
        proxy_set_header        X-Real-IP       $remote_addr;
        proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
    }

The user is always created and the new user can login without a problem but I can't figure out where the 500 error is coming from.
Any thoughts?

I just ran through a user registration and did not have an issue.  I have, however, seen this before and was unable to track it down.
Could you share part of your env-config/config-deploy.py file with me?
SECURITY_REGISTERABLE = True
SECURITY_CONFIRMABLE = True
SECURITY_RECOVERABLE = True

Specifically, I'm wondering if you have SECURITY_CONFIRMABLE enabled.

#64 is a related Registration issue, and is another bug that I haven't seen in a long time.  Not sure if setting CONFIRMABLE fixed this, or if a version of flask security fixed it.
Currently on Flask-Security==1.7.4.

Thanks @monkeysecurity :)
I changed
SECURITY_CONFIRMABLE = From

to
SECURITY_CONFIRMABLE = True

and restarted supervisor. The register page now works perfectly (I did have to add a confirm route  in the nginx configration so I didn't generate a 404 page from the confirm url).
Thx again!


Erroneus dependency on material design in DestinationsNavHost.kt

Hi!
The generated DestinationsNavHost.kt actually depends on material design:
import androidx.compose.material.*

Even if none of the material components are used (of course I'd say!), it breaks my build as androidx.compose.material is not a dependency of my application.
I guess that line should be removed!

Hi @vfsfitvnm 👋
Thanks for reporting.
Yes, you are right, this issue was already fixed in branch main-multiple-cores which will deal with dependencies in a much better way and will be the branch that will originate the next release version.
This will be a pretty big release that will change a lot of internal things and some minor APIs (also adds new features like being able to use Parcelables as navigation arguments, etc). So it will take me some time to release as I want to update all documentation on the wikis, etc.
Until then, I hope this doesn't block you. If you are still in the testing phase, maybe you can temporarily add that dependency.
Sorry for the inconvenience and thank you so much again for reporting!

Hi, thanks for the quick reply!
I just added the dependency as you said 😌


Add option to copy textures to export directory

This would work well when combined with #213

Basically covered by texture converter option to save to a different directory.


Use ? instead of * for search wildcard

Might help to differentiate traffic.

Does it work the same?! :o

That's an interesting trick, cool.

The default search is "Begins With", and ? is a wildcard that matches any single character...


Fix docs for cargo publish --dry-run vs cargo package

In latest nightly at least, cargo publish --dry-run and cargo package are not equivalent:
e@e egui-tetra2 % cargo publish --dry-run
    Updating crates.io index
error: crate<EMAIL_ADDRESS>already exists on crates.io index
e@e egui-tetra2 % cargo package
   Packaging egui-tetra2 v0.5.1 (/Users/e/Documents/GitHub/egui-tetra2)
    Updating crates.io index
    Packaged 19 files, 135.3KiB (37.7KiB compressed)
   Verifying egui-tetra2 v0.5.1 (/Users/e/Documents/GitHub/egui-tetra2)
...

IIUC by having https://github.com/rust-lang/cargo/pull/14742, this PR is no longer. Thanks for the contribution anyway!


Vulnerability roundup 106: envoy-1.16.4: 4 advisories [8.3]

search, files

[ ] CVE-2021-32777 CVSSv3=8.3 (nixos-21.05)
[ ] CVE-2021-32779 CVSSv3=8.3 (nixos-21.05)
[ ] CVE-2021-32778 CVSSv3=7.5 (nixos-21.05)
[ ] CVE-2021-32781 CVSSv3=7.5 (nixos-21.05)

CVE details
CVE-2021-32777
Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions when ext-authz extension is sending request headers to the external authorization service it must merge multiple value headers according to the HTTP spec. However, only the last header value is sent. This may allow specifically crafted requests to bypass authorization. Attackers may be able to escalate privileges when using ext-authz extension or back end service that uses multiple value headers for authorization. A specifically constructed request may be delivered by an untrusted downstream peer in the presence of ext-authz extension. Envoy versions 1.19.1, 1.18.4, 1.17.4, 1.16.5 contain fixes to the ext-authz extension to correctly merge multiple request header values, when sending request for authorization.
CVE-2021-32779
Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions envoy incorrectly handled a URI '#fragment' element as part of the path element. Envoy is configured with an RBAC filter for authorization or similar mechanism with an explicit case of a final "/admin" path element, or is using a negative assertion with final path element of "/admin". The client sends request to "/app1/admin#foo". In Envoy prior to 1.18.0, or 1.18.0+ configured with path_normalization=false. Envoy treats fragment as a suffix of the query string when present, or as a suffix of the path when query string is absent, so it evaluates the final path element as "/admin#foo" and mismatches with the configured "/admin" path element. In Envoy 1.18.0+ configured with path_normalization=true. Envoy transforms this to /app1/admin%23foo and mismatches with the configured /admin prefix. The resulting URI is sent to the next server-agent with the offending "#foo" fragment which violates RFC3986 or with the nonsensical "%23foo" text appended. A specifically constructed request with URI containing '#fragment' element delivered by an untrusted client in the presence of path based request authorization resulting in escalation of Privileges when path based request authorization extensions. Envoy versions 1.19.1, 1.18.4, 1.17.4, 1.16.5 contain fixes that removes fragment from URI path in incoming requests.
CVE-2021-32778
Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions envoy’s procedure for resetting a HTTP/2 stream has O(N^2) complexity, leading to high CPU utilization when a large number of streams are reset. Deployments are susceptible to Denial of Service when Envoy is configured with high limit on H/2 concurrent streams. An attacker wishing to exploit this vulnerability would require a client opening and closing a large number of H/2 streams. Envoy versions 1.19.1, 1.18.4, 1.17.4, 1.16.5 contain fixes to reduce time complexity of resetting HTTP/2 streams. As a workaround users may limit the number of simultaneous HTTP/2 dreams for upstream and downstream peers to a low number, i.e. 100.
CVE-2021-32781
Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions after Envoy sends a locally generated response it must stop further processing of request or response data. However when local response is generated due the internal buffer overflow while request or response is processed by the filter chain the operation may not be stopped completely and result in accessing a freed memory block. A specifically constructed request delivered by an untrusted downstream or upstream peer in the presence of extensions that modify and increase the size of request or response bodies resulting in a Denial of Service when using extensions that modify and increase the size of request or response bodies, such as decompressor filter. Envoy versions 1.19.1, 1.18.4, 1.17.4, 1.16.5 contain fixes to address incomplete termination of request processing after locally generated response. As a workaround disable Envoy's decompressor, json-transcoder or grpc-web extensions or proprietary extensions that modify and increase the size of request or response bodies, if feasible.

Scanned versions: nixos-21.05: 6120ac5cd20.
Cc @lukegb

NixOS 21.05 is EOL.


[PE-D][Tester B] Can deduct salary to negative number

The user is currently able to deduct salary to a negative number. This might require a warning to present errors.

Labels: type.FunctionalityBug severity.Low
original: InfiBeyond/ped#13

Already mentioned in ug that the value must be positive.


Fix builder.rs example

I noticed that the builder.rs example is using the wrong entry type for the password example.

Good catch, thanks!


DiagramWidget doesn't render after wrap in div

Hello.
I have a problem with DiagramWidget. When I'm trying to wrap it in div it doesn't render.
Code like this works:
return(<RJD.DiagramWidget diagramEngine={diagramEngine} />);
but when I trying to add e.g. navbar, and I need to wrap it in any div my diagram doesn't render.
return(
<RJD.DiagramWidget diagramEngine={diagramEngine} />
);
What I'm doing wrong?
Thank from advance for your help!

Ok, I know what was wrong.
It was about CSS, which I have copied from demo4 and display: flex.


Snaps interface openstack

What does this PR do?
This PR  create a separate br-ex network configuration file during the deployment of openstack.
On cleanup br-ex.cfg is removed from the /etc/network/interfaces.d folder and target hosts are rebooted
to fallback to static network configuration.
Do you have any concerns with this PR?
No
How can the reviewer verify this PR?
by deploying and cleaning openstack setup
Any background context you want to provide?
NA
Screenshots or logs (if appropriate)
Questions:

Have you connected this PR to the issue it resolves?
#150 and #156
Does the documentation need an update?
yes
Does this add new Python dependencies?
No
Have you added unit or functional tests for this PR?
No
Does this patch update any configuration files?
No

Regarding the issue on kola_toolbox, We have checked the CableLabs setup and found that pull_from_hub was set as “no”.
It seems that there is some issue in the kolla opensource code with kolla_toolbox, because of which deployment is failing.
We suggest you to please change the pull_from_hub tag to “yes” and re-deploy the openstack.
Please try with this change, and let us know if still the deployment is failing.
Also, apart from kolla_toolbox issue, there was some other issue seen in cleanup of the interface file, which we have checked in in this pull request.

@RandyLevensalor PR has been updated as per the requested changes

We have decided to postpone and re-work this patch at a later date.  Closing this PR and leaving the branch and issue open.


Will tf.reshape() perform extra memcopy in tensorflow gpu backend?

mediate_op = tf.some_op(inputs)
output_op = tf.reshape(mediate_op, [128, -1])

In terms of device memory occupation, is tf.reshape performed in place (reuse the data memory of mediate_op)?

@ghostplant
Please, fill issue template.
Request you to share colab link or simple standalone code to reproduce the issue in our environment.It helps us i localizing the issue faster. Thanks!

From the docs:

The tf.reshape does not change the order of or the total number of elements in the tensor, and so it can reuse the underlying data buffer. This makes it a fast operation independent of how big of a tensor it is operating on.

Closing this issue since its resolved. Feel free to reopen if necessary. Thanks!

Thanks! I also verified that.


[Bug] IssueLabelBot no longer works

🐞 Bug Report
Describe the bug

The document references https://github.com/marketplace/issue-label-bot but the owner shut it down:

https://github.com/machine-learning-apps/Issue-Label-Bot

The Issue label bot is no longer live. You can still view the code, but we have taken down the bot because of related infrastructure costs

Is this a regression?

Yes it probably did once work.

To Reproduce
No idea what to write here.

Expected behaviour

To automatically apply issue labels but it doesn't

Media prove

Your environment

OS:
Node version:
Npm version:
Browser name and version:

Additional context

Thanks for letting me know. I will try to find any similar bots or any solution.
I will let you know.

If no similar bot is found, then I guess is not a big deal as the issue templates apply some labels depending on the issue selected. Anyways I'll do some research. Thanks!


MTG-12 use custom detekt rule

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1233 (85f0ca8) into develop (120224b) will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #1233      +/-   ##
===========================================
+ Coverage    82.31%   82.33%   +0.02%
===========================================
  Files          353      353
  Lines        11795    11802       +7
  Branches      2007     2008       +1
===========================================
+ Hits          9708     9716       +8
+ Misses        1475     1474       -1
  Partials       612      612

Impacted Files
Coverage Δ

...rsistence/file/batch/PlainBatchFileReaderWriter.kt
86.27% <0.00%> (-2.94%)
:arrow_down:

...android/log/internal/domain/DatadogLogGenerator.kt
94.63% <0.00%> (-1.34%)
:arrow_down:

.../kotlin/com/datadog/android/v2/core/DatadogCore.kt
89.86% <0.00%> (-0.46%)
:arrow_down:

...n/kotlin/com/datadog/android/ktx/rum/ContextExt.kt
100.00% <0.00%> (ø)

...in/com/datadog/android/log/internal/LogsFeature.kt
88.71% <0.00%> (ø)

...datadog/android/coil/DatadogCoilRequestListener.kt
100.00% <0.00%> (ø)

...android/v2/core/internal/DatadogContextProvider.kt
81.54% <0.00%> (ø)

...android/rum/internal/ndk/DatadogNdkCrashHandler.kt
87.68% <0.00%> (+0.49%)
:arrow_up:

.../kotlin/com/datadog/android/ktx/tracing/SpanExt.kt
88.89% <0.00%> (+2.22%)
:arrow_up:

...droid/rum/tracking/FragmentViewTrackingStrategy.kt
78.85% <0.00%> (+3.85%)
:arrow_up:

... and 2 more


189 part2 max probabilities

#189
Partial PR, still need to do CLI tests.
Testing:

[ ] Ran tests and they passed OK
[ ] Added new tests for the new feature(s)

Links to acceptance test data on Jira.


OCM-10711 | test: fix ids:73449, 74403

OCM-10711

/test coverage

@AkashKanni Did you run them with your fix? Could paste the log here if yes.

/lgtm


[RFE] Reduce the App VM sizes

Reduce the App VM sizes (Currently each has 18GB disk, only 5GB required)

Uploading RHEL 7.5 vmdk ...

Reduced LB and DB to 4GB


Avoid hardcoded limit of 20 in projection evaluation

Hi there,
I want to propose a breaking API change, about moving resource.Conf in github.com/rs/rest-layer/resource to conf.Conf in github.com/rs/rest-layer/resource/conf. The reason for this is that I want to use resource configuration in schema/query package, that currently results in cyclic dependency.
More specifically I want to remove this constant:
https://github.com/rs/rest-layer/blob/3f2cd5df9e8e6690c56f806710ef53048109c323/schema/query/projection_evaluator.go#L336
And use conf.PaginationDefaultLimit in connected resource.

I see your point. Having it set to 20, I agree seam a bit arbitrary; it should probably rely on resources set for the specific resource.
However, I think the Conf is on the correct package (It's configuring a resource), and moving it to a separate package doesn't really make sense.
Besides, there are  other issues with the current dependency tree that would make sense to solve at the same time. I.e. the query package is relying on resource.Item and resource.ItemList being translated to simple interface types containing the payload only, and define a separate Resource interface to glue this together.
It might be worthwhile reviewing the two packages resource and query, to find out if they could either be merged, or renamed & split in a different way so that the dependence cycle (including workarounds) is broken.
PS! The schema package should not need depend on the query package; we can solve dependencies with a schema instead of a query, and it would work equally well.

I acknowledge the problem, but I think we need to come up with a better solution. I am thus going to close this issue now . Feel free to create a new issue with an alternate suggestion for restructuring.

Closing is okay, but I feel that this is major issue, and should be addressed soon, before any major package refactoring. Currently I am using a fork of rest-layer just because of this limit of 20, and more importantly I have removed validation for the connected resources, because I rely on Context and this validation uses just Context.Backgound() which is critical for me. It could have been superb if this validation especially can be turned ON/OFF via config.

Let's reopen/rename it then; just doing a bit of a cleanup in the issue tracker.

I rely on Context and this validation uses just Context.TODO() which is critical for me.

Ok I reopened #192 as well; I suppose we still need to track it. It's really a bug, not an enchantment.

Thanks. I will think about it more, when I have some time.

Here is a suggestion (breaking change) for solving the circular dependencies:

In package Schema, replace the Dependency query.Predicate field with Dependency *schema.Schema. See JSON Schema for documentation/help.
Move the query package from schema/query to resource/query.
Now, we can, as a bonus, remove all wrapper types in the query package that replaces the direct use of resource.Item ++/

I would milestone this for a 0.3 release, if we can get #213 merged first so we can push out a release with that.

Cool, thanks! Will dig around when have some time.  But maybe a query interface could be defined for use in the resource package.

Maybe the least invasive change would be to add a GetDefaultLimit to the existing Resource interface within the Query package?


Make the user docs for the valve

I think the documentation for DMC's Siemens Open Library is a good reference for documenting the library. I found their documentation very helpful when first starting out using their library. Example below:
4- Siemens Open Library - Detailed Block Overview.pdf

Yes. The Rockwell PlantPax object library docs are also a good example.

...Example below:
4- Siemens Open Library - Detailed Block Overview.pdf

See Section 7 starting p. 50 for valve tags and diagrams

Yes. The Rockwell PlantPax object library docs are also a good example.

https://literature.rockwellautomation.com/idc/groups/literature/documents/rm/proces-rm001_-en-p.pdf
See valve examples on p. 34-35. Not sure if this is the documentation you had in mind for PlantPax

No Rockwell/PlantPax has dedicated docs for the objects.
This is an older version example of the valve:
https://literature.rockwellautomation.com/idc/groups/literature/documents/rm/syslib-rm014_-en-e.pdf
But I can't find the latest one.
It's quite extensive. Probably a bit too much.


Treat entries with constant type as constant

This should be allowed:
cdef extern from *:
    const long N

cdef int arr[N]

This is required to fix a testcase in #2016.

Isn't this only legal in c99?

Isn't this only legal in c99?

First of all, the answer to that question really shouldn't matter. Even if it is only legal in C99, Cython should just accept it and let the C compiler complain if needed.
Now, about your actual question: maybe you are thinking about variable-length arrays? In this case, the length is a constant.

IIRC, the notion of is_const here means known at compile time, which is very different meaning than the C const type. (I don't recall everywhere it's used, but I'm pretty sure it's more broad than array sizes...) This seems like the wrong fix, or at least we should verify it doesn't widen things we don't want widened. (E.g. is the following now legal
cdef const int f(int)
cdef int foo() except f(5)

?)
As for the C99 case, I'm generally in favor of only generating legal code rather than requiring the user to also trip over C compiler errors (especially if C files are compiled elsewhere). Yes, this isn't always possible, but it would be nice to emit a nice warning (error?) about a minimum standard required if we use these features rather than an error in the middle of auto-generated code.
If we want to allow this C99 feature, that's a separate (valid) feature request, but shouldn't be limited to const types. The notion of "only allow dynamic arrays if the runtime varible is declared as a const type" is strange at best, as well as overly restrictive.

IIRC, the notion of is_const here means known at compile time, which is very different meaning than the C const type.

As far as I know, Cython doesn't really have a notion of "name whose value is known at compile time". So I'm using a const variable as proxy for that.
What is the correct way to deal with LONG_MAX in Cython? Technically, it's a #define but Cython does not understand that. So, the best (only?) way to declare it in Cython is as
cdef extern from "<limits.h>":
    const long LONG_MAX

even though it's not actually a variable.

Though they're not really enums, there is an issue that generally enums may
not fit into a long. Perhaps we should be able to declare something like
cdef unsigned long enum: ...
which we could use here and make enums more flexible.
On Nov 25, 2017 2:09 PM, "jdemeyer"<EMAIL_ADDRESS>wrote:

IIRC, the notion of is_const here means known at compile time, which is
very different meaning than the C const type.
As far as I know, Cython doesn't really have a notion of "name whose value
is known at compile time". So I'm using a const variable as proxy for
that.
What is the correct way to deal with LONG_MAX in Cython? Technically,
it's a #define but Cython does not understand that. So, the best (only?)
way to declare it in Cython is as
cdef extern from "<limits.h>":
const long LONG_MAX
even though it's not actually a variable.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cython/cython/pull/2020#issuecomment-346966334, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdqgdLJVy1ZG9cV7cF6tIco9-uW2YZyks5s6IIfgaJpZM4Qpx4Q
.

cdef unsigned long enum: ...

What's wrong with "const" for this use case?

Mostly, this seems a rather big change to work around the fact that enums don't always fit into ints, which it seems we should fix more directly. (Had these been literal enum values, that would have been the natural change, and one may need to wrap such enums.) In C, these behave more like enum values in the sense they can appear anywhere a literal appears, which is more places than a const int can appear (e.g. in switch statements). (On a quick check it looks like we also use check_const to validate exception check values and enum definitions, so maybe it's not that bad.) However if we (finally) support integer template arguments this is a common case that would make it easier to generate illegal code (though using an actual constant, like MAX_LONG, would be totally legal).
In addition, if we want to allow C99 style arrays at all, we should not restrict them to const-typed sizes.
So either fixing Cython to understand that enums may be larger than ints or dropping the (compile-time) constant restriction on array sizes both seem better and safer choices than redefining check_const.


Add generator for System.Version

In our project, we naively pointed AutoBogus at a type containing a Version property, and the resulting Version object was initialized in an odd way, with Build and Revision set to -1 and no bogus data in Major or Minor. This PR adds a default VersionGenerator to AutoBogus so that Version objects are generated with valid (non-negative) random integers in all properties.
A unit test verifies the new functionality.

Force push: https://github.com/logiclrd/AutoBogus/compare/1413e22..94ec2e3

Okay I was too quick on the trigger with that, a bunch of unit tests now fail with this change and it appears to be because the testing infrastructure cannot abide a primitive set to its default value, and the version's .MajorRevision has value 0 == default(short). Hmm...


scope/cortex: metric queries do not filter for node type

This concerns the k8s types deployment, stateful_set, and cron_job. If they share the same name and namespace, we will end up with pods not being owned by that specific node. The metric kube_pod_owner from kube-state-metrics should reveal that info.

daemon-set too.

The daemon_set's pod name is different, though. It is name-hash and not name-id-hash as for the others. Doesn't hurt to explicitly specify the type, though.


python3Packages.pytest_6: 6.0.1 -> 6.1.0

Motivation for this change
https://docs.pytest.org/en/stable/changelog.html
The say they follow semantic version, yet have a breaking change section every minor release... odd
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

seems to break pytest_xdist_2

Pytest is at 6.1.2 now.

Pytest is at 6.1.2 now.


[New Port Request] cbc

Library name: cbc
Library description: COIN-OR Branch-and-Cut solver
Source repository URL: https://github.com/coin-or/Cbc
Project homepage (if different from the source repository):
Anything else that is useful to know when adding (such as optional features the library may have that should be included): ortools depends on this.

the port is not mine
did not test the port
cbc.zip

Create by Adobe Flash & ActionScript 3.0
Description:
Drag the black balls to activate the whites.. Sounds easy? Try it!
white ball is activated if the lines pass through it! To complete the level you have to activate all grey balls.
Features:
◆ unlimited levels
◆ amazing design
◆ original soundtrack
◆ increasing difficulty
Screenshots

If you wish to add this port in the future, you can reopen this issue and continue related PR, but we're closing it for now.


Change title to RobloxFastFlagRandomizer 🙏🙏🤔🤔🤔🤔

Add your description here...

original name better khalid

nuu we tell the people its fast


Refactoring use-echarts hook

📝 Description
This pull request includes improvements to the EChart component and introduces several utility functions to enhance the functionality and maintainability of the ECharts integration in the codebase.
⛳ Current behavior (updates)
The current use-echarts.tsx file includes a lot of code and is hard to understand and maintain. Also functions unrelated to state are unitized within the hook. Which has performance implications.
🚀 New behavior
The changes include the addition of detailed documentation, restructuring of the component's initialization and event handling, and the introduction of utility functions for ECharts setup and configuration.
💣 Is this a breaking change (Yes/No)
No
📝 Additional Information
This was tested using the project in the example folder. During my testing I was unable to find any regressions that this refactoring me cause

@hugocxl any chance at getting this reviewed? It will also solves #37


iOS Mobile Status Bar

Is there a way to maintain the functionality of "apple-mobile-web-app-status-bar-style" while using iScroll?
Since the page isn't really 'scrolling', mobile safari doesn't shrink the status bar.

If you have height 100% layout and want to minimize mobile browser status bar, you should use something like this: https://github.com/scottjehl/Hide-Address-Bar

This method no longer works: https://github.com/scottjehl/Hide-Address-Bar/issues/7


Added $scope $watcher for the chart's options.

Added $scope $watcher for the chart's options that reflects the updating behavior of the data.  This is especially useful when loading the information asynchronously or using a single canvas element for multiple charts.  I simply pulled the initialization code out of the data $watcher and put it in a standalone function that gets called by both the data and options $watchers.

PR addressing multiple issues are rarely merged (IMO).
So keep it simple to increase the chances of your PR to be merge.

Sorry for the extra fixes in there.  I forgot I had made this PR.  We've been using my fork via bower in a project at work and we've just been using it as our 'up-to-date' version.


Bug in Vienna 3.9.0 - Open links in external browser

Clicking on a link in the internal browser that opens in the external browser, disables up-down keys navigation in the Headlines section.
In Vienna 3.8.8 I can click on the title of an article or on any link in the internal browser, it opens in the background in the external browser (Safari) and I can continue using the up-down keys to go to the previous or next headline.

Vienna version 3.9.0
OS version: macOS 12.7.3

Will need to investigate this:

opening a link through one of the contextual menu items will keep the focus to the article list ;
opening a link with a direct click will make the article list lose the focus.

The 3.8.8 version had code which returned first responser responsibility to the article list.
Will probably have to implement an equivalent through WebKitArticleView's WKNavigationDelegate
Any advice, @Eitot or @TAKeanice ?

Fixed in 3.9.1


File Save Error

I was running my analysis on the sidecar worker today, and ran into this pop-up in JupyterLab several times.

The first time it popped up, the analysis seemed to continue on. The second time it popped up (around 59%), it seemed to hang forever. I'm using the analysis-casa.ipynb file from the tutorial repository, which may be somewhat outdated.

I ended the run when it seemed to hang at 59%, and started a run on one of the smaller examples. It continued to hang at 0%, so it seems that if this error pops up it fries your ability to run analyses until you do a server restart.

Just confirming that this error is still persisting after all the power outage problems have been resolved, so I don't think it's related to that. I was, however, able to finish a run on my analysis despite it popping up, so the hanging problem might be separate from this error pop-up (and that might have been related to the power outages).

Another similar pop-up is this, which occasionally comes up in the middle of an analysis run:

I can at least understand what this one means, though it doesn't seem to be true. If I just hit "dismiss" and ignore it, the analysis continues to run and I can continue to do new runs afterwards without a server restart.

I think this problem was resolved, please reopen this GH issue again.


After updating to 1.0, Litecoin mainnet, no prompt to unlock wallet

After updating to 1.0, Litecoin mainnet, no prompt to unlock wallet, instead this:

After exiting this screen with control-c, the prompt to unlock lnd appears, some users might not know how to proceed though.

jikes - other litecoin mainnet updates were reported working - so not sure where this is coming from.
Would recommend the hard way of updating .. make backup of LND data dir, setup fresh Litecoin Blitz 1.0 and then play the backup back - see FAQ: https://github.com/rootzoll/raspiblitz/blob/master/FAQ.md#how-to-backup-my-lightning-node

pls close this


docs(DIST-1999): Add docs for chaining typeforms, update callbacks docs

:tada: This PR is included in version @typeform/embed-v2.4.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


⚠ Bofrost.be has degraded performance

In d96a48d, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1065 ms

Resolved: Bofrost.be performance has improved in f1d069d.


[1.21] [Neoforge] Missing Crusher recipe Blazerod

Describe the bug
The Blazerod to Blaze powder using a crusher daemon is missing
Expected behavior
There should be a recipe output instead of a barrier block
Screenshots

System (please complete the following information):
Occultism Version: 1.133.2
OS: Windows
Minecraft Version: 1.21

Hmm that indicates that the recipe exists but that blaze dust is not tagged as a dust. Maybe it is safe to just make the recipe output the item here, I'll check!


Timeout errors since updating to 18.0.x with Chrome V124/125

Timeout errors since updating to 18.0.x with Chrome V124/125
Description
My code runs in a .net 4.8 executable which is launched by a Windows Service running under my Windows Admin account

    Dim opts As New LaunchOptions With {
        .Headless = True
    }
    Dim browserFetcher = new BrowserFetcher
    Await browserFetcher.DownloadAsync()

    Using browser = Await Puppeteer.LaunchAsync(opts)
    ...

It hangs on the LaunchAsync line and eventually gives the timeout error below.  If I tell Puppeteersharp to use Chrome Version 123, things work as normal again, but with Versions 124/125 I get the errors. Packaging and delivering Chrome 123 is not an option for me. Any Ideas?
ERROR:
System.AggregateException: One or more errors occurred. ---> System.TimeoutException: Timeout of 180000 ms exceeded
   at PuppeteerSharp.Helpers.TaskHelper.<WithTimeout>d__12`1.MoveNext() in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Helpers/TaskHelper.cs:line 185
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at PuppeteerSharp.Cdp.CdpCDPSession.<SendAsync>d__13.MoveNext() in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Cdp/CdpCDPSession.cs:line 112
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at PuppeteerSharp.CDPSession.<SendAsync>d__34`1.MoveNext() in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/CDPSession.cs:line 44
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at PuppeteerSharp.Cdp.CdpPage.<PdfInternalAsync>d__88.MoveNext() in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Cdp/CdpPage.cs:line 829
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at PuppeteerSharp.Page.<PdfAsync>d__203.MoveNext() in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Page.cs:line 382
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at WFS.ReportTools.VB$StateMachine_5_RenderURL.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at WFS.ReportTools._Closure$__6-0.VB$StateMachine___Lambda$__0.MoveNext()
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at WFS.ReportTools.CreateReportGoJS_PDF_Puppeteer(String pageSize, String pageOrientation, Boolean multiPage, String mapType, String reportName, String userName, String mapDataFileName, Boolean bPackage, String PackageName)
---> (Inner Exception #0) System.TimeoutException: Timeout of 180000 ms exceeded
   at PuppeteerSharp.Helpers.TaskHelper.<WithTimeout>d__12`1.MoveNext() in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Helpers/TaskHelper.cs:line 185
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at PuppeteerSharp.Cdp.CdpCDPSession.<SendAsync>d__13.MoveNext() in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Cdp/CdpCDPSession.cs:line 112
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at PuppeteerSharp.CDPSession.<SendAsync>d__34`1.MoveNext() in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/CDPSession.cs:line 44
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at PuppeteerSharp.Cdp.CdpPage.<PdfInternalAsync>d__88.MoveNext() in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Cdp/CdpPage.cs:line 829
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at PuppeteerSharp.Page.<PdfAsync>d__203.MoveNext() in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Page.cs:line 382
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at WFS.ReportTools.VB$StateMachine_5_RenderURL.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at WFS.ReportTools._Closure$__6-0.VB$StateMachine___Lambda$__0.MoveNext()

Versions

PuppeteerSharp 18.0.0 and 18.0.1
.NET framework 4.8

Seeing the same issue here on PuppeteerSharp 18.0.1 with Chrome 125, also running in a Windows Service. Works fine on 18.0.0 with Chrome 124, so our suspicion is that this could be related to the Windows permissions issue in https://github.com/hardkoded/puppeteer-sharp/pull/2637.

Chrome V126 is now available but has the same errors with PuppeteerSharp 18.0.x. Interestingly, if I go back to PuppeteerSharp 10.1.0 and point at the Chrome V126 exe, it works fine with no errors... So, is there are change within Puppeteer that could solve this issue?

Thank you for the report. I'm on vacation right now. I'll take a look at it on Monday!

Just to add more information, I also ran into the Timeout issues with PuppeteerSharp 18.0.1 running on .NET 8 on a Windows IIS environment.  When I reverted back to version 18.0.0 everything started working again.

@aerichmond can you try using Chrome 124?

@aerichmond can you try using Chrome 124?

Yes.  Specifying the Chrome 124 path does work also.

@ezanker @aerichmond @janode maybe the user executing puppeteer doesn't have permissions to run this piece of code?
I tried doing something that not even the puppeteer upstream is doing. They are telling users to do this on their own.

I ran the icacls command on the "..Chrome\Win64-125.0.6422.76\chrome-win64" folder but am still getting the timeout errors.

Same here; running icacls is fine, but still getting timeouts when trying to printPdf.


Allow to send non confirmable requests via UDP

In udp/client/clientconn.go all messages are set to "Confirmable"
See:
func (cc *ClientConn) writeMessage(req *pool.Message) error {
	req.SetMessageID(cc.getMID())
	req.SetType(udpMessage.Confirmable)

I don't see the reason why. It removes the ability to send non confirmable messages via UDP.
When just removing the line req.SetType(udpMessage.Confirmable) at least some tests are failing. Seems like the client can't deal with not getting any response and should return nil rather than time out.

I found some issues with no-confirmable messages and created a pull request.
I'm not happy with the UDP Message "Type" field that gets lost in generic packages like net/blockwise.


ADC2 gives incorrect reading after light sleep of more than 90 seconds. (IDFGH-6252)

Environment

Development Kit: ESP32-S2-Kaluga-1
Kit version (for WroverKit/PicoKit/DevKitC): V1.3
Module or chip used: ESP32-S2-Wrover
IDF version: v4.3.1 (Stable)
Build System: idf.py
Compiler version: xtensa-esp32-elf-gcc (crosstool-NG esp-2020r3) 8.4.0
Operating System: Linux
Using an IDE?: No
Power Supply: external 5V-2A

Problem Description
ADC2 Reading is incorrect after light sleep of more than 90 seconds. I am giving stable 0.55V on channel 3 of ADC2. It gives me raw value of 559 when board is not in light sleep but if board enters into light sleep for more than 90 seconds then after wake up ADC2 channel 3 reading 1490 and then it always remains the same. If I use 60 seconds light sleep then issue does not occur.
Expected Behavior
It should give correct value as it is without light sleep.
Actual Behavior
It is giving incorrect value after waking up from light sleep.
Steps to reproduce

Take the sample ADC2 example.
GIve 0.55V or any other voltage you want to channel 3 of ADC2.
Measure RAW value from ADC2. It should be correct. In my case, it was 559 (after voltage conversion ) which is almost equal to 0.55V.
now put esp32s2 into light sleep for more than 90 second.
after wake up, again take raw reading. now it is 1490 (after voltage conversion ) , while input voltage at channel is still 0.55V.
I also checked the input voltage on oscilloscope, it was always 0.55V.

Code to reproduce this issue
// the code should be wrapped in the ```cpp tag so that it will be displayed better.
#include "driver/adc.h"
#include "esp_adc_cal.h"
#include "esp_sleep.h"
#include "esp_log.h"
#include "driver/uart.h"

#define TAG    "ADC2"
#define DEFAULT_VREF    1100
#define NO_OF_SAMPLES   64          //Multisampling

static const adc_channel_t channel = ADC_CHANNEL_3;
static const adc_bits_width_t width = ADC_WIDTH_BIT_13;
static esp_adc_cal_characteristics_t *adc_chars;
static const adc_atten_t atten = ADC_ATTEN_DB_11;
static const adc_unit_t unit = ADC_UNIT_2;

static void check_efuse(void)
{
    if (esp_adc_cal_check_efuse(ESP_ADC_CAL_VAL_EFUSE_TP) == ESP_OK) {
        ESP_LOGI(TAG, "eFuse Two Point: Supported");
    } else {
        ESP_LOGE(TAG, "Cannot retrieve eFuse Two Point calibration values. Default calibration values will be used.");
    }
}

uint32_t drdGetBatVoltage(void)
{
    uint32_t voltage = 0;
    uint32_t adc_reading = 0;
    //Multisampling
    for (int i = 0; i < NO_OF_SAMPLES; i++) {
        int raw;
        adc2_get_raw((adc2_channel_t)channel, width, &raw);
        adc_reading += raw;
    }
    adc_reading /= NO_OF_SAMPLES;
    //Convert adc_reading to voltage in mV
    voltage = esp_adc_cal_raw_to_voltage(adc_reading, adc_chars);
    return voltage;
}

void drdAdc2Init(void)
{
    check_efuse();
    adc2_config_channel_atten((adc2_channel_t)channel, atten);
    vTaskDelay(20);
    adc_chars = heap_caps_calloc(1, sizeof(esp_adc_cal_characteristics_t), MALLOC_CAP_INTERNAL);
	if (adc_chars == NULL) {
		ESP_LOGE(TAG, "ADC INIT: Mem error");
		return;
	}
    esp_adc_cal_characterize(unit, atten, width, DEFAULT_VREF, adc_chars);
}

void app_main()
{
    drdAdc2Init();
    printf( "Voltage: %d\n", drdGetBatVoltage());
    printf( "Voltage: %d\n", drdGetBatVoltage());
    printf( "Voltage: %d\n", drdGetBatVoltage());
    printf( "Voltage: %d\n", drdGetBatVoltage());
    uint32_t batVoltage = 0;
    while (true) {
        batVoltage = drdGetBatVoltage();
        if (batVoltage < 875) {
            esp_sleep_enable_timer_wakeup(180000000); /* 180 seconds */
            printf("Entering light sleep: %d\n", batVoltage);
            uart_wait_tx_idle_polling(0);
            esp_light_sleep_start();
        } else {
            printf("Voltage become high %d\n", batVoltage);
        }
    }
}

Debug Logs
Voltage: 559
Voltage: 558
Voltage: 559
Voltage: 559
Entering light sleep: 559
Voltage become high 1490
Voltage become high 1491
Voltage become high 1490
...

Note that I am not using WiFi or BLE in my project.

I did some more digging and found that it does not happen on each ESP32S2 wrover. I have 6 Kaluga board. Only two of them is having this issue? Is this something related to calibration?

Any update on this? I am still facing this issue on some of the ESP32S2. It just give increased value. I am using automatic light sleep. Without automatic light sleep, it just works fine.

This issue is now critical for us in production phase. Is there any solutions for this? It is simply not working. Does it mean that we can not use ESP32S2 ADC in light sleep mode?

Hi @nilesh-dryad
Please do this, in hal/adc_hal.c.
void adc_hal_set_calibration_param(adc_ll_num_t adc_n, uint32_t param)
{
    // if (param != s_previous_init_code[adc_n]) {
        adc_ll_calibration_init(adc_n);
        adc_ll_set_calibration_param(adc_n, param);
    //     s_previous_init_code[adc_n] = param;
    // }
}

This is just a temp fix. Final fix will be merged to Master then v4.3

@Icarus113 Your fix works in my initial test. I will test this with all of my boards which were giving wrong ADC results before. I will also test it with different input voltages


[Question] Remote ssh server no more session channel, please increase sshd_config MaxSessions

Question
centos服务器监控，运行了有一段时间了，最近突然报这个错误，并且监控显示【不可用】，但是通过ssh方式连接服务器是没有问题的。
后来调整hertzbeat的配置【复用连接】，将其关闭，现在又变得好使了。
请问这个【复用连接】的作用是什么。

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Question
Centos server monitoring has been running for a while. Recently, this error suddenly reported, and the monitoring showed [Unavailable], but there is no problem connecting to the server through ssh.
Later, I adjusted the configuration of hertzbeat [Reuse Connection] and turned it off, and now it works fine again.
What is the function of this [reuse connection]?

【复用连接】就是一直复用保持一个ssh tcp链接，但是长时间运行在某些环境有可能server因为其它原因断开保持 但是client没有察觉 导致出链接失败的现象

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

[Reuse connection] is to reuse and maintain an ssh tcp link. However, if it runs for a long time in some environments, the server may be disconnected due to other reasons, but the client is not aware of it, resulting in a link failure.

We had the same problem in our environment, even after turning off the "Reuse connection" option, we still couldn't connect, and restarting the target server's sshd service didn't work, but only after restarting hertzbeat could we connect!

Got it, we will follow


Fixed falcoctl image-value location

Checklist

[ ] Update changelog in CHANGELOG.md.
[ ] Make sure values.yaml and values.schema.json are valid.

Important: After this PR is tested and approved, ensure you "Squash and Merge" unless you are updating a subtree. The release automation in use on this repository relies on squashing, but git subtrees will be lost if squashed. This repo allows both, so you may need to change the merge type when merging.

I merged this because I needed to fix a cluster


adhoc db calls for specific tasks

Currently to display all the studies we are doing multiple DB calls because we are using the object methods to retrieve all this info. Ideally, somewhere, we should have some special methods where we can retrieve certain information, like this, without having to do multiple calls.

closed by: https://github.com/biocore/qiita/pull/1831


[BEAM-8191] Fixes potentially large number of tasks on Spark after Flatten.pCollections()

In the Spark runner (Beam 2.14.0 and 2.15.0), a Flatten.pCollections() PTransform is translated into a Spark union operation. This union will create a potentially large number of partitions in the RDD that can overload the driver.
This PR does a coalesce operation after the union, which will reduce the number of partitions in the RDD at virtually no cost.
See the JIRA ticket for more detail:
https://issues.apache.org/jira/browse/BEAM-8191

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @iemejia @dmvk

Oups sorry for late answer, @RyanSkraba can you PTAL.

stale bot calm down this fix seems worth the attention still


UX Assurance - Request Description - Front End Fixes

UX Assurance - Request Description - Front End Fixes
Series of front end changes to Request Descriptions Page so that UX better aligns with original designs and provides a more consistent user experience with consistent margin and spacing.

[x]  Issue with grey appearing instead of white below left nav
[x]  Alignment! There is a huge variety of alignment and spacing in this window. (All window "Request Details, Address and Contact Info, Request Description" should have same margins) All items in box should be aligned
[x]  Spacing between "Description History" and top of box should be decrease which will move all content up with it

Screenshot provided with notes to provide visual reference of changes

Checked this on Chrome and Edge, on different sized monitors, and in full screen and half screen modes - looks good!