support theartistunion.com

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
Supports https://theartistunion.com, which seems to be a marketing site for artists. I created this extractor because otherwise you have to sign in with Spotify and provide your email address and Spotify playlists to the artist in order to even download from them.

Will review it the following days :)

lol that's hilarious
i wrote this extractor because the site was shitty and locked downloads to people who connect their spotify account anyway, so i'm glad it's down i guess


fix: Error bad centralized. Issues  Fixed #23

Before

After

css correction and remove padding
.error-icon svg{
padding-left: 1px;

Thank you for your contribution😊

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Tests failing after changing the Test Log Level

Hi
So I was attempting to adjust the Test Log Level, by changing test/resources/log4j.properties, because it is currently set as INFO, thus producing a ton of log, but, to my surprise, it resulted a couple of test failures:
Tests in error:
  CacheTest.shouldGenerateJSONFromQueryCache:221 » IndexOutOfBounds Index: 0, Si...
  PartitionIDSpec.shouldIncludePartitionColumnsIntoUPDATEAndDELETE:27 » IllegalArgument
  JsonLog4jLayoutSpec.shouldClearLogValues:158->getLastLine:83 » ArrayIndexOutOfBounds
  JsonLog4jLayoutSpec.shouldLogJson:63 » Test Test object:
java.lang.Integer == ...
  JsonLog4jLayoutSpec.shouldPrintJsonLogValuesAndParams:94->getLastLine:83 » ArrayIndexOutOfBounds
  JsonLog4jLayoutSpec.shouldPrintJsonWithoutParams:123->getLastLine:83 » ArrayIndexOutOfBounds
  JsonLog4jLayoutSpec.shouldPrintJsonWithoutParamsAndLogValues:143->getLastLine:83 » ArrayIndexOutOfBounds

I wonder if it is really necessary for these tests to access the logging output, or if they could be changed somehow so the log level wouldn't have impact their success.
Thanks

If this is too trouble to fix, I've come with a functioning workaround by doing:
mvn ... | grep -v "{\"level\":\"INFO\""

no, the tests should log all this stuff, as it is mostly [JsonLog4jLayout](https://github.com/javalite/activejdbc/blob/dadffbc1f66487bd85a5296896e3b83ad34bace7/javalite-common/src/main/java/org/javalite/logging/JsonLog4jLayout.java) that we are testing.

closing as non-issue


Implement sanitizing and storing API key.

The features are functional, but need to be connected to the Menu options, so they run when the user presses the buttons.
Demonstration of their functionality can be made via direct calls in the console, while on the index.html page.
Then, upon navigating to the drive.html, one will see an error message for invalid api keys before being returned to the main menu, or the api is valid and the game loads as expected.


Create home static part

Create home static part

When mouseover, block should be green. Now no effect
https://gyazo.com/bc4247eee5a81e0f3165a721c7531ca1
Font's style was ugly and size was too small, did you check the font with design?
Responsive lose border on Chrome OS X, and boxes seem messed, could you make it better?
https://gyazo.com/541487b64e24ec584355edfade8c4c0a


Set Telegraf hostname from enviromental variable

Seems like influxdb v2 load-data/telegrafs currently creates configs like the following:
  hostname = ""
  omit_hostname = false

When using such a config in a telegraf docker container, it takes on the hostname of the container and not the docker host.
This can obviously be undesirable when it is used as the telegraf instance for the host.
I imagine that by setting it to something like "$TELEGRAF_HOSTNAME" this could easily be solved, while retaining the existing behavior if the env var is unset?

@qm3ster thanks! You can download the config and make those changes. You can use the API to update that config in the system: https://v2.docs.influxdata.com/v2.0/api/#operation/PutTelegrafsID
Or better yet, use the influxdb cli pkg command to export the Telegraf config as a manifest, make the changes, and use influx pkg -f path/to/file.yml to load it back into the system.  https://v2.docs.influxdata.com/v2.0/influxdb-templates/create/

I did
docker exec influxdb influx pkg export --telegraf-configs 05656e888c6f2000 > temp.yml
code -w temp.yaml
docker exec -i influxdb influx pkg -o daid  < temp.yml
rm temp.yml

Wherein I obtained 05656e888c6f2000 from Setup Instructions in the UI.
This created an updated Telegraf besides the original one, with a different ID.
Shouldn't I want to update the same ID, so that daemons can reload it on restart?


verifyWebhook seems not to work properly

Hi, as shown here we want to validate the incoming content from the webhook.
This is the code that we are using:
class GetStreamValidator implements SignatureValidator
{
    public function __construct(
        protected GetStreamService $getStreamService,
    ) {}

    public function isValid(Request $request, WebhookConfig $config): bool
    {
        $signature = $request->header('X-Signature');

        $body = json_encode($request->all());

        return $this->getStreamService->verifyWebhook($body, $signature);
    }
}

With our getStreamService->verifyWebhook just passing the parameters through to your method :
class GetStreamService
{
    public function __construct(
        protected Client $client,
    ) {}

    // ...

  public function verifyWebhook(string $requestBody, string $signature): bool
    {
        return $this->client->verifyWebhook($requestBody, $signature);
    }
}

The odd thing is now, that this function always returns false even though we're using the actual request that we receive after we wrote something in our chat. This is the actual request that we receive to the url that we configured here:

I don't know if this is important but we enabled teams for our application. We're using version 3.3.0 of this package in a laravel application.
We don't know what we're doing wrong. I tripple checked our key and secret, to ensure that they are correct. But the given signature in the request from above seems not to match with the given body.
Can you help us on this one please?

Hey @tfs-guy, this is just a guess but the line $body = json_encode($request->all()); seems suspect. In order for the signatures to match the request body string needs to be identical (as in byte-for-byte) to the request body. Could $request->all() or json_encode change the body in some way like the order of the keys or something?

Hey @JimmyPettersson85 thanks for your fast response.
I also tried using $request->getContent() as suggested here. Both are not working.
I also just tried to copy the body directly from the body of our request (logged via telescope) like this:

But this also fails... even though it looks pretty much the same as it is shown here.

hey @tfs-guy
I've gotten it to work locally so I dont think there's something wrong with how the signature checking works. The body in your example seems to contain newlines (\n) which the raw response doesn't. As for $request->getContent() I cant really say as I'm not familiar with that.

Hey @JimmyPettersson85 ,
thank you, there were escape signs that shouldn't have been there.
But in your example it looks like  you used the apiSecret to verify. In the code from the package it uses the apiKey:

If I change this in my vendor folder to apiSecret it works. Otherwise even without any newlines or escape chars it still returns false. So it seems like a bug in the verifyWebhook method?

No wait sorry. I just checked the code in this repository and it clearly says apiSecret. Don't know where the apiKey in my vendor folder comes from.
Thank you very much for your help :)


This package is not working at all in android and ios in proudction and in testflight

Useless package.

Could you kindly write detailed description how it is not working?
There are many users using this modules. It'd be great if you can be more helpful.
We are all spending our free time.
Feel free to reopen when you think you can share more details.


Brushup Barbarian Rage automation

Still need to be able to add reach to strikes

Still need to be able to add reach to strikes

You can add reach to strikes. What's the use case?

Animal instinct's specialization ability The frog's tongue attack and deer's antler attack gain reach 10 feet


Create Gradle plugin for FMUs

Create a plugin which automatically generates source code for an FMU
A FMU named "ControlledTemperature.fmu" which is located in src/main/fmu" will have a class file ControlledTemperature.kt with named getters and setter for all variables.
This is similar to Fmu2Jar expect that it will be MUCH easier to use.

Plugin has been pushed to dev. Will eventually publish it online


[Review][Olshansky] Review, Update, Improve & Provide Feedback on Documents

Objective
Review various documents covering different domains across the stack
Goals

Help Olshansky organize all the documents that need to be reviewed in this iteration
Make it easy for others to add additional requests by adding a deliverable in this GitHub Issue
Review all of the documents that need feedback
Make it easy to add additional documents

Deliverables
Public Docs (or docs that will be made public)

[ ] Review RPC Session Life-cycle 🟡
[ ] Review Redelegation Event Delays 🟡
[ ] Review protocol infra notion doc and update protocol infra github repo 🟡
[ ] Review SMT Audit Report ⚪
[ ] WebSocket Design ⚪
[ ] Prepare Q2 requirements for protocol/backend crossover ⚪
[ ] DecAI PNF G2M ⚪
[ ] DecAI Grove G2M ⚪
[ ] Review strategy⚪
[ ] Kickoff this effort ⚪
[ ] Review Quality of Service docs ⚪
[ ] Prepare DecAI effort 🔴
[ ] Update deck 🟡
[ ] wPOKT Migration Plan ⚪

Creator: @Olshansk

Human readable Shannon summary and Morse differences: https://www.notion.so/buildwithgrove/Shannon-Overview-f3ca88d385194f5485aea69066bdcd07


GitLab: adds support for /test <pipelinerun-name> comment

Closes #663
Signed-off-by: Shivam Mukhade<EMAIL_ADDRESS>
Changes

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

Codecov Report

Merging #679 (553711d) into main (4a2b18e) will decrease coverage by 0.12%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #679      +/-   ##
==========================================
- Coverage   70.35%   70.23%   -0.13%
==========================================
  Files          61       61
  Lines        3738     3729       -9
==========================================
- Hits         2630     2619      -11
  Misses        852      852
- Partials      256      258       +2

Impacted Files
Coverage Δ

pkg/provider/gitlab/gitlab.go
88.73% <0.00%> (-1.63%)
:arrow_down:

pkg/hub/get.go
81.81% <0.00%> (-1.04%)
:arrow_down:

pkg/acl/acl.go
100.00% <0.00%> (ø)

pkg/random/random.go
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4a2b18e...553711d. Read the comment docs.


Prepare to release v1.0.15

Pull Request Test Coverage Report for Build 85

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 19.759%

Totals

Change from base Build 84:
0.0%

Covered Lines:
852

Relevant Lines:
4312

💛  - Coveralls


redirect request target url error

redirect request target url none response;
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: ETIMEDOUT

Because I misspelled cause no error handling.
I'm sorry

From CONTRIBUTING.md:
Submitting an Issue

Provide a small self sufficient code example to reproduce the issue.
Run your test code using request-debug and copy/paste the results inside the issue.
You should always use fenced code blocks when submitting code examples or any other formatted output:

  ```js
  put your javascript code here
  ```

  ```
  put any other formatted output here,
  like for example the one returned from using request-debug
  ```

If the problem cannot be reliably reproduced, the issue will be marked as Not enough info (see CONTRIBUTING.md).
If the problem is not related to request the issue will be marked as Help (please use Stackoverflow).


add tensorboardX for loss visualization

Codecov Report

Merging #60 into master will increase coverage by 0.14%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #60      +/-   ##
==========================================
+ Coverage      49%   49.15%   +0.14%
==========================================
  Files          62       62
  Lines        3357     3361       +4
==========================================
+ Hits         1645     1652       +7
+ Misses       1712     1709       -3

Impacted Files
Coverage Δ

fastNLP/core/trainer.py
67.8% <100%> (+0.64%)
:arrow_up:

fastNLP/modules/utils.py
66.21% <0%> (+2.02%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4f37144...baf1789. Read the comment docs.


[BUG]

🐛 Bug
After Following the Install Instruction of #290 and start of of LLM Studio:
i run in the following error (the Error Log)
Cuda Version : WSL Cuda : 11.5
Ubuntu Version: Ubuntu-22.04.3 LTS
WSL Version : wsl-2
h2o-llmstudio Version: 1.2.0 (the newest of main branch)
Error :
INFO:     <IP_ADDRESS>:57600 - "POST / HTTP/1.1" 200 OK 2024-01-23 11:15:44,411 - INFO: Initializing app ... 2024-01-23 11:15:44,421 - INFO: Initializing app ... done 2024-01-23 11:15:44,421 - INFO: Initializing client None 2024-01-23 11:15:44,425 - INFO: User name: anon 2024-01-23 11:15:44,425 - INFO: No user settings found. Using default settings. 2024-01-23 11:15:44,425 - INFO: Heap off 2024-01-23 11:15:44,558 - INFO: {'init_app'} 2024-01-23 11:15:44,562 - ERROR: Unknown exception Traceback (most recent call last):   File "/home/wyv3rn/Downloads/h2o-llmstudio/./llm_studio/app_utils/handlers.py", line 76, in handle     await home(q)   File "/home/wyv3rn/Downloads/h2o-llmstudio/./llm_studio/app_utils/sections/home.py", line 66, in home     stats.append(ui.stat(label="Current GPU load", value=f"{get_gpu_usage():.1f}%"))   File "/home/wyv3rn/Downloads/h2o-llmstudio/./llm_studio/app_utils/utils.py", line 1951, in get_gpu_usage     usage /= len(all_gpus) ZeroDivisionError: float division by zero 2024-01-23 11:15:44,563 - INFO: {'init_app'}
To Reproduce
Follow the Install Instruction #290  and install cuda 11.5 instead of 12.3
Go to http://localhost:10101/ to the UI and wait for the downloads of the datasets.
then take a look onto the Console and you will see the error
LLM Studio version
Commit Version : dff97918d822567e56217fd96f753b1713d848a5

Thank you for reporting.
This error surfaces when LLM Studio is not able to detect any GPU on your system. Can you please run nvidia-smi in your WSL console to ensure that drivers are correctly installed.

Nvidia-Smi said i have cuda and he shows my GPU

no problem :3

https://github.com/h2oai/h2o-llmstudio/blob/dff97918d822567e56217fd96f753b1713d848a5/llm_studio/app_utils/utils.py#L1951
this could be modified to
if len(all_gpus) > 0:
    usage /= len(all_gpus)

Very interesting that nvidia-smi is working for you, as the GPUtil package that we use for the GPU stats claims to grab the stats from the nvidia-smi output.

Requirements
NVIDIA GPU with latest NVIDIA driver installed. GPUtil uses the program nvidia-smi to get the GPU status of all available NVIDIA GPUs. nvidia-smi should be installed automatically, when you install your NVIDIA driver.


⚠ Jenkins Plugins Artifactory has degraded performance

In 84a18c5, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1014 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 9a73ae5 after 40 minutes.


[Bundle Size][Encryption] Offload randomBytes dependency

Description
Use ramdomBytes exported by noble/secp256k1 intstead of extra ramdombytes dependency in encryption package.
For details refer to issue #1193
Type of Change

[ ] New feature
[X] Bug fix
[ ] API reference/documentation update
[ ] Other

Does this introduce a breaking change?
No
Are documentation updates required?
No
Testing information

npm run test

Checklist

[X] Code is commented where needed
[X] Unit test coverage for new or modified code paths
[X] npm run test passes
[ ] Changelog is updated
[X] Tag @janniks and @zone117x for review

@janniks It's a simple PR. Let me know if it can be merged.


add term: 'gastric intestinal metaplasia'

@sabrinatoro could you review this?
There is another metaplasia term in Mondo.
But this is a finding in NCIT
Also, I wonder if this NCIT xref would be more appropriate:
https://www.ebi.ac.uk/ols/ontologies/ncit/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FNCIT_C3956
(vs https://www.ebi.ac.uk/ols/ontologies/ncit/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FNCIT_C8360&lang=en&viewMode=All&siblings=false)

I agree that http://purl.obolibrary.org/obo/NCIT_C3956 would be more appropriate x-ref. However, this term is, as you mentioned, in the "finding" branch of NCIT, and we are excluding these as there are not diseases. So the NCIT cannot be an equivalent term. I suggest using the source "MONDO:relatedTo" (=same by in a different hierarchy)
The main question is: should this term be in Mondo? it looks like it might need to be in HPO instead as I am not sure that it is an actual disease. This part probably requires expert input.


Change lottery factor graph to bar chart

I think this probably needs to be a bar chart excluding Other / None, but I also think there's some thing wrong with the current graph. When I exclude other / none from the legend, the top contributor in the CHAOSS org only has 3 contributions, and I got something similar for another search. Here's a temp doc with the issue I mentioned and some examples of why I think a bar chart is more appropriate for bus factor: https://docs.google.com/document/d/1V0vpMc6jIA-nvVnOd1vv-0aEf4MCn7m1xEccLAcCFgU/edit
Show less

Update: There was something wrong with the graph and now that it is fixed it looks correct. the pie + line chart combo fills the gaps necessary


Add topics via admin tweet

It would be nice for admins to be able to send tweets like "@ImpeachmentTrak add topic #ImpeachAndConvict" to add topics to the topics list.
Implementation Details:
We can store the topics in a BigQuery table and have the collector and have the collector read topics from there. In the collector's on_status method, if a registered admin twitter handle sends a tweet to the registered twitter app account handle (i.e. @ImpeachmentTrak), this will ensure the given topic is in the topics table, and then restart the collection with a new set of topics to collect.

closed via #10


Pantheon: Settings - About: NixOS logo missing

Describe the bug
logo is missing
To Reproduce
Steps to reproduce the behavior:

...
...
...

Expected behavior
logo as before
Screenshots

Additional context
Add any other context about the problem here.
Notify maintainers
@worldofpeace
Metadata

system: "x86_64-linux"
host os: Linux 5.8.16, NixOS, 20.09beta1322.ba2ec4867d7 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.7
channels(root): "home-manager-20.09, nixos-20.09beta1322.ba2ec4867d7, nixos-hardware, nixos-unstable-21.03pre248062.5265d49a36b"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

I noticed that this wasn't the case on vms, and was the case sometimes. I think just the code upstream was buggy, but it's been rewritten to use stuff in GLib so I could fetch that patch.

The proposed fix was from Oct. last year, so it has to be in the channel now.
I still have the issue.

NixOS 20.09.3009.8e78c2cfbae

Still an issue in 21.05pre273435.0aeba64fb26.

This works for me in NixOS 21.05. Though I upgraded to unstable from Nightingale a week ago.

I can still reproduce the issue with Pantheon 6, but also with gnome.gnome-control-center.

It seem not to happen with fresh installs.
The logo with the name nix-snowflake is used, see
[davidak@gaming:~]$ cat /etc/os-release
NAME=NixOS
ID=nixos
VERSION="21.11.git.165c18ade65 (Porcupine)"
VERSION_CODENAME=porcupine
VERSION_ID="21.11.git.165c18ade65"
PRETTY_NAME="NixOS 21.11 (Porcupine)"
LOGO="nix-snowflake"
HOME_URL="https://nixos.org/"
DOCUMENTATION_URL="https://nixos.org/learn.html"
SUPPORT_URL="https://nixos.org/community.html"
BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"

I do have such files in nix store, but maybe the package nixos-icons is not installed in the current system for some reason.
[davidak@gaming:~]$ sudo find / -name 'nix-snowflake.*'
[sudo] password for davidak:
find: ‘/run/user/1000/gvfs’: Permission denied
/nix/store/zd13xszbsb3jpsa28ayz99c60q87grcp-nixos-icons-2021-02-24/share/icons/hicolor/scalable/apps/nix-snowflake.svg
/nix/store/zd13xszbsb3jpsa28ayz99c60q87grcp-nixos-icons-2021-02-24/share/icons/hicolor/1024x1024/apps/nix-snowflake.png
/nix/store/zd13xszbsb3jpsa28ayz99c60q87grcp-nixos-icons-2021-02-24/share/icons/hicolor/48x48/apps/nix-snowflake.png
/nix/store/zd13xszbsb3jpsa28ayz99c60q87grcp-nixos-icons-2021-02-24/share/icons/hicolor/96x96/apps/nix-snowflake.png
/nix/store/zd13xszbsb3jpsa28ayz99c60q87grcp-nixos-icons-2021-02-24/share/icons/hicolor/128x128/apps/nix-snowflake.png
/nix/store/zd13xszbsb3jpsa28ayz99c60q87grcp-nixos-icons-2021-02-24/share/icons/hicolor/24x24/apps/nix-snowflake.png
/nix/store/zd13xszbsb3jpsa28ayz99c60q87grcp-nixos-icons-2021-02-24/share/icons/hicolor/32x32/apps/nix-snowflake.png
/nix/store/zd13xszbsb3jpsa28ayz99c60q87grcp-nixos-icons-2021-02-24/share/icons/hicolor/256x256/apps/nix-snowflake.png
/nix/store/zd13xszbsb3jpsa28ayz99c60q87grcp-nixos-icons-2021-02-24/share/icons/hicolor/512x512/apps/nix-snowflake.png
/nix/store/zd13xszbsb3jpsa28ayz99c60q87grcp-nixos-icons-2021-02-24/share/icons/hicolor/64x64/apps/nix-snowflake.png
/nix/store/zd13xszbsb3jpsa28ayz99c60q87grcp-nixos-icons-2021-02-24/share/icons/hicolor/16x16/apps/nix-snowflake.png
/nix/store/zd13xszbsb3jpsa28ayz99c60q87grcp-nixos-icons-2021-02-24/share/icons/hicolor/72x72/apps/nix-snowflake.png
/nix/store/3ngjivliq4pcb2gwcg97szn4w1yr65f0-nixos-icons-2021-02-24/share/icons/hicolor/scalable/apps/nix-snowflake.svg
/nix/store/3ngjivliq4pcb2gwcg97szn4w1yr65f0-nixos-icons-2021-02-24/share/icons/hicolor/1024x1024/apps/nix-snowflake.png
/nix/store/3ngjivliq4pcb2gwcg97szn4w1yr65f0-nixos-icons-2021-02-24/share/icons/hicolor/48x48/apps/nix-snowflake.png
/nix/store/3ngjivliq4pcb2gwcg97szn4w1yr65f0-nixos-icons-2021-02-24/share/icons/hicolor/96x96/apps/nix-snowflake.png
/nix/store/3ngjivliq4pcb2gwcg97szn4w1yr65f0-nixos-icons-2021-02-24/share/icons/hicolor/128x128/apps/nix-snowflake.png
/nix/store/3ngjivliq4pcb2gwcg97szn4w1yr65f0-nixos-icons-2021-02-24/share/icons/hicolor/24x24/apps/nix-snowflake.png
/nix/store/3ngjivliq4pcb2gwcg97szn4w1yr65f0-nixos-icons-2021-02-24/share/icons/hicolor/32x32/apps/nix-snowflake.png
/nix/store/3ngjivliq4pcb2gwcg97szn4w1yr65f0-nixos-icons-2021-02-24/share/icons/hicolor/256x256/apps/nix-snowflake.png
/nix/store/3ngjivliq4pcb2gwcg97szn4w1yr65f0-nixos-icons-2021-02-24/share/icons/hicolor/512x512/apps/nix-snowflake.png
/nix/store/3ngjivliq4pcb2gwcg97szn4w1yr65f0-nixos-icons-2021-02-24/share/icons/hicolor/64x64/apps/nix-snowflake.png
/nix/store/3ngjivliq4pcb2gwcg97szn4w1yr65f0-nixos-icons-2021-02-24/share/icons/hicolor/16x16/apps/nix-snowflake.png
/nix/store/3ngjivliq4pcb2gwcg97szn4w1yr65f0-nixos-icons-2021-02-24/share/icons/hicolor/72x72/apps/nix-snowflake.png
/nix/store/nklf9m0i30agdl7r2baqpzldjch8hk3f-system-path/share/icons/hicolor/scalable/apps/nix-snowflake.svg
/nix/store/nklf9m0i30agdl7r2baqpzldjch8hk3f-system-path/share/icons/hicolor/48x48/apps/nix-snowflake.png
/nix/store/nklf9m0i30agdl7r2baqpzldjch8hk3f-system-path/share/icons/hicolor/96x96/apps/nix-snowflake.png
/nix/store/nklf9m0i30agdl7r2baqpzldjch8hk3f-system-path/share/icons/hicolor/128x128/apps/nix-snowflake.png
/nix/store/nklf9m0i30agdl7r2baqpzldjch8hk3f-system-path/share/icons/hicolor/24x24/apps/nix-snowflake.png
/nix/store/nklf9m0i30agdl7r2baqpzldjch8hk3f-system-path/share/icons/hicolor/32x32/apps/nix-snowflake.png
/nix/store/nklf9m0i30agdl7r2baqpzldjch8hk3f-system-path/share/icons/hicolor/256x256/apps/nix-snowflake.png
/nix/store/nklf9m0i30agdl7r2baqpzldjch8hk3f-system-path/share/icons/hicolor/512x512/apps/nix-snowflake.png
/nix/store/nklf9m0i30agdl7r2baqpzldjch8hk3f-system-path/share/icons/hicolor/64x64/apps/nix-snowflake.png
/nix/store/nklf9m0i30agdl7r2baqpzldjch8hk3f-system-path/share/icons/hicolor/16x16/apps/nix-snowflake.png
/nix/store/nklf9m0i30agdl7r2baqpzldjch8hk3f-system-path/share/icons/hicolor/72x72/apps/nix-snowflake.png
/nix/store/72hvxa4cvlj00ii718nsnj7ii39w6ddm-nixos-icons-2021-02-24/share/icons/hicolor/scalable/apps/nix-snowflake.svg
/nix/store/72hvxa4cvlj00ii718nsnj7ii39w6ddm-nixos-icons-2021-02-24/share/icons/hicolor/1024x1024/apps/nix-snowflake.png
/nix/store/72hvxa4cvlj00ii718nsnj7ii39w6ddm-nixos-icons-2021-02-24/share/icons/hicolor/48x48/apps/nix-snowflake.png
/nix/store/72hvxa4cvlj00ii718nsnj7ii39w6ddm-nixos-icons-2021-02-24/share/icons/hicolor/96x96/apps/nix-snowflake.png
/nix/store/72hvxa4cvlj00ii718nsnj7ii39w6ddm-nixos-icons-2021-02-24/share/icons/hicolor/128x128/apps/nix-snowflake.png
/nix/store/72hvxa4cvlj00ii718nsnj7ii39w6ddm-nixos-icons-2021-02-24/share/icons/hicolor/24x24/apps/nix-snowflake.png
/nix/store/72hvxa4cvlj00ii718nsnj7ii39w6ddm-nixos-icons-2021-02-24/share/icons/hicolor/32x32/apps/nix-snowflake.png
/nix/store/72hvxa4cvlj00ii718nsnj7ii39w6ddm-nixos-icons-2021-02-24/share/icons/hicolor/256x256/apps/nix-snowflake.png
/nix/store/72hvxa4cvlj00ii718nsnj7ii39w6ddm-nixos-icons-2021-02-24/share/icons/hicolor/512x512/apps/nix-snowflake.png
/nix/store/72hvxa4cvlj00ii718nsnj7ii39w6ddm-nixos-icons-2021-02-24/share/icons/hicolor/64x64/apps/nix-snowflake.png
/nix/store/72hvxa4cvlj00ii718nsnj7ii39w6ddm-nixos-icons-2021-02-24/share/icons/hicolor/16x16/apps/nix-snowflake.png
/nix/store/72hvxa4cvlj00ii718nsnj7ii39w6ddm-nixos-icons-2021-02-24/share/icons/hicolor/72x72/apps/nix-snowflake.png

Needs more investigation.

The issue is reproducible when setting:
documentation.doc.enable = false;


Question about the ASTAR dataset

May I know how to access the ASTAR dataset？

Hi Jihan,
You could ask Astar by sending an email to their Astar3D team, not sure if
their dataset is available or not though... I graduated a long time ago, so
I might don’t have the dataset in the University server now…
Best Regards,
Weichen
jihan.yang @.***>于2022年9月6日 周二22:48写道：

May I know how to access the ASTAR dataset？
—
Reply to this email directly, view it on GitHub
https://github.com/zhangweichen2006/SRDAN_Open/issues/3, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADLK4U2C26THRML6Z73WZUDV444SBANCNFSM6AAAAAAQFZNYRE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks so much.


Character Layer Issue - update_wrapper

Definition of update_wrapper function takes two argumuents.
https://github.com/L1nked2/LostarkDPM/blob/55b2b0e7e23d0195febbee39d424fe2cf6fb36e5/src/layers/static/character_layer.py#L49-L54
But, the usage of the function as decorator takes no argument, does it work?
https://github.com/L1nked2/LostarkDPM/blob/55b2b0e7e23d0195febbee39d424fe2cf6fb36e5/src/layers/static/character_layer.py#L76-L83
In my execution ( execute main_wooz.py ), it does not work as follows.
TypeError: update_wrapper() missing 2 required positional arguments: 'self' and 'update_func'

We may take different way for update_wrapper

Check PR #17


VScode 2022 extensions trouble

This issue has been moved from a ticket on Developer Community.

thank you for supporting and i wish you can reply me by the other mail address which i used the most.
Mail: [Redacted]@[Redacted]
and the problem is, i discover that the extension searching have some issue that i cant find and install the extension which i need to use.
for an example , i cant find the python preview in the VScode but i can find it by online site.
when i click the install button, nothing happens also cant install the extension by downloading the extension.
https://marketplace.visualstudio.com/items?itemName=dongli.python-preview&ssr=false#overview

Original Comments
Feedback Bot on 8/7/2022, 11:58 PM:
(private comment, text removed)

Original Solutions
(no solutions)

Thanks for the report, however, this is not a Microsoft extension. Please contact the author.


[UI Apps] Auth State

Follow the read me here: https://github.com/DataDog/apps-auth-sample/blob/main/README.md

I'm leaving my main feedback for the work across the repos in this PR so that it's centralized.
This works well, thanks in particular for the very thorough demo app!
The polling of authStateCallback while the authorization popup is open is really unfortunate. I do understand why it's implemented that way, it is the easiest way to maintain the constraint that we can use existing application authentication mechanisms with zero effort required from developers.
It would be better all around if there were a way for developers to 'tell us' when the auth state is resolved. One idea i had is to make a generic redirect page that developers could redirect to after the user authenticates, like/apps/resolve-auth-state?app_id=id&isAuthenticated=true&.... It would be a blank page with a spinner that would maybe be running framepost to send a message to the parent saying the auth state is resolved before closing itself.
That would mean that the developers would need some of their auth logic to be specific to the datadog app, at least the handler that says to redirect to that url on successful auth. I wonder if the UX + performance improvements would be worth that minimal effort?
Potentially it could be an option we give developers called like resolutionType= "poll" | "redirect" They could do the easiest thing with polling to get off the ground, but we could recommend a redirect resolution as the better way to do it if they want to put the minimal effort in.
I left some other comments about naming and where we put certain logic inline below, happy to discuss!

I think a generic redirect page might work, but it will require a some tedious configuration from the developer's side because the full url will change based on the env (us, eu, etc) and most auth providers require the redirect url to be predefined. Until we support cross-region availability, I don't think it's worth the effort.
I think the redirect use case can be simpler to handle with the second auth provider that I demoed earlier. Basically the redirect page will be part of this app itself and we leverage the framepost's requestChannelWithPopup that I added it just for this purpose so we can run the sdk on the popup. Developers can then just call client.auth.resolveAuthState() on demand without polling.  (a working POC is still available here).
That said, I believe the simplicity of polling approach might be appealing to most developers specially with the ability to customize the logic in authStateCallback to short circuit it based on the existence of a localStorage token or cookie and/or fine tune timeout/interval periods for expensive API calls. I'd rather stick to the simplicity of this approach and get some feedback from users before considering a more complex solution.

yeah your original POC using framepost and client.auth.resolveAuthState() would work really well actually, that is a much better idea than mine :) I agree polling is the simplest approach for now. Let's roll out with it, and investigate other methods as a followup


Improve IPv6ScopeIdMatchUnitTestCase

Improve failure message in test. Don't try and add a scope_id to global IPv6 addresses.
This relates to but isn't expected to correct https://issues.jboss.org/browse/WFCORE-934 I'm trying to get a bit more info to understand the cause, plus fix a flaw in the test that likely is unrelated, but worth fixing anyway.

Core - Full Integration - Windows Build 78 is now running using a merge of e8710dadb6c5c7683a0da3b1d298d14b51d20e30

Windows Build 2041 is now running using a merge of e8710dadb6c5c7683a0da3b1d298d14b51d20e30

Core - Full Integration Build 1657 is now running using a merge of e8710dadb6c5c7683a0da3b1d298d14b51d20e30

Linux Build 2531 is now running using a merge of e8710dadb6c5c7683a0da3b1d298d14b51d20e30

Windows Build 2041 outcome was SUCCESS using a merge of e8710dadb6c5c7683a0da3b1d298d14b51d20e30
Summary: Tests passed: 3405, ignored: 64 Build time: 00:35:28

Linux Build 2531 outcome was SUCCESS using a merge of e8710dadb6c5c7683a0da3b1d298d14b51d20e30
Summary: Tests passed: 3405, ignored: 64 Build time: 00:37:26

Core - Full Integration - Windows Build 78 outcome was SUCCESS using a merge of e8710dadb6c5c7683a0da3b1d298d14b51d20e30
Summary: Tests passed: 3060, ignored: 358 Build time: 00:48:59

Core - Full Integration Build 1657 outcome was SUCCESS using a merge of e8710dadb6c5c7683a0da3b1d298d14b51d20e30
Summary: Tests passed: 3060, ignored: 358 Build time: 00:49:33


Create localization for French users, will be added to crowdin

Localizations should be added through an issue: https://github.com/trakt-tools/universal-trakt-scrobbler/issues/new?assignees=trakt-tools-bot&labels=new+language&template=new-language.md&title=Add+new+language%3A+[LANGUAGE] It will be automatically created on Crowdin and then you can add the translations there. We don't add translations through PRs.


refactor: improved naming in TxExecutionRequest

Please read contributing guidelines and remove this line.

#6014  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @benesjan and the rest of your teammates on  Graphite

Benchmark results
Metrics with a significant change:

note_successful_decrypting_time_in_ms (8): 225 (+42%)
note_trial_decrypting_time_in_ms (64): 118 (+284%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
772
772
772

l1_rollup_calldata_gas
6,832
6,844
6,844

l1_rollup_execution_gas
587,313
587,325
587,325

l2_block_processing_time_in_ms
1,493 (+4%)
5,492 (+4%)
10,479 (+2%)

note_successful_decrypting_time_in_ms
:warning: 225 (+42%)
603 (-1%)
1,150 (+12%)

note_trial_decrypting_time_in_ms
15.2 (-68%)
100 (-3%)
:warning: 118 (+284%)

l2_block_building_time_in_ms
19,054 (+2%)
74,239 (+1%)
147,635 (+1%)

l2_block_rollup_simulation_time_in_ms
18,835 (+2%)
73,457 (+1%)
146,142 (+1%)

l2_block_public_tx_process_time_in_ms
8,653 (+2%)
33,614 (+1%)
67,253 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
16,429 (+6%)
30,559 (-8%)

note_history_successful_decrypting_time_in_ms
1,326 (-2%)
2,650 (-1%)

note_history_trial_decrypting_time_in_ms
79.7 (-9%)
120 (-8%)

node_database_size_in_bytes
19,116,112
35,774,544

pxe_database_size_in_bytes
29,859
59,414

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
159 (-10%)
47,763
31,978

private-kernel-inner
177 (-9%)
80,794
31,978

private-kernel-ordering
137 (-10%)
57,732
50,043

base-parity
79.2 (+3%)
128
265

root-parity
129 (+5%)
1,244
265

base-rollup
12,394 (-4%)
110,926
957

root-rollup
50.0 (-1%)
4,551
821

public-kernel-app-logic
1,676 (-2%)
62,017
52,067

public-kernel-tail
4,258 (-3%)
168,566
7,491

merge-rollup
3,115 (-5%)
2,760
957

public-kernel-teardown
111 (-5%)
62,017
52,067

public-kernel-setup
118
62,017
52,067

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
11.0 (-2%)
17.7 (-1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.641 (-2%)
0.545 (-2%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
51.6 (-6%)
81.2 (+2%)
261 (+2%)
500 (-4%)
987 (+2%)
1,965 (+2%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
96.0
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.529 (-6%)
0.500 (+2%)
0.475 (+1%)
0.467 (-4%)
0.468 (+1%)
0.468 (+2%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
60.5 (-5%)
120 (+3%)
382 (+2%)
735 (-8%)
1,479 (+2%)
2,936 (+2%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
105
207
691
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.534 (-6%)
0.539 (+1%)
0.516 (+2%)
0.506 (-8%)
0.511 (+2%)
0.510 (+1%)
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
67.6 (-6%)

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
109

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.588 (-6%)

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
51,411
543,524

Transaction size based on fee payment method

Metric
native fee payment method
fpc_public fee payment method
fpc_private fee payment method

tx_with_fee_size_in_bytes
897
1,145
1,345

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
1,285 (+4%)
867 (-9%)
3,536 (+2%)

Metric
1 public data writes
2 public data writes
3 public data writes
4 public data writes
5 public data writes
8 public data writes

tx_sequencer_processing_time_ms
834 (-5%)
758
1,357 (+1%)
900
2,080
1,089 (+1%)


Spyder   fix to issue #1785 regarding the comment function

Comment function : adds a space after the comment string (# for Python)
Uncomment function : removes the comment string and removes one space
if there is one

I think I shouldn't have targeted the master branch, so i closed the pr

No, please target the 3.x branch.


Refactor property error structure

Codecov Report

Merging #71 into master will decrease coverage by 0.4%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master      #71      +/-   ##
==========================================
- Coverage    91.8%   91.39%   -0.41%
==========================================
  Files          69       69
  Lines         976      976
  Branches      194      194
==========================================
- Hits          896      892       -4
  Misses         36       36
- Partials       44       48       +4

Impacted Files
Coverage Δ

packages/rawmodel-core/src/core/validator.ts
84.21% <ø> (-5.79%)
:arrow_down:

packages/rawmodel-core/src/core/handler.ts
84.21% <ø> (-5.79%)
:arrow_down:

packages/rawmodel-core/src/core/models.ts
91.47% <0%> (-0.72%)
:arrow_down:

packages/rawmodel-core/src/core/props.ts
91.04% <100%> (-0.69%)
:arrow_down:


[SPARK-32685][SQL] When specify serde, default filed.delim is '\t'

What changes were proposed in this pull request?
In hive script transform, when we use specified serde, the filed.delim is '\t'

And change to other serde and explain query plan, filed.delim is same.
In spark current code, the result is as below:

We should keep same as hive.
Notic:
the result's NULL value is   different is another issue  https://issues.apache.org/jira/browse/SPARK-32684
Why are the changes needed?
Keep same with hive serde
Does this PR introduce any user-facing change?
In script transform, is not specified,  field.delim keep same with hive as \t
How was this patch tested?
UT added

Add UT
val query4 = sql(
      """
        |SELECT split(value, "&") FROM (
        |SELECT TRANSFORM(a, b, c)
        |  ROW FORMAT SERDE 'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe'
        |USING 'cat'
        |  ROW FORMAT SERDE 'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe'
        |  WITH SERDEPROPERTIES (
        |   'serialization.last.column.takes.rest' = 'true',
        |   'field.delim' = '&'
        |  )
        |FROM (SELECT 1 AS a, 2 AS b, 3 AS c) t
        |) temp;
      """.stripMargin)
    checkAnswer(query4, identity, Row(null) :: Nil)

Since in Hive

FYI @maropu @cloud-fan

Test build #133421 has started for PR 30942 at commit 79e78f3.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38012/

Test build #133421 has finished for PR 30942 at commit 79e78f3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133421/

The code has been modified to make it easier for it to add other possible default parameters in specified Hive serde mode.
FYI @cloud-fan

thanks, merging to master!

@AngersZhuuuu Please upgrade the migration guide

@AngersZhuuuu Please upgrade the migration guide

@AngersZhuuuu Please update the migration guide

Yea

@AngersZhuuuu Please update the migration guide

Yea


Unable to control exposure of the color camera

I'm having troubles toggling auto exposure and getting/setting exposure time manually. supports_option() function works and reports that the rs::option::color_enable_auto_exposure is supported. However, when I try to get or set this option I get the following error:
RealSense error calling rs_get_device_option(device:0x19f7af0, option:COLOR_ENABLE_AUTO_EXPOSURE):
    VIDIOC_G_CTRL error 22, Invalid argument

At the same time, I can toggle auto exposure using v4l2-ctl -d /dev/video1 -c exposure_auto=1. So it seems to be a problem on the library side.
$ uname -a
Linux raccoon 3.19.0-49-generic #55~14.04.1-Ubuntu SMP Fri Jan 22 11:24:31 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Tried with both R200 and F200. Any suggestions?

Hmm. We already have an inline comment for this as well https://github.com/IntelRealSense/librealsense/blob/master/src/uvc-v4l2.cpp#L459
It works for F200, R200, and SR300 on our Windows backend, so we'll look into it more deeply.

I'll also give it a try on my Arch laptop this weekend and let you know about the results.

Confirming this works fine on Windows but throws an error on Ubuntu 14.04.

UVC controls across the backends have slightly inconsistent interfaces when it comes to exposure. There is some additional logic that will need to be added to the V4L2 backend. Just noting here that we acknowledge color exposure is broken on Linux but at the moment it's lower priority to fix.

I aslo can notset this option in Window10，but I can set it，I used：
dev->set_option(rs::option::color_exposure, 100);
but it is not worked

I confirm this happens on 14.04 when using the Realsense ROS package and setting R200_LR_AUTO_EXPOSURE_ENABLED to 1. That makes the IR and depth images stall until I reconnect the device.
What's also interesting: the cpp-enumerate-devices example shows the following:
COLOR_ENABLE_AUTO_EXPOSURE : 0 .. 0, 1

Which I understand as the color auto exposure having range 0-0. That's strange.

As I noted before, it is possible to toggle auto exposure and adjust exposure time using v4l2-ctl command-line tool. I had a look inside the source code, and it turns out they use different control IDs. For auto exposure it is V4L2_CID_EXPOSURE_AUTO, and for exposure time it is V4L2_CID_EXPOSURE_ABSOLUTE.
So this patch fixes the issue for me:
diff --git a/src/uvc-v4l2.cpp b/src/uvc-v4l2.cpp
index 9c1b01b..05a94f5 100644
--- a/src/uvc-v4l2.cpp
+++ b/src/uvc-v4l2.cpp
@@ -462,14 +462,14 @@ namespace rsimpl
             case RS_OPTION_COLOR_BACKLIGHT_COMPENSATION: return V4L2_CID_BACKLIGHT_COMPENSATION;
             case RS_OPTION_COLOR_BRIGHTNESS: return V4L2_CID_BRIGHTNESS;
             case RS_OPTION_COLOR_CONTRAST: return V4L2_CID_CONTRAST;
-            case RS_OPTION_COLOR_EXPOSURE: return V4L2_CID_EXPOSURE; // Is this actually valid? I'm getting a lot of VIDIOC error 22s...
+            case RS_OPTION_COLOR_EXPOSURE: return V4L2_CID_EXPOSURE_ABSOLUTE;
             case RS_OPTION_COLOR_GAIN: return V4L2_CID_GAIN;
             case RS_OPTION_COLOR_GAMMA: return V4L2_CID_GAMMA;
             case RS_OPTION_COLOR_HUE: return V4L2_CID_HUE;
             case RS_OPTION_COLOR_SATURATION: return V4L2_CID_SATURATION;
             case RS_OPTION_COLOR_SHARPNESS: return V4L2_CID_SHARPNESS;
             case RS_OPTION_COLOR_WHITE_BALANCE: return V4L2_CID_WHITE_BALANCE_TEMPERATURE;
-            case RS_OPTION_COLOR_ENABLE_AUTO_EXPOSURE: return V4L2_CID_AUTOGAIN; // Automatic gain/exposure control
+            case RS_OPTION_COLOR_ENABLE_AUTO_EXPOSURE: return V4L2_CID_EXPOSURE_AUTO;
             case RS_OPTION_COLOR_ENABLE_AUTO_WHITE_BALANCE: return V4L2_CID_AUTO_WHITE_BALANCE;
             default: throw std::runtime_error(to_string() << "no v4l2 cid for option " << option);
             }

Tested with all (R200, F200, SR300) cameras. Note that V4L2_CID_EXPOSURE_AUTO encodes modes with enum, where 1 is manual mode, and 3 is aperture priority. This means that to disable auto exposure one needs to call device->set_option(rs::options::color_enable_auto_exposure, 1), and to enable it device->set_option(rs::options::color_enable_auto_exposure, 3).

I've been using librealsense with this patch for over a month now on Ubuntu 14.04 and 16.04 without any problems. Should I submit a pull request?

Thank you, this does seem to solve the problem.
This fix is also available on the development branch and will be merged to master.

Auto exposure should be functional now on all platforms


net: ip: igmp: IGMP v2 membership reports are sent to <IP_ADDRESS> instead of the group being reported

Describe the bug
The Zephyr network stack is sending IGMP v2 membership reports to the <IP_ADDRESS> multicast address instead of the multicast group it is being reported. When reading through RFC 2236 (http://www.faqs.org/rfcs/rfc2236.html) Section 9 this seems to be a violation. I've copy pasted the relevant text from the RFC:
9.  Message destinations

   This information is provided elsewhere in the document, but is
   summarized here for convenience.

   Message Type                  Destination Group
   ------------                  -----------------
   General Query                 ALL-SYSTEMS (<IP_ADDRESS>)
   Group-Specific Query          The group being queried
   Membership Report             The group being reported
   Leave Message                 ALL-ROUTERS (<IP_ADDRESS>)

The reason why I am reporting this issue is when I was reporting https://github.com/zephyrproject-rtos/zephyr/issues/52409 , with IGMP snooping enabled on my Cisco SG300 switch the STM32H7 device was not able to receive UDP IPv4 multicast data when it opened up a socket. What I observed was despite sending membership reports for <IP_ADDRESS> the device was able to receive mDNS multicast however, it was not able to receive multicast from a 239.255.x.x address. Hence why this issue was raised.
The leave reports are sent to the correct destination address of <IP_ADDRESS>.
Please also mention any information which could help others to understand
the problem you're facing:

What target platform are you using? Nucleo-H753ZI Evaluation board
What have you tried to diagnose or workaround this issue? This issue cannot be worked around since IGMP snooping is required to avoid flooding a device with multicast
Is this a regression? If yes, have you been able to "git bisect" it to a
specific commit? This issue is present in v3.1 and v3.2

To Reproduce
Steps to reproduce the behavior:

Run wireshark
Open a socket to receive UDP/IP multicast data
Join the multicast group address (net_ipv4_igmp_join)

Expected behavior
The device should send the IGMP membership report to the multicast group that is being reported and be able to receive the UDP/IP multicast data on a network with IGMP snooping enabled.
Impact
We cannot ship our product that is not able to receive UDP/IP multicast in a network with IGMP snooping enabled.
Additional context
I have a fix for this issue: in zephyr/subsys/net/ip/igmp.c: igmp_send_generic, the following should be changed:
ret = igmp_v2_create_packet(pkt, &all_routers, addr,
			join ? NET_IPV4_IGMP_REPORT_V2 : NET_IPV4_IGMP_LEAVE);

to
ret = igmp_v2_create_packet(pkt, join ? addr : &all_routers, addr,
			join ? NET_IPV4_IGMP_REPORT_V2 : NET_IPV4_IGMP_LEAVE);

Whoever is reviewing this ticket agrees with my change, feel free to assign the ticket to me and I will send a PR for the change and quote the ticket number in the change commit.

Thanks for the report, please send a PR for it.

Sorry @jukkar for the delay in submitting the PR: https://github.com/zephyrproject-rtos/zephyr/pull/52521. This was my first time sending a PR so it took some time to sort out the various issues around pushing changes github.


Installation Instruction wrong bro-pkg install bro/hosom/file-extraction

for install this package you must remove bro/
bro-pkg install hosom/file-extraction (correct)
bro-pkg install bro/hosom/file-extraction (wrong)
also you can use zkg instead bro-pkg
dont forget install zkg with sudo pip install zkg

Thanks! The docs have been updated.


Any reason why MNLIReader.py was deleted?

In the new version of the paper, MNLI results were removed. May I know what the problem is in using ADAPET on MNLI?

In our paper, we never had results on any of the datasets outside of SueprGLUE (MNLI is not in SuperGLUE). For reference, you can access the first version of our paper here.

My bad, I got confused with the PET paper.


Responsive navigation

Codecov Report

Merging #84 (627fbe5) into main (41d89d6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #84   +/-   ##
=======================================
  Coverage   30.25%   30.25%
=======================================
  Files          51       51
  Lines         542      542
  Branches      123      123
=======================================
  Hits          164      164
  Misses        359      359
  Partials       19       19

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 41d89d6...627fbe5. Read the comment docs.


support jsc.baseUrl

Currently it is very selective and does not include this.

Thanks for reminding. I've fixed it. 👍
I'm keeping two set of configs in sync as much as possible. However some fields in tsconfig are not fully supported by swc.
Vice versa. But they are iterating. If anything is out of sync please let me know.

In that case, there are a few more typescript related options in https://swc.rs/docs/configuration/compilation

Could you be more specific?

{
  "jsc": {
    "parser": {
      "syntax": "typescript",
      "tsx": false,
      "decorators": true,
      "dynamicImport": true
    }
  }
}


unknown setting opendistro_security.disabled, documentation requires update?

Hi, i was setting up opendistro with security disabled, for development purpose, and folled the guide to disable security, in the docs here https://opendistro.github.io/for-elasticsearch-docs/docs/security/disable/
A exception is thrown indicating the setting  opendistro_security.disabled  is removed.
I removed all the settings related to opendistro_security including opendistro_security.disabled, and got it working without security.
I think, the setting has been removed, but the documentation is not updated.

Hi @abhijithshivaswamy, can you share your elasticsearch.yml, whether you're using the RPM installation or Docker install, and the timing of the error message?
If I fire up a fresh cluster using Docker, that line seems essential, but if you've already removed the plugin or the cluster is already running, I can imagine an error being thrown. Thanks!

I Apologise for late reply.
I installed it using RPM, added the opendistro_security.disabled  in elasticsearch.yml, and moved the plugins/security out of the installation folder of opendistro.
Then restarted opendistro, and above mentioned exception was being thrown in log file.
Here's the elasticsearch.yml (i have not changed any settings related to elasticsearch, only opendistro settings)
######## Start OpenDistro for Elasticsearch Security Demo Configuration ########
WARNING: revise all the lines below before you go into production
opendistro_security.disabled: true
cluster.routing.allocation.disk.threshold_enabled: false
discovery.zen.minimum_master_nodes: 1
node.max_local_storage_nodes: 3
######## End OpenDistro for Elasticsearch Security Demo Configuration ########

Hi @abhijithshivaswamy, gotcha, that's what I suspected. I'll see if I can separate the two operations a bit in the documentation. Basically:

If you want to temporarily disable the plugin, but reenable it at a later time, you just add

oh, i'm sorry then, i read it as both steps are required to disable security.
Thanks for clarifying @aetter  :+1:

Hi @abhijithshivaswamy, no worries at all. If you read it that way, others will, too. I'll separate it with headers or something. Thanks a bunch for reporting!


mupx not installing on osx, npm or node v issue?

Hi Im trying to test a deployment with mupx, but im getting this error on install. Is this a npm or node v issue?
Richs-MacBook-Air-2:~ rich$ npm install -g mupx
npm WARN locking Error: EACCES, open '/Users/rich/.npm/_locks/mupx-84ac75d4c3f80c3a.lock'
npm WARN locking     at Error (native)
npm WARN locking  /Users/rich/.npm/_locks/mupx-84ac75d4c3f80c3a.lock failed { [Error: EACCES, open '/Users/rich/.npm/_locks/mupx-84ac75d4c3f80c3a.lock']
npm WARN locking   errno: -13,
npm WARN locking   code: 'EACCES',
npm WARN locking   path: '/Users/rich/.npm/_locks/mupx-84ac75d4c3f80c3a.lock' }
npm ERR! Darwin 14.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "mupx"
npm ERR! node v0.12.6
npm ERR! npm  v2.11.2
npm ERR! Attempt to unlock /usr/local/lib/node_modules/mupx, which hasn't been locked
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     https://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/rich/npm-debug.log
Richs-MacBook-Air-2:~ rich$

try:
sudo npm install -g mupx

yeah that worked


MemoryError when the dimention is too large

I have to solve a QP problem with all dimension between zero and one , in order to use the OSQP solver, so I change them into the linear inequality form constraints ,maybe the vector dimention is too large ,more than 200000 ,then in numpy prompted MemoryError

Could you please provide a MWE in which you get the error?

P = sparse.csc_matrix(H)
E = np.vstack([H, Aeq])
E = sparse.csc_matrix(E)
l =  np.vstack([lb, beq])
u = np.vstack([ub, beq])
prob = osqp.OSQP()
prob.setup(self.P, self.q, self.E, self.l, self.u, alpha=1.0, verbose=False)
my demo code is above
the error is below:
File "/home/lth/myProject/cnn/mul_layer.py", line 68, in init
P=sparse.csc_matrix(np.eye(N))
File "/home/lth/anaconda3/lib/python3.5/site-packages/numpy/lib/twodim_base.py", line 186, in eye
m = zeros((N, M), dtype=dtype, order=order)
MemoryError

I am sorry, but this is not a minimum working example. You should provide code that someone else could run. You have not provided all the information required.
However, it seems from the error code above that the error does not occur with OSQP, but with NumPy.  You might consider setting P as P=sparse.eye(N).tocsc().

I am sorry , this is my demo code:
import numpy as np
import random
import time
def tic():
globals()['tt'] = time.clock()
def toc():
print ('\nElapsed time: %.8f seconds\n' % (time.clock()-globals()['tt']))
N=100000
k=100
v_index=random.sample(range(0,N),k)  #minimal:0  maximal:N-1  sample:k
v = np.zeros([N,1])
v[v_index,0]=1
y1 = np.zeros([N,1])
f=-v-y1
H=np.eye(N)
lb=np.zeros([N,1])
ub=np.ones([N,1])
Aeq=np.ones([N,1]).transpose()
beq=k*np.ones([1,1])
'''osqp'''
import osqp
import scipy.sparse as sparse
Define problem data
P = sparse.csc_matrix(H)
q = f
A = np.vstack([H, Aeq])
A = sparse.csc_matrix(A)
l = np.vstack([lb, beq])
u = np.vstack([ub, beq])
Create an OSQP object
tic()
prob = osqp.OSQP()
toc()
tic()
Setup workspace and change alpha parameter
prob.setup(P, q, A, l, u, alpha=1.0)
Solve problem
res = prob.solve()
toc()
z3=res.x
print(z3.shape)

I just edited few lines of your code and it seems to work now. The code is shown below:
import numpy as np
import random

import time

def tic():
  globals()['tt'] = time.clock()

def toc():
  print ('\nElapsed time: %.8f seconds\n' % (time.clock()-globals()['tt']))

N=100000
k=100
v_index=random.sample(range(0,N),k) #minimal:0 maximal:N-1 sample:k
v = np.zeros([N,1])
v[v_index,0]=1
y1 = np.zeros([N,1])
f=-v-y1
#H=np.eye(N)                          # COMMENTED OUT

lb=np.zeros([N,1])
ub=np.ones([N,1])

Aeq=np.ones([N,1]).transpose()
beq=k*np.ones([1,1])

import osqp
import scipy.sparse as sparse

P = sparse.eye(N).tocsc()             # MODIFIED
q = f
A = sparse.vstack([P, Aeq]).tocsc()   # MODIFIED
#A = sparse.csc_matrix(A)             # COMMENTED OUT
l = np.vstack([lb, beq])
u = np.vstack([ub, beq])

tic()
prob = osqp.OSQP()
toc()

tic()
prob.setup(P, q, A, l, u, alpha=1.0)
res = prob.solve()
toc()
z3=res.x
print(z3.shape)

The problem was not related to OSQP. The error occurred when you tried to construct a dense matrix H with 1e10 elements. This can be avoided by using sparse matrices instead.

Thank you so much !
I will have a try.

I will close the issue. Feel free to reopen it if you still have some problems.


Update Code - Proof_Of_ContributionSnapshot7.md

Morpheus Rewards Claim App
Details
Developed a claiming application/dashboard that enables capital and code contributors to connect their wallets and easily claim their rewards. The application features a simple, effective UI and follows a three-step process. First, users connect their wallets to load their accrued rewards. Second, they claim these rewards to an Arbitrum receiver address of their choice. In the final step, a timer and current balance are displayed, updating in real-time when the tokens arrive, and a confirmation card shows the updated balance and the amount of reward sent to the Arbitrum wallet. Additionally, the application includes a separate page where users can track their MOR token holdings on Arbitrum without needing to connect their wallets.
This application is built directly on top of the distribution contract, ensuring direct interaction with the contract through our efficient and aesthetically pleasing UI. The streamlined claim process guarantees complete security while providing a seamless user experience.
Links
MOR Rewards Claim App

Thanks for the contribution.


Babel 7 Compatibility

Trying to use Electron-Spellchecker which depends on this results in a failure due to the es2015-node5 babel plugin in the .babelrc
You can solve this by replacing the existing .babelrc for Electron-Remote with the following:
{
  "plugins": ["@babel/plugin-transform-async-to-generator"]
}

@paulcbetts what would be the best (most susttainable and user friendly) approach to supporting Babel 7?

This seems to be resolvable by using a babel.config.js file instead of a .babelrc file.


Bugfix windows have a other default loop now

Description:
Future will have now a other core loop as the default, so it need to set the loop for working now.
Related issue (if applicable): fixes #4194

Fix works great for me :-)


Fix slide on resize

Prevent slide to previous view when isEnd and you resize window

Thanks, i merged it manually, as PR should be made only to the files in dist/ folder without affecting the current stable release


Add #[must_use] to Parser trait

Parsers don't do anything by themselves, so the #[must_use] attribute should probably be applied to them (as with Iterator).

Just checking to see if this can be closed due to #179, or if there is still more work to be done here :)

Ah yep, all good. Thanks for reminding me!


Protogalaxy Verifier

This already exists: https://github.com/AztecProtocol/barretenberg/issues/690


chore: bdd-sbrp-import-1587821622 to 0.0.1

chore: Promote bdd-sbrp-import-1587821622 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Feature Request - Snap Zones

Pickable objects should support being "snapped" into snap-zones. These snap-zones should support being fixed to the environment, or put on the player as pockets.

I liked your video on this! I closed my "holster" issue accordingly.  Not sure if it is in your code but would be good to have a check box in the editor to say whether the object should be hidden or not when placed in the snap zone, e.g., difference between using the snap zone on a "back pack" object that hides it, or using the snap zone on a shoulder holster where you want other players to continue to see the object on your back, like a sword.

Tested in 2.4 release.


Feedback for “Masking”

Hi!
Is it possible to add support for async on the masking function?
We have our own redaction functionality that we'd like to use here, but the current masking function must be synchronous.

thank you!
https://github.com/orgs/langfuse/discussions/3981


abstract linked data key pair classes

We need to implement the interfaces for minimal cipher / linked data proof suite keys...
sign, verify, derive, toKeyPair, toJsonWebKey, etc...

This is almost done, remaining work:

[ ] PGP KeyPair migration
[ ] ld-key-pair updates


TERM signal causes restart, but process not updated with new codebase

I'm following the instructions in DEPLOYING for redeploying my Rails app with Capistrano.
When the restart capistrano task is run, it is executing:
run "killall -u deploy niet"
Niet kicks into action, and sends the TERM signal, which I see in the syslog:
Oct 31 11:55:45 tst-app1 bundle: [Worker(host:tst-app1 pid:9895)] Starting job worker
Oct 31 11:55:45 tst-app1 bundle: [Worker(host:tst-app1 pid:9895)] Exiting...
Oct 31 11:55:45 tst-app1 bundle: bundle finished as requested
Oct 31 11:55:45 tst-app1 bundle: Running bundle```

But the restarted process (delayed job) retains the old codebase. To work around this, I have replaced the start with capistrano restart task with:

```run "while killall -u deploy -QUIT niet; do sleep 1; done"
start```

It's running on Ubuntu 10.04, and I'm initiating the restart with:

```after 'deploy:restart', 'niet:restart'```

Any help would be much appreciated.

Cheers

Nigel

Can you paste your daemon start scripts and command(s)?  I want to check that you're using current_path, not the path to the specific version you just released.

    2.times do
      run "niet -c #{current_path} bundle exec rake jobs:work RAILS_ENV=#{stage}"
    end
  end

I think I see what will be causing this.  -c currently causes a chdir applied just once, when niet starts.  Linux's handling of the current directory acts like a caching with the directory symlinks though.
Let me do some testing and see if this is the same behavior as other unixes.  I think I should probably change -c to chdir every time it spawns, but I'd better make sure it's consistent.

Thanks Will. Niet is pretty awesome. I've found it a lot easier to get going, compared with runit.

Cool, glad to hear it's useful. Thanks for the feedback :).
New version 0.8 should sort you out.


[native_toolchain_c] Support MSVC arm64 toolchain

This PR adds support to be able to compile native-assets on windows-arm64.
It seems to be what is needed to compile windows-arm64 flutter apps, as discussed initially here.
@dcharkes I'm not sure which tests to update exactly. Since windows-arm64 runners are not available for this repository, will we still be able to test this? In more, do existing x64 runners have installed msvc arm64 toolchain?

@dcharkes I'm not sure which tests to update exactly. Since windows-arm64 runners are not available for this repository, will we still be able to test this?

I think we have to rely on you testing this locally inside flutter_tools on an arm64 Windows host.

In more, do existing x64 runners have installed msvc arm64 toolchain?

I wouldn't think so, but you can try adding a test and see if the arm64 executables can be found on the Windows bot.

Ok. Locally I can test this, no problem.
To enable flutter windows-arm64 support, we'll need to have a new version of native_toolchain_c published, so it can be referenced in pubspec.yaml.
I'll try to add a new test here to see if it works on windows-x64 hosts.

Please bump the version in the pubspec and add an entry to the changelog.md for that.

Will do once you're okay with changes and tests are passing.

Updated tests to see how it goes.
I fixed vcvarsX from cl.exe tests which were not testing the right vcvars was found.

(to be squashed)

PRs are squashed on merge in most (or all) of Dart/Flutter repos.

Hm, seems like we have a bunch of failures due to https://github.com/dart-lang/native/pull/161#issuecomment-1782646646.

I have retracted package:native_assets_cli v0.3.1, try pushing a commit.

No problem, I rebased on top of commit parent of this PR.

coverage: 97.985%. first build when pulling 9be1b8f5ed1664805e83c84f957033f5a1d4f47f on pbo-linaro:windows-arm64 into 762b4da07b39def23e84d78dd5967026b3b3217a on dart-lang:main.

Tests were successful, so arm64 toolchain is available on runners :+1:.
Bumped version and added an entry in changelog.

Implemented changes required by open discussions.
I checked built example with native assets create a windows-arm64 dll with expected symbols.
I still have a problem with symbol not being loaded (using flutter test), but I think it's something on flutter side, so this PR should be complete.

See the bots: we have some analysis failures:
      error - lib/src/native_toolchain/msvc.dart:81:11 - The argument type 'dynamic' can't be assigned to the parameter type 'String'. - argument_type_not_assignable
      error - lib/src/native_toolchain/msvc.dart:83:17 - The argument type 'dynamic' can't be assigned to the parameter type 'String'. - argument_type_not_assignable
    warning - lib/src/native_toolchain/msvc.dart:66:9 - The type of fileName can't be inferred without either a type or initializer. Try specifying the type of the variable. - inference_failure_on_uninitialized_variable
       info - lib/src/native_toolchain/msvc.dart:66:9 - An uninitialized variable should have an explicit type annotation. Try adding a type annotation. - prefer_typing_uninitialized_variables

Fixed, final fileName; required explicit typing.

Thanks @dcharkes for quick interactions, that was a fun ride!

Will the new version for native_toolchain_c be published automatically, or do you tag it manually?

I've created a release+tag. It should be published automatically now.

I can use it now, perfect! Thanks

Well, thank you! 🙏


python310Packages.flux-led: 0.28.11 -> 0.28.17

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.flux-led is: "Python library to communicate with the flux_led smart bulbs"
meta.homepage for python310Packages.flux-led is: "https://github.com/Danielhiversen/flux_led"
meta.changelog for python310Packages.flux-led is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
Warning: no invocation of /nix/store/ncw9bpnjx0hdgnvifrkqwf8jsr2y4fdf-python3.10-flux-led-0.28.17/bin/.flux_led-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/ncw9bpnjx0hdgnvifrkqwf8jsr2y4fdf-python3.10-flux-led-0.28.17/bin/flux_led had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 0.28.17 with grep in /nix/store/ncw9bpnjx0hdgnvifrkqwf8jsr2y4fdf-python3.10-flux-led-0.28.17
found 0.28.17 in filename of file in /nix/store/ncw9bpnjx0hdgnvifrkqwf8jsr2y4fdf-python3.10-flux-led-0.28.17

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

3 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.flux_led
python310Packages.flux-led
python39Packages.flux-led

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ncw9bpnjx0hdgnvifrkqwf8jsr2y4fdf-python3.10-flux-led-0.28.17 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ncw9bpnjx0hdgnvifrkqwf8jsr2y4fdf-python3.10-flux-led-0.28.17
ls -la /nix/store/ncw9bpnjx0hdgnvifrkqwf8jsr2y4fdf-python3.10-flux-led-0.28.17/bin

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

3 packages built:

home-assistant-component-tests.flux_led
python310Packages.flux-led
python39Packages.flux-led

Maintainer pings
cc @colemickens for testing.

Result of nixpkgs-review pr 156990 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.flux_led
python310Packages.flux-led
python39Packages.flux-led


named node (pool member) IP address is not changed

Environment

Application Services Version: 3.35.0
BIG-IP Version: <IP_ADDRESS>

Summary
Deployment of the new LTM configuration (with named nodes) based on AS3 rest call is working correctly. But another POST (or PATCH) call changes all required objects correctly, except IP address of existing named pool member (named node). In other words, it is not possible change IP address of the (named) pool member when this pool member (node) exists.
This issue is connected to new feature - named pool members (added in f5-appsvcs v3.35.0)
Steps To Reproduce

Submit the following declaration:

{
    "$schema": "https://raw.githubusercontent.com/F5Networks/f5-appsvcs-extension/master/schema/3.35.0/as3-schema.json",
    "class": "AS3",
    "action": "deploy",
    "persist": true,
    "declaration": {
        "class": "ADC",
        "schemaVersion": "3.35.0",
        "id": "testid",
        "label": "pat declaration v1.0",
        "updateMode": "selective",
        "test-as3-issue": {
            "class": "Tenant",
            "defaultRouteDomain": 5,
            "Shared": {
                "class": "Application",
                "template": "shared",
                "sf_pool1": {
                    "class": "Pool",
                    "remark": "AS3>Shared",
                    "minimumMonitors": "all",
                    "minimumMembersActive": 1,
                    "members": [
                        {
                            "remark": "AS3>Shared",
                            "servicePort": 8080,
                            "adminState": "enable",
                            "serverAddresses": [
                                "<IP_ADDRESS>",
                                "<IP_ADDRESS>"
                            ],
                            "servers": [
                                {
                                    "name": "rserver1",
                                    "address": "<IP_ADDRESS>"
                                },
                                {
                                    "name": "rserver2",
                                    "address": "<IP_ADDRESS>"
                                }
                            ]
                        }
                    ]
                }
            }
        }
    }
}

Everything is deployed correctly. See bigip.conf:
# cat bigip.conf
#TMSH-VERSION: <IP_ADDRESS>

ltm node /test-as3-issue/<IP_ADDRESS>%5 {
    address <IP_ADDRESS>
}
ltm node /test-as3-issue/<IP_ADDRESS>%5 {
    address <IP_ADDRESS>
}
ltm node /test-as3-issue/rserver1 {
    address <IP_ADDRESS>
}
ltm node /test-as3-issue/rserver2 {
    address <IP_ADDRESS>
}
ltm pool /test-as3-issue/Shared/sf_pool1 {
    description AS3>Shared
    members {
        /test-as3-issue/<IP_ADDRESS>%5:8080 {
            address <IP_ADDRESS>
            description AS3>Shared
            metadata {
                source {
                    value declaration
                }
            }
        }
        /test-as3-issue/<IP_ADDRESS>%5:8080 {
            address <IP_ADDRESS>
            description AS3>Shared
            metadata {
                source {
                    value declaration
                }
            }
        }
        /test-as3-issue/rserver1:8080 {
            address <IP_ADDRESS>
            description AS3>Shared
            metadata {
                source {
                    value declaration
                }
            }
        }
        /test-as3-issue/rserver2:8080 {
            address <IP_ADDRESS>
            description AS3>Shared
            metadata {
                source {
                    value declaration
                }
            }
        }
    }
    min-active-members 1
}

Submit another declaration with changed IP addresses (marked):

{
    "$schema": "https://raw.githubusercontent.com/F5Networks/f5-appsvcs-extension/master/schema/3.35.0/as3-schema.json",
    "class": "AS3",
    "action": "deploy",
    "persist": true,
    "declaration": {
        "class": "ADC",
        "schemaVersion": "3.35.0",
        "id": "testid",
        "label": "pat declaration v1.0",
        "updateMode": "selective",
        "test-as3-issue": {
            "class": "Tenant",
            "defaultRouteDomain": 5,
            "Shared": {
                "class": "Application",
                "template": "shared",
                "sf_pool1": {
                    "class": "Pool",
                    "remark": "AS3>Shared",
                    "minimumMonitors": "all",
                    "minimumMembersActive": 1,
                    "members": [
                        {
                            "remark": "AS3>Shared",
                            "servicePort": 8080,
                            "adminState": "enable",
                            "serverAddresses": [
                                "<IP_ADDRESS>",
                                "<IP_ADDRESS>"  << change
                            ],
                            "servers": [
                                {
                                    "name": "rserver1",
                                    "address": "<IP_ADDRESS>"
                                },
                                {
                                    "name": "rserver2",
                                    "address": "<IP_ADDRESS>"  << change
                                }
                            ]
                        }
                    ]
                }
            }
        }
    }
}

Response to this POST (I'm trying also PATCH) is correct (code 200 with correct declaration response):
{
    "results": [
        {
            "code": 200,
            "message": "success",
            "lineCount": 24,
            "host": "localhost",
            "tenant": "test-as3-issue",
            "runTime": 8730
        }
    ],
    "declaration": {
        "test-as3-issue": {
            "class": "Tenant",
            "defaultRouteDomain": 5,
            "Shared": {
                "class": "Application",
                "template": "shared",
                "sf_pool1": {
                    "class": "Pool",
                    "remark": "AS3>Shared",
                    "minimumMonitors": "all",
                    "minimumMembersActive": 1,
                    "members": [
                        {
                            "remark": "AS3>Shared",
                            "servicePort": 8080,
                            "adminState": "enable",
                            "serverAddresses": [
                                "<IP_ADDRESS>",
                                "<IP_ADDRESS>"
                            ],
                            "servers": [
                                {
                                    "name": "rserver1",
                                    "address": "<IP_ADDRESS>"
                                },
                                {
                                    "name": "rserver2",
                                    "address": "<IP_ADDRESS>"
                                }
                            ]
                        }
                    ]
                }
            }
        },
        "class": "ADC",
        "schemaVersion": "3.35.0",
        "id": "testid",
        "label": "pat declaration v1.0",
        "updateMode": "selective",
        "controls": {
            "archiveTimestamp": "2022-03-28T12:55:27.767Z"
        }
    }
}

Above change is applied correctly - it is possible to confirm by  GET https://{{bigip_mgmt}}/mgmt/shared/appsvcs/declare/test-as3-issue, but bigip configuartion is not changed (IP address of 'rserver2' is not changed):
# cat bigip.conf
#TMSH-VERSION: <IP_ADDRESS>

ltm node /test-as3-issue/<IP_ADDRESS>%5 {
    address <IP_ADDRESS>
}
ltm node /test-as3-issue/<IP_ADDRESS>%5 {
    address <IP_ADDRESS>
}
ltm node /test-as3-issue/rserver1 {
    address <IP_ADDRESS>
}
ltm node /test-as3-issue/rserver2 {
    address <IP_ADDRESS>
}
ltm pool /test-as3-issue/Shared/sf_pool1 {
    description AS3>Shared
    members {
        /test-as3-issue/<IP_ADDRESS>%5:8080 {
            address <IP_ADDRESS>
            description AS3>Shared
            metadata {
                source {
                    value declaration
                }
            }
        }
        /test-as3-issue/<IP_ADDRESS>%5:8080 {
            address <IP_ADDRESS>
            description AS3>Shared
            metadata {
                source {
                    value declaration
                }
            }
        }
        /test-as3-issue/rserver1:8080 {
            address <IP_ADDRESS>
            description AS3>Shared
            metadata {
                source {
                    value declaration
                }
            }
        }
        /test-as3-issue/rserver2:8080 {
            address <IP_ADDRESS>
            description AS3>Shared
            metadata {
                source {
                    value declaration
                }
            }
        }
    }
    min-active-members 1
}

(Workaround) When name of named pool member is changed, IP address is also changed:

{
    "$schema": "https://raw.githubusercontent.com/F5Networks/f5-appsvcs-extension/master/schema/3.35.0/as3-schema.json",
    "class": "AS3",
    "action": "deploy",
    "persist": true,
    "declaration": {
        "class": "ADC",
        "schemaVersion": "3.35.0",
        "id": "testid",
        "label": "pat declaration v1.0",
        "updateMode": "selective",
        "test-as3-issue": {
            "class": "Tenant",
            "defaultRouteDomain": 5,
            "Shared": {
                "class": "Application",
                "template": "shared",
                "sf_pool1": {
                    "class": "Pool",
                    "remark": "AS3>Shared",
                    "minimumMonitors": "all",
                    "minimumMembersActive": 1,
                    "members": [
                        {
                            "remark": "AS3>Shared",
                            "servicePort": 8080,
                            "adminState": "enable",
                            "serverAddresses": [
                                "<IP_ADDRESS>",
                                "<IP_ADDRESS>" <<< new ip
                            ],
                            "servers": [
                                {
                                    "name": "rserver1",
                                    "address": "<IP_ADDRESS>"
                                },
                                {
                                    "name": "rserver3",  <<< new name
                                    "address": "<IP_ADDRESS>" <<< new ip
                                }
                            ]
                        }
                    ]
                }
            }
        }
    }
}

bigip.conf is now correcly changed:
# cat bigip.conf
#TMSH-VERSION: <IP_ADDRESS>

ltm node /test-as3-issue/<IP_ADDRESS>%5 {
    address <IP_ADDRESS>
}
ltm node /test-as3-issue/<IP_ADDRESS>%5 {
    address <IP_ADDRESS>
}
ltm node /test-as3-issue/rserver1 {
    address <IP_ADDRESS>
}
ltm node /test-as3-issue/rserver3 {
    address <IP_ADDRESS>
}
ltm pool /test-as3-issue/Shared/sf_pool1 {
    description AS3>Shared
    members {
        /test-as3-issue/<IP_ADDRESS>%5:8080 {
            address <IP_ADDRESS>
            description AS3>Shared
            metadata {
                source {
                    value declaration
                }
            }
        }
        /test-as3-issue/<IP_ADDRESS>%5:8080 {
            address <IP_ADDRESS>
            description AS3>Shared
            metadata {
                source {
                    value declaration
                }
            }
        }
        /test-as3-issue/rserver1:8080 {
            address <IP_ADDRESS>
            description AS3>Shared
            metadata {
                source {
                    value declaration
                }
            }
        }
        /test-as3-issue/rserver3:8080 {
            address <IP_ADDRESS>
            description AS3>Shared
            metadata {
                source {
                    value declaration
                }
            }
        }
    }
    min-active-members 1
}

Expected Behavior
Expected behavior is that IP address of named pool member change without the need for renaming.
Actual Behavior
IP address of the named pool member is not changed. In this case is IP address change possibly only two ways:

(two steps workaround) first delete pool member, then create it with new IP address, or
(one step workaround) pool member re-create with the new name

UPDATE after discussion with f5 support.
Long story short:
The problem is connected with 'design' of NODE. POOL MEMBERS are referenced to NODE. With legacy tools (GUI or tmsh) is not possible to change IP address of the NODE, because it's 'by design'. Explanation: If it were possible to change IP address of NODE, it would affect many other referenced objects (Pools/Pool Members).
This 'design' is here for many years. We can discuss if it's good or not. I think no.
My point of view:
AS3 is declarative model. In other words - what I want (to configure), I will get (configured). In this case it's not valid. Requested change (with named Nodes/Pool Members) is not configured. Moreover, it's confusing because response from the device is code: 200 (OK), message: success and it's not true (all objects - except named nodes are configured).
In this situation, is new feature for naming nodes coming with f5-appsvcs v3.35.0 strongly unusable in NetOps process (automation gets response 200 ok, but it's not true and declarative model is not 'declarative' in this case).
It would be good to make a change:

At first: response from device can't be '200 success', but something other with explanation that the objects (named nodes) are not configured.
Then (preferred and final): change please 'the design' of NODEs with possibility to change IP address. Sure, change will affect other referenced objects, but:

this change may be desirable for lot of administrators (in 'legacy world'),
declarative model remains declarative.

There is also an outstanding bug for config-sync issues and named nodes... https://support.f5.com/csp/article/K16592


Remove global-nav.html

Resolves #473.

I think it is a good idea to offer global nav and footer through styleguide eventually. but currently they are both powered by Mapzen website. Styleguide having it does make some confusions so I will give 👍

Wait - is the plan to actually migrate nav and footer to styleguide? I thought we tried to do that already, (documentation used to pull nav/footer from here, I think) and ended up making repo-specific navs and footers in the end. Do we want to make a point of reversing that?

Developer dashboard has its own header (and I think our ideal plan is making the repo to pull the nav from somewhere central) Documentation & Metroextract is pulling the nav from the website. So I thought this pr was about making that central point to website?

No, this PR was just to remove files that are not being used.
If we want styleguide to be the central location, then I would make another
issue that sets into motion moving the files off the website repo. (Or does
that already exist?)
On Thu, Jun 15, 2017 at 1:56 PM Hanbyul Jo<EMAIL_ADDRESS>wrote:

Developer dashboard has its own header (and I think our ideal plan is
making the repo to pull the nav from somewhere central) Documentation &
Metroextract is pulling the nav from the website. So I thought this pr was
about making that central point to website?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mapzen/styleguide/pull/498#issuecomment-308820157,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACb1tF7dULlIBDOfBEn7rN1QiK5m4usPks5sEXA4gaJpZM4N42k8
.

I said 'making website as a central point' including 'removing not-used files styleguide' (so it is obvious for everybody that nav in styleguide is not used, and the website where other repos pull the nav). Yeah as you said, I don't see now as a timing of changing from where other repos are pulling nav. I left the first comment since I think it makes more sense that styleguide lives with global nav and footer since it controls how it looks?


change components to singletons ?

I wanted to discuss a change that I think could help mithril work more intuitively and work better for componentisation - that is change controllers from being functions to a singleton. View's will obviously stay as functions since they need to be recomputed, but controllers are automatically instantiated by mithril anyway.
So modules will look more like this :

var app = {};

var pages =  [ { url, title } ...  ] ;

//controller
app.controller = {
        pages: pages,
        rotate: function() {
            this.pages.push(this.pages.shift());
        }
}
//view
app.view = function(ctrl) {
    return [
        ctrl.pages.map(function(page) {
            return m("a", {href: page.url}, page.title);
        })
    ];
};

In order to do this - all that's needed is removing the "new" keyboard on the following line
var controller = new module.controller;
I've tried this out and it appears to work for all examples so far. One benefit is that it means that the addition of the code below to the current m.module function means that we can get simple componentization out of the box
		if( arguments.length == 1) {
			// first arg is actually the module
			return root.view(root.controller)
		}

The example from the guide on components then becomes :
//root module
var dashboard = {};

dashboard.controller = {
}

dashboard.view = function(ctrl) {
    return [
        userProfile,
        projectList
    ]
}

Of course the lack of being able to pass options into the controller constructor means that we would have to create factories instead.
Anyway --- I'm quite new to all this --- so entirely possible there's a gaping hole in all of this ^_^ Look forward to hearing your responses.

Wouldn't that prevent controller reuse on the same page?

More importantly, this would prevent lazy loading of controllers in a routing scenario (i.e. this would make controllers for all routes run on page load, which is most likely not what you'd want)

OK --- thanks for the heads up


PR #29 failed to support compile hooks "onsave" on Windows.

My PR #24 got closed, so I fork on my machine, and fixed Windows issue, but I didn't pull upstream after July, 2023.
Here's the diff:
diff --git a/fnl/tangerine/api/compile.fnl b/fnl/tangerine/api/compile.fnl
index 209aada..e3e858f 100644
--- a/fnl/tangerine/api/compile.fnl
+++ b/fnl/tangerine/api/compile.fnl
@@ -133,8 +133,8 @@
   "compiles the current active vim buffer."
   ;; opts { :float boolean :verbose boolean :filename string :globals list }
   (local opts (or ?opts {}))
-  (let [bufname (vim.fn.expand :%:p)
-        sname   (vim.fn.expand :%:t)
+  (let [bufname (env.expand :%:p)
+        sname   (env.expand :%:t)
         target  (p.target bufname)]
     :compile
     (hpcall! #(compile.file bufname target (tbl-merge opts {:filename sname}))
diff --git a/fnl/tangerine/api/eval.fnl b/fnl/tangerine/api/eval.fnl
index 9b376af..db0faeb 100644
--- a/fnl/tangerine/api/eval.fnl
+++ b/fnl/tangerine/api/eval.fnl
@@ -11,6 +11,7 @@
 (local {
   : p
   : fs
+  : env
 } (require :tangerine.utils))

 (local {
@@ -30,7 +31,7 @@

 (lambda get-bufname []
   "returns name of current buffer, parses [No Name] correctly."
-  (let [bufname (vim.fn.expand :%:t)]
+  (let [bufname (env.expand :%:t)]
     (if (not= bufname "") bufname
         :else "[No Name]")))

diff --git a/fnl/tangerine/fennel.fnl b/fnl/tangerine/fennel.fnl
index e34fbdf..02cda5c 100644
--- a/fnl/tangerine/fennel.fnl
+++ b/fnl/tangerine/fennel.fnl
@@ -32,7 +32,7 @@
       (table.insert out (format-path t ext macro-path?)))
     ; rtp dirs
     (each [entry (rtps:gmatch "(.-),")]
-          (local glob (vim.fn.glob (.. entry "/fnl/") 0 1))
+          (local glob (env.glob-list (.. entry "/fnl/") 0 1))
           (each [_ path (ipairs glob)]
                 (table.insert out (format-path path ext macro-path?))))
     :return
diff --git a/fnl/tangerine/utils/env.fnl b/fnl/tangerine/utils/env.fnl
index ff37cf1..2bb037c 100644
--- a/fnl/tangerine/utils/env.fnl
+++ b/fnl/tangerine/utils/env.fnl
@@ -6,7 +6,22 @@
 ;; -------------------- ;;
 ;;        Utils         ;;
 ;; -------------------- ;;
-(local config-dir (vim.fn.stdpath :config))
+(local windows? (= (vim.fn.has "win32") 1))
+
+(lambda cvt-backslash [path]
+  (if windows? (pick-values 1 (string.gsub path "\\" "/")) path))
+
+(local config-dir (cvt-backslash (vim.fn.stdpath :config)))
+
+(lambda expand [...]
+  (cvt-backslash (vim.fn.expand ...)))
+
+(lambda glob-list [...]
+  (icollect  [_ v (ipairs (vim.fn.glob ...))]
+    (-?> v (cvt-backslash))))
+
+(lambda resolve-and-expand [...]
+  (cvt-backslash (vim.fn.resolve (vim.fn.expand ...))))

 (lambda endswith [str args]
   "checks if 'str' ends with one of arr::'args'."
@@ -16,7 +31,7 @@

 (lambda resolve [path]
   "resolves 'path' to POSIX complaint absolute path."
-  (let [out (vim.fn.resolve (vim.fn.expand path))]
+  (let [out (resolve-and-expand path)]
        (if (endswith out ["/" ".fnl" ".lua"])
            (do out)
            (.. out "/"))))
@@ -50,7 +65,8 @@

 (lambda luafmt []
   "returns default lua formatter for ENV."
-  (let [exec  (vim.fn.expand "~/.luarocks/bin/lua-format")
+  (let [exec  (if (= vim.fn.executable "lua-format" 1)
+                  "lua-format" (vim.fn.expand "~/.luarocks/bin/lua-format"))
         width (vim.api.nvim_win_get_width 0)]
     :return [
       exec
@@ -273,4 +289,7 @@
   :get  env-get
   :set  env-set
   :conf env-get-conf
+  : expand
+  : resolve-and-expand
+  : glob-list
 }
diff --git a/fnl/tangerine/utils/path.fnl b/fnl/tangerine/utils/path.fnl
index a2fe0ed..67bb0f4 100644
--- a/fnl/tangerine/utils/path.fnl
+++ b/fnl/tangerine/utils/path.fnl
@@ -17,7 +17,7 @@

 (lambda p.resolve [path]
   "resolves 'path' to POSIX complaint path."
-  (vim.fn.resolve (vim.fn.expand path)))
+  (vim.fn.resolve (env.expand path)))

 ;; ------------------------- ;;
@@ -31,9 +31,9 @@

 (lambda p.transform-path [path [key1 ext1] [key2 ext2]]
   "changes path's parent dir and extension."
-  (let [from (.. "^" (esc-regex (env.get key1)))
-        to   (esc-regex (env.get key2))
-        path (path:gsub (.. "%." ext1 "$") (.. "." ext2))]
+  (let [from (.. "^" (esc-regex (p.resolve (env.get key1))))
+        to   (esc-regex (p.resolve (env.get key2)))
+        path (: (p.resolve path) :gsub (.. "%." ext1 "$") (.. "." ext2))]
        (if (path:find from)
            (path:gsub from to)
            (path:gsub (.. "/" ext1 "/") (.. "/" ext2 "/")))))
@@ -58,7 +58,7 @@
 ;; -------------------- ;;
 (lambda p.goto-output []
   "open lua:target of current fennel buffer."
-  (let [source (vim.fn.expand :%:p)
+  (let [source (env.expand :%:p)
         target (p.target source)]
     (if (and (= 1 (vim.fn.filereadable target))
              (not= source target))
@@ -72,7 +72,7 @@
 ;; -------------------- ;;
 (lambda p.wildcard [dir pat]
   "expands wildcard 'pat' inside of 'dir' and return array of paths."
-  (vim.fn.glob (.. dir pat) 0 1))
+  (env.glob-list (.. dir pat) 0 1))

 :return p

I was patching fs.fnl like PR #29, but we should support compile hooks, to compile fnl to lua "onsave", so you need modify deep down to compile.fnl and eval.fnl, so I put those patched functions to env.fnl.
@Sharparam, hope these codes helps you to make a new PR, my coding skill really sucks and I don't think my patch should get merge to upstream, I'm not a professional programmer anyway.

PR #29 failed to support compile hooks "onsave" on Windows.

I don't know why the onsave hook is not working on your end, here is the code of the hook:
(lambda hooks.onsave []
  "runs everytime fennel files in source dirs are saved."
  (local patterns (vim.tbl_flatten [
    ;; vimrc
    (esc-file-pattern (env.get :vimrc))
    ;; source directory
    (.. (esc-file-pattern (env.get :source)) "*.fnl")
    ;; rtpdirs
    (map #(.. (esc-file-pattern $) "*.fnl")
         (env.get :rtpdirs))
    ;; custom paths
    (map #(.. (esc-file-pattern $) "*.fnl")
         (icollect [_ [s] (ipairs (env.get :custom))] s))
  ]))
  (augroup :tangerine-onsave
    [[:BufWritePost (table.concat patterns ",")] run-hooks]))

There is nothing here that is a POSIX specific, the only thing that could be problematical would be esc-file-pattern which escapes \ from the pattern, I don't know if that's is causing problem:
(lambda esc-file-pattern [path]
  "escapes magic characters from 'path'."
  (pick-values 1
    (path:gsub "[%*%?%[%]%{%}\\,]" "\\%1")))

Try tweaking the esc-file-pattern function and see if that does anything.

After further investigation, It seems like the problem is that env will return resolved paths with os specific separators which is good for io operations but causes issues in autocmd-patterns because:
Note that for all systems the '/' character is used for path separator (even
Windows). This was done because the backslash is difficult to use in a pattern
and to make the autocommands portable across different systems.

It is possible to use |pattern| items, but they may not work as expected,
because of the translation done for the above.

source :h file-pattern

This would be an easy fix as I just need to change resolved path like \foo\baz\bar to /foo/baz/bar if the os is windows.

@UnderCooled Try pulling the git repo and see if #22f5bc7 fixes the issue


Text Not Readable

Running the test game shows text like this:

Thanks for your work

Hi. I wasn't able to replicate the issue from my local machine, but I suspect it's caused by the lack of a set text colour in the default style. I've set it to black now. If you have the time, I would appreciate if you could confirm whether or not this fixed your issue.
Thanks a bunch!

Perrrrrrrfect

Thaaaaank you. I must have a weird theme :D