Volume plugin pulseaudio support

Thanks so much for your quick work at resolving issues so far :)
Would it be possible to extend the volume plugin to allow for pulseaudio support?
You might be able to merge the volume plugin code from lxpanel back in which does support pulseaudio...
A right-click option like you have for the tclock plugin could allow the user to open a mixer of their choice eg pavucontrol
Also, it would be ideal if the volume slider would disappear when you click off it rather than having to click back on the icon to close it (same for calendar/tclock plugin) - this maybe a separate issue.
Thanks!

I prefer to have such functionality to be implemented as a separate program. It runs as deamon and provides XEMBED icon for gui.
These projects look intresting:

ipha/pulse-volumeicon
Maato/volumeicon (I use  this one)

The criteria for plugin is low dependency, here in order of preference

no external deps at all
accessing /proc, /sys only
acessing disk
launching smth very common, like wget


[FEATURE REQUEST] Add possibility to use dynamic modules like in nginx, apache, php, etc.

The main idea of the request is to have CORE of the roadrunner with minimal necessary functionality, e.g. http module, or probably more general (logging, monitoring, workers scheduling, ...) and have dynamic pluggable modules for the main roadrunner role.
As result we can have robust core with officially supported main-modules:

roadrunner binary with: logging, monitoring, scheduling, ...
pluggable part: http.so, grpc.so, jobs.so, ...

How to plug those modules

Section may have naming like: load-module: http.so
All module related configs will be parsed on module side

Duplicate: #474


Define qualitative data JSON

Define JSON data structure for qualitative data:

Description of overall architecture;
How does the validator automate things / what tools do they use;
What approaches does the validator use for logging, metrics, monitoring, and observability;
How does the validator alert when things go wrong: monitoring system;
Key handling policies;
Failover and or high availability approaches;
Scenario runbooks (how do they upgrade, how do they migrate servers);
Which providers does the validator use (gcp, aws, azure, etc);
Role Based Access Control Policies (who has access to their infra, who can make changes, etc);
Stake management automation (how does the validator determine the efficiency of their own stake);
DDoS Protection (especially now that sentries are going to be removed);
Communication - how does the validator actively communicate with its nominators, what channels / platforms do they use;
Does the validator produce education content (blog posts and tutorials);
Monitoring and alert system in place: yes/no?;
Which regions do they operate in?;
Are they active in Riot / Telegram / other platforms?;
Does the validator offer support in Riot / Telegram / other platforms?.
Does the validator contribute with open source tools? Must include links to the repositories.


Symbol range incorrect for functions and classes

 Environment data

Language Server version: 2021.2.4
OS and version: darwin x64
Python version (and distribution if applicable, e.g. Anaconda):
python.analysis.indexing: undefined
python.analysis.typeCheckingMode: off

 Expected behaviour
When calling documentSymbol.range, I'd expect it to return the exact range of the function, eg

 Actual behaviour
It returns the range of the function and part of the next few lines:

 Logs

Python Language Server Log
[Info  - 4:03:04 PM] Pylance language server 2021.2.4 (pyright a18e6fb4) starting
[Info  - 4:03:04 PM] Server root directory: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist
[Info  - 8:32:05 PM] No configuration file found.
[Info  - 8:32:05 PM] Setting pythonPath for service "pokey_talon"<EMAIL_ADDRESS>Search paths found for configured python interpreter:
<EMAIL_ADDRESS><EMAIL_ADDRESS>  /Users/pokey/Library/Python/3.9/lib/python/site-packages
  /usr/local/lib/python3.9/site-packages
  /usr/local/Cellar/protobuf/3.14.0/libexec/lib/python3.9/site-packages
[Info  - 8:32:05 PM] Assuming Python version 3.9
[Info  - 8:32:05 PM] Assuming Python platform Darwin
[Info  - 8:32:05 PM] Searching for source files
[Info  - 8:32:05 PM] Found 82 source files
Background analysis message: setConfigOptions
Background analysis message: setTrackedFiles
Background analysis message: markAllFilesDirty
Background analysis message: getSemanticTokens
[BG(1)] parsing: /Users/pokey/src/pokey_talon/apps/vscode/command_client.py (24ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 1ms] (41ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/builtins.pyi (16ms)
[BG(1)] binding: /Users/pokey/src/pokey_talon/apps/vscode/command_client.py (2ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/queue.pyi [fs read 0ms] (1ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/queue.pyi (1ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (6ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/typing.pyi [fs read 2ms] (13ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/typing.pyi (8ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stubs/typing-extensions/typing_extensions.pyi [fs read 0ms] (2ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stubs/typing-extensions/typing_extensions.pyi (1ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/threading.pyi [fs read 0ms] (5ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/threading.pyi (3ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/time.pyi [fs read 0ms] (2ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/time.pyi (1ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/__init__.pyi [fs read 0ms] (19ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/__init__.pyi (0ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/__init__.pyi [fs read 1ms] (2ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/__init__.pyi (0ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/context.pyi [fs read 1ms] (11ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/context.pyi (2ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/module.pyi [fs read 0ms] (1ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/module.pyi (0ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/datetime.pyi [fs read 1ms] (3ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/datetime.pyi (2ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/pathlib.pyi [fs read 1ms] (2ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/pathlib.pyi (1ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/os/__init__.pyi [fs read 1ms] (7ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/os/__init__.pyi (3ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/abc.pyi [fs read 0ms] (1ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/abc.pyi (0ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/json/__init__.pyi [fs read 1ms] (1ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/json/__init__.pyi (2ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/app.pyi [fs read 1ms] (3ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/app.pyi (1ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/enum.pyi [fs read 0ms] (1ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/enum.pyi (0ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/dataclasses.pyi [fs read 0ms] (0ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/dataclasses.pyi (0ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/actions.pyi [fs read 1ms] (2ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/actions.pyi (0ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/json/encoder.pyi [fs read 0ms] (0ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/json/encoder.pyi (0ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/io.pyi [fs read 1ms] (5ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/io.pyi (3ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/types.pyi [fs read 0ms] (4ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/types.pyi (2ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/registry.pyi [fs read 1ms] (2ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/registry.pyi (3ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/dispatch.pyi [fs read 0ms] (1ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/dispatch.pyi (0ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/types.pyi [fs read 0ms] (2ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/types.pyi (1ms)
Background analysis message: getSemanticTokens
[BG(1)] parsing: /Users/pokey/src/pokey_talon/apps/vscode/vscode.py (3ms)
[BG(1)] binding: /Users/pokey/src/pokey_talon/apps/vscode/vscode.py (2ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/socket.pyi [fs read 1ms] (6ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/socket.pyi (3ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/scope.pyi [fs read 0ms] (1ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/scope.pyi (0ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/match.pyi [fs read 0ms] (1ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/match.pyi (0ms)
Background analysis message: getSemanticTokens
[BG(1)] parsing: /Users/pokey/src/pokey_talon/code/code.py (3ms)
[BG(1)] binding: /Users/pokey/src/pokey_talon/code/code.py (1ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/settings.pyi [fs read 0ms] (1ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/scripting/settings.pyi (0ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/imgui.pyi [fs read 0ms] (5ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/imgui.pyi (2ms)
Background analysis message: getSemanticTokens
[BG(1)] parsing: /Users/pokey/src/pokey_talon/code/parrot.py (0ms)
[BG(1)] binding: /Users/pokey/src/pokey_talon/code/parrot.py (1ms)
Background analysis message: getSemanticTokens
[BG(1)] parsing: /Users/pokey/src/pokey_talon/apps/mac/safari.py (0ms)
[BG(1)] binding: /Users/pokey/src/pokey_talon/apps/mac/safari.py (0ms)
Background analysis message: getSemanticTokens
[BG(1)] parsing: /Users/pokey/src/pokey_talon/apps/mac/things3.py (2ms)
[BG(1)] binding: /Users/pokey/src/pokey_talon/apps/mac/things3.py (0ms)
Background analysis message: getSemanticTokens
[BG(1)] parsing: /Users/pokey/src/pokey_talon/code/tabs.py (0ms)
[BG(1)] binding: /Users/pokey/src/pokey_talon/code/tabs.py (0ms)
Background analysis message: getSemanticTokens
[BG(1)] parsing: /Users/pokey/src/pokey_talon/apps/slack/slack.py (0ms)
[BG(1)] binding: /Users/pokey/src/pokey_talon/apps/slack/slack.py (0ms)
Background analysis message: getSemanticTokens
[BG(1)] parsing: /Users/pokey/src/pokey_talon/code/todo_list.py (0ms)
[BG(1)] binding: /Users/pokey/src/pokey_talon/code/todo_list.py (0ms)
Background analysis message: getSemanticTokens
[BG(1)] parsing: /Users/pokey/src/pokey_talon/code/find_and_replace.py (0ms)
[BG(1)] binding: /Users/pokey/src/pokey_talon/code/find_and_replace.py (0ms)
Background analysis message: getSemanticTokens
[BG(1)] parsing: /Users/pokey/src/pokey_talon/code/switcher.py (2ms)
[BG(1)] binding: /Users/pokey/src/pokey_talon/code/switcher.py (2ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/re.pyi [fs read 0ms] (1ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/re.pyi (1ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/os/path.pyi [fs read 0ms] (2ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/os/path.pyi (0ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/ui.pyi [fs read 0ms] (6ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/ui.pyi ...
[BG(1)]   parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/mac/ui.pyi [fs read 0ms] (1ms)
[BG(1)]   binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/mac/ui.pyi (1ms)
[BG(1)]   parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/linux/ui.pyi [fs read 0ms] (2ms)
[BG(1)]   binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/linux/ui.pyi (0ms)
[BG(1)]   parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/windows/ui.pyi [fs read 0ms] (5ms)
[BG(1)]   binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/windows/ui.pyi (0ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/ui.pyi (11ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/fs.pyi [fs read 0ms] (3ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/fs.pyi (0ms)
[BG(1)] parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/system.pyi [fs read 0ms] (1ms)
[BG(1)] binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/system.pyi (0ms)
[BG(1)] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/posix.pyi [fs read 0ms] (1ms)
[BG(1)] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/posix.pyi (2ms)
Background analysis message: analyze
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/apps/mac/safari.py ...
[BG(1)]   checking: /Users/pokey/src/pokey_talon/apps/mac/safari.py ...
[BG(1)]     parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/ctrl.pyi [fs read 1ms] (7ms)
[BG(1)]     binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/ctrl.pyi ...
[BG(1)]       parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/mac/ctrl.pyi [fs read 1ms] (1ms)
[BG(1)]       binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/mac/ctrl.pyi (0ms)
[BG(1)]       parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/linux/ctrl.pyi [fs read 0ms] (4ms)
[BG(1)]       binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/linux/ctrl.pyi (0ms)
[BG(1)]       parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/windows/ctrl.pyi [fs read 1ms] (2ms)
[BG(1)]       binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/windows/ctrl.pyi (1ms)
[BG(1)]     binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/ctrl.pyi (9ms)
[BG(1)]     parsing: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/clip.pyi [fs read 0ms] (2ms)
[BG(1)]     binding: /Applications/Talon.app/Contents/Resources/python/lib/python3.9/site-packages/talon/clip.pyi (0ms)
[BG(1)]   checking: /Users/pokey/src/pokey_talon/apps/mac/safari.py (19ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/apps/mac/safari.py (19ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/apps/slack/slack.py ...
[BG(1)]   checking: /Users/pokey/src/pokey_talon/apps/slack/slack.py (0ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/apps/slack/slack.py (0ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/apps/vscode/command_client.py ...
[BG(1)]   checking: /Users/pokey/src/pokey_talon/apps/vscode/command_client.py (3ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/apps/vscode/command_client.py (3ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/apps/vscode/vscode.py ...
[BG(1)]   checking: /Users/pokey/src/pokey_talon/apps/vscode/vscode.py (8ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/apps/vscode/vscode.py (8ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/code/code.py ...
[BG(1)]   checking: /Users/pokey/src/pokey_talon/code/code.py (11ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/code/code.py (11ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/code/find_and_replace.py ...
[BG(1)]   checking: /Users/pokey/src/pokey_talon/code/find_and_replace.py (1ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/code/find_and_replace.py (1ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/code/parrot.py ...
[BG(1)]   checking: /Users/pokey/src/pokey_talon/code/parrot.py (1ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/code/parrot.py (1ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/code/switcher.py ...
[BG(1)]   checking: /Users/pokey/src/pokey_talon/code/switcher.py (10ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/code/switcher.py (10ms)
Background analysis message: resumeAnalysis
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/code/tabs.py ...
[BG(1)]   checking: /Users/pokey/src/pokey_talon/code/tabs.py (0ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/code/tabs.py (0ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/apps/mac/things3.py ...
[BG(1)]   checking: /Users/pokey/src/pokey_talon/apps/mac/things3.py (1ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/apps/mac/things3.py (1ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/code/todo_list.py ...
[BG(1)]   checking: /Users/pokey/src/pokey_talon/code/todo_list.py (1ms)
[BG(1)] analyzing: /Users/pokey/src/pokey_talon/code/todo_list.py (1ms)
Background analysis message: resumeAnalysis
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[FG] parsing: /Users/pokey/src/pokey_talon/code/switcher.py (19ms)
[FG] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 0ms] (52ms)
[FG] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/builtins.pyi (17ms)
[FG] binding: /Users/pokey/src/pokey_talon/code/switcher.py (2ms)
[FG] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (7ms)
[FG] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (0ms)
[FG] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/typing.pyi [fs read 0ms] (19ms)
[FG] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/typing.pyi (3ms)
[FG] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stubs/typing-extensions/typing_extensions.pyi [fs read 0ms] (2ms)
[FG] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stubs/typing-extensions/typing_extensions.pyi (0ms)
[FG] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/re.pyi [fs read 0ms] (5ms)
[FG] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/re.pyi (0ms)
[FG] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/abc.pyi [fs read 0ms] (0ms)
[FG] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/abc.pyi (0ms)
[FG] parsing: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/enum.pyi [fs read 0ms] (1ms)
[FG] binding: /Users/pokey/.vscode/extensions/ms-python.vscode-pylance-2021.2.4/dist/typeshed-fallback/stdlib/enum.pyi (1ms)
[FG] parsing<EMAIL_ADDRESS>[fs read 1ms] (16ms)
[FG] binding<EMAIL_ADDRESS>(2ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange

 Code Snippet / Additional information

XXX

Out of curiosity, how did you obtain the highlighting like that?

https://marketplace.visualstudio.com/items?itemName=pokey.semantic-movement

Thanks for the bug report and repro steps. This will be fixed in the next release.
Here's the change if you're interested: https://github.com/microsoft/pyright/commit/c575ed0790132eb861cae1680b0e92653a2573e9

Awesome thanks!

We'll leave the bug open until the fix is released.

Well that seems awfully responsible 😄

This issue has been fixed in version 2021.3.1, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202131-10-march-2021

Confirmed fixed; thanks!


tsx - Babel loader in webpack.config.js

Hello, I was having issues with this { test: /\.ts(x?)$/, include: /ClientApp/, use: 'babel-loader' }, in your webpack.config.js (It used to display errors when building minif. production files.).
I change it to { test: /\.js(x?)$/, include: /ClientApp/, use: 'babel-loader' }, and now it's working properly.
Shouldn't it be .js(x?)$:  { test: /\.js(x?)$/, include: /ClientApp/, use: 'babel-loader' }, when we are using babel-loader instead of tsx?
Hope it makes sense.
Thank you

In the React templates in this repo, the source files are .tsx, so the Webpack config is correct as-is. You'd only change it to .jsx if you change your source files. The fact that you're using babel-loader is not relevant to the loader rules - all that matters are the names of the actual files on disk.


Update dependencies for Debian Bookworm

Summary
What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[x] Build-related changes
[ ] Other, please describe:

If changing the UI of web configuration, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing setups:
The PR fulfills these requirements:

[x] When resolving a specific issue, it's referenced in the PR's body (e.g. Fixes: #xxx[,#xxx], where "xxx" is the issue number)
Fixes: #1612
If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature

[ ] Related documents have been updated (docs/docs/en)

[ ] Related tests have been updated

PLEASE DON'T FORGET TO ADD YOUR CHANGES TO CHANGELOG.MD

[x] Yes, CHANGELOG.md is also updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:

Thank you for the PR. 👍


Default YOURLS_DB_PREFIX to blank as per documentation

Documentation at https://hub.docker.com/_/yourls/ states that YOURLS_DB_PREFIX should default to null.

Thanks for this PR, but I'll reject it for the reason given in https://github.com/YOURLS/docker-yourls/issues/45#issuecomment-591570085.
The whole line regarding YOURLS_DB_PREFIX was wrong, see https://github.com/docker-library/docs/pull/1662


Documentation of Model#validate can be misleading

In the Backbone 1.3.3 docs it is only mentioned in the section for the method Model#isValid that it:

Run validate to check the model state.

https://github.com/jashkenas/backbone/blob/master/index.html#L1612
However when inspecting the code it is clear that calling such a method can also trigger an "invalid" event and set the Model#validationError state (by means of its internal call to _validate).
https://github.com/jashkenas/backbone/blob/master/backbone.js#L737:L739
Such explanations can also be found in the annotated source https://github.com/jashkenas/backbone/blob/master/docs/backbone.html#L1854:L1890
Following the docs to the section for the method Model#validate is states:

If validate returns an error, save will not continue, and the model attributes will not be modified on the server. Failed validations trigger an "invalid" event, and set the validationError property on the model with the value returned by this method.

https://github.com/jashkenas/backbone/blob/0b2835f7fc479d7f2a6ebe4442d33aac5d38f86b/index.html#L1367:L1369
It is true it never mentions that it is the invocation of Model#validate what would cause the "invalid" event to be triggered, however the location in which the docs are placed and the order in which they are linked can lead to confusion. It at least happened to me and to some other colleagues when trying to explicitly test for the validity of a model.
My proposal would be to reorder some parts of the documentation between these two methods.

Do you have a specific change to the docs you'd like to propose?

@jashkenas  I've created a PR including my proposal: #4163

Merged. Thanks.


Calling reason truncated on call script screen

When the calling reason is more than 1 line the text is truncated. See screenshot.

Darn that used to work. Investigating.

Fixed in PR #31

Even works on iPhone 5!


June 2022 Doc Merge

Docs Build status updates of commit 8977376:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.md
:bulb:Suggestion
View
Details

docs/release-notes/Index.md
:white_check_mark:Succeeded
View

docs/release-notes/NuGet-6.2.md
:white_check_mark:Succeeded
View

docs/TOC.md

Line 68, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /azure/devops/artifacts/nuget/publish?view=azure-devops. Otherwise, remove the view parameter.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit bbee831:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.md
:bulb:Suggestion
View
Details

docs/release-notes/Index.md
:white_check_mark:Succeeded
View

docs/release-notes/NuGet-6.2.md
:white_check_mark:Succeeded
View

docs/TOC.md

Line 68, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /azure/devops/artifacts/nuget/publish?view=azure-devops. Otherwise, remove the view parameter.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Introduce a Update method to a resource using the PUT if it does not have a patch

This is a convenient method for those resources that do not have a patch, if we do not have this method, we will not have any way to update it inside the resource instance, we have to do it in the collection, which involves its parent.

Today if you have a resource object and it only provides a PUT method and no PATCH which acts as a CreateOrUpdate in order to update it you must do it from the parent since there will be no Update method generated on the resource class.
var resource = armClient.GetResource(id);
//this method won't exist
resource.Update(new ResourceData());

//instead customers must do something like this
var parent = armClient.GetParent(id.Parent);
var resourceCollection = parent.GetResources();
resourceCollection.CreateOrUpdate(id.Name, new ResourceData());

Since PUT works as a CreateOrUpdate then we should provide a duplicate copy of this method named Update on the resource class directly to avoid the inconvenience above.


1018 users can change the number of days each premises needs to allow for turnaround

Changes in this PR
This PR allows users to set, update and view the turnaround time for a premises. For now the changes are hidden behind a feature flag in prod, whilst we await full support for turnaround features in the UI and API.
I have also added the new premises summary endpoint to Wiremock, and created a premises summary factory, to allow continued local development against Wiremock.
Screenshots of UI changes
Before

After

Release checklist
Release process
documentation.
Pre-merge checklist

[ ] Are any changes required to dependent services for this change to work?
(eg. CAS API)
[ ] Have they been released to production already?

Post-merge checklist

[ ] Manually
approve
release to test
[ ] Manually
approve
release to preprod
[ ] Manually
approve
release to prod

 Users can change the number of days each premises needs to allow for turnaround


Looking for build czmq for iOS

Hi, can you please share your build experience with this thread?
https://github.com/zeromq/czmq/issues/1628
thx a lot!

No problem. I will do it right now 👍


Button not working when project exported to HTML5

Godot Version: 3.2 Mono Stable
Device/OS: Windows 10 Probook. Exported to Chrome Browser.
Description: Button Node with simple C# code to change scenes works in the editor, but when I export to HTML5, the button does not work. Instead, it gives this error:

Steps to reproduce: Make a Godot mono project. The main scene should have a button that changes scenes. Export this project. to HTML5.
Here's my project: https://github.com/NoohAlavi/bullet-hell-2
Edit 1: Just tried Windows Dekstop build.... it works... HTML5 doesn't.
Edit 2: I accidentally wrote Chrome OS before; meant chrome browser.
Edit 3: Updated Steps to reproduce and fixed Godot Version.

@NoohAlavi Please upload a minimal reproduction project to make this easier to troubleshoot. (It seems you didn't include a download link in OP.)

@Calinou Should I put the github link to the project?

@NoohAlavi Yes, that works fine :slightly_smiling_face:

CANNOT HANDLE COOKIE

@Calinou hey, just wanted to tell you that I experienced this same issue again, in a different project: html5 export, godot 3.2 mono, C#

CANNOT HANDLE COOKIE F

Judging by this warning I'm closing this issue as a duplicate of #36858


refactor: get rid of managedResource

What this PR changes/adds
removed the managedResource field on DataRequest and all the accessors because it had no more meaning in the current situation
Why it does that
refactoring
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes #3292
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

Codecov Report
Patch coverage: 100.00% and project coverage change: +54.43 :tada:

Comparison is base (034258e) 17.75% compared to head (ab3c3dc) 72.18%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #3297       +/-   ##
===========================================
+ Coverage   17.75%   72.18%   +54.43%
===========================================
  Files         837      837
  Lines       16867    16832       -35
  Branches      951      948        -3
===========================================
+ Hits         2994    12151     +9157
+ Misses      13795     4288     -9507
- Partials       78      393      +315

Impacted Files
Coverage Δ

...nsfer/provision/ResourceManifestGeneratorImpl.java
100.00% <ø> (+100.00%)
:arrow_up:

...ment/transferprocess/model/TransferRequestDto.java
100.00% <ø> (+76.74%)
:arrow_up:

...orm/JsonObjectToTransferRequestDtoTransformer.java
76.31% <ø> (+76.31%)
:arrow_up:

...ransferRequestDtoToTransferRequestTransformer.java
100.00% <ø> (+100.00%)
:arrow_up:

...s/store/schema/TransferProcessStoreStatements.java
96.29% <ø> (-0.14%)
:arrow_down:

...cess/store/schema/postgres/DataRequestMapping.java
100.00% <ø> (ø)

.../edc/connector/transfer/spi/types/DataRequest.java
23.80% <ø> (+23.80%)
:arrow_up:

...nector/transfer/spi/types/ProvisionedResource.java
86.36% <ø> (+86.36%)
:arrow_up:

...tor/transfer/spi/types/ProvisionedResourceSet.java
76.92% <ø> (+76.92%)
:arrow_up:

...r/transfer/process/TransferProcessManagerImpl.java
89.95% <100.00%> (+67.17%)
:arrow_up:

... and 3 more

... and 537 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Submit button re-enabled after form submit before redirecting user to another page

Hi,
I am facing the following problem:
When a user submits a form in my Rails 7 application the submit button is disabled. After a form is submitted the user is redirected to another page. In between the moment that the form is submitted and the user is actually redirected the submit button is suddenly enabled again. This is similar behavior as described in this old issue in rails-ujs https://github.com/rails/rails/pull/31441 (see GIFs in that issue). For an end user this might seem strange and it seems like a bug to me. Note, I am not using rails-ujs. In that pull request they fixed the issue by not enabling disabled elements for XHR redirects.
In https://github.com/hotwired/turbo/pull/386 a change was made for disabling/enabling submit buttons. This pull request states "If callers need to control the submitter's disabled attribute more finely, they can declare listeners to do so.". Since the button is enabled again in Turbo's FormSubmission.requestFinished method just before dispatching a TurboSubmitEndEvent, I can workaround this problem by re-disabling the button myself again by declaring a listener on turbo:submit-end:
document.addEventListener('turbo:submit-end', (event) => {
  if (event.detail.fetchResponse.response.redirected === true) {
    event.target.querySelectorAll('[type=submit]').forEach((button) => {
      button.disabled = true;
    });
  }
});

Although this seems to work, I think this should be fixed in Turbo.
Is it maybe an idea to change the requestFinished method in form_submission.ts to something like:
diff --git a/src/core/drive/form_submission.ts b/src/core/drive/form_submission.ts
--- a/src/core/drive/form_submission.ts	(revision 4dd0e83c2a695ecf5490c07da298cca867b2b1f8)
+++ b/src/core/drive/form_submission.ts	(date<PHONE_NUMBER>099)
@@ -201,7 +201,11 @@

   requestFinished(_request: FetchRequest) {
     this.state = FormSubmissionState.stopped
-    this.submitter?.removeAttribute("disabled")
+
+    if (!this.result?.fetchResponse?.redirected) {
+      this.submitter?.removeAttribute("disabled")
+    }
+
     dispatch<TurboSubmitEndEvent>("turbo:submit-end", {
       target: this.formElement,
       detail: { formSubmission: this, ...this.result },

If so, I could open a pull request to fix this.

I agree!
The disabled attribute being removed too early when redirecting presents a very confusing message to the user. The old UJS behaviour was easy to use and did what it should, but the new Turbo implementation seems to be lacking as it's not providing the same level of support.

Having this problem as well.  Seeing as how this is 2 years old with no PR or other progress, I'm going to submit one with your suggestion.


cmd/go: add *_unix.go recognition (and presumably unix build tag)

It does understand *_windows.go, and I was surprised to (re)learn that it does not support *_unix.go. Would it do so, things would be clearer and all the *_unix.go files that already exist wouldn't need to maintain their
// +build darwin dragonfly freebsd linux netbsd openbsd solaris

tags as the list grows.

More concretely, does this mean "unix" would mean anything in a pre-defined list of GOOS values? Would we proactively add unsupported GOOS values that might be supported later, like we did with GOARCH values, or would "unix" mean anything that's not windows or plan9 or nacl? Wait, is nacl unix?
Also, should we define "posix"? Currently we have some _posix.go files which include windows.
I don't object to this, but I'm just curious which definition we'd use.

All good questions for which I don't know the answer.
My main concern is maintaining the long list of os names in the build tags. Making things easier would be an advantage too.
Discussion needed.

I'd suggest the focus should be on user code and the standard library, and a new build tag is required (perhaps "unix"). The standard library has clear manifestations of a notion of "unix" in packages intended for general use (most obviously in net), and I'd suggest any GOOS that implements these should satisfy the build constraint word "unix."  For example, if nacl's net package supports network types "unix", "unixgram" and "unixpacket" it would satisfy some of the predicates the "unix" build constraint should require.
The *_unix.go convention could implicitly define +build unix.

That's pretty much what I mean.

Related: #6325

Looking at the list of OSes, the BSD's may be the most homogeneous and largest sublist. But do you count Solaris, Darwin? Even if not, just defining bsd as dragonfly freebsd netbsd openbsd seems handy regardless of any other tags that might be included. If Darwin and Solaris are included, the build tag in the OP shrinks down to // +build linux bsd
Looking at the feature sets, posix may be the simplest target, but which subset of posix? Is it just the shared subset of all the unix-like OSes currently supported? When a new posix-y OS is added does that mean it can't be added to posix if it's missing one thing the other posix OSes support or do the set of guaranteed features lose a member? Since posix is so vast and as far as I know in practice little agreed upon, that seems the most problematic.
Looking at the stdlib, there seems to be very little agreement in practice among which OSes to include, even in *_unix.go and *_posix.go files. Of course, that doesn't preclude having build tags like // +build unix,!freebsd when needed.
Looking to the future, if the list is not proactive, as Brad put it, that means a new OS could suddenly match with a new version of Go when it should not. That may be worrisome but then again currently we have the situation where a new GOOS doesn't match anything without manual intervention. Of course, even a future proofed list is only as good as targets currently known and can't contain as yet uninvented OSes, and then the same issues arise as with posix.

From a user code perspective it shouldn't matter if the "unix" is bsd, lunix, solaris or other. I'd consider mandating cgo for test purposes for "unix" candidates and having a cgo-centric test suite to make sure all the unix-type-things for a given Go toolchain aren't at odds with the C toolchain as known to the Go toolchain for a given GOOS.

This is basically a straight duplicate of #6325, as @dominikh points out. The problem here, as there, is that "unix" changes based on various details - sometimes it includes Linux, sometimes not, for example. It's not clear we want to be in the business of defining it exactly one way. Also, this should not affect users terribly much, given that we try to provide OS-independent APIs to the largest extent possible.

You're skirting the point here, which is just to avoid maintaining the huge list of Unix variants Go supports. It's to discriminate the basic difference between Windows and Unix. Windows has many versions, but there is only one predefined "windows" tag, in the sense the foo_windows.go works. I'm asking for the same courtesy for Unix.

Ignoring ios and android for the moment, as they're essentially defined to be "variants" of darwin and linux, and only looking at the GOOS build tags, the complete list, as of 1.8, is:
windows plan9 nacl linux solaris darwin dragonfly openbsd netbsd freebsd

The goal, as I understand it, is to be able to use *_GOOS.go as much as possible, by defining one or more "super-GOOS" tags that match a large subset of the above tags.
I'm going to ignore the implications of defining unix or posix and just look at what's in the stdlib so there's some data. (Apologies if I made any mistakes).
Looking at the *_posix.go files in the $GOROOT/src† the definition of posix uses seems to be almost equivalent to !plan9, with occasion to additionally specify !nacl (3/15 of the files) and once adding !solaris.
(Windows is not what most people think of when they thing posix. An alternative would be to allow something like x_not-T.go to be equivalent to a // +build !T directive and rename most of those as _not-plan9.go.)
† using
find -type f -name "*_posix.go" -exec grep "^// [+]build " {} \; | cut -d" " -f3- | sort

For the *_unix.go files,I took the list of tags, removed two that, despite the name, only had to do with cgo, took out all arches, android build tags, etc., manually expanded the negations, reordered them so all the tags were in the same order and then counted the occurrences of each unique subset of GOOSes:
18: darwin dragonfly freebsd linux nacl netbsd openbsd solaris
12: darwin dragonfly freebsd linux netbsd openbsd solaris
3: darwin dragonfly freebsd linux nacl netbsd openbsd plan9 solaris
2: darwin dragonfly freebsd linux netbsd openbsd
2: darwin dragonfly freebsd linux nacl netbsd openbsd solaris windows
1: dragonfly freebsd linux nacl netbsd openbsd solaris
1: dragonfly freebsd linux netbsd openbsd
1: dragonfly linux netbsd openbsd solaris
1: freebsd linux netbsd

Looking at that it seems !windows,!plan9 would get the most existing *_unix.go files, fit most people's expected definition, but often require an additional // +build !nacl directive.
In practice how build tags are written seems to be somewhat ad hoc. Maybe gofmt could sort them in a standard way or golint warn if they're not alphabetical? Perhaps a new tool that deals solely with build constraints?

Here's similar for every GOOS build tag :
https://gist.github.com/jimmyfrasche/24f45e37a35f02eab8dcd1fb2c1c6af2

It sounds like the real interesting use would be outside the standard library. Can someone survey what usages look like outside, like in the go corpus files?

Maybe the best expression of "unix" is !windows,!android,!plan9,!nacl as it's much easier to express why a GOOS is !unix and the build tag waters aren't muddied when user code has to pander to particular variants of things that aren't !unix.

On hold for someone to present evidence about the need for this outside the standard library.

Any code that needs to support variant operating systems would need this. For example, Upspin has
errors_unix.go:5:// +build darwin linux freebsd netbsd
Is that the right list? No. What is? I don't know. The code in that file is Unix-generic, but what is Unix from Go's point of view?
It seems to me that if we can define golang.org/x/sys/unix then we can define build tag unix and _unix.go.

There is a new GOOS value to take into account now: aix .
We have ported GCC Go on AIX 7 and we are working now on porting golang.
Nearly all changes dealing with AIX and GCC Go have been submitted and merged.
We are now working on golang.org/x and it appears that it contains a lot of OS cases. Moreover, colleagues who are porting Go applications on AIX are facing face many cases where they have to manage the OS (adding aix) though the code is far from the Operating System.
About golang.org/x, here are some recent (2018/05/30) data about how it depends on "linux", goos, and goarch  . That provides an idea about the amount of work required for adding a new operating system or a new architecture.
Number of times the expression:  '// +build ...linux...' appears in the sources of each package:
arch: 0
benchmarks: 3
blog: 0
build: 3
crypto: 8
exp: 14
image: 0
mobile: 34
net: 54
oauth2: 0
perf: 0
sync: 0
sys: 94
talks: 0
text: 0
tools: 8
vgo: 5
Number of times the key-word: 'linux' appears in the sources of each package:
arch: 1
benchmarks: 3
blog: 5
build: 488
crypto: 9
exp: 18
image: 0
mobile: 57
net: 153
oauth2: 0
perf: 12
sync: 0
sys: 283
talks: 15
text: 0
tools: 46
vgo: 70
Number of times the key-word: 'goos' appears in the sources of each package:
arch: 0
benchmarks: 1
blog: 1
build: 35
crypto: 0
exp: 0
image: 0
mobile: 19
net: 0
oauth2: 0
perf: 10
sync: 0
sys: 8
talks: 0
text: 0
tools: 6
vgo: 27
Number of times the key-word: 'goarch' appears in the sources of each package:
arch: 0
benchmarks: 1
blog: 0
build: 37
crypto: 0
exp: 0
image: 0
mobile: 8
net: 0
oauth2: 0
perf: 10
sync: 0
sys: 5
talks: 0
text: 0
tools: 6
vgo: 28

dang I thought this was going to be a proposal to port Go to run on the old PDP unix made at bell labs. :(
Also, I explored thinking about this awhile back but how hard would it be to port Go to run on top of a virtual OS layer like inferno?

On Jun 5 2017 I wrote:

On hold for someone to present evidence about the need for this outside the standard library.

Issue #38364 and #37503 may be evidence that the standard library is need enough, because it would make it easier to maintain Unix-like ports outside the main Go tree.
Perhaps it would be enough to define unix = all the Unixes and then systems that want to use a unix tag can filter with things like
// +build unix
// +build !linux

(There's a proposal to make these better. Still not ready to post that yet.)

There are some stats above, but they might be old. Does anyone want to investigate how much things might get cleaned up for code outside the main tree if we added "unix"?
For sake of discussion, unix would be all the operating systems traditionally recognized as Unix (aix, android, darwin, dragonfly, freebsd, hurd, illumos, linux, netbsd, openbsd, solaris; NOT js, nacl, plan9, windows, zos). It is of course ironic that GNU Hurd is unix by this definition.

go-locale is a lib for cross platform locale detection, we have to add build tags like following:
https://github.com/Xuanwo/go-locale/blob/master/locale_unix.go#L1

I did a search with the sourcegraph cli across repos outside the main tree for files that have the suffix _unix.go.
 Many exclude operating systems like hurd and aix. A few explicitly include non-unixes like js, nacl, plan9, and windows.

 If it's the former, it'd be interesting to know what fraction of them would be affected by the addition of a unix build tag.

@smasher164 the attached file has all the build tags. The list in my comment filters it to count the lines with only platforms.
Given the current list, I don't think any of the lines exactly matches all the unixes as listed by @rsc (android appears really unpopular), though the correctness of the build tag lines in the wild can be debated (as people may forget about the less common platforms).

Thanks for the data, @seankhliao and @smasher164. It does look like having unix would have avoided a lot of entropy in the current build lines. Given that possible reduction in entropy along with possibly simplifying Unix-like ports (as discussed in #37503), it sounds like we should probably adopt this proposal.
Quoting my previous message:

For sake of discussion, unix would be all the operating systems traditionally recognized as Unix (aix, android, darwin, dragonfly, freebsd, hurd, illumos, linux, netbsd, openbsd, solaris; NOT js, nacl, plan9, windows, zos). It is of course ironic that GNU Hurd is unix by this definition.

Does anyone want to argue against adopting this proposal?

Based on the discussion above, this seems like a likely accept.
(See previous comment for exact definition of "unix".)

Has this been implemented? If so, I haven't found any documentation about it. Adding an explicit //go:build unix to a file excludes it from the build on macOS, so it doesn't seem to be meaningful to Go.

@bitfield this proposal is accepted but still open, meaning it hasn't been implemented. It doesn't appear like anyone is actively working on it, so it's up for grabs if someone has the time to work it out :)

I took a look at the _unix.go files in the standard library.  There are several such files that have a //go:build line that matches non-Unix systems.  This is not a big deal, in that we can rename the files (I'm thinking of _unixy.go) and carry on.  But if the same pattern happens in packages outside the standard library, then changing the treatment of _unix.go files will break those packages.
It may be safer to define the unix build tag in go:build lines, but to not recognize it in file names.  There are of course other similar build tags, such as cgo or gc or go1.18.  That seems like a conservative approach to me.  Does anybody think that it would be a mistake?
Here are some examples from the standard library (this is not a complete list).  If we recognize _unix.go files as we do _GOOS.go files, each of these files (and more) will have to be renamed to make the build succeed.
time/sys_unix.go: //go:build aix || darwin || dragonfly || freebsd || (js && wasm) || linux || netbsd || openbsd || solaris
cmd/go/internal/base/signal_unix.go: //go:build aix || darwin || dragonfly || freebsd || js || linux || netbsd || openbsd || solaris
cmd/go/stop_unix_test.go: //go:build aix || darwin || dragonfly || freebsd || (js && wasm) || linux || netbsd || openbsd || solaris
crypto/rand/rand_unix.go://go:build aix || darwin || dragonfly || freebsd || linux || netbsd || openbsd || plan9 || solaris
path/filepath/path_unix.go: //go:build aix || darwin || dragonfly || freebsd || (js && wasm) || linux || netbsd || openbsd || solaris
golang.org/x/sys/unix/sockcmsg_unix.go: //go:build aix || darwin || dragonfly || freebsd || linux || netbsd || openbsd || solaris || zos
syscall/env_unix.go: //go:build aix || darwin || dragonfly || freebsd || (js && wasm) || linux || netbsd || openbsd || solaris || plan9
net/error_unix.go: //go:build aix || darwin || dragonfly || freebsd || js || linux || netbsd || openbsd || solaris
os/exec/exec_unix.go: //go:build !plan9 && !windows
os/signal/signal_unix.go: //go:build aix || darwin || dragonfly || freebsd || (js && wasm) || linux || netbsd || openbsd || solaris || windows

The CL https://go.dev/cl/389934 implements "unix" as a build tag, but only in go:build lines, not in file names.
The CL https://go.dev/cl/389935 shows how the standard library can take advantage of the new build tag.


Adding links to relevant docs in comments

What would you think about adding links to relevant documentation/issues from various projects to explain each part of the application? For example, folks familiar with the simpler configuration of react-router might initially be confused if they don't understand the more advanced configuration, why it's useful, and how to use it.

I plan to write extensive documentation in case this project reaches a state that's worth it, briefly introducing each interesting dependency and linking to documentation of other projects.
Your suggestion sounds like a great additional resource for newcomers. Right now it probably isn't worth it yet as the project is still in the experimentation phase and a lot is changing.

Got it. Thanks for the prompt response! I'll close this for now.


feat(button): add active styles

Description
Added Active button styles pseudo-class.
Ticket: https://dialpad.atlassian.net/browse/DT-308?atlOrigin=eyJpIjoiZmY1NDQ3MDZjYjAyNGZhZTliYzFkMzJlNjM5NDkyMzEiLCJwIjoiaiJ9
Figma File: https://www.figma.com/file/zP2uyVxAg4notGNZwW64mW/branch/XnnI2V4nrwhZWmxRM70sMm/Components?node-id=2055%3A4256
Pull Request Checklist

[x] Ask the contributors if a similar effort is already in process or has been solved.
[x] Review the contribution guidelines.
[x] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[x] Ensure all gulp scripts successfully compile.
[ ] Update, remove, or extend all affected documentation.
[ ] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).
[x] Request a review from Brad Paugh, David Becher, or Drew Chandler.

Obligatory GIF (super important!)

We need to update documentation for this right?

Where should I add the documentation? I haven't found any documentation on :active button styling either in Dialtone 5 or 6

We need to update documentation for this right?

Where should I add the documentation? I haven't found any documentation on :active button styling either in Dialtone 5 or 6

Yeah I guess we don't need to, it's completely internal to the button, for example we don't say anything about hover button styles either.

We need to update documentation for this right?

Where should I add the documentation? I haven't found any documentation on :active button styling either in Dialtone 5 or 6

Yeah I guess we don't need to, it's completely internal to the button, for example we don't say anything about hover button styles either.

Yeah, that's what I was thinking too.
I just realized I need to add and .d-btn--active class so we can retain the active state in dialtone-vue, I'll create a new PR for that changes.


Candle Type Indicators

Is there a way to draw candle indicators?

#202

Sorry, I meant if we can draw candle bars in the indicator pane like in the attached image.

This is just an example, to show you that you can customize any shape you want.


No English on website

Without English it's hard to use the icons on my own site. So, add English.

you can switch language in the bottom left corner


Add online phone providers

Could you add a small description about why these services are useful? I think this could help many people who may don't know hwat this is for

Thanks!


Run command with Maven properties

Hi,
I have tried to run some commands before deploying an application during the wildfly:run goal with some Maven properties in order to add for instance a data source
<beforeDeployment>
        <commands>
            <batch>false</batch>
            <command>
                data-source add --jndi-name=${hibernate.datasource.jndi.name} ...
            </command>
        </commands>
    </beforeDeployment>

but the maven properties are not filtered so the command fails. I have seen you can use a property file when you run the ``jboss-cli.bat` but I do not know how to specify it and moreover I would like to use some Maven default properties coming from the IDE configuration (I use Idea and I can specify properties in the Maven Runner settings).
Is there a way to do? is it an enhancement of the plugin?
Thanks a lot for your time.

The problem is using properties like that is a valid value for some attributes. Knowing when to resolve the property in maven vs send the expression to with the command would be a best guess.

+1 for this.
Could eg. escaping be used to mark when resolving should (not) be done by maven or with some additional cfg like below to remain backwards compatible?
<expandPropertiesAnchor>#<expandPropertiesAnchor>
<command>
    data-source add --jndi-name=#{hibernate.datasource.jndi.name} ...
</command>

Why not using a script instead of commands and have maven filter the script file with default maven resource filtering?
http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html

Have to try that one!

I prefer the script + resource filtering approach @sventorben suggests. I think adding a a separate syntax could be confusing.
I'm closing this issue as I think the script + resource filtering is a sufficient workaround.


modified LANL2DZ

Please can you add the modified LANL2DZ basis sets (uses standard LANL2DZ ECP) to the repository? "Basis Sets for Transition Metals: Optimized Outer p Functions," Marc Couty and Michael B. Hall, J. Comput. Chem., 1996, 17, 1359-1370. I have the file, or you get it from the old EMSL Basis Set Exchange website. Thanks!

Sounds reasonable. I have all the old data.
Is the data that you have the same as in the old BSE, or from another source? If it's from another source, I would like to compare.

I am the one who uploaded the old data on the old BSE, so it is the same
data.
You can compare to here:
http://dev.chem.tamu.edu/rgroup/hall/laboratories/Couty-Hall_Basis_Sets.html
Thanks!
Edwin
On Wed, Apr 3, 2019 at 1:16 PM Benjamin Pritchard<EMAIL_ADDRESS>wrote:

Sounds reasonable. I have all the old data.
Is the data that you have the same as in the old BSE, or from another
source? If it's from another source, I would like to compare.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MolSSI-BSE/basis_set_exchange/issues/53#issuecomment-479601690,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Au943Oc77MuJH5WxkOsFYWd8qNDFq340ks5vdO_xgaJpZM4cbE89
.

Added to the library in 35fc7c5.  I will leave this open until it is live on the website

This should be live on the website now.
I just realized that the notes were not moved over. I will move them over today and they will be on the website at the next update.
Thanks


Setting up Flox with SQLite

I try to deploy flox on my Raspberry Pi with sqlite.
However, the database doesn't get filled, the db file stays empty even though the "php artisan flox:db" command outputs "MIGRATION COMPLETED".
I followed the instructions on https://laravel.com/docs/6.x/database and those on this site.
The webserver is Apache2 on a debian based linux (OSMC).
This is my .env:
TMDB_API_KEY=apikey
TRANSLATION=DE

CLIENT_URI=/flox/public
LOADING_ITEMS=30

# Default 10 minutes (600 seconds)
PHP_TIME_LIMIT=600

# Set your correct timezone
TIMEZONE=UTC

# Date pattern for reminder mails
DATE_FORMAT_PATTERN=d.m.Y

DAILY_REMINDER_TIME=10:00
WEEKLY_REMINDER_TIME=20:00

DB_CONNECTION=sqlite
DB_HOST=
DB_PORT=
DB_DATABASE=/var/www/html/flox/backend/database/database.sqlite
DB_USERNAME=
DB_PASSWORD=

APP_URL=http://osmc
APP_ENV=local
APP_KEY=appkey
APP_DEBUG=true

APP_LOG=daily
QUEUE_DRIVER=database

REDIS_HOST=<IP_ADDRESS>
REDIS_PASSWORD=null
REDIS_PORT=6379

MAIL_DRIVER=smtp
MAIL_HOST=smtp.mailtrap.io
MAIL_PORT=2525
MAIL_USERNAME=null
MAIL_PASSWORD=null
MAIL_ENCRYPTION=null

Thank you for any input in advance!

Many thanks for the report :)
The problem was, that DB_DATABASE in the env had no impact to the sqlite config. I fixed it!

Great, thank you very much for sharing this project and fixing the bug! :)


Fix build warnings and style

Fix style - primarily indentation
Fix warnings - missing header in umbrella and outError in doc comments

cc: @mortenbekditlevsen


Added django-model-field-meta

In one of my Django projects, we needed to supply extra information about our model fields. For the purpose, help_text is too limited. Using code comments is not feasible as I need to use those information programatically. Hence, django_model_field_meta package is created.

Hi @melvinkcx , This package looks really cool. I'm going to wait until it has a little more usage before adding to the list. But I see the need. Well done :) -Will


Extends RakugoVars types

Now RakugoVars are can have any type as value, but it makes harder to use arrays and dictionaries.
We need to add:

RakugoDict
RakugoList
RakugoString
RakugoBool

Is done in resource-save branch

Now I think I need make them all base on Dictionary and update Rakugo nodes and text passer to this changes

I can't make them to base on Dictionary, but I update them to last changes.


Translation Error

Hi,
I'm having an error while compiling locale with `compilemessages.
I'm using Django 5, the error is the following:
Execution of msgfmt failed: /app/.venv/lib/python3.11/site-packages/allauth_ui/locale/fr/LC_MESSAGES/django.po:226: 'msgstr' is not a valid Python format string, unlike 'msgid'. Reason: In the directive number 1, the character 'p' is not a valid conversion specifier.
msgfmt: found 1 fatal error

What commands did you run? What is the git diff?

I used python manage.py compilemessages.
python 3.11
Django 5
the git diff between the file and the latest in your repository shows no difference

I think the problem is %(provider_name) at line 228 that misses the s character at the end: https://github.com/danihodovic/django-allauth-ui/blob/master/allauth_ui/locale/fr/LC_MESSAGES/django.po#L228C51-L228C66

I opened a PR for this, it could be related to this issue in django rosetta: https://github.com/mbi/django-rosetta/issues/128

Hi,
I have a new compilemessages error for the language pt.
allauth_ui/locale/pt_BR/LC_MESSAGES/django.po:126: a format specification for argument 'passwd_reset_url' doesn't exist in 'msgstr'
#16 1.547 /app/.venv/lib/python3.11/site-packages/allauth_ui/locale/pt_BR/LC_MESSAGES/django.po:229: 'msgid' and 'msgstr' entries do not both end with '\n'

I think it would be helpful to add a CI task that verifies that the translations can be compiled, to avoid having them committed in the source code


Replace Whoosh with a faster and more scalable full-text engine

An initial testing is required:

http://lucene.apache.org/solr/ !!!
http://www.elasticsearch.org/ !
http://sphinxsearch.com/
http://xapian.org/
...?

Maybe I exaggerated a little, when said performance test - since I havent tried to run the original epsg.io site and dont have anything to compare with.
I just took the gml_parser from the latest release and modified it(python not being my main language).
My modifications are here, https://gist.github.com/s093294/6cd8909439b28295b6e3 and the purpose was just to get a fast way to make users able to search for a projection in a form we was doing and needed a little more control that using epsg.io directly.
you can get a free test service, but you will need an microsoft azure subscription. Let me know if you need more info on that. Docs to azure search: http://azure.microsoft.com/en-us/documentation/articles/search-api-2014-10-20-preview/
Azure Search target a response time of 250-300 ms on queries and has options to scale very easily if demands raises. I would be happy to help set it up for epsg.io, but since you already have a working solution - i dont think theres much to gain.


Automatic error report

<!---   *** BEFORE SUBMITTING: PASTE CLIPBOARD HERE TO COMPLETE YOUR REPORT ***   ---!>
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Closing as a duplicate of issue #20984.


Fix #106: Handle reflection classes more dynamically

Fix #106: Handle reflection classes more dynamically
Uses Jandex to collect subclasses rather than list each class individually. Also future proofs it for new Lucene classes.

cc @dainiusjocas

@all-contributors add @melloware for docs and code


Error E0425 while trying to cargo run on FreeBSD machine

Bug Description
When trying to run command cargo run, the compilation is terminated because of error[E0425]: cannot find function 'size_of' in this scope error. I am running an Actix server on FreeBSD version 14.1-RELEASE-p3.
Details
While using cargo run on my development machine (Manjaro Linux 24.0.7) works as intended, I get the below error while running it on the server (FreeBSD version 14.1-RELEASE-p3):
error[E0425]: cannot find function `size_of` in this scope
   --> /home/deaponn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/sqlx-postgres-0.8.1/src/types/cube.rs:307:33
    |
307 |     const PACKED_WIDTH: usize = size_of::<u32>();
    |                                 ^^^^^^^ not found in this scope
    |
help: consider importing one of these items
    |
1   + use core::mem::size_of;
    |
1   + use std::mem::size_of;
    |

For more information about this error, try `rustc --explain E0425`.
error: could not compile `sqlx-postgres` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...

My workflow is as follows:

Make some changes in my git repo, tested with localhost postgres database
If everything works I push the changes
Connect to the server via SSH and pull the changes
Run the server there with cargo run to confirm everything works fine

The only difference between development machine and the server is the .env file, but its content is read only after compilation.
Minimal Reproduction
Remember to do it on FreeBSD machine

git clone https://github.com/Deaponn/rybocheck.git
cd rybocheck/backend
mv example.env .env (shouldn't be an issue, but for completeness sake)
cargo run

Info

SQLx version: 0.8 (in the error message it says something about sqlx-postgres-0.8.1 though)
SQLx features enabled: "runtime-tokio", "postgres"
Database server and version: PostgreSQL 16.3
Operating system: FreeBSD version 14.1-RELEASE-p3
rustc --version: rustc 1.78.0 (9b00956e5 2024-04-29) (built from a source tarball)
Full output of SELECT version(); on development machine: PostgreSQL 16.3 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 14.1.1 20240720, 64-bit
Full output of SELECT version(); on the server: PostgreSQL 16.3 on amd64-portbld-freebsd14.1, compiled by clang version 15.0.7, 64-bit

@Deaponn the issue has been resolved 17 hours ago
See the following issue for further context:

https://github.com/launchbadge/sqlx/issues/3461


build swiftdriver for lldb pull requests

The old Swift Driver is basically EoL.

@swift-ci please smoke test


Question

Hi,
Do you have any plan to update the pipeline so that can be used for the new Nanopore RNA flow cells, as guppy Basecaller doesn't have any cfg file that can support the new flow cells. Instead Nanopore recommends to use Dorado.
I saw that f5c now supports RNA004 eventalign.
Thank you,
Nick

That is a good advise!
I will check the latest version of Dorado to see whether it can use in FdR.
Thanks!


Disable check-deps ci step

Summary
A new owasp dep check release is not distributed yet through bintray causing a required ci test to fail.
Ticket Link
N/A
Related Pull Requests
https://github.com/mattermost/mattermost-server/pull/17083

Skipping 3: QA Review since CI/CD only.

/cherry-pick cloud

Cherry pick is scheduled.

@amyblais This need to be cherry picked into cloud

/cherry-pick release-5.31

Cherry pick is scheduled.

Error trying doing the automated Cherry picking. Please do this manually
+++ Updating remotes...
Fetching upstream
Failed to add the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts (/app/.ssh/known_hosts).
From github.com:mattermost/mattermost-webapp
   6e21569e0..b1302f040  cloud        -> upstream/cloud
   3beab88d5..a4275231e  release-5.31 -> upstream/release-5.31
   7bbbc739a..983c1a8b2  release-5.33 -> upstream/release-5.33
Fetching origin
Failed to add the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts (/app/.ssh/known_hosts).
+++ Updating remotes done...
+++ Creating local branch automated-cherry-pick-of-mattermost-webapp-#7657-upstream-release-5.31-1616431650
Switched to a new branch 'automated-cherry-pick-of-mattermost-webapp-#7657-upstream-release-5.31-1616431650'
Branch 'automated-cherry-pick-of-mattermost-webapp-#7657-upstream-release-5.31-1616431650' set up to track remote branch 'release-5.31' from 'upstream'.

+++ About to attempt cherry pick of PR #7657 with merge commit<PHONE_NUMBER>da480d48f4d72440d52f994d853f34.

The previous cherry-pick is now empty, possibly due to conflict resolution.


document M1 Mac temporary patch

What was changed
document M1 Mac temporary patch
Why?
a lot of people failing to use us and not aware there is a simple fix

sorry about that but exec format error is not the same error i had - you may be seeing a different problem.

for those finding this in future, the M1 / ARM build was fixed in 1.14.2 #60


Index by address

Trying to go piece-meal with my membership speed-ups. Quick fix to index members by their address for faster access:
Running 2 benchmark(s) for benchmarks/find-member-by-address.js
606d65c Benchmark for finding member by address 73,264 ops/sec
3731aff Index members by address 26,864,034 ops/sec
Benchmark complete!

@markyen @Raynos

lgtm.


Roll engine 56bad48ab2ed..be9d8ffbb8ed (4 commits)

https://github.com/flutter/engine/compare/56bad48ab2ed...be9d8ffbb8ed
git log 56bad48ab2ed..be9d8ffbb8ed --no-merges --oneline
be9d8ffbb Roll src/third_party/skia 5f0726b01019..33f34556b5fc (1 commits) (flutter/engine#6107)
f3ff83a5d [dart roll] Roll dart to 3e0631761c84d9fb86c237cc57dca7b878f5800f. (flutter/engine#6105)
56139397e Roll src/third_party/skia 7ba1d64f0706..5f0726b01019 (12 commits) (flutter/engine#6104)
47a1ce0e6 Allow embedders to set the root surface transformation. (flutter/engine#6085)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

@rmistry @liyuqian : New roll has been created by https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/5670554107379712 , https://cirrus-ci.com/task/5107604153958400 , https://cirrus-ci.com/task/5002051037691904

PullRequest is not longer mergeable. Closing it.

Commit queue failed; closing this roll.

PullRequest is not longer mergeable. Closing it.


Fix #63: Change all messages to extend RequestResponseProtocol

Fixes #63
Proposed Changes

Change all messages to extend RequestResponseProtocol

Related
n/a

there are still some errors introduces by the merge I guess

Yeah, sorry. Just fixed it. It was a time package mess up.


Make -http-directory work with -dynamic-response

Please describe your feature request:
Would it be possible (or a good idea?) to make http-directory files work with -dynamic-response headers/status. example:
request ==> oast.fun/s/evil-image.png?header=content-type:image/svg%2Bxml&status=500
Describe the use case of this feature:

Sometimes when the body of the response is big i can't use dynamic response normally and include it in the url
Having to write response then url encoding it then copying it to the url is annoying

I forked the repo and made a change for this changes to work. But I am not sure if it's the best approach. you can check the changes here

@ounissi-zakaria, Thanks for taking the initiative to open up this issue and your efforts to make it happen! Could you please raise a PR and let us review it?


[stable/jaeger-operator] Update image

What this PR does / why we need it:
Updates img to 1.10.0
Special notes for your reviewer:
cc @cpanato
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

cc @cpanato

bump

/lgtm


Transfer an ms100 from one Hub to another cause duplicate sensors

Dear all, I tranferred an MS100 sensor (humidity and temperature) from an Hub to Another.
The new sensor is added in the new Hub, but it is not deleted from the old one.
So I got duplicated entities names.....
Latest version of Meross LAN is installed, Windows docker with HA 2021.11.5
deleted a MS100 sensor (temperature and humidity) from an Hub (using the Meross app), and I associate the same sensor to another Hub.
When I go in Home Assistant I see the sensor in both the Hub configuration.
Seems that the sensor is not deleted (or refreshed) so I can see it in both my Hub configuration.
To explain better I attached two pictures:

-->
Could be that I am wrong, somebody has faced (and solved) the same problem ?
Thanks a lot
cheers
Roberto

Hello @robertolamm ,
This is expected since in meross_lan entities are 'uniquelly' binded to the root device so when you move a 'subdevice' like an ms100 to another hub, even though the hw device is the same, meross_lan identifies its child entities as new under the other hub.
The old entity entries too are not automatically deleted because I didn't figure out a stable mechanism to intercept the unbind from the old one so, my impression is that a missing device from one hub could be an offline one.
This later assumption is not really sure on my side: I'll try to check if it's possible to detect this kind of event but for the time, being this what I guess an 'edge' case you're left with manual deletion of the old entities (HA should allow this but I'm not sure for this case since I've never had a chance to try it)
Also, I've never seen any integration able to automatically delete 'stale' entities and, from my knowledge, this is also an HA core design choice since these 'stale' entities could have some data in the recorder and the user must be aware and make a 'responsible choice' about deleting these.

Hello @krahabb,
I tried to delete the entities from the HA section but unfortunately it's not possible: when I select the entity and push "delete" HA says me that these entities are controlled by an integration so is not possible to perform the action.
I think would be great, if possible, add the function to delete them manually from the integration itself.
Thanks a lot!

Yeah..that must be manually possible so I'll definitely check why it still thinks they're on the old hub too. Did you already restarted HA? sometimes it need to reconfigure the integration to detach the 'stale' entities. You could just reload the old hub integration without the full HA restart (I guess so)

Yes, I tried to restart HA and also to restart the Integration.
I can try to delete the integration and reinstall it, but only thinking to this option make me cry, because I renamed all the entities (15 x 3 sensors) and I have a lot of automation and related sensors in my configuration :)
I am pretty sure that after the reinstall, I will obtain the "original" names :)

Yeah..wait a bit:)
you can try disable them if not done yet..I'm checking a bit more on this
I'm sometimes struggling too to delete 'vanished' entities (and I'm not sure this is only related to meross_lan but I don't want to be too selfish here)
I remember I have to explicitly disable them form UI and then after some 'restarts' I can finally delete them. Maybe this is only happening on meross_lan so I'm trying to get more serious at it ;)
In order to be sure the old hub is not still publishing those lost entities (which could happen since I've never seen an unbind procedure for hub attached devices) I would need a trace from both in order to check if these entities still appear twice because both the hubs are publishing them

Ok, I am available for any thing you need. Only let me know how (if) I can be helpful.
Thx

Yeah thank you :)
Just go to the integration configuration panel for both of the hubs and enable the 'tracing' checkbox.
You will find the captured files (1 for each device trace) under 'custom_components/meross_lan/traces'
meross_lan will collect data for 10 minutes so, after this time, upload those files to this thread so I can check them

Hello,
these are the two files.
I only checked on for the 2 integrations the checkbox, I reloaded the Integration w/out restart HA.
I hope it is enough, be free to ask me for other tasks.
msh300-1638020203.csv
msh300-1638020212.csv

Thank you,
will look at it for sure.

Hello @robertolamm ,
I guess I've found the issue in code preventing the removal of stale entities (either manually or not: at the time meross_lan still thinks they're in place)
The only two options are:

remove the whole hub entry and re-setup again (very annoying like you said)
wait for a patch I'm working on: in the meantime just disable the stale entities

Hi @krahabb
thank you so much.
I will wait for your patch since I am not stopped :) , in the meantime I will to install the new release (I seen there is a new one available from yesterday).
Cheers from Milan :)

Hello @krahabb,
I installed the new version and restarted HA.
I have manually deleted the orphan entities with the button "delete", but the removed devices are visible again in the integration. So the problem seems to be partially solved.
I attached some pictures, in who we have one ms100 sensor removed from the app, and not installed in every hub (named free).

Thanks alot
Roberto

Hello Roberto,
Yes I was aware of this since deleting a device entity is not easily achieved (the UI too does not allow to delete an orphan device so you're likely left with manually editing the HA core files under '.storage')
I didn't investigate this too much anyway, since I thought the device (ms100) should have been 'grabbed' (HA internal configuration-wise) from the new hub on which it is now binded and so I thought your case would have been resolved this way.
I can't promise anything now since it is a bit hard to test but I'll try to give some 'care' to this issue since I don't really like 'unclean' behaviours in code

Hello @krahabb
naturally this is not a problem because I can use the devices correctly.
I've seen also the .storage directory but this is too much complex to edit for my HA skills :)
I duplicated the file, edited  as I understood but the HA was freezed at the restart. I restored the old file and is came back to be ok. So I am scared to edit manually anymore the files 😵
Could be possible to let the user to manually delete the orphan devices in the GUI ? Or maybe is too much difficult to realize ?
However thanks a lot for your effort :)
Keep in touch.
Roberto


NIO's EBADF blacklisting maybe is a bit too much

Expected behavior
the following program should not crash
import NIO

let handle: FileHandle
//let fd = open("/tmp/foo", O_RDWR | O_TRUNC | O_CREAT) // Attention: this will truncate the file if it already exists
//if fd >= 0 {
//    handle = FileHandle(descriptor: fd)
//} else {
//    fatalError("boo")
//}

let ioThreadPool = BlockingIOThreadPool(numberOfThreads: 1)
ioThreadPool.start()
defer {
    try! ioThreadPool.syncShutdownGracefully()
}
let group = MultiThreadedEventLoopGroup(numberOfThreads: 1)
defer {
    try! group.syncShutdownGracefully()
}
let io = NonBlockingFileIO(threadPool: ioThreadPool)
handle = try FileHandle(path: "/tmp/foo")
var buffer = ByteBufferAllocator().buffer(capacity: 100)
buffer.write(bytes: "asdfadsfadsfads".utf8)

try io.write(fileHandle: handle, buffer: buffer, eventLoop: group.next()).map {
    try? handle.close()
}.wait()

Actual behavior
it crashes with Assertion failed: blacklisted errno 9 Bad file descriptor in write(descriptor:pointer:size:)) because FileHandle(path:) opens the fd read-only.
Steps to reproduce
run the above program
If possible, minimal yet complete reproducer code (or URL to code)
NIO master 13th Dec 2018

ok, problem is obviously that we can't race-free check if that was a socket or not because EBADF usually means that the fd doesn't exist... Given that we only do this in debug mode, maybe this is okay?

Why not expose an alternative syscall wrapper that doesn’t do the EBADF policing for this use-case?

Good idea, yeah!

On 13 Dec 2018, at 9:37 pm, Cory Benfield<EMAIL_ADDRESS>wrote:
Why not expose an alternative syscall wrapper that doesn’t do the EBADF policing for this use-case?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok, so here's a question: do we actually want this issue?
I wrote up a fix for this, but while I was running the tests I realised that this blacklisting only blows up in debug mode. Release mode programs have their assertions compiled out, which means that in release mode this will simply throw IOError. I think it's defensible to argue that EBADF should trigger crashes in debug mode, as it will make those errors obvious to developers before their programs hit production.
What do you think? If you disagree I can still bring the patch up.

@Lukasa I think I agree with you.

Ok, let's not do this then.

Note that #1156 changes this behavior. EBADF has been promoted from an assertion to a precondition, and will crash in release mode.

I kinda think the current behaviour is fine, tbh

My use case is using SwiftNIO to make an SFTP server, where the client makes open(), read(), write(), and close()-like calls individually. I think it would be nicer if when the client opened a file descriptor that was a directory, and tried writing to it thinking it was a file, to get an error response back instead of the server crashing and losing the connection.
However, the simple fix for this is to call fstat() on the opened file descriptor before potentially reading from or writing to a directory.
I think the reason for the precondition is because the EBADF is supposedly non-recoverable. I'm not entirely sure why this is the case, but I can see why this might be favored in a library that's meant more for sockets than for file/directory handling. It will mean that anyone expecting to handle EBADF as an IOError will need to guard their code more, else they received unexpected crashes.

Yeah, the EBADF protection was present for the internal use-case of SwiftNIO, which is fairly forceful about the FDs it owns being correct. The interaction with FileHandle is a bit rough though. As you say, in the short term this can be worked around with fstat, but we should have a think about whether the right choice is to make NIO's FileHandle run through a different code path or whether we should be pushing this use case towards Swift System.


Short solution needed: "LIMIT OFFSET query example with PHP PDO" (php-pdo)

Please help us write most modern and shortest code solution for this issue:
LIMIT OFFSET query example with PHP PDO (technology: php-pdo)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

LIMIT OFFSET query example with PHP PDO


old trained model

See that the trained model you publish here is from the old code base

Don't we have the pre-trained model for FADNet++ yet?


Mentions not working

Client version: 0.1.68
Beaker version: 0.7.7
URL to reproduce: dat://beddfd47e26d685d075410d16ed68fecbad686b837005f5dc8082fa9bae78cff/#mentions
my Rotonde portal says I have three mentions, but when I click on that tab I get nothing:

there are no exceptions in the console, but there are a few "connection failed" messages:

rotonde is amazing btw. i love the minimalist aesthetic
@neauoire

yeah I've noticed it broke again… I'm on it!

I've noticed that we're counting the mentions separately from all other entries... and that the "Entries" tab number counts "invisible" entries, too.
In feed.js, we could update the for(id in sorted_entries){ to count all visible entries (f.e. c_all or short, ca) and make the "Entries" tab use that instead. Something similar could be applied for mentions to only count "visible" mentions. This would mean that right now, something's either wrong with the mention filtering, or with how mentions are counted.
(By the way, I'm supporting your comment. Rotonde really is amazing!)

for(id in sorted_entries){ is stopping after 40 entries though: if(c > 40){ break; }

I rather meant the following check with "visible" / "invisible" entries, should've been clearer 😅: if(!entry.is_visible(r.home.feed.filter,r.home.feed.target)){ continue; }
Haven't taken a deep look yet, just wondering if a difference between the mention counter and is_visible could cause the mismatch.


If network dto data class property's datatype is String and if number is given in sheet cell, then getting JsonDecodingException with kotlinx-serialization library.

@Venkat-juju Could you share your sheet? If not possible, a tiny repro ?


Simpilfy dns filter fuzz tests

Signed-off-by: Boteng Yao<EMAIL_ADDRESS>

In this PR, #20744 the answer message is disabled.
Remove separate fuzzing of the parseDnsQueryRecord as it is tested as part of the parseDnsObject method.
Remove fuzz_function randomization and only test the parseDnsObject method as it is used in the filter implementation.


Support exporting cut values

Deviating from the rest of the API functions, the value is returned as a json array interface. The choice is optional, but I want to start the discussion of this choice as we will return more complicated arrays in the future including CUDA arrays.

Add functions to export cut values in C and Python.
Move ellpackpage into src for accessing HistogramCuts.
Tests.

Downstream projects can use the information to compress the tree model if needed.

No. I'm looking into enabling inference libraries to use the quantization result to compress the model.

@hcho3 Please note that this doesn't work with approx, which changes cut value for each iteration

One will have to get the value for every iteration. Currently, this has to be done through some hacks.

For now, Treelite can continue to scan the thresholds manually to compute the smallest integer width that will fit all thresholds.


resolved some incorrect comments

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind cleanup
What does does this PR do / why we need it:
see $SUBJECT
Which issue(s) this PR fixes:
No issue
How to test changes / Special notes to the reviewer:
tests should pass - there is no code change in the PR, just code comments changed.

/lgtm

/retest

/retest

https://mirror.shastacoe.net/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel
http://mirror.siena.edu/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel
https://mirror.chpc.utah.edu/pub/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel
error: build error: running 'yum -y install make wget gcc git httpd-tools' failed with exit code 1
2020/07/06 20:36:41 Create release image registry.svc.ci.openshift.org/ci-op-nvpibykh/release:latest
2020/07/06 20:37:42 Copied 2.58MB of artifacts from release-latest to /logs/artifacts/release-latest
2020/07/06 20:37:42 No custom metadata found and prow metadata already exists. Not updating the metadata.
2020/07/06 20:37:43 Ran for 1m10s
error: some steps failed:
  * could not run steps: step root failed: could not wait for build: the build root failed with reason DockerBuildFailed: Docker build strategy has failed.
http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata...xml: [Errno -1] repomd.xml does not match metalink for epel
https://mirror.shastacoe.net/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel

prow failure
/retest

/approve


(Pillow Error)  AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'

def __init__(self, image_path: str) -> None:
        self.image_path = image_path
        self.image = Image.open(self.image_path)
        self.dominant_color: str = ""
        self.r: int = 0
        self.g: int = 0
        self.b: int = 0
        self.l: int = 0
        self.resized_image = self.image.resize(
            **(DominantColor.resize_value, DominantColor.resize_value), Image.ANTIALIAS**
        ).convert("RGBA")
        self.image.close()
        self.image_data = self.resized_image.getdata()
        self.generate_dominant_color_of_pixels_of_image_array()
        self.resized_image.close()

I get the same error, copilot sys:
[The error message you’re encountering indicates that the attribute 'ANTIALIAS' is no longer available in Pillow (PIL) starting from version 10.0.0. Instead, you should use 'LANCZOS' for antialiasing when resizing images.

I have fixed this in my fork of this package called "imagedominantcolour":
https://github.com/Demmenie/imagedominantcolour
https://pypi.org/project/imagedominantcolour/


Updating CreateConversation UI CSharp

Executed build pipeline
https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/4828419637


“split tab” or “duplicate tab” in ssh session

          If you are seeing the text "Could not access starting directory," do not set the `startingDirectory` in your SSH profile.

Originally posted by @DHowett in https://github.com/MicrosoftDocs/terminal/issues/25#issuecomment-2532839405
This is my “settings.json” and without “startingDirectory” and when I duplicate tab I do “split tab” or “duplicate tab” I still have the same problem.
    "list":
    [
        {
            "commandline": "ssh -t<EMAIL_ADDRESS>            "guid": "{d8fb0bf4-0044-406e-b034-6d3b91938a9b}",
            "icon": "ms-appx:///ProfileIcons/{9acb9455-ca41-5af7-950f-6bca1bc9722f}.png",
            "name": "UbuntuJP",
            "tabTitle": "Ubuntu1"
        },

the problem is:
[error<PHONE_NUMBER> (0x8007010b) when launching `ssh -t user@ip_server']
Could not access starting directory "/home/user"

I am facing an issue with Windows Terminal when duplicating or splitting a tab in an SSH session. The error I get is:
[error<PHONE_NUMBER> (0x8007010b) when launching ssh -t user@ip_server']
Could not access starting directory "/home/user"`
Problem Overview:

When I open a new SSH session in Windows Terminal and connect to a Linux machine (through SSH), everything works fine. However, when I duplicate or split the tab, the error above appears.
The problem seems related to the handling of the "startingDirectory" in the duplicated or split tab. It appears that the terminal is attempting to access the directory locally, even though it should be accessing the remote server’s directory.

Current Configuration:

commandline: ssh -t user@ip_server
startingDirectory: Either omitted or set to an empty string

The error occurs only when performing the tab duplication or splitting. When I first open a tab with the command above, the session works as expected. The issue arises only after duplicating or splitting the tab.
Additional Information:

Modifying the startingDirectory in different ways (including setting it to empty, or leaving it out altogether).
Various configurations in the SSH command line options (RemoteCommand, etc.), but the issue persists.

I would appreciate any guidance or resolution to this issue.

Oh, I get it now. Sorry I redirected you away from the original issue. We'll have to spend some engineering time looking into this!


JsonDiff

I know this was discussed in #281, but referenced within that ticket was this code: https://github.com/agourlay/cornichon/blob/c2e0974ac2a27dc973e0a3ffdc8520ea55b6effe/src/main/scala/com/github/agourlay/cornichon/json/JsonDiff.scala
I know for more advanced functionality diffson is a very useful tool, but for basic diff'ing it is overkill and adds needless complexity.  As shown in the above code basic diff'ing can be accomplished with a fairly minimal amount of Circe code.  I'd like to propose the above be introduced as a very light-weight solution for anyone wanting basic diff support in Circe without the requirement of a third-party library.
It could be incorporated as-is (which I've done in my own project with minimal modifications) or the basic concepts could be introduced in a more Circe-esque way.

Use diffson for this


LCM Defragmentation Support

Hello again!
This patch includes support for defragmentation of LCM packages, as specified in the LCM protocol description (https://lcm-proj.github.io/udp_multicast_protocol.html).
As my PR before, this patch is intended to be used in combination with an open PR (https://github.com/lcm-proj/lcm/pull/220) towards the GitHub LCM repository that adds golang + gopacket support.
As you can see, I put the defragmenter into a package called defrag. My suggestion is that the IPv4 defragmenter is also moved there as well and is renamed to ipv4defrag.go (and ipv4defrag_test.go respectively). IMHO this would be a bit more cleaner in case new defragmenters should come in. If you agree, I would open another PR for that.
Thanks for your openness towards new protocols :+1:  :sunglasses:

Hello @gconnell!
I just wanted to kindly ask, if we somehow can get this in? :) Right now, we are using this already in production and it works fine :) But obviously, we do not want to have the dependency to my personal clone, but rather to this repository. Thanks!

Hey, Taco, sorry for the slow response on this; review just slipped my mind.
The biggest sticking point for me right now is the defrag subdirectory... what would you think of putting this code into something like defrag/lcmdefrag, so we don't have all the future defrag stuff in a single directory and run into a problem like we have now with layers being a catch-all?

No problem!
Yeah, that sounds like a good idea. I guess that this would then also apply for the ip4defrag packet (which IMHO should be under defrag as well)?
Let me amend on Monday! Have a nice weekend!

yep, sounds good.  let's not do the ip4defrag switch as part of this pull (we'll want to do some silly type aliasing and stuff to not break compatibility), but I think long-term it's a fine idea.

Yeah, I wasn't talking about this PR. Should definetely be a seperate one!

Hi @gconnell. Moved to a new package. Sorry 'bout the merge commit there. Not quite sure how we can get rid of it...

Ignore the mess that was in between here. Now it looks nice :sunglasses:

Great, thanks for the fast turn-arounds!


Contribute data to Character endpoint

The /character endpoint currently has ~25~ ~40~ characters.  (Update #25 )
There are still few characters that we can add to this endpoint.
Contribute data for individual characters of Final Space in the given schema.
Resource: https://final-space.fandom.com/wiki/Category:Characters
P.S. You can leave the field for img_url.
You can send a PR with the data in JSON format to the endpoint branch under character folder.
Please check if the data for that character exists.
Here is the schema for /character endpoint:

Key
Type
Description

id
int
The id of the character (starting from 1).

name
string
The name of the character.

status
string
The status of the character.

species
string
The species of the character.

gender
string
The gender of the character.

hair
string
The hair color of the character.

origin
object
Name of the character's origin location.

abilities
array
Different abilities of character.

alias
array
Different names of character.

img_url
string (url)
Link to the character's image.

I will add some more to this for you.

Thanks @stevenjburrows
I will assign this issue to you then.

I will add some more to this for you what do you want for origin as the wiki doesn't mention it for the three I have looked at

Hey,
You can add Unknown in such cases,
There are many characters with less information,
You can refer here for more such queries,
https://finalspaceapi.com/api/v0/character
Thanks

Update : After #25 there are 40 characters in the database now, I am keeping this issue open,  just in case someone come across a character that isn't present in the database and want to work on it.


Remove IAVL per-get/delete timing info

Remove timing info from every IAVL get/delete call.
Varies between .5 to 1% speedups to blocksync, and I have never once used this telemetry info.

Summary by CodeRabbit

Refactor

Improved the timing of telemetry measurements in the Get, Has, and Delete operations to enhance performance tracking.

its already removed upstream, nice