Update Sonarr/Radarr to use v3 api

Motivation for changes:
The latest versions of Sonarr and Radarr have removed the legacy API. We need to start using API v3. I believe it is as simple as changing the URL path.
I've changed this on my system and ill test for a few days.
To Do:

[ ] Do we need to handle old versions of Sonarr/Radarr??

Good question about backward compatibility, we have a similar standing issue with #2906
I think we need some sort of of (soft) policy. It's always annoying if updating software x then requires upgrading bunch of other applications too, but we don't have too many maintainers / testers to keep everything tested to be backwards compatible ....
I'd say we note these upgrade requirements in changelog and support only latest stable releases.
@gazpachoking, any opinions?

@paranoidi i believe Radarr and Sonarr v3 and v4 (latest unstable) both support v3 API. So this may be a non-issue.

I've been running off this brach for 24 hours, so far no errors.

@gazpachoking @paranoidi been running for a while now. It seems stable.
Thoughts on how we handle legacy?
NOTE: I do need to look into the current versions of sonarr/radarr to understand what API level they support vs the bleeding edge.

@gazpachoking @paranoidi thoughts on merge?

Will this be included into the main branch soon?

@stevezau Can you review #3771 and accept the MR, so we can move on with this MR enabling support for radarr/sonarr v3 api? Thx.

@gazpachoking @paranoidi this has been working for me for a long time.. Should we merge?
It only handles v3 API from sonarr/radarr.. Given they have been out for a while maybe that's ok?

@stevezau Can you review #3771 and accept the MR, so we can move on with this MR enabling support for radarr/sonarr v3 api? Thx.

looks like there might be 1 or 2 more merge conflicts?

The commit list is suspiciously long, and the actual changes are suspiciously short. Are those few changes the only things actually needed? If so it shouldn't be too hard to fix up the conflicts.

It only handles v3 API from sonarr/radarr.. Given they have been out for a while maybe that's ok?

I'm fine with it.

The commit list is suspiciously long, and the actual changes are suspiciously short. Are those few changes the only things actually needed? If so it shouldn't be too hard to fix up the conflicts.

I think it is because I've kept it up to date with develop, at one point. I also opened it a long time ago. But yes, the file changes as fairly small.

@stevezau Can you review #3771 and accept the MR, so we can move on with this MR enabling support for radarr/sonarr v3 api? Thx.

looks like there might be 1 or 2 more merge conflicts?

Merged branch develop and fixed conflicts: #3775

@patrickegli odd it is still showing conflicts?

@patrickegli i merged in your changes but it caused a whole lot more merge conflicts.. I didn't review your changes as I don't have time..
I am not sure what has happened?

@patrickegli i merged in your changes but it caused a whole lot more merge conflicts.. I didn't review your changes as I don't have time..
I am not sure what has happened?

I don't know exactly what went wrong, because all checks passed in my MR. Maybe it's because i merged branch develop in my fork repository and not in original repo? 🤔
Easiest would be if you can grant me write access on this branch?

@patrickegli i added you to the team so you should have access

@patrickegli i added you to the team so you should have access

06:50:18.295: [Flexget] git push
remote: Permission to Flexget/Flexget.git denied to patrickegli.
fatal: unable to access 'https://github.com/Flexget/Flexget.git/': The requested URL returned error: 403

Doesn't work yet... Other option would be to create a new MR with a clean start from current develop instead of this almost two years old branch. What do you think?

@patrickegli i added you to the team so you should have access
Doesn't work yet... Other option would be to create a new MR with a clean start from current develop instead of this almost two years old branch. What do you think?

Sorry, had to join the team first... Works now.

All tests are passing. Merging it in.


Support binary type natively

aws-sdk-dynamodb expects StringIO object for binary and returns back the same object type for binary values.
Current implementation incorrectly converts and stores binary values as strings that due to Base64 encoding use 33% more storage and read/write capacity.
Request Before:
{
  "TableName": "dynamoid_tests_documents_1732010637_594",
  "Item": {
    "image": {
      "S": "AIj/"
    },
    ...
}

Request After:
{
  "TableName": "dynamoid_tests_documents_1732010679_801",
  "Item": {
    "image": {
      "B": "AIj/"
    },
    ...
}

Started a discussion https://github.com/aws/aws-sdk-ruby/discussions/3146.

Code coverage seems to have already been broken in master. It might need a later ruby version?

Yeah, I didn't have a chance to fix this annoying issue. Please don't bother.
The only thing left is to squash working commits. I can do it on my own today later.

Cool - feel free to squash and merge when you'd like. Thank you!


[CT-729] [Bug] unrendered_config in manifest.json doesn't update correctly from model properties yaml

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Config changes from model properties yaml are not correctly propagated to the manifest.json, thus not showing up as a state change when using the state:modified selector.
Expected Behavior
I expect the config changes from the model properties yaml to be correctly propagated to the manifest.json - "unrendered_config", just like it does from the config changes made in dbt_project.yml.
This will fix the state:modified selector to correctly detect my config changes made in the model properties yaml files.
Steps To Reproduce

Clone the jaffle shop example, and set up the profiles.yml to get dbt working.
Run dbt compile. Look for customers model in target/manifest.json - has "unrendered_config": {"materialized": "table"}
Copy target/manifest.json to top directory.
Go to models/schemas.yaml and add the config block for customers model.

- name: customers
   config:
     materialized: view

Run dbt compile. Look for customers model in target/manifest.json - still has "unrendered_config": {"materialized": "table"}. The materialization config change hasn't been propagated
5-1. Side-effect (which is the real problem for me): Run dbt ls -s state:modified --state .

The selection criterion 'state:modified' does not match any nodes
No nodes selected!

Go to dbt_project.yml, and update the model config as below:

models:
  jaffle_shop:
      materialized: table
      customers:
        materialized: view
      staging:
        materialized: view

Run dbt compile. Look for customers model in target/manifest.json - now the updated config is shown here: "unrendered_config": {"materialized": "table"}.
7-1. Run dbt ls -s state:modified --state .

jaffle_shop.customers
jaffle_shop.not_null_customers_customer_id
jaffle_shop.relationships_orders_customer_id__customer_id__ref_customers_
jaffle_shop.unique_customers_customer_id

I expect the same result from step 5-1.
Relevant log output
No response
Environment
- OS: MacOS 12.1
- Python: 3.8.9
- dbt: 1.1.0 (dbt-bigquery 1.1.0)

What database are you using dbt with?
bigquery
Additional Context
Similar issue is reported for the jinja config macro:
https://github.com/dbt-labs/dbt-core/issues/3680
But the fix for the jinja config macro won't necessarily fix this issue.

Agree that https://github.com/dbt-labs/dbt-core/issues/3576 and https://github.com/dbt-labs/dbt-core/issues/3680 are related to the larger topic here, but actually separate from the specific bug reported here.
The bug here seems much easier to reproduce, and (hopefully) to get to the bottom of why configurations defined in standard .yml files aren't being reflected in unrendered_config.
Ideally, unrendered_config would include (as the name says) the unrendered versions of configs in .yml files, such that if your config looks like:
- name: customers
   config:
     materialized: "{{ 'view' if target.name == 'dev' else 'table' }}"

We'd store that whole Jinja expression, rather than 'view' or 'table' (depending on the environment), leading to cross-env "false positives" for state:modified.
As a practical matter, even just storing 'view' or 'table' sounds better than the status quo, where the materialization change fails to propagate at all, leading to a "false negative" worse.


Ensure that signatures involving Java wildcards are stable. [phab:D1364]

Created by benjyw at 2017-02-23 01:39:05:
Previously wildcards were disambiguated using a Java hashCode,
which is not stable across compiler invocations.
This change replaces that hashCode with a string composed of
the source file path (relative to the source root), and the index
of the wildcard in the order encountered in the source file.
This guarantees that the relevant vnames are stable across
multiple invocations, and even stable if a file is compiled
in different compilation units (e.g., compiling A.java and B.java
together, and later compiling each separately).

salguarnieri commented inline (context lost during migration) at 2017-02-23 01:49:50:
It may be unlikely, but given that getWildcardNode and getFileNode are both public, is it possible to call getWildcardNode before getFileNode? If so, that would make the API a little brittle. Is there a way to not have this method depend on getFileNode?

benjyw wrote at 2017-02-23 02:24:14:

Implement without relying on getFileNode being called before getWildcard.

benjyw commented inline (context lost during migration) at 2017-02-23 02:24:48:
You're right - this assumes that getFileNode is called on a file before getWildcardNode is on some wildcard in that file, which I agree is not ideal.
See if you like this version better.

benjyw wrote at 2017-02-23 02:24:48:
Pushed a change that should address your valid concern.

salguarnieri commented inline (context lost during migration) at 2017-02-23 16:46:38:
What about passing ctx.getSourceName* (from visitWildcard) and keeping a map from source name -> wildcard count? That way users of this class don't have to remember to call setCurrentSourceFile. It also might help in the case that someone is using this class in a weird way and switching back and forth between source files.
*I don't know if getSourceName provides enough absolute context, so it might not work.

benjyw commented inline (context lost during migration) at 2017-02-23 20:59:46:
getSourceName doesn't provide enough context (it's just the file name, with no path) but it's trivial to add getSourcePath to the TreeContext.
Have changed this as you suggest, just testing it out now.  Will push the code once I'm sure it works.

benjyw wrote at 2017-02-23 20:59:46:
In general, is use of lambdas acceptable in the Kythe Java source? I don't recall seeing any, but I wanted to use this idiom to maintain the wildcardIndex map:
sourceToWildcardCounter.merge(sourcePath, 0, (i, __) -> i + 1))
Is that reasonable, or is there some prohibition on these?

salguarnieri wrote at 2017-02-23 21:07:32:
In general, lambdas are OK.

benjyw wrote at 2017-02-23 21:21:51:
Never mind - the non-lambda version was simple and more readable anyway...

benjyw wrote at 2017-02-23 22:31:57:

Maintain a map from source file -> wildcard counter.

salguarnieri commented inline (context lost during migration) at 2017-02-23 22:51:29:
You are removing the leading / here, right? If so, can you just add a simple comment that explains the substring(1) bit.

salguarnieri commented inline (context lost during migration) at 2017-02-23 22:51:29:
Can you replace sourcePath + counter with Objects.hash(sourcePath, counter) to make it future proof. If not, I'm ok with how it is because it should be unique for Java as I understand it.

salguarnieri wrote at 2017-02-23 22:51:29:
LGTM, I'll accept after the comments are addressed.
Thanks for putting up with my nit picks :)

benjyw wrote at 2017-02-23 23:35:40:

Add more detail in a comment.

benjyw commented inline (context lost during migration) at 2017-02-23 23:36:36:
I'd rather not, if that's OK, because most other salts are human-readable (or as close to it as we can get) and this stuff is hard enough to debug already... :)

salguarnieri commented inline (context lost during migration) at 2017-02-24 00:05:49:
SGTM

salguarnieri accepted this revision at 2017-02-24 00:05:49

salguarnieri closed via commit 92d7e9e4a68c94d3a3aff21b4c61841d1897d903 at 2017-02-24 01:16:44


Update text and make filters sticky

Update text

Sticky filters on custom compare

It's actually the same size. Maybe some optical effect


Added the necessary import 'webpack-dev-server' to configuration-languages for typescript

Improved the example in configuration languages for typescript to include the necessary “import 'webpack-dev-server';”.
This one line would have saved me some time. I hope it will help someone else.

Can you share what kind of problem do you have without import 'webpack-dev-server'? I've tested without import 'webpack-dev-server', and it seems fine so far:

You are correct, it does build fine.
When I test it in VS Code there are no errors shown, but in VS 2019 typescript shows the following error.


/event-data page broken in 2.12.0

Describe the Bug
Clicking on the Event Data link (/websites/THE_LONG_WEBSITE_ID_STRING/event-data) in the website details page triggers a Cannot read properties of null (reading 'toString') error.

This issue occurs on both local machine and the version deployed on Heroku. The page was working fine in 2.11.3
Database
PostgreSQL
Relevant log output
No response
Which Umami version are you using? (if relevant)
2.12.0
Which browser are you using? (if relevant)
Chrome, Firefox
How are you deploying your application? (if relevant)
Heroku

Looks like the same as #2798.

Fixed in v2.12.1.


bug: demo workflows keep going stale

move code into shared workflow runs so only one place needs updating
add workflow dispatch, so deploy can happen without a PR (optional)

Unless there's interest I'm going to leave nr-fom's devops alone.Unless there's interest I'm going to leave nr-fom's devops alone.


kitematic

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

https://www.docker.com/community-edition#/mac


connectivity_macos not found. Please update settings.gradle.

flutter run --verbose:
https://pastebin.com/mibuJkfJ
pubspec.yaml:
https://pastebin.com/3x7wtXA1
flutter analyze
https://pastebin.com/X1mPmMmr
flutter doctor -v
https://pastebin.com/riX1pswq

Hi @danielmessi13
I see there's an open issue addressing the case you described (https://github.com/flutter/flutter/issues/62413).
Please follow up on that issue, I'm closing the current one as a duplicate.
If you disagree, please write in the comments and I will reopen it.
Thank you


Wpf XAML Autocomplete for VSCode

Visual Studio UI lacks a lot of functionallity built in VSCode and the performance is terrible. I use normally VSCode for all my work and my productivity is increased in comparison to using Visual Studio. I really love VSCode ❤. The only downfall is the lack of proper XAML autocompletion.
That's why I would like to request an autocomplete support extension for visual studio code. I don't want a full visual designer like in visual studio, I don't even use that. I only would want to have a working XAML code autocomplete.
I already suggested this in the wpf official repository and they told me to ask here.
The UNO Platform extension looks good but it doesn't work for WPF.

https://github.com/OmniSharp/omnisharp-vscode/issues/3338

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!

OmniSharp/omnisharp-vscode#3338

Thanks for pointing me to the correct thread


docs: [RU] Translation update

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

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[x] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Other information:
Latest updates to RU documentation :)

Maybe better to merge into dev branch?


[Linux] Bundling the Linux app as a Snap file and eventually publishing to the Snap Store, CMake Error:

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Bundling the Linux app as a Snap file and eventually publishing to the Snap Store, filed
(if build from flutter git version its ok)
snapcraft --use-lxd --bind-ssh
bound : https://github.com/flutter/flutter/issues/108419
Actual results
build
Logs
Still not working:
snapcraft --use-lxd --bind-ssh

[+15 ms] executing: [build/linux/x64/release/] cmake -G Ninja
-DCMAKE_BUILD_TYPE=Release -DFLUTTER_TARGET_PLATFORM=linux-x64
/root/parts/myapp/build/linux
[ +777 ms] CMake Error: The current CMakeCache.txt directory
/root/parts/myapp/build/build/linux/x64/release/CMakeCache.txt is different
than the directory /home/vboxuser/projects/myapp/build/linux/x64/release where
CMakeCache.txt was created. This may result in binaries being created in the
wrong place. If you are not sure, reedit the CMakeCache.txt
[ +9 ms] CMake Error: The source
"/root/parts/myapp/build/linux/CMakeLists.txt" does not match the source
"/home/vboxuser/projects/myapp/linux/CMakeLists.txt" used to generate cache.
Re-run cmake with a different source directory.
[ +167 ms] Building Linux application... (completed in 958ms)
[ ] "flutter linux" took 3,316ms.
[ +5 ms] Unable to generate build files
[ +1 ms]
0 throwToolExit
(package:flutter_tools/src/base/common.dart:10:3)
1 _runCmake
(package:flutter_tools/src/linux/build_linux.dart:151:5)

2 buildLinux
(package:flutter_tools/src/linux/build_linux.dart:73:5)

3 BuildLinuxCommand.runCommand
(package:flutter_tools/src/commands/build_linux.dart:86:5)

4 FlutterCommand.run.
(package:flutter_tools/src/runner/flutter_command.dart:1297:27)

5 AppContext.run.
(package:flutter_tools/src/base/context.dart:150:19)

6 CommandRunner.runCommand
(package:args/command_runner.dart:212:13)

7 FlutterCommandRunner.runCommand.
(package:flutter_tools/src/runner/flutter_command_runner.dart:339:9)

8 AppContext.run.
(package:flutter_tools/src/base/context.dart:150:19)

9 FlutterCommandRunner.runCommand
(package:flutter_tools/src/runner/flutter_command_runner.dart:285:5)

10 run..
(package:flutter_tools/runner.dart:115:9)

11 AppContext.run.
(package:flutter_tools/src/base/context.dart:150:19)

12 main (package:flutter_tools/executable.dart:90:3)

### Flutter Doctor output

snapcraft 7.5.2
cmake version 3.27.4

(snap download Flutter 3.13.2 • channel stable • https://github.com/flutter/flutter.git
Framework • revision ff5b5b5fa6 (8 days ago) • 2023-08-24 08:12:28 -0500
Engine • revision b20183e040)
Tools • Dart 3.1.0 • DevTools 2.25.0

Ubuntu 22.04.3 LTS (vbox)

Thanks for the report @statsss
Does https://stackoverflow.com/a/14459230 help in your case ? Or by deleting the build folder and recreating it ?

Please check if this helps in your case or not.


2.0 release

This project has outgrown my personal hobby project, so i like to discuss a few options about what to do with the repository when we release 2.0:

transfer to an organization
keep everything as is under my account
fork to an organization, archive this repository

I'd prefer option 1, but i don't know how package managers etc targeting 1.* versions would handle that.

We should also think about a good name for the organization. Fastfetch is on the hand, but in the long term we might split out usefull parts as extra libraries etc, so maybe we need a common name.

From the GitHub docs:

All links to the previous repository location are automatically redirected to the new location. When you use git clone, git fetch, or git push on a transferred repository, these commands will redirect to the new repository location or URL.

I think we are fine transfering it.

What about libfastfetch, or shorter, libfetch?

What about libfastfetch, or shorter, libfetch?
Or fastfetch-cli

Those all seem like the name of a single repository, not the name of the organization containing all of them

Or fastfetch-cli

I actually took the idea from Macchina-CLI, which is also a neofetch like CLI tool.
Fastfetch-CLI ( the group name )
  |- fastfetch ( the CLI program exe file )
  |- libfastfetch ( the library behind exe. May be compiled into a so / dylib / dll in the future )

I did go this way.


[Website][CI] Build Website without Warnings + Add Workflow for Building Website

Description

Fix some bugs and documentation issues to build website without any warnings
Add workflow for building website

TODO:

[ ] Include model_zoo documentation for website build
[ ] Deploy website on github.io or S3

Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[ ] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage
[x] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

cc @dmlc/gluon-nlp-team

what's the motivation to run shell commands in a python script?

For me, I felt it more convenient to run and debug this workflow in python script rather than in shell script.


[BUG] Improve protected member usage

Describe the bug
Lots of Access to a protected member _(...)_thread of a client class
Evidence

pylint plugwise/*py (and/or subdirectories)
W0212: Access to a protected member _(...)_thread of a client class (protected-access)
Rewrite these to non-underscore to share outside of class

Additional context
Found as part of codefactor improvements and refactoring.
Should be handled with care since we don't have the appropriate tests for the stick part.

List of todo's (usb related, excluding already marked as fixme/todos)
************* Module plugwise.stick
plugwise/stick.py:67:0: C0103: Class name "stick" doesn't conform to PascalCase naming style (invalid-name)
plugwise/stick.py:560:15: W0212: Access to a protected member _run_receive_timeout_thread of a client class (protected-access)
plugwise/stick.py:561:23: E1101: Instance of 'Thread' has no 'isAlive' member (no-member)
plugwise/stick.py:561:23: E1101: Instance of 'bool' has no 'isAlive' member (no-member)
plugwise/stick.py:561:23: W0212: Access to a protected member _receive_timeout_thread of a client class (protected-access)
plugwise/stick.py:565:20: W0212: Access to a protected member _receive_timeout_thread of a client class (protected-access)
plugwise/stick.py:567:24: W0212: Access to a protected member _receive_timeout_loop of a client class (protected-access)
plugwise/stick.py:572:20: W0212: Access to a protected member _receive_timeout_thread of a client class (protected-access)
plugwise/stick.py:573:20: W0212: Access to a protected member _receive_timeout_thread of a client class (protected-access)
plugwise/stick.py:575:15: W0212: Access to a protected member _run_send_message_thread of a client class (protected-access)
plugwise/stick.py:576:23: E1101: Instance of 'Thread' has no 'isAlive' member (no-member)
plugwise/stick.py:576:23: W0212: Access to a protected member _send_message_thread of a client class (protected-access)
plugwise/stick.py:580:20: W0212: Access to a protected member _send_message_thread of a client class (protected-access)
plugwise/stick.py:582:24: W0212: Access to a protected member _send_message_loop of a client class (protected-access)
plugwise/stick.py:587:20: W0212: Access to a protected member _send_message_thread of a client class (protected-access)
plugwise/stick.py:588:20: W0212: Access to a protected member _send_message_thread of a client class (protected-access)
plugwise/stick.py:591:23: E1101: Instance of 'Thread' has no 'isAlive' member (no-member)
plugwise/stick.py:635:28: W0212: Access to a protected member _request_ping of a client class (protected-access)
plugwise/stick.py:639:28: W0212: Access to a protected member _request_power_update of a client class (protected-access)
************* Module plugwise.util
plugwise/util.py:156:4: W0231: __init__ method from base class 'BaseType' is not called (super-init-not-called)
************* Module plugwise.connections
plugwise/connections/__init__.py:36:12: E1101: Instance of 'StickConnection' has no '_open_connection' member (no-member)
plugwise/connections/__init__.py:52:19: E1101: Instance of 'StickConnection' has no '_read_data' member (no-member)
plugwise/connections/__init__.py:83:16: E1101: Instance of 'StickConnection' has no '_write_data' member (no-member)
plugwise/connections/__init__.py:103:15: E1101: Instance of 'Thread' has no 'isAlive' member (no-member)
plugwise/connections/__init__.py:107:15: E1101: Instance of 'Thread' has no 'isAlive' member (no-member)
plugwise/connections/__init__.py:120:18: E1101: Instance of 'Thread' has no 'isAlive' member (no-member)
plugwise/connections/__init__.py:123:12: E1101: Instance of 'StickConnection' has no '_close_connection' member (no-member)
************* Module plugwise.messages
plugwise/messages/__init__.py:18:14: E1101: Instance of 'PlugwiseMessage' has no 'ID' member (no-member)
************* Module plugwise.messages.requests
plugwise/messages/requests.py:252:8: C0103: Variable name "t" doesn't conform to snake_case naming style (invalid-name)
plugwise/messages/requests.py:254:8: C0103: Variable name "d" doesn't conform to snake_case naming style (invalid-name)
************* Module plugwise.messages.responses
plugwise/messages/responses.py:78:14: E1101: Instance of 'NodeResponse' has no 'ID' member (no-member)
plugwise/messages/responses.py:258:8: C0103: Attribute name "in_RSSI" doesn't conform to snake_case naming style (invalid-name)
plugwise/messages/responses.py:259:8: C0103: Attribute name "out_RSSI" doesn't conform to snake_case naming style (invalid-name)
plugwise/messages/responses.py:340:8: C0103: Attribute name "hz" doesn't conform to snake_case naming style (invalid-name)
************* Module plugwise.nodes
plugwise/nodes/__init__.py:46:8: C0103: Attribute name "_RSSI_in" doesn't conform to snake_case naming style (invalid-name)
plugwise/nodes/__init__.py:47:8: C0103: Attribute name "_RSSI_out" doesn't conform to snake_case naming style (invalid-name)
plugwise/nodes/__init__.py:323:15: E1101: Instance of 'PlugwiseNode' has no '_categories' member (no-member)
plugwise/nodes/__init__.py:330:15: E1101: Instance of 'PlugwiseNode' has no '_sensors' member (no-member)
plugwise/nodes/__init__.py:337:15: E1101: Instance of 'PlugwiseNode' has no '_switches' member (no-member)
plugwise/nodes/__init__.py:365:15: E1101: Instance of 'PlugwiseNode' has no 'self' member (no-member)
plugwise/nodes/__init__.py:392:4: C0103: Method name "get_in_RSSI" doesn't conform to snake_case naming style (invalid-name)
plugwise/nodes/__init__.py:401:4: C0103: Method name "get_out_RSSI" doesn't conform to snake_case naming style (invalid-name)
************* Module plugwise.nodes.circle_plus
plugwise/nodes/circle_plus.py:100:8: C0103: Variable name "dt" doesn't conform to snake_case naming style (invalid-name)
************* Module plugwise.nodes.scan
plugwise/nodes/scan.py:100:4: C0103: Method name "CalibrateLight" doesn't conform to snake_case naming style (invalid-name)
plugwise/nodes/scan.py:104:4: C0103: Method name "Configure_scan" doesn't conform to snake_case naming style (invalid-name)
plugwise/nodes/scan.py:129:4: C0103: Method name "SetMotionAction" doesn't conform to snake_case naming style (invalid-name)
************* Module plugwise.nodes.sed
plugwise/nodes/sed.py:38:8: C0103: Attribute name "_SED_requests" doesn't conform to snake_case naming style (invalid-name)
plugwise/nodes/sed.py:118:4: W0221: Parameters differ from overridden '_request_ping' method (arguments-differ)
plugwise/nodes/sed.py:140:4: C0103: Method name "Configure_SED" doesn't conform to snake_case naming style (invalid-name)

#78 and #90 have solved almost all issues.
This is the present result:

Looks like the removed BaseType-inherit causes new pylint warnings.

The remaining issues were fixed in #91.


docs: elaborate the contributing guide

This closes #180.
Signed-off-by: tison<EMAIL_ADDRESS>I'm trying to elaborate the contributing guide a bit to help on answering repeating questions, while keep short to avoid pulling too much context before we have more contributors (and real-world needs).
As a result, we can still write all stuff in CONTRIBUTING file. Let's keep it concise and only introduce a folder layout later when necessary.
Brief changes:

A copy-and-paste-able get started section
Community principles
How to review patches
How to make code contribution and verify patch locally
Licenses

For someone who are not familiar with GitHub workflow, perhaps we should give a quick entry.
Like this:
https://github.com/MaterializeInc/materialize/blob/45042e12f937bcd5f37ff6a04335b02e834c3321/README.md?plain=1#L116

@DCjanus I've thought of it, but give up since actually we don't label "good first issue" heavily. If you take a closer look, we don't have even one "good first issue". So I don't include such a sentence before we really do it.
However, it's a good point that @huachaohuang and other further maintainers can try to apply and we add this entry later.

Hi, after reviewing this PR, I cannot give too many suggestions about content 🤔 As for the structure, could we separate the Get Started part into a standalone document?

I think it's OK so far. We can keep it together until it gets lengthy.

However, it's a good point that @huachaohuang and other further maintainers can try to apply and we add this entry later.

Well, the truth is, there aren't many "good first issues" so far. I think most tasks are quite hard actually. But I will pay attention to it.


Support for Category-Page Metadata definition.

Issue
Part of #4786: Add support for web metadata on category pages
Note
Remaining task: category-metadata.js needs to be filled first.

@jessopb can you consider this as part of your re-work of homepage configuration?


Error during "go install" on ARM platforms (Pi & Odroid)

When I documented the build and installation of LND about three weeks ago in a guide (see section 8) for usage on a ARM-based Odroid HC2, the installation of LND as described in the Github installation instructions worked flawlessly.
Starting last week, I got several feedbacks of users (see this and this) that get the following error:
$ cd $GOPATH/src/github.com/lightningnetwork/lnd
$ git pull && glide install
$ go install . ./cmd/...
# github.com/lightningnetwork/lnd/htlcswitch
htlcswitch/circuit.go:21: syntax error: unexpected = in type declaration

Today, I retested my guide on two machines and ran into the same error.

Raspberry Pi 3 with Raspbian GNU/Linux 9.3 (stretch)
Odroid HC2 with  Ubuntu 16.04.4 LTS

Some parameters:
$ uname -r
4.9.59-v7+ (Raspberry Pi)
4.14.20-108 (Odroid HC2)
$ go version
go version go1.8 linux/arm
$ echo $GOPATH
/home/pi/go
$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin:/home/pi/go/bin

Any idea what's causing this? Any additional info that I can provide?

The minimum version of Go was changed to 1.10, because this error is due to a type alias, a feature introduced in go1.9, and you only have 1.8 installed.
See https://github.com/lightningnetwork/lnd/pull/818 & https://github.com/lightningnetwork/lnd/issues/815

Thanks, I just tested it for myself and when using go1.10 it works.


Intelligent base branch detection

We ran into a problem where people's branches become stale after someone merges some new changes into the base branch and then pint tries to report problems on issues that they haven't introduced themselves. As far as I know, GitHub does not have a base branch ref of a pull request: https://github.com/isaacs/github/issues/757.
Thus, I propose adding an option such as pick_base_branch to the ci block. If set to true then when pint runs it should point to a merged ref, and pint should automatically detect the base branch from that.
Either pick_base_branch should be set or baseBranch - not both. @prymitive what do you think? If it makes sense then I could implement this. It would solve some pain points for us.

How are you running pint? Is it via actions or some other way?
For actions there seem to be base ref in the context - https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#github-context

Via Jenkins. FWIW I have worked around this problem by having baseBranch = "$baseBranchPlaceholder" and:
COMMON_ANCESTOR = sh(script: "git merge-base origin/${env.GIT_BRANCH} origin/${env.CHANGE_TARGET}", returnStdout: true).trim()
sh "sed -i 's/\$baseBranchPlaceholder/${COMMON_ANCESTOR}/g' .pint.hcl"

I guess the ergonomics could be improved here however that's a different issue altogether so I'll close this. Thanks for your response & time! pint is great (:


Cut dependency from Core to Complex.

With this, Math-Core does not depend on anything else from Polymath.


Using this (or newer version on pferrel) with Swift 2.0

Hi,
I am wondering if there are any plans to update the PredictionIOSDK for swift to be compatible with Xcode 7 and Swift 2.0.  Currently it is impossible to use PredictionIO with the newer version of Swift.
Thanks!
Anthony

Hi,
Now I use the xcode7 version, but can not use pod to import your SDK what method can you normally import your SDK? .
Thanks!
zhong


Add a heatmap to a chord diagram

I need help figuring out how to add a color bar to a chord diagram I have made. I would like to add a color bar such as in a heat map:  but in a chord diagram: This is not to be confused with a filled chord diagram in python plotly.
Here are their tutorials: Heat Map, Chord Diagram, Filled Chord Diagram
The way in which I plan to use the heat map is to have each line on the chord diagram be a certain color based on the data. For example, if the data says the line has a value of 80, it would be red like in the heat map. If the data said 50, it would be an orange-ish yellow, like in the heat map.
Thank you so much!

Don't think we can help you with that here. 😁


Fix exunit tests for ateles

Overview
Fix exunit tests for ateles

Testing recommendations
make exunit

Related Issues or Pull Requests

Checklist

[x] Code is written and works correctly
[x] Changes are covered by tests
[ ] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[ ] A PR for documentation changes has been made in https://github.com/apache/couchdb-documentation

ateles is not an Apache CouchDB application we can't depend on it
I think we might want to depend on couch_eval there perhaps


Convert eligible methods to use @property decorator

Convert methods that are used to access private attributes to use the @property decorator. Refactor usages of the methods.
Example:
class Offering:
    def __init__(
            self,
            instructor: str,
            price: str,
    ):
        self._instructor = instructor
        self._price = price

    def instructor(self) -> str:
        return self._instructor

    def price(self) -> str:
        return self._price

Becomes:
class Offering:
    def __init__(
            self,
            instructor: str,
            price: str,
    ):
        self._instructor = instructor
        self._price = price

    @property
    def instructor(self) -> str:
        return self._instructor

    @property
    def price(self) -> str:
        return self._price

Archived.


CORE-16230 Split UniquenessProcessor into its own worker

UniquenessProcessor split into its own worker

Errr, why split the uniqueness processor into its own worker? Doesn't this change fly in the face of everything we've recently learnt about Kafka? :exploding_head:
I cannot for the life of me understand how this can possibly make Corda 5 process flows any faster. More likely, it will do the exact opposite, while also making Corda more expensive to operate.

Flows will communicate with other workers via RPC, not Kafka. Having more different processors in different workers will enable scaling each of them as separately. I'm not sure whether/how much difference will it actually make, @Omar-awad did a POC and can comment more regarding this.

Flows will communicate with other workers via RPC, not Kafka. Having more different processors in different workers will enable scaling each of them as separately. I'm not sure whether/how much difference will it actually make, @Omar-awad did a POC and can comment more regarding this.

At the moment, each flow processor is deployed alongside its own uniqueness processor within the same JVM, and I really don't see how you can get any faster than that.

Flows will communicate with other workers via RPC, not Kafka. Having more different processors in different workers will enable scaling each of them as separately. I'm not sure whether/how much difference will it actually make, @Omar-awad did a POC and can comment more regarding this.

@mbrkic-r3 that doesn't sound like a strong reason to me - I thought we'd established during the GA release cycle about the need to show a benefit from performance related changes? Can you point me to the evidence of the performance testing you've done to show that this change will be a positive one?
From conversations I've had with @driessamyn and @Omar-awad it sounds like there are other reasons for making this change, but the difficulty is this hasn't been properly communicated with the SME's, and I need that background in order to sensibly review this PR. Can we get a meeting set up with yourself / @JamesHR3 / @Omar-awad to discuss the background in more detail?

At the moment, each flow processor is deployed alongside its own uniqueness processor within the same JVM, and I really don't see how you can get any faster than that.

@chrisr3 not quite - it actually lives as part of the DB worker alongside the DB processor, with the idea being that it is then co-located with DB access functions which matter given how DB sensitive the uniqueness checker is. But I agree with the thrust of your argument.

@chrisr3 not quite - it actually lives as part of the DB worker alongside the DB processor, with the idea being that it is then co-located with DB access functions which matter given how DB sensitive the uniqueness checker is. But I agree with the thrust of your argument.

OK. The problem with writing something like the driver is that you end up finding and using all the necessary components, but without always understanding where they fit into a real Corda deployment :wink:.
But regardless, I had thought we'd discovered that our Kafka problem was at least in part due to our unnecessarily sending messages over Kafka that could have been handled locally.
As an aside, I have previously (i.e. before R3) written servers for a micro-service architecture that was designed to communicate via HTTP(S), and IIRC it was very much an "eventually consistent" system requiring idempotent messaging. And it wasn't trivial to write either!

I thought we'd established during the GA release cycle about the need to show a benefit from performance related changes? Can you point me to the evidence of the performance testing you've done to show that this change will be a positive one?

This change will not have performance improvements by itself as it is part of a bigger initiative which is documented in high level here: https://r3-cev.atlassian.net/wiki/spaces/CB/pages/4552491009/Corda+Scalable+Topology+Design. As of why we need this segregation then please refer to another PR comment here: https://github.com/corda/corda-runtime-os/pull/4465#issuecomment-1683769408

But regardless, I had thought we'd discovered that our Kafka problem was at least in part due to our unnecessarily sending messages over Kafka that could have been handled locally, which could have been addressed without many of the efforts I am seeing now.

The two main issues we are tackling in the next release are:

Optimize the events flow in the system by reducing loops and congestion on some topics.
Revise heavy communication protocols in an effort to reduce the number of messages over-the-wire.

I thought we'd established during the GA release cycle about the need to show a benefit from performance related changes? Can you point me to the evidence of the performance testing you've done to show that this change will be a positive one?

This change will not have performance improvements by itself as it is part of a bigger initiative which is documented in high level here: https://r3-cev.atlassian.net/wiki/spaces/CB/pages/4552491009/Corda+Scalable+Topology+Design. As of why we need this segregation then please refer to another PR comment here: #4465 (comment)

Actually, I think @relyafi was asking to examine the performance data that presumably underlies all these extensive architectural changes. I don't think that particular comment qualifies.

Actually, I think @relyafi was asking to examine the performance data that presumably underlies all these extensive architectural changes. I don't think that particular comment qualifies.

Please refer to the design document. The reasoning and the verification is documented there.

@Omar-awad:

This change will not have performance improvements by itself as it is part of a bigger initiative which is documented in high level here: https://r3-cev.atlassian.net/wiki/spaces/CB/pages/4552491009/Corda+Scalable+Topology+Design.

Thanks for forwarding that document. The overall theoretical approach seems reasonable, but I don't see it mention splitting the uniqueness worker as one of its objectives? Combined with the fact that you say this has no performance benefits in and of itself, why do we feel this change is necessary at this point?

The two main issues we are tackling in the next release are:

Optimize the events flow in the system by reducing loops and congestion on some topics.
Revise heavy communication protocols in an effort to reduce the number of messages over-the-wire.

I don't see how this change addresses either of these issues? Uniqueness already has its own topic, and this change doesn't do anything with communication protocols.

Please refer to the design document. The reasoning and the verification is documented there.

The only evidence I see in that document is a PoC, which I'm assuming has made a multitude of changes? It could be that the individual changes made in the PoC were a mix of positive, neutral, and negative, and on balance they turned out to be positive. That does not mean we can infer that every change in the PoC was a positive.
The only way to do that is A/B testing for a specific change we want to make. I think the following from the acceptance criteria of the document you linked backs this up:
Implemented components should show clear value in being shipped.
As it stands, I don't think this PR passes that test.


Google SSO Error: Disallowed User Agent

Hello,
I am using the Browser to display an Open ID Login Page. Sadly, Google blocks the Browser by it's user agent. I know I can set headers, but the only persist for the first request. The google sign in screen comes after a redirect. Is there a way you can fix that?
Kind regards,
Marius
Edit: Error appears on iOS and Android.

Can you provide a reproduction repo ?
it will be a bit hard to find a solution for this i believe so a bit of help will be super useful

Oh yes, sure!
Maybe it's easier for you if I just provide a code snipped:
await InAppBrowser.openWebView({
  title: 'Login',
  url: 'https://dashboard.clerk.com/sign-in',
  toolbarType: ToolBarType.NAVIGATION
});

When you click on "Continue with Google" it shows the error.
If you still need a Demo Project, please let me know!
Thank you!

 I noticed that the package was updated to version 1.2.7. I gave it a try using the iOS simulator, but unfortunately, I'm still encountering the disallowed_useragent error.

@jaderinoo
That's odd, have you ruled out cached packages by running npx cap sync ios ?

Yes, I've also gone through and checked the version in the files, and they're all pointing to 1.2.7.

@jaderinoo I see, I'll look into further in morning. Also what iOS version were you running?

@neo773 Thanks for being so quick about it. The simulator is running ios 17.0.

@neo773 Any update on this?

@jaderinoo
https://github.com/Cap-go/capacitor-inappbrowser/assets/62795688/f3a8b7f1-ec4c-47c2-87d5-4b1c568e9d38
Hey, I just tested it I'm unable to reproduce it on my end.
Maybe you're using a bad user-agent
Could you try with mine?
 InAppBrowser.openWebView({
  title: 'Login',
  url: 'https://dashboard.clerk.com/sign-in',
  toolbarType: ToolBarType.NAVIGATION,
  headers: {
    'user-agent': `Mozilla/5.0 (iPhone; CPU iPhone OS16_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.5.2 Mobile/15E148 Safari/604.1`
  }
});

@neo773 Thanks for the tip, I’ll check it out a little later.

Shouldn't it work out of the box without setting a user agent? If I am using the standard iOS In-App-Browser it also works out of the box.

@mariusbolik That's what I had expected as well

That's just standard WKWebView behavior. Remember, WKWebView !== Safari. Although they may appear similar on the surface, they have many differences under the hood.
The default user-agent on the left is from Safari, while the one on the right is from WKWebView. This issue has nothing to do with the library, which is why you are getting the disallowed_useragent when a custom user-agent isn't set.

@neo773 I get what you're saying, but how would one handle this in production? I tested using the custom user agent you posted and that works just fine, but how would we handle this on different devices.

@jaderinoo What do you mean by “different devices”” all iPhones have same user agent it doesn’t reveals the exact iPhone model.
So a hardcoded one should work perfectly fine in production.

@neo773 Sorry, I should've been more specific. I'm building my app for web, android, and ios. So, in this case, I'd be using the same useragent for all 3 unless I specify presets for each platform.

@jaderinoo Does using Capacitor’s native APIs to detect the platform and setting the user-agent conditionally not work for you?
https://www.npmjs.com/package/@capacitor/device#interfaces

@neo773 I'll give that a shot, it's been a long week and I've been fogged up a bit. Not sure why I didn't think of this.

Just a friendly reminder that this issue still isn't fixed. The problem is, that this browser does not work with OAuth out of the box. Yes, it's possible to set a custom user agent, but it would be great if the browser would work with OAuth without further configuration :)


Feature: rstuf state backups

What is the feature about?
We would like to make sure the state of rstuf is preserved and eventually have a way to restore/replicate rstuf state to a testing environment. Is there a preferred way on how to perform backups of an rstuf deployment? Thanks!
Services it relates to
repository-service-for-tuf
Related tasks
https://github.com/repository-service-tuf/repository-service-tuf/issues/402
References
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @fridex,
Thank you for the issue. We can improve our documentation for Repository Service for TUF (RSTUF) administrators.
The RSTUF Worker has the core data of RSTUF, the TUF Metadata.
The current RSTUF Worker uses the RSTUF_STORAGE_BACKEND; At the moment, it supports only LocalStorage type, which is a container volume. Backup the content of this volume (JSON files), saving a copy of the JSON files.
We are working also to support AWSS3 type, which uses the AWS S3 objects, and in this case, is required to backup it using the AWS options.
RSTUF Worker uses the private online key as read-only RSTUF_KEYVAULT_BACKEND. Currently, we support only LocalKeyVault type. Backup the content of this volume, saving a copy of the key.
The RSTUF Worker also uses a Postgres database to support high-traffic repositories, configured at the RSTUF_SQL_SERVER variable. This database also needs a backup. The backup strategy depends on how you deploy the Postgres.
The RSTUF Worker and API also use the Redis services. It is required to backup the repository settings database id, also defined RSTUF_REDIS_SERVER and by default id 1, or customized id RSTUF_REDIS_SERVER_DB_REPO_SETTINGS
Note: The message queue RSTUF_BROKER_SERVER and backend result RSTUF_REDIS_SERVER (default db id 1 or custom id by RSTUF_REDIS_SERVER_DB_REPO_RESULT) for tasks are not required data for RSTUF. In some integration cases, you might want this information as well.
Note: RSTUF API only requires backup if you use the RSTUF API built-in authentication/authorization, which we do not advise using. Instead, we recommend using an API Gateway service/server to implement your authentication/authorization for the API requests.
If still, you're using it. Backuping your RSTUF API mapped to the RSTUF_DATA.
To summarize:

Backup the TUF Metadata stored in  RSTUF_STORAGE_BACKEND
Backup the Private Online Key in the RSTUF_KEYVAULT_BACKEND
Backup the Postgres RSTUF Database RSTUF_SQL_SERVER
Backup the Redis databases RSTUF_REDIS_SERVER

Feature-wise, creating a restore mechanism for RSTUF from the TUF Metadata would also be possible. It will require some tests and investigation, but it could also be a simple strategy.

Thanks Kairo, this is definitely helpful. It looks like there are needed some lower level operations to make this happen. If there would be a native support for this feature that would be great. Thanks again!

I filed an issue to continue the idea as a feature. 😄
Thanks, @fridex, for bringing it up.


[ARROW-977][java] Add Timezone aware timestamp vectors

@wesm follow up on https://github.com/apache/arrow/pull/568
cleaning up the templates

@wesm rebased

@wesm: fixed. Sorry about that

Since we now have 8 timestamp classes in Java, if there is any way to simplify in the near future to limit the collateral damage in downstream projects of future API changes, that would be great


Learn netty 4.1.91.final

Motivation:
Explain here the context, and why you're making that change.
What is the problem you're trying to solve.
Modification:
Describe the modifications you've done.
Result:
Fixes #.
If there is no issue then describe the changes introduced by this PR.

commit


xla_lhlo.neg and xla_lhlo.abs support integer arguments

This pr requires a change in llvm-project , to add negi in mlir standard dialect, as discussed in
https://reviews.llvm.org/D75662

@joker-eph  plz take a look ^_^

@qqsun8819  Can you please check joker-eph's comments and resolve conflicts? Thanks!

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

I'll update this PR according to what @joker-eph comment

@joker-eph please take a look again ^_^

@joker-eph pr updated according to you comments, take a look again ^_^


Transformed files with lastUpdated in Frontmatter cause errors with Starlight typechecking

Describe the bug
From the following frontmatter:

The output file is produced:

Causing this error with Starlight:

I tested removing the " from the output file and that fixed this issue.
To Reproduce

Create a project with this plugin (copyStarlightFrontmatter: true) and a simple Obsidian Vault and a singular empty note.
Populate the a frontmatter containing lastUpdated: 2024-09-21 (I've tested other dates cause the same error)
Run the dev server and observe the outcome

Expected behavior
The page should load and the date set in the frontmatter should be shown at the bottom of the page
How often does this bug happen?
Every time
System Info

MacOS 14.6 (23G80)
Chrome

Additional Context
This used to work - only noticed the issue earlier today, not sure what or when it was introduced

Thanks for the report :raised_hands:
I assume this regression was introduced in the 0.4.7 version but should now be fixed in the 0.4.9 version that I just released.

Thanks for the swift fix!


Squid3 v1.1.6: Reference CRM values mismapped as RM values

This is only a little one, but it has stopped me in my tracks for the moment (though that doesn't matter; I have identified a larger issue as well, to be documented separately). Below is my Spot Naming and Reference Materials screen, all set up the way I want:

But when I generated my Report Table, I found all my Concentration data (U and Th) were zeroes. This was confusing because my Task had no Unhealthy Expressions. But I found at least part of the problem when I checked the RM values, specifically Ref_Th_Concen (as I am trying to test a Th-centric Task):

It shows me a zero (in contrast to the value of 418 ppm I was expecting, from my first screenshot), but helpfully points me at the Notes, and the Notes explain the problem. The explanatory sentence "Reference Th content of CM" is correct, but it is clear that the value is being taken from the wrong Model (see my first screenshot). "TEMORA2 dates only" is my Isotopic RM model, whereas Ref_Th_Concen should be taken from my Concentration RM model.
Same problem with Ref_U_Concen.

Please supply models.

Can't find them. Squid3 must know where they are, if the screenshot is any indication... but it isn't telling me! I am searching all my hard drives and network drives using Windows Explorer - no joy yet.

M127 values only v.1.0.zip
TEMORA2 dates only v.1.0.zip


How to reproduce the results for Neon. JAX.

Hi, I am trying to reproduce the results for Neon, I am running the following code with default base config and only changes to batch_size = 256, pretrain iterations = 100 and optim iterations = 100_000 (for now, will be increased if results not matched):
Training Code
import sys

from absl import logging
from ferminet.utils import system
from ferminet import base_config
from ferminet import train
import numpy as np

logging.get_absl_handler().python_handler.stream = sys.stdout
logging.set_verbosity(logging.INFO)

cfg.system.electrons = (5,5)
cfg.system.molecule = [system.Atom('Ne')]

cfg.batch_size = 256
cfg.pretrain.iterations = 100

train.train(cfg)

Loading Model
with open('ferminet_2021_08_22_16:24:03/qmcjax_ckpt_099929.npz', 'rb') as f:
    params = dict(np.load(f, allow_pickle=True))['params'].tolist()

with open('ferminet_2021_08_22_16:24:03/qmcjax_ckpt_099929.npz', 'rb') as f:
    data = dict(np.load(f, allow_pickle=True))['data']

with open(path+'geometry.npz', 'rb') as f:
    geometry = dict(np.load(f, allow_pickle=True))

foo = partial(networks.fermi_net, envelope_type='isotropic', full_det=False, **geometry)
# networks.fermi_net gives the sign/log of the wavefunction. We only care about the latter.
network = lambda p, x: foo(p, x)[1]
batch_network = jax.vmap(network, (None, 0), 0)
loss = train.make_loss(network, batch_network, geometry['atoms'], geometry['charges'], clip_local_energy=5.0)
ploss = jax.pmap(loss, axis_name='qmc_pmap_axis')  # right now, the code only works if the loss is wrapped by pmap

loss_ = ploss(params, data)  # For neon, should give -128.94165
loss_[0]

At this step loss_ = ploss(params, data), I am getting this error:

ValueError: Incompatible shapes for broadcasting: ((1, 5, 1, 1), (3, 3, 1, 160))

I compared my params with the cloud files given and it seems my pi and sigma envelopes have different shapes.
Any help on how to reproduce the pretrained results would be appreciated.

You need to use the same settings in networks.fermi_net as you used in training. In particular, the envelope_type and full_det arguments should match cfg.network.envelope_type and cfg.network.full_det.

is envelope_type and full_det in networks.fermi_net for the current Neon result the same as the current settings in cfg.network.envelope_type and cfg.network.full_det? If not, what should these values be?
Also, what are the param settings to reproduce the other elements? A list of params to reproduce the results would be helpful :)

By "current Neon result" do you mean from the Phys Rev Research paper? That was produced with the TF version (which is essentially deprecated). The isotropic envelope setting was introduced in the NeurIPS workshop paper, which gives motivation for this and comparison to the full envelope. All results published before then used the full envelope setting.
The full_det setting is experimental. Set it to False to match the published results.
For neon, neither of these settings will make a substantial difference to the final energy within statistical errors. Note your batch size is very small and might limit the accuracy you achieve.
Please refer to our papers for the settings used in the models. The PRR paper used the same set of configuration options for all experiments, except where noted, and this broadly matches the current defaults (except for full_det and envelope_type).


Worker heartbeating: Wrap critical section with read lock

Summary:
A critical section access to the @workers hash was not protected with a read lock, meaning a read could occur while another thread was writing to it.  Workers access @workers via a DRb thread running on the server process, while the server's main thread is also accessing it.
Note, this is probably not a huge problem because a slightly incorrect last_heartbeat value will probably not be something anyone would notice.
43e9676 Wrap critical @workers reads with a read lock
fbf7007 last_heartbeat is already nil, don't check it again
18a938f Add explanation of the missing stopping workers.
caf0e77 Initial worker heartbeat wasn't saving the record.
271856d Extract a method to read the last_heartbeat.
This is only partly related to this BZ:  https://bugzilla.redhat.com/show_bug.cgi?id=1395736.
This PR doesn't resolve that BZ.  I'll let @gtanzillo @Fryguy decide if we need euwe/yes on this or if a new BZ is needed...
EDIT:
https://bugzilla.redhat.com/show_bug.cgi?id=1415290
Please review commit by commit.

Ok, @Fryguy updated to remove the nil check after running the server locally.  I added it since many other areas checked for a nil sync/mutex but in this case, it's completely not needed since we call setup_drb_variables as part of the server boot.
app/models/miq_server/worker_management.rb-  def setup_drb_variables
app/models/miq_server/worker_management.rb:    @workers_lock        = Sync.new
app/models/miq_server/worker_management.rb-    @workers             = {}
app/models/miq_server/worker_management.rb-
app/models/miq_server/worker_management.rb-    @queue_messages_lock = Sync.new
app/models/miq_server/worker_management.rb-    @queue_messages      = {}
app/models/miq_server/worker_management.rb-  end

@jrafanie Since this PR only partially fixes a BZ... can you please create a new BZ for the part that's fixed in this PR?

ok, @simaishi I opened https://bugzilla.redhat.com/show_bug.cgi?id=1415290 for this issue.  I also updated the description of this PR.

Euwe backport details:
$ git log -1
commit 6814026a233df44b8f194869d059ee078236a0fa
Author: Jason Frey<EMAIL_ADDRESS>Date:   Sat Dec 10 23:30:32 2016 -0500

    Merge pull request #12932 from jrafanie/wrap_critical_section_with_read_lock

    Worker heartbeating: Wrap critical section with read lock
    (cherry picked from commit bb18704733652ab3c38c3c1d3e21e886f07d381a)

    https://bugzilla.redhat.com/show_bug.cgi?id=1415332


Identify floating windows in ShareX

This is an attempt to allow floating windows, with the existing ShareX entry

[X] I have formatted applications.yaml with komorebic fmt-asc.

Sorry I thought it was checking the identifier for the app and then the float identifiers, so didn't expect this. I'll close this for now, but use it myself.


Update ca-certificates before travis build

This should fix the travis build because html-proofer should then be able to access all URLs.

It doesn't look good. I will replace html-proofer with jekyll-test which should fix the build.


BitView.buffer is no longer changed as BitView._view changes

node v0.10 has changed the behaviour when creating a Uint8Array with a Buffer. It no longer shares the reference, but clones the buffer. That means any changes made with writeBits is not reflect in the buffer property.

Any chance of merging this please?

Heh, yep, just flipped through the cracks.


How to reverse the process, so that matching results are shown after being hidden

Currently, the filter works by hiding list items that do not match the search query. However, I would like the filter to work by not showing any results until text is added.
I can't figure out how to do this - could somebody work it out?
Thank you.

I've modified the script to have 2 additional options which would solve your needs in #29
jsFiddle based on the author's demo code: https://jsfiddle.net/r60mqt7s/2/


Add support for the new URLSession async/await APIs

Simple integration using URLSessionProxyDelegate on iOS 16.0 is creating the request in logs, but they are stuck "Pending". I did a little bit of debugging and it seems urlSession(_:task:didCompleteWithError:) isn't being called by the system.
Reproduction
import SwiftUI
import Pulse
import PulseUI

struct API {
    let session: URLSession = {
        let config = URLSessionConfiguration.default
        let delegate = URLSessionProxyDelegate()
        return URLSession(configuration: config, delegate: delegate, delegateQueue: nil)
    }()

    func fetchTodos() async throws -> Data {
        let url = URL(string: "https://jsonplaceholder.typicode.com/todos/1")!
        let (data, _) = try await session.data(from: url)
        return data
    }
}

struct ContentView: View {
    let api = API()

    @State var isLoading = false
    @State var data: Data?

    @State var showPulse = false

    var body: some View {
        VStack {
            if let data {
                Text("\(data.count) bytes of data")
            } else if isLoading {
                ProgressView("Loading...")
            } else {
                Text("No data")
            }

            Button("Fetch Todos", action: fetchTodos).buttonStyle(.borderedProminent)

            Button("Show PulseUI", action: { showPulse = true }).buttonStyle(.bordered)
        }
        .sheet(isPresented: $showPulse, content: {
            PulseUI.MainView()
        })
        .padding()
    }

    func fetchTodos() {
        isLoading = true
        Task {
            self.data = try? await api.fetchTodos()
            isLoading = false
        }
    }
}

I'm pretty sure it used to work in the previous versions, but yes, I just tested it, and the new async/await APIs on URLSession such as data(for:) are not supported. The issue is that almost none of the delegate methods get called for tasks created using these methods. Crucially, urlSession(_:task:didCompleteWithError:) doesn't.

I thought that might be the case so I tried to work around it with the following but it runs into the same issue, which makes me think the issue is more related to the new concurrency system then URLSession's concurrency methods themselves.
func fetchTodos() async throws -> Data {
    let url = URL(string: "https://jsonplaceholder.typicode.com/todos/1")!

    // let (data, _) = try await session.data(from: url)
    // return data
    return try await withCheckedThrowingContinuation { continuation in
        let task = session.dataTask(with: URLRequest(url: url)) { data, _, error in
            if let error {
                continuation.resume(throwing: error)
                return
            }
            continuation.resume(returning: data ?? Data())
        }
        task.resume()
    }
}

+1

@vdka , the completion-based methods also don't call the delegate. There is probably a way to swizzle some of the URLSession method to make it work automatically.

I believe we have to use URLSessionTaskDelegate in order to get the call back. Some people are discussing the issue here: https://www.reddit.com/r/swift/comments/ptpxf7/swift_55_async_await_issue_with_delegates_using/

The same "pending" issue appears if you use Combine dataTaskPublisher. It seems like dataTaskPublisher doesn't invoke the delegate methods both for URLSessionTaskDelegate and URLSessionDataDelegate. Maybe someone also have this issue?

I'd love to make a PR to fix this, however I am not likely to get the time. If anybody is interested in looking into this, I know ProxymanApp/Atlantis appears to be unaffected. It appears to Swizzle internal Method's and so AppReview would likely not approve, however, could be offered as an option similar to the existing Experimental integration approach

You can use Method Swizzling technique to swizzle certain functions of NSURLSession to capture HTTP/HTTPS traffic on the fly.
Check Atlantis
https://github.com/ProxymanApp/atlantis/blob/main/Sources/NetworkInjector.swift
https://github.com/ProxymanApp/atlantis/blob/main/Sources/NetworkInjector%2BURLSession.swift

I'm assuming the URLSession.DataTaskPublisher internally uses the completionHandler based dataTask method. Apple's Docs state that if a completionHandler is set, the delegate methods will not be called.

For the completion handler case, is it possible to tell the pulse logger after the completion block is called that the request is complete?

Hi @kean
I've exactly the same problem with "new" Swift concurrency URLSession as requests are always shown as "Pending..." when they are done like this:
let (data, _) = try await session.data(from: url)

As this is not possible/acceptable for our iOS team to modify all requests in another way than modern Swift concurrency try await session.data(from:), do you think that any fixes/refacto could be done in Pulse about this in a futur version (v3 ?) of your great and so useful tool ?
Thanks for your answer and again: Big up for all your work 👏
Have a nice day
Jeremie

Just adding my two experience here: if you're using URLSession.dataTaskPublisher, you can replace it with this extension and you'll at least get network call logs (no metrics, though).
It relies on creating a fake dataTask and then subscribing to events of the dataTaskPublisher, as the publisher itself doesn't expose its dataTask instance.
extension URLSession {
  func trackedDataRequest(for urlRequest: URLRequest, with networkLogger: NetworkLogger) -> AnyPublisher<DataTaskPublisher.Output, DataTaskPublisher.Failure> {
    let dataTask = dataTask(with: urlRequest)

    return dataTaskPublisher(for: urlRequest)
      .handleEvents(
        receiveSubscription: { _ in
          networkLogger.logTaskCreated(dataTask)
        },
        receiveOutput: { output in
          networkLogger.logDataTask(dataTask, didReceive: output.data)
        },
        receiveCompletion: { completion in
          switch completion {
          case .finished:
            networkLogger.logTask(dataTask, didCompleteWithError: nil)
          case let .failure(error):
            networkLogger.logTask(dataTask, didCompleteWithError: error)
          }
        }
      )
      .eraseToAnyPublisher()
  }
}

For me, solution was to transform codebase to use URLSessionProtocol  protocol. It used by default in API generated by openapi-generator
public protocol URLSessionProtocol {
    func dataTask(with request: URLRequest, completionHandler: @escaping @Sendable (Data?, URLResponse?, Error?) -> Void) -> URLSessionDataTask
}

Then, Pulse can be easily integrated:
class URLSessionPulse: URLSessionProtocol {
    let session: URLSession
    let networkLogger: NetworkLogger

    init(session: URLSession) {
        self.session = session
        self.networkLogger = NetworkLogger()
    }

    func dataTask(with request: URLRequest, completionHandler: @escaping @Sendable (Data?, URLResponse?, Error?) -> Void) -> URLSessionDataTask {
        var task: URLSessionDataTask?
        let onReceive: (Data?, URLResponse?, Error?) -> Void = { (data, response, error) in
            if let task {
                if let data {
                    self.networkLogger.logDataTask(task, didReceive: data)
                }
                self.networkLogger.logTask(task, didCompleteWithError: error)
            }
        }

        task = session.dataTask(with: request) {data, response, error in
            onReceive(data, response, error)
            completionHandler(data, response, error)
        }
        if let task {
            self.networkLogger.logTaskCreated(task)
        }
        return task!
    }
}

According to docs, if you're specifying completion handler (use async version that uses it under the hood or use dataTaskPublished that uses completion handler as well) it will ignore data delegate note section of docs. I wonder how it worked before?

For me, solution was to transform codebase to use URLSessionProtocol protocol. It used by default in API generated by openapi-generator, and URLSession conforms to it, so Pulse can be easily removed in production
public protocol URLSessionProtocol {
    func dataTask(with request: URLRequest, completionHandler: @escaping @Sendable (Data?, URLResponse?, Error?) -> Void) -> URLSessionDataTask
}

Then, Pulse can be easily integrated:
class URLSessionPulse: URLSessionProtocol {
    let session: URLSession
    let networkLogger: NetworkLogger

    init(session: URLSession) {
        self.session = session
        self.networkLogger = NetworkLogger()
    }

    func dataTask(with request: URLRequest, completionHandler: @escaping @Sendable (Data?, URLResponse?, Error?) -> Void) -> URLSessionDataTask {
        var task: URLSessionDataTask?
        let onReceive: (Data?, URLResponse?, Error?) -> Void = { (data, response, error) in
            if let task {
                if let data {
                    self.networkLogger.logDataTask(task, didReceive: data)
                }
                self.networkLogger.logTask(task, didCompleteWithError: error)
            }
        }

        task = session.dataTask(with: request) {data, response, error in
            onReceive(data, response, error)
            completionHandler(data, response, error)
        }
        if let task {
            self.networkLogger.logTaskCreated(task)
        }
        return task!
    }
}

More generic solution that uses URLSessionDataDelegate and checks cancellation that worked for me.
extension URLSession {     /// Allows to track URLSessionDataDelegateusing closure based call.     /// By default if you use async interface orcompletionHandlerbased interface,     /// URLSession won't notifyURLSessionDataDelegate`.
public func dataTask(for request: URLRequest) async throws -> (Data, URLResponse) {
var dataTask: URLSessionDataTask?
    let onSuccess: (Data, URLResponse) -> Void = { (data, response) in
        guard let dataTask, let dataDelegate = self.delegate as? URLSessionDataDelegate else {
            return
        }
        dataDelegate.urlSession?(self, dataTask: dataTask, didReceive: data)
        dataDelegate.urlSession?(self, task: dataTask, didCompleteWithError: nil)
    }
    let onError: (Error) -> Void = { error in
        guard let dataTask, let dataDelegate = self.delegate as? URLSessionDataDelegate else {
            return
        }
        dataDelegate.urlSession?(self, task: dataTask, didCompleteWithError: error)

    }
    let onCancel = {
        dataTask?.cancel()
    }

    return try await withTaskCancellationHandler(operation: {
        try await withCheckedThrowingContinuation { continuation in
            dataTask = self.dataTask(with: request) { data, response, error in
                guard let data = data, let response = response else {
                    let error = error ?? URLError(.badServerResponse)
                    onError(error)
                    return continuation.resume(throwing: error)
                }
                onSuccess(data, response)
                continuation.resume(returning: (data, response))
            }
            dataTask?.resume()
        }
    }, onCancel: {
        onCancel()
    })
}

}`

@salmin-skelia where delegate is used? can you show all code please?

@salmin-skelia where delegate (URLSessionDataDelegate) is used? can you show all code please?

What do you mean by where? You just pass URLSessionDataDelegate as delegate for your session like URLSession(configuration: sessionConfiguration, delegate: sessionDelegate, delegateQueue: nil) and sessionDelegate using snipped I liked will receive appropriate action if sessionDelegate will conform URLSessionDataDelegate.

Hey, folks. Thanks for engaging in this issue and suggesting the solutions!
Pulse was originally designed back in 2020 for delegate-based URLSession instances, but I recognize that these are less prevalent now. I'm going to address it with the following changes in the upcoming Pulse 5.0 release.
1. Swizzling
Pulse will now offer swizzling inspired by https://github.com/ProxymanApp/atlantis suggested by @vdka. You'll be able to enable it with one line of code:
NetworkLogger.enableProxy()`.

It will be added to a separate PulseProxy library to eliminate the risk of app review rejection for folks who do not use it.
2. URLSessionProtocol
PulseProxy cannot be a complete solution because, unlike Atlantis, the goal of Pulse is to provide not just logging but also debugging capabilities such as mocking, breakpoints, and rewriting without the need for an HTTP proxy.  To address it, I will follow @alexdremov's suggestion and add a URLSessionProtocol type to its Pulse-specific implementation that will power all its features.
let session: URLSessionProtocol
#if DEBUG
session = NetworkLogger.URLSession(configuration: .default)
#else
session = URLSession(configuration: .default)
#endif

NetworkLogger.URLSession  supports URLSession convenience closure-based APIs, async/await APIs, and I'm currently working on the Combine support. It uses a delegate-based approach similar to what @lukeredpath suggested.
This is the optimal solution because it doesn't rely on Objective-C runtime and opens more possibilities in the future to add more debugging features to NetworkLogger.URLSession that are impossible to add in any other way.

so Pulse can be easily removed in production

It is an important point, and in both cases it will be relatively easy to disable Pulse in production or eliminate it completely using #if canImport(Pulse).
3. URLSessionProxyDelegate
The existing URLSessionProxyDelegate is used internally by NetworkLogger.URLSession and will continue to be available as a way to enable logging for Alamofire or other framework that use delegate-based URLSession setup and where you can't access the underlying URLSession instances.

Swift made implementing these things quite a bit harder, and the integration will have too many choices, but that seems to be the only way. It will continue to be modular enough to accommodate almost any system. Once you set it up once, you generally won't have to think about it again.
The suggested changes are available in the following PR: https://github.com/kean/Pulse/pull/285. I'm open to suggestions, especially about the API design.

The PR (https://github.com/kean/Pulse/pull/285) is largely complete except for a few methods. I would appreciate if someone could take it for a spin in their project and see how well it works.

The changes shipped in Pulse 5.0.


Clarify license owner

I assume this should be something like:
Copyright 2017 Sam Thorogood

I don't speak legal-ish, but I'd guess that you'd better make the change, not me.

Classically the LICENSE file in repos isn't changed, e.g., in my old life: https://github.com/GoogleChrome/web.dev/blob/main/LICENSE
It's just when you apply it to a file/header.

Ah! Ok, I guess that kinda makes sense. It was just odd to see that the main LICENSE file didn't have a name attached to that copyright notice. Thanks for clearing that up!


runtime: else on if

(if (= a 'good)     ; if a is equal to "good"
  (print 'good)     ; print "good"
  (else             ; otherwise
    (print 'bad)))  ; print "bad"

I think I prefer it now, that is:
(if (= a 'good) (print 'good) (print 'bad))

that is, if there is a third argument in the fi it is the else
this also solves the else if

another example:
(if (= a 'good)
	(print 'good)
	(if (= 'bad)
		(print 'bad)
		(print 'ugly)))

I believe we can close this issue, the current mode of if ... else is more lisp like
same with issue #20
(let a "good")
(if (== a "good")
    (print "good")
    (if (== a "bad")
       (print "bad")
       (print "ugly")))


Can not install nexe

I got this error while I was trying to install nexe via this command npm install nexe -g.
npm ERR! Linux 3.19.0-41-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "nexe" "-g"
npm ERR! node v5.5.0
npm ERR! npm  v3.3.12
npm ERR! path /usr/lib/node_modules/nexe/bin/nexe
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/lib/node_modules/nexe/bin/nexe'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR!     /home/project/npm-debug.log

Same error on Mac OS X El Capitan.

This may be an issue with npm. I'll look into it right now.

Reproduced on Linux. Interesting.

Fixed by<EMAIL_ADDRESS>(3f997ca it would seem)
For some reason npm wasn't including bin/nexe.


Add templating example using Swig and YAML frontmatter

I was at a lack of documentation when trying to setup YAML front matter + templating for gulp. Here's a simple recipe for setting up gulp with YAML front matter and swig.

gulp-data isn't needed if you set gulp-front-matter option to property: 'data'.

Due to a bunch of unfortunate, but necessary rebases, this is out of sync.  Can you rebase your changes on the new master?  Thanks.

Rebased and cleaned up the example a bit more.
Should be clean to be upstreamed -- let me know anything else standing in the way.


Report issue suggestion

Just an idea (which might not make sense to mix it with compiler) that it would be nice (being in Terminal) to be able to type tsc -i or tsc --issue which could open github new issue with all the details of TS version populated (not sure if node version and os info is important for you but would be easy to add).
Kind of similar how vscode allows to click "Report issue" and it opens github with template and all variables populated.

As you can tell by the nearly three year lag time here, an easier way to create more issues is the last thing we need 🙃


Use rasters with a different extent - problem with Float32 tifs

Expected behaviour: if there is a NoData in any input raster for a given pixel, the output should be NoData
This works (nodata in any input raster gives nodata in output)
standard_path = "../testcase/zwarte_beek/input/"
simple = nv.Niche()
simple.set_input("mhw", standard_path + "mhw.asc")
simple.set_input("mlw", standard_path + "mlw.asc")
simple.set_input("soil_code", standard_path + "soil_smallerextent.tif") #Signed integer 32 bit with NoData = -2147483647
simple.run(strict_checks=False, full_model=False)
simple

ax = simple.plot(14)

This doesn't work (NoData in soil map becomes no potential)
standard_path = "../testcase/zwarte_beek/input/"
simple = nv.Niche()
simple.set_input("mhw", standard_path + "mhw.asc")
simple.set_input("mlw", standard_path  + "mlw.asc")
simple.set_input("soil_code", standard_path + "soil_smallerextent_float.tif") #Float32
simple.run(strict_checks=False, full_model=False)
simple

ax = simple.plot(14)

soil_smallerextent.zip
Is there something we can do about it? Or should we add a warning (avoid Float), at least in the documentation?

FYI: for most of the input layers, we should be able to work with Int format. Seepage and nitrogen_atmospheric are layers that as Float could come

I can not reproduce this locally. Can you show which versions of rasterio and gdal you use. If you just type simple after running the code above, this should be reported. Eg:
# Niche Vlaanderen version: 1.2b1
# Newer niche_vlaanderen  1.2b2 available
# Run at: 2023-03-08 12:40:22.688925

package_versions:
  pandas: 1.4.0
  numpy: 1.22.1
  rasterio: 1.3.4
  gdal: 3.5.3
  python: '3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110]'

model_options:
  deviation: false
  full_model: false
  name: ''
  strict_checks: false

model_properties:
  model_extent: ((216590.0, 198380.0), (216905.0, 198170.0))

input_layers:
  mhw: ../testcase/zwarte_beek/input/mhw.asc
  mlw: ../testcase/zwarte_beek/input/mlw.asc
  soil_code: ../testcase/zwarte_beek/input/soil_smallerextent.tif
  # Model run completed

Running conda list in my niche environment gives me this:
gdal                      3.5.2            py39h34c8707_1    conda-forge
rasterio                  1.3.2            py39h223f425_0    conda-forge

Some additional testing on windows show the error. No data is correctly parsed on the input layer, but not after calculations.

Fixed by https://github.com/inbo/niche_vlaanderen/pull/371


How to distribute a Golang library/SDK without disclosing source code?

What version of Go are you using (go version)?

$ go version
go version go1.16.5 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="linux"

What did you do?
  A Go program that imports one or more of those Go packages may be linked against this shared library.
...
This mode is mainly intended to support distro builders."

However, I could not find any details on how to make it work.
What did you expect to see?
Our company is building a Golang library that we want to distribute to other companies (customers), who are then expected to use it in their Golang executables. There is no involvement of Cgo or C-based programs / libraries. Our source code is not intended to be open-sourced, nor do we want our customers to view it. I understand they can decompile and see the code if they want, but at least we don't want to give them the plaintext source code files.
What is the recommended way to do this using Golang? I could not find any working solution so far after searching a lot.
What did you see instead?
Nothing so far. If sharing our source code with customers is the only way to do this, we may want to investigate source code obfuscation options.

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions


Add Sensu to list with company profile

This is a modified version of the Contributing Guidelines.
This pull request adheres to the repository's Code of Conduct

[x] This PR contains housekeeping (URL edits, copy changes etc)
[X] You know your alphabet - company is listed in alphabetical order in the README
[X] A company profile is included - Not essential but it really helps!
[X] The company directly hires employees - This may sounds odd but while awesome, this list is not for coding bootcamps, "teaching" positions a network (Teacher positions employed directly, such as Treehouse, are allowed), or networking sites for listing a CV looking for gigs
[X] The company added hires remote employees, or positions are available to remote workers and are clearly illustrated as such
[X] A company-profile has been included for each addition to the list
[X] I am an employee of the company mentioned and confirm all details are correct
[X] Remote status has details regarding how the culture includes remote employees, how the company integrated remote workers, etc
[X] Region details any restrictions to applicants based on geography
[X] How to apply details the best approach for new applications, link to open positions, and any other help available for job hunters
[x] Any missing parts from the profile, please use <Unknown> to allow for future completion

I wasn't sure about the first and last entries in the checklist as these don't seem to pertain to this PR. So I checked them anyway, because it seems complete.

@DamianFekete Fixed. Thanks!

@grepory I might edit the template, not all checkboxes are required 👍
Thanks for the PR!

Thanks!


Add standard programming commands

Hi, I wonder if there's any interest in incorporating this pattern of a standard programming command interface.
This idea is taken from Caster. It defines a common set of programming commands for languages to implement. I think it makes it more straightforward to start adding a new language, and makes it easier to switch between languages as a user.
I added a JavaScript implementation and adapted the existing Python one. When adapting the Python file, I attempted to keep any commands that weren't covered by the standard ones. I did not change Go because it makes use of dictation.
More commands, (or even dictation commands, like the Go implementation?), could be added.
Thanks, I appreciate the amount of work that goes into this repository.

Thanks, this is the direction I intend to move. I've got something very similar in a different branch (https://github.com/knausj85/knausj_talon/tree/generic-language-grammar). I'll take a look, and take the best of both worlds.

Closing this out since I've merged our approaches and committed


Docs Incorrect & Don't Refer to this Repository

What is the current behavior?
The docs for captioning refer to some non-existent API on the Python SDK.
https://developers.deepgram.com/docs/automatically-generating-webvtt-and-srt-captions

Hi @rawkode
Thanks for pointing this out. I will update the link you have provided with the correct info. This repo is definitely the source for getting captions on python.


Fail to run Azure Storage Spring Boot Starter Sample on Windows Server 2008R2

Environment

Spring boot starter:

storage spring boot starter

OS Type:

Windows

Java version:

1.8

Summary
As part of one of our projects, we would like to have a cloud storage to upload files and share them between our teams. So, we opened an account to Azure and tried an investigation how Azure Storage could cover our requirements. As a first step, we chose to run Azure Storage Spring Boot Starter Sample on our servers. Despite the respective sample application was executed successfully on our development PCs (i.e., Windows 7 Professional) when we tried the same on our Windows servers (i.e., Windows Server 2008R2 were installed as OS) we got an IOException that remote host closed the connection.
Reproduce steps

We packaged sample using Maven following the respective instructions (i.e., https://github.com/Microsoft/azure-spring-boot/tree/master/azure-spring-boot-samples/azure-storage-spring-boot-sample) on Windows 7 dev PC.
We run the sample on dev PC using the following command:
java -jar target/azure-storage-spring-boot-sample-0.0.1-SNAPSHOT.jar
Sample was executed successfully creating a container and uploading the sample file on our Storage account
JAR file copied to Windows server and executed using the aforementioned command
Execution failed with the following error:
java.io.IOException: An existing connection was forcibly closed by the remote host

Expected Results

No exception to be observed while a new container to be created and the sample file to be uploaded on our Azure Storage Account.
Actual Results

Please see below the log of the execution failed:
2019-02-28 09:01:34.160  INFO 25044 --- [           main] sample.storage.StorageSampleApplication  : Starting StorageSampleApplication v0.0.1-SNAPSHOT on DBTPA05P with PID 25044 (C:\Users\uoclo\Documents\azure-storage-spring-boot-sample-0.0.1-SNAPSHOT.jar started by uoclo in C:\Users\uoclo\Documents)
2019-02-28 09:01:34.169  INFO 25044 --- [           main] sample.storage.StorageSampleApplication  : No active profile set, falling back to default profiles: default
2019-02-28 09:01:57.848  INFO 25044 --- [           main] sample.storage.StorageSampleApplication  : Started StorageSampleApplication in 24.587 seconds (JVM running for 25.794)
Start creating container azure-storage-sample...
2019-02-28 09:04:00.993  INFO 25044 --- [           main] ConditionEvaluationReportLoggingListener :
Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2019-02-28 09:04:01.005 ERROR 25044 --- [           main] o.s.boot.SpringApplication               : Application run failed
java.lang.IllegalStateException: Failed to execute CommandLineRunner
at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:816) [spring-boot-2.1.2.RELEASE.jar!/:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.callRunners(SpringApplication.java:797) [spring-boot-2.1.2.RELEASE.jar!/:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:324) [spring-boot-2.1.2.RELEASE.jar!/:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1260) [spring-boot-2.1.2.RELEASE.jar!/:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1248) [spring-boot-2.1.2.RELEASE.jar!/:2.1.2.RELEASE]
at sample.storage.StorageSampleApplication.main(StorageSampleApplication.java:42) [classes!/:0.0.1-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_201]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_201]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_201]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_201]
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48) [azure-storage-spring-boot-sample-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT]
at org.springframework.boot.loader.Launcher.launch(Launcher.java:87) [azure-storage-spring-boot-sample-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT]
at org.springframework.boot.loader.Launcher.launch(Launcher.java:50) [azure-storage-spring-boot-sample-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT]
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51) [azure-storage-spring-boot-sample-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT]
Caused by: java.lang.RuntimeException: java.io.IOException: An existing connection was forcibly closed by the remote host
at io.reactivex.internal.util.ExceptionHelper.wrapOrThrow(ExceptionHelper.java:46) ~[rxjava-2.2.5.jar!/:na]
at io.reactivex.internal.observers.BlockingMultiObserver.blockingGet(BlockingMultiObserver.java:93) ~[rxjava-2.2.5.jar!/:na]
at io.reactivex.Single.blockingGet(Single.java:2807) ~[rxjava-2.2.5.jar!/:na]
at sample.storage.StorageService.createContainer(StorageService.java:69) ~[classes!/:0.0.1-SNAPSHOT]
at sample.storage.StorageSampleApplication.run(StorageSampleApplication.java:49) [classes!/:0.0.1-SNAPSHOT]
at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:813) [spring-boot-2.1.2.RELEASE.jar!/:2.1.2.RELEASE]
... 13 common frames omitted
Caused by: java.io.IOException: An existing connection was forcibly closed by the remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method) ~[na:1.8.0_201]
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43) ~[na:1.8.0_201]
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[na:1.8.0_201]
at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[na:1.8.0_201]
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) ~[na:1.8.0_201]
at io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:288) ~[netty-buffer-4.1.31.Final.jar!/:4.1.31.Final]
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) ~[netty-buffer-4.1.31.Final.jar!/:4.1.31.Final]
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:347) ~[netty-transport-4.1.31.Final.jar!/:4.1.31.Final]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148) ~[netty-transport-4.1.31.Final.jar!/:4.1.31.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:648) ~[netty-transport-4.1.31.Final.jar!/:4.1.31.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:583) ~[netty-transport-4.1.31.Final.jar!/:4.1.31.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:500) ~[netty-transport-4.1.31.Final.jar!/:4.1.31.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:462) ~[netty-transport-4.1.31.Final.jar!/:4.1.31.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:897) ~[netty-common-4.1.31.Final.jar!/:4.1.31.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.31.Final.jar!/:4.1.31.Final]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_201]

@kpapadopoul
Thanks for your issue. It looks the same jar works well but got some network issue from windows server 2008R2, right ? If so it seems that due to network issue instead of jar itself. We may need to prepare env to try to reproduce your issue. It may take some time indeed, or you may can provide one env for this if urgent.

@Incarnation-p-lee
We tried remote debugging on Windows Server from our development PCs and we observed that our application performed HTTP access (i.e,, when executing PUT request that used by Azure SDK to create a container) instead of HTTPS (as should be based on Azure Storage configuration) when executed on Windows Servers. On the contrary, the latter didn't happen when our application is executed on development PCs. Trying to step-by-step debugging Azure SDK behavior, we found that there is a configuration property of the respective Spring Boot Starter to enable HTTPS explicitly. After enabling HTTPS, problem was solved. As a proposal, I think the aforementioned property (i.e., azure.storage.enable-https) and its effect should be referred to the README of the azure-storage-spring-boot-starter (i.e., https://github.com/Microsoft/azure-spring-boot/blob/master/azure-spring-boot-starters/azure-storage-spring-boot-starter/README.md) to avoid such issues to the future.
Thanks for your support.

Hi @kpapadopoul , thanks for your trying. We are retiring this starter, please check new repo azure-spring-boot-sample-storage-blob, I check the default propertiy item azure.storage.enable-https=true, maybe need to emphasize this setting in readme. Now we will close this issue.


Include user.id on session

I feel like I see this particular issue come up in the discord at least a few times a week, and it's always bothered me.
Should be as simple as:
// in [...nextAuth].ts
callbacks: {
  async session({ session, user }) {
    session.user.id = user.id;
    return Promise.resolve(session);
  },
}

// in a random next-auth.d.ts
declare module "next-auth" {
  /**
   * Returned by `useSession`, `getSession` and received as a prop on the `Provider` React Context
   */
  interface Session {
    userId: string;
  }
}

Ideally NextAuthJS would include this 😅 hoping us including it can work as a forcing function for them to get on it

Cut an issue on NextAuthJS because this should be fixed there IMO
https://github.com/nextauthjs/next-auth/issues/4903

Unhappy w/ response on NextAuth side, let's do this here instead

Hey I can pick this up @TheoBr

Yeah, that happened by mistake LoL @nexxeln

@bhatvikrant looks correct to me


The get and set commands are very repetitive

The get and set commands are very repetitive.
from line 138 to 234 of cpu is really repetitive.

Use a macro

I'll test these in the morning tomorrow. We should definitely get some sort of testing. #78


Changed the feature

Closes #1
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


New package: DimisAIO.DindeGDPS version 3.0B

[ ] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/110836&drop=dogfoodAlpha

[Policy] Needs-Author-Feedback
CLA needs to be signed.


relates to #944: property for collecting path params as tags in the h…

Added the stargate.metrics.http_server_requests_path_param_tags property option to declare what path params should be taken into account and use them as the tags in the http_server_resuests. Examples:

~stargate.metrics.http_server_requests_path_param_tags=*~ - can not be supported, produces diff amount of tags every time
stargate.metrics.http_server_requests_path_param_tags=keyspaceName,collection - only path params that are matching keyspaceName or collection.

This is a global option and affects all endpoints.

Was lucky enough to get INT test to fail due to the different amount of tags in the same process.. Moved to a fixed amount of tags.


It's here
https://github.com/hannob/ctgrab/blob/master/ctgrab