Install script fails with: main: line 908: http_code: unbound variable

[Enter feedback here]
Currently the bash install script fails on ubuntu bionic and focal docker images:
DOTNET_VERSION=3.1.403
DOTNET_INSTALL_DIR=/usr/local/dotnet/${DOTNET_VERSION}
curl -sfL https://dot.net/v1/dotnet-install.sh | bash -s - --version $DOTNET_VERSION --install-dir ${DOTNET_INSTALL_DIR}

#5 16.67 dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
#5 16.67 dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
#5 16.67 dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
#5 16.67 dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.
#5 16.67
#5 17.70 dotnet-install: Downloading primary link https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.403/dotnet-sdk-3.1.403-linux-x64.tar.gz
#5 27.58 main: line 908: http_code: unbound variable

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a2e484a9-5e0c-eb3e-1413-7b507c4fa07d
Version Independent ID: 5bc7caa5-f1c2-d7d5-fe02-80c65cca9672
Content: dotnet-install scripts - .NET CLI
Content Source: docs/core/tools/dotnet-install-script.md
Product: dotnet-fundamentals
Technology: dotnet-cli
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

verbose run: now with 3.1.405
#5 17.08 dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
#5 17.08 dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
#5 17.08 dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.
#5 17.08
#5 17.08 dotnet-install: Calling: machine_has curl
#5 17.08 dotnet-install: Calling: calculate_vars
#5 17.08 dotnet-install: Calling: get_normalized_architecture_from_architecture <auto>
#5 17.08 dotnet-install: Calling: get_machine_architecture
#5 17.08 dotnet-install: Calling: get_normalized_architecture_from_architecture x64
#5 17.08 dotnet-install: normalized_architecture=x64
#5 17.08 dotnet-install: Calling: get_normalized_os
#5 17.09 dotnet-install: Calling: get_current_os_name
#5 17.09 dotnet-install: Calling: get_linux_platform_name
#5 17.09 dotnet-install: normalized_os=linux
#5 17.09 dotnet-install: Calling: get_specific_version_from_version https://dotnetcli.azureedge.net/dotnet LTS x64 3.1.405
#5 17.10 dotnet-install: Calling: get_specific_product_version https://dotnetcli.azureedge.net/dotnet 3.1.405
#5 17.10 dotnet-install: Calling: machine_has curl
#5 17.85 dotnet-install: specific_version=3.1.405
#5 17.85 dotnet-install: Calling: construct_download_link https://dotnetcli.azureedge.net/dotnet LTS x64 3.1.405 linux
#5 17.85 dotnet-install: Calling: get_specific_product_version https://dotnetcli.azureedge.net/dotnet 3.1.405
#5 17.85 dotnet-install: Calling: machine_has curl
#5 18.09 dotnet-install: Constructed primary named payload URL: https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.405/dotnet-sdk-3.1.405-linux-x64.tar.gz
#5 18.09 dotnet-install: Calling: construct_legacy_download_link https://dotnetcli.azureedge.net/dotnet LTS x64 3.1.405
#5 18.09 dotnet-install: Calling: get_legacy_os_name
#5 18.09 dotnet-install: Calling: get_legacy_os_name_from_platform ubuntu.20.04
#5 18.09 dotnet-install: Distribution specific OS name and version could not be detected: UName = Linux
#5 18.10 dotnet-install: Cound not construct a legacy_download_link; omitting...
#5 18.10 dotnet-install: Calling: resolve_installation_path /usr/local/dotnet/3.1.405
#5 18.10 dotnet-install: InstallRoot: /usr/local/dotnet/3.1.405
#5 18.10 dotnet-install: Calling: install_dotnet
#5 18.10 dotnet-install: Calling: is_dotnet_package_installed /usr/local/dotnet/3.1.405 sdk 3.1.405
#5 18.10 dotnet-install: Calling: combine_paths /usr/local/dotnet/3.1.405 sdk
#5 18.10 dotnet-install: combine_paths: root_path=/usr/local/dotnet/3.1.405
#5 18.10 dotnet-install: combine_paths: child_path=sdk
#5 18.10 dotnet-install: Calling: combine_paths /usr/local/dotnet/3.1.405/sdk 3.1.405
#5 18.10 dotnet-install: combine_paths: root_path=/usr/local/dotnet/3.1.405/sdk
#5 18.10 dotnet-install: combine_paths: child_path=3.1.405
#5 18.10 dotnet-install: is_dotnet_package_installed: dotnet_package_path=/usr/local/dotnet/3.1.405/sdk/3.1.405
#5 18.10 dotnet-install: Zip path: /tmp/dotnet.LVMe9cJGe
#5 18.10 dotnet-install: Downloading primary link https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.405/dotnet-sdk-3.1.405-linux-x64.tar.gz
#5 18.10 dotnet-install: Calling: download https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.405/dotnet-sdk-3.1.405-linux-x64.tar.gz /tmp/dotnet.LVMe9cJGe
#5 18.10 dotnet-install: Calling: machine_has curl
#5 18.11 dotnet-install: Calling: downloadcurl https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.405/dotnet-sdk-3.1.405-linux-x64.tar.gz /tmp/dotnet.LVMe9cJGe
#5 28.00 main: line 908: http_code: unbound variable

Duplicate of https://github.com/dotnet/install-scripts/issues/136.
The product team is already aware of the issue, and has made a fix, which may take a few hours to be published.


generating the tflm build files for mbed breaking with create_tflm_tree.py

Hi Team, am trying the generate the tflm build (2.8.0) to be used with mbed environment using create_tflm_tree.py file and it is breaking with below error.
I used below to generate the build. Not sure how to fix this issue and need inputs on addressing this.
"python3 tensorflow/lite/micro/tools/project_generation/create_tflm_tree.py --makefile_options="TARGET=cortex_m_generic TARGET_ARCH=cortex-m4+fp  OPTIMIZED_KERNEL_DIR=cmsis_nn TARGET_TOOLCHAIN_ROOT=/opt/gcc-arm-none-eabi-9-2020-q2-update/bin/ TARGET_TOOLCHAIN_PREFIX=arm-none-eabi- " tflm-tree
Traceback (most recent call last):
File "tensorflow/lite/micro/tools/project_generation/create_tflm_tree.py", line 303, in
main()
File "tensorflow/lite/micro/tools/project_generation/create_tflm_tree.py", line 293, in main
_copy(src_files, dest_files)
File "tensorflow/lite/micro/tools/project_generation/create_tflm_tree.py", line 124, in _copy
shutil.copy(src, dst)
File "/home/pvasa/.conda/envs/embed_env/lib/python3.8/shutil.py", line 418, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
File "/home/pvasa/.conda/envs/embed_env/lib/python3.8/shutil.py", line 264, in copyfile
with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: 'LICENSE'

Thank you for your interest in TFLM.  I have tested your command line for generating your project using a Ubuntu 18.04 system, and found no errors (the tree was generated successfully).
Did you have a full clone of the tflite-micro repository?  An example of the command to clone the tflite-micro repository is as follows: git clone --depth 1 --single-branch "https://github.com/tensorflow/tflite-micro.git"
This issue will now be closed.  Please feel free to reopen the issue should you wish to add further information.


Added 7 fonts

#61
Added 7 fonts using Calligraphr.
@anushbhatia @smaranjitghose

Can you please attach the screenshots of all the seven fonts

Added screenshots of 5 more fonts
@anushbhatia @smaranjitghose

Is there any further changes still required or is that okay ?
@anushbhatia @smaranjitghose


Add bower.json and tag as 0.2.1

grunt-bower-install (used by Yeoman's generator-angular) infers files paths according to the main property provided in bower.json. Without a main, manual configuration of index.html is required.

+100500


fix(package): Fix high severity vulnerability with<EMAIL_ADDRESS>

Upgrade dependencies to fix high severity vulnerability
Details: https://snyk.io/test/npm/hybrid-crypto-js/
Dependencies:
node-forge: 0.8.5 -> 0.10.0
Vulnerability: https://snyk.io/test/npm/node-forge/
Fixed: https://snyk.io/test/npm/node-forge/0.8.5
Note: version 0.10.0 is a breaking change removing the vulnerable functions.
DevDependencies:
mocha 4.0.1 -> 9.0.0
Vulnerability: https://snyk.io/test/npm/mocha/4.0.1
Fixed: https://snyk.io/test/npm/mocha/9.0.0

Any update on this?


[Select] Improve native validation, autofill, and testability

Closes #20402

[x] I have followed (at least) the PR section of the contributing guide.

@netochaves Thanks!


it works or not.can inuse it for my project

can i use it for my project now

Sure, You can use it, It works
just add my GitHub account in References if found useful.


BUG: Code-review check result is wrong

Hello Team,
I see that the code review check is not providing the right result,

{
"Details": [
"found pr with committer different than author: 1",
"found pr with committer different than author: 2",
"found pr with committer different than author: 9",
"found pr with committer different than author: 33",
"Gerrit code reviews found for 0 commits out of the last 30",
"Prow code reviews found for 0 commits out of the last 4"
],
"Score": 10,
"Reason": "GitHub code reviews found for 4 commits out of the last 4 -- score normalized to 10",
"Name": "Code-Review"
},

Here the pr number 33 is having bhuvi11 as the author and committer, but it is mentioned as different.
Why is it so?
PR for reference

https://github.com/bhuvi11/ecom-service/pull/33/commits

Thanks in advance

The GitHub API returns the committer of the PR as null which leads to Scorecard recognizing author and committer as different. Giving a score of 10 here seems like the wrong behavior. @laurentsimon this is an interesting corner case to look into.

@bhuvi11 thanks for the report!
Can you give me the steps to reproduce the problem (and how the PR was merged)? Example:

Create a branch on the same repo
XXX
etc

I need to figure out why the committer is null and whether we can tweak the message/score.

Hello @laurentsimon,
Sure

I have created a branch called testing
I made a change
I raised a PR and merged it with master

Pull request :

https://github.com/bhuvi11/ecom-service/pull/40

Branch successfully merged

Hello @laurentsimon,
Thanks a lot for the response.
What is that i need to do?

@azeemsgoogle recently updated this code with GraphQl. It may have fixed the problem. Can you run check if the changes have fixed the problem?

Hello @laurentsimon,
I just ran and got this as my result
{
"details":[
"Info: Gerrit code reviews found for 0 commits out of the last 30",
"Info: Prow code reviews found for 0 commits out of the last 5"
],
"score":10,
"reason":"GitHub code reviews found for 5 commits out of the last 5 -- score normalized to 10",
"name":"Code-Review"
}
I believe i got score 10 because code review were done for all the commits? So it is a good case right ?

I think that's incorrect, because you reviewed your own commits.  @azeemsgoogle is there a way to fix this with codeQL? (the value seems to be returned by the server https://github.com/ossf/scorecard/blob/main/clients/githubrepo/graphql.go#L151)

Hello @laurentsimon , So this issue is resolved?

I don't think so. @laurentsimon could you please look into this?
./scorecard --repo=bhuvi11/ecom-service --checks=Code-Review
Starting [Code-Review]
Finished [Code-Review]

RESULTS
-------
Aggregate score: 10.0 / 10

Check scores:
|---------|-------------|--------------------------------|------------------------------------------------------------------------------------------------------------|
|  SCORE  |    NAME     |             REASON             |                                         DOCUMENTATION/REMEDIATION                                          |
|---------|-------------|--------------------------------|------------------------------------------------------------------------------------------------------------|
| 10 / 10 | Code-Review | GitHub code reviews found for  | https://github.com/ossf/scorecard/blob/aa93ac232925102ff71023081932f8630778d2bf/docs/checks.md#code-review |
|         |             | 5 commits out of the last 5 -- |                                                                                |
|         |             | score normalized to 10         |                                                                                |
|---------|-------------|--------------------------------|------------------------------------------------------------------------------------------------------------|


Maya: Vray handling of default aov

Bug
There was a bug when Vray default "beauty" AOV was not handle properly, resulting in invalid publishes of multiple cameras.

It will be better to include resolution of #755 here too.


The page bounces and glitches as the model types if the text box reaches the bottom of page.

Pretty much what the title says haha. Its glitchy as the model types and the whole page bounces up and down!

its down to this mfer not linking the rapid changed while parsing markdown.
https://github.com/nilsherzig/LLocalSearch/blob/1e19940ea5079fdd00e922bf7e7712f79eb9a47b/src/lib/log_item.svelte#L14
While using a slow model you can see how the markdown parser gets confused by the streaming text from time to time (for example everything becomes a heading while an empty list item exists). I think i need to implement some kind of buffer for this. I still want the streaming responses be in rendered markdown. Especially tables look very cool while getting created haha

Ohhhhh gotcha!

I still want the streaming responses be in rendered markdown.

Yes certainly! I think it's really cool too!

i really dont know how to fix the glitching, so i guess i should just debounce the page scrolling?

Thats fine!

nvm i think i got it


Improve on-boarding text

Change the one on the maps tab for the one below
"Aloha user_name
Welcome to the CartoDB Editor.
Drag your data file here to create your first map.
From here, your maps screen, you will be able to create new maps as well as finding the ones you've liked"

It is already done, and the image was updated, closing! :)


remove redundant runnable post

onImageAvailable is called at mBackgroundThread, so no need to post a runnable into its handler.

I signed it!

This sample has been migrated to a new location where we can accept Pull Requests (check README for more information).
As recommended by GitHub, we are closing all issues and pull requests now that this older repo will be archived.
If you still see this issue in the updated repo, please reopen the issue/PR there. Thank you!


Invalid tiff file

I am trying to run minerva-author on a H&E dataset of file type .scn . Since, minerva supports OME-TIFF/SVS formats, I opened the .scn file in QuPath (https://qupath.github.io/) and exported it out as OME-TIFF format. However, I get error on using this TIFF file.

This is what the console log on server says :
(author) vscode ➜ /workspaces/minerva-browser/minerva-author (master ✗) $ python src/app.py
Closing tiff file
Closing mask files
Closing import pool
Closing tiff file
Closing mask files
Closing import pool
Opening file:  /workspaces/minerva-browser/sample003/Untitled.ome.tif
OME  6
'Array' object has no attribute 'values'
Opening file:  /workspaces/minerva-browser/sample003/Untitled.ome.tif

Any suggestions on what could be wrong here ? Any other suggested tool which could be used for compatible file conversion related to minerva ?

I tried some sample files from https://docs.openmicroscopy.org/ome-model/6.0.0/ome-tiff/data.html, thinking that there might be an issue in my conversion process. But these files give similar error.

Further reports of a similar issue have been reported on image.sc thread https://forum.image.sc/t/converting-scn-files-to-16-bit-unsigned-8-bit-integers-ome-tiff-files-for-usage-in-minerva-browser/51857
It looks like it may be due to support only being available for a limited number of pixel types, would it be possible to add support for the full range of possible pixel types?

I have the same issue here too.

Same issue here


WIP: S3 direct uploads

implements S3 direct upload
refactors some form handling logic to be much cleaner
adds comments
adds tests for file deletion

open questions:

should we add a boolean attribute to ProjectDataFile called completed to track if a direct upload has been completed?

Current coverage is 89.87% (diff: 89.88%)

Merging #591 into master will increase coverage by 0.34%

@@             master       #591   diff @@
==========================================
  Files           209        209
  Lines          8303       8352    +49
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           7433       7506    +73
+ Misses          870        846    -24
  Partials          0          0

Diff Coverage
File Path

••••••••   83%
private_sharing/api_views.py

•••••••••• 100%
private_sharing/testing.py

•••••••••• 100%
private_sharing/api_urls.py

Powered by Codecov. Last update f0c8d30...818d8fe


Add Windows support

This issue is meant to track progress on adding support for Windows systems for the following items:

[x] Compile/run the builder via zig build
[ ] Compile/run all examples via zig build -Dexample=[NAME]

[ ] #18

[ ] All example binary/test runs work as expected

[x] #11

Currently, the only example I'm running into issues with is the cross-compilation one from the Build System chapter. This is because the aarch64 binary that is built cannot easily be run on x86 Windows machines.
Windows does not have a binfmt_misc equivalent that I am aware of, but this is being looked into.

Windows support is looking good right now. I abandoned the effort of finding a built-in alternative to the *NIX file command as that seemed to be way more trouble than it was worth.
The best method I could find was using dumpbin.exe from Visual Studio Tools, however that did not seem feasible as it is not available on the system PATH by default, and doing so would cause way too much friction for just one example.


React-form version is not specified in documentation https://react-form.js.org/

Hi. Thanks for your hard work guys.
Tried to find out why validation hook does not work running 2.x version
It'll be really nice to have documentation for each different version, what do you think?

This is kind of a dup of this https://github.com/react-tools/react-form/issues/255 issue so im going to close and we can chat over there but yeah we may deploy the old docs somewhere when we get a chance.


Out of Bounds Write Attempt - Fatal

The assertion
Assert Failed:  (size_t)len < (size_t)sizeof(b->hash)
aborts at src/discord-ratelimit.c:33:.
I believe this is due to DISCORD_ROUTE_LEN being defined as 64 and the
length of the string which is being given to the assertion is 71. The string
generated can be found in the stack trace:
#0  0x00007ffff7d9e34c in __pthread_kill_implementation () from /usr/lib/libc.so.6
#1  0x00007ffff7d514b8 in raise () from /usr/lib/libc.so.6
#2  0x00007ffff7d3b534 in abort () from /usr/lib/libc.so.6
#3  0x00005555555d4e93 in _discord_route_init (adapter=0x55555561a6b0,
route=0x55555580e5ec ":5:applications:%lu:guilds:896679108350722109:commands:%lu:permissions", b=0x555555819520)
at src/discord-ratelimit.c:33
#4  0x00005555555d73e2 in _discord_bucket_get_match (adapter=0x55555561a6b0,
route=0x55555580e5ec ":5:applications:%lu:guilds:896679108350722109:commands:%lu:permissions",
info=0x7fffffffd8c0) at src/discord-ratelimit.c:205
#5  0x00005555555d7c5f in discord_bucket_build (adapter=0x55555561a6b0, b=0x5555556194a0,
route=0x55555580e5ec ":5:applications:%lu:guilds:896679108350722109:commands:%lu:permissions",
info=0x7fffffffd8c0) at src/discord-ratelimit.c:371
#6  0x00005555555d3e28 in _discord_adapter_check_action (adapter=0x55555561a6b0, msg=0x55555561ff50)
at src/discord-adapter.c:810
#7  0x00005555555d4279 in discord_adapter_perform (adapter=0x55555561a6b0) at src/discord-adapter.c:882
#8  0x00005555555cfdbd in on_io_poller_curl (io=0x555555618ec0, mhandle=0x5555556188e0, user_data=0x55555561a6b0)
at src/discord-adapter.c:37
#9  0x00005555555cb38e in io_poller_perform (io=0x555555618ec0) at core/io_poller.c:111
#10 0x000055555555a016 in discord_run (client=0x55555561a600) at src/discord-client.c:353
#11 0x0000555555558888 in main (argc=1, argv=0x7fffffffe808) at wikid.c:78
Source code can be found here: https://github.com/arcnyxx/wikid
Using Concord with latest commit hash fe93008fb7307a74f8fef89c6f51dd322adda634.

Hey, thanks for filing a report.
Does this issue also manifest with the update_deps branch?

No, it does not. It seems that when I updated I got some new warnings about missing function prototypes for the free function. Thanks for the suggestion and sorry for the use of your time.

Alright, glad you could get it fixed! We are in the process of replacing utHash with Antropez's chash, as utHash has some portability issues (particularly on System V C compilers). Nonetheless, the new replacement seems to be much more reliable than utHash.


Upgrade gluegun to 2.0 beta

gluegun is undergoing cleanup, switch over to latest gluegun for optimal code cleanliness.

can finish this out now that https://github.com/infinitered/gluegun/pull/228 is to be!


Add Ansible playbook env. setup wrapper script

The environment executing the test playbooks matters.  Establish a
script to bootstrap a known-good and fixed-version python virtual
environment.  Spell out precise execution requirements in a standard
pip 'requirements.txt' file, including version numbers and hashes.
Upon executing the venv-ansible-playbook.sh wrapper, a virtual
environment is setup and contained within a fixed (or temporary)
directory, with full logs from setup.  If this is to be preserved
across executions, the $WORKSPACE environment variable must be
set and exported beforehand.
Example execution command-line provided in script file
Signed-off-by: Chris Evich<EMAIL_ADDRESS>

@mrunalp This should help address CI environment inconsistencies.  My intention is to utilize this wrapper & requirements.txt inside our CI testing job.  I'll my analysis of the consistency problem in by e-mail.

I am not sure any of us are qualified to review. Looks like a bash script to me. :+1:

I have use virtualenvs before ;) Pinning down versions make sense to make this reproducible :+1:

LGTM


MODIFIED : [Deep Learning Intuitions]

Fixed image link for the course
Added an image compatible for desktop view and mobile view

Hey, can you have a look at https://github.com/Ebazhanov/in-quiz-questions/commit/9d824673787a0d1756a9c6d3d744dde042b0bdc8
changing on: [pull_request, issues] on: [pull_request_target, issues] might fix the failure when there are incoming PRs from forked repo

Hello maintainer, do you want to merge this.
The build fail seems to be due to some issue with the github action.
Let me know if you want me to make some other changes

Also if you planning to maintain the repo, I would like to try out a search feature. There are pretty descent recommendations from the contributors, currently it looks hard to find a specific course


Still get lockout message even with AXES_LOCK_OUT_AT_FAILURE set to False

I have AXES_LOCK_OUT_AT_FAILURE set to False, which does work properly, since I can still log in using valid credentials even when I have passed the failure limit. However, if I have passed the failure limit and enter invalid credentials, then Axes still shows the lockout message (or redirect/template depending on your settings), even though the account isn't actually locked.
If AXES_LOCK_OUT_AT_FAILURE is set to False, then shouldn't Axes also suppress any lockout responses on failed logins?

You are correct, good catch and PR.


Get rid of the toolbar

See: https://github.com/boundlessgeo/sdk/commit/0033e04606a3c819bf9469a490560bdf0dfb8dc6 for the print


[SPARK-43294][BUILD] Upgrade zstd-jni to 1.5.5-2

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Thanks for your review @srowen. I am on vacation and will continue to complete these tasks after May 8th.

发件人: Sean Owen @.***>
发送时间: 2023年5月4日 22:57:27
收件人: apache/spark
抄送: yangjie01; Author
主题: Re: [apache/spark] [SPARK-43294][BUILD] Upgrade zstd-jni to 1.5.5-2 (PR #40962)
@srowen approved this pull request.
Looks OK, just add context about what the update does
―
Reply to this email directly, view it on GitHubhttps://mailshield.baidu.com/check?q=4%2FgpZ9TUEilYD9%2FXl%2F%2FdZ08xybHnY39K5GNnRidojzsXOcQrY4G74%2FtGPWda%2F0bG4rBPHY0ERfSeAWNQe0IWpFuPmjDRr01b0B39Jw%3D%3D, or unsubscribehttps://mailshield.baidu.com/check?q=TboBl7gBc9ssIw%2FYtfvVtyVmwybmo1xowOHIEtt99hxrTkRQwwlxhTAqm6PKe8JFikz38E%2BrBzEwW4wnNg2bfgrGkPmhNQuOrjnb8SXet2ZBamJzhIHTAlf6q8NZ5jsCpAi%2F6Nn5zu0%3D.
You are receiving this because you authored the thread.Message ID: @.***>

The changes are minor:
https://github.com/luben/zstd-jni/compare/v1.5.5-1...v1.5.5-2
I think it's fine.

Thanks @dongjoon-hyun @srowen , I am checking the microbenchmark results and updating this pr later

Since the one failure seems to be flaky one, we can ignore it.
[info] *** 1 TEST FAILED ***
[error] Failed: Total 3638, Failed 1, Errors 0, Passed 3637, Ignored 10, Canceled 2
[error] Failed tests:
[error] 	org.apache.spark.scheduler.HealthTrackerIntegrationSuite

Please make a clean PR.

Please make a clean PR.

OK, Let me make a new one.

@dongjoon-hyun I open a new one : https://github.com/apache/spark/pull/41135


Update .env

missing prefix

Please close this PR, the Nacos jar verison is x.y.z, without prefix v, thanks for your contribution.

fixed


Merge preprocess scripts into Makefile

With merge of #219 only preprocess\generate_consts.py remains. I noticed it does nothing. Could it be dropped?

I'm afraid not, this file generate the const.py file.

I noticed It does nothing in ci. Perhaps we could rename preprocess to scripts and remove it from Makefile?

Sure, go ahead.


Reorder navigation items

The navigation is currently a bit unorganized. This PR reorganizes the items. Links to the pages remain the same.

changing the page to faq.md if necessary.

If the file name is changed, I'd suggest using https://github.com/mkdocs/mkdocs-redirects to ensure old links remain working.


Give CODEOWNERS file an owner in CODEOWNERS

Give the CODEOWNERS file owners.
@RickWinter as per your instructions you and @ronniegeraghty, along with azure-sdk-eng are added to the owners.
When the linter pipeline and github actions have been added to the repository, those owners will also need to be added as part of the same block.

Closing out this one to open a new one targeting the correct branch.


Exophase Blizzard games achievements not Syncing

Hello,
Thank you for the amazing work, really love this plugin!

Problem:  Blizzard games such as world of warcraft and starcraft achievements do not sync properly with the linked and authenticated Exophase account. Achievement stats and completion status appear correctly on the Exophase profile page however the extension only retrieves the achievements without the user info (also achievement images are not retrieved, source is correct and directs to the proper Exophase  page).

I have authenticated the Exophase account from the addon settings tab and made sure I am logging in with the proper credentials.
No warning appears when game achievements are added
I have attempted to remove and then add again the game however the outcome is always the same
After adding the achievements: Right click -> SuccessStory -> Edit -> Causes the error box below

Is it because there are too many?
Thanks again for the great plugin!

Can you post your extension.log?

extension.log file: extensions.log
I removed the extension file and then:

removed achievements from starcraft -> added it using "Add"
removed achievements from wow -> added it using "Add" option -> edit for it to crash

Though this time instead of getting the "Edit" option for starcraft there was refresh and when I clicked it it synched properly. However the same did no happen for wow it remains as is.

Not sure if this can help as well,
I created my Exophase account today and then shortly after synced the blizzard games.

Authentication on Exophase is only to have localized achievements and to have the right match for rarity if your language is not English.
however there is this: #227

Thank you for the help and the amazing work!
Feel free to close this issue!

Can you post your playnite.log?

extensions.log
playnite.log
I installed the 2 recent versions of the plugin though the problem still remains with Wow (same as above, no achievements retrieved and no images).

Nevermind, I am mentally challenged.
I found the new settings opttion to enable the wow achievements. It works perfectly now!!
Thanks so much! Amazing work!


Add iam-role filters to check presence of specific managed policy

For situations where all managed roles must have specific policy attached or highlighting usage of highly critical managed policy (eg. FullAdministrator)

Thanks! looks like travis failed when running sphinx on the doc strings of these filters.

Great, just fixed that up!

thanks @marchen87 before i can merge, would you mind signing our contributor license agreement referenced from our readme, direct link https://docs.google.com/forms/d/19LpBBjykHPox18vrZvBbZUcK6gQTj7qv1O5hCduAZFU/viewform

@kapilt done, please go ahead


Another server crasher with e2 <3

erased link

we know

My bad haha

Enable this https://github.com/wiremod/wire/blob/master/lua/entities/gmod_wire_expression2/init.lua#L615
this is the only way to fix it currently
it's off by default because it might give false positives


Get all notes on the current page

Only get the results that are shown in the page

[ ] figure out how to get the 8(or so) note elements on the note list sidebar
[ ] figure out how to select the date on each sidebar note element
[ ] figure out how to convert date string in sidebar note element to epoch timestamp
[ ] figure out how to click each sidebar note element to trigger changing of the main note page/element
[ ] figure out how to select the title on main note element
[ ] figure out how to select the body on main note element
[ ] append timestamp, title and body into an array

Result should be saved in a variable that looks like
[
{
'timestamp':<PHONE_NUMBER>814,
'title': 'this is a title that can also be blank',
'body': '
http://m.yes24.com/Goods/Detail/91231989

Green course

http://m.yes24.com/Goods/Detail/66924896
'
},
{
'timestamp':<PHONE_NUMBER>815,
'title': 'this is another title',
'body': '
this is a body'
},
]

Hints:

figure out what the selector should be to get the sidebar note elements and select with document.getElementsByClassName
Get datetime by using document.getElementsByClassName on selected sidebar element
convert datetime to epoch timestamp by using momentjs
You can use momentjs inside the console by running fetch('https://momentjs.com/downloads/moment.min.js')  .then(response => response.text())  .then(text => eval(text))
convert date time string into datetime object by running moment('3/21 12:12', 'MM/DD HH:mm').toDate().getTime()
after getting the time, click on the sidebar obj by running .click() on the element
get title by selecting the main note object, selecting the input tag using getElementsByTagName('input')[0] and checking the value
select the body of the note by getting the classname of the editor and get innerHTML
save inner html and title to the object
go to the next sidebar object and repeat until you run out


Unable to show \{

When using mathjax, \{ is unable to produce {...
Below is the configuration:

MathJax.Hub.Config({
  config: ["MMLorHTML.js"],
  extensions: ["tex2jax.js"],
  jax: ["input/TeX"],
  tex2jax: {
    inlineMath: [ ['$','$'], ["\\(","\\)"] ],
    displayMath: [ ['$$','$$'], ["\\[","\\]"] ],
    processEscapes: false
  },
  TeX: {
    extensions: ["AMSmath.js", "AMSsymbols.js"],
    TagSide: "right",
    TagIndent: ".8em",
    MultLineWidth: "85%",
    equationNumbers: {
      autoNumber: "AMS",
    },
    unicode: {
      fonts: "STIXGeneral,'Arial Unicode MS'"
    }
  },
  showProcessingMessages: false
});

Thanks!

I'm unable to reproduce this.$\{$ works fine for me, e.g., in https://cdn.rawgit.com/mathjax/MathJax/2.7.2/test/sample-dynamic-2.html.
You might want to post a complete example, e.g., using jsbin.

@pkra Thanks for your reply. Hmm, this is weird. When I paste the following line to the test html you posted and change to Mathjax 2.7.1 (https://cdn.rawgit.com/mathjax/MathJax/2.7.1/test/sample-dynamic-2.html), it works fine. Even I fork this repo, and change that test page to my config, it still works fine. This is weird... https://github.com/yxliang01/MathJax/blob/master/test/sample-dynamic-2.html
Formula $ \{C_1, C_2\} $ represents $ C_1 \land C_2 $

You may want to have a look at https://github.com/yxliang01/UnimelbSharedFiles/blob/master/Models of Computation/MoC-summary.html
All \{ and \} don't work...

All \{ and \} don't work...

There's no \{ in the page's HTML source. I'm guessing you're using markdown and the HTML conversion is stripping out backslashes. This is a well known issues with (some) markdown processors; you'll either need to escape the backslash or find out if your markdown processor has other means of protecting TeX input.
FWIW, this problem is documented in http://docs.mathjax.org/en/latest/tex.html#tex-and-latex-in-html-documents.

All \{ and \} don't work...

There's no \{ in the page's HTML source. I'm guessing you're using markdown and the HTML conversion is stripping out backslashes. This is a well known issues with (some) markdown processors; you'll either need to escape the backslash or find out if your markdown processor has other means of protecting TeX input.
FWIW, this problem is documented in http://docs.mathjax.org/en/latest/tex.html#tex-and-latex-in-html-documents.

well-spoted @pkra . However, in the file https://github.com/yxliang01/UnimelbSharedFiles/blob/test-mathjax/Models of Computation/MoC-summary.html , I added \ to the html source code manually. But, now the formula can't be displayed...
Thanks!

The only expression including \{ is $ p : D^n \rightarrow \{f, t} $, which is invalid TeX, since the closing brace } has no matching open brace {.  Try $ p : D^n \rightarrow \{f, t\} $ instead.

(Also, the : should be \colon to get the spacing correct, but that is a different issue.)

Oh! @dpvc Right! Thank you all! Problem solved! Very appreciated! :)


Ensure Umpire usage is correctly guarded in Axom

@rhornung67 observed that there are several places in the code that are not properly guarded against Umpire not being present in configurations that have RAJA but not Umpire.
We can test this by using a configuration with RAJA that does not have Umpire.

I think I addressed this in https://github.com/LLNL/axom/pull/983 but we're not testing this in our CI.
Perhaps we should add an extra CI test to catch regressions?

Add a test, not build another configuration to test.

@rhornung67 , @kennyweiss , my understanding is that we want RAJA and Umpire to both be optional dependencies for Axom, independent of each other.  That is, we want to support RAJA+Umpire, RAJA, Umpire, and neither.  Correct?

I think that is correct. I don't know which projects want to use the various combinations, however.


New name proposal

As we discussed some time ago with @justinwoo, the name of this repo/program has a bit of a name clash with the spacchetti package set repo, and this is super confusing.
So I'd like to propose a new name for this repo and tool: spago
(IPA: /ˈspaɡo/)
Why?

It means "twine" in Italian, and it would symbolize the new role of this tool (well at least after #21), to "tie everything together"
It is different than spacchetti
It kind of reminds of it at the same time (they have the same root)
It is actually shorter to type at the command line, but unique enough

Sample image to visualize it:

@nwolverson what do you think of this name change?

What I'm the arbitrer of taste now? It's a name, I can probably find it by tab completing => ok!


build(JitPack): Disable signing for JitPack snapshort builds

Signing is not set up for JitPack, so simply disable it as these are just snapshot builds.

The build log should soon be available at https://jitpack.io/com/github/oss-review-toolkit/ort/jitpack-no-sign-SNAPSHOT/build.log.

Unfortunately, this does not work for unknown reasons.

@sschuberth :
How about we put a condition in ort-publication-conventions.gradle.kts
if (project.property("SIGN_PUBLISHED_ARTIFACTS") == true) {
       signAllPublications()
}

Set it to true in gradle.properties and override it to false in jitpack.yml ?

How about we put a condition in ort-publication-conventions.gradle.kts

I don't believe that's going to help as signing is built into the plugin we use.

Yes I saw this code but I am not sure it's relevant, as setting RELEASE_SIGNING_ENABLED to false didn't disable the signing as expected.
Anyway putting the code I mentionned earlier and
./gradlew --no-daemon --stacktrace -x dokkatooGeneratePublicationJavadoc -PSIGN_PUBLISHED_ARTIFACTS=false publishToMavenLocal in jitpack.yml doesn't  trigger the signing error anymore.

I am not sure it's relevant, as setting RELEASE_SIGNING_ENABLED to false didn't disable the signing as expected.

Right, but this is the only place where the plugin calls signAllPublications(). So I assume it's always called, and for some reason setting the surrounding condition to false does not work.

doesn't cause the signing error anymore.

That doesn't make any sense to me. Setting -PSIGN_PUBLISHED_ARTIFACTS=false should have the same effect as not adding the code you propose at all, which is the same state that we have now, so why should the signing error go away then suddenly?

That doesn't make any sense to me.

Ah! We already have signAllPublications() in our code! That's the issue. That should go away completely, as we should rely on the plugin functionality here.


Install with npm is failing due to not finding cdk which does exist

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v16.4.1
Amplify CLI Version
N/A
What operating system are you using?
Mac
Amplify Categories
storage
Amplify Commands
status
Describe the bug
The installer with npm keeps failing. I've updated node to the latest version and tried again. I have manually deleted the current amplify and cdk files. This command keeps failing.
> npm install -g @aws-amplify/cli
npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path /Users/stehlib/.npm-global/lib/node_modules/@aws-amplify/cli/node_modules/aws-cdk/bin/cdk
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/stehlib/.npm-global/lib/node_modules/@aws-amplify/cli/node_modules/aws-cdk/bin/cdk'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

Expected behavior
The npm install shown in the docs should complete successfully.
Reproduction steps

npm install -g @aws-amplify/cli
Look for the error

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

@brennanMKE npm install is working for me. Some things you can try:

sudo npm i -g @aws-amplify/cli -- in general sudo npm install ... isn't recommended, but depending on how you have npm configured it's sometimes necessary
Check that the global installation location is owned by the current system user. The global installation location can be found using npm root -g
As a last resort, try reinstalling node & npm

In my ~/.npmrc I have just 1 line.
prefix=~/.npm-global

I never run npm with sudo since it should have access to install files in ~/.npm-global which I have added to my PATH. I've updated the latest version of node already. I also ran npm -g cache clean --force and npm cache clean --force and tried the install again. It keeps failing with the same error.
Why is this chmod command failing with cdk? I am able to confirm the path exists after the install fails.

Resolved offline by upgrading to the latest version of npm. Closing this issue.


Popover appears to assume it will be invoked from NavBar

Ionic version:  (check one with "x")
[ ] 1.x
[ x] 2.x
I'm submitting a ...  (check one with "x")
[ x] bug report
[ x] feature request
[ ] support request => Please do not submit support requests here, use one of these channels:
Current behavior:
I invoke a popover from a parent element that is NOT that nav bar.  From a card for example.  When doing so the popover aligns itself over the icon that invoked it and the arrow does not display but is actually in the middle of the page ( and yes the event is being passed in properly )
Expected behavior:
I would expect  the popover to render with arrow underneath whatever element I attached it to.
Steps to reproduce:
Create an ion-card with an ion-card-header that has a button to invoke a popover

Thanks for the issue! Could you provide some code, a repository, or a plunker that we can use to reproduce this? I'm not able to reproduce it in our tests:

Hello all! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!


feat: add duptable support for reth db get

Closes #2836

Tables:
    (TableType::DupSort, PlainStorageState::const_name()),
    (TableType::DupSort, AccountChangeSet::const_name()),
    (TableType::DupSort, StorageChangeSet::const_name()),
    (TableType::DupSort, HashedStorage::const_name()),
    (TableType::DupSort, StoragesTrie::const_name()),

Right now it works this way:
reth db get-dup <table> <key> <subkey>

Codecov Report

Merging #2897 (8d45e47) into main (b03208c) will decrease coverage by 53.80%.
The diff coverage is 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##             main    #2897       +/-   ##
===========================================
- Coverage   71.16%   17.36%   -53.80%
===========================================
  Files         513      515        +2
  Lines       66470    66778      +308
===========================================
- Hits        47301    11595    -35706
- Misses      19169    55183    +36014

Flag
Coverage Δ

integration-tests
17.36% <0.00%> (-0.07%)
:arrow_down:

unit-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

bin/reth/src/db/get.rs
0.00% <0.00%> (-50.50%)
:arrow_down:

bin/reth/src/db/mod.rs
0.00% <0.00%> (-9.10%)
:arrow_down:

bin/reth/src/utils.rs
0.00% <0.00%> (-5.89%)
:arrow_down:

... and 372 files with indirect coverage changes

Thanks for the review. Just to note: there is this pr: https://github.com/paradigmxyz/reth/pull/2935 which needs to be merged before merging this one since it changes a few things related to this pr

what I'm looking at right now is how to generate the view_dupsort function inside the same macro, but only for DupSort table type. Since that function would need to have type view_dupsort. I'm looking into the macro's identifiers, and expressions but still struggling to do it correctly


feat: update config.json and add hello-world exercise

@ErikSchierboom
I made some changes to add the first exercise but I'm stuck on the Setup Continuous Integration step, I know how to use GitHub Actions, I know how CI/CD works, and I know how Unix works, but the problem is that I don't know how to go about testing it.
https://github.com/exercism/batch/issues/1

@kotp Should I merge it now or wait for Erik to see it?

@kotp Should I merge it now or wait for Erik to see it?

I would wait for 2 more approvals, if possible, and not rush it really.  Erik will see it and recognize anything that he knows to look for in terms of construction and organization in terms of the platform.  Otherwise may know to look for Batch Script specific things, others will look at content and understanding in other ways.

@kotp Should I merge it now or wait for Erik to see it?

I would wait for 2 more approvals, if possible, and not rush it really. Erik will see it and recognize anything that he knows to look for in terms of construction and organization in terms of the platform. Otherwise may know to look for Batch Script specific things, others will look at content and understanding in other ways.

I will take your advice and wait for Erik's guidance, I am in no hurry, it is more important to move forward correctly.

Don't worry about that, I'm happy to help. Let's first focus on getting this PR merged, then on creating a basic test runner and then I can do the CI bit for you.

Thanks you, I'm currently focused on this PR. <3


Allow users to sign in again from switch network modal

:tada: This PR is included in version 1.24.0-dev.15 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.27.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update package versions related to MPI build matrix

Packages need to be listed twice to get the right pinnings from conda-smithy.  netcdf-cxx-legacy and tempest-remap have now been build with the appropriate versions of libnetcdf and hdf5, so
they are also pinned for consistently.

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [87]

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you but ran into some issues, please ping conda-forge/core for further assistance. You can also try re-rendering locally.

@conda-forge-admin, please rerender


Remove operators from the init file and make sure they are loaded when setting up the anonymizers and deanonymizers dictionaries.
Add dynamic add of operators, so when someone is using the python package, he can access the anonymizer/deanonymizer engine and add_anonymizer/deanonymizer and remove_anonymizer/deanonymizer

I wonder why we can't have something like this by default. Plugging a new operator shouldn't require having your own fork.

@djejaquino I agree. A workaround (without having to fork) is to use custom operators. See this as an example
Having said that, it is on our roadmap, just no ETA.


feat: support normalizing Ds\Collection

When I use transformers
(new \CuyZ\Valinor\MapperBuilder())
    ->registerTransformer(fn (\Ds\Set $v) => $v->toArray())
    ->registerTransformer(fn(Value $v) => $v->get())
    ->normalizer(\CuyZ\Valinor\Normalizer\Format::json())

My \Ds\Set<Value> is normalized to array<Value> but the Value is then ignored since the serialization is not recursive for the Set.
This fixes it.
Initially, I wanted to make this work for all IteratorAggregates and Iterators but with then 'iterable class' case does not pass since it is designed to serialize its properties and not inner Iterator.

Thanks @simPod! I've decided to change the behavior regarding iterable objects, which fixes the issue you had with Ds\Collection objects, or any other collection objects. 🙂

Awesome!

@simPod Hi! Would you have a real-life example of why this feature would be needed? 😊

E.g. serde of a ds map:
use \Ds\Map;

/** @var Map<list<int>, string> */
$m = new Map();
$m->put([1], 'le value');
$m->put([1, 2], 'le value2');

$normalizer->normalize($m);

or just a simple generator yield [1]=>'le value'


Connection types for dynamic schema

Hi, is it correct that I'll have to reimplement all the connection types for dynamic schema, doesn't look like I'll be able to use what's already there? https://github.com/async-graphql/async-graphql/tree/master/src/types/connection

Yes, you need to implement them yourself.😀

Thanks for confirming ser!


addTool in Relay Server Appears to Never Trigger Tool Handlers

Description
We are trying to use the addTool function in the relay server's instance of RealtimeClient, but it seems the tool handlers are never triggered when the tool is invoked. Instead, the tool logic appears to be bypassed entirely.
Here's a minimal code example demonstrating the issue:

Code Example
import { WebSocketServer, WebSocket } from "ws";
import { RealtimeClient } from "@openai/realtime-api-beta";
import { personalInstruction } from "../constants/personalInstruction";

export type RealtimeEvent = {
  type: string;
  [key: string]: unknown; // Allow for additional properties in the event object
};

export class RealtimeRelay {
  private apiKey: string;

  private wss: WebSocketServer | null;

  constructor(apiKey: string) {
    this.apiKey = apiKey;
    this.wss = null;
  }

  listen(port: number): void {
    this.wss = new WebSocketServer({ port });
    this.wss.on("connection", this.connectionHandler.bind(this));
    this.log(`Listening on ws://localhost:${port}`);
  }

  private async connectionHandler(
    ws: WebSocket,
    req: { url?: string; headers: { host?: string } },
  ): Promise<void> {
    if (!req.url) {
      this.log("No URL provided, closing connection.");
      ws.close();
      return;
    }

    const url = new URL(req.url, `http://${req.headers.host}`);
    const { pathname } = url;

    if (pathname !== "/") {
      this.log(`Invalid pathname: "${pathname}"`);
      ws.close();
      return;
    }

    // Instantiate new client
    this.log(`Connecting with key "${this.apiKey.slice(0, 3)}..."`);
    const client = new RealtimeClient({ apiKey: this.apiKey });

    client.addTool(
      {
        name: "get_weather",
        description: "Retrieve weather information for a given location.",
        parameters: {
          type: "object",
          properties: {
            location: {
              type: "string",
              description: "Name of the location to retrieve weather for.",
            },
          },
          required: ["location"],
        },
      },
      async ({ location }: { location: string }) => {
        console.log("get_weather tool called with location: ", location);
      },
    );

    client.updateSession({
      instructions: personalInstruction,
      input_audio_transcription: { model: "whisper-1" },
      turn_detection: { type: "server_vad" },
      tool_choice: "required",
    });

    // Relay: OpenAI Realtime API Event -> Browser Event
    client.realtime.on("server.*", (event: RealtimeEvent) => {
      this.log(`Relaying "${event.type}" to Client`);
      ws.send(JSON.stringify(event));
    });
    client.realtime.on("close", () => ws.close());

    // Relay: Browser Event -> OpenAI Realtime API Event
    const messageQueue: string[] = [];
    const messageHandler = (data: string) => {
      try {
        const event = JSON.parse(data) as { type: string };
        this.log(`Relaying "${event.type}" to OpenAI`);

        if (!client.isConnected()) {
          throw new Error("RealtimeClient is not connected");
        }

        client.realtime.send(event.type, event);
      } catch (e) {
        const error = e instanceof Error ? e.message : "Unknown error";
        console.error(error);
        this.log(`Error parsing event from client: ${data}`);
        this.log(`Error processing message from client: ${error}`);
      }
    };

    ws.on("message", (data: string | Buffer) => {
      const message = typeof data === "string" ? data : data.toString();
      if (!client.isConnected()) {
        messageQueue.push(message);
      } else {
        messageHandler(message);
      }
    });

    ws.on("close", () => {
      this.log("WebSocket closed. Disconnecting client...");
      messageQueue.length = 0; // Clear the message queue
      return client.disconnect();
    });

    // Connect to OpenAI Realtime API
    try {
      this.log(`Connecting to OpenAI...`);
      await client.connect();
    } catch (e) {
      const error = e instanceof Error ? e.message : "Unknown error";
      this.log(`Error connecting to OpenAI: ${error}`);
      ws.close();
      return;
    }

    this.log(`Connected to OpenAI successfully!`);
    while (messageQueue.length) {
      const message = messageQueue.shift()!;
      if (client.isConnected()) {
        messageHandler(message);
      } else {
        this.log("Client disconnected. Re-queuing message.");
        messageQueue.unshift(message); // Re-queue the message
        break; // Exit the loop until reconnection
      }
    }
  }

  public async testConnectionHandler(
    ws: WebSocket,
    req: { url?: string; headers: { host?: string } },
  ): Promise<void> {
    await this.connectionHandler(ws, req);
  }

  // eslint-disable-next-line class-methods-use-this
  private log(...args: unknown[]): void {
    console.log(`[RealtimeRelay]`, ...args);
  }
}

Expected Behavior
When the get_weather tool is invoked, the handler defined in addTool should be triggered, and its logic (e.g., logging "get_weather tool called with location: ") should execute.

Observed Behavior
The tool appears to be registered, but its handler is never triggered when the tool is called.

Questions

Is this behavior expected?
Should addTool be supported in relay server environments, or is there a limitation in how tools are executed server-side?
Is there a specific configuration required to enable addTool in the relay server?

Thank you for looking into this! Let me know if additional details or test cases are needed.

I previously reported an issue where tools registered using addTool in the server-side context (via the relay server's instance of RealtimeClient) were not triggering their handlers when invoked. I followed up with a patch as per the approach mentioned [here](https://github.com/openai/openai-realtime-api-beta/issues/14#issuecomment-2395041263).

Steps Taken

Installed patch-package:

Command: npm i patch-package --save-dev.
Added @openai+realtime-api-beta+0.0.0.patch to the patches folder.
Updated package.json with the "postinstall": "patch-package" script.

Applied the patch:

This resolved the issue for tools registered via addTool when invoked from the client side.

Persisting Issue

When addTool is used on the server side, the tool's handler is not triggered.

However, if the tool description (not the function) is added client-side in the updateSession call, the server-side handler for the tool begins to work. Example:
client.updateSession({
    turn_detection: { type: 'server_vad' },
    tool_choice: 'auto',
    tools: [
        {
            type: 'function',
            name: 'get_weather',
            description: 'Retrieve current weather information for a given location.',
            parameters: {
                type: 'object',
                properties: {
                    lat: {
                        type: 'number',
                        description: 'Latitude of the location.',
                    },
                    lng: {
                        type: 'number',
                        description: 'Longitude of the location.',
                    },
                    location: {
                        type: 'string',
                        description: 'Name of the location.',
                    },
                },
                required: ['lat', 'lng', 'location'],
            },
        },
    ],
});

Adding only the description client-side appears to "activate" the tool's functionality server-side.

Next Steps
Could you provide clarification on the expected behavior for server-side tool registration using addTool? Additionally, any insights on resolving this issue without needing redundant client-side updates would be helpful.
Thank you for your support!


App Startup Time Benchmarks

Per discussion https://github.com/facebook/react-native/issues/19297, let's use this thread to post startup time metrics. The big hope is that Fabric and turbo modules will speed things up significantly.
To standardize our metrics, let's use the following code snippets:
AppDelegate.m
#import "AppDelegate.h"

#import <React/RCTLog.h>  //Import RCTLog
#import <React/RCTBridge.h>
#import <React/RCTBundleURLProvider.h>
#import <React/RCTRootView.h>

extern CFAbsoluteTime StartTime; //Declare start timestamp

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{

  RCTSetLogThreshold(RCTLogLevelInfo - 1);   //Print all logs to stdout, even on production

  NSDictionary *props = @{@"starttime" : @(StartTime)};   //Generate start timestamp

  RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:launchOptions];

  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"testapp"
                                            initialProperties:props];   //Pass to App.js props

  rootView.backgroundColor = [[UIColor alloc] initWithRed:1.0f green:1.0f blue:1.0f alpha:1];

  self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
  UIViewController *rootViewController = [UIViewController new];
  rootViewController.view = rootView;
  self.window.rootViewController = rootViewController;
  [self.window makeKeyAndVisible];

  return YES;
}

- (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
{
#if DEBUG
  return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
#else
  return [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif
}

@end

MainActivity.java
package com.testapp;

import com.facebook.react.ReactActivity;
import com.facebook.react.ReactActivityDelegate;
import android.os.Bundle;
import android.util.Log;

public class MainActivity extends ReactActivity {

    private long starttime = System.currentTimeMillis();  //Start timestamp

    @Override
    protected String getMainComponentName() {
        return "testapp";
    }

    @Override
    protected ReactActivityDelegate createReactActivityDelegate() {
      return new ReactActivityDelegate(this, getMainComponentName()) {
        //Pass to App.js props
        @Override
        protected Bundle getLaunchOptions() {
          Bundle initialProperties = new Bundle();

          initialProperties.putSerializable("starttime", starttime);
          return initialProperties;
        }
      };
    }
}

In App.js, end the timer with the first  onLayout callback rather then render.
App.js
import React from 'react';
import { Text, View, StyleSheet, Platform } from 'react-native';

export default class App extends React.Component {
  async componentDidMount() {
    console.info(`${Date.now() - this.getStarttime()} ms to data loaded`);
  }

  getStarttime() {
    const { starttime } = this.props;
    //Convert CFAbsoluteTime to unix timestamp on ios...
    return Platform.OS === 'ios'
      ? Math.round(starttime * 1000 +<PHONE_NUMBER>00)
      : starttime;
  }

  logTimeToInteractive = () => {

    console.info(
      `${Date.now() -
        this.getStarttime()} ms to application paint`,
    );
  };

  render() {
    return (
      <View style={styles.container} onLayout={this.logTimeToInteractive}>
        <Text>Test startup time</Text>>
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: {
    marginTop: 100,
    justifyContent: 'center',
  },
  text: {
    fontSize: 40,
    textAlign: 'center',
  },
});

On RN 59, these are the metrics I got

Phone
Approx. Start Time

iPhone SE
~250ms

Huawei Honor 7x (Kirin 659/3GB/8.0)
~550ms

Please, only post metrics from real devices running the latest version of RN with production builds.
Also, please ensure you have no native dependencies in your app. Just the bare React Native app.

Thanks for creating this issue. Because it isn't actionable on it's own, I'm going to set it to the closed state but feel free to keep discussion app startup time here and share your findings. I'm happy to reopen if it translates into actionable tasks for changes for RN.

Hey Christoph, I actually think it would likely be best if this issue was reopened. I'll rename the issue title to "Achieve startup time parity on Android". Performance is a feature and for many users this is strongly lacking feature in React Native.
It sounds like amazing things are happening in React Native core, which among other things should increase app startup performance. So let's keep this open until Android achieves parity with iOS or some acceptable threshold of performance.

i think @scottmas brings up a good point. Android engineers tends to not like RN because the of these performance. @cpojer I understand that issues should have actionable tasks. But is there anyway we can keep this issue visible and the community is aware of this?


As a developer, I would like to have a checklist to use when reviewing a change

For example:

If fields are added, were they added to the right fieldsets, layouts, profiles in template, etc

https://developer.salesforce.com/blogs/engineering/2015/05/developer-practices-checklist.html
good developer checklist we might want to use or incorporate.

**lurch: attach W-007264

Tracking W-007264


Add 'dev' script

Adds a dev script to improve the internal developer experience of magic-js packages.

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


nixos: add "systemd" udev TAG to /dev/{kvm,sev}

Description of changes
Add the "systemd" udev TAG to the KVM and AMD SEV devices to allow adding dependencies on the devices in systemd units.
See systemd.device(5) for details:

systemd will dynamically create device units for all kernel devices that are marked with the "systemd" udev tag. [...] To tag a udev device, use "TAG+="systemd"" in the udev rules file, see udev(7) for details.

Example
{
  systemd.services."test-example" = {
    after = [ "dev-kvm.device" ];
  };
}

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

cc @NixOS/systemd

Do other distributions do this too?

Honestly, I don't know.

Expanding the quote from above:

systemd will dynamically create device units for all kernel devices that are marked with the "systemd" udev tag (by default all block and network devices, and a few others)

I propose opening an issue upstream, I don't see a reason to whydev-kvm.device couldn't be part of these "few others". Configuring this only downstream in NixOS won't fix it in other places.

Fine for me, thanks for taking the time to look into it!


Added posibility to change 'label' settings for regression line

'label' setting possibility was missing so i added it in case if anyone would not want text to be displayed below the line (just like me)

Thanks !
Did you test the case of default {} value for the label ?

Sure, you can check it here. https://codepen.io/pbanas/pen/vYOGVEE
Only thing i realized is that i missed is that readme needs to be updated too


Skip hash tests in the dev environment:

Overview
This module was imported (see 4725ab9e for details), and rarely
changes.
These tests will no longer run on mvn test, but still will on
./run_all_tests.sh or mvn test -P ci-build.

See: https://jira.bf.local/browse/ECR-XYZ
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage remained the same at 86.581% when pulling 58047c93a930b7db825497a679c8d1d9dded8177 on dmitry-timofeev:skip-hash-tests into e9dd5508f491babb0cb856b49117ff5e82385162 on exonum:master.


typo ('were' instead of 'where')

[Enter feedback here]
Fourth line of the Message Submission Format block should start with 'where'

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e53205b5-8850-42b6-0b0c-8a61b7ef7776
Version Independent ID: 0a9e7903-ce3c-e877-e6b3-b45d09642308
Content: User submissions policies - Office 365
Content Source: microsoft-365/security/office-365-security/user-submission.md
Service: o365-seccomp
GitHub Login: @chrisda
Microsoft Alias: chrisda

@yeezus24, I fixed it. But in the future, you can make updates like this directly without opening a GitHub issue first. For more information, see https://github.com/MicrosoftDocs/microsoft-365-docs/blob/public/README.md.
Thanks for the feedback.
Closing


threading plugin feature request: allow to replace the threading backend

As I understand it the threading plugin uses pthreads for thread management. This means that in software that uses OpenMP for threading there may be a clash between OpenMP's understanding of how many threads are being used and pthreads' understanding of the same, resulting in overallocation of threads compared with the available number of virtual CPUs.
It would be nice to be able to replace the threading backend in a similar manner to what FFTW does (documentation at the bottom of this page).

OpenMP takes a completely different approach, you mark parts of your code as able to be parallelized and the compiler does the job. Using pthreads or win32 API is a low level operation where you control all threading. The architecture of plug-in is based on having control on threads and cores. On the other hand OpenMP and pthreads can coexist. The plug in allows you to specify how many thereads it will use at most at init time. Regarding to replacing the threading backed, I put it on the wish list.

Thank you :pray:


fix(build): avoid build failures and rejigger types

I could not build this project locally, so I set out to fix it.  I think I did?  There were problems especially with wdio, and I know from experience that ts-node is required to address them.  I have also added @types/mocha but we're not actually doing much typechecking.
Anyway, we now have incremental builds!  That means "it's faster" since TS will only build one project at a time instead of all of them.
I was able to remove build.js, since tsc -b does the same thing now.  I was unable to retain the index.d.ts in the base plugin (though could probably figure it out if I spent more time with it); instead, the definitions are now in the docstrings of plugin.js.  All declarations are now generated by tsc and are output alongside the output .js files.  Please note that I did have to actually implement a couple functions which were previously commented-out.  We will want to define a Plugin interface later which allows the <cmd> methods. Since these don't exist in BasePlugin, we should not attempt to define them in this type.
Not too much actual type-checking is happening here, but we can enable that later (per file via // @ts-check pragma, or a checkJs: true in a project's tsconfig.json).

OK, I think I need to revert a portion of this for now.  I'm still unsure how, exactly, to get the generated .d.ts files to read the hand-edited ones... hmm.

I don't actually see any type files in this PR, are they not meant to be added?

I don't actually see any type files in this PR, are they not meant to be added?

No, they are all just build artifacts.  But as I mentioned above (somewhere), I don't think I can get away with that.

I like the idea of making BasePlugin a pure interface rather than an actual class, but we make use of class/interface-specific features like static fields that would be hard to model outside of a real interface model (i.e., duck typing would be not ideal).

I'm not sure I follow--is this in reference to this comment?
If we don't have classes, we don't need static members.  e.g.,
/** @type {IPlugin} */
const myPlugin = {
  name: 'MyPlugin',
  newMethodMap: { /* stuff */},
  async updateServer(app, server) {
    /* stuff */
  },
  findElement(context, driver, next, strategy, selector) {
    // `context` is what `this` would have been and is of type `Plugin`.
    // interface `Plugin` extends `IPlugin`, but it would have props `logger`, `name`, and `opts`.
    // when Appium loads `myPlugin`, it could use something like `Object.create({...myPlugin, logger, etc})`
    // to create a `Plugin`.
    // additionally, we could merge interface `Plugin` with _class_ `Plugin` (currently `BasePlugin`) in case
    // somebody really wanted to do `class MyPlugin extends Plugin`
  }
}
export default myPlugin;

but, as I said, I understand if you don't want to change the API to deviate from how drivers work (unless you wanted to change that as well).  it'd be an opportune time to do so, however!
If we change the API or not, we still have three different types we need to separate:

the interface that extensions must implement (call it IPlugin)
some default behavior (e.g., the BasePlugin class; mainly just its constructor)
the result of applying BasePlugin to an IPlugin, which results in a working instance of type e.g., Plugin

the result of applying BasePlugin to an IPlugin, which results in a working instance of type e.g., Plugin

That means that this in a method of an IPlugin is not an IPlugin but rather a Plugin, if you follow.

Before I was just trying to say that in Appium we currently make use of both the class-level fields and the instance-level fields. I.e., we distinguish between class objects and instances, so if we merge the concept of a plugin into a single object that implements an interface, we need to account for that in a redesign of how we work with plugins in the main Appium server code.

oh..yeah, I was assuming that to support anything new we'd have to write code lol

My vote would be to leave as-is right now, and for Appium 3 we could target updating the driver/plugin mode to be interfaces if we want (I'm not actually sure it will ever make reasonable sense to change drivers from instances to objects satisfying interfaces), hopefully requiring minimal updates on part of the extension authors. Right now would be an especially bad time to try and update driver handling since we need to support old appium 1.x drivers with appium 2.0, so there's probably lots of challenges if any driver updates are required.

Fair enough.  I'll close this PR and re-open one with minimal changes to just to get the build running.  We will still need to consider those three concepts, but it doesn't have to happen right away

Yes, please reopen one with all your build modifications. I had to steal from them in a branch where I'm adding a new plugin.

@boneskull are you able to open your minimal PR soon? I have work i want to do that is sort of reimplementing what you've done but you've done it more cleanly i imagine.

should be able to work on this today

@jlipps OK, after pulling master I am now able to build properly, so I have no idea what's going on here.  I am not going to change anything right now, so you should go ahead and do what you're going to do.

(I'm unsure how to make incremental builds work properly with a hand-coded .d.ts file.  If you really want that, I can spend some more time trying to figure it out, otherwise I'd just as soon leave it as-is.)

harrumph. ok. i think my problem is i added webdriverio as a dep and i got tons of ts build errors until i applied some of your magic changes, without understanding what i was doing.

to be sure, do not assume I know what I'm doing either.  it's mostly just adapting config from some rando's tutorial.


Add Standup Module

closes #221

All in all more deleted lines than new ones. Wouldnt have expected that.


object/extend should handle symbols

reminder.

found a way to resolve.
assign will handle symbols
extend will not handle symbols
can keep both. differ enough to warrant it.


Suggestions

Hi, I wanted to comment on a few things. The first is that messages can be seen with / me, the second is that moderation things can be done from the chat itself, there are streamers that do not have double screens and it costs them more. Thank you very much for continuing to develop this mod!

I don't understand the /me thing. In-game chat moderation doesn't feel doable right now, because I would have to modify how the Minecraft chat works and I'm just not that smart

When the user puts /me and message the message doesn't appear in chat(if u don't know what it is I put here an Image)

Ohh!! Now I get it, yeah, it's a bug, I'll try to fix it in the next release


StringBasedR2dbcQuery incorrectly binds params

I have such query:
    @Query("select :param1, :param2;")
    fun findSomething(@Param("param1") param1: String, @Param("param2") param2: Int): Mono<Void>

When both params are provided as params and within query then everything seems OK.
But when I modify the code (remove one of params from query) like:
@Query("select :param1, 2021;")
    fun findSomething(@Param("param1") param1: String, @Param("param2") param2: Int): Mono<Void>

then I could observe strange results.
My test looks like (written in Kotlin):
@Test
    fun name() {
        walletsRepository.findSomething("some-string-param", 123).verifyErrorResponse(Throwable::class.java)
    }

verifyErrorResponse is custom extension method which verifies that exception is thrown (cause repository method returns Mono<Void> so cannot map it to anything)
I have tried to debug code and have found out that there is something wrong with named parameters binding:

At the end I could observe following logs which indicates that query with wrong params have been triggered:
2022-06-27 13:35:53.807 [Test worker]   DEBUG o.s.r2dbc.core.DefaultDatabaseClient    : Executing SQL statement [select $1, 2021;]
2022-06-27 13:46:18.642 [Test worker]   DEBUG io.r2dbc.h2.client.SessionClient        : Request:  select $1, 2021 {1: 123}

Spring Data detects if named parameters are used within the query and if so, the parameters are bound by name. Parameters not used in the query (parameter name does not occur within the SQL query) are bound by index as Spring Data assumes you're using native bind markers.
Mixing named and index parameters within the same query asks for trouble as a mixed binding can easily mix up the parameter order. That being said, the second parameter that is not used in the query, can only be bound via index and that is the result you experience here.

The issue was noticed because of the fact that the initial query required to provide 2 parameters.
After some time when the code has evolved next version of the query required only second param (method signature has not changed) which caused the above-mentioned issue.
My expectation as a user is that if within a @Query I have a statement like SELECT :some-param-name and the method signature contains param with the same name this param would be bound by name (because in the query I use its name and not index) and not by index (regardless of a number of method signature params).  Otherwise, it could happen that if someone would forget to modify the method signature then the code would start to behave in a wrong way which would be really hard to investigate (especially if both params have the same type - like numbers).

My expectation as a user is that if within a @Query I have a statement like SELECT :some-param-name and the method signature contains param with the same name this param would be bound by name (because in the query I use its name and not index) and not by index (regardless of a number of method signature params).

This is true for the first parameter. Here we have a second parameter that is not used. We cannot tell whether the argument is used as $2, ? or with another binding marker.
It would be possible to switch to named parameters-only once we find that at least one parameter is being referenced by name but that would break queries like SELECT :myparam, $2.


Cleans up warning line decals

About the PR
Allows for seamless usage of warning line decals, in ever configuration. Now with extra configuration!
Oh I guess it should be mentioned to any mappers, this will ERROR texture a number of your maps' existing warning line decals, as some had to be renamed. Delete and repaint.
Screenshots

Changelog

:cl: Delete

add: Adds extra warning line decal, and fixed up existing ones.

Change the PR to keep the old decals functional, then we can let people know they are going away. After that either someone else, or you can remove them from the maps in different PRs, and eventually the old decals can be removed.


disable pre-commit.ci autofixing pull request branches

applied suggestions from https://github.com/asdf-format/asdf/issues/1679#issuecomment-1810737318

I am against re-enabling pre-commit-ci unless they fix the issue. The benefits it provides (autofixing prs and automatically updating pre-commit versions) do not seem worth the risk.

I fail to see how this is a risk? ASDF uses GitHub's freely available runners and all the CI that can be triggered from a PR has read only permissions (or should have read-only permissions).

I am against re-enabling pre-commit-ci unless they fix the issue. The benefits it provides (autofixing prs and automatically updating pre-commit versions) do not seem worth the risk.

I am not sure if this it what you mean, but you can have at least one of the benefits (automatically updating pre-commit versions) without enabling the other (autofixing PRs) by changing the pre-commit configuration in .pre-commit-config.yaml, e.g. by adding
ci:
  autofix_prs: false
  autoupdate_schedule: weekly

Thanks for the suggestion. Unfortunately even with autofix_prs disabled adding a pre-commit.ci autofix comment will trigger pre-commit-ci to fix the PR which will then allow the CI to run (this comment can be added by any account, even one brand new to GitHub). It would be nice if there were a way to disable autofixing or limit permissions for auto fixes to existing maintainers but the pre-commit-ci developers aren't interested in making that change.

Thank you for the insight @braingram , that is unfortunate to hear


egui_winit/wgpu: enable Android support

I've recently been looking at using egui to create an Android app that I can use to test a Bluetooth library that I'm building but I found that it would panic due to some assumptions that it's possible to access a native window for initializing render + surface state while the application is paused.
This implements the proposal in #1633 which enables graphics state to be lazily initialized on Android when the application is Resumed (at which point it has a valid native window) as well as support dropping/recreating surface state each time the application is paused/resumed on Android.
Since I'm currently using egui_winit and egui_wgpu directly this PR only focuses on enabling Android support via these APIs. The corresponding epi/glium changes adapt to the egui_wini/wgpu API changes but have some remaining assumptions about when a window is valid which means they would require some further work to add Android support.
Closes https://github.com/emilk/egui/issues/1633.

If we're changing the wgpu constructor, can we maybe go a step further and allow the user to fully set wgpu::Backends, wgpu::RequestAdapterOptions and wgpu::DeviceDescriptor?

yeah, sounds good, it was fairly arbitrary that I just exposed the power preference and present mode

Thanks for working on Android support!
I assume the FIXME:s in the code need fixin' before mergin'?

In this case I added the FiXMEs to code where I was maintaining status quo (where it wont currently work on Android) but I had to make integration changes to use the updated egui_wgpu and egui_winit API.
My intent was to just focus first on supporting Android better via egui_winit + egui_wgpu directly (i'm not cuurently using eframe) but I figured it was worth highlighting where the current integration details for epi / eframe aren't portable to Android.
I can try to take another pass later to also support Android via epi / eframe by addressing the FIXMEs, but would it be ok perhaps to leave them for this PR? Or perhaps just remove for cleaner aesthetics?

If we're changing the wgpu constructor, can we maybe go a step further and allow the user to fully set wgpu::Backends, wgpu::RequestAdapterOptions and wgpu::DeviceDescriptor?

With the updated patches I've just pushed the Painter::new() now takes a wgpu::Backends mask and wgpu::DeviceDescriptor struct and but not wgpu::RequestAdapterOption. The adapter options struct has a lifetime that's normally associated with the surface that can be given, which is not expected to be available when calling Painter::new(). It still accepts the wgpu::PowerPreference so it's currently just the force_fallback_adapter adapter option that's not exposed.


e2e-hub: install in different namespaces

In https://github.com/openshift/release/pull/49549, we want to transition to bundles for those CI jobs and operator-sdk will refuse to install both operators in the same OperatorGroup because they have different install modes.
/cc @ybettan

/retest


Copy edit needed

URL: https://pub.dartlang.org/help
This page and others need a bit of a copy edit. I'd be happy to do it.

@kwalrath – pull requests welcome! https://github.com/dart-lang/pub-dartlang-dart/blob/master/app/views/v2/help.mustache

Working on it now...

The change was merged and deployed.


11140

11140
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[ ] All filenames are lower case (including folders, images, files, etc.)
[ ] Filenames are descriptive
[ ] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[ ] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[ ] Image references in markdown contain an alternate text

@DialloOracle - This workshop is in Approved status. Please complete the Self QA of the workshop using the Self QA Checklist in WMS and update the workshop status to Self QA Complete to review this PR.

@DialloOracle  - Just following up on the PR.


Fix Android NativeEventEmitter warnings

Fixes: https://github.com/Expensify/react-native-share-menu/issues/191

@AndrewGable This PR is another React Native version update, it silences some warnings from not overriding these methods


Text on number of tickets is not fully displayed

Describe the bug
Text on number of tickets is not fully displayed
Screenshots

Would you like to work on the issue?
Yes

@anhanh11001 It is fine in my phone

I think this is a simple issue, I will fix it. If the event name takes up 2 lines, I guess you can reproduce the bug


Runtime terminate it in an unusual way

Hello Pandas developers.
Running any python script with the pandas produce 'Runtime to terminate it in an unusual way'
To reproduce the error use:

Pandas version 0.15.2, C Python
Python 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit (Intel)] on win32
SO windows 7

create a python script (myfile.py) with the line of code
import pandas as pd
run the code with
c:\my_path>python myfile.py
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Kind regards
Adrian

it is not recommended to actually compile on windows. and if you do, you need to use MS C++.
see here for installation instructions.
not exactly sure what version/libraries are shipped with XY Python. I have compiled successfully using conda (and libpython on windows however).

When not compiling Pandas on Windows, what is the suggested source?  I have tried pip install pandas, pip install --upgrade pandas, and pip install (whl file) from the [unofficial Python extension] builds(http://www.lfd.uci.edu/~gohlke/pythonlibs/).  All give the same exception when doing python -c "import pandas".  I'm on Windows Python 2.7 32-bit trying to install Pandas 0.18.1.


Baleen tests fail with OpenJDK 8

The Baleen "requirements" suggest Oracle JDK but also just say that Baleen works with Java 8.
I've tried compiling with OpenJDK, but Maven fails because of a test failure. Baleen doesn't require JavaFX anywhere, but the testComponents() unit test for AbstractComponentApiServletTest uses JavaFX for its example data. OpenJDK doesn't include JavaFX.
I've managed to build Baleen by commenting out the entire contents of that test. It would be helpful if Baleen's tests didn't depend on proprietary classes that aren't in OpenJDK when the core functionality does not require those classes.

A fair point, this has been fixed and will be included in the next future SNAPSHOT release.

Addressed in Baleen 2.4


Upgrade dependencies for node8

@elbuo8 I had approved when it was just couchbase. I'm concerned about this bcrypt update. the modules in this repo are the built-ins for rules and I'm worried that this will break people.
particularly because of this change: https://github.com/kelektiv/node.bcrypt.js/blob/master/CHANGELOG.md#200-2018-04-07

@fyockm second question, why is pg-native needed? The pg dependency hasn't changed, and including the pg-native is giving us issues on CI (and I guess on prod deployment as well).
https://auth0.slack.com/archives/C03H01D14/p1539785983000100


Build on Illumos

I've built and run tests/Tests.hs on Ubuntu 14.04 and on SmartOS base-multiarch 15.3.0.

Further conversation with @rmustacc showed that I'm missing an include to use those defines.  I'll update and reopen this tomorrow.
#include <sys/isa_defs.h>


Collision config doesn't function properly when right-clicking entities

Currently, MixinChunk_Collisions just uses the source BlockSnapshot or Entity in the current PhaseContext to determine what collisions to perform. However, this can lead to issues when interacting with mod items, such as in this issue. Our collision system will see the source entity as a Player, rather than the entity being interacted with.
I suggest that we delegate determination of the active entity to IPhaseState. It will default to returning the source entity or blocksnapshot, but will be overridden in InteractionPacketState to use the target entity or block.
Pinging @bloodmc for input.

This should be fixed by https://github.com/SpongePowered/SpongeCommon/pull/2453
InteractionPacketState now inherits isCollision from IPhaseState
https://github.com/SpongePowered/SpongeCommon/blob/bafbfa0a6849bee99d6fd1c0b8f563e5fb1bee35/src/main/java/org/spongepowered/common/event/tracking/IPhaseState.java#L528-L530
Which is making the method return early here
https://github.com/SpongePowered/SpongeCommon/blob/bafbfa0a6849bee99d6fd1c0b8f563e5fb1bee35/src/main/java/org/spongepowered/common/mixin/entitycollisions/ChunkMixin_Collisions.java#L88
This is valid for all Phasestates since they all have isCollision returning false (except EntityCollisionState)


undefined symbol: xdo_new

Xdo builds fine on my Ubuntu-based machine, however transporting it to Manjaro/Arch has been a different story.
Trying both
sudo pip install python-libxdo
# and
sudo pip install https://github.com/rshk/python-libxdo/tarball/master

The program crashes upon importing:
  File "voice_assistant.py", line 12, in <module>
    from xdo import Xdo
  File "/usr/lib/python3.7/site-packages/xdo/__init__.py", line 10, in <module>
    from .xdo import libX11 as _libX11
  File "/usr/lib/python3.7/site-packages/xdo/xdo.py", line 380, in <module>
    libxdo.xdo_new.argtypes = (c_char_p,)
  File "/usr/lib/python3.7/ctypes/__init__.py", line 369, in __getattr__
    func = self.__getitem__(name)
  File "/usr/lib/python3.7/ctypes/__init__.py", line 374, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))
AttributeError: python: undefined symbol: xdo_new

Ran with python 3, 3.7 and with 2 there seems to be no SpeechRecognition package (and it's going out of date anyways...)

Had to install xdotools


Issue #1378: Auto-install Vagrant plugins

PR fail is unrelated, and due to my own inept upgrading of PostgreSQL. D'oh!


Video playback restarts when seeking

Video playback restarts when seeking.
Showcase:
https://veed.io/view/b48ebee1-5f72-4bdb-ba60-013bbd4df9e3

Seems to work after removing secret key


Pane divider?

Environment
Microsoft Windows 10 Pro for Workstations
10.0.18363.1016 (1909)
Windows Terminal Preview 1.3.2382.0
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Split a tab vertically
Expected behavior
Unknown

Actual behavior
See below

Here are magnified pics of the split ... first, when the right pane is active

... second, when the left pane is active

In the second case (left pane active) there's an extra vertical bar.  ???
In both cases there's a blue thingy (window border?).

You may need to share a larger screenshot so that we can understand the context in which you're reporting this bug.
Here's what's up/what should normally happen:

The pane divider is split into two parts: "active" (matches your system accent color) and "inactive" (matches the system default chrome color). The "active" color surrounds the pane you are currently focused on, and the inactive color surrounds all other panes.
This is most evident when you have multiple panes visible:

We've never seen reports of this gray bar you've indicated on the righthand edge of your left pane, but I can't help diagnose without a screenshot that includes the rest of the pane layout ;P

Here's the whole thing, sitting on the desktop, left pane active.

K, that's a scrollbar. This is by design as explained above.

I know there's a scroll bar. What's the thin vertical grey stripe next to it ... the inactive part of the pane divider?  That's not entirely obvious and (at least for me) it doesn't provide much of a visual signal (of anything).
In your pic there are some very thin scroll bars (yes/no?).  How do you get them?

Yes, the thin gray strip is the inactive part of the pane divider. It's more evident when you have more than one split pane.
I'm using this setting:

I should have known.  I tried that when Windows 10 was new and didn't like it.
Why is there no scrollHome/scrollEnd

Because nobody's implemented it yet.

Does it need to be suggested/requested?

Is it meaningful to go to the top of a 9001-line buffer and see the lines that are about to scroll off the top of the screen while output is actively being processed? scrollToEnd is covered by input snapping (press a key, it jumps to the prompt line) already...
When in doubt, search for related issues! :smile:

With 9001 lines available, it's likely that the beginning of a session is available.  If you wanted to get there ...
Can't the input snapping be turned off?


v2.0.0 getTableRows return uint128 field as decimal rather than hex

Before v2.0.0, getTableRows return uint128 field as decimal but in v2.0.0 it returned as hex. Is this an intended behavior? Any ways to request it to return as hex but not decimal? Thanks.

See also https://github.com/EOSIO/eos/issues/8330


Please build stable version

I have the greatest respect for this project so don't get the wrong idea but please stop adding features and build one stable version.
I'm trying for days to get this running and have to go up and down all issues to find every little bug fix to get to the next step.
My setup is working with:

Raspberry Pi 2
RFID-RC522
Stretch
Headphone, no USB Audio stick at the moment

The current master branch is not working. There is no device found.
The only branch I found is Version-1.1.5-dynamicRFIDreader.
I had to struggle with playlist m3u problems after uploading a mp3.
It always wants to load a playlist from /tmp and returned with a mpd error.
I fixed it and in the end no errors but when I swipped a card there is no music.
So far I will give up and try it maybe later.
When I compare master with that branch it looks like that these changes are not included. Why?

Ok, now I'm back to v1.1.7 and I can play my music in the web app.
But on this branch I'm unable to find my RFID-RC522 device. So I can not trigger it with my rfid card.
When I run RegisterDevice.py there is no device listed.

I feel you, i had the same trouble the last 3 weeks. I decided to step back and wait for some days before starting again.
I use a Raspberry Zero with a RaspiAudioZero Soundcard. Stretch, Rotary knob and a RC522 RFID Reader. I got it all working somehow but never in a stable way and only with taking scripts from several Issues (like you said).
I think there is a lot of stuff going on in the Background, the new wiki, so many new Features, Spotify...
I hope it's gonna be better and easier in a few weeks :)
I love the Project and i love all the guys doing this in their free time. And i already learned a lot about Linux and python! So dont get me wrong and keep on doing the great work! I'm just gonna wait a bit and start again!

Hi @TKlement @MaxZimmermann99
I feel you, too :) as the owner of the project, I have partly made it grow in features (based on great ideas in the community, thanks!) and seen it grow (based on code contributions, which elevated the scope, thanks!). @MaxZimmermann99 is a good example why it has become more complex to install: "Raspberry Zero with a RaspiAudioZero Soundcard, Stretch, Rotary knob and a RC522 RFID Reader"
When I started the project, the idea was very "Apple" if you like: you know the hardware and it's all plug and play, using RFID cards as the only UI. Then I added the web app to control the playout. Then the suggestion came to use the web app also for adding files and changing the configuration (which was and is a good idea and I integrated that), then more hardware was thrown in the ring and the soldering irons came out to play with GPIO buttons and dials. All good stuff - and suddenly also more complex to maintain. And test.
Often it's the case that new code contributions work for one setup and once they are out in the wild, they create problems for different hardware and bug fixes create problems for custom setups (audio on USB or external hard disk for example).
I have been thinking about how to best handle this process, the balance of "growth versus stability". Spotify is a good example, many people really, really wanted this. And it's there, thanks to @princemaxwell. Then it did create problems once it was public, the fixes required upgrades and the documentation lacked behind. So it is wonderful to have it, but as a distributed project, this also meant that there is nobody who tests everything on all possibly hardware (which would be quite a task, given the different non-USB RFID readers currently used in the Phoniebox community).
@princemaxwell and I decided to have two "versions", the classic and the +spotify (where the + already indicates that I am sure more will come).
My goal would be to work on the classic documentation and installation and make this stable. That's what I can do (and will do as soon as my new job gives me a bit more elbow room :)
In my mind everything else is "experimental" and that's why I started the wiki: to give more spaces for code snippets regarding special hardware and hacked features.
I am writing this not in defense, but to explain where the project stands and also to indicate that I am still following the discussion and hope to jump back in the ring to clean up soon. This thread is valuable, because it allows me to do this. And I am happy that a) you feel strongly and positive about the Phoniebox project and b) you understand that the culture of this project is capable of such critique and input. Which it is. Thanks for that.
All the best, micz

Ahhh this explains why nearly 2 weeks nothing didn't happen to my pull request ;)
Congratulations to your new job.

I have also trouble with 1.1.8-rc2 classic coming from 1.0.0 - my RFID Reader does accept the second swipe option play/pause once (second swipe) but does ignore it on forth swipe or 6th swipe.
So after 3 swipes the swipes are ignored and the folder keeps playing.
I would like to switch to a v1.1.1 or v1.1.6. version (https://github.com/MiczFlor/RPi-Jukebox-RFID/releases/tag/v1.1.6)  like described in the upgrade manual, but I can't get the right commands to switch back to, anyone?

Same problem here. Pi2 with RC522. I tried out every "workaround" but i can't get it working together.

Hi @thade666 @gizmo21
Please have a read here
https://github.com/MiczFlor/RPi-Jukebox-RFID/wiki/RFID-Reader-Special
Because the last attempt to unify all efid readers in one script created mayhem for many usb reader users, I split the scripts to stable and experimental. Usb readers are the majority and in the spirit of this thread (make stable olease) I decided for this split.
All the best, micz


Consider switching to GitHub pages

Changing to GitHub pages would be a good idea with an automatic deployment instead of using Heroku.

Also need to get the DNS re-pointed to this domain name: https://servicemanual.digital.mod.uk.
We could potentially host on GitHub pages. Simple static website.

Done.