Bazel native build not working for multiple older versions of TF. Python dependency and commit hash issues.

Description
Some of the recent changes being merged have broken bazel builds using the Makefile for some of the older versions of Tensorflow. I am currently attempting to build libedgetpu for TF 2.13.1 and I am using Bazel 5.3.0.
It seems that the commit hash is not getting set in the bazel build command ran by the Makefile. The command shown here is missing a commit on the embed_label argument:
bazel build --stripopt=-x --compilation_mode=opt --cpu=k8 --embed_label='TENSORFLOW_COMMIT=' --stamp //tflite/public:libedgetpu_direct_all.so.stripped
The only modification I made to the workspace.bzl file was commenting out the TF 2.16.1 commit hashes and uncommenting TF 2.13.1 commit hashes.
Bazel also seems to be unable to pull the python toolchain for tensorflow, not sure why (maybe because the commit is missing). This is printed out in multiple places during the build:
ERROR: error loading package '': Label '@org_tensorflow//tensorflow/tools/toolchains/python:python_repo.bzl' is invalid because 'tensorflow/tools/toolchains/python' is not a package; perhaps you meant to put the colon here: '@org_tensorflow//tensorflow/tools/toolchains:python/python_repo.bzl'?
Checking out a82c669fb7a9b2e813cfb3d5409fea98d6a6ac8c before the toolchains were updated fixes both the python issue and commit not being set in the bazel build command. I am also able to fully build libedgetpu for TF 2.13.1 when checked out to this commit.
Click to expand!
Issue Type
Build/Install
Operating System
Linux, Ubuntu
Coral Device
USB Accelerator, M.2 Accelerator with dual Edge TPU
Other Devices
No response
Programming Language
C++
Relevant Log Output
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
ERROR: error loading package '': Label '@org_tensorflow//tensorflow/tools/toolchains/python:python_repo.bzl' is invalid because 'tensorflow/tools/toolchains/python' is not a package; perhaps you meant to put the colon here: '@org_tensorflow//tensorflow/tools/toolchains:python/python_repo.bzl'?
Loading: 0 packages loaded
Loading: 0 packages loaded
bazel build --stripopt=-x --compilation_mode=opt --cpu=k8 --embed_label='TENSORFLOW_COMMIT=' --stamp //tflite/public:libedgetpu_direct_all.so.stripped
Another command holds the client lock:
pid=5283
owner=client
cwd=/tmp/libedgetpu
tty=/dev/pts/1

Waiting for it to complete...
ERROR: error loading package '': Label '@org_tensorflow//tensorflow/tools/toolchains/python:python_repo.bzl' is invalid because 'tensorflow/tools/toolchains/python' is not a package; perhaps you meant to put the colon here: '@org_tensorflow//tensorflow/tools/toolchains:python/python_repo.bzl'?
INFO: Elapsed time: 0.037s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
Loading: 0 packages loaded
ERROR: error loading package '': Label '@org_tensorflow//tensorflow/tools/toolchains/python:python_repo.bzl' is invalid because 'tensorflow/tools/toolchains/python' is not a package; perhaps you meant to put the colon here: '@org_tensorflow//tensorflow/tools/toolchains:python/python_repo.bzl'?
Loading: 0 packages loaded
Loading: 0 packages loaded
make: *** [Makefile:99: libedgetpu-direct] Error 1

Bump, push

Bump, push

I'm just going to use docker I guess.

Hello! Do you resolve this issue?

No, it seems development had generally stopped and support for make builds isn't great. I find the using the docker environment to compile from source works for most versions.
Even if you get the makefile build to finish, it's not guaranteed to work. I had to change versions and then build and export with docker to get a working edgetpu library.

Try again, there have been several updates to fix the exact issues you are having. The current libesdgetpu builds against TF 2.16.1 successfully.


feat(query-tab): Added basic query module with routing.

Note: If there are pending changes to the PR, prefix the PR title with "WIP" and add the label "DO NOT MERGE"
Mandatory

[ ] What does this PR do?
For custom-query support story this PR adds a basic query module skeleton with routing.

[ ] What issue/task does this PR references?
https://openshift.io/openshiftio/Openshift_io/plan/detail/360

[ ] Are the tests Included?

Optional

[ ] Is the documentation Included?

[ ] Are the Release Notes included?

[ ] @mention(s) to expected reviewer(s) included

/ok-without-tests

@divyanshiGupta Your image is available in the registry. Run docker pull quay.io/openshiftio/rhel-fabric8-ui-fabric8-planner:SNAPSHOT-PR-2742 && docker run -it -p 5000:8080 quay.io/openshiftio/rhel-fabric8-ui-fabric8-planner:SNAPSHOT-PR-2742 and visit http://localhost:5000 to access it.


Sound Alerts Not Playing

The sound alerts are not currently playing while Pomomo is running. Multiple users on server having the same issue, can't see anything within server settings that would cause this issue.
Thanks!

I got this erro.
Command raised an exception: PermissionError: [Errno 13] Permission denied: '../sounds/ffmpeg.exe'
I think the programmer made it only for windows :/

Go to src/util/player.py
Change de line 21 to
source = PCMVolumeTransformer(FFmpegPCMAudio(path, executable='ffmpeg'), volume=0.1)
Make sure you have ffmpeg installed


Suggestion to customize brazilian phone

{"mask": "+55-##-9####-####","cc": "BR","cd":"Brazil" "desc_en": "", "name_ru":"Бразилия","desc_ru": "" },
{"mask": "+55-##-####-####","cc": "BR","cd":"Brazil","desc_en":"", "name_ru":"Бразилия","desc_ru":""},
I was trying to customize to our new reality of number formats (the official formats available do not serve perfectly), but I do not know how to do exactly.
The situation is as follows: When starting with 9, the structure must have 9 digits (include the 9). But in any other situation, it must have 8 digits. But when I type 9 in this position that I showed in the example, it is not dynamic and leaves the last digit hidden (even enabled for typing), and can confuse the user.

maybe this can help you, @dhiogoacioli:
  $(selector).inputmask({ mask: function () {
    return ['(99) 9999-9999', '(99) 99999-9999'];
  }})

Actually, I was thinking of something more dynamic. Example: as you type the beginning of the number, the mask automatically changes.

You can get some ideas from #836
Our phone numbers are really complicated.

Here is a working regex for almost all brazilians phones (+55 [0-9]{2} ((7[0|7|8|9])|([2|3|4|5][0-9])|([7|8|9][0-9]{2}))[0-9]{2}-[0-9]{4})
The only not working phones are:
0800 999 9999
0300 999 9999
0500 999 9999
0900 999 9999
Those are non geographical phones.

Remove Phone alias #1981


Support both yml and yaml extensions

Currently, only rushfile.yml name is supported. Add support for rushfile.yaml too for better flexibility.

Boom! done....rush now supports both rushfile.yml and rushfile.yaml format


Add support for basic authentication

Hello @notoriousbdg,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

6fe44c38b013b6ec027cecfe07866da640c2f0c8 - This commit has something that looks like an email address (gbrandon@vmware.com). Maybe try linking that to GitHub?.
a3ce2d56448a144f52f734db33cbe0ba8561439b - This commit has something that looks like an email address (gbrandon@vmware.com). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

?


add CONFIG_FREERTOS_HZ=1000 to sdkconfig.defaults

By default it is 100 Hz, which means all thread sleeps under 10 ms do not work as expected.
So this would just busy wait and does not give other threads chance to run. And it can be very confusing for the user.
loop {
   thread::sleep(Duration::from_millis(9))
}

So from user perspective it makes sense to explicitly define CONFIG_FREERTOS_HZ here. It would be less surprising then.
I learned it hard way here: https://github.com/esp-rs/esp-idf-sys/issues/71

I'm not really sure switching to 1000Hz by default is such a good idea:

If the ESP-IDF folks did choose 100Hz as default, perhaps they had a good reason for that
Even after the 1000Hz adjustment you still have the issue. How long until somebody comes in and says "Hey! I'm doing thread::sleep(Duration::from_micros(500)) and the IDLE tasks' watchdogs are barking at me!"

If you really really insist on having this parameter in esp-idf-template, I would suggest it to be commented out by default.
And then, as per the other issue, this would've not been a problem in the first place, if your tasks were sleeping a bit more. Having such short sleep times are a bit concerning. Why do you need that? E.g. in my not-yet-revealed-yet-complex-pet-project, the shortest sleep time I have is precisely 10ms, and this is only because our esp-idf-hal does not yet have support for GPIO interrupts, so I have to poll 'em damn buttons real quick (but - GPIO interrupts are coming!). The next shortest sleep time is ~ 200ms, which is a whole lot more bearable (that's for the ULP program I'm running).

Oh, sorry. You've explained it all in the other issue. Let me take a look.
Still: having this as a commented out parameter is what I feel most comfortable with.

Now it is commented out.

@ivmarkov Just stumbled over this here using a GitHub wide search for CONFIG_FREERTOS_HZ=1000. Although I don't use esp-rs, I thought I might answer your question "Having such short sleep times are a bit concerning. Why do you need that?" with my use case:
I'm building an ESP32-based CAN-Bus adapter that talks via a protocol named ISOTP (ISO15675-2), which is a fragmentation protocol. In this protocol, there is a mechanism called flow control, which indicates how long a sender should sleep between CAN-frames. It is indicated in milliseconds, often in the single digit regions. So, for some hardware, it's indeed a necessity to have millisecond-granularity for sleep times.

@ivmarkov Just stumbled over this here using a GitHub wide search for CONFIG_FREERTOS_HZ=1000. Although I don't use esp-rs, I thought I might answer your question "Having such short sleep times are a bit concerning. Why do you need that?" with my use case:
I'm building an ESP32-based CAN-Bus adapter that talks via a protocol named ISOTP (ISO15675-2), which is a fragmentation protocol. In this protocol, there is a mechanism called flow control, which indicates how long a sender should wait between sending consecutive CAN-frames. It is indicated in milliseconds, often in the single digit regions. So, for some hardware, it's indeed a necessity to have millisecond-granularity for sleep times.

If you need shorter sleep times, you should not try to poll your system more often. You have to keep in mind that any given context switch takes x amount of computing. By lowering this value you allow the system to context switch "more often" and not "faster". The context switch time itself is still the same length.
So you probably should use another method for waiting between frames. For example using the Ets delay - or another Timer that you are getting a signal from. You should try to stay in one context for the time you are running your frames.


I am getting error when I run the run_train_eval.sh

What am I doing wrong?
(driving) joshua@joshua:~/interp-e2e-driving$ ./run_train_eval.sh

2020-07-03 11:18:07.804356: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcuda.so.1
2020-07-03 11:18:08.070159: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-03 11:18:08.075765: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1618] Found device 0 with properties:
name: GeForce GTX 1080 with Max-Q Design major: 6 minor: 1 memoryClockRate(GHz): 1.468
pciBusID: 0000:01:00.0
2020-07-03 11:18:08.076109: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcudart.so.10.0'; dlerror: libcudart.so.10.0: cannot open shared object file: No such file or directory
2020-07-03 11:18:08.076323: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcublas.so.10.0'; dlerror: libcublas.so.10.0: cannot open shared object file: No such file or directory
2020-07-03 11:18:08.076515: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcufft.so.10.0'; dlerror: libcufft.so.10.0: cannot open shared object file: No such file or directory
2020-07-03 11:18:08.076704: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcurand.so.10.0'; dlerror: libcurand.so.10.0: cannot open shared object file: No such file or directory
2020-07-03 11:18:08.076907: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcusolver.so.10.0'; dlerror: libcusolver.so.10.0: cannot open shared object file: No such file or directory
2020-07-03 11:18:08.077095: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcusparse.so.10.0'; dlerror: libcusparse.so.10.0: cannot open shared object file: No such file or directory
2020-07-03 11:18:08.077282: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libcudnn.so.7'; dlerror: libcudnn.so.7: cannot open shared object file: No such file or directory
2020-07-03 11:18:08.077328: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1641] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
2020-07-03 11:18:08.078256: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2020-07-03 11:18:08.119019: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2020-07-03 11:18:08.120306: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x564c626d43c0 executing computations on platform Host. Devices:
2020-07-03 11:18:08.120379: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): Host, Default Version
2020-07-03 11:18:08.423663: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-03 11:18:08.439622: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x564c6274ab90 executing computations on platform CUDA. Devices:
2020-07-03 11:18:08.439684: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): GeForce GTX 1080 with Max-Q Design, Compute Capability 6.1
2020-07-03 11:18:08.439998: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1159] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-07-03 11:18:08.440029: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1165]
pygame 1.9.6
Hello from the pygame community. https://www.pygame.org/contribute.html
free(): invalid pointer
Fatal Python error: Aborted

Current thread 0x00007f370b009740 (most recent call first):
  File "<frozen importlib._bootstrap>", line 219 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 922 in create_module
  File "<frozen importlib._bootstrap>", line 571 in module_from_spec
  File "<frozen importlib._bootstrap>", line 658 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 955 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 971 in _find_and_load
  File "/home/joshua/anaconda/envs/driving/lib/python3.6/site-packages/carla/__init__.py", line 8 in <module>
  File "<frozen importlib._bootstrap>", line 219 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 678 in exec_module
  File "<frozen importlib._bootstrap>", line 665 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 955 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 971 in _find_and_load
  File "/home/joshua/gym-carla/gym_carla/envs/carla_env.py", line 20 in <module>
  File "<frozen importlib._bootstrap>", line 219 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 678 in exec_module
  File "<frozen importlib._bootstrap>", line 665 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 955 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 971 in _find_and_load
  File "/home/joshua/gym-carla/gym_carla/envs/__init__.py", line 1 in <module>
  File "<frozen importlib._bootstrap>", line 219 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 678 in exec_module
  File "<frozen importlib._bootstrap>", line 665 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 955 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 971 in _find_and_load
  File "<frozen importlib._bootstrap>", line 994 in _gcd_import
  File "/home/joshua/anaconda/envs/driving/lib/python3.6/importlib/__init__.py", line 126 in import_module
  File "/home/joshua/anaconda/envs/driving/lib/python3.6/site-packages/gym/envs/registration.py", line 17 in load
  File "/home/joshua/anaconda/envs/driving/lib/python3.6/site-packages/gym/envs/registration.py", line 72 in make
  File "train_eval.py", line 127 in load_carla_env
  File "/home/joshua/anaconda/envs/driving/lib/python3.6/site-packages/gin/config.py", line 1009 in wrapper
  File "train_eval.py", line 401 in train_eval
  File "/home/joshua/anaconda/envs/driving/lib/python3.6/site-packages/gin/config.py", line 1009 in wrapper
  File "train_eval.py", line 825 in main
  File "/home/joshua/anaconda/envs/driving/lib/python3.6/site-packages/absl/app.py", line 250 in _run_main
  File "/home/joshua/anaconda/envs/driving/lib/python3.6/site-packages/absl/app.py", line 299 in run
  File "train_eval.py", line 831 in <module>
./run_train_eval.sh: line 5:  4829 Aborted                 (core dumped) CUDA_VISIBLE_DEVICES=0 python train_eval.py --root_dir logs --experiment_name latent_sac --gin_file params.gin --gin_param load_carla_env.port=2000

Could you check if your GPU:0 (default in run_train_eval.sh) is already occupied?

Sorry how do I check if it's occupied? I have used the same GPU:0 recently to train other DRL algo in CARLA.

Sorry how do I check if it's occupied? I have used the same GPU:0 recently to train other DRL algo in CARLA.

Did you solve this problem?

Hi, i get the same error. Did you solve it? And maybe we need two GPUs?
Any tipps, I appreciate!!

I never got to to work for me, unfortunately.  I have long moved to other CARLA RL implementation.

It never got to work for me, unfortunately. I have long moved to other CARLA RL implementation.

Hi Jidenna, thanks a lot for your reply. Would you mind share with me which CARLA RL implementation you are using? I am also doing some research about this part. I appreciate again.

This https://github.com/dotchen/LearningByCheating Although they implemented behavioral cloning you can implement an RL agent as wellt. My research involves pedestrian crossing so it works for me


TerminusDb Vs BrightStarDB

TerminusDB https://terminusdb.com/ has some similarities with BrigthstarDB  but what is different is WOQL the query language which is really great for querying RDF store . It would ne great If we can implement WOQL for Brightstardb.

I agree with @ansarizafar


Request for updating a section

In the 'QuestDB 6.2 January release, SQL JIT compiler' release blog , 'New LATEST BY syntax and improvements' section (https://questdb.io/blog/2022/01/27/release-sql-jit-compiler/#new-latest-by-syntax-and-improvements), I updated the following.

Updated the 'LATEST BY documentation' link to 'LATEST ON' since the link directs users to the 'LATEST ON' page (https://questdb.io/docs/reference/sql/latest-on/).
Updated the section so that new users don't get confused between the deprecated LATEST BY syntax and the newer LATEST ON syntax.

If my understanding is correct and you agree with it, please feel free to accept the updates.

Deleting since this is added to consolidated PR.


Minor updates for the cover art scripts

Various minor improvements for ECAU and supercharged cover art edits, based on the suggestions by chaban in the forums.

Support new packaging types (one of them is non-square) and release statuses for supercharged cover art edits
Use the latest version of Image Max URL for compatibility with new Violentmonkey (beta) versions (untested)
Support filenames on archive.org which require URL encoding in ECAU:

New test for the given example to cover this case.
I'm restoring path separators after URL encoding to be on the safer side, although I haven't seen examples for full paths "including directory paths" yet, as per https://github.com/ROpdebee/mb-userscripts/blob/d04c2514a93e5a45a61cba0087a1161bf95c875d/src/mb_enhanced_cover_art_uploads/providers/archive.ts#L20

Thanks!


how to use jks instead pem ?

how to use
kafka.client.truststore.jks
instead of file in pem format ?

I fear that's it's not possible. We provide common authentification. It's hard with an UI to manage all authentification kind.
@fbricon do you think we should provide jks?

According to https://github.com/tulios/kafkajs/issues/1127#issuecomment-867554450, kafkajs doesn't provide a way to use keystores directly, they should be converted to PEM files first. Maybe there's a way to use  https://www.npmjs.com/package/jks-js to do that automagically

As far as I know, client certificate/key is optional, only Certificate Authority is mandatory. Is it possible to handle this situation ? (only provide Certificate Authority, let client certificate/key empty)

Is there any solution ?

I m a newbie with jks and I have no time to investigate some solution. Any contribution are welcome!


--ponyminthreads is confusing

It doesn't control the number of threads. It sets a floor for scaling threads. So if I set 999 it won't create 999 threads, it will not scale LOWER than 999 threads. So if --ponythreads is less than --ponyminthreads no downscaling will occur.
Options:

better help description
better flag name

Thoughts?

From sync. We believe there should be a flag for "don't scale my threads".
And --ponyminthreads will error out if it is greater than --ponythreads.
--ponynoscale is the current idea for turning off scaling.
if --ponynoscale is used on application startup then it should be a startup error to use --ponyminthreads.

@SeanTAllen If I am understanding this correctly the changes needed are:

[ ]  Clarify use and interaction of --ponyminthreads and --ponythreads
[ ]  Add a --ponynoscale flag that errors if used with --ponyminthreads

Should this --ponynoscale flag be the same as stating --ponyminthreads=0?

@RHagenson Not quite.
--ponynoscale is the same as setting --ponyminthreads equal to the value of --ponythreads. That is, it will never try to scale down the number of scheduler threads. Whereas --ponyminthreads=0 will allow you to scale all the way down to no scheduler threads running.
As part of this, we need to confirm that --ponyminthreads <= --ponythreads. If it isn't it should error out.
Documentation would need to be updated accordingly.

Got it. I had --ponyminthreads=0 in my head as a special value rather than an actual possibility of zero scheduler threads running. Good to know that is possible (not sure when it is useful, but not a major concern right now).

@alexsnaps has a PR open for this #3303.


Fallback operator

Hi, would it be possible to have a fallback operator instead of using a complementary operator (i.e. > and <=)?

Fallback is an interesting feature.
I don't think the operator has to take the responsibility of fallbacking, an alternative could be a fallback node. After comparing all the node's childs, if no one satisfies the condition, continue with the fallback node or return an error.


[BUG] Can't Add Credentials on Latest Version

Describe the bug
Just made deploy on Huggingface following instructions but can't add credentials, this is the console log:
`
===== Application Startup at 2024-02-20 11:25:37 =====
2024-02-20 11:27:08 [INFO]: Starting Flowise...
2024-02-20 11:27:08 [INFO]: ⚡ [server]: Flowise Server is listening at 7860
2024-02-20 11:27:08 [INFO]: 📦 [server]: Data Source has been initialized!
2024-02-20 11:27:10 [ERROR]: ❌ [server]: Error during Data Source initialization: require() of ES Module /usr/local/lib/node_modules/flowise/node_modules/json-with-bigint/json-with-bigint.js from<EMAIL_ADDRESS>not supported.
Instead change the require of json-with-bigint.js in<EMAIL_ADDRESS>to a dynamic import() which is available in all CommonJS modules.
Error [ERR_REQUIRE_ESM]: require() of ES Module /usr/local/lib/node_modules/flowise/node_modules/json-with-bigint/json-with-bigint.js from<EMAIL_ADDRESS>not supported.
Instead change the require of json-with-bigint.js in<EMAIL_ADDRESS>to a dynamic import() which is available in all CommonJS modules.
at Object. (/usr/local/lib/node_modules/flowise/node_modules/@qdrant/openapi-typescript-fetch/dist/cjs/fetcher.js:5:28)
at Object. (/usr/local/lib/node_modules/flowise/node_modules/@qdrant/openapi-typescript-fetch/dist/cjs/index.js:4:22)
at Object. (/usr/local/lib/node_modules/flowise/node_modules/@qdrant/js-client-rest/dist/cjs/api-client.js:4:36)
at Object. (/usr/local/lib/node_modules/flowise/node_modules/@qdrant/js-client-rest/dist/cjs/qdrant-client.js:5:25)
at Object. (/usr/local/lib/node_modules/flowise/node_modules/@qdrant/js-client-rest/dist/cjs/index.js:18:26)
at Object. (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/vectorstores/Qdrant/Qdrant.js:4:26)
at /usr/local/lib/node_modules/flowise/dist/NodesPool.js:32:42
at Array.map ()
at NodesPool.initializeNodes (/usr/local/lib/node_modules/flowise/dist/NodesPool.js:30:38)
at async NodesPool.initialize (/usr/local/lib/node_modules/flowise/dist/NodesPool.js:20:9)
at async /usr/local/lib/node_modules/flowise/dist/index.js:78:13
Error: Node qdrant not found
at /usr/local/lib/node_modules/flowise/dist/index.js:229:23
at Layer.handle [as handle_request] (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/layer.js:95:5)
at next (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/route.js:144:13)
at Route.dispatch (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/route.js:114:3)
at Layer.handle [as handle_request] (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/layer.js:95:5)
at /usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:284:15
at param (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:365:14)
at param (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:376:14)
at Function.process_params (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:421:3)
at next (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:280:10)
at sanitizeMiddleware (/usr/local/lib/node_modules/flowise/dist/utils/XSS.js:24:5)
at Layer.handle [as handle_request] (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:328:13)
at /usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:286:9
at Function.process_params (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:346:12)
at next (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:280:10)
Error: Credential azureOpenAIApi not found
at /usr/local/lib/node_modules/flowise/dist/index.js:197:27
at Layer.handle [as handle_request] (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/layer.js:95:5)
at next (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/route.js:144:13)
at Route.dispatch (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/route.js:114:3)
at Layer.handle [as handle_request] (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/layer.js:95:5)
at /usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:284:15
at param (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:365:14)
at param (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:376:14)
at Function.process_params (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:421:3)
at next (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:280:10)
at sanitizeMiddleware (/usr/local/lib/node_modules/flowise/dist/utils/XSS.js:24:5)
at Layer.handle [as handle_request] (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:328:13)
at /usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:286:9
at Function.process_params (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:346:12)
at next (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:280:10)
Error: Credential azureOpenAIApi not found
at /usr/local/lib/node_modules/flowise/dist/index.js:197:27
at Layer.handle [as handle_request] (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/layer.js:95:5)
at next (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/route.js:144:13)
at Route.dispatch (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/route.js:114:3)
at Layer.handle [as handle_request] (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/layer.js:95:5)
at /usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:284:15
at param (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:365:14)
at param (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:376:14)
at Function.process_params (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:421:3)
at next (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:280:10)
at sanitizeMiddleware (/usr/local/lib/node_modules/flowise/dist/utils/XSS.js:24:5)
at Layer.handle [as handle_request] (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:328:13)
at /usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:286:9
at Function.process_params (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:346:12)
at next (/usr/local/lib/node_modules/flowise/node_modules/express/lib/router/index.js:280:10)
`
To Reproduce
Try to add credentials for any service on any screen.

Setup

Huggingface

I have the same problem locally. I tried downgrading to flowise version 1.4.0, but the problem is still there.

I have almost the same problem here with the latest version of Flowise, (forked yesterday).
I try to add credentials to ChatOpenAI and to Pinecone but it seems like it don't let me create new credentials, when I click on  - Create New - , nothing is happening, I also tried two different browser, the problem is the same in both.
Could please help me with this ?


pythonPackages.semver: 2.8.1 -> 2.10.2

Motivation for this change
Update pythonPackages.semver to latest version. Old version was almost 2 years old. Release notes: https://github.com/python-semver/python-semver/releases

[x] Updates doc webpage
[x] Bumps version
[x] Update to new GitHub repo.
[x] updates tests
[x] formatting

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I took the liberty of unbreaking a few packages that came up in nix-review.

Result of nixpkgs-review pr 91982 1

21 packages built:
- apache-airflow (python37Packages.apache-airflow)
- keepkey_agent (python38Packages.keepkey_agent)
- ledger_agent (python38Packages.ledger_agent)
- python27Packages.prance
- python27Packages.semver
- python37Packages.apispec
- python37Packages.flask-appbuilder
- python37Packages.jupyter-repo2docker
- python37Packages.keepkey_agent
- python37Packages.ledger_agent
- python37Packages.libagent
- python37Packages.prance
- python37Packages.semver
- python37Packages.trezor_agent
- python38Packages.apispec
- python38Packages.flask-appbuilder
- python38Packages.jupyter-repo2docker
- python38Packages.libagent
- python38Packages.prance
- python38Packages.semver
- trezor_agent (python38Packages.trezor_agent)


Panic during monomorphization in noir-rsa

Aim
Compile noir-rsa with latest noir
Expected Behavior
Should compile!
Bug
The application panicked (crashed).
Message:  internal error: entered unreachable code: Encountered Error node during monomorphization
Location: compiler/noirc_frontend/src/monomorphization/mod.rs:459

To Reproduce
use dep::biguint::BigUint56;

fn main(
    dkim_sig: BigUint56,
) {
    let top = BigUint56::from_u56(131072 as u56);
    assert(dkim_sig.lt(top));
}

The problem might be that it's not looking into regular impl methods for operator trait methods
Project Impact
None
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional Context
No response
Installation Method
None
Nargo Version
No response
NoirJS Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response

Running the given example with the dependency biguint = { path = "noir-bigint/crates/biguint" } gives me:
error: cannot find `Self` in this scope
   ┌─ /home/user/Code/Noir/noir/short/noir-bigint/crates/biguint/src/lib.nr:34:9
   │
34 │         Self { limbs: [0 as u56; NUM_LIMBS] }
   │         ---- not found in this scope
   │

error: expected type BigUint56, found type ()
   ┌─ /home/user/Code/Noir/noir/short/noir-bigint/crates/biguint/src/lib.nr:33:22
   │
33 │     pub fn zero() -> Self {
   │                      ---- expected BigUint56 because of return type
34 │         Self { limbs: [0 as u56; NUM_LIMBS] }
   │              -------------------------------- () returned here
   │

error: Expected an expression but found :
   ┌─ /home/user/Code/Noir/noir/short/noir-bigint/crates/biguint/src/lib.nr:34:21
   │
34 │         Self { limbs: [0 as u56; NUM_LIMBS] }
   │                     -
   │

error: Expected a ; separating these two statements
   ┌─ /home/user/Code/Noir/noir/short/noir-bigint/crates/biguint/src/lib.nr:34:14
   │
34 │         Self { limbs: [0 as u56; NUM_LIMBS] }
   │              -
   │

Aborting due to 4 previous errors

Yep, there seems to be a diferent bug also happening. You can extract the array initialization from the struct initialization to the previous line and this issue arises!


How to create https server and support wss use koa2? I need it very much.

http + https =
const Koa = require('koa');
const app = new Koa();
http.createServer(app.callback()).listen(80);
const options = {
    key: fs.readFileSync('./ssl/private.pem', 'utf8'),
    cert: fs.readFileSync('./ssl/20180303.crt', 'utf8')
};
https.createServer(options, app.callback()).listen(443);

http + ws =
const Koa = require('koa');
const websockify = require('koa-websocket');
const app = websockify(new Koa());
app.listen(80);

https + wss = ?

Any solution you might found?

@avihaymenahem no solution， need somebody to develop a package to  support it(https + wss).

In anyway, you can perfectly stick with HTTP and use a reverse-proxy (nginx, httpd) to enable HTTPS.

@motet-a, Not use nginx, only a single ECS.

you can do  it this way:
const server = new Koa();

// ... middlewares and routes

const options = {
   // Local certificates, if you don;t have them generate from mkcert or letsEncrypt
    key: fs.readFileSync("localhost-key.pem"),
    cert: fs.readFileSync("localhost.pem")
  };

  https.createServer(options, server.callback()).listen(port);


Transient issue in CuratorDruidCoordinatorTest

Noted a transient build failure caused by org.apache.druid.server.coordinator.CuratorDruidCoordinatorTest timing out:
Running org.apache.druid.server.coordinator.CuratorDruidCoordinatorTest
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

I've seen this several times today in Travis.


jetbrains.{idea,pycharm}-community-src: 2023.3.2 -> 2024.1.2

Description of changes

Updates the from source builds of IntelliJ IDEA and PyCharm Community to 2024.1.2.
They have been not in sync with the binaries for some time, and the code currently is structured to always show the (wrong) version of the binary package, not the source build.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

oh i didn't see #316185


(Expo) Stripe iOS Build Error: "You did not provide an API key" despite Providing Key

Hello, I'm encountering an issue with Stripe integration in my Expo app when running it on a real iOS device.
Everything works fine on Android builds, iOS simulators, and Android simulators, but when I try to add a payment card on the real iOS build, I get the following error:
Error code: Failed You did not provide an API key. You need to provide your API key in the Authorization header, using Bearer auth (e.g. 'Authorization: Bearer YOUR_SECRET_KEY'). See https://stripe.com/docs/api#authentication for details, or we can help at https://support.stripe.com/.
What I’ve Done:
I followed the Expo/Stripe documentation and have provided the publishable key in the frontend using the  component, like this:
<StripeProvider publishableKey={process.env.EXPO_PUBLIC_STRIPE_PKEY} urlScheme="your-url-scheme" // required for 3D Secure and bank redirects merchantIdentifier="merchant.com.{{YOUR_APP_NAME}}" // required for Apple Pay >

The API keys are correctly set in the environment variables.
On Android, iOS simulators, and Android build, everything works as expected.
The issue happens only on real iOS devices.

Setup:

Expo SDK version: 50
API version: 2024-04-10
@stripe/stripe-react-native: ~0.35.1
react-native: 0.73.6
Device: iPhone13 (iOS 18.1.1)

What I've Tried:

Verified that the API key is correct and correctly loaded in process.env.EXPO_PUBLIC_STRIPE_PKEY.
Double-checked the relevant documentation for iOS integration with Expo/Stripe, but nothing seems to address this specific error.

We have the same issue... please provide a solution why only ios does not work. At build time, which is handled by EAS, the stripe key is present, yet stripe handling on  ios builds does not work..


Get through the gauntlet by swapping colors and dodging!

How do you play your game?
Press W and S to move up and down, J to swap colors. When the game is over press I to restart. You must match a gate's color to go through.

Code
Check off the items that are true.

[x] The game was made using the Sprig editor.
[x] The game is placed in the in the /games directory.
[x] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[x] The game runs without errors.
[x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x] The game name is not the same as the others from gallery

Image (If an image is used)

[ ] The image is in the /games/img directory.
[ ] The name of the image matches the name of your file.

Thanks for your PR!

Congratulations!  If you're a teenager, and if you haven't already received a Sprig game, feel free to fill out this form to receive a device of your own!  Additionally, feel free to join the Hack Club Slack and share your creation in the #sprig channel!

Thanks for the merge! I'm taking part in the Sprig Jam - should I fill out the form now or wait until the winners are announced?


Feature Request: Always Show Starred Smart Feed

When the show/hide read articles toggle is active, the starred articles smart feed is hidden unless there are starred articles that have also been marked unread. This feels wrong to me, as it requires two steps to get back to something important that I started reading but didn't finish—either I have to mark an article as unread and star it, or I have to star it and remember to deactivate the show/hide articles toggle.
I think a better option would be to exclude all three smart feeds (or at the very least the starred smart feed) from being affected by the show/hide read articles toggle to make it easier to find / remember to get back to important articles.

Agreed!

+1 on this.

This is already there in the iOS 6.0 release and will be in the upcoming mac 6.0.3 release.

I should have said that I was speaking to OS X. I am aware of it in iOS. Thank you for your reply.


NixOS Packages not listed

Macchina doesn't recognize Nix packages and only lists packages installed via cargo

Support for the Nix package manager was added in https://github.com/Macchina-CLI/libmacchina/pull/172.


What if I typed nothing in the texts（Instructions），it seems that the model would generate it randomly.

What if I typed nothing in the texts（Instructions），it seems that the model would generate it randomly.

Hi @chengfengke,
Yes, you are correct that the model will generate scenes randomly if text prompts are none.
Examples of text prompts for generation can be found in the appendix of the paper or the project website, such as: "Add a corner side table with a round top to the left of a black and silver pendant lamp with lights".

thanks for your answer


Fix staging branch conflicts

Before submitting this PR, please make sure:

[ ] Your code builds clean without any errors or warnings
[ ] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
https://github.com/hummingbot/gateway/commit/324a7391b27f5cc4e9c344de48af4837bbb0ff63
Tests performed by the developer:
Tips for QA testing:

This change shouldn't fix the Gateway workflow, but I'm glad it passed. I'll fix it properly before the next release.


timeout for connectng to  http://localhost:5173

some system are not fast enough for it's cpu, and that will cause the issue when connecting to http://localhost:5173 (timeout)
the code you written will try to connect to http://localhost:5173 immediately after the service up,
i recommand to change these line (just example)
tmp = requests.get("http://localhost:5173")
to this line
  wait_time = 0
  if_connect =False

  while if_connect == False and wait_time<=6:
      try:
          tmp = requests.get("http://localhost:5173")
          if_connect = True
      except:
          print(".")
          time.sleep(10)
          wait_time+=1

Hi B3N50N,
Really gooooood suggestion indeed!! The original timeout logic is not good.
I added this in the startup. Should be working now.


Load Balance - route traffic to same Data Center with upsream/target configuration

I have a requirement to set up multi-DC cluster using upstream/targets for dynamic load balance.  If we add targets of multi-DC to the upstream, how can I make Kong to route traffic to target on the same DC, instead of other DCs,  unless the services are all down in the local DC. For example, if traffic comes to Kong in Dallas DC, I prefer kong route the traffic to endpoint located in Dallas too.

The Kong load balancer implements distributes load among targets based on weights. What you want instead is to prioritize targets differently on each DC. One way to use that is, instead of having the upstream balance multiple targets, to set those targets in one SRV record in DNS and use SRV record priorities. For example, in your Dallas DC, you can set up your DNS so that the Dallas endpoint gets higher priority. Our lua-resty-dns-client library used by Kong supports SRV records honoring priority so things should work as you expect.
(Side note: the Github issue tracker is aimed at reporting bugs, for general support please refer to the mailing list or Gitter — thanks!)


CAMEL-11357 - Change examples groupId and disable publishing to Maven…

… central
I am not %100 sure about disabling push to Maven Central. I followed the config here [1]
1

Thanks I think we have some old -example in the parent/pom.xml and maybe also in apache-camel/pom.xml. I wonder if you could check there as well and then remove those so we have it all cleaned up

@davsclaus, i checked but could not find other examples.

Thanks for the PR it has been merged. Do you mind closing this?


Header size does not change

Summary
If we set title to empty, the size of the header does not change

______________
"Choose date"
null
______________

API Changes
We need to add hasTitle parameter to the constructor
public DatePickerDialog(UIColor? textColor = null, UIColor? buttonColor = null, UIFont? font = null, NSLocale? locale = null,
            bool showCancelButton = true, bool useLocalizedButtons = false, bool hasTitle = true)

@alexsorokoletov Hi
Do you have any ideas on this issue?
Changing the value to 320 in this line corrects UI. But I think this solution is not very good


ESS Prism will return more than one result if there is an ebook and a physical book with the same ISBN

Hi,
Hope you don't mind but I've stumbled across a small and possibly fairly infrequent problem! Barnet libraries have ebook records from overdrive on their Prism catalog. If you search for an ISBN that has both an ebook and a physical book copy, the code in catalogues-api/connectors/prism3.js will return the ebook, and the returned item page is not in the same format, meaning librarybooks.uk will not return an item. I suspect this would be the same for other ESS (Capita) library services that add their ebooks to Prism.
Here's an example request to the prism API.
https://prism.librarymanagementcloud.co.uk/barnet/items.json?query=9781843103912
A request to this url gives the the following object keys
 ['https://prism.librarymanagementcloud.co.uk/barnet/items.json?query=9781843103912', 'urn:uuid:f52b3d55-af62-5750-8172-638b99c99a20', 'http://prism.librarymanagementcloud.co.uk/barnet/items/dda-1/EDZ0001381927', 'http://prism.librarymanagementcloud.co.uk/barnet/items/36660']
The code in catalogues-api/connectors/prism3.js relies on const itemUrl = Object.keys(searchRequest.data)[2], where as in this instance, the correct item would be index 3.
Returning this url http://prism.librarymanagementcloud.co.uk/barnet/items/dda-1/EDZ0001381927 makes it look as though there is no copy available.

I think this is fixed now - certainly for that example anyway!

Excellent 👌 good work!
On Sat, 31 Jul 2021, 18:40 Dave, @.***> wrote:

I think this is fixed now - certainly for that example anyway!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LibrariesHacked/catalogues-library/issues/3#issuecomment-890380854,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG6XLKKIC6PFBT3TZCTDSCLT2QYSFANCNFSM5BJL7TJA
.


Show laoding indicator when fetching data from an api

I can solve this issue. Can you please assign this issue to me

I want to solve this is issue. and contribute in this project .

I can solve this issue by using conditional rendering with the help of react state.
Can you please assign this issue to me


sink (ticdc): add ddl encoder for simple protocol

What problem does this PR solve?

Issue Number: ref #9898 close #9901
What is changed and how it works?
Check List
Tests

Unit test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

/retest

/check-issue-triage-complete


Fix global notifications settings not live-updating on settings page

I fixed #2358 as well, since I couldn't test #2527 otherwise (as the server basically 500-ed instead of showing the updated settings page).
I hope it is all good :smiley:

Automated message from Dropbox CLA bot
@bojidar-bg, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Automated message from Dropbox CLA bot
@bojidar-bg, thanks for signing the CLA!

So, a commit message more in line with Zulip conventions would be:
component: what you did

Extra details if necessary

Fixes #bug if applicable

Ok, remaking commits....

It would be great if you added some tests for the new code paths in apply_events to make coveralls not unhappy.

Ok, should be better now, let's see what coveralls would report :smile:

Yay, passed all checks :tada:

@bojidar-bg This is great work so far, but I'm a little confused about some of the changes in the second commit.  When we get status changes, it seems like we shouldn't have to redraw the whole setup page.  We should be able to make more precise changes to the existing page by just updating the specific settings that come in through server_events.js.  It's possible that I'm misunderstanding something here.  It may be worth discussing this on https://chat.zulip.org/#narrow/stream/GCI.20help.
To other GCI mentors, the code quality code here looks great, but this is a pretty significant change, so as the mentor, please take the time to test these changes thoroughly in your own dev environment, not only to find bugs, but also to increase your own understanding of these changes.

Also, for the first commit, I'm a little confused about why we are adding all that Python code, since I believe we already were sending those settings in page_params before.

Yeah, would fix later / tomorrow :)

Ok, should be better that way..
I'm not sure either for the first commit, but... if it works it works :smiley:

OK, tested on a server running your branch and regarding #2527; when the user has two windows open on the settings page, updating settings under Display Settings updates them for the other window too but I can't seem to have the same with the settings under Notifications. Any idea what might be wrong?
Feel free to ping me here or on chat.zulip.org if you need additional information or need me to spin up my server, which is accessible over the Internet.

@femnad did you click "Save changes"?

For the Display Settings I don't have to do that. But if I click Save Changes for saving something under Notifications I get an error message saying Error saving changes, even though the settings seem to have changed.

Hmm? Works flawlessly on my end... That's strange.

You're right, can't seem to trigger that now. Let me test it a bit more and get back to you on that.

OK, I know how to replicate it now: go to settings page, change something in the Notifications, the page will redirect. Then change something in the same section again, the green OK message will be displayed. Change something again and the error message will show up.

Now, that's even stranger, here it would always redirect, heh. Maybe we can speak about it here? https://chat.zulip.org/#narrow/stream/GCI.20tasks/topic/.232527.2F.232649

Ah, I would have to go, unfortunately... Would it be a problem if the PR is merged even with this issue still standing? I mean, it was probably present even before the PR (in current master), and if that's the case, then it would be unrelated to the PR :smiley:

Well, in that case first the bug on master should be fixed before this one is merged, to make sure there are no regressions. But the question is, can you replicate that behavior? If you can, testing in on master would be the next step.
By the way, the reason we're being so careful with this PR is that is concern an important user facing issue and we need to make sure it works correctly. You've done a very good job so far we just need to go the extra mile.

@bojidar-bg looks great!  I can confirm the bug being discussed is present in master; we should make sure it is fixed, but I'm fine with merging this and dealing with that separately.  I opened https://github.com/zulip/zulip/issues/2697 for that issue.
Merged, thanks for fixing these 2 issues!!


How to set target/max speed (5kmph) for auto pilot?

Is there any way to set the target/max speed for Adaptive Cruise Control (ACC) in Autopilot mode.
I could not find such settings in manual_control.py or automatic_control.py. I will be glad to know the location for ACC code.
I think, by default, it was set to 20kmph. I need to set it like 5kmph.
Btw, I am trying to use LIDAR for mapping the environment. So, I need a slow moving car.
Thanks!

For now, I am using automatic_control.py with few changes in basic_agent.py.
def __init__(self, vehicle, target_speed=20): to def __init__(self, vehicle, target_speed=5):
It is working!
But I will be glad if anyone tell how to implement the same for manual_control.py (Coz, autopilot mode in manual_control.py is smooth and better)

Hi @AravindChandradoss,
The autopilot in manual_control.py is run on server-side, the code is in WheeledVehicleAIController.cpp.

Hi @bigsheep2018,
Yes, "spawn_npc.py" uses the autopilot in server-side (UE4).

@AravindChandradoss I also want to set to 5km/h. Can you tell me how to do it?
Thanks in advance.

@Guanwh  check these lines 483-495 in this code
Sorry for late reply.

@AravindChandradoss  Thanks for your reply! But I had tried it, it didn't work for the auto pilot!

you have to recompile. do make launch in your carla directory. refer this if needed.

Check out the Traffic Manager in Python API.

The vehicles will drive at 80% their current speed limit, leaving at least 5 meters between them and never perform a lane change.
tm = client.get_trafficmanager(port) tm_port = tm.get_port() for v in my_vehicles:   v.set_autopilot(True,tm_port) danger_car = my_vehicles[0] tm.global_distance_to_leading_vehicle(5) tm.global_percentage_speed_difference(80) for v in my_vehicles:    tm.auto_lane_change(v,False)

here are the link

@Guanwh check these lines 483-495 in this code
Sorry for late reply.

The code is 190 lines, could you please tell me where exactly/which variables in the CPP file must be changed?


[SPARK-13452][MLLIB] RegressionMetrics to support RootMeanSquareLogar…

What changes were proposed in this pull request?
[SPARK-13452][MLLIB] RegressionMetrics to support RootMeanSquareLogarithmicError - RMSLE.
Here we are adding a new metric for regression. RMSLE is used for wide variety of problems on Kaggle as an evaluation metric.
How was the this patch tested?
Corresponding test cases have been added and are passing. Also, scalastyle checks are passing too.
…ithmicError - RMSLE

Can one of the admins verify this patch?

@srowen @mengxr Could you please review this one?

The code looks OK... I think two passes is too much complexity.
I guess the thing is that I've never seen log error used before. That could just be my ignorance. What's the case where it's the theoretically right thing to use? squaring the log is throwing me here. I only see it mentioned in the context of Kaggle, where the motivation is just to penalize predictions that are low more than high, but this doesn't make it a generally useful metric beyond ranking submissions.

@srowen true. I have coded the same logic several times mostly for kaggle problems. Since it is supported in R, I felt a need for it in spark as well. However if the community does not need such metric, I am happy to close.

I asked around and couldn't find anyone who had heard of this metric being used -- except for the examples you cite in Kaggle. Since it's quite easy to implement yourself for these cases, I'd suggest it's not worth including. The downside is simply a little extra weight in the API for little-r gain. We can revive it later if someone has evidence to the contrary. Would you close this PR?

@srowen Sure. thanks!.


[REQUEST] Optimize memory usage for GTFS Shape entity

Is your feature request related to a problem? Please describe.
Currently, in https://github.com/MobilityData/gtfs-validator/pull/70 we are storing each shapes.txt record as a Shape object. Shape and stop_times.txt are the two GTFS files that will likely consume the vast majority of memory for GTFS entities, as they are typically the two largest files in the feed.
Describe the solution you'd like
We can reduce the amount of memory for Shape considerably, from two perspectives:

The String shapeId is the same for each point in the trip - we only need to store it once per trip
The lat/lon points for the trip can be losslessly compressed from floats to an encoded polyline, which is a variable-length String depending on the number of points (see https://developers.google.com/maps/documentation/utilities/polylinealgorithm - there are libraries as well, such as this code)

A new object to hold the shape info for each trip (e.g., TripShape) could have these fields:

String shapeId
String encodedPolyline // The points of the shape
float[] shape_dist_traveled // (if this optional field exists)

The new optimized process to read shapes.txt into memory could be:

Read all records for a given shape_id into Shape entity List
Sort list by increasing shape_pt_sequence
Encode lat/longs for list of Shape entities into encodedPolyline
(If optional field shape_dist_traveled exists) Store all shape_dist_traveled values of Shape entities into the shape_dist_traveled array

We could also optionally simplify the shape before encoding it to something like decimeter level precision to reduce the number of points, although this is a lossy operation.
Describe alternatives you've considered
Do nothing
Additional context
https://github.com/MobilityData/gtfs-validator/pull/70

Implemented in #70

Working on this.


Prepare SDK for alpha-4

So the SDK makes heavy use of the assetManager field where it could use Application.getAssetManager().
It might also extend Application instead of SimpleApplication (now LegacyApplication).
The question is if we should implement Application or extend LegacyApplication? I'd say we can go for the latter and worry about those things later.

For now, just extend LegacyApplication wherever Application is extended
directly.  You have at least a year to worry about any other refactoring.
On Tue, Mar 29, 2016 at 2:32 PM, MeFisto94<EMAIL_ADDRESS>wrote:

So the SDK makes heavy use of the assetManager field where it could use
Application.getAssetManager().
It might also extend Application instead of SimpleApplication (now
LegacyApplication).
The question is if we should implement Application or extend
LegacyApplication? I'd say we can go for the latter and worry about those
things later.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/jMonkeyEngine/sdk/issues/43


Unneeded calls to get and get-in removed

just a nit and some questions to ensure you're paying attention :-)


The lamp dissapears from the scene

Try to represent and fix this issue

After testing, still can't represent this issue


driver: lpspi: add the lpspi driver for rt1170

enable the  lpspi1 for the rt1170 evk board
Signed-off-by: Crist Xu<EMAIL_ADDRESS>

Please rebase

@CristXu you may need my CI fix here as well - https://github.com/zephyrproject-rtos/zephyr/pull/36887

related this PR: #36887


Fix deps

When running Main_Demo.ipynb for local development, circuitsvis and plotly are not installed.
This PR adds them to the poetry requirements.

note: CI/CD for 3.10 took over 10mins on the depenency installation step

not sure why :shrug:

Ah, this is deliberately NOT part of the requirements, and only used in the
tutorials to avoid bloating the package, CircuitsVis in particular comes
bundled with node stuff in a way that's messy.
The demo notebook automatically installs these, but I only want them to be
installed for the demo notebooks not for pip installing the package.
The issue is that the demo notebook checks whether it's in colab (if so,
installs the packages) or in Jupyter (where it assumes it's working locally
and doesn't install things because I already have them installed). I think
that people using the demo locally is a valid use case though, which is a
pain... I could do something stupidly hacky like checking whether a
specific file in my system exists?
Ooh, a better idea would be to try importing them, and use an except
statement to then install and then import?
On Sun, 22 Jan 2023, 8:48 pm Jason Hoelscher-Obermaier, <
@.***> wrote:

note: CI/CD for 3.10 took over 10mins on the depenency installation step
[image: image]
https://user-images.githubusercontent.com/6757489/213916573-50e387b7-4996-4d96-bb69-4e6831ad8957.png
not sure why 🤷
—
Reply to this email directly, view it on GitHub
https://github.com/neelnanda-io/TransformerLens/pull/149#issuecomment-1399476095,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRPNKJXOPHIQOEKFNQBLE3WTUUARANCNFSM6AAAAAAUC6WQQA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I'm considering adding some plotly based utils, but want to have a mediumly
high bar for adding new large dependencies unless they seem important.
On Sun, 22 Jan 2023 at 20:57, Neel Nanda @.***> wrote:

Ah, this is deliberately NOT part of the requirements, and only used in
the tutorials to avoid bloating the package, CircuitsVis in particular
comes bundled with node stuff in a way that's messy.
The demo notebook automatically installs these, but I only want them to be
installed for the demo notebooks not for pip installing the package.
The issue is that the demo notebook checks whether it's in colab (if so,
installs the packages) or in Jupyter (where it assumes it's working locally
and doesn't install things because I already have them installed). I think
that people using the demo locally is a valid use case though, which is a
pain... I could do something stupidly hacky like checking whether a
specific file in my system exists?
Ooh, a better idea would be to try importing them, and use an except
statement to then install and then import?
On Sun, 22 Jan 2023, 8:48 pm Jason Hoelscher-Obermaier, <
@.***> wrote:

note: CI/CD for 3.10 took over 10mins on the depenency installation step
[image: image]
https://user-images.githubusercontent.com/6757489/213916573-50e387b7-4996-4d96-bb69-4e6831ad8957.png
not sure why 🤷
—
Reply to this email directly, view it on GitHub
https://github.com/neelnanda-io/TransformerLens/pull/149#issuecomment-1399476095,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRPNKJXOPHIQOEKFNQBLE3WTUUARANCNFSM6AAAAAAUC6WQQA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

yep, you're right. this should definitely not be in the main requirements.
should it be in the dev dependencies , though?
I think development work is still more likely to happen locally, in which case circuitsvis and plotly are not installed automatically when running Main_Demo.ipynb

on a side note: I'm actually confused how plotly is pulled in (if it is). does not seem to be installed explicitly anywhere

@alan-cooney Takes?

Ah, Plotly is pre-installed on Colab.
Hmm, I'm not actually sure how dev requirements work, but I agree that
including them there seems reasonable (at least, if there's no convention
to keep *those *simple), happy to take a PR for that.
On Mon, 23 Jan 2023 at 19:10, Jason Hoelscher-Obermaier <
@.***> wrote:

on a side note: I'm actually confused how plotly is pulled in (if it is).
does not seem to be installed explicitly anywhere
—
Reply to this email directly, view it on GitHub
https://github.com/neelnanda-io/TransformerLens/pull/149#issuecomment-1400171516,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRPNKMATWVGOL5I75CRZD3WTZRMFANCNFSM6AAAAAAUC6WQQA
.
You are receiving this because you commented.Message ID:
@.***>

Yeah putting them in dev requirements makes sense. These are installed whilst developing as poetry install --group dev or they can be installed by end user as pip install transformer-lens[dev].
The reason for the slower CD is that where there are changed requirements, the CD checks that all possible combinations of packages in the ranges specified work with each other. This is expensive where packages fail to declare their requirements properly (as it has to download all versions), but is important to do. When there are no changed requirements it uses a cache to speed this up dramatically.

don't merge yet. they're still in the main requirements. I'll move it to the dev requirements

done. should be good to merge now

Thanks for the PR!


fix group change loader

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


The Meetup API continues to return 0 length content responses

The meetup API continues to return 0 length responses on the first request to any API. Subsequent requests work which is why most people don't file this bug but for any service that makes repeated requests to different resources (i.e. request the group info for a bunch of groups) this is clearly evident.

Which API are you calling?


Improve thumbnail caching

Cache thumbnails to girder files

I'd like to up. Vote this one... Should be easy and will be helpful as I
wrote galleries...
On Aug 16, 2016 10:26 AM, "David Manthey"<EMAIL_ADDRESS>wrote:

Cache thumbnails to girder files
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DigitalSlideArchive/large_image/issues/70, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AArhzo0p4uNJjtoSoFPTlrab_MvA5rRrks5qgch8gaJpZM4JldcG
.

I'm working on it now.

Added in PR #76.


New PR for form

This is a long overdue PR for the translation of form. I got stuck with some local conflicts because I did not check out from the master branch, so I decided to ditch that PR and start a new one. 🙈
This translation has been review previously in this PR here: https://github.com/reactjs/zh-hant.reactjs.org/pull/23
I believe that I've made all the changes, but please take a look and let me know if there is anything I should edit!
I will close the other PR once this is merged in!

@neighborhood999 Thanks for your great review! I accepted all the changes. Let me know if there are anything I still need to change. :)


[Proposal] Refactor Resolver

Remove ResolverMiddleware, should be wrap
Simplify Resolver via removing ResolverMiddleware. Using of ResolverMiddleware is too complicated. I always forget how it works, and view its source code. Remove methods composeArgs, composeResolve and composeOutputType.
class Resolver {
  wrap((newResolver, prevResolver) => newResolver): newResolver;
  wrapResolve((next) => (resolveParams) => resolveFn): newResolver;
  wrapArgs((prevArgs) => newArgs): newResolver;
  wrapOutputType((prevOutputType) => newOutputType): newResolver;
}

Method wrap is the common method that can clone parent Resolver and override/wrap it.
Methods wrapResolve, wrapArgs, wrapOutputType are the helpers that work on top of the wrap method.
Remove cross-references with TypeComposer
Cross-reference between TypeComposer and Resolver should be removed. It brings unnecessary complexity and some bugs, which occurs when cloning resolver with existed name.
Resolver will not have TypeComposer in its props anymore. TypeCompose can be provided via wrap callback
TypeComposer may have a list of resolvers with arbitrary names. This name may not coincide with resolver name. Previously cross-reference updates resolver if it was wrapped. But it works buggy and unclear.
If you want to change Resolver in TypeComposer you should do it explicitly.  Resolver wrapping should keep reference to parent Resolver. It should help to print resolvers chain and it's source code:
class Resolver {
  parent: Resolver;
  toString(): string;
}

// getNestedName() should return
wrapArgs(wrapRelay(findMany))

// toString() should return
Resolver(
  displayName: string,
  outputType: stringified type,
  args: stringified args,
  resolve: js code,
  parent: Resolver(
    ...
    parent: Resolver(
      ...
    )
  )
)

This proposal is not final and may be changed.

This proposal realized in https://github.com/nodkz/graphql-compose/commit/fe78e3a17646ec127c8c2116f40496ebfc51c1bc
Before publishing<EMAIL_ADDRESS>should be rewritten graphql-compose-mongoose, graphql-compose-relay and graphql-compose-connection.


Blade on iPadOS / VisionOS?

Blade clearly already supports MacOS via Metal, is it currently supported on iOS specifically iPad?

I haven't tested it on iOS yet, but there should be minimal, if any, changes needed.
This is based on the experience we had with wgpu.
Note that, in terms of window system integration, there is already support - https://github.com/kvark/blade/blob/1875b776edfc87763ebc4206fd31973b79076a2d/blade-graphics/src/metal/mod.rs#L386-L388
If you try it out, I'm curious to see how it goes!

I can try it out, but it will be with SDL and not winit, and it'll run as a rust program in an swift project.


[Monitor] Enable sovereign cloud testing

This refactors some of the monitor ingestion/query library tests to allow for sovereign cloud testing. China cloud and Government cloud testing are also enabled on the weekly pipelines.

API change check
API changes are not detected in this pull request.


x/build: add LUCI solaris-amd64 builder

s11-i386.foss.cebitec.uni-bielefeld.de.csr.txt
Somehow I'm not able to add the new-builder as required in the installation docs.

@roth The instructions have been updated with a method on how to add the new-builder label via gopherbot.

Please generate a new certificate signing request useing solaris-amd64 as the hostname. I will clarify the documentation. The hostname will be what the host will appear as in the build environment. It's not necessarily what the actual hostname is.

solaris-amd64-1690923319.cert.txt
I've generated the cert and registered your bot.

cc/ @golang/release

@roth We've looked into this error. The swarming bot doesn't seem to support solaris-amd64. Thanks for doing this work, it revealed that this would be an issue. We added the work to add support to our roadmap. I will comment on this issue once that work has started.

Hi @rorth, I think we're now in a state where running the latest bootstrapswarm will work. Please give it a try?
Regarding your earlier questions:
The -hostname flag to bootstrapswarm overrides the bot's hostname calculation; I believe the crash was unrelated.
There isn't any official way to control the builder's parallelism. Feel free to try setting GOMAXPROCS, especially if that' s what you were doing before, and we can verify that it's getting propagated into the child processes. But that will only have some effect, since there's a lot of parallelism across many processes.
It is currently hardcoded as $HOME/.swarming in bootstrapswarm, yes. If there's a compelling need to change it (or make it overridable) we can look into that.

Hi Heschi,

Hi @rorth, I think we're now in a state where running the latest
bootstrapswarm will work. Please give it a try?

sure, just did so.  I get along further now, but still fail with
28804 2023-09-05 12:21:35.703 E: Request to https://chromium-swarm.appspot.com/swarming/api/v1/bot/handshake failed with HTTP status code 403: 403 Client Error: Forbidden for url: https://chromium-swarm.appspot.com/swarming/api/v1/bot/handshake
28804 2023-09-05 12:21:35.703 E: Failed to contact for handshake, retrying in 0 sec...
I get a similar error when I try to access that URL with wget:
bash-5.2$ wget https://chromium-swarm.appspot.com/swarming/api/v1/bot/handshake
--2023-09-05 14:26:20--  https://chromium-swarm.appspot.com/swarming/api/v1/bot/handshake
Resolving chromium-swarm.appspot.com (chromium-swarm.appspot.com)... <IP_ADDRESS>, 2a00:1450:4001:831::2014
Connecting to chromium-swarm.appspot.com (chromium-swarm.appspot.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 405 Method Not Allowed
2023-09-05 14:26:20 ERROR 405: Method Not Allowed.

Regarding your earlier questions:
The -hostname flag to bootstrapswarm overrides the bot's hostname
calculation; I believe the crash was unrelated.

Ok, I see.

There isn't any official way to control the builder's parallelism. Feel
free to try setting GOMAXPROCS, especially if that' s what you were doing
before, and we can verify that it's getting propagated into the child
processes. But that will only have some effect, since there's a lot of
parallelism across many processes.

Good: I'll continue with GOXMAXPROCS as before; it worked well enough.

It is currently hardcoded as $HOME/.swarming in bootstrapswarm, yes. If
there's a compelling need to change it (or make it overridable) we can look
into that.

It would certainly be nice to be able to control that: software
enforcing directory layouts when there's no strong reason to do so feels
inflexiblel.
Rainer

Just to eliminate any confusion, what --hostname argument did you pass?

Heschi Kreinick @.***> writes:

Just to eliminate any confusion, what --hostname argument did you pass?

I used -hostname solaris-amd64, matching what I passed to genbotcert
-bot-hostname.

Oh, are you passing --token-file-path? I think that's an attractive nuisance at the moment -- bootstrapswarm understands it, but the actual Swarming bot doesn't, so its requests are coming in without a token. In this case I definitely agree that you should be able to override the token path, but it'll take a little while to get that implemented in the bot. In the meantime, can you use the default path of /var/lib/luci_machine_tokend/token.json just to see if there are other surprises in store?

Heschi Kreinick @.***> writes:

Oh, are you passing --token-file-path? I think that's an attractive
nuisance at the moment -- bootstrapswarm understands it, but the actual
Swarming bot doesn't, so its requests are coming in without a token. In
this case I definitely agree that you should be able to override the token
path, but it'll take a little while to get that implemented in the bot. In
the meantime, can you use the default path of
/var/lib/luci_machine_tokend/token.json just to see if there are other
surprises in store?

Sure: I hadn't used the default because /var/lib is completely alien to
Solaris, so I went for a more convenient/appropriate location instead.
Switching to the default definitely helped, thanks.
However, I noticed this in swarming_bot.log:
557 2023-09-06 07:18:29.947 D: State {'audio': None, 'cpu_name': None, 'cost_usd_hour': 0.6155357096354167, 'cwd': '/opt/golang/tokend/.swarming', 'disks': {'/system/shared': {'free_mb': 135725.0, 'size_mb': 135731.7}}, 'env': {'PATH': '/usr/bin'}, 'gpu': None, 'hostname': 's11-i386.foss', 'ip': '<IP_ADDRESS>', 'nb_files_in_temp': 22, 'pid': 557, 'python': {'executable': '/usr/bin/python3', 'packages': ['asn1crypto==1.5.1', 'attrs==22.2.0', 'Babel==2.10.1', 'cffi==1.15.1', 'chardet==5.1.0', 'cheroot==9.0.0', 'CherryPy==18.8.0', 'cmd2==2.4.0', 'colorama==0.4.6', 'cryptography==37.0.2', 'filelock==3.8.0', 'idna==3.4', 'jsonrpclib-pelix==<IP_ADDRESS>', 'jsonschema==4.5.1', 'lxml==4.9.1', 'Mako==1.2.4', 'MarkupSafe==2.1.2', 'more-itertools==9.0.0', 'numpy==1.23.4', 'Pillow==9.3.0', 'pkg==0.1', 'ply==3.8', 'portend==3.1.0', 'prettytable==3.3.0', 'psutil==5.9.4', 'pyasn1==0.5.0', 'pyasn1-modules==0.3.0', 'pybonjour==1.1.1', 'pycairo==1.21.0', 'pycparser==2.21', 'pycurl==7.45.2', 'Pygments==2.15.1', 'PyGObject==3.42.0', 'pyOpenSSL==22.0.0', 'pyparsing==3.0.9', 'pyperclip==1.8.2', 'pyrsistent==0.19.3', 'python-ldap==3.4.2', 'python-rapidjson==1.6', 'pytz==2022.5', 'requests==2.28.2', 'simplejson==3.18.4', 'six==1.16.0', 'tempora==5.0.1', 'urllib3==1.26.15', 'wcwidth==0.2.6'], 'version': '3.9.17 (main, Aug  4 2023, 07:38:38) \n[GCC 12.2.0]'}, 'ram': 0, 'running_time': 43072, 'ssd': [], 'started_ts':<PHONE_NUMBER>, 'uptime': 0, 'user': 'golang-luci', 'quarantined': 'Bot denied running for user "golang-luci"', 'original_bot_id': 'solaris-amd64', 'sleep_streak': 767}
The "Bot denied" error certainly bothered me ;-)  I've switched to a new
"swarming" user instead and the message vanished.  However, no builds so
far AFAICS.
It seems to me that LUCI has an unfortunate habit of forcing its own
conventions (directories, usernames, probably more) on the bots when
it's completely unnecessary and uncalled for ;-(
One other issue: I noticed this in ~swarming/.swarming/README:
Maintenance
Installing, shutting down, etc.
https://chrome-internal.googlesource.com/infra/infra_internal/+/master/doc/luci/swarming_bot.md
This URL seems to only be accessible inside Google, which seems
unfortunate if visible/expected to be usable on the bots.
Thanks.
Rainer

The bot seems to have died, possibly because I sent it work for the first time. Can you take a look? Thanks for your patience.

Heschi Kreinick @.***> writes:

The bot seems to have died, possibly because I sent it work for the first
time. Can you take a look? Thanks for your patience.

Right: I'd started it in the foreground and my DSL connection died.
Restarted now.  The log ends in
10780 2023-09-07 17:36:35.059 I: [UFS]: zone ['cloud'] is not managed by UFS, skipping UFS state checks
10780 2023-09-07 17:36:35.059 I: get_dimensions(): 0s
10780 2023-09-07 17:36:35.096 I: get_state(): 0.036s
10780 2023-09-07 17:36:35.097 I: get_settings(): 0s
10780 2023-09-07 17:36:35.098 I: Unknown OS sunos5
10780 2023-09-07 17:36:35.098 I: Restarting machine with command sudo -n shutdown -r now (Internal failure)
10780 2023-09-07 17:36:35.107 E: Failed to run sudo -n shutdown -r now: [Errno 2] No such file or directory: 'sudo'
10780 2023-09-07 17:36:35.108 I: Sleeping for 300
Do I need to provide a fake sudo to work around this?

No, that won't help much.
Thanks; I have a list of things to work on now and I'll let you know when it makes sense for you to try again.

Heschi Kreinick @.***> writes:

No, that won't help much.
Thanks; I have a list of things to work on now and I'll let you know when
it makes sense for you to try again.

Excellent, thanks a lot.

Hi @rorth, most of the stuff that needs doing should be done now. Can you try again?
I've added a couple of environment variables you can use:

Set SWARMING_ALLOW_ANY_USER to anything to disable the swarming user requirement. That said, it might be best if you leave it running under swarming for now, just to keep thing simple while we're still working on it.
Set LUCI_MACHINE_TOKEN to the path of the LUCI token to override the default /var/lib location.
Set SWARMING_NEVER_REBOOT to prevent it from trying to reboot the machine.

That's correct. The changes were made to the Swarming bot. Did you try using them? Did it work?

I'd started with
LUCI_MACHINE_TOKEN=/opt/golang/tokend SWARMING_NEVER_REBOOT=1 /opt/golang/bin/bootstrapswarm -hostname solaris-amd64
2023/09/22 11:24:17 Bootstrapping the swarming bot with certificate authentication
2023/09/22 11:24:17 retrieving the luci-machine-token from the token file
2023/09/22 11:24:17 unable to read file "/var/lib/luci_machine_tokend/token.json": open /var/lib/luci_machine_tokend/token.json: no such file or directory

after moving  /var/lib/luci_machine_tokend aside.  Same behaviour with LUCI_MACHINE_TOKEN pointing at the token.json file itself.  Also running under truss showed no hint of access attempts under $LUCI_MACHINE_TOKEN.
I've now restored /var/lib/luci_machine_tokend and re-run bootstrapswarm with SWARMING_NEVER_REBOOT=1.  Let's see what happens...

2023/09/22 11:24:17 unable to read file "/var/lib/luci_machine_tokend/token.json": open /var/lib/luci_machine_tokend/token.json: no such file or directory

@rorth Sorry, there was a typo, the env var to set the LUCI token path is LUCI_MACHINE_TOKEN_FILE (with a "_FILE" suffix at the end), if you'd like to try it. Thanks.

Apologies, I was so focused on the stuff I was less familiar with I completely forgot that bootstrapswarm also needed updating. Dmitri was kind enough to take care of that in http://go.dev/cl/530475, so LUCI_MACHINE_TOKEN should work if you reinstall bootstrapswarm.
In the meantime my other changes have taken effect, and I've been able hit the next roadblock. Fix is in progress. Thanks for leaving the bot up.

We got our first green build: https://luci-milo.appspot.com/ui/p/golang/builders/ci/x_oauth2-gotip-solaris-amd64/b8769217496445479345/overview. It won't be fully up and running until I put the final touches on, but I think we're in good shape now.

OK. Please give it one last restart.

It looks like the builder is doing fine on x/ repos, but hangs indefinitely when testing the main repo. (example: http://ci.chromium.org/b/8768937412553978545) Unfortunately result-adapter is swallowing all the test output so we have nothing to go on from our side. @rorth, can you see anything happening on the machine?

I don't find anything obvious in logs/swarming_bot.log.  However, bootstrapswarm is currently running in the foreground and on the command's stdout I see three (so far) prompts:
Password: .  I vaguely remember that something like this also happened with the old buildbot.  Such a unanswered prompt could certainly explain the build not completing...

I've now converted the swarming bot to a proper Solaris SMF service.  Let's see how it fares now...

On the one hand it's not hanging any more, but on the other it's crashing hard in the same test every time with a strange runtime bug that doesn't happen on the old builders:
https://ci.chromium.org/ui/p/golang/builders/ci-workers/gotip-solaris-amd64-test_only/b8768782473709459681/overview:
=== RUN   TestLookupDotsWithRemoteSource
runtime: port_getn on fd 3 failed (errno=9)
fatal error: runtime: netpoll failed

runtime stack:
runtime.throw({0x682dcc?, 0x3?})
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/runtime/panic.go:1018 +0x5c fp=0x7fffbfffd110 sp=0x7fffbfffd0e0 pc=0x438d9c
runtime.netpoll(0xc00002c000?)
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/runtime/netpoll_solaris.go:257 +0x46f fp=0x7fffbfffddb0 sp=0x7fffbfffd110 pc=0x43538f
runtime.findRunnable()
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/runtime/proc.go:3195 +0x845 fp=0x7fffbfffded8 sp=0x7fffbfffddb0 pc=0x440dc5
runtime.schedule()
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/runtime/proc.go:3589 +0xb1 fp=0x7fffbfffdf10 sp=0x7fffbfffded8 pc=0x442051
runtime.park_m(0xc0005069c0?)
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/runtime/proc.go:3752 +0x11f fp=0x7fffbfffdf58 sp=0x7fffbfffdf10 pc=0x44255f
traceback: unexpected SPWRITE function runtime.mcall
runtime.mcall()
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/runtime/asm_amd64.s:458 +0x57 fp=0x7fffbfffdf70 sp=0x7fffbfffdf58 pc=0x46a697

Any idea what's going on there? I can ask someone from the runtime team to take a look if necessary.

I have no idea, unfortunately.  I tried running the tests manually as the bot user inside the build tree (w/ir/x/w/goroot/src) with
go test -c net
./net.test -test.run=TestLookupDotsWithRemoteSource

and all tests just PASS this way.
I've got two questions:

When/why does a test enter the PAUSE state as obvserved for the failing tests?
Is there any better way to investigate those failures?  I mean to run the exact command from the failing test, environment and all, but this will have to wait for tomorrow.

It seems there's something amiss with the JSON output: when I run
go tool dist test -run net.TestLookupGoogleSRV

I get the expected

##### Test execution environment.
# GOARCH: amd64
# CPU: Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz
# GOOS: solaris
# OS Version: SunOS 5.11 <IP_ADDRESS>.0 i86pc

ALL TESTS PASSED (some were excluded)

while for
go tool dist test -run net.TestLookupGoogleSRV -json

the command returns with no output and exit status 0.  Very weird.
I suspect the current buildbot (like running all.bash manually) uses the classical output while the swarming bot relies on JSON.

@mknyszek spotted the more interesting stack trace: it appears to be crashing inside libc. You mentioned configuring it as a Solaris service. Perhaps that's causing a problem somehow? It seems unlikely to be LUCI-related per se.
SIGSEGV: segmentation violation
PC=0x7fffbf161128 m=11 sigcode=1 addr=0x88f000
signal arrived during cgo execution

goroutine 900 [syscall]:
runtime.cgocall(0x401220, 0xc0001f9788)
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/runtime/cgocall.go:157 +0x3e fp=0xc0001f9760 sp=0xc0001f9728 pc=0x405d1e
net._C2func_res_ninit(0x88bc50)
	_cgo_gotypes.go:207 +0x55 fp=0xc0001f9788 sp=0xc0001f9760 pc=0x6023d5
net._C_res_ninit.func1(0xc0001f97d8?)
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/net/cgo_unix_cgo_resn.go:28 +0x34 fp=0xc0001f97c0 sp=0xc0001f9788 pc=0x602c94
net._C_res_ninit(0x228?)
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/net/cgo_unix_cgo_resn.go:28 +0x13 fp=0xc0001f97d8 sp=0xc0001f97c0 pc=0x602c33
net.cgoResSearch({0x67facf, 0xb}, 0xc000133814?, 0x2e?)
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/net/cgo_unix.go:324 +0x108 fp=0xc0001f9ac8 sp=0xc0001f97d8 pc=0x544828
net.resSearch.func1()
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/net/cgo_unix.go:314 +0x25 fp=0xc0001f9af8 sp=0xc0001f9ac8 pc=0x544705
net.doBlockingWithCtx[...]({0x6db2d0, 0x881440}, 0xc000213380)
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/net/cgo_unix.go:45 +0x25f fp=0xc0001f9bc8 sp=0xc0001f9af8 pc=0x60ca5f
net.resSearch({0x6db2d0, 0x881440}, {0x67facf, 0xb}, 0x5, 0x1)
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/net/cgo_unix.go:313 +0x9c fp=0xc0001f9bf8 sp=0xc0001f9bc8 pc=0x54467c
net.cgoLookupCNAME({0x6db2d0?, 0x881440?}, {0x67facf?, 0x6db2d0?})
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/net/cgo_unix.go:299 +0x45 fp=0xc0001f9d38 sp=0xc0001f9bf8 pc=0x544485
net.(*Resolver).lookupCNAME(0xc0001f9dd0?, {0x6db2d0, 0x881440}, {0x67facf, 0xb})
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/net/lookup_unix.go:92 +0xa5 fp=0xc0001f9d98 sp=0xc0001f9d38 pc=0x565d25
net.(*Resolver).LookupCNAME(0xc000133830?, {0x6db2d0?, 0x881440?}, {0x67facf, 0xb})
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/net/lookup.go:484 +0x2b fp=0xc0001f9de0 sp=0xc0001f9d98 pc=0x562a8b
net.LookupCNAME(...)
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/net/lookup.go:467
net.testDots(0xc000507520, {0x67d6f8, 0x3})
	/opt/golang/swarm/.swarming/w/ir/x/w/goroot/src/net/lookup_test.go:674 +0x12e fp=0xc0001f9ef0 sp=0xc0001f9de0 pc=0x5bc44e
net.TestLookupDotsWithRemoteSource(0xc000507520)

Thanks, that led me way further: the failure can be reproduced with
$ cd src/net && go test -c .
$ ./net.test
SIGSEGV: segmentation violation
PC=0x7fffbf161128 m=11 sigcode=1 addr=0x887000
signal arrived during cgo execution

goroutine 1004 [syscall]:
runtime.cgocall(0x401220, 0xc0000eb788)
        /opt/golang/swarm/goroot/src/runtime/cgocall.go:157 +0x3e fp=0xc0000eb760 sp=0xc0000eb728 pc=0x405d1e
net._C2func_res_ninit(0x8841b0)
        _cgo_gotypes.go:206 +0x55 fp=0xc0000eb788 sp=0xc0000eb760 pc=0x5ff955
net._C_res_ninit.func1(0xc0000eb7d8?)
        /opt/golang/swarm/goroot/src/net/cgo_unix_cgo_resn.go:28 +0x34 fp=0xc0000eb7c0 sp=0xc0000eb788 pc=0x600214
net._C_res_ninit(0x228?)
        /opt/golang/swarm/goroot/src/net/cgo_unix_cgo_resn.go:28 +0x13 fp=0xc0000eb7d8 sp=0xc0000eb7c0 pc=0x6001b3
net.cgoResSearch({0x67ca24, 0xb}, 0xc000014460?, 0x2e?)

Running the test under truss shows really weird exit handling: at the end of the run (before the SEGV) there's
/17:    read(4, "FE ]8180\001\001\004\007".., 1232)     = 265
/17:    port_dissociate(5, 4, 0x00000004)               Err#2 ENOENT
/17:    close(4)                                        = 0
/17:    zone_lookup(NULL)                               = 0
/17:    zone_getattr(0, ZONE_ATTR_BRAND, 0x7FFF733FF940, 256) = 8
/17:    door_info(3, 0x7FFF733FF910)                    = 0
/17:            target=540 proc=0x7FD53AC471D0 data=0xDEADBEED
/17:            attributes=DOOR_UNREF|DOOR_NO_CANCEL|DOOR_ON_TPD
/17:            uniquifier=1108
/17:    door_call(3, 0x7FFF733FF990)                    = 0
/17:            data_ptr=0x7FFFBEEC0000 data_size=211
/17:            desc_ptr=0x0 desc_num=0
/17:            rbuf=0x7FFFBEEC0000 rsize=25600
/17:    close(1948263178)                               Err#9 EBADF
/17:    close(1635020399)                               Err#9 EBADF
[...]

many more with absurd fds, the a large number of
/17:    close(0)                                        Err#9 EBADF

ultimately
/17:        Incurred fault #6, FLTBOUNDS  %pc = 0x7FFFBF161128
/17:          siginfo: SIGSEGV SEGV_MAPERR addr=0x00887000
/17:        Received signal #11, SIGSEGV [caught]
/17:          siginfo: SIGSEGV SEGV_MAPERR addr=0x00887000

gdb shows
Thread 18 received signal SIGSEGV, Segmentation fault.
[Switching to Thread 8 (LWP 8)]
0x00007fffbf161128 in res_nclose () from /lib/64/libresolv.so.2
3: x/i $pc
=> 0x7fffbf161128 <res_nclose+56>:  mov    0x0(%r13),%eax
(gdb) bt
#0  0x00007fffbf161128 in res_nclose () from /lib/64/libresolv.so.2
#1  0x00007fffbf1611a5 in res_ndestroy () from /lib/64/libresolv.so.2
#2  0x00007fffbf15f5c6 in __res_vinit () from /lib/64/libresolv.so.2
#3  0x00007fffbf15f57b in res_ninit () from /lib/64/libresolv.so.2
#4  0x000000000040124c in net(.text) ()
#5  0x000000000046c351 in runtime.asmcgocall ()
    at /opt/golang/swarm/goroot/src/runtime/asm_amd64.s:872
#6  0x00007fff75fffe58 in ?? ()
#7  0x00000000004439b2 in runtime.exitsyscallfast.func1 ()
    at /opt/golang/swarm/goroot/src/runtime/proc.go:4271
#8  0x000000000046a713 in runtime.systemstack ()
    at /opt/golang/swarm/goroot/src/runtime/asm_amd64.s:509
#9  0x0000000000200000 in ?? ()
#10 0x000000c00030e1a0 in ?? ()
#11 0x00007fff75fffee0 in ?? ()
#12 0x000000000046a605 in runtime.mstart ()
    at /opt/golang/swarm/goroot/src/runtime/asm_amd64.s:394
#13 0x00000000004019f4 in runtime/cgo(.text) ()
#14 0x00007fffbf5e3240 in ?? ()
#15 0x0000000000000000 in ?? ()

which lets me suspect that Go gets res_state/struct __res_state * wrong somehow.

I've confirmed that now: struct __res_state has never been initialized after state has been allocated in net/unix_cgo.go:cgoResSearch.  However, this is a clearly documented requirement in Solaris resolv(3RESOLV):
       State information is kept in statp and is used to control the  behavior
       of  these  functions.  Set statp to all zeros prior to making the first
       call to any of these functions.

This way, depending on the vagaries of memory allocation various fields in the struct are set to random values, e.g. _vcsock, _u._ext.nscount, and _u._ext.nssocks[].  This way, res_nclose tries to close a potentially large number of random values, which will all fail, and ultimately leads to the SEGV observed.
The attached patch seems to fix this (it's a bit hard to tell since the success of failure of the resolver tests depends very much on memory layout).  net/cgo_unix_syscall.go will need a definition of _C_memset, too.
res.patch.txt

I'll send a different patch.  @rorth thanks for finding the problem.

Great, thanks a lot for your help.

The memory clearing patch is committed.

We got a green build! Thanks all.

The solaris-amd64 builder has been failing with an infra failure for a day now.  I have no idea what that's supposed to mean and the logs (both on the gotip-solaris-amd64 build page nor the local logs gave me any clue what might be going on.  Any suggestions?

@rorth It initially failed due to a bad rollout on the LUCI side, but then the machine got quarantined due to too many consecutive failures (that were not related to a build). I'll figure out how to get that resolved ASAP.

I'm told the machine just has to be rebooted. :( Sorry for the inconvenience. Whenever you get the chance, can you do that please? Thanks.

Anyway: I've just rebooted the zone.

Thanks, it appears to be back online.

Right, thanks for your help.


Removed IMG_Init() and IMG_Quit()

avif side looks broken to me:
--- a/src/IMG_avif.c
+++ b/src/IMG_avif.c
@@ -214,3 +214,3 @@ bool IMG_isAVIF(SDL_IOStream *src)
         /* This might be AVIF, do more thorough checks */
-        if (!IMG_InitAVIF()) {
+        if (IMG_InitAVIF()) {
             avifROData header;
@@ -368,3 +368,3 @@ SDL_Surface *IMG_LoadAVIF_IO(SDL_IOStream *src)

-    if ((IMG_InitAVIF()) {
+    if (!IMG_InitAVIF()) {
         return NULL;

avif side looks broken to me:

Yes indeed, thank you!

@madebr, did I break CI here?

@madebr, did I break CI here?

No, it's the latest libjxl that decodes jxl images in another way, with a delta-color bigger then our tests allow.
https://github.com/libsdl-org/SDL_image/actions/runs/12130547154/job/33821102023?pr=482#step:13:357

On the other hand, MSVC also fails which uses our vendored libjxl library. (We vendor an older version)

@madebr, did I break CI here?

--- a/src/IMG_avif.c
+++ b/src/IMG_avif.c
@@ -118,3 +118,3 @@ static bool IMG_InitAVIF(void)

-    return false;
+    return true;
 }
diff --git a/src/IMG_webp.c b/src/IMG_webp.c
index 2541d86..57e76d3 100644
--- a/src/IMG_webp.c
+++ b/src/IMG_webp.c
@@ -100,3 +100,3 @@ static bool IMG_InitWEBP(void)

-    return false;
+    return true;
 }

Getting various drivers to init on demand is good, but how do they clean up without an explicit quit? I saw one of these calls CoCreateInstance during init, for example.

They don't, but in practice I don't think unloading the image DLLs is that important these days. The WIC driver is the only one that does CoCreateInstance(), and I think we can potentially just drop that.


Missing Output window when running python prg

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

[severity:I'm unable to use this version]
After having installed Python 3.12.6 and MS Visual studio I can run my program, no errors, but I cannot see the proper output (window).
I just use "print" to show if program works.

Original Comments
Feedback Bot on 9/20/2024, 09:43 AM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Hi,
after I have removed the last line of code, it works!
I was testing the strange example, written in a booklet, it seems there is something wrong.
I didn't understand the code, therefore I was trying this example.
You may close this ticket.
Thanks for your patience!


Upgrade iam-auth for versions 1.21 to 1.26

Issue #, if available:
Description of changes:

Upgrade iam authenticator to v0.5.13 for versions 1-21 to 1-24
Upgrade iam authenticator to v0.6.4 for versions 1-25 to 1-26
Update README accordingly

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/lgtm