False positive Lint/Syntax with ruby 3.3.1 and anonymous rest arg/keyword argument forwarding

Ruby 3.3.0 changed how anonymous args/keyword args can be used and the newly released 3.3.1 contains a bugfix for some unambiguous/unintentional places where they could be safely used, see: https://bugs.ruby-lang.org/issues/20090
Expected behavior
Rubocop is able to parse & validate code that runs on ruby 3.3.1
Actual behavior
Get Lint/Syntax errors such as:
Lint/Syntax: anonymous keyword rest parameter is also used within block
Lint/Syntax: anonymous rest parameter is also used within block
Lint/Syntax: unexpected token $end
❯ bundle exec rubocop --debug
For /Users/<username>/repos/rubocop-repo: Default configuration from /Users/<username>/.asdf/installs/ruby/3.3.0/lib/ruby/gems/3.3.0/gems/rubocop-1.63.3/config/default.yml
Use parallel by default.
Running parallel inspection
Loading cache from /Users/<username>/.cache/rubocop_cache/d8000782e70b69f8ef9f890bf197e06093695a19/6d7a3b621ca1730e04accd938619e4bdab66cfb1/14b887b108489c87a0ce57f4b58361ea46a3fdc3
Loading cache from /Users/<username>/.cache/rubocop_cache/d8000782e70b69f8ef9f890bf197e06093695a19/6d7a3b621ca1730e04accd938619e4bdab66cfb1/88559496eb2db1f6bae77024cd89412cfad0a51c
Inspecting 2 files
Scanning /Users/<username>/repos/rubocop-repo/Gemfile
Loading cache from /Users/<username>/.cache/rubocop_cache/d8000782e70b69f8ef9f890bf197e06093695a19/6d7a3b621ca1730e04accd938619e4bdab66cfb1/14b887b108489c87a0ce57f4b58361ea46a3fdc3
.Scanning /Users/<username>/repos/rubocop-repo/test.rb
Loading cache from /Users/<username>/.cache/rubocop_cache/d8000782e70b69f8ef9f890bf197e06093695a19/6d7a3b621ca1730e04accd938619e4bdab66cfb1/88559496eb2db1f6bae77024cd89412cfad0a51c
F

Offenses:

test.rb:3:10: F: Lint/Syntax: anonymous keyword rest parameter is also used within block
(Using Ruby 3.3 parser; configure using TargetRubyVersion parameter, under AllCops)
    puts(**)
         ^^
test.rb:11:10: F: Lint/Syntax: anonymous rest parameter is also used within block
(Using Ruby 3.3 parser; configure using TargetRubyVersion parameter, under AllCops)
    puts(*)
         ^
test.rb:16:1: F: Lint/Syntax: unexpected token $end
(Using Ruby 3.3 parser; configure using TargetRubyVersion parameter, under AllCops)

2 files inspected, 3 offenses detected
Finished in 0.08651399999507703 seconds

Steps to reproduce the problem
Here's a sample test case: (there are more in https://bugs.ruby-lang.org/issues/20090)
def test(**)
  [1].each do
    puts(**)
  end
end

test(a: 1)

def bar(*)
  [1].each do
    puts(*)
  end
end

bar('1')

The code works on ruby 3.3.1 (and did on 3.2), but not 3.3.0:
❯ ruby --version
ruby 3.3.1 (2024-04-23 revision c56cd86388) [arm64-darwin23]
❯ ruby test.rb
{:a=>1}
1
❯ asdf local ruby 3.3.0
❯ ruby test.rb
test.rb:
test.rb:3: anonymous keyword rest parameter is also used within block (SyntaxError)
test.rb:11: anonymous rest parameter is also used within block
❯ bundle exec rubocop
Inspecting 2 files
.F

Offenses:

test.rb:3:10: F: Lint/Syntax: anonymous keyword rest parameter is also used within block
(Using Ruby 3.3 parser; configure using TargetRubyVersion parameter, under AllCops)
    puts(**)
         ^^
test.rb:11:10: F: Lint/Syntax: anonymous rest parameter is also used within block
(Using Ruby 3.3 parser; configure using TargetRubyVersion parameter, under AllCops)
    puts(*)
         ^
test.rb:16:1: F: Lint/Syntax: unexpected token $end
(Using Ruby 3.3 parser; configure using TargetRubyVersion parameter, under AllCops)

2 files inspected, 3 offenses detected```

RuboCop version
❯ bundle exec rubocop -V
1.63.3 (using Parser <IP_ADDRESS>, rubocop-ast 1.31.2, running on ruby 3.3.0) [arm64-darwin23]

This requires a new release from the parser gem: https://github.com/whitequark/parser/issues/1009

The versions ranges on rubocop allow for an updated version of the parser gem, https://github.com/whitequark/parser/releases/tag/v<IP_ADDRESS> - but anyone who's on 3.3.0 may want to stick with previous version of parser, it doesn't have differences for patch versions of ruby.


src: update to Node.js 9.9.0

@lance Was there something I missed last time with regards to publishing the docker image? I kinda recall something about the tagging of the images that might have changed.


Use the esm_score_multi_residue_mutations.py to calculate missense mutation LLR score

Can I use the script used for calculating PLLR(esm_score_multi_residue_mutations) to calculate the LLR score of the missense mutation?

@JieHe233 No, it will give you the PLLR of missense mutations, not the LLR. In theory PLLR is a valid score for missense mutations too, but we don't know how it compares in terms of performance (in our paper we only evaluated LLR scores in the case of missense mutations). I'd therefore recommend that you use the LLR scores for missense mutations, which can be obtained by the script esm_score_missense_mutations.

@nadavbra OK, I got it. Thanks for your reply.


on change, not refreshing the selected value in the select

Version: https://cdnjs.cloudflare.com/ajax/libs/select2/4.0.12/js/select2.min.js
Bootstrap 4.0 behind
It only happens when you submit a form, and then change the select to another option.
The select is part of an array of selects
As you can see I select manually the "27" but still is selected the "0"
I've also try .trigger('change.select2');

It looks like you didn't actually select the option using the selected property of the option or val() on the original select.

This appears to be more of a usage question than a bug report or common feature request.  As we continue to keep the Select2 issue tracker geared towards these two areas, bug reports and common feature requests, we are redirecting usage questions to other communities such as the mailing list, IRC, or Stack Overflow.

Hi Kevin as you can see in this video, the problem is not the val() set option.
And If I destroy the select2 and use the common select there is no problem.
https://youtu.be/HqxT7v8hF8k

I'm having the exactly same problem here.
The select2 was initialized on a "$(document).ready(function () { ..." block.
Then, on a callback function of a button click, after calling "$('#mySelect2field').val('BR').trigger('change');" when I click on the select2, I can see that the value is actually selected, but it is not being displayed in the "closed" select2.


Update l10n dependency and pull Mongolian

scratch-blocks part of https://github.com/LLK/scratch-l10n/pull/119

LGTM


Add 'report bug' / 'feature request' button.

@orishim could you make typeforms for these two?

@mrrobot16 is going to hop on implementing this.

Sure thing. Sounds good!

https://dorgtech.typeform.com/to/IaeXKv


clangd is very slow on WSL2

On WSL2, clangd's complement function is very slow, just a file like "hello world" takes about 1 second for me. However, on Windows this process is very fast. VSCode status bar shows that clangd spent a lot of time in "clangd: parsing includes, running EnumerateTweaks". When I switch from WSL2 to WSL1 the speed is back to normal. I'm not sure if this is a clangd issue, as it seems to be only clangd that is experiencing performance issues on WSL2, everything is fine when I write TypeScript or python on WSL2.
Microsoft C/C++ plugin also performs fine on WSL2, but I prefer to use clangd.
[/home/blade/projects/c_cpp]
/usr/lib/llvm-14/bin/g++ --driver-mode=g++ -std=c++20 -Wall -Wextra -Wno-unused-parameter -I includes -resource-dir=/home/blade/.vscode-server/data/User/globalStorage/llvm-vs-code-extensions.vscode-clangd/install/16.0.2/clangd_16.0.2/lib/clang/16 -- /home/blade/projects/c_cpp/main.cpp
I[13:24:50.329] Code complete: sema context Statement, query scopes [] (AnyScope=true), expected type <none>
I[13:24:50.329] Code complete: 27 results from Sema, 100 from Index, 15 matched, 0 from identifiers, 100 returned (incomplete).
I[13:24:50.331] --> reply:textDocument/completion(86) 414 ms
I[13:24:50.353] <-- textDocument/completion(88)
I[13:24:50.455] --> textDocument/clangd.fileStatus
I[13:24:50.517] <-- textDocument/codeAction(89)
I[13:24:50.569] <-- textDocument/foldingRange(90)
I[13:24:50.569] --> reply:textDocument/foldingRange(90) 0 ms
I[13:24:50.802] Code complete: sema context Statement, query scopes [] (AnyScope=true), expected type <none>
I[13:24:50.802] Code complete: 0 results from Sema, 4 from Index, 0 matched, 0 from identifiers, 4 returned.
I[13:24:50.803] --> reply:textDocument/completion(88) 449 ms
I[13:24:50.804] <-- textDocument/documentSymbol(91)
I[13:24:50.904] --> reply:textDocument/semanticTokens/full/delta(87) 587 ms
I[13:24:50.904] Skipping rebuild of the AST for /home/blade/projects/c_cpp/main.cpp, inputs are the same.
I[13:24:50.904] --> textDocument/publishDiagnostics
I[13:24:50.904] --> reply:textDocument/codeAction(89) 386 ms

I'm currently using Windows 11 (10.0.25931.1000) with WSL <IP_ADDRESS>.
clangd --version:
clangd version 16.0.2 (https://github.com/llvm/llvm-project 18ddebe1a1a9bde349441631365f0472e9693520)
Features: linux+grpc
Platform: x86_64-unknown-linux-gnu

I fixed this issue, it turned out that WSL2 kept Windows environment variables by default causing it to be slow. sorry about that.

I fixed this issue, it turned out that WSL2 kept Windows environment variables by default causing it to be slow. sorry about that.

@WiresawBlade Hello, I wanted to ask how you managed to solve this issue. I cannot quiet understand the comment you wrote. An elaboration would be pretty helpful for me.

@WiresawBlade Hello, I wanted to ask how you managed to solve this issue. I cannot quiet understand the comment you wrote. An elaboration would be pretty helpful for me.

@Sawansunar56 WSL2 by default adds windows environment variables to the system environment variables as well, and it is well known that IO operations between WSL2 and Windows are slow and for some reason, it slows down clangd.
Specifically, you need to edit the contents of the file /etc/wsl.conf . Use sudo chmod +w /etc/wsl.conf to make sure you have permission to edit it, then sudo vim /etc/wsl.conf , adding at the end of the file:
[interop]
appendWindowsPath = false

Finally, you need to reboot your WSL completely and then everything will be fine. But this has the side effect that you can no longer quickly initiate a remote connection by typing code . inside WSL.

@WiresawBlade Your issue clicked my brain yesterday and I figured that out as well. I use neovim in wsl, and treesitter was accessing nodejs from my windows, that was how I understood your comment about the environment.
Thank you very much, I could have gone forever not noticing this detail.


Unnecessary question mark

The question mark in the phrase "Discover who we are?" is unnecessary. When inviting the user to discover our website question mark doesn't seem required.

Please assign this issue to me.
Thank you

@Chinmayeep58 We are happy to know that you are contributing but we are accepting  big changes (level3 ) so that after same contributor can change minor changes


Styles issue

Hello i have a problem with the styles.

Hi.
Looks like the list-image directive is not working. Do you have any errors in the console?
There will be an update on the Material Version tomorrow evening. The issue will be obsolete then, I think.

Could you please check if the Sass is compiled for the directive too?

no console errors. How i can check if the sass is compiled?

I see - your on windows, right?
This should be fixed with the latest version, see Issue Nr. #18, fixed by @petersandor
I just published 0.1.4 on npm, I recommend to try the latest version, just run npm install to get it.
I am just working on a layout update and plan to release tomorrow.

ok thank you

Just reinstall the generator by running
npm install -g generator-material-app

and create a new application. Did that work for you?

No is not working

Are there any errors when running
yo material-app
gulp

i am getting this error on yo material-app

This looks like a permission problem to me. Could you grant read/write permissions to C:\Users\panayoitis\AppData\Roaming\npm-cache?
Sorry, I have no experience with node development under Windows.

I set the permissions. Now i dont get an error but the style is the same. No changes at all

I had the same issue with styles. I didn't have ruby or sass installed, and gulp build was showing some errors related. I installed ruby (Download Ruby) and installed sass gem install sass and finally do gulp build and styles should work fine.

Did you run gulp build before npm start ?

I also met this issue on Window, Run gulp styles command, ut there is no app.css to be generated in the client\styles directory.

Are you Chinese?
Recommand: 不要用windows开发!
Maybe you can try the new windows10 bash for linux?

I have a friend came up with this issue, too. I think what @donchoko said is the right answer

Thank stupidisum, Windows is not friend.


[ko] Translate concepts/storage/projected-volumes into Korean

This is a Feature Request
What would you like to be added
Translate content/en/docs/concepts/storage/projected-volumes.md into Korean
◾ Page: https://kubernetes.io/docs/concepts/storage/projected-volumes/
◾ File: https://github.com/kubernetes/website/blob/dev-1.24-ko.2/content/en/docs/concepts/storage/projected-volumes.md
Why is this needed
Not translated yet
Comments
/language ko
/assign

/triage accepted

Resolved by

#36381
#36804
#36810

/close


Adds basic space retrieval

I wanted to keep it simple and add only the methods I need. Maybe there will come more in the future :)
For now:

adds spaces endpoint
adds get all spaces method

looks good, feel free to add more :)


feat(split): add split function test

What problem does this PR solve?
This pull request adds partition split function tests.

LGTM


Sketch V45 crashes on Runner 'run' command

Version
0.3.0
Sketch version
v45
What is exptected?
Sketch simply crashes when i try to run the Runner. Both through the menu and "cmd+'".
The error log from Console.app when the problem occurred
https://pastebin.com/LmwKssu7

Yep, but the real reason is the Runner v0.9.1 and early are not compatible with Sketch 45, and now Runner v0.9.2 has been able to work with Sketch 45, so this issue was not caused by sketch-plugin-monster : )


TestBootstrapper forced Shopware install uses stale plugins configuration

PHP Version
8.2
Shopware Version
<IP_ADDRESS>
Expected behaviour
When I use TestBoostrapper and force a Shopware reinstall, the system should not execute any code from plugins before plugins are actually registered.
Actual behaviour
When \Shopware\Core\Kernel boots, it picks up active plugins from the database.
When TestBoostrapper forces a reinstall through system:install, the kernel is not rebooted after dropping the db - those active plugins are still registered, but their DB schema is now gone.
After system:install drops the db and runs the core migrations, it will call dal:refresh:index.
If one of those stale plugins had a service tagged shopware.entity_indexer, this service will be triggered, and i that service was not written defensively, it can crash with a missing DB table or a similar problem.
If that crash happens, the test database no longer contains the problematic plugin, so the next time TestBootstrapper boots, it will not register the plugin/indexer, and the test run will complete successfully. But if the test bootstrapper installs that poisonous plugin, the next test run will crash again... and the test runner will flip-flop between running and crashing with every run.
I imagine that this is not limited to an entity indexer, and there are other scenarios where using those stale services can cause a problem.
How to reproduce

create a plugin that:

creates a new db table
tags a service with shopware.entity_indexer
tries to access that new table in the indexer service

configure phpunit's test bootstrap script to install this plugin and force install Shopware
run phpunit, it should succeed and register the plugin
run phpunit again, it should crash in the indexer service
run phpunit again, it should succeed and register the plugin
run phpunit again, it should crash in the indexer service...

Hi,
thx for your issue we will put it into our new evaluation process and have a look at it again.

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-37957.
[created from NEXT-37957, comment 489033]


fix: CMAKE_BUILD_DIR to CMAKE_CURRENT_BINARY_DIR

this allows for cmake add_subdirectory to be used with this project

A bit more context. This package does not exist on the AUR and I need to use it in my dissertation work. I have a few options: adding it to the AUR and linking the shared library or, as I am doing, adding a subdirectory in cmake then statically linking.
As I am looking at comparing multiple FHE libraries I would prefere not to statically link them but as I am aiming at targetting an embedded device soon I thought that static linking could be better. So this PR is still a WIP but, will allow for static linking within cmake by add_subdirectory(openfhe) then target_link_libraries(yourname openfhe::core) or similar.

Cheers for having an initial look at this @yspolyakov, I was wondering if you could give me a bit of advise on the best way to document these changes.


[macOS] Platform view not clipped with when using rotated ClipRect

Example code: https://github.com/knopp/platform_view_macos_example/tree/rotate_clip_rect
Current behavior:
https://github.com/flutter/flutter/assets/96958/1c189776-b9e8-44d9-bdc4-4cfc60610c2e
Expected behavior:
https://github.com/flutter/flutter/assets/96958/352bc66e-a1cd-4787-a3f6-2d47a6ffd589

Reproducible using the code sample provided above.

flutter doctor -v
[!] Flutter (Channel master, 3.11.0-18.0.pre.76, on macOS 13.4 22F66 darwin-arm64, locale en-GB)
    • Flutter version 3.11.0-18.0.pre.76 on channel master at /Users/nexus/dev/sdks/flutters
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 0b7415356e (2 days ago), 2023-06-03 07:16:37 -0400
    • Engine revision c838a1b059
    • Dart version 3.1.0 (build 3.1.0-166.0.dev)
    • DevTools version 2.24.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9971841/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode-14.3.0.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9971841/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9862592/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.2)
    • IntelliJ at /Users/nexus/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 74.0.4
    • Dart plugin version 231.9065

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.2)
    • IntelliJ at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/231.9011.34/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.1)
    • IntelliJ at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/231.8770.65/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.78.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.66.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 13.4 22F66 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 114.0.5735.90

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.


change ws address - [closed]

In GitLab by @liyanq528 on Nov 30, 2017, 02:24
Merges dev-refactor-service-ui -> dev-refactor-service-config

In GitLab by @wknet123 on Nov 13, 2019, 10:12
the build is FAILED console log

In GitLab by @wknet123 on Nov 13, 2019, 10:12
closed


Icon to reset statistics does not display in versions older than v0.4.3

In OpenRCT2 v0.4.3 and onward, the reload icon displays as intended. In older versions, the plugin API doesn't have the ability to take a string and convert it to the image id. What complicates the matter is that the reload icon was only introduced in v0.4.2, so setting the value to a constant number will not solve the problem for older versions.

A proposed solution is to check for if the API version is less than that for v0.4.3 and use a different icon instead. Ideally one that would be the same across v0.4.0 to 0.4.2 (so most likely something in G1). Perhaps the sprite for demolish (5165)?

The sprite for No Entry (5178) is also a potential candidate, but ultimately, Demolish (5165) is best after looking through. I will start work on this.


[JOSS] Single animal pose estimation tutorial

Hi,
I had a go at the pose estimation full-frame tutorial and am getting this error when selecting to export the data:
Using C:\Users\sminano\Downloads\VID_20220201_160304.mp4 for pose estimation...
Traceback (most recent call last):
  File "C:\Users\sminano\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\omni_trax\__init__.py", line 783, in execute
    pose_output_file.write(pose_joint_header_l1 + "\n")
UnboundLocalError: local variable 'pose_joint_header_l1' referenced before assignment
Error: Python: Traceback (most recent call last):
  File "C:\Users\sminano\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\omni_trax\__init__.py", line 783, in execute
    pose_output_file.write(pose_joint_header_l1 + "\n")
UnboundLocalError: local variable 'pose_joint_header_l1' referenced before assignment

This are my pose estimation parameters:

I used the sample video provided  VID_20220201_160304.mp4
I also noticed the Blender file explorer that pops up when filling in the DLC model guides you to select a file, but actually we need to select only a folder. Maybe a clarification could be added to the tutorial, something like 'double click Accept to select the parent folder' ?

Thanks a lot for the detailed description of the issue!
I fixed the (global) variable assignent and now the export should function correctly.
I'll try to make more progress on the other raised issues and code refactoring before adding a new release with all additions included!
Thank you so much for your time and dedication. Your comments have helped me a lot to make this repo more robust and slowly more maintainable as well!

Sounds great!
No worries, I'm glad it's been helpful! On my side it's been very fun to explore this tool 🤓


Error on Signup Page

Error on signup page for element not existing
To Reproduce
Steps to reproduce the behavior:

Go to Signup Page
Click on Submit after filling in

Expected behavior
It should submit the form

Assigned @programerr01


[BUG] ImportError: cannot import name 'url_quote' from 'werkzeug.urls'

(base) C:\Users\28622>conda activate lama

(lama) C:\Users\28622>lama-cleaner --model=lama --device=cuda --port=8080
- Platform: Windows-10-10.0.22621-SP0
- Python version: 3.10.11
- torch: 1.13.1+cu117
- torchvision: 0.14.1+cu117
- Pillow: 10.0.1
- diffusers: 0.16.1
- transformers: 4.27.4
- opencv-python: <IP_ADDRESS>
- xformers: N/A
- accelerate: N/A
- lama-cleaner: 1.2.3
- rembg: N/A
- realesrgan: N/A
- gfpgan: N/A

Traceback (most recent call last):
  File "D:\miniconda3\envs\lama\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "D:\miniconda3\envs\lama\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "D:\miniconda3\envs\lama\Scripts\lama-cleaner.exe\__main__.py", line 7, in <module>
    sys.exit(entry_point())
  File "D:\miniconda3\envs\lama\lib\site-packages\lama_cleaner\__init__.py", line 16, in entry_point
    from lama_cleaner.server import main
  File "D:\miniconda3\envs\lama\lib\site-packages\lama_cleaner\server.py", line 44, in <module>
    from flask import (
  File "D:\miniconda3\envs\lama\lib\site-packages\flask\__init__.py", line 5, in <module>
    from .app import Flask as Flask
  File "D:\miniconda3\envs\lama\lib\site-packages\flask\app.py", line 30, in <module>
    from werkzeug.urls import url_quote
ImportError: cannot import name 'url_quote' from 'werkzeug.urls' (D:\miniconda3\envs\lama\lib\site-packages\werkzeug\urls.py)

(lama) C:\Users\28622>pip install torch==1.13.1+cu117 torchvision==0.14.1+cu117 torchaudio==0.13.1 --extra-index-url https://download.pytorch.org/whl/cu117
Looking in indexes: https://pypi.org/simple, https://download.pytorch.org/whl/cu117
Requirement already satisfied: torch==1.13.1+cu117 in d:\miniconda3\envs\lama\lib\site-packages (1.13.1+cu117)
Requirement already satisfied: torchvision==0.14.1+cu117 in d:\miniconda3\envs\lama\lib\site-packages (0.14.1+cu117)
Requirement already satisfied: torchaudio==0.13.1 in d:\miniconda3\envs\lama\lib\site-packages (0.13.1+cu117)
Requirement already satisfied: typing-extensions in d:\miniconda3\envs\lama\lib\site-packages (from torch==1.13.1+cu117) (4.8.0)
Requirement already satisfied: numpy in d:\miniconda3\envs\lama\lib\site-packages (from torchvision==0.14.1+cu117) (1.26.0)
Requirement already satisfied: requests in d:\miniconda3\envs\lama\lib\site-packages (from torchvision==0.14.1+cu117) (2.31.0)
Requirement already satisfied: pillow!=8.3.*,>=5.3.0 in d:\miniconda3\envs\lama\lib\site-packages (from torchvision==0.14.1+cu117) (10.0.1)
Requirement already satisfied: charset-normalizer<4,>=2 in d:\miniconda3\envs\lama\lib\site-packages (from requests->torchvision==0.14.1+cu117) (3.3.0)
Requirement already satisfied: idna<4,>=2.5 in d:\miniconda3\envs\lama\lib\site-packages (from requests->torchvision==0.14.1+cu117) (3.4)
Requirement already satisfied: urllib3<3,>=1.21.1 in d:\miniconda3\envs\lama\lib\site-packages (from requests->torchvision==0.14.1+cu117) (2.0.6)
Requirement already satisfied: certifi>=2017.4.17 in d:\miniconda3\envs\lama\lib\site-packages (from requests->torchvision==0.14.1+cu117) (2023.7.22)

(lama) C:\Users\28622>pip install lama-cleaner
Requirement already satisfied: lama-cleaner in d:\miniconda3\envs\lama\lib\site-packages (1.2.3)
Requirement already satisfied: torch>=1.9.0 in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (1.13.1+cu117)
Requirement already satisfied: opencv-python in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (<IP_ADDRESS>)
Requirement already satisfied: flask==2.2.3 in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (2.2.3)
Requirement already satisfied: flask-socketio in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (5.3.6)
Requirement already satisfied: simple-websocket in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (0.10.1)
Requirement already satisfied: flask-cors in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (4.0.0)
Requirement already satisfied: flaskwebgui==0.3.5 in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (0.3.5)
Requirement already satisfied: pydantic in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (2.4.2)
Requirement already satisfied: rich in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (13.6.0)
Requirement already satisfied: loguru in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (0.7.2)
Requirement already satisfied: yacs in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (0.1.8)
Requirement already satisfied: diffusers==0.16.1 in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (0.16.1)
Requirement already satisfied: transformers==4.27.4 in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (4.27.4)
Requirement already satisfied: gradio in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (3.46.0)
Requirement already satisfied: piexif==1.1.3 in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (1.1.3)
Requirement already satisfied: safetensors in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (0.3.3)
Requirement already satisfied: omegaconf in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (2.3.0)
Requirement already satisfied: controlnet-aux==0.0.3 in d:\miniconda3\envs\lama\lib\site-packages (from lama-cleaner) (0.0.3)
Requirement already satisfied: Pillow in d:\miniconda3\envs\lama\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (10.0.1)
Requirement already satisfied: einops in d:\miniconda3\envs\lama\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (0.7.0)
Requirement already satisfied: filelock in d:\miniconda3\envs\lama\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (3.12.4)
Requirement already satisfied: huggingface-hub in d:\miniconda3\envs\lama\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (0.17.3)
Requirement already satisfied: importlib-metadata in d:\miniconda3\envs\lama\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (6.8.0)
Requirement already satisfied: numpy in d:\miniconda3\envs\lama\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (1.26.0)
Requirement already satisfied: scikit-image in d:\miniconda3\envs\lama\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (0.22.0)
Requirement already satisfied: scipy in d:\miniconda3\envs\lama\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (1.11.3)
Requirement already satisfied: timm in d:\miniconda3\envs\lama\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (0.9.7)
Requirement already satisfied: torchvision in d:\miniconda3\envs\lama\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (0.14.1+cu117)
Requirement already satisfied: regex!=2019.12.17 in d:\miniconda3\envs\lama\lib\site-packages (from diffusers==0.16.1->lama-cleaner) (2023.10.3)
Requirement already satisfied: requests in d:\miniconda3\envs\lama\lib\site-packages (from diffusers==0.16.1->lama-cleaner) (2.31.0)
Requirement already satisfied: Werkzeug>=2.2.2 in d:\miniconda3\envs\lama\lib\site-packages (from flask==2.2.3->lama-cleaner) (3.0.0)
Requirement already satisfied: Jinja2>=3.0 in d:\miniconda3\envs\lama\lib\site-packages (from flask==2.2.3->lama-cleaner) (3.1.2)
Requirement already satisfied: itsdangerous>=2.0 in d:\miniconda3\envs\lama\lib\site-packages (from flask==2.2.3->lama-cleaner) (2.1.2)
Requirement already satisfied: click>=8.0 in d:\miniconda3\envs\lama\lib\site-packages (from flask==2.2.3->lama-cleaner) (8.1.7)
Requirement already satisfied: whichcraft in d:\miniconda3\envs\lama\lib\site-packages (from flaskwebgui==0.3.5->lama-cleaner) (0.6.1)
Requirement already satisfied: packaging>=20.0 in d:\miniconda3\envs\lama\lib\site-packages (from transformers==4.27.4->lama-cleaner) (23.2)
Requirement already satisfied: pyyaml>=5.1 in d:\miniconda3\envs\lama\lib\site-packages (from transformers==4.27.4->lama-cleaner) (6.0.1)
Requirement already satisfied: tokenizers!=0.11.3,<0.14,>=0.11.1 in d:\miniconda3\envs\lama\lib\site-packages (from transformers==4.27.4->lama-cleaner) (0.13.3)
Requirement already satisfied: tqdm>=4.27 in d:\miniconda3\envs\lama\lib\site-packages (from transformers==4.27.4->lama-cleaner) (4.66.1)
Requirement already satisfied: typing-extensions in d:\miniconda3\envs\lama\lib\site-packages (from torch>=1.9.0->lama-cleaner) (4.8.0)
Requirement already satisfied: python-socketio>=5.0.2 in d:\miniconda3\envs\lama\lib\site-packages (from flask-socketio->lama-cleaner) (5.9.0)
Requirement already satisfied: aiofiles<24.0,>=22.0 in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (23.2.1)
Requirement already satisfied: altair<6.0,>=4.2.0 in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (5.1.2)
Requirement already satisfied: fastapi in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (0.103.2)
Requirement already satisfied: ffmpy in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (0.3.1)
Requirement already satisfied: gradio-client==0.5.3 in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (0.5.3)
Requirement already satisfied: httpx in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (0.25.0)
Requirement already satisfied: importlib-resources<7.0,>=1.3 in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (6.1.0)
Requirement already satisfied: markupsafe~=2.0 in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (2.1.3)
Requirement already satisfied: matplotlib~=3.0 in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (3.8.0)
Requirement already satisfied: orjson~=3.0 in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (3.9.7)
Requirement already satisfied: pandas<3.0,>=1.0 in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (2.1.1)
Requirement already satisfied: pydub in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (0.25.1)
Requirement already satisfied: python-multipart in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (0.0.6)
Requirement already satisfied: semantic-version~=2.0 in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (2.10.0)
Requirement already satisfied: uvicorn>=0.14.0 in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (0.23.2)
Requirement already satisfied: websockets<12.0,>=10.0 in d:\miniconda3\envs\lama\lib\site-packages (from gradio->lama-cleaner) (11.0.3)
Requirement already satisfied: fsspec in d:\miniconda3\envs\lama\lib\site-packages (from gradio-client==0.5.3->gradio->lama-cleaner) (2023.9.2)
Requirement already satisfied: annotated-types>=0.4.0 in d:\miniconda3\envs\lama\lib\site-packages (from pydantic->lama-cleaner) (0.5.0)
Requirement already satisfied: pydantic-core==2.10.1 in d:\miniconda3\envs\lama\lib\site-packages (from pydantic->lama-cleaner) (2.10.1)
Requirement already satisfied: colorama>=0.3.4 in d:\miniconda3\envs\lama\lib\site-packages (from loguru->lama-cleaner) (0.4.6)
Requirement already satisfied: win32-setctime>=1.0.0 in d:\miniconda3\envs\lama\lib\site-packages (from loguru->lama-cleaner) (1.1.0)
Requirement already satisfied: antlr4-python3-runtime==4.9.* in d:\miniconda3\envs\lama\lib\site-packages (from omegaconf->lama-cleaner) (4.9.3)
Requirement already satisfied: markdown-it-py>=2.2.0 in d:\miniconda3\envs\lama\lib\site-packages (from rich->lama-cleaner) (3.0.0)
Requirement already satisfied: pygments<3.0.0,>=2.13.0 in d:\miniconda3\envs\lama\lib\site-packages (from rich->lama-cleaner) (2.16.1)
Requirement already satisfied: wsproto in d:\miniconda3\envs\lama\lib\site-packages (from simple-websocket->lama-cleaner) (1.2.0)
Requirement already satisfied: jsonschema>=3.0 in d:\miniconda3\envs\lama\lib\site-packages (from altair<6.0,>=4.2.0->gradio->lama-cleaner) (4.19.1)
Requirement already satisfied: toolz in d:\miniconda3\envs\lama\lib\site-packages (from altair<6.0,>=4.2.0->gradio->lama-cleaner) (0.12.0)
Requirement already satisfied: mdurl~=0.1 in d:\miniconda3\envs\lama\lib\site-packages (from markdown-it-py>=2.2.0->rich->lama-cleaner) (0.1.2)
Requirement already satisfied: contourpy>=1.0.1 in d:\miniconda3\envs\lama\lib\site-packages (from matplotlib~=3.0->gradio->lama-cleaner) (1.1.1)
Requirement already satisfied: cycler>=0.10 in d:\miniconda3\envs\lama\lib\site-packages (from matplotlib~=3.0->gradio->lama-cleaner) (0.12.0)
Requirement already satisfied: fonttools>=4.22.0 in d:\miniconda3\envs\lama\lib\site-packages (from matplotlib~=3.0->gradio->lama-cleaner) (4.43.0)
Requirement already satisfied: kiwisolver>=1.0.1 in d:\miniconda3\envs\lama\lib\site-packages (from matplotlib~=3.0->gradio->lama-cleaner) (1.4.5)
Requirement already satisfied: pyparsing>=2.3.1 in d:\miniconda3\envs\lama\lib\site-packages (from matplotlib~=3.0->gradio->lama-cleaner) (3.1.1)
Requirement already satisfied: python-dateutil>=2.7 in d:\miniconda3\envs\lama\lib\site-packages (from matplotlib~=3.0->gradio->lama-cleaner) (2.8.2)
Requirement already satisfied: pytz>=2020.1 in d:\miniconda3\envs\lama\lib\site-packages (from pandas<3.0,>=1.0->gradio->lama-cleaner) (2023.3.post1)
Requirement already satisfied: tzdata>=2022.1 in d:\miniconda3\envs\lama\lib\site-packages (from pandas<3.0,>=1.0->gradio->lama-cleaner) (2023.3)
Requirement already satisfied: bidict>=0.21.0 in d:\miniconda3\envs\lama\lib\site-packages (from python-socketio>=5.0.2->flask-socketio->lama-cleaner) (0.22.1)
Requirement already satisfied: python-engineio>=4.7.0 in d:\miniconda3\envs\lama\lib\site-packages (from python-socketio>=5.0.2->flask-socketio->lama-cleaner) (4.7.1)
Requirement already satisfied: charset-normalizer<4,>=2 in d:\miniconda3\envs\lama\lib\site-packages (from requests->diffusers==0.16.1->lama-cleaner) (3.3.0)
Requirement already satisfied: idna<4,>=2.5 in d:\miniconda3\envs\lama\lib\site-packages (from requests->diffusers==0.16.1->lama-cleaner) (3.4)
Requirement already satisfied: urllib3<3,>=1.21.1 in d:\miniconda3\envs\lama\lib\site-packages (from requests->diffusers==0.16.1->lama-cleaner) (2.0.6)
Requirement already satisfied: certifi>=2017.4.17 in d:\miniconda3\envs\lama\lib\site-packages (from requests->diffusers==0.16.1->lama-cleaner) (2023.7.22)
Requirement already satisfied: h11>=0.8 in d:\miniconda3\envs\lama\lib\site-packages (from uvicorn>=0.14.0->gradio->lama-cleaner) (0.14.0)
Requirement already satisfied: anyio<4.0.0,>=3.7.1 in d:\miniconda3\envs\lama\lib\site-packages (from fastapi->gradio->lama-cleaner) (3.7.1)
Requirement already satisfied: starlette<0.28.0,>=0.27.0 in d:\miniconda3\envs\lama\lib\site-packages (from fastapi->gradio->lama-cleaner) (0.27.0)
Requirement already satisfied: httpcore<0.19.0,>=0.18.0 in d:\miniconda3\envs\lama\lib\site-packages (from httpx->gradio->lama-cleaner) (0.18.0)
Requirement already satisfied: sniffio in d:\miniconda3\envs\lama\lib\site-packages (from httpx->gradio->lama-cleaner) (1.3.0)
Requirement already satisfied: zipp>=0.5 in d:\miniconda3\envs\lama\lib\site-packages (from importlib-metadata->controlnet-aux==0.0.3->lama-cleaner) (3.17.0)
Requirement already satisfied: networkx>=2.8 in d:\miniconda3\envs\lama\lib\site-packages (from scikit-image->controlnet-aux==0.0.3->lama-cleaner) (3.1)
Requirement already satisfied: imageio>=2.27 in d:\miniconda3\envs\lama\lib\site-packages (from scikit-image->controlnet-aux==0.0.3->lama-cleaner) (2.31.5)
Requirement already satisfied: tifffile>=2022.8.12 in d:\miniconda3\envs\lama\lib\site-packages (from scikit-image->controlnet-aux==0.0.3->lama-cleaner) (2023.9.26)
Requirement already satisfied: lazy_loader>=0.3 in d:\miniconda3\envs\lama\lib\site-packages (from scikit-image->controlnet-aux==0.0.3->lama-cleaner) (0.3)
Requirement already satisfied: exceptiongroup in d:\miniconda3\envs\lama\lib\site-packages (from anyio<4.0.0,>=3.7.1->fastapi->gradio->lama-cleaner) (1.1.3)
Requirement already satisfied: attrs>=22.2.0 in d:\miniconda3\envs\lama\lib\site-packages (from jsonschema>=3.0->altair<6.0,>=4.2.0->gradio->lama-cleaner) (23.1.0)
Requirement already satisfied: jsonschema-specifications>=2023.03.6 in d:\miniconda3\envs\lama\lib\site-packages (from jsonschema>=3.0->altair<6.0,>=4.2.0->gradio->lama-cleaner) (2023.7.1)
Requirement already satisfied: referencing>=0.28.4 in d:\miniconda3\envs\lama\lib\site-packages (from jsonschema>=3.0->altair<6.0,>=4.2.0->gradio->lama-cleaner) (0.30.2)
Requirement already satisfied: rpds-py>=0.7.1 in d:\miniconda3\envs\lama\lib\site-packages (from jsonschema>=3.0->altair<6.0,>=4.2.0->gradio->lama-cleaner) (0.10.3)
Requirement already satisfied: six>=1.5 in d:\miniconda3\envs\lama\lib\site-packages (from python-dateutil>=2.7->matplotlib~=3.0->gradio->lama-cleaner) (1.16.0)

(lama) C:\Users\28622>lama-cleaner --model=lama --device=cuda --port=8080
- Platform: Windows-10-10.0.22621-SP0
- Python version: 3.10.11
- torch: 1.13.1+cu117
- torchvision: 0.14.1+cu117
- Pillow: 10.0.1
- diffusers: 0.16.1
- transformers: 4.27.4
- opencv-python: <IP_ADDRESS>
- xformers: N/A
- accelerate: N/A
- lama-cleaner: 1.2.3
- rembg: N/A
- realesrgan: N/A
- gfpgan: N/A

Traceback (most recent call last):
  File "D:\miniconda3\envs\lama\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "D:\miniconda3\envs\lama\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "D:\miniconda3\envs\lama\Scripts\lama-cleaner.exe\__main__.py", line 7, in <module>
    sys.exit(entry_point())
  File "D:\miniconda3\envs\lama\lib\site-packages\lama_cleaner\__init__.py", line 16, in entry_point
    from lama_cleaner.server import main
  File "D:\miniconda3\envs\lama\lib\site-packages\lama_cleaner\server.py", line 44, in <module>
    from flask import (
  File "D:\miniconda3\envs\lama\lib\site-packages\flask\__init__.py", line 5, in <module>
    from .app import Flask as Flask
  File "D:\miniconda3\envs\lama\lib\site-packages\flask\app.py", line 30, in <module>
    from werkzeug.urls import url_quote
ImportError: cannot import name 'url_quote' from 'werkzeug.urls' (D:\miniconda3\envs\lama\lib\site-packages\werkzeug\urls.py)

(lama) C:\Users\28622>

I also have same problem

I don't know how to solve the problem that happened later. However, I found out how to solve the first problem you wrote.
This problem arises when a library called werkzeug with dependencies was recently updated to 3.0.0. Therefore, clone the repository and add werkzeug==2.2.2 to requirements.txt. And try running pip install -r requirements.txt.
And running python main.py will solve the problem.

@Kiminjo Thank you very much, I have fixed this issue in version 1.2.4.

how do you fix this problem for azure? even if i change the requirements file it still fails on azure (it works on local computer though)

how do you fix this problem for azure? even if i change the requirements file it still fails on azure (it works on local computer though)

Sorry, I haven't deployed it on the azure server, so I can't answer your question.

how do you fix this problem for azure? even if i change the requirements file it still fails on azure (it works on local computer though)

Same problem, if you ever resolved it, please let me know

Was having the same issue on my azure VM trying to run mitmproxy. This fixed it: pip uninstall -y Werkzeug && pip install Werkzeug==2.3.6


Social media: icons in hero cards are not clear

CMS users and editors keep getting confused about the function of the icons in the hero card. They think they'll link to social media channels, rather than being share buttons. To be discussed how this could be improved.

@beatrizmartinmartins Where can we review this one?

https://www.figma.com/design/RRxsfLNxjoypKrfJg1EwJf/ILO-Components-Library?m=auto&node-id=7218%3A14778&t=xiREKhqZcf3yfhXq-1

@inesdgomes In order to create this, I created a new component, I think it will be easier to maintain in the long term in case we need to make changes to it.
We have 4 options:

Mode: Light and Dark (for the different bg of the cards)
Type: Open and closed

I also had to include a new icon called Share so we could use it on the new component. You can check that new icon here. cc @justintemps

Great @beatrizmartinmartins I quite like this solution. @justintemps I think we can move it to development, but let me know if there's anything that you think doesn't work.

Hey @inesdgomes  and @beatrizmartinmartins I think we'd need to see this in action in the components where it's used. So far as I'm aware it's only used in the hero card. I think the important thing is that it doesn't change the layout when it's open. It shouldn't move things around or change the height or width of the components it's inside of when the user opens it.

@justintemps The component is indeed used only in the hero card. Beatriz already added it to the templates and you can see it here: https://www.figma.com/design/TnVsWy6VobbHzZdbHdx3Rb/ILO-Page-Templates?node-id=3763-36970&t=Aee4em4sPrxZxJ4z-0
As for your question on whether the layout changes when it's open, the width should not be affected, but I'm not sure about the height as it seems the rounded rectangle where the social media icons show is slightly taller than the 'Share' text. Is that an issue? Can it be resolved in the code or do you need design changes? cc @beatrizmartinmartins

@justintemps @inesdgomes when I did this, I was thinking about it, and the conclusion was that the circled container needs to be in absolute position so it doesn't affect the height of the hero cards. Is it possible?

@inesdgomes can you send me a link to this component in figma for the opened state I cant seem to find it :|

@Shashika6 https://www.figma.com/design/RRxsfLNxjoypKrfJg1EwJf/ILO-Components-Library?node-id=3767-23230&node-type=FRAME&t=jTAA2DrY2X75zEDg-0

Before @Shashika6 dives into this, @beatrizmartinmartins and @inesdgomes , could you provide some information about the transitions here?
Questions:

Does it only happen on click or on hover?
What are the select and focus states?

Hi @beatrizmartinmartins Please see above. Apart from the click/hover, I think all that info is in the design files, but maybe it needs to be clearer. Could you please follow up on this one?

@inesdgomes we don't need selected state, because selected is open or closed version. I did create the hover and focus state though. Check it here The hover and focus states for closed version is the same as the link

@inesdgomes fixed the comments on the Social Media icons and also on the Link component because it wasn't behaving the way intended https://www.figma.com/design/RRxsfLNxjoypKrfJg1EwJf/ILO-Components-Library?m=auto&node-id=3767-23230&t=aVB8uFepBwsqHlC8-1

Hi @beatrizmartinmartins I think this looks good, but I'm finding it a bit strange now that we're introducing all these round shapes, which  I think we haven't used anywhere else. Just double checking you tried other options?

I remember we tried to include a simple text above, or just use a simple icon button where you click and the popover opens up. I know what you mean, ILO has all sharp edges or just very subtle border-radius, but it was a way to differentiate between the background and the popover surface. Maybe we can remove the border around the social media icons and just leave the bg as transparent?
Other options:

Link
Link

@inesdgomes

Hi @beatrizmartinmartins We agreed last week that we'd go for something with sharper angles, like this example. https://es.pinterest.com/pin/1030198483485184929/

@inesdgomes done. check the design here

@beatrizmartinmartins Very nice, thanks!
@justintemps This is ready for development. Please see design here. The users need to click 'Share' to see the 'Open' state.

Moving this into development with #1284


Total Working Set of Currently Selected Processes

Is your feature request related to a problem? Please describe.
I often want to know the total working set of a program using multiple processes (e.g. Firefox, Chrome).
Describe the solution you'd like
Add an option to display the total working set of all the currently selected processes in the status bar.
Thank you.

Added to latest nightly build

@dmex,
👍
Very useful and works like a charm. Thank you so much.

The status-bar fields' values take ~4 seconds to display (compared to ~1 second in v2.39).
Is there anything I can do (disable ?) to speed it up?

The status-bar fields' values take ~4 seconds to display (compared to ~1 second in v2.39).

After starting PH or at runtime?

After starting PH.
I've tested it on two machines and the difference is significant.
If this can not be changed, would it be possible to adapt the new ToolStatus.dll to v2.39?
Thanks again.

https://github.com/processhacker/processhacker/issues/929


pronlem with xwayland {   force_zero_scaling = true }

Hyprland Version
hyprctl version
Bug or Regression?
Bug
Description
after i set
xwayland {
force_zero_scaling = true
}
and replace all the "-hidpi"paks by the original one
the xorg apps work in some wrong way, it seams that it have a wrong screen edge
How to reproduce
IDK
Crash reports, logs, images, videos
https://github.com/hyprwm/Hyprland/assets/102898587/581975af-1286-4154-a6a1-9b9101104ac2

weird, never seen that, but you may also want to run chrome in wayland.

Some of the app’s that I have to use(WeChat and qq) have to run in x11, chrome is just for demo, I just switch back to the hidpi-patch and the problem solved.

can't repro, seems to be working just fine to me

try connect to a second display?

if you want maybe you can remote desktop to my computer and try to find the problem?

I am facing similar problems. On my main monitor (DP-2, 3840x2160, 2x), applications cannot detect the cursor going any further than halfway across the horizontal axis. It is almost as if there is a border at x = 1920, and any mouse position/clicks right of that are modified to be on 1920 instead.
This did not happen when using the hidpi patches, which I stopped using after seeing the warning in the wiki.
A code-style explanation (using python syntax):
def on_click:
    if cursor.x > 1920 and monitor == "DP-2":
        cursor.x = 1920
    click()

Output of hyprctl monitors:
Monitor HDMI-A-1 (ID 0):
<EMAIL_ADDRESS>at 3840x0
	description: Hewlett Packard LA1951 CNK0480FBJ (HDMI-A-1)
	make: Hewlett Packard
	model: LA1951
	serial: CNK0480FBJ
	active workspace: 1 (1)
	special workspace: 0 ()
	reserved: 0 24 0 44
	scale: 1.00
	transform: 1
	focused: no
	dpmsStatus: 1
	vrr: 0

Monitor DP-1 (ID 1):
<EMAIL_ADDRESS>at 0x0
	description: ASUSTek COMPUTER INC VG249Q1R L8LMDW001342 (DP-1)
	make: ASUSTek COMPUTER INC
	model: VG249Q1R
	serial: L8LMDW001342
	active workspace: 2 (2)
	special workspace: 0 ()
	reserved: 0 24 0 44
	scale: 1.00
	transform: 0
	focused: yes
	dpmsStatus: 1
	vrr: 1

Monitor DP-2 (ID 2):
<EMAIL_ADDRESS>at 1920x0
	description: Samsung Electric Company LU28R55 H4ZT404747 (DP-2)
	make: Samsung Electric Company
	model: LU28R55
	serial: H4ZT404747
	active workspace: 3 (3)
	special workspace: 0 ()
	reserved: 0 24 0 44
	scale: 2.00
	transform: 0
	focused: no
	dpmsStatus: 1
	vrr: 1

Relevant sections of my hyprland.conf:
# See https://wiki.hyprland.org/Configuring/Monitors/
monitor = DP-1, highrr, 0x0, 1
monitor = DP-2, highres, 1920x0, 2, bitdepth, 10
monitor = HDMI-A-1, preferred, 3840x0, 1, transform, 1

...

xwayland {
	force_zero_scaling = true
}

My setup is 2 vertical monitors (2160x3840) + 1 horizontal monitor (3840x2160) + nvidia card + hyprland 8e04a80e60983f5def26bdcaea701040fea9a7ae (current version in nixpkgs) + hyprland.conf config similar to @maxyvisser 's and I can reproduce the issue described by @maxyvisser by running xev on either one of vertical monitor, except in my case it is y-axis get cut at 2159. When xev is on my horizontal monitor the mouse coordinate is correct.
@maxyvisser 's mouse on DP-2 got cut at 1920 (their DP-1's x-axis length), and my mouse got cut 2159 (which is very close to 2160, my monitor's x-axis length), so maybe this bug has something to do with mouse location clipping using wrong limit?

Another potentially interesting observation: the layout of the surrounding monitors matters. My regular setup:
+-------------------++-------------------++-----------+
|       DP-1        ||       DP-2        || HDMI-A-1  |
|     1920x1080     ||     3840x2160     || 1040x1280 |
|     scale: 1      ||     scale: 2      || scale: 1  |
|                   ||                   || transf: 1 |
+-------------------++-------------------++-----------+

This has a cutoff on monitor DP-2 at x = 1915. However, when switching DP-1 and HDMI-A-1:
+-----------++-------------------++-------------------+
| HDMI-A-1  ||       DP-2        ||       DP-1        |
| 1280x1024 ||     3840x2160     ||     1920x1080     |
| scale: 1  ||     scale: 2      ||     scale: 1      |
| transf: 1 ||                   ||                   |
+-----------++-------------------++-------------------+

The cutoff changes to x = 2811.
This is not at all what I expected: 1915 is roughly the width of the leftmost monitor (so I get where that number could come from), but 2811 has nothing to do with any dimensions of any of my monitors.
Relevant monitors section:
monitor = DP-1, highrr, 2944x0, 1
monitor = DP-2, highres, 1024x0, 2, bitdepth, 10
monitor = HDMI-A-1, preferred, 0x0, 1, transform, 1

@sifmelcara Do you see any similar strange numbers when switching up your layout?
Also, this might be nvidia related (both @sifmelcara and I use a nvidia card with the patch). Could this maybe be why @vaxerski can't reproduce the issue?

Some other monitor layouts:
+-------------------++-----------++-------------------+
|       DP-1        || HDMI-A-1  ||       DP-2        |
|     1920x1080     || 1040x1280 ||     3840x2160     |
|     scale: 1      || scale: 1  ||     scale: 2      |
|                   || transf: 1 ||                   |
+-------------------++-----------++-------------------+

Monitors section:
monitor = DP-1, highrr, 0x0, 1
monitor = DP-2, highres, 2944x0, 2, bitdepth, 10
monitor = HDMI-A-1, preferred, 1920x0, 1, transform, 1

^ Cutoff: x = 891 (Again, completely nonsensical)
+-------------------++-----------++-------------------+
|       DP-2        || HDMI-A-1  ||       DP-1        |
|     3840x2160     || 1280x1024 ||     1920x1080     |
|     scale: 2      || scale: 1  ||     scale: 1      |
|                   || transf: 1 ||                   |
+-------------------++-----------++-------------------+

Monitors section:
monitor = DP-1, highrr, 2944x0, 1
monitor = DP-2, highres, 0x0, 2, bitdepth, 10
monitor = HDMI-A-1, preferred, 1920x0, 1, transform, 1

^ No apparent cutoff? x goes all the way to 3832 (which appears to be correct considering my borders)

Last two layouts:
+-------------------++-------------------++-----------+
|       DP-2        ||       DP-1        || HDMI-A-1  |
|     3840x2160     ||     1920x1080     || 1280x1024 |
|     scale: 2      ||     scale: 1      || scale: 1  |
|                   ||                   || transf: 1 |
+-------------------++-------------------++-----------+

Monitors:
monitor = DP-1, highrr, 1920x0, 1
monitor = DP-2, highres, 0x0, 2, bitdepth, 10
monitor = HDMI-A-1, preferred, 3840x0, 1, transform, 1

^ Again, no apparent cutoff.
+-----------++-------------------++-------------------+
| HDMI-A-1  ||       DP-1        ||       DP-2        |
| 1280x1024 ||     1920x1080     ||     3840x2160     |
| scale: 1  ||     scale: 1      ||     scale: 2      |
| transf: 1 ||                   ||                   |
+-----------++-------------------++-------------------+

Monitors:
monitor = DP-1, highrr, 1024x0, 1
monitor = DP-2, highres, 2944x0, 2, bitdepth, 10
monitor = HDMI-A-1, preferred, 0x0, 1, transform, 1

^ Again a cutoff at x = 891
It appears that if DP-2 is on the left side, no cutoff occurs. If it is on the right side, the cutoff will be at x = 891. And if it is in the middle, the cutoff is dictated by the positions of other monitors.

I cannot test multimon stuff (on holiday)
you can ping me in a week and I can see what's up. For now, on a single monitor on my laptop with 1.5 scale and force zero scaling everything seems alright

Sure, I will ping you later. Have a nice holiday!

OT: if you can't use "pinch-to-zoom", "smooth-scrolling" etc. with google-chrome with the new update (removed hidpi). Set chrome://flags/#ozone-platform-hint to Auto or Wayland. I spent half a day debugging, maybe this will save someone some time 🙂
P.S. ty for anime girl on background :)

then there’ll be some problem with the input method

then there’ll be some problem with the input method

try google-chrome-stable --ozone-platform=wayland --enable-wayland-ime

I’ve tried before, working not stable

Okay, on my computer this works well. I have a 2K monitor on the left and a 1080P monitor on the right. I enabled xwayland:force_zero_scale but can't repro the problem.

Okay, on my computer this works well. I have a 2K monitor on the left and a 1080P monitor on the right. I enabled xwayland:force_zero_scale but can't repro the problem.

I tried 1x and 1.33x zoom, both work fine

Try rotation?

Try rotation?

Also works fine

metaphysics

metaphysics

what?

usually i use this word to describe the problems hard to find the cause or describe don’t know why do something can solve something

量子力学？

usually i use this word to describe the problems hard to find the cause or describe don’t know why do something can solve something

玄学

@imxyy1soope1 do you have a Nvidia graphics card, and do you use the Nvidia patch?

@imxyy1soope1 do you have a Nvidia graphics card, and do you use the Nvidia patch?

no, I use AMD ATI Radeon RX 5500XT

Ok, so to make a brief overview of the repro status:

name:
@sifmelcara
@maxyvisser
@gfhdhytghd
@imxyy1soope1
vaxerski

GPU:
Nvidia
Nvidia
?
AMD
?

Monitor count
3
3
2?
2
1

Scale
?
2x
?
1.33
?

Repro
Yes
Yes
Yes
No
No

This table would suggest that this issue is related to Nvidia and/or triple monitor setups (depending on @gfhdhytghd's monitor count, which was not yet specified)

i7-1260p+iris Xe，
3120x2080，sf=2
1920x1080，sf=1.15，rotation90
origin version

this is the statue when i report this issus

Updated the table with the new info, thanks

i have the dual monitor in configuration file but not pluged when it first happens（when i first swich to original version add the “force zero”in the file），but when pluged it also happens（on both monitors）

can someone post the output of xrandr when the bug happens? I have an idea.

wait for me to go home

❯ xrandr
Screen 0: minimum 16 x 16, current 3670 x 3861, maximum 32767 x 32767
eDP-1 connected 3120x2080+550+1781 (normal left inverted right x axis y axis) 300mm x 200mm
3120x2080     89.97*+
2048x1536     89.91
1920x1440     89.91
1600x1200     89.91
1440x1080     89.93
1400x1050     89.92
1280x1024     89.91
1280x960      89.91
1152x864      89.80
1024x768      89.72
800x600       89.85
640x480       89.73
320x240       87.89
2560x1600     89.95
1920x1200     89.91
1680x1050     89.94
1440x900      89.83
1280x800      89.89
1152x720      89.83
960x600       89.70
928x580       89.74
800x500       89.80
768x480       89.62
720x480       89.45
640x400       89.60
320x200       87.62
2880x1620     89.94
2560x1440     89.92
2048x1152     89.87
1920x1080     89.93
1600x900      89.88
1368x768      89.74
1280x720      89.80
1024x576      89.65
864x486       89.72
720x400       89.87
640x350       89.05

the conf
monitor=eDP-1, 31202080@90, 550x1781, 2
monitor=DP-4, 1920x1080@60, 870x0, 1.078, transform,1
monitor=DP-3<EMAIL_ADDRESS>0x342,1.5

umm, I think it got cut off? can you show xrandr for every display?

❯ xrandr
Screen 0: minimum 16 x 16, current 3670 x 4208, maximum 32767 x 32767
eDP-1 connected 3120x2080+550+2128 (normal left inverted right x axis y axis) 300mm x 200mm
3120x2080     89.97*+
2048x1536     89.91
1920x1440     89.91
1600x1200     89.91
1440x1080     89.93
1400x1050     89.92
1280x1024     89.91
1280x960      89.91
1152x864      89.80
1024x768      89.72
800x600       89.85
640x480       89.73
320x240       87.89
2560x1600     89.95
1920x1200     89.91
1680x1050     89.94
1440x900      89.83
1280x800      89.89
1152x720      89.83
960x600       89.70
928x580       89.74
800x500       89.80
768x480       89.62
720x480       89.45
640x400       89.60
320x200       87.62
2880x1620     89.94
2560x1440     89.92
2048x1152     89.87
1920x1080     89.93
1600x900      89.88
1368x768      89.74
1280x720      89.80
1024x576      89.65
864x486       89.72
720x400       89.87
640x350       89.05
DP-4 connected 1920x1080+870+350 left (normal left inverted right x axis y axis) 340mm x 190mm
1080x1920     59.96*+
1024x768      59.92
800x600       59.86
640x480       59.38
320x240       59.52
960x600       59.63
928x580       59.88
800x500       59.50
768x480       59.90
720x480       59.71
640x400       59.95
320x200       58.96
1024x576      59.90
864x486       59.92
720x400       59.55
640x350       59.77

the things goes well on that 4k display

I think I know why. Will fix later today.

OHHHH！

Also I wish the program can auto set the scale of xrandr in order to let the xorg apps run in a correct size on different dpi screens

CMake Error at CMakeLists.txt:183 (target_sources):
Cannot find source file:
protocols/hyprland-global-shortcuts-v1-protocol.c

Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm
.ccm .cxxm .c++m .h .hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90
.f95 .f03 .hip .ispc
Call Stack (most recent call first):
CMakeLists.txt:211 (protocol)

when i'm trying to build from github

either didnt clone --recursive or forgot to do make protocols

thanks that is the problem

the mouse on x11 apps totally stop working

hyprctl version
Hyprland, built from branch main at commit 2b4537606f604f29b2d42d7be369182831269958 dirty (master: fix always_center_master (2961)).
Tag: v0.28.0-56-g2b453760
flags: (if any)

xrandr
Screen 0: minimum 16 x 16, current 4750 x 4208, maximum 32767 x 32767
eDP-1 connected 3120x2080+550+2128 (normal left inverted right x axis y axis) 300mm x 200mm
3120x2080     89.97*+
2048x1536     89.91
1920x1440     89.91
1600x1200     89.91
1440x1080     89.93
1400x1050     89.92
1280x1024     89.91
1280x960      89.91
1152x864      89.80
1024x768      89.72
800x600       89.85
640x480       89.73
320x240       87.89
2560x1600     89.95
1920x1200     89.91
1680x1050     89.94
1440x900      89.83
1280x800      89.89
1152x720      89.83
960x600       89.70
928x580       89.74
800x500       89.80
768x480       89.62
720x480       89.45
640x400       89.60
320x200       87.62
2880x1620     89.94
2560x1440     89.92
2048x1152     89.87
1920x1080     89.93
1600x900      89.88
1368x768      89.74
1280x720      89.80
1024x576      89.65
864x486       89.72
720x400       89.87
640x350       89.05
DP-4 connected 1080x1920+3670+350 left (normal left inverted right x axis y axis) 340mm x 190mm
1920x1080     59.96*+
1440x1080     59.99
1400x1050     59.98
1280x1024     59.89
1280x960      59.94
1152x864      59.96
1024x768      59.92
800x600       59.86
640x480       59.38
320x240       59.52
1680x1050     59.95
1440x900      59.89
1280x800      59.81
1152x720      59.97
960x600       59.63
928x580       59.88
800x500       59.50
768x480       59.90
720x480       59.71
640x400       59.95
320x200       58.96
1600x900      59.95
1368x768      59.88
1280x720      59.86
1024x576      59.90
864x486       59.92
720x400       59.55
640x350       59.77

the config using now
monitor=eDP-1, 3120x2080@90, 550x2128, 2
monitor=DP-4, 1920x1080@60, 870x350, 1.078, transform,1
monitor=DP-3<EMAIL_ADDRESS>0x342,1.43

patch.txt
okay since that didn't work I'll just post a patch for now. Test this.

ok i will try

problem solved

https://github.com/hyprwm/Hyprland/assets/102898587/92b4a273-f725-48c0-9251-f1fd7a3e7550
is this regular?

another wired problem, some x11 app with a startup windows in the centre may shown in  a place that isn't centre, or out of the screen like this

(when open this app when focuse on the built-in display, the windows disapear, but able to see in btop I guess it is at some where out of the screen)

No such things happened on hidpi-patch version, maybe some extra work need to do

patch.txt
try this for positioning issues

/usr/bin/ld: IHyprLayout.cpp:(.text+0x4721): undefined reference to `CHyprXWaylandManager::xwaylandToWaylandCoords(Vector2D const&)'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
make[1]: *** [Makefile:13: release] Error 1
make[1]: Leaving directory '/home/wilf/Downloads/Hyprland'
make: *** [Makefile:38: install] Error 2

fixed and pushed to main anyways

ok

it is finally on the screen, but not that centre
on DP-1, it have a few pixels offset
on eDP-1, it have a huge offset

I will try to debug it more when I come back from holiday. For now, I am stuck with only one monitor. Since it's on the screen, it's not a big deal.
You can open a new issue for this, and ping me after the 20th

ok

I will try to debug it more when I come back from holiday. For now, I am stuck with only one monitor. Since it's on the screen, it's not a big deal.
You can open a new issue for this, and ping me after the 20th

back from holiday?

Off topic: Chromium supports Wayland
--ozone-platform-hint=auto


Flow Name as file name can break because of unallowed chars used in file system

In the New-PowerAutomateDoc.ps1 file are three spots where you need to remove illegal characters from the flow name before saving to file system.
I will provide a pull request with a fix shortly.

Hi @acieslik,
Thanks added this fix also to my development branch. Will publish a new main branch today with most of the fixes.


Add rule: Readme file should be present

Fixed in https://github.com/iwarapter/sonar-puppet/pull/226


clj-kondo: 2024.02.12 -> 2024.03.13

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/clj-kondo/clj-kondo/releases.
meta.description for clj-kondo is: A linter for Clojure code that sparks joy
meta.homepage for clj-kondo is: https://github.com/clj-kondo/clj-kondo
meta.changelog for clj-kondo is: https://github.com/clj-kondo/clj-kondo/blob/v2024.03.05/CHANGELOG.md
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.03.05 with grep in /nix/store/pjbvr2r5a1fzzn4kk87ikhaqk1hjcm0v-clj-kondo-2024.03.05
found 2024.03.05 in filename of file in /nix/store/pjbvr2r5a1fzzn4kk87ikhaqk1hjcm0v-clj-kondo-2024.03.05

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
clj-kondo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pjbvr2r5a1fzzn4kk87ikhaqk1hjcm0v-clj-kondo-2024.03.05 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A clj-kondo https://github.com/r-ryantm/nixpkgs/archive/4cdbfb24eae1fc96485f59cac21dbcc14c29db38.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/4cdbfb24eae1fc96485f59cac21dbcc14c29db38#clj-kondo

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pjbvr2r5a1fzzn4kk87ikhaqk1hjcm0v-clj-kondo-2024.03.05
ls -la /nix/store/pjbvr2r5a1fzzn4kk87ikhaqk1hjcm0v-clj-kondo-2024.03.05/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

clj-kondo

Maintainer pings
cc @jlesquembre @bennyandresen for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/clj-kondo/clj-kondo/releases.
meta.description for clj-kondo is: A linter for Clojure code that sparks joy
meta.homepage for clj-kondo is: https://github.com/clj-kondo/clj-kondo
meta.changelog for clj-kondo is: https://github.com/clj-kondo/clj-kondo/blob/v2024.03.13/CHANGELOG.md
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.03.13 with grep in /nix/store/b1ilkysbpvjp6d8ljhi7s8nvnm2hjy4z-clj-kondo-2024.03.13
found 2024.03.13 in filename of file in /nix/store/b1ilkysbpvjp6d8ljhi7s8nvnm2hjy4z-clj-kondo-2024.03.13

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
clj-kondo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b1ilkysbpvjp6d8ljhi7s8nvnm2hjy4z-clj-kondo-2024.03.13 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A clj-kondo https://github.com/r-ryantm/nixpkgs/archive/8f22f2aefff9d18df80f0504be0ff6fae94419a0.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/8f22f2aefff9d18df80f0504be0ff6fae94419a0#clj-kondo

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b1ilkysbpvjp6d8ljhi7s8nvnm2hjy4z-clj-kondo-2024.03.13
ls -la /nix/store/b1ilkysbpvjp6d8ljhi7s8nvnm2hjy4z-clj-kondo-2024.03.13/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

clj-kondo

Maintainer pings
cc @jlesquembre @bennyandresen for testing.


chore(docs): fix typo in conan install step in readme

Fixes a typo in the README.md for the conan install step
Fixes #915

Thanks!


Bring BVReorderTableView to Xcode 6+ and iOS7/iOS8 standards

This goes hand-in-hand with StackOverflow question UITableView tap and hold + drag and drop for which BVReorderTableView is an elegant solution.

@bvogelzang What would you think about reviewing/merging some of these pull requests? Lots of work has gone into your library.


[Distributed] Add macros to module; early stubs and resolve

Kicking off work on macros for distributed protocol #resolve.
SE Proposal: https://github.com/apple/swift-evolution/pull/2277 // TODO: not updated for macros yet.

Giving this a jab if I broke anything unexpected

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


Update ctest to 0.2

@alexcrichton: no appropriate reviewer found, use r? to override

@bors: r+

:pushpin: Commit e72f187cd42565c85f4f20bac470d28e9a3a141b has been approved by alexcrichton

:hourglass: Testing commit e72f187cd42565c85f4f20bac470d28e9a3a141b with merge 2c063c243f1856f2e40af81d91bca12f8f2ede77...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 2c063c243f1856f2e40af81d91bca12f8f2ede77 to master...


Allow chain to accumulate error types

Allows chaining Either methods to accumulate a union of error types.
Example
import * as T from 'io-ts'
import {Either, left, right} from 'fp-ts/lib/Either

const isBuffer = (x: any): Either<S3Error, Buffer> =>
    Buffer.isBuffer(x) ? right(x) : left(S3Error.NotBuffer)

export const validateData = (data: any):  =>
    isBuffer(data)
    .map(x => x.toString())
    .chain(x => T.validate(x, Project))

Without this chain is unable to match S3Error and T.ValidationError[]
I think this strictly speaking breaks FantasyLand spec but it seems useful to unify the error types.
Alternative solution is to cast up the Either type when you call the method, but it requires to to add all the other errors that could come along.
import * as T from 'io-ts'
import {Either, left, right} from 'fp-ts/lib/Either

const isBuffer = (x: any): Either<S3Error, Buffer> =>
    Buffer.isBuffer(x) ? right(x) : left(S3Error.NotBuffer)

export const validateData = (data: any):  =>
    (isBuffer(data) as Either<S3Error | T.ValidationError[], Buffer>)
    .map(x => x.toString())
    .chain(x => T.validate(x, Project))

I'm also experiencing some pain in this area. I've noticed that I'm having to add type annotations in many places where it would ideally be inferred. Example and workaround:
import * as either from 'fp-ts/lib/Either';
import { Either } from 'fp-ts/lib/Either';

const typecheck = <A>(a: A) => a;

const myE = either.right<string, string>('foo');
const myFn = (s: string): Either<number, string> => either.right(s);

{
    const myE2 = myE.chain(myFn) // error: Type 'number' is not assignable to type 'string'.
}
// Workaround 1: annotate chained either
{
    const myE2 = typecheck<Either<number | string, string>>(myE)
        .chain(myFn)
}
// Workaround 2: annotate left value
{
    const myE2 = myE
        .mapLeft(error => typecheck<number | string>(error))
        .chain(myFn)
}

@gcanti Do you have any ideas on this?

@OliverJAsh @DylanRJohnston That's not compatible with the definition of Chain.
Expect bad things to happen when you do not stick with definitions.......

@DylanRJohnston
I understand all what you're saying :)
'Either<L, _>' (<= partial type application) is a Monad, if you decide to change the type of the Left side, then, it's no more a Monad (monad is parametrized over one Type param), meaning you can no more abstract over it as a Monad, that's all.
What you're proposing is a handy combinator but not the chain function of the Chain type class.
Oh I've seen your changes :)
It's interesting to note that within a language with Union types, those patterns are now available that were not possible in other FP without this feature.
We should maybe think more about all this new power and how to tame it.. (new type classes for HKT2 types?)
Maybe stealth from somewhere.. I haven't looked into it.
@gcanti have you?

@sledorze I understand that Monads in Haskell are over one type parameter, but there's no reason why that has the to be the case in general. The categorical theory behind it allows it. Edward Kmett talks about doing something similar in this talk: https://www.youtube.com/watch?v=Klwkt9oJwg0.

@DylanRJohnston oh sure, you can have some morphisms to make that a monad but you need to apply them beforehand, that's not the case here.

I've been thinking about this some more. I think the issue at the heart of this is the way tagged unions work in TypeScript. Example:
{
    interface TwitterApiError { type: 'TwitterApiError' }
    const fetchTwitter = (): Either<TwitterApiError, string> => either.right('foo');

    interface GitHubApiError { type: 'GitHubApiError' }
    const fetchGitHub = (): Either<GitHubApiError, string> => either.right('foo');

    type ParentError = TwitterApiError | GitHubApiError;
    const fetchTwitterAndGitHub = (): Either<ParentError, string> =>
        fetchTwitter()
            // error: Type '"GitHubApiError"' is not assignable to type '"TwitterApiError"'.
            .chain(fetchGitHub)
}

As you can see, this is a problem when you want to compose functions that return Eithers with different types on the left hand side.
Is there any way we can make this a better experience, without breaking any FP laws?

FP laws promise us there can only ever be one error, right? So the output type of Either.chain should be an Either with the left side being of either type.
chain<L2, B>(f: (a: A) => Either<L2, B>): Either<L | L2, B>
Because Either always specifically makes sure only one error propagates, this type should still be correct, without breaking any FP laws. In case of L = L2, TypeScript will reduce ConcreteL | ConcreteL to just ConcreteL. If we go up the abstraction, chain is only defined over B, so the Monad laws don't care how we treat the left side of an Either.

So, basically, there's no reason for chain_, you can just define the regular chain as accumulating errors and still be correct.

In Elm I can write:
fetchFoo x = Err "foo"
fetchBar x = Err 1
type FetchFooAndBarError string number = FooError string | BarError number
fetchFooAndBar =
  fetchFoo "foo" |>
    Result.mapError FooError |>
    Result.andThen
      (\s -> (Result.mapError BarError (fetchBar s)))

Result.andThen (chain) knows that FooError and BarError are part of the FetchFooAndBarError tagged union, so it doesn't error.
The same thing in TypeScript with fp-ts would need manual type widening:
const fetchFoo = (): Either<string, string> => either.of('foo');
const fetchBar = (): Either<number, string> => either.of('foo');

class FooError {
    constructor(public error: string) {}
}
class BarError {
    constructor(public error: number) {}
}
type FetchFooAndBarError = FooError | BarError;
const fetchFooAndBar = (): Either<FetchFooAndBarError, string> =>
    fetchFoo()
        .mapLeft(error => new FooError(error))
        // Manually widen type of Left generic
        .mapLeft((error): FetchFooAndBarError => error)
        .chain(() => fetchBar().mapLeft(error => new BarError(error)));

@OliverJAsh Type inference, being local, needs a hint
export const fetchFooAndBar = (): Either<FetchFooAndBarError, string> =>
  fetchFoo()
    .mapLeft<FetchFooAndBarError>(error => new FooError(error))
    .chain(() => fetchBar().mapLeft(error => new BarError(error)))

otherwise infers mapLeft<FooError>

@OliverJAsh, if you want to use it now I just have this module extension defined in my project.
import { Either } from 'fp-ts/lib/Either'

declare module 'fp-ts/lib/Either' {
  export interface Left<L, A> {
    chain<B, L2>(f: (a: A) => Either<L2, B>): Either<L | L2, B>
  }

  export interface Right<L, A> {
    chain<B, L2>(f: (a: A) => Either<L2, B>): Either<L | L2, B>
  }

  export function of<R>(r: R): Either<never, R>
}

export * from 'fp-ts/lib/Either'

Closing due to lack of interest

For anyone interested, here is an explanation of why TypeScript does not infer a union for generics:
https://stackoverflow.com/a/39905723/5932012

I've found that using unionize to represent tagged union types aka sum types helps a lot with this—you don't have to manually widen to the union types, because the record constructors return the union type. Here is an example:
{
    type Cases<T> = {
        foo: () => T;
        bar: () => T;
    };
    const match = <T>(cases: Cases<T>) => {};

    {
        class Foo {
            readonly type = 'foo';
        }
        class Bar {
            readonly type = 'bar';
        }
        type Type = Foo | Bar;
        match(
            /*
            Error:
            Argument of type '{ foo: () => Foo; bar: () => Bar; }' is not assignable to parameter of type 'Cases<Foo>'.
                Types of property 'bar' are incompatible.
                    Type '() => Bar' is not assignable to type '() => Foo'.
                        Type 'Bar' is not assignable to type 'Foo'.
                        Types of property 'type' are incompatible.
                            Type '"bar"' is not assignable to type '"foo"'.
            */
            {
                foo: () => new Foo(),
                bar: () => new Bar(),
            },
        );
    }

    {
        const Type = unionize({
            Foo: ofType<{ fooId: string }>(),
            Bar: ofType<{ barId: string }>(),
        });
        // No error!
        match({
            foo: () => Type.Foo({ fooId: 'foo' }),
            bar: () => Type.Bar({ barId: 'bar' }),
        });

        // This works because the record constructors for the sum type return the union type, not
        // the record type:
        const foo = Type.Foo({ fooId: 'foo' });
        foo.tag; // "Foo" | "Bar"
    }
}


Fauxbar Address Box matches “Error: URl malformed” text

When typing characters in the Fauxbar Address Box, it returns hits for bookmarks marked “Error: URl malformed” (it matches on the substring “URl malformed”). So when I type “med”, it highlights all “URl malforMED”. Can you change this behaviour?
PS: The “Error” bookmarks are those with embedded “%s” which are compatible with another Chrome extension that has the ability to substitute %s with address bar text provided as a search string.
Thanks for a brilliant extension!

Thanks for reporting both issues.
It seems Fauxbar's urldecode method is failing to parse the URL since %s is not a valid encoding character (eg doesn't match anything on this HTML encoding list).
I will likely investigate seeing if, in the event of it failing to decode, if returning the URL as is would work better.

Fixed in v1.8.0. Added a catch to just return the URL as is if the URI malformed error is encountered.


Two different official lists of supported SDXL resolutions - which one to use?

I've had recently short discussion with Fooocus author about official list of supported resolutions, because currently there is a discrepancy between list in SDXL research paper (Appendix I), and your code.
Could you please explain which one of those list is complete and fully supported by SDXL models list of resolutions and aspect ratios, and then stick to it in both paper, and the code? We shouldn't have 2 different sources of truth here.

@ablattmann It was your commit with that list, I believe - could you explain that difference?

Additional questions:

are both 704x1344 and 1344x704 supported? (SDXL paper is not symmetrical, but both are in src)
what are supported aspect range ratios? (SDXL paper goes from 0.25 to 4.0, src goes from 0.5 to 3.0)
are custom resolutions (not included in official resolution list) but close to 1 MP and using width / height with 64 px steps okay? let's say something like 1152x768 (3:2, 0.84 MP), 960x1280 (3:4, 1.17 MP), 1024x1280 (4:5, 1.25 MP), etc. - could we offer resolutions like that to the end users? and if so - on what ground (math / scientific justification), and what are safe limits (in terms of MP / aspect ratio)?


crossbeam-channel v0.3.9 fails to compile

After bumping the rustc-ap-* crates in rustfmt, I get
error[E0432]: unresolved import `crossbeam_utils::atomic`
 --> /home/r/.cargo/registry/src/github.com-1ecc6299db9ec823/crossbeam-channel-0.3.9/src/flavors/tick.rs:8:22
  |
8 | use crossbeam_utils::atomic::AtomicCell;
  |                      ^^^^^^ could not find `atomic` in `crossbeam_utils`

The dependency tree looks as follows:
crossbeam-channel v0.3.9
└── crossbeam-utils v0.6.6
    ├── cfg-if v0.1.10
    └── lazy_static v1.4.0

I was able to fix the build with
cargo update -p crossbeam-utils --precise 0.6.5

Actually turns out that even without bumping anything, rustfmt master with its current lockfile just doesn't build here...?
$ rustc --version
rustc 1.40.0-nightly (237d54ff6 2019-10-15)

https://github.com/rust-lang/rust/issues/65424 explains what is going on: the crate was relying on a nightly feature that got changed.

Duplicate of https://github.com/crossbeam-rs/crossbeam/issues/434, fixed by https://github.com/crossbeam-rs/crossbeam/commit/5b5d727fcd2616b1f5314db03f4e6b96791a303d but there is no new release yet.

Is there an eta on a new release? I am a bit hamstrung at the moment.

New version has been published now :)


add support to cookieless Google Analytics

we may want cookieless thinking about the direction things are moving (the "cookieless future"), and to avoid updating the accept cookies banner

to enable cookieless GA we would need to have some work setting up GTM for server-side events and etc. (https://developers.google.com/tag-platform/tag-manager/server-side/intro)
on a second thought, I think I'll start with Plausible and see how it goes


Spring auto configuration failed when the container has multiple ObjectMapper beans

Parameter 0 of method jsonFormatter in org.zalando.logbook.spring.LogbookAutoConfiguration required a single bean, but 2 were found:

Similar issue: https://github.com/spring-projects/spring-boot/issues/6529
Usually, we can avoid error to specify @Primary annotation to one of ObjectMapper bean.  But how can we do when we want to use other ObjectMapper for each auto configurations?

for each auto configurations

Which auto configurations are yo referring to? Do you want a special ObjectMapper just for the logging?

Yes, our projects register multiple ObjectMapper beans for each role.
For http request / response body, for denormalized data on database, for event messaging, and so on.
Each ObjectMapper has different configuration.  So we want define new ObjectMapper bean for logbook.

Ok, got it, fundamentally I think it's purely a Spring issue and not really related to Logbook. Having said that, the easiest way that I see to resolve your issue is to define the following bean yourself:
@Bean
public HttpLogFormatter jsonFormatter(@Qualifier("special") final ObjectMapper mapper) {
    return new JsonHttpLogFormatter(mapper);
}

Thank you, my issue is resolved! 😉


Binance error

System information

Have I written custom code (as opposed to using zenbot vanilla): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Debian 9
Zenbot version (commit ref, or version): current unstable
Exact command to reproduce (include everything): ./zenbot.sh trade binance.BTC-USDT
Did I make any changes to conf-sample.js?: no

Describe the problem
Binance is giving me the "Way too many requests" error when backfilling and wants us to use the websocket instead
Source code / Error logs

I have about 150 dockers running to Binance and never get this ban, how many requests do you do to come to that point??
Just so I know, I did change the polling settings to 30s but still.

Wow that's crazy, I was running like 20 instances. My polling rate was at 30s too. I think the problem may have been because I was trying to backfill multiple instances at the same time. Either way that ban was temporary.

Oh yeah, I use a backfill script on one node that does it for each trading pair in serial, not concurrent, and slowly filled my central mongodb up every day by adding like 5 more days.
The issue you opened is a thing we gotta address nevertheless.

Actually I just made a pull request that backfills data from Binance using candle data instead of raw trade data. It was merged today. It calls the API way less and backfills like 20x faster. This could completely solve the problem but we won't know for sure unless we get another error like above.


[dv] Switch DV's Makefiles to calling Meson for SW builds

I don't actually know what the correct files to emit are, so I've mostly just guessed from what the Makefiles currently do; however, calling make sw_build with the appropriate environment variables for selecting a test will build the right SW targets and copy .bin files that look correct into the same places the old Make call would. shrug
I have no way to test this, so I'd appreciate if someone in the know (@sriyerg, do you have opinions?) can point out if I'm doing anything obviously wrong. Currently there is no "DV" platform in Meson, because DV does not seem to really do anything special. It's not hard to add this, but I don't really know how it should be different from fpga (which is kind of the "default" platform right now). For reference, the two things that sim-verilator changes are the baud rate for UART and the iteration count for coremark.

@tjaychen and @weicaiyang for visibility in @sriyerg 's absence (back EO next week)

@mcy I just tried to run DV with this PR and it didn't work.
DV needs below 2 files to run, but I'm not sure how Meson can generate these 2 files.
/edascratch/weicai-opentitan/sanity_openTitan/vcs/top_earlgrey/chip_sanity/latest/sw_build/rom/rom.vmem
/edascratch/weicai-opentitan/sanity_openTitan/vcs/top_earlgrey/chip_sanity/latest/sw_build/sw/sw.vmem

BTW, we may need to add Meson as required software at
https://github.com/lowRISC/opentitan/blob/master/doc/ug/install_instructions/index.md#install-required-software

i can help have a look at this also..sorry still catching up...

@weicaiyang I've updated the change to copy over the vmem files; let me know if they wind up in the right place. Also; meson is already required software: it's in requirements.py.

thanks Miguel and Weicai!
On Fri, Dec 6, 2019 at 8:36 AM Garret Kelly<EMAIL_ADDRESS>wrote:

Merged #1117 https://github.com/lowRISC/opentitan/pull/1117 into master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/1117?email_source=notifications&email_token=AAH2RSVVH4F2F5UVAAH5QW3QXJ5QJA5CNFSM4JUEN5D2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVKLP2IY#event-2862021923,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSSNVGZJK3JJDNMCJT3QXJ5QJANCNFSM4JUEN5DQ
.


Update MD file on new branch 2017-11-15_15-24-29

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Where to change english month names to spanish month names

Hi, I was able to transalate to Spanish almost 99% using your instractions for translation. However, I can not find a way to show the spanish month names, for example:
Jan = ENERO
Feb = Febrero
etc...
This is a great program, thank for  your help.

Please use the https://github.com/prashants/webzash repository. This is old defunct version which is no longer maintained.


Hide grant award amount

The grant amount should be hidden until the researcher decides to reveal it. I'll talk to Kimmy about how the reveal should be depicted.

Agreed, we are working under the assumption that anything in the experts linked database is public, and therefore, we need to make that available to the harvester (or conceivably sooner, to FIS) so it isn't propagated.  Technically, it's not hard, the trick is in the fact that this is local information, and our goal is to not jump over that fence until after the first prototype.
Realistically, we could pretty easily work w/ CDL to get some of these flags to the profile, but it would probably look strange to the other UCs.

We should discuss purchasing the grants module.

The grants module can accept grant amounts.
For now we are leaving the grant amounts off the data that we are pulling into Aggie Experts.
We'll revisit this topic at a later time.


Locate startup type by name or assembly.

#254
Previously you could use the config variable Hosting:Application or app to specify the assembly in which to find your Startup class.
I've expanded that field so that you can optionally specify a fully qualified type name, including the assembly. MyType, MyAssembly.... This also combines with your current dev/production environment  setting so that we will auto locate MyTypeDev if you ask for MyType.
@muratg @davidfowl @Matthew-Bonner

:shipit:

Can we hair support the assembly name?

Hair?

Just Assembly name is still supported.

I mean dropping support for type name. It's a pretty obscure syntax. Let's just use the pattern we have been using. You can specify the assembly but not he type name. It has to be called startup

yeah especially since I just went and nuked this same logic in ServerLoader for the sake of simplicity...
https://github.com/aspnet/Hosting/pull/295

I agree with supporting only the assembly name. Even the type name lookup is already fancy - don't we support Startup{EnvironmentName} already?

Yeah Startup{Env}, Configure{Env}, Configure{Env}Services I think

I thought one of the points of #254 was the ability to directly specify a startup type. If you want to keep it constrained to specifying an assembly the we don't need this PR at all. The startup assembly can already be specified via the Hosting:Application config entry.


Lint/BinaryOperatorWithIdenticalOperands raises error following merge of #8478

Following updating to rubocop 0.89.1, we are getting an error when passing one of our files. I suspect something in #8478 has caused the issue as the line in question includes a *.

Expected behavior
Run lint without errors
Actual behavior
When running the lint, the following message appeared
1 error occurred:
An error occurred while Lint/BinaryOperatorWithIdenticalOperands cop was inspecting /path_to_file/expire.rb:74:44.
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
https://github.com/rubocop-hq/rubocop/issues

Mention the following information in the issue report:
0.89.1 (using Parser <IP_ADDRESS>, rubocop-ast 0.3.0, running on ruby 2.6.5 x86_64-darwin18)

Steps to reproduce the problem
The line which triggers the error includes the following Sequel.function(:count).*
While a little unusual, it is valid Ruby and a necessary part of the Sequel gem see docs
RuboCop version
$ bundle exec rubocop -V
0.89.1 (using Parser <IP_ADDRESS>, rubocop-ast 0.3.0, running on ruby 2.6.5 x86_64-darwin18)

OMG, I never thought of using these operators like that, kind of cute and kind of horrific 😆
That's my bad I think, I'll fix this, sorry for the trouble.


Tinycrad can't find libhsa because hardcoded /lib in the code.

By this line https://github.com/tinygrad/tinygrad/blob/master/tinygrad/runtime/autogen/hsa.py#L32C92-L32C98 they try to find lib by /lib/libhsa-runtime64.so inside ROCM_PATH, but on my system (Gentoo) this file in lib64 - /usr/lib64/libhsa-runtime64.so .
I don't think we should use absolute path in that case, it should be follow by ld.so

We can use --print-file-name to find path to lib:
$: gcc --print-file-name=libhsa-runtime64.so
/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../lib64/libhsa-runtime64.so

$: clang --print-file-name=libhsa-runtime64.so
/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../lib64/libhsa-runtime64.so


fix: Use correct branch for coverage badge

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fixed some minor typos

Hope this helps ✌

@Ashikpaul : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Creat new objects parameterized with posterior mean

Dear Maih,
With the illumination of issue #80 , I know how to creat new objects parameterized with randomly drawed parameter set by running "[draw,m1]=draw_parameter(m0,Results.pop)", or parameterized with the best drawed parameter set by running "[draw,m1]=draw_parameter(m0,Results.pop(best))".
My question is, after implement MCMC sampling, how can I creat new objects parameterized with other parameter sets, such as the having computed posterior mean parameter set called "Mean", or some other self-defined parameter sets?
Best,
Kairey

Hi,
You parameterize a model using the samples you obtained from the MCMC procedure. You cannot parameterize the model with the mean or any other quantile of the parameters. This is in part because those quantiles need not be valid parameter vectors.
If, say, you want to compute the mean of the impulse responses, the way to go about it is to compute impulse responses for many parameterizations of the model and then average those impulse responses.
This is the way to go about it for any other statistic you have in mind.
Cheers,
J.