Error during make install

I was running make install as described in the readme and the following error showed up:
avanderlee@Antoines-MBP-2 CreateAPI % make install
swift build --disable-sandbox -c release
warning: Usage of /Users/avanderlee/Library/org.swift.swiftpm/collections.json has been deprecated. Please delete it and use the new /Users/avanderlee/Library/org.swift.swiftpm/configuration/collections.json instead.
Building for production...
Build complete! (0.15s)
warning: Usage of /Users/avanderlee/Library/org.swift.swiftpm/collections.json has been deprecated. Please delete it and use the new /Users/avanderlee/Library/org.swift.swiftpm/configuration/collections.json instead.
mkdir -p /usr/local/bin
sudo cp -f /Users/avanderlee/Developer/GIT-Projects/Forks/CreateAPI/.build/arm64-apple-macosx/release/CreateAPI /usr/local/bin/create-api
cp: /Users/avanderlee/Developer/GIT-Projects/Forks/CreateAPI/.build/arm64-apple-macosx/release/CreateAPI: No such file or directory
make: *** [install] Error 1
avanderlee@Antoines-MBP-2 CreateAPI %

I'm using Xcode 13.4.1 (13F100) and I'm on this machine:

Thanks for flagging! I'll take a look 👀

Fixed by https://github.com/CreateAPI/CreateAPI/pull/54, I will merge shortly 👍

Please pull down main to try it again and let me know if you have any more issues 🙏

I got it working using Mint in the end, so all good! Thanks for fixing this so quickly 💪


can't run stable_diffusion_v2_1_webui in kaggle because it default still python 3.7

hello camenduru thanks for the amazing notebook and I really appreciate it. I just wondering is there a way to run SD 2.1 in kaggle.
here the error message when I try to run it on kaggle.
Error code: 1 stdout: <empty> stderr: ERROR: Ignored the following versions that require a different python version: 2022 Requires-Python >=3.8,<4.0 ERROR: Could not find a version that satisfies the requirement blendmodes==2022 (from versions: 2020, 2020.1, 2020.2, 2020.2.1, 2020.2.2, 2020.3.0, 2021, 2021.1, 2021.2, 2021.3, 2021.3.1, 2021.3.2, 2021.3.3) ERROR: No matching distribution found for blendmodes==2022

maybe you are missing -b v1.5 part !git clone -b v1.5 https://github.com/camenduru/stable-diffusion-webui
this is working code
!pip install torch==1.12.1+cu113 torchvision==0.13.1+cu113 --extra-index-url https://download.pytorch.org/whl/cu113
!pip install https://github.com/camenduru/stable-diffusion-webui-colab/releases/download/0.0.14/xformers-0.0.14.dev0-cp37-cp37m-linux_x86_64.whl

!git clone -b v1.5 https://github.com/camenduru/stable-diffusion-webui
%cd /kaggle/working/stable-diffusion-webui

!sed -i -e 's/numpy==1.23.3/numpy==1.21.6/g' requirements_versions.txt
!sed -i -e 's/fairscale==0.4.9/fairscale==0.4.6/g' requirements_versions.txt

!wget https://huggingface.co/stabilityai/stable-diffusion-2-1/resolve/main/v2-1_768-ema-pruned.ckpt -O /kaggle/working/stable-diffusion-webui/models/Stable-diffusion/v2-1_768-ema-pruned.ckpt
!wget https://raw.githubusercontent.com/Stability-AI/stablediffusion/main/configs/stable-diffusion/v2-inference-v.yaml -O /kaggle/working/stable-diffusion-webui/models/Stable-diffusion/v2-1_768-ema-pruned.yaml

!python launch.py --share --force-enable-xformers


BUG while using user_followers() code expample: followers = await cl.user_followers(cl.user_id)

Try HikerAPI SaaS with a free trial https://hikerapi.com/p/KhMxYMSn
Describe the bug
followers = await cl.user_followers(cl.user_id)
when using the above function im getting the below error message in the output
To Reproduce
followers = await cl.user_followers(cl.user_id)
Traceback
Show your full traceback so that it is clear where exactly the error occurred.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Output
Status 201: JSONDecodeError in public_request (url=https://www.instagram.com/username/?__a=1&__d=dis) >>>
'NoneType' object has no attribute 'cookies'
Traceback (most recent call last):
File "D:\Projects\Python\raph\venv\Lib\site-packages\aiograpi\mixins\user.py", line 891, in user_followers
users = await self.user_followers_gql(user_id, amount)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Projects\Python\raph\venv\Lib\site-packages\aiograpi\mixins\user.py", line 780, in user_followers_gql
items, end_cursor = await self.user_followers_gql_chunk(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Projects\Python\raph\venv\Lib\site-packages\aiograpi\mixins\user.py", line 732, in user_followers_gql_chunk
self.inject_sessionid_to_public()
File "D:\Projects\Python\raph\venv\Lib\site-packages\aiograpi\mixins\auth.py", line 851, in inject_sessionid_to_public
self.graphql.set_cookies(cookie)
File "D:\Projects\Python\raph\venv\Lib\site-packages\aiograpi\reqwests.py", line 87, in set_cookies
self._client.cookies.set(k, v)
^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'cookies'
Desktop (please complete the following information):

OS: [e.g. Ubuntu 21.04]
Python version [e.g. 3.8.3]
aiograpi version [e.g. 1.9.3, not "latest"]
moveipy version if used
imagemagick version if used

Additional context
Add any other context about the problem here.

the same bug, any idea?

@proxies.setter
def proxies(self, p):
self._proxies = p
self._set_client()
looks like setter never call

I have found a workaround, see https://github.com/subzeroid/aiograpi/issues/90


Revert "Fix xds_test on MacOS by configuring ..."

Reverts istio/istio#5779
Sorry I missed what the CLA bot said. It seems you haven't signed the CLA yet. Please fix that one up and then resubmit the Pr.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

tests/OWNERS [rshriram]

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

FYI @holgero ..

@rshriram: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
9cb3fac0c3ed5fe5faa434ebc37bba961036e2b2
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram I thought I did have my company signed the CLA and as far as I know it has been done by adding me to a google group (SAPatGoogle).
I think the bot just got confused by the rebase to master of this change and lost track of who has signed the CLA.

Also the page https://cla.developers.google.com/clas tells me that there is a corporate agreement signed.


Voice Recieving

Need to start on receiving voice. Ideally convert to PCM16 with DCA. (i need u @bwmarrin)

hahah. hmn, okay.. let me think how I would do this.
Receiving is going to be more difficult.  You need a separate opus decoder for each person/bot that is talking.  So if you've got 12 people in a channel chatting away, you need 10 decoders running and for opus to work right (as I understand) they need to remain active the entire time each person/bot is in the channel - or at least speaking..

@bwmarrin Would we be able to just use FFmpeg with libopus?

No, I don't think it would support the raw opus data that you receive from Discord.

Kinda-implemented, able to receive Opus. Waiting on DCA rewrite for decoding.


Uber cuts 350 employees in latest round of layoffs.

Did this event affect uber web development team?

This has had no affect on this project. 👍


test: testing if main is healthy

Fixes #issue-number-here
What

changed thing a for b
also did this other unrelated thing in my path

Why

to fix a bug
to add more value to the user

Testing done

tested the new feature
tested the bug fix

Decisions made

Checks

[ ] I have tested this code
[ ] I have reviewed my own PR
[ ] I have created an issue for this PR
[ ] I have set a descriptive PR title compliant with conventional commits

Reviewing tips

User facing release notes

checked!


added condition for if song is already playing

If the audio element getting changed included an autoplay attribute, causing the audio to automatically play, the pause/play button would not change to the pause state or respond at all. This is just a condition to make sure it is in the pause state if already playing.
Edit: Added another fix for setting the button back to the pause state when finished sliding and the audio still plays.

Many thanks Leonard. Sorry it took me so long to reply!


helm upgrade with --wait support jobs in manifest to be completed

What this PR does / why we need it:
Resolves #5948
Helm --wait should wait for all manifest resources to be ready
However helm doesn't wait for jobs to be completed when job appears in the manifest, not in the hooks
Special notes for your reviewer:
I noticed that many are using jobs in the manifest, not just in hooks. They need all the jobs (in the manifest) to be completed to mean that helm release is successfully installed/upgraded
For example, a job performs an initialization task. Although when deployment and related pods are all in the ready state, the job is incomplete and the service is still unavailable, then this release should be considered as not ready
Why jobs not using hooks? we want jobs managed together with the release lifecycle

can you write a unit test to cover this case. Thanks.

please write a unit test to cover this case. Thanks.

@bacongobbler Thanks for your attention! I have completed the unit test for this case and any other cases. Please take another look?

@zh168654 do you know what the plan is for this one. Is it going to be merged. Itll be a huge addition to helm when this goes in. It might make use of ordered hooks that all run post-install, less attractive than jobs that can run in parallel to the deployment of the pods.

Adding to 3.4.0 for review.

@bacongobbler I'm ready for a review on this. Would be great to see this feature in 3.4.0

@zh168654 Sorry for the slow response. We talked about this because of the impact.
People today depend on jobs not being behind the --wait flag. It would be a behavior change to put it behind the flag in Helm v3. In order to wait for jobs we would need a second flat to opt-in. Can you make that change?

@mattfarina This sounds reasonable and I'd like to have a try. Is it okay to use --wait-jobs as the second flag, or do you have any suggestions?

@mattfarina @bacongobbler I've made the changes and introduced --wait-for-jobs. So CLI examples:
$ helm install --wait --wait-for-jobs mysql stable/mysql
Looking forward to your review. Thanks very much

@mattfarina Already updated and ready for review again

Another way to get this functionality would be #8661, which would avoid needing to expose a --wait-for-jobs flag.

Could also consider replacing --wait-for-jobs with e.g. HELM_EXPERIMENTAL_WAIT in this PR, and then if/when #8661 is implemented, this env var will simply provide expanded functionality beyond just waiting for jobs.

In our setup, we've actually run into both situations, some where we wanted jobs to be waited for, and some we did not. We'd been discussing potentially submitting a patch to have helm honor an annotation on the job to determine whether it's waited for; would that approach be more palatable than adding a new flag? (the default could be helm's current behavior)

@novas0x2a I agree something like a helm.sh/ignore-wait: true or helm.sh/ignore-status: true could be useful, for all resources not just Jobs, and could potentially fit under the same HELM_EXPERIMENTAL_WAIT flag and HIP, although that too is indeed orthogonal if there were a desire to separate them. It's possible kstatus could implement a similar annotation based functionality, in which case that could potentially be gotten for free in Helm, so a feature request there could be relevant.

@seaneagan waiting for jobs can't be an experiment in Helm v3 because we cannot make a change in Helm v3 around this. It would break semver. The earliest the change could be made in Helm v4. So, a flag makes it something supported in v3. Using HELM_EXPERIMENTAL_WAIT would not really make that the case.
There is also a separation in control. Things in the chart like an annotation are for chart creators. Those who use the Helm cli to add flags are Helm users and chart consumers. Those are different roles that are often fulfilled by people at different companies. So a flag or an annotation is about who we give control to in the situation.


403 Forbidden

Describe the bug
When I start the docker container, it does not connect and produces a 403 Error.
To Reproduce
Steps to reproduce the behavior:

What version of AdGuardHome sync used?
v0.4.3

What version of AdGuardHome us used?
v0.108.0-b.9

How does the configuration look?
`cron: "*/1 * * * *"

origin:
url: http://<IP_ADDRESS>:9970
insecureSkipVerify: true
username: username
password: password
replica:
url: http://<IP_ADDRESS>:9970
insecureSkipVerify: true
username: username
password: password
api:
port: 9080
username: username
password: password`

What is the error message?
Error getting origin status	{"from": "<IP_ADDRESS>:9970", "error": "403 Forbidden"}

Expected behavior

I expected the files to sync across.

Log Files
`-------------------------------------
_         ()
| |  ___   _    __
| | / | | |  /
| | _ \ | | | () |
|| |/ ||  __/
Brought to you by linuxserver.io
To support LSIO projects visit:
https://www.linuxserver.io/donate/
GID/UID
User uid:    1000
User gid:    1000
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 50-config: executing...
[cont-init.d] 50-config: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2022-06-12T12:56:10.665+0200	INFO	root	cmd/root.go:114	Using config file:/config/adguardhome-sync.yaml
2022-06-12T12:56:10.668+0200	INFO	sync	sync/sync.go:30	AdGuardHome sync	{"version": "0.4.3", "build": "2022-02-14T17:40:34Z"}
2022-06-12T12:56:10.669+0200	INFO	sync	sync/sync.go:50	Setup cronjob	{"cron": "*/1 * * * *"}
2022-06-12T12:56:10.669+0200	INFO	sync	sync/http.go:54	Starting API server	{"port": 9080}
2022-06-12T12:56:10.669+0200	INFO	sync	sync/sync.go:60	Running sync on startup
2022-06-12T12:56:10.670+0200	DEBUG	client	client/client.go:126	do get	{"host": "<IP_ADDRESS>:9970", "method": "GET", "path": "status"}
2022-06-12T12:56:10.673+0200	DEBUG	client	client/client.go:138	got response	{"host": "<IP_ADDRESS>:9970", "method": "GET", "path": "status", "status": 403, "body": "Forbidden"}
2022-06-12T12:56:10.673+0200	ERROR	sync	sync/sync.go:99	Error getting origin status	{"from": "<IP_ADDRESS>:9970", "error": "403 Forbidden"}
github.com/bakito/adguardhome-sync/pkg/sync.(*worker).sync
/home/bakito/go/src/github.com/bakito/adguardhome-sync/pkg/sync/sync.go:99
github.com/bakito/adguardhome-sync/pkg/sync.Sync.func3
/home/bakito/go/src/github.com/bakito/adguardhome-sync/pkg/sync/sync.go:61
`

Please share your /config/adguardhome-sync.yaml

Please share your /config/adguardhome-sync.yaml
The Config file is in the issue above but here it is:
cron: "*/1 * * * *"

origin:
url: http://<IP_ADDRESS>:9970/
insecureSkipVerify: true
username: username
password: password
replica:
url: http://<IP_ADDRESS>:9970/
insecureSkipVerify: true
username: username
password: password
api:
port: 9080
username: username
password: password

@nknab I was not able to reproduce this issue.
Do you see any errors in  the logs of your origin instance?
Is the origin instance setup correctly?
Are passwords correct.

closing, since there's no update


Fix a number of crashing bugs in the python wrappers

The function pythonObjectToVect() returns, by design, a nullptr when it's called with either None or an empty sequence.
However, there are a bunch of spots in the code where the results of pythonObjectToVect() are de-referenced without being checked.
This fixes all of those.

Changes are great, the error message it self could be a little more clear.

Makes sense. Those are now all done.


I can't use the _Bash theme

??? _Bash is an example

Can you explain further? Do you mean that it is not intended to be used?
Because i see it is referenced in themes/_base.sh and has color data  in data/themes.json even displayed on the website. I thought it looked great and wanted to use it as well but it does not populate in the script. I guess I can add the colors manually.

yea .. i guess i have to rename it to end with example. :smile:


Firefox: "Too much recursion"

On the Javascript console in Firefox (Iceweasel 38.1.0) I get a vast number of "too much recursion" messages.
too much recursion app.js:107336:19
too much recursion app.js:103781:12
too much recursion app.js:56096:10
etc.

I can confirm I get these error messages as well in Firefox ("for Ubuntu") 38.0.  Seems to really slow the browser down, too.

have you checked to see if your computer is plugged in? easy mistake.

I'm no longer getting this message as of 5156dc809ff101f581da696e12f51e6cf26c2f9c.  Closing this for now; if this pops up again for anyone else, please re-open this issue.

Did a very brief check, no longer getting errors here either.

This issue has reared its ugly head again, I'm sad to report:
too much recursion
var result = request.responseText; app.js (line 110296, col 8)

too much recursion
m._isValid = !isNaN(m._d.getTime()) &&
app.js (line 21601, col 26)

too much recursion
if (isCustomAttributeFn(attributeName)) {

Only seems to happen in Firefox, as before.

i'm guessing this sometimes happens (depending on network/cpu) due to the vast number of async operations happening on load to get all the markets and subsequent data.   although, i wouldn't call it very recursive.  in fact, the market fetching has been flattened somewhat and i would say only goes about 3 deep per market (one async call, making another, then possibly another.
so, i'm not exactly sure.

it could also have been relating to the unoptimized react rendering.  i'm not getting this anymore after test firefox mac os and windows with both remote and local (local lan) geth instance.
going to close for now.


Move log to delete(), add more information to log in clean_up()

Short description:

Move logs with resource data to delete()
Only log if the resource exists
Add more information to log in clean_up()

More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

/verified


Release notes for 8 Aug

@bensonlee5 anything else you want to add here?

@eriis1 (maybe in a separate PR) - can you add a short snippet to demo how to query from an agent?  I think it prob would go on sdk/markdowns/AgentDataModels

@eriis1 (maybe in a separate PR) - can you add a short snippet to demo how to query from an agent? I think it prob would go on sdk/markdowns/AgentDataModels

just took a stab at this and am merging in; let me know if it's off (I just referenced your remote agent PR)

the bigquery APIs aren't released yet

the bigquery APIs aren't released yet

ah ok - let me remove from docs


Ionic 2 cli section typescript

The CLI section of the Ionic 2 docs seems to be missing references to how to generate a typescript ionic 2 project. I was not able to find a reference to using --ts like there is in the tutorial in the Getting Started secition.

Is this still necessary?

Nope, already have a note in there about generating a typescript project.
http://ionicframework.com/docs/v2/getting-started/tutorial/

swiggity sweet


Follow on items for Regex

Throw a specific exception for the None match. Originally posted by @jlowe in https://github.com/NVIDIA/spark-rapids/pull/4071#discussion_r746601861

Consider to tighten the test to check for the specific expected result. Right now the test succeeds even with typos.

This is being handled by #4071 per this discussion and corresponding change.


Spelling Mistake | TypeScruot > TypeScript

Url: https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html#version-selection-with-typesversions
Section: Version selection with typesVersions
Paragraph: 4
Error: TypeScruot
Valid: TypeScript

Thanks! This will be fixed on the next deploy


Add small util to build nuclide string from Z and A values

As a helpful util, build_nuclide_string() is added to radioactivedecay.utils to build a nuclide string from atomic number and atomic mass (optional). If atomic mass is omitted, the function returns the element symbol corresponding to the input atomic number.

Please disregard this PR, as changing the DecayData class to hold a DataFrame will resolve this issue.

Reopening this to add simple Z, A parsing without the need for major refactoring.

Hi @lemointm
There are some really great ideas in this PR! I think it would be great if we could do the following:

Since you added the stable nuclides, I think the Radionuclide class should be subsumed into this new Nuclide class. All the functionality of Radionuclide works for the stable nuclides, so renaming to Nuclide will make it clearer that stable nuclides are supported.
The new Z and A properties are great. What about adding an atomic_mass property or method as well? To return the atomic mass in g/mol?
As mentioned on Slack, reading the csv file on every instantiation is inefficient. Actually, given Wolfgang's suggestions and the fact that the package file I/O's might have to be overhauled in future, I was thinking instead of reading a CSV of the element symbol data, it might just be easier to just write this into a list or dict into the code itself. It's not so big a list to do this.
In terms of functionality, the class you drafted doesn't appear to support metastable state specification. I was thinking for increasing the general usability of the package, it would be good if support was added for PyNE-style zzzaaassss canonical ids. This also has the advantages that the init() arguments for Nuclide and Inventory will become simpler - no need to have the second and third int parameters for A and state number that are only sometimes used. We'd then need some function or method to convert nuclide name strings to zzzaaassss, On the TARDIS side zzzaaassss ints will be easy to process to get what you need just with // integer divisions.

I'm happy to guide you in coding this, and writing the docs and tests!

I added most of the functionality, although it was hasty and may have some bugs; next I'll get on to doc updates and tests! Let me know if you find anything that could be improved.

Oh one tiny thing - I noticed when I added the Radionuclide methods to Nuclide that the plot method is again adding extra white space, I may have not updated my code in this branch to include the edits you made to fix this, I can double check.

There are still some a few changes I need to make, namely merging devel to get your changes to Radionuclide that will be put into nuclide, and fixing tests, but the latest commit has some nice fixes to get around the element problem (namely, element symbol parsing is put in utils so that when it's needed for TARDIS we can use the utils and not have element parsing needed in Nuclide). Let me know what you think!

Here's the merged changes, this adds your devel changes to nuclide at least... next is fixing tests and docs!

Here's some small comments I noticed while looking through:

decaydata.py has picked up an old part of the docstring on lines 344-345 - the atomic masses are now in the DecayMatrices class - so those lines can be deleted
nuclide.py in the attributes section of the Nuclide docstring, list all the attributes (add the atomic_mass, prog_bf_modes and decaydata attributes)
L67 init() now raises TypeError instead of ValueError
In the refactoring, the eq, ne and hash methods have been deleted - did you intend this?
util.py L142 - would be good to have a docstring for build_nuclide_string
Radionuclide -> Nuclide on L160

Going well so far! Thanks

I think it should all be working properly now, and I fixed up the loose ends with Radionuclide references and such. Docs are next!

I added the id parser to utils, and actually placed it in inside parse_nuclide as well so that most of the references in Inventory.py were already good to go! I also added a good amount of tests for both utils.py and Nuclide.py, let me know if I missed any functionality.


Translation to Czech

Started to translate.

spojme síly // we can join our forces, I have a beginning translated already at
https://github.com/omichalek/duvera/
I am aiming at

informal addressing of the player (tykání) - I usually do not like this, but I feel that using the formal addressing would feel alien to children - one of the target groups
gender neutral language
...
yes, our language is complicated

Also, the used font lacks Czech letters, suggested replacements are welcome!

Since the only Czech translation in progress has been stuck half-finished for a while and contains some serious mistakes in basic terminology, I'm starting from scratch here.

Hi! @nextghost
What is state of your translation? Is it finished and published? If not I can do it, if you want.

@nadvornix The game is completely translated but I haven't had time to finish translating the extra notes. I'll get to it sometime in April.

Great, thanks. In case you would want help don't worry to ask me.

@nextghost Hi, how it's going?

@nadvornix Still working on it, check back in the weekend.

Thanks!

Thank you all! It's been pulled :) https://github.com/ncase/trust/pull/97


Use GHA checkout v2 for faster fetch

Hey, I just made a Pull Request!
Let's use checkout@v2 on GitHub Actions because it is faster at the initial fetch :)
Ref. https://github.com/actions/checkout/releases/tag/v2.0.0

This PR won't make any changes for the code so I don't think the checklist is necessary, but tell me if I'm wrong!
:heavy_check_mark: Checklist

[ ] All tests are passing yarn test
[ ] Screenshots attached (for UI changes)
[ ] Relevant documentation updated
[ ] Prettier run on changed files
[ ] Tests added for new functionality
[ ] CODEOWNERS updated (for new stuff)
[ ] Regression tests added for bug fixes

Thanks!


Support for WebSocketClient

Please add websocket/wss client to DSL. For example, jmeter has a good websocket plugin https://jmeter-plugins.org/?search=websocket-samplers.
This will greatly simplify the work !

Upvote!

Upvote, it's necessary and useful

Upvote!

Upvote!

Upvote

Upvote !

Upvote, it's super necessary!

"Upvote !"

Upvote!

Upvote!

Upvote!

Upvote!

Upvote!

upvote!

Upvote !

upvote

Upvote!

Wow, a lot of suden upvoting in this issue. Do you have any additional insight why is this important for so many people in such short time period?
There is also this issue which requests the same support .

Hi Rebelenda ! Glad you heard us, thank you!
We all came to you from the Russian Performance tests and QA communities. A lot of guys use Jmeter dsl and we would like to see the ability to test websockets. We know that you can add your script through the DslJavaSample + BaseSampler wrapper. But I would like to see the ability to use a websocket client according to the standard like http. We will be very grateful to you if you implement this.

Wow, a lot of suden upvoting in this issue. Do you have any additional insight why is this important for so many people in such short period of time?
There is also this issue which requests the same support .

https://github.com/abstracta/jmeter-java-dsl/issues/286#issuecomment-2515390470

Hello @rabelenda!
We are all very interested in this feature.
Resolving this issue would be highly appreciated by the performance testing community

Hi, @rabelenda! We will highly appreciate you if you increase the priority of implementing this functionality. This really helpful to build performance testing tools for numerous projects.

Upvote!

Can you provide different samples (maybe jmx files, potentially scrumbling urls and any potential sensitive config) of the main ways you use the samplers plugin?
I am interested in identifying what are the main/most common scenarios to ease their usage, and also identify the scope (how much features & effort is needed to support most of the use cases).

Upvote!

Hi @rabelenda, thank you for supporting this issue. Here are the answers to your questions and the simple script example.
As for samplers, the most popular:

WS Write
WS Read
WS Open
WS Close
WS Ping Pong sampler
WS Text Frame Filter

As for loading the body samplers, I load them from the txt files. I don't use the binary response assertion, the simple text Response assertion works for me
Example.zip

Hi @rabelenda, sorry for the long reply. There are some good usage examples here: https://github.com/Luminis-Arnhem/jmeter-websocket-samplers/tree/master/samples
Thx @NaumVik thx for examples !


Proportional scaling in Deployments

@kubernetes/deployment ptal

This change is

LGTM from a docs perspective. Could somebody who knows more about it than me give it a once-over?

@janetkuo Can you give a tech review?

@mfojtik can you have a tech review here?

few nits, lgtm otherwise :)

Comments addressed.

@jaredbhatti can we get this merged?

@janetkuo can we get this merged

@janetkuo thanks for your comments, updated

One last comment, LGTM otherwise

@janetkuo done

@david-mcmahon can we get this merged? Thanks

@david-mcmahon can we get this merged? Thanks

oops, meant @devin-donnelly


R5 value

Looking at original schematics for Disk II interface, R5 seems to be 47KΩ not 49KΩ as per your design. Moreover 49K is practically impossible to find in the contrary to 47K.

Indeed it is, I think that has to have been a typo. 47k is what I used in my builds.

Cool, thanks! That was my assumption as the rest of resistors have value as per original design. Although it's a minor issue to me, you might think of correcting the silkscreen and BOM.

yep, it'll be fixed in next revision. thanks!


BadGoal returns positive reward

I have the environment up and running well.  However, when I run into a "BadGoal" it returns a positive reward, just like a "GoodGoal" (0.5 to 5 depending on the size).  It shows up with the correct color (red) in the arena and "GoodGoal" shows up green, as expected.

Hello,
thanks for reporting this bug, I've fixed it and will include this as part of v0.6 which should be released in 2 days.
Ben

Should be fixed in the latest version.

Tested and found fixed in version 0.6


handle_error logic obfuscates original error stack trace

If the logic of this function has an error occur, it will prevent any stack trace from showing for the original error: https://github.com/opsani/servox/blob/b4fe0f84ea069a541698dfcb8e6deaf170580da5/servo/connectors/kubernetes.py#L1599
I have a tentative solution here but the resulting logs could still be better organized, just not sure how yet: https://github.com/opsani/servox/blob/d7f8f52e57be5812e6673e91b1bf5d0d824fca48/servo/connectors/kubernetes.py#L2052-L2078
Note example_output.txt and how we only see the stack trace for the failed rollback and very minimal info on the original error (422
Reason: Unprocessable Entity)

This is a good catch and I think there's a simpler solution:
We can use the raise [ErrorType] from error explicit exception chaining syntax (see PEP 3134 -- Exception Chaining and Embedded Tracebacks) to wrap the underlying error and ensure that the traceback is maintained.
Does this change cover it without having to trampoline through the try/except block?
async def handle_error(self, error: Exception, mode: "FailureMode") -> bool:
    if mode == FailureMode.CRASH:
        raise RuntimeError(
            "an unrecoverable failure occurred while interacting with Kubernetes"
        ) from error

    elif mode == FailureMode.IGNORE:
        self.logger.warning(f"ignoring runtime error and continuing: {error}")
        self.logger.opt(exception=error).exception("ignoring Kubernetes error")
        return True

    elif mode == FailureMode.ROLLBACK:
        await self.rollback(error)
        return True

    elif mode == FailureMode.DESTROY:
        await self.destroy(error)
        return True

    else:
        raise NotImplementedError(
            f"missing error handler for failure mode '{mode}'"
        ) from error

Went ahead and pushed the error chaining to master. Lemme know if that covers it or we need to do more

The change is good, it covers one of the cracks the original error can slip through. However, it does not address particular crack I raised this issue for. Note in the following stack trace that an exception is bubbling out of the call to await self.rollback(error) causing the original error to be discarded:
  File "/home/linkous/code_review/servox/servo/connectors/kubernetes.py", line 2309, in apply
    if await optimization.handle_error(
             │            └ <function BaseOptimization.handle_error at 0x7fc446130dc0>
             └ DeploymentOptimization(name='web-main/main', timeout=Duration('5m' 0:05:00), deployment_config=DeploymentConfiguration(descri...

  File "/home/linkous/code_review/servox/servo/connectors/kubernetes.py", line 1630, in handle_error
    await self.rollback(error)
          │    │        └ ApiException()
          │    └ <function DeploymentOptimization.rollback at 0x7fc44613b310>
          └ DeploymentOptimization(name='web-main/main', timeout=Duration('5m' 0:05:00), deployment_config=DeploymentConfiguration(descri...

  File "/home/linkous/code_review/servox/servo/connectors/kubernetes.py", line 1762, in rollback
    await asyncio.wait_for(
          │       └ <function wait_for at 0x7fc448505f70>
          └ <module 'asyncio' from '/home/linkous/.pyenv/versions/3.8.5/lib/python3.8/asyncio/__init__.py'>

  File "/home/linkous/.pyenv/versions/3.8.5/lib/python3.8/asyncio/tasks.py", line 483, in wait_for
    return fut.result()
           │   └ <method 'result' of '_asyncio.Future' objects>
           └ <_GatheringFuture finished exception=ApiException()>

  File "/home/linkous/code_review/servox/servo/connectors/kubernetes.py", line 1177, in rollback
    self.obj = await api_client.create_namespaced_deployment_rollback(
    │    │           │          └ <function ExtensionsV1beta1Api.create_namespaced_deployment_rollback at 0x7fc4463360d0>
    │    │           └ <kubernetes_asyncio.client.api.extensions_v1beta1_api.ExtensionsV1beta1Api object at 0x7fc443d3f430>
    │    └ {'api_version': 'apps/v1',
    │       'kind': 'Deployment',
    │       'metadata': {'annotations': {'deployment.kubernetes.io/revision': '1',
    │         ...
    └ {'api_version': 'apps/v1',
       'kind': 'Deployment',
       'metadata': {'annotations': {'deployment.kubernetes.io/revision': '1',
         ...

  File "/home/linkous/.cache/pypoetry/virtualenvs/servox-eNeZ9xha-py3.8/lib/python3.8/site-packages/kubernetes_asyncio/client/api_client.py", line 189, in __call_api
    raise e
  File "/home/linkous/.cache/pypoetry/virtualenvs/servox-eNeZ9xha-py3.8/lib/python3.8/site-packages/kubernetes_asyncio/client/api_client.py", line 182, in __call_api
    response_data = await self.request(
                          │    └ <function ApiClient.request at 0x7fc446404940>
                          └ <kubernetes_asyncio.client.api_client.ApiClient object at 0x7fc443d3f640>
  File "/home/linkous/.cache/pypoetry/virtualenvs/servox-eNeZ9xha-py3.8/lib/python3.8/site-packages/kubernetes_asyncio/client/rest.py", line 230, in POST
    return (await self.request("POST", url,
                  │    │               └ 'https://<IP_ADDRESS>:8443/apis/extensions/v1beta1/namespaces/default/deployments/web-main/rollback'
                  │    └ <function RESTClientObject.request at 0x7fc4463f9e50>
                  └ <kubernetes_asyncio.client.rest.RESTClientObject object at 0x7fc443d3fe50>
  File "/home/linkous/.cache/pypoetry/virtualenvs/servox-eNeZ9xha-py3.8/lib/python3.8/site-packages/kubernetes_asyncio/client/rest.py", line 187, in request
    raise ApiException(http_resp=r)
          │                      └ <kubernetes_asyncio.client.rest.RESTResponse object at 0x7fc445e681f0>
          └ <class 'kubernetes_asyncio.client.exceptions.ApiException'>

kubernetes_asyncio.client.exceptions.ApiException: (404)
Reason: Not Found
HTTP response headers: <CIMultiDictProxy('Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'Date': 'Wed, 11 Nov 2020 17:13:31 GMT', 'Content-Length': '174')>
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}

My proposed solution is to wrap the handle_error() logic in a try/catch block that ensures both exceptions get logged/raised like such (I'm not sure which error should raise from which):
https://github.com/opsani/servox/blob/a6c82478022d1f1d8604896b7b3463cc8d7b41a9/servo/connectors/kubernetes.py#L2146-L2173

I see your point here. Thanks for following up and reopening.
In ca4b3e5 I just did the same trick again using the raise from syntax.
We don't need to trap them separately and log/reraise independently. When PEP 3134 was adopted the traceback module and friends were updated to become aware of exception chaining. Covering this other missed chaining scenario should mean that whatever catches it downstream will show you the full chain.
Reopen if I again missed something.


fix: updates to reflect updated API

havent checked these but this should get the ball rolling for the updates to the code to match the Carrier API updated key structure

looks good, just the double _ and two ruff errors about white space.
Thanks for writing this up, I'll merge it once you update.


Allow customization of built-in autopilot

A great addition would be more control of the build-in autopilot. Major issues are here track control as well as velocity control. This would allow a more controlled dataset generation using CARLA.

Any update to this feature?  E.g. lane changing but still in autopilot mode.


Support from_attribute similar to Panel widgets .from_param

With Panel you can (see)
widget = pn.widgets.IntSlider.from_param(Example.param.unbounded_int, start=0, end=100)

Being able to create single widgets from Pydantic Model Attributes would be very useful as well. Some method like the below would be useful
widget = from_attribute(pn.widgets.IntSlider, example, "unbounded", start=0, end=100)

Im not sure I understand what you are proposing. Do you mean to split up the logic inside the for loop of pydantic_widgets to a separate function so people can use the function to get a single widget instead of a dictionary with widgets for each field? Or do mean to just make this function more accessible to users that want to create the widgets and modify them themselves?

I actually don't understand the implementation of pydantic-panel yet. But what I propose is to expose functionality to create a single widget.
The motivation is that I have often seen with Param that users ask for help to define or get hold of single widgets.

Ok, I guess I can add documentation for how to do this and maybe some more user friendly docstrings. Currently this function is just used internally.

This is now solved via Pydantic pane supporting arbitrary python objects.
e.g. for the above example pn.panel(example, start=0, end=100) works.


[FLOC-3755] Fix benchmark no load scenario test

Fixes a non-executed test, that also contained a bug. The test passed a callback result to the stop method as an extraneous parameter. This was not detected because the test method did not start with the test prefix.
Also, changed interface test to avoid use of globals(), following a comment on Slack. https://clusterhqteam.slack.com/archives/flocker-benchmarking/p1450723154000373

Great, thanks.


when use two gpus in one node, error!

Hi, when I use 2 gpus in one node to train train_cmkd.py, the error like:
2022-11-25 09:49:08,244   INFO  Start training xxx/project_3D/CMKD-main/tools/cfgs/kitti_models/CMKD/cmkd_caic_R50_scd_V2(default)
epochs:   0%|          | 0/10 [00:00<?, ?it/s]
epochs:   0%|          | 0/10 [00:00<?, ?it/s]
Traceback (most recent call last):
File "/xxx/project_3D/CMKD-main/tools/train_cmkd.py", line 226, in
main()
File "/xxx/project_3D/CMKD-main/tools/train_cmkd.py", line 198, in main
merge_all_iters_to_one_epoch=args.merge_all_iters_to_one_epoch,
File "/xxx/project_3D/CMKD-main/tools/train_utils/train_utils.py", line 245, in train_model_cmkd
dataloader_iter = iter(train_loader)
File "/root/anaconda3/envs/CMKDK/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 355, in iter
return self._get_iterator()
File "/root/anaconda3/envs/CMKDK/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 301, in _get_iterator
return _MultiProcessingDataLoaderIter(self)
File "/root/anaconda3/envs/CMKDK/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 914, in init
w.start()
File "/root/anaconda3/envs/CMKDK/lib/python3.7/multiprocessing/process.py", line 112, in start
self._popen = self._Popen(self)
File "/root/anaconda3/envs/CMKDK/lib/python3.7/multiprocessing/context.py", line 223, in _Popen
return _default_context.get_context().Process._Popen(process_obj)
File "/root/anaconda3/envs/CMKDK/lib/python3.7/multiprocessing/context.py", line 284, in _Popen
return Popen(process_obj)
File "/root/anaconda3/envs/CMKDK/lib/python3.7/multiprocessing/popen_spawn_posix.py", line 32, in init
super().init(process_obj)
File "/root/anaconda3/envs/CMKDK/lib/python3.7/multiprocessing/popen_fork.py", line 20, in init
self._launch(process_obj)
File "/root/anaconda3/envs/CMKDK/lib/python3.7/multiprocessing/popen_spawn_posix.py", line 47, in _launch
reduction.dump(process_obj, fp)
File "/root/anaconda3/envs/CMKDK/lib/python3.7/multiprocessing/reduction.py", line 60, in dump
ForkingPickler(file, protocol).dump(obj)
TypeError: can't pickle spconv.core_cc.csrc.sparse.all.ops_cpu3d.Point2VoxelCPU objects
I start the code with:
CUDA_VISIBLE_DEVICES=0,1 python -m torch.distributed.launch --nproc_per_node=2 train_cmkd.py --launcher pytorch --cfg ${CONFIG_FILE} --tcp_port 16677 --pretrained_lidar_model ${TEACHER_MODEL_PATH}
when I use 1 gpu to train , it's ok! That's why?

Can give a version of pytorch, cuda, spconv ?


Sync.worker.js import error Module not found: ESM packages in NextJs

I am getting the following error when using useQuery in NextJs:

NextJs

/app directory (page.tsx)
"use client"
Version: 13.4.5

"use client";
import { useQuery } from "@/lib/schema/schema";

export default function Home() {
  const { rows } = useQuery(
    (db) => db.selectFrom("word").selectAll(),
    (row) => row
  );

  return (
    <main>
      <pre>{JSON.stringify(rows)}</pre>
    </main>
  );
}

Evolu

Version: ^6.1.1

Schema (@effect/schema)

Version: ^0.20.1

Data (@effect/data)

Version: ^0.12.6

Any idea how to solve? Is this an internal ESM issue?

Try to add experimental: { esmExternals: "loose" } in next.config.js. I think it's some Next.js bug.

Try to add experimental: { esmExternals: "loose" } in next.config.js. I think it's some Next.js bug.

This works, but it seems to give some problems with reloads (the page does not update after changes and other issues with setState). Feel free to close if you think this is related to Next.

@SandroMaglione Can you check https://github.com/evoluhq/evolu/tree/main/examples/nextjs, please?

Related:

When a dependency package has "type": "module" in package.json, and uses new Worker(new URL("./worker.js", import.meta.url)) to create a web worker, next build failed with

https://github.com/vercel/next.js/issues/33914

If I remove "type": "module", Next.js suddenly works without experimental: { esmExternals: "loose" }. The problem is it's not a valid ESM, so Node.js will refuse to work. If I change file extensions to .mjs, Next.js complains again.

ESM will be supported in React Native 0.72. Electron will support it soon too https://github.com/electron/electron/pull/37535. I'm considering releasing evolu-cjs lib build from evolu for edge cases and old bundlers.

So I used rollup with the rollup-plugin-off-main-thread plugin, and it worked. I was curious why so I compared codes, and the only difference was that the rollup output striped './' from the worker path. So I stripped it from my source code, and suddenly, Next.js works without esmExternals: "loose" 🤦
I spent weeks studying all Web Worker issues (e.g., https://github.com/lgarron/web-worker-compat). I was reading esbuild, rollup, and Next.js issues... for no real outcome because I used the wrong path format. And because Firefox 114 finally supports the module Web Worker.


Update to GOVERNANCE.md

Made the project name Orion.

 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.


Select2 forms

Select2 on all the forms is working along with proper CSS. This is the latest develop , and since there are no merge conflicts, you can merge it

will raise an other request


[SEDONA-207] Implemented a new geometry serde for supporting Z/M dimensions and better performance

Did you read the Contributor Guide?

Yes, I have read Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

Yes, the URL of the assoicated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-207. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?
New Geometry Serde
The new geometry serde was implemented in common/src/main/java/org/apache/sedona/common/geometrySerde/. The ShapeSerde used by Kryo serializer and the WKB based serde used by GeometryUDT were replaced by this new serde. Please refer to SEDONA-207 for a detailed explanation of this new geometry serde.
GeoParquet
GeoParquet stores geometry objects as WKB binary values, which happens to be the old serialization format of GeometryUDT thus no special treatment was needed. This PR changed the serialization format of GeometryUDT, so geometry values in GeoParquet files need to be explicitly parsed and serialized.
GeometryUDT in Python
We've implemented the new serialization format in pure python, it is 2~3x slower than shapely.wkb.loads/dumps, which would impact the performance of collect, toPandas and Python UDFs in pyspark. We'll explore ways to implement it as a CPython extension to achieve good performance.
Python version of the geometry serde does not support M dimension and SRID due to the restrictions of shapely. We'll support M dimension once https://github.com/shapely/shapely/issues/1648 was resolved.
How was this patch tested?
Unit tests were added to test this patch. This patch was also manually tested on a Spark standalone cluster.
The geometry serde code for Python was manually tested with shapely 2.0. We need to update the python unit tests to be compatible with shapely 2.0 in the future.
Did this PR include necessary documentation updates?

No, this PR does not affect any public API so no need to change the docs.

Example project build failed since the snapshot artifact for Sedona 1.3.1-incubating was gone. Do we need to switch the dependency to a released version?

@Kontinuation I just switched all versions to 1.3.1-incubating. If you pull the latest change, you should be fine.
A quick question: does this solve SEDONA-222?

@Kontinuation I just switched all versions to 1.3.1-incubating. If you pull the latest change, you should be fine.
A quick question: does this solve SEDONA-222?

It does not resolve SEDONA-222. I'm working on another branch to resolve issues related to GeoParquet, and this issue will be resolved in an upcoming PR.


Fix host networking

Resolves https://github.com/docker-library/docker/issues/443
I think the iptables behaviour is a bug but the DOCKER_ENSURE_BRIDGE behaviour might be considered out of scope. It's pretty handy if you're using host networking though and it shouldn't affect anyone that doesn't have it set so it would be great to include it if people think it's appropriate.

README-win32.txt

See https://github.com/docker-library/docker/pull/437#issuecomment-1845920765

Closing in favor of https://github.com/docker-library/docker/pull/437 (DOCKER_ENSURE_BRIDGE is definitely out of scope, sorry!)


cuda_config.h is required to build non-CUDA release

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): NixOS 18.03.git.869485a (Impala)
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 1.4
Python version: 3.5
Bazel version (if compiling from source): 0.7.0
GCC/Compiler version (if compiling from source): 6.4.0
CUDA/cuDNN version: -
GPU model and memory: -
Exact command to reproduce: bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package

Describe the problem
TensorFlow with CUDA support disabled doesn't build. CUDA support is disabled in ./configure.
Source code / logs
./tensorflow/stream_executor/dso_loader.h:32:30: fatal error: cuda/cuda_config.h: No such file or directory
 #include "cuda/cuda_config.h"

It seems that disabling MPI support allows TensorFlow to be built.

Thanks for your feedback.
What options you picked when running ./configure?

      export TF_NEED_GCP=1
      export TF_NEED_HDFS=1
      export TF_ENABLE_XLA=1
      export TF_NEED_MPI=1
      export TF_NEED_CUDA=0

Others by default.

@tfboyd @gunan

It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Nagging Awaiting TensorFlower: It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.


fix: terser-webpack-plugin hanging on WSL

Motivation
Fix #6723
When running react-scripts build on Windows Subsystem for Linux, the webpack build will hang during the uglifying step. This is caused due to a bug on terser not being able to run in parallel on WSL
(https://github.com/webpack-contrib/terser-webpack-plugin/issues/21)
This PR attempts to disable parallel run on WSL until that bug is fixed upstream

Please resolve merge conflicts.

@iansu seems that a kind hearted @bugzpodder has done that. Thank you 👍

Thanks!


Support for un-grouped layers

At the time of writing, all selectable visualisation layers must be contained within a group. This means it is not currently possible to present a visualisation with a list of layers without some overarching "All Data" group.
Implementing layers without a group will be difficult, perhaps an easier option is to allow developers to skip adding the group node to the Layers tree, effectively presenting the layers as a flat list.

Confirmed as a reasonable request, but is presently a low priority.


Network error during merge PR

Description
I got a popup with alert "Network error" after clicking "Create squash commit" in my Gitea.
There are no logs presents in the Gitea server docker container for that request.
Gitea Version
1.21.6
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No server logs
Screenshots

Git Version
2.40.1
Operating System
Alpine Linux 3.18
How are you running Gitea?
Dockerized Alpine Linux 3.18 on Ubuntu 18.04.6 LTS host EC2 instance.
Database
MySQL/MariaDB

It's weird that it'd show you the padding at the end (padding added for msie message etc), as that comes from the reverse proxy.

It's weird that it'd show you the padding at the end (padding added for msie message etc), as that comes from the reverse proxy.

It could also be wrong error message due to JS errors.

Request to merge PR was blocked by WAF rule. Issue solved.
Thank you all.


Update release script to create Homebrew bottles

Describe your problem(s)
We need to create Homebrew bottles so we can attach them to releases on GitHub to support
Homebrew installs by mac users.
https://github.com/wso2/choreo-cli/issues/36
Describe your solution
Update release script to create Homebrew bottles
Checklist
~- [ ] Unit tests~
~- [ ] Documentation~
~- [ ] Updated release note~

Why don't we copy the license file for other binaries as well?
I think when generating Mac Package binaries we should extract the Mac archive and generate it from that. Otherwise what we generate for Mac archive and package binaries can change with modifications to the file.

Why don't we copy the license file for other binaries as well?

we do copy.

I think when generating Mac Package binaries we should extract the Mac archive and generate it from that. Otherwise what we generate for Mac archive and package binaries can change with modifications to the file.

fixed


Merge master

Merging master as a rebase would be painful

@ivanfoong its a little mess... maybe squashing the commits beforehand might be better ?

@jrichardlai I'll try to squash the commits and create a new PR on https://github.com/lelandrichardson/react-native-maps this weekend

@jrichardlai I don't have experience with squashing commits, is the above what you meant by squashing the commits?

@ivanfoong squashed the commits and made a new branch https://github.com/lelandrichardson/react-native-maps/pull/294, but rather have you as the commiter as this is your work can you double check the code and make another PR? Thanks!

Here is the patch, can't figure out how to put it on github load-cache-map.patch.zip

Please make another branch from leland master.
Extract it in the root folder.
Run git apply load-cache-map.patch to apply the patch.

This should do it

Thanks! Will do it today
On Tuesday, 14 June 2016, Jean-Richard Lai<EMAIL_ADDRESS>wrote:

Here is the patch, can't figure out how to put it on github
load-cache-map.patch.zip
https://github.com/ivanfoong/react-native-maps/files/312972/load-cache-map.patch.zip

Please make another branch from leland master.
Extract it in the root folder.
Run git apply load-cache-map.patch to apply the patch.

This should do it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ivanfoong/react-native-maps/pull/5#issuecomment-225755242,
or mute the thread
https://github.com/notifications/unsubscribe/AAwtRnp41EModGAS5TsZwQlH2RAU7Fgyks5qLgI6gaJpZM4If4L6
.

--
Regards,
Ivan<EMAIL_ADDRESS>


Add locale support

Implementing locale support in Amiga style

Indeed, this would be a good thing to have. I need to figure out how Vim does these things.

FlexCat may help https://yam.ch/discussion/topic/116?discussion_action=set-display;display=flat-asc

My lang.rexx
/* Set Unix language environment */
address command
"rxset LANG `search from MOSSYS:Data/ISO/639 $Language`"
parse value getclip(LANG) with . country .
ask '"Save LANG='country'?"'
if rc=0 then SAVE=""
"setenv LANG" SAVE country

Nice, it looks like Vim uses gettext for localization. I don't know gettext and I need to do some investigations to see whether it's feasible to create a shim or if the (Vim) native solution is preferable. One obvious pro of using Vims solution would be that we get many many translations for free, and that those are updated by upstream.


[Feature] cron.update_mirrors - LIMIT_SIZE config parameter

Description

The update_mirrors cron is updating all mirros (where updated_unix is ...) in one row. In my case I'm running the one once per day. That the cron needs ~2,5h to update all >6000 mirrors. And if Gitea is updating too much repos in one row GitHub is blocking Gite for some minutes. In this case Gitea gets 503 HTTP-ERROR
2021/09/07 04:09:27 ...irror/mirror_pull.go:176:runSync() [E] Failed to update mirror repository &{394 67 OpenAPITools <nil> openapi-generator-cli openapi-generator-cli   2 https://github.com/OpenAPITools/openapi-generator-cli.git master 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 false false false true <nil> [] 0 map[] map[] [] <nil> false 0 <nil> false 0 <nil> 54835310 <nil> <nil> false false [openapi openapi3 npm openapi-generator openapi2] default<PHONE_NUMBER><PHONE_NUMBER>}:
        Stdout: Fetching origin

        Stderr: fatal: unable to access 'https://github.com/OpenAPITools/openapi-generator-cli.git/': The requested URL returned error: 503
        error: Could not fetch origin

        Err: exit status 1
        /source/services/mirror/mirror_pull.go:176 (0x2006e8a)
        /source/services/mirror/mirror_pull.go:276 (0x2008e9e)
        /source/services/mirror/mirror.go:79 (0x2004545)
        /source/modules/graceful/manager.go:139 (0xc5c565)
        /usr/local/go/src/runtime/asm_amd64.s:1371 (0x47aa40)

In this case I would preffer some config parameter where I can set the size of the current update_mirror cron.
; Update mirrors
[cron.update_mirrors]
; SCHEDULE = @every 24h
SCHEDULE = 0 0 * * * *
**LIMIT_SIZE = 50**

In this case the update_mirrors cron will run every hour und call the update for the 50 oldest (select * from repository where is_mirror = true order by updated_unix asc limit 50) mirrors. And if LIMIT_SIZE is not set, then it will gets all mirrors in the right order.
Or is this now possible?
There is an MIRROR_QUEUE_LENGTH config parameter. But I didn't find the usage in code.

Worker number and queue number should help to control that but it's not direct.

In 1.16 the mirror queue will be a proper queue and we would recommend that you use TYPE=level or TYPE=redis queue if you have a lot of mirrors.

In 1.16 the mirror queue will be a proper queue and we would recommend that you use TYPE=level or TYPE=redis queue if you have a lot of mirrors.

Sounds good. Is there an config example? I can't find nothing in
https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini

If you're happy to run redis for all your queues it would be as simple as:
[queue]
TYPE=redis
CONN_STR=; as per docs

To specifically make the mirror queue and the pull request task queues level queues then it's:
[queue.pr_patch_checker]
TYPE=level

[queue.mirror]
TYPE=mirror

That should do it.

@zeripath currently I'm running my Gitea on an Mini-Server with 8GB RAM with PostgreSQL and Memcached, Nexus, ... . And if I will optimize my mirror process than I need Redis. In this case I can replace Memcached with Redis. Could be possible.
Perhaps it will be better to reduce the amount of different tools which can be used with Gitea. ;) Cause not every tool can be used for some operations. And the development process will be easier.
But if I set
[queue]
...
LENGTH = 2000
and my mirror cron runs every 24 hours than only 2000 oldest mirrors will be updated. Right? This means, that if I have 6000 mirrors after 3 days all mirrors will be up2date. Right?

@somera if you don't want to use redis just use the level queue which is built into gitea itself.
The problem with using a persistable-channel queue for the mirror queue is if you have 2001 mirrors and 2000 are queued, the 2001st request to push to the mirror queue will block.
It is this blocking that is likely the cause your repeated issues of opened or stuck processes. Not every call to queue.Push() is async'd with go queue.Push(...).

ok. But what is with this question? Cause I try to understand this new functionality. It this what I "wanted" in my initial post?
If I set
[queue]
...
LENGTH = 2000
and my mirror cron runs every 24 hours than only 2000 oldest mirrors will be updated. Right? This means, that if I have 6000 mirrors after 3 days all mirrors will be up2date. Right?

Ah I think I now understand what you mean - you'd prefer to limit the number of mirrors added to the queue by cron.update_mirrors.
OK let me take a look at that now.

@zeripath right. I don't want update all the 6000 mirrors in one row. but split theam. On every update mirror cron only update xxxx oldest updated mirrors.

@zeripath thx. If I set than (perhaps in 1.16.0)
PULL_LIMIT=1000
than on update_mirrors cron only 1000 oldest mirrors will be updated?

Each time the update_mirrors task is run only the oldest PULL_LIMIT pull mirrors and oldest PUSH_LIMIT push mirrors will be added to the queue.
If the mirror is already in the queue it will not count towards the limit.
So if the task limit is 3 say and you have repos A-N waiting to be updated and in increasing staleness, if A-E are already in the queue F, G and H will be added.

@zeripath after upgrade to 1.16.0 the update mirror process isn't working like in 1.15.x anymore. See #18607
And I don't understand the new process.
I did ~9000 curl api calls to Gitea:
curl -X 'POST' 'http://nuc-mini-celeron:3000/api/v1/repos/gaphor/in-app-notification-demo/mirror-sync' -H 'accept: application/json' -H 'Authorization: token xxxxx' -d ''
If I repead the curl calls I see this
2022/02/05 01:04:08 ...ces/mirror/mirror.go:161:func1() [E] Unable to push sync request for to the queue for push mirror repo[6616]: Error: already in queue
        /source/services/mirror/mirror.go:161 (0x1cd87c9)
        /usr/local/go/src/runtime/asm_amd64.s:1581 (0x471520)

in the logs.
And I set this:
[cron.update_mirrors]
SCHEDULE = 0 0 4 * * 5
PULL_LIMIT = -1
PUSH_LIMIT = -1

But Gitea is not updating all the repos.
Thy? When will Gitea update all the repos where the mirror.updated_unix date is older than one day?


[Bug] - Error messages on macos contain absolute paths

The tests in regression-new/kprove-java fail incorrectly on macos because a source location is being printed as an absolute path, but the expected output is not.
The diff output is:
[Error] Compiler: Found variable _ on right hand side of rule, not bound on left hand side. Did you mean "?_"?
	Source(/Users/brucecollie/code/k/k-distribution/tests/regression-new/kprove-java/rhs-vars-broken-spec.k)
	Location(12,20,12,21)
[Error] Compiler: Found variable A on right hand side of rule, not bound on left hand side. Did you mean "?A"?
	Source(/Users/brucecollie/code/k/k-distribution/tests/regression-new/kprove-java/rhs-vars-broken-spec.k)
	Location(14,20,14,21)
[Warning] Compiler: Variable 'A' defined but not used. Prefix variable name with underscore if this is intentional.
	Source(/Users/brucecollie/code/k/k-distribution/tests/regression-new/kprove-java/rhs-vars-broken-spec.k)
	Location(14,20,14,21)
[Error] Compiler: Had 2 structural errors.
0a1,10
> [Error] Compiler: Found variable _ on right hand side of rule, not bound on left hand side. Did you mean "?_"?
> 	Source(rhs-vars-broken-spec.k)
> 	Location(12,20,12,21)
> [Error] Compiler: Found variable A on right hand side of rule, not bound on left hand side. Did you mean "?A"?
> 	Source(rhs-vars-broken-spec.k)
> 	Location(14,20,14,21)
> [Warning] Compiler: Variable 'A' defined but not used. Prefix variable name with underscore if this is intentional.
> 	Source(rhs-vars-broken-spec.k)
> 	Location(14,20,14,21)
> [Error] Compiler: Had 2 structural errors.

On first inspection, this happens because the output from kprove isn't being redirected to stdout, so the REMOVE_PATHS invocation of sed never actually sees the correct output.
If I add CONSIDER_PROVER_ERRORS=2>&1 to the Makefile in this directory, the test passes as expected.


Enable support per-event dragability/sizability

Ok sorry, misunderstood what you asked for.
What about this update? :)

@dbuchet-bandc Nice work! What do you think @jquense?

Looking good!


where is the compiler

Hi Team,
I am looking for the typescript compiler. I had a look at the typescript playground, which is using getEmitOutput, but I cannot find how to use it myself. Could you please guide me on how to proceed ?
Thanks,
Nicolas

@jrieken Should we add getEmitOutput to monaco-typescript ?

We should expose the whole language service API or the promise'isified version of it so folks are free to do. Only things like the program or ASTs that cannot be JSONified we shouldn't expose

Do you have any timeline for this ?

Would be much appreciated

We don't really have a timeline for this but the good news is that we are accepting PRs :-).
Getting to the emitOutput is mostly about exposing this function and exposing more language service features in the worker - tho arguments and return types must JSON'able.
'Exposing' things happens in the createApi such that others can do something like this: monaco.languages.typescript.withWorker(uri1, uri2).getEmitOutput(fileName).then(result ...)

I'm on it :)

we have it


Pages to App Router Migration

The documentation should be migrated from the pages router to the app router to take advantage of current and future NextJS features.
https://nextjs.org/docs/pages/building-your-application/upgrading/app-router-migration

i'm all for it, as long as we stay backwards compatible with the current URL structure

i'm all for it, as long as we stay backwards compatible with the current URL structure

Understood. I think the plus side is NextJS does offer an incremental migration, so Ill fool around with it this week and see what that would look like.

I'm totally with you 😀
Life happens...


Need a way to add ref to

I need to add a ref to:
<div className="marquee-container ref={ref}>
</div>

Is there anyway I can do so? I tried adding it to the  tag but it doesn't appear to work.  This is needed for nextjs image's lazy load: lazyboundary. or the images are loading too slow.
<Marquee ref={ref}>
</Marquee>

Added support for this in 1.5.0


Better handling for child process logging

fixes https://github.com/ethereum/trinity/issues/1381
What was wrong?
The child processes hook into the main process over an IPC socket to pass logs through.
First, we weren't closing this IPC socket which resulted in lots of errors due to unclosed sockets.
Second, once the socket is closed, the handler was still left on the logger which meant that other things that might use logging, like things in the standard library, which do things during the python shutdown, would cause the handler to throw errors since it wouldn't be able to communicate with the parent process.
How was it fixed?
Used two context managers, one to close the socket, and another to remove the handler.
Cute Animal Picture

Hah, looks like you just got hit by #1362 (#1382 is approved to fix it)


(Preview) kafka stream implementation, import Kafka libs

Added unbounded semaphore for credit signalling. There is a dropbox unbounded semaphore lib, but it takes and releases resources one at a time, which isn't what we want. This implementation is generic enough to handle size-based credits in the future.
Otherwise, this just doles out messages from the channel and counts credits

Coverage decreased (-0.3%) to 68.99% when pulling 202b23ae76bd023601eb5bebf0b31642c835b46d on kafkaStream into 7bc2f8ef99ecd3199b45f548171cec9df374ad35 on master.

Coverage decreased (-0.4%) to 68.889% when pulling 8db0bd4b7b3aa696be36224cc9033ad52ad107a4 on kafkaStream into 7bc2f8ef99ecd3199b45f548171cec9df374ad35 on master.

Coverage decreased (-0.3%) to 68.904% when pulling 8db0bd4b7b3aa696be36224cc9033ad52ad107a4 on kafkaStream into 7bc2f8ef99ecd3199b45f548171cec9df374ad35 on master.

Coverage increased (+0.05%) to 68.662% when pulling 59b72f5f1cfeb5b67e261253bba8a14b98bd8433 on kafkaStream into c449efda528c93b2adbbd5a7f1d9f6d8af51a730 on master.

Is there anything we are waiting on for this? @aravindvs

@GuillaumeBailey lgtm!

Coverage decreased (-0.03%) to 68.906% when pulling 2e695346dfc6b2559096f78a0255a213a829d0c5 on kafkaStream into bc5a9e470b54942b87fd20266f02257c6395c231 on master.


KernelSHAP breaks for specific values of nsamples

It appears there is something fishy in the way subsets are selected in kernelSHAP that causes issues with certain values of nsamples (and IndexError fires). I have attached a demonstration of this phenomenon below:
https://gist.github.com/lukemerrick/2dea4c9320c2231385099ad604fa490f

Thanks!


Unsupported state class

After upgrade HomeAssistant to version 2023.8.2 it shows 2 errors (for sensor.w1000_import and sensor.w1000_export):

Unsupported state class
The state class of this entity, is not supported.
Statistics cannot be generated until this entity has a supported state class.
If this state class was provided by an integration, this is a bug. Please report an issue.
If you have set this state class yourself, please correct it. The different state classes and when to use which can be found in the developer documentation. If the state class has permanently changed, you may want to remove the long term statistics of it from your database.
Do you want to permanently remove the long term statistics of sensor.w1000_import from your database?

Is this really a bug? What could I do to fix this issue?
By,
paya

I'm afraid it is indeed the fault of the integration. I'll check it out with this version soon.

I've opened HomeAssistant to check any change of issue, and the errors are disappeared... I don't know how...

Closing this as not reproducible.


feat: add dcm presets

Changes

add dcm presets
fix

Docs:

Checklist for self-check

[x] Commits and PRs have been filed according to the rules on the project.
[x] The author is marked as an assigne and assigned mandatory reviewers.
[x] Required labels marked
[x] Specified related tasks and/or related PRs.
[x] Specified Changes.
[x] Attached videos/screenshots demonstrating the fix/feature.
[x] All unspecified fields in the PR description deleted.
[x] New code covered by tests.

Checklist for reviewers

[ ] CI passed successfully (with a green check mark).
[ ] PR is atomic, by volume no more than 400 (+-) corrected lines (not including codogen).

Design:

[ ] System design corresponds to the agreements on structure and architecture on the project.
[ ] The code is decomposed into necessary and sufficient components.

Functionality:

[ ] The code solves the problem.
[ ] Any changes to the user interface are reasonable and look good.

Complexity:

[ ] The code is clear, easy to read, functions are small, no more than 50 lines.
[ ] The logic is not overcomplicated, there is no overengineering (no code sections that may be needed in the future, but no one knows about it).

Tests:

[ ] Updated or added tests for mandatory components.
[ ] The tests are correct, helpful, and well designed/developed.

Naming:

[ ] The naming of variables, methods, classes and other components is understandable.

Comments:

[ ] The comments are understandable and helpful.

Documentation:

[ ] All labels are correct
[ ] Technical documentation updated (after approval, updates last reviewer).

Codecov Report
Attention: Patch coverage is 37.74834% with 94 lines in your changes are missing coverage. Please review.

:exclamation: No coverage uploaded for pull request base (main@e88a8f6). Click here to learn what that means.

Files
Patch %
Lines

...tures/debug/presentation/ui_kit/ui_kit_screen.dart
0.00%
30 Missing :warning:

.../features/debug/presentation/ui_kit/ui_kit_wm.dart
0.00%
9 Missing :warning:

...ib/features/debug/presentation/debug/debug_wm.dart
0.00%
8 Missing :warning:

...ence/storage/theme_storage/theme_mode_storage.dart
0.00%
7 Missing :warning:

lib/uikit/text/app_text_scheme.dart
12.50%
7 Missing :warning:

...re_example/presentation/feature_example_model.dart
0.00%
4 Missing :warning:

.../data/repositories/feature_example_repository.dart
0.00%
3 Missing :warning:

...ature_example/presentation/feature_example_wm.dart
0.00%
3 Missing :warning:

...ures/theme_mode/presentation/theme_mode_model.dart
0.00%
3 Missing :warning:

lib/uikit/colors/app_color_scheme.dart
40.00%
3 Missing :warning:

... and 13 more

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #92   +/-   ##
=======================================
  Coverage        ?   26.48%
=======================================
  Files           ?       57
  Lines           ?      925
  Branches        ?        0
=======================================
  Hits            ?      245
  Misses          ?      680
  Partials        ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Ambiguuty between name and short ID

Steps to reproduce:
1 - Create a container of any kind - say Ubuntu
2 - Create a container of another kind - say Redis and give it a name which is a prefix (say 5 chars long) of the former container ID (the one which was created at step 1) Let us mark this prefix and name with XXXXX
3 - docker inspect XXXXX
You will get the container from stage 2.
Looking at the code Get tries as follows:
1 - match exact name
2 - match full Id
3 - match partial ID
now since before the creation of the second container the command in 3 return the Ubuntu container and after it the Redis container return this seems to me like an ambiguity (and if you delete the redis you get the ubuntu again after the inspect command)

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Version:
Client version: 1.6.0
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 4749651
OS/Arch (client): linux/amd64
Server version: 1.6.0
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 4749651
OS/Arch (server): linux/amd64
Info:
Containers: 70
Images: 118
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 280
Dirperm1 Supported: true
Execution Driver: native-0.2
Kernel Version: 3.16.0-38-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 4
Total Memory: 7.829 GiB
Name: vizio-devswarm-host2
ID: JZQE:UR3Q:IVBX:JIH2:MZTT:LETM:GPIK:6ITF:OYXL:F2Z3:KHR6:JCZA
Username: haih
Registry: [https://index.docker.io/v1/]
WARNING: No swap limit support
uname:
Linux ubuntu 3.13.0-51-generic

Thanks for reporting, @doronp. The actual behavior (in 1.8) is:

If the ID is a full match (i.e., when using the full ID), use that
If the Name is a full match, use that
If there's no full match, match on partial ID

So, in all cases, a full ID will make sure that you're addressing the right container or image, and is the recommended approach here.
I just tested this and it seems to work as described above, but feel free if you're still able to reproduce this on 1.8 or 1.9
Thanks for reporting, I'm going to close this issue, but feel free to comment after I've closed

Hi,
I just retested with 1.9 and It still behaves that same
(create 1 container take prefix of its ID and name another container with it, then the existence of the second container effect the response you get for inspect on that prefix (which is the name of the second container)) See above for full scenario.
BTW I fully agree that using full ID is best - but what I see is that when people can use prefix they do and this corner may prove problematic.
Thanks,
Doron P

@doronp see my previous comment https://github.com/docker/docker/issues/17247#issuecomment-150036904. this is the expected behavior; doing a partial ID match first would, for example, not enable you to use a container named db (many people do that) if a container ID exists that starts with db......
If you need to access a specific container or image, use the full ID


feat: bright colors variants

Bright colors variants as mentioned in #47 😄
Also added few empty lines separating colors group for easier navigating through the code

Is it possible to add orange color?

@MrFoxPro absolutely I can contribute to that :) but this PR focus only on adding corresponding/existing colors in bright variants. if that will/would be accepted then I can proceed in adding something more 👍🏻

Thanks for your work @MHase
Any chance of seeing this merged?
I feel it would really help people who are migrating from chalk -> picocolors
Or are there any issues with the PR, or the impact it would have on the overall size?

@WaldoJeffers I would love to see this merged, but we need someone to approve/merge this PR for us
Only those with write access to this repository can merge pull requests.
Any idea who we can ping to move this forward?

@alexeyraspopov

Still not approved? What is it about? I also need "bright" colors.
@marco-carvalho @borodean @alexeyraspopov ?

based on responses it looks like this repo was abandoned...

15 million projects use this module, maybe someone will take it further...

The library is mostly used indirectly, by other more significant projects. I appreciate the PRs and will get back to them as soon as I got time, but I can’t just prioritize PRs that start bloating the size for little to no benefit.
Thanks

@alexeyraspopov Thanks for showing up!
This PR increases the size by just a few hundred bytes, in return doubles the number of available colors. And most importantly, it fulfills the promise of easy migration from Chalk, where *Bright colors are present.

@alexeyraspopov any chance we can get these bright colours over the line?
As part of the ecosystem cleanup effort I'm leading, we're replacing chalk & others with picocolours in many popular repos. The only missing thing that all other alternatives have seems to be these variants
If you need any help maintaining this too, let me know. I would be happy to help, especially given I'm making quite a few large packages depend on it

@MHase can you possibly catch this up from main? The fallback logic was refactored since, so there's probably some conflicts

Hallo @MHase / @alexeyraspopov  !
but this PR was not published on npm? correct?

@WuglyakBolgoink unfortunately correct
the latest release was on 14 May with version 1.0.1

@alexeyraspopov When is this expected to be published?
Is it going to be in 1.1.0 or 1.0.2?

I will publish 1.1.0 once https://github.com/alexeyraspopov/picocolors/pull/71 is resolved

@alexeyraspopov Can you publish 1.0.2 with this fix in the meantime to unblock migrations from chalk?

I just posted a PR to migrate from chalk to picocolors in changesets https://github.com/changesets/changesets/pull/1417
The maintainers have not reviewed it at the time of comment, but there's a possibility they might block it because of the absence of redBright API.
I also posted migrations requests on popular repos, where maintainers seem to be onboard at the time of comment:

jest https://github.com/jestjs/jest/issues/15189
eslint https://github.com/eslint/eslint/issues/18686

I will publish 1.1.0 once #71 is resolved

we need this( please publish it in 1.0.2


Better interaction with pagers (Broken pipe)

Since the result of verification can be hundreds of lines or more, I use the command with a pager, exit in the middle, and then a "Broken pipe (os error 32)" error occurs. It is not a critical problem but it would be great if we can get rid of the error.
I am using cargo-crev 0.15.1, installed with cargo on Ubuntu 18.04 (amd64) on WSL.

backtrace
$ RUST_BACKTRACE=1 cargo crev crate verify | less
Error: Broken pipe (os error 32)
stack backtrace:
   0: failure::backtrace::internal::InternalBacktrace::new
   1: failure::backtrace::Backtrace::new
   2: cargo_crev::deps::print_term::print_dep
   3:  as core::iter::traits::iterator::Iterator>::next
   4:  as alloc::vec::SpecExtend>::from_iter
   5: cargo_crev::deps::verify_deps
   6: cargo_crev::run_command
   7: cargo_crev::main
   8: std::rt::lang_start::{{closure}}
   9: std::rt::lang_start_internal::{{closure}}
             at src/libstd/rt.rs:48
      std::panicking::try::do_call
             at src/libstd/panicking.rs:287
  10: __rust_maybe_catch_panic
             at src/libpanic_unwind/lib.rs:78
  11: std::panicking::try
             at src/libstd/panicking.rs:265
      std::panic::catch_unwind
             at src/libstd/panic.rs:396
      std::rt::lang_start_internal
             at src/libstd/rt.rs:47
  12: main
  13: __libc_start_main
  14: _start

Ignore would IMHO be suitable behavior if there were any valuable processing done. It may or may not be suitable for a cargo crev repo fetch all, but a cargo crev crate verify should just use the default UNIX behavior and terminate.


Upload from URL

Is it possible to upload from URL like this?
ios-uploader -u<EMAIL_ADDRESS>-p aaaa-bbbb-cccc-dddd -f "https://exp-shell-app-assets.s3.us-west-1.amazonaws.com/ios/test-archive.ipa"

Only files on the local filesystem are supported atm. But will consider implementing it as a new feature as I can see the uses for it.


Add TypeScript support, add package-lock file

Hello!
Liked this minimalist project to format some currencies, I like to work in TypeScript and this project is missing types, this PR fixes #6 and also adds a package-lock.json file for faster installs and better dependency versioning for npm versions >=5
hope you can merge and release this!

@RyanZim are you going to approve this??

Bump

If @RyanZim doesn't sort this out soon, I'll release this on npm myself with the PR applied.

I'm okay with us supporting this. Please remove package-lock.json, package.json modifications, and remove CHANGELOG.md modifications.


Stricter TS config

Summary
The current TS config does not raise any error when a function is declared as returning a specific type but still returns null or undefined.
This may lead to misunderstanding of the functions when relying on the signature.
Expected Behavior
Considering the following code
function doThings(): boolean {
  if (someSpecificCondition) { return null }

  // some more code here
  return true
}

Get a linter error when running make as
Current Behavior
The previous example may compile without any warning.

Lat’s give this priority - ilhaving stricter type checking might reduce bugs.

Reevant article: https://www.figma.com/blog/inside-figma-a-case-study-on-strict-null-checks/

@davidjgoss should this be closed and relevant issue(s), raised on the constituent repos if needed?


Multi-screen display issue

Display issue when disconnecting second screen

Expected Behavior

Current Behavior

When using Franz plugin on a second screen and then disconnecting second screen, we are unable to see the Franz frame. This one actually sticks to the disconnected screen.
Screenshots (if appropriate):
Possible Solution

Steps to Reproduce (for bugs)

Connect a second screen and drag the Franz frame on it
Reduce Franz
Disconnect the second screen
Open Franz again

Context

Can't use Franz when my laptop isn't connected to a second screen
Your Environment

Franz Version used: Franz v.5.0.0-beta.17
Operating System and version: Windows 10

I run into this issue daily. The only fix I've found is to:

Click the franz app to make sure it's opened (even though you can't see it)
Press Alt + spacebar
Click Maximize

Hope this can be fixed soon.


[SPARK-48967][SQL] Improve performance and memory footprint of "INSERT INTO ... VALUES" Statements

What changes were proposed in this pull request?

In this PR we improve the memory pressure on the driver and runtime performance when executing very large INSERT INTO ... VALUES by eagerly evaluating the parse subtree that is generated for such statements into a LocalTable. Instead of waiting until the analyzer stage to do so.
Why are the changes needed?
Currently very large "INSERT INTO ... VALUES" statements result into disproportionally large parse trees as each parsed literal will need to remain in the parse tree, until it eventually gets evaluated into a LocalTable, which takes place when analyzer/optimizer rules are applied.
This results in increased memory pressure on the driver, when multiple such large statements are executed in parallel, that can lead to OOMs and GC pauses. It also results in suboptimal runtime performance as the time it takes to apply analyzer/optimizer rules is typically proportional to the size of the parse tree.
Both these issues can be resolved by applying the functions that evaluate the unresolved table into a local table eagerly from the AST Builder, thus short-circuiting the evaluation of such statements.
Runtime & Memory Benchmarks
For this benchmark we generated a table (we are attaching the create statement later in this section), and we captured both the execution time and the memory footprint of the driver when executing an INSERT INTO ... VALUES statement of increasing size, both with and without this PR.
Runtime Comparison
The table below shows the runtime difference between various sizes of insert statements:
Number of tuples      AVG time WITH this change (seconds)   AVG time WITHOUT this change (seconds)      speedup
500k                           40.27                            48.26                                   20%
1M                             79.80                            95.88                                   20%
1.5m                           122.11                           145.42                                  19%
3m                             232.37                           283.71                                  22%

Note that this was ran on fairly high spec machine, so these numbers should be much more substantial on more average-spec'd machines.
Memory Comparison
The memory footprint was captured by generating a heap dump right after the generation of the parse tree. In the heap dumps below we notice that the footprint of the InsertIntoStatement for:

1M tuples was reduced from roughly ~4.6 GB to roughly 888MB (~81% improvement).
3M tuples was reduced from roughly ~19.4 GB to roughly ~3.14 GB (~83% improvement).

The attached heap dumps also illustrate that the child node of the InsertIntoStatement has successfully been replaced by a LocalTable.
Heap dumps while inserting 1M tuples
Before this fix:

After this fix:

Heap dumps while inserting 3M tuples
Before this fix:

After this fix:

Create Table Statement
CREATE TABLE extensive_data_table (
    id INT,
    first_name VARCHAR(50),
    last_name VARCHAR(50),
    age INT,
    gender CHAR(1),
    email VARCHAR(100),
    phone_number VARCHAR(20),
    address VARCHAR(200),
    city VARCHAR(50),
    state VARCHAR(50),
    zip_code VARCHAR(10),
    country VARCHAR(50),
    registration_date DATE
);

Machine info
Benchmarks were run into a machine with the following specs:
costas.zarifis@ip-10-110-52-199:~$ lscpu
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Byte Order:                         Little Endian
Address sizes:                      46 bits physical, 48 bits virtual
CPU(s):                             32
On-line CPU(s) list:                0-31
Thread(s) per core:                 2
Core(s) per socket:                 16
Socket(s):                          1
NUMA node(s):                       1
Vendor ID:                          GenuineIntel
CPU family:                         6
Model:                              106
Model name:                         Intel(R) Xeon(R) Platinum 8375C CPU @ 2.90GHz
Stepping:                           6
CPU MHz:                            3509.092
BogoMIPS:                           5799.88
Hypervisor vendor:                  KVM
Virtualization type:                full
L1d cache:                          768 KiB
L1i cache:                          512 KiB
L2 cache:                           20 MiB
L3 cache:                           54 MiB

Does this PR introduce any user-facing change?
No
How was this patch tested?
Provided scala tests.
Was this patch authored or co-authored using generative AI tooling?
No

Mind filing a JIRA please? See also https://spark.apache.org/contributing.html

cc @cloud-fan

thanks, merging to master!


onRemoteChange deprecated? (onLocalChange proposal)

Since this commit (https://github.com/PuppetJs/PuppetJs/commit/126455697921be73b31809fc959246bf3132d50e), onRemoteChange is marked in README.md as "Deprecated".
Did we discuss it?
I would like to add a new callback onLocalChange, which is useful for puppet-polymer-client. But then I need to "undeprecate" onRemoteChange.
onPatchSent is almost suitable for me, but I dislike the fact that data is a string there.

cc @miyconst, @tomalec
The question is - do you agree to add onLocalChange and undeprecate onRemoteChange?
Alternatively, I would like to change the argument of onPatchSent and onPatchReceived to be the actual array (sequence of patches). Right now it is string.

The question is - do you agree to add onLocalChange and undeprecate onRemoteChange?

If we need onLocalChange then it is very likely someone would also need onRemoteChange. So, I would either keep both or remove both.

Alternatively, I would like to change the argument of onPatchSent and onPatchReceived to be the actual array (sequence of patches). Right now it is string.

I also thought so, and at some point was going to change it. Those events rise even if the patch received from the server is not a valid json, and this helps debugging. What if we extend the argument, not replace it?

Please note, the fact that patch was received does not mean it was applied, due to JSON-Patch-Queue.
I also like the idea to exposing data in already parsed format, but to avoid performance overhead of JSON parsing just for debugging/external use, I would prefer to parse it once for the queue and call back then.
Regarding renaming, I would like to rename callback argument to something more descriptive, like onDataReady

Please note, the fact that patch was received does not mean it was applied, due to JSON-Patch-Queue.

Because of that, I think that I actually need onLocalChange and onRemoteChange - because my external JavaScript (in this case puppet-polymer-client) works on the local object.

Let's add onLocalChange and de-deprecate onRemoteChange then?

I think we are all agreed, aren't we?

Yeah, thanks! Done


Create Icon

Hey, we have the AppIcon.kt but how can we use it to do the app's icon ?

sry to answer you so late，you can preview it in Split mode and right-click to save the image as icon


Steam Audio behaves very differently in a Unity build as opposed to the Editor when using "one shot" sounds.

System Information

Steam Audio version: 4.5.0
Unity version: Unity 2022 and Unity 6 (have tried in both)
(If applicable) FMOD Studio version: Using Unity audio
Operating System and version: Windows 10 64 bit

Issue Description
I have created a fairly simple "roll your own" pooled audio source system for creating one-shot audio I need to "summon" instantly to a particular position. Physics impacts, footsteps, etc. The prefab is a gameobject with an audio source, a steam audio source, and nothing else. I pool them all at startup (about 10 of them) and call them as one-shots by first moving their position, then setting their clip, then playing them.
This works PERFECTLY in the editor. However, when I make a build, I rarely ever hear my audio playing in this manner. Sometimes I can FAINTLY hear it, or like a subtle echo of a footstep for example. But largely I hear nothing. Very strange.
I DO hear Steam Audio sources that are statically placed in the world already and don't move in any way (like a generator sound, or a cricket, etc.).

Are you able to share some minimal repro we can take a look at? This would be ideal.
Otherwise, can you share additional information on your prefab and your script so we can try to repro this behavior on our end.


[FEATURE] Gitpodify Project

⭐ Suggestion
Make the project ready for gitpod
💻 Use Cases
No response
❌ Related Problems
No response

Let me check the fix

I cant really explain why it fails at the build. Its exactly the same as in build.yml but in the docker-action its failing


API to load another notebook

resulting from discussion with @kyotov and @ildipo:
users often have a problem where they want to share code between notebooks in a less formal way than moving the code into a regular module.  an easy way to get this is to define a function on the beaker object that imports another notebook, and then evaluates its init cells.  ie:
beaker.loadLibrary("......").then(.......)

library notebooks can be developed to define useful functions in their init cells, and then document and demonstrate them in regular cells.
the loadLibrary function should be able to take a list.
it should only load each lib once (keep a table as it goes).
it should work on a URI that beaker can open.
before implementing this, should check how it interacts with the module systems of the underlying languages.  it it possible to define a proper python or R module from inside a beaker notebook?
maybe not necessary but should not be uninformed on this point.

In order to do so properly, you will need cell dependencies an cell references, because initialization cells are rather bad way to indicate which part of the notebook is loaded. To top it all, user can not control when initialization cells are loaded (If cell loads slowly, it is very inconvenient).
On the other hand, if you have cell dependencies, you can reference not the whole notebook, but a specific cell, and then this specific cell and its dependencies are loaded when needed.

we don't want to reference a specific cell.  perhaps someday we'll have dependencies between cells and then this API can be extended to include a cell tag in addition to a notebook URI.  as far as i can tell what you are asking for is a superset of this plan, so this is a good place to start.

as far as i can tell what you are asking for is a superset of this plan

This is not quite correct. In fact, you should make an ideological decision about weather you want to use either notebook or cell as your main structural element and adhere to this decision. The example of bad similar decision is java packages. Sun intended them to be major structural element, but in practice they are used only as name spaces and package private visibility modifiers always never used.
In my opinion, notebook is not very good structural element, because it does not have definite way to know which of its elements are calculated and which of calculated ones are up-to-date. Additionally, notebook can and usually does contain some additional cells, which does not matter for particular calculation. How to decide which cells to run? Currently you want to use initialization cells only. But what if you want to run non-initialization cell or if initialization cells have conflicting global state change?
Each cell changes global state, which is bad for dependency integrity as itself (and one do not control the order of cell execution, which is bad squared). Currently the only way to make results reproducible is to line up all cells and call them one after another. Initialization cells do not have the same order of execution as notebook, so there will be a great mess, when one will try to define what his notebook does or how to reproduce some result.

I might be missing something, but my understanding is that initialization cells are evaluated in the order the appear in the notebook. So "evaluating a notebook", defined as evaluating all its initialization cells in order, will work (for me) as a Phase 1 feature.
Cells modifying global state is tricky but it is not a new phenomenon. Python packages can modify global state when they are imported... With too much expressiveness you always have to have a healthy judgement and responsibility.
I would put a disclaimer that I come from an environment where each "notebook" had effectively a single cell (they were the same thing) and so I might be a bit naive in my way of thinking notebook dependency is enough. But on the other hand, putting dependencies on the individual cells inside a notebook seems like an unnecessary complication to me (at least on the surface).

There may be "normal" cells between initialization cells. So "run all cells" in general does not give the same result as initialization run. Also if one notebook calls another one with an initial global state of its own, then two subsequent runs of external notebook could provide completely different results. Some problems could be solved with reset and rerun option, but it complicates things.
Global state is necessary evil in script languages, but uncontrollable global state change must be avoided where it is possible.
I am working on dependency-based data analysis system (with an aim to make analysis 100% reproducible), so my opinion is also biased. But I think that Beaker developers should carefully consider this point since it could define future development vector.
In fact, there is another option. If notebook is an object and could be operated as one, than external notebook could be another instance of this object with its own beaker class and global state.


Error upon starting up LethalLib

Hello, I'm new to modding Lethal Company and I'm hoping I can have some help. I see that in the BepInEx terminal, it prints me this error upon starting up the game:
[Error  : Unity Log] TypeLoadException: Could not load type of field 'LethalLib.Modules.Enemies+<>O:<0>__RegisterLevelEnemies' (0) due to: Could not load file or assembly 'MMHOOK_Assembly-CSharp, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
Stack trace:
LethalLib.Plugin.Awake () (at <4eedb4dc36094adcb65137cf81f2803d>:IL_0098)
UnityEngine.GameObject:AddComponent(Type)
BepInEx.Bootstrap.Chainloader:Start()
UnityEngine.Rendering.HighDefinition.HDRenderPipelineAsset:OnEnable()

My only mod installed is LethalLib, and this goes away when LethalLib is taken out of the plugins folder. I tried running the last three versions of LethalLib and the issue persists.
Any help would be appreciated!

I found a fix by installing https://thunderstore.io/c/lethal-company/p/Evaisa/HookGenPatcher/

dosn't work anyway


From my last PR, the header files where not being found on windows, not all of them.

This fixes them.

Good. Was this the cause of Windows 64bit crash? I don't think so, right?