Strange "Could not get unknown property 'projectConfiguration' for DefaultProjectDependency" error in multi-project in gradle 4.1

I have a project contains two modules, api and service.
The service depends on the api module.
dependencies {     compile project(':api') }
But I get below warning:
Could not get unknown property 'projectConfiguration' for DefaultProjectDependency
And the service module can not access the classes in api.
The Gradle version is 4.1. And I also test the Gradle 2.14.1. It works fine in Gradle 2.14.1.

From the provided information I can only assume you are trying to import a new Gradle project into an older version of IntelliJ IDEA. Please upgrade to the latest version.
If that doesn't fix the issue, please provide a reproducible example project and instructions how to reproduce the problem.

Thanks, oehme, you are right. I update the IDEA to latest version, and it works fine now. Thanks a lot.

I am having this problem right now! Unfortunately, my IDE does not indicate any updates currently available(I am on 2017.2.4, "Build #IU-172.4155.36, Built on September 11, 2017"), so I cannot benefit from the previously mentioned solutions (nor do I have any other known recourse)! 😞 👎

That's a completely different problem. Please open a bug report including a reproducible example.


Feature Request: Getting exif data for images - Latitude & Longitude

I'm already using react-native-image-picker in my app, but it's insufficient on the video side.
This library has a lot of advanced features for video. I can get Exif data with the help of a separate library, but it would be great if it could be added to Result on the native side

I also plan to implement it but this will take quite a while to return results[]. So my plan would will be separate function calls when necessary. For example, get data before pushing it to the server.
const response = await getExif()
...
// call to server


how to detected the actural physical dimensions ( or the approximate value) of face

eg. get the width of face in cm

just with this model, i don't think anything would make sense as you don't have anything to compare with and have no idea how far is the face from the camera or whats the field of view.
what comes to mind is to use object with known size as anchor and then do simple math to determine size of the face.
for example, human iris is quite stable and iris model (which augments facemesh model, not face-api) is not bad.
so running facemesh model augmented with iris model would give size of iris which can be used to infer distance which then can be inferred to calculate scale of the face itself.
if you want to check it out, i've done some work on that to combine different models in https://github.com/vladmandic/human, i might add this as it seems like an interesting problem to solve.

Hi @vladmandic .
Did you end up incorporating detection of distances in your repo? I found it super interesting!!

yes, its been part of https://github.com/vladmandic/human for a while

Hi @vladmandic ,  I hate to ask this, but could you please point me towards an example? I went all the wiki pages but couldn't find anything.
If you could help me learn how to get an approximate distance in millimeters from left iris to right iris, using your library, I'd be super grateful for you!
I was doing something like the below, but I then realized I'm looking at the wrong 'distance' method.
human.detect(input, userConfig)
      .then((result) => {

        const annotations = result.face?.[0]?.annotations;
        console.log({ annotations }, `DISTANCES`, {
          ipd: human.distance(
            annotations.leftEyeIris?.[0],
            annotations.rightEyeIris?.[0],
          )
        })
...

i've answered in https://github.com/vladmandic/human/discussions/310


Lazy - Lua support

Hi !
First thanks for continuing the project.
Can this be installed from Lazy? any attempts where in vain (can't use :AirLatex)
i use neovim v0.10.1
checkhealth yields no errors.

 I get around UpdateRemotePlugin for nix, by just generating the bindings: https://github.com/dmadisetti/AirLatex.vim/blob/main/export.py

hmm it seems that possible windows (yeah) is buggy somehow. It does not seem to have to do w/ the project per se


Save a sequence from STOCHASTIC channel to a NOTE channel

Hi Claudio,
I tried another solution for recording a sample from STOCHASTIC channel
Solution:
Record a sequence from a STOCHASTIC channel to a NOTE channel
Example:
8-step sequence, no particular scale or root selection
Channel 1: STOCHASTIC
I send the :

GATE1 to CV2 IN
CV1 to CV1 IN

I select "REC" to record the STOCHASTIC sequence on channel 8, by example
However :

STEPS: the 1st step is not recorded (incidentally, I've noticed that I have the same problem when I use a synchronised keyboard; the first note is never recorded)
NOTES: the last note is wrong and not part of the sequence
REPEAT : No recorded
RETRIG : No recorded
LENGHT : Yes, recorded
SLIDE : No recorded
COND : No cheked

I may be making a mistake, but is it possible to copy a STOCHASTIC sequence to a NOTE channel?
Jil

could u try recording a note track into a note track?
just to see if it works as expected.

anotehr thing did u try setting in project page cv/gate inout when recording?

Yes, the cv/gate input is selected: CV1/CV2
Here is the result of recording from NOTE to NOTE:
STEPS: the 1st step is not recorded
NOTES: OK, but not for the 1st step, which is not recorded.
If the length is 100%, the next note is not recorded.
REPEAT: For a repeat of 3, no repeat is recorded on the note, but 3 notes are created in succession.
RETRIG: Not recorded
LENGHT: Yes, recorded
SLIDE : No recording
COND: No verification

so it's pretty similar to the stochastic track recording

Yes

ok, so the main issue is that the first note will not be recorded (general issue both for nothe and stochastic).
then could you explain what u mean with " the last note is wrong and not part of the sequence"

FYI : Using a KS37 keyboard, synchronised: the first note is not recorded

" the last note is wrong and not part of the sequence"
As far as I'm concerned, the last note that appears to be wrong is the SLIDE interpolation of the preceding note.
If I remove the SLIDE, the note is correct.
However, the SLIDE is not recorded.
Another point:
The LOOP function in STOCHASTIC mode does not read SLIDE, RETRIG or REPEAT.
Is this normal?

Yes, when u engage the loop you take a picture of the actual stochastic sequence running. If there is a slide you can engage loop and freeze the sequence and you cannot edit anymore

Okay, I understand the LOOP mode
Do you think it's possible to copy a sequence (from one channel: NOTE or STOCHASTIC) into another NOTE channel, copying all the information defined for each step?
Step, note, repeat, retrig, slide...

I'm working on a copy loop method


Add the build configuration

Configure Azure Pipelines

 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.:x: a360devops sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


[Missing] Cloud themes

Blog: https://telegram.org/blog/scheduled-reminders-themes

This too is related to telegram X.
Has Color theme still not been in the tdlib?
It's missing from the tgx but is there in the plus messenger.
So it's support in the tdlib or not?

@shah-sudeep ok so I've been through a couple of issues where you ping for some things that TGX doesn't support yet. If you have any question about TGX, please ask them in its chat (make sure to read the pinned message, there's a list of missing features). If an issue is still open here, it means the public version of tdlib still doesn't support that functionality. Btw Plus Messenger doesn't use tdlib. The only applications that uses it are Telegram X, Unigram, the bot API and telegram-react


feat: styled and configured for consumption as a shared resource

This is a big PR that does a lot of things, including and especially proving out how to document the use of the UI assets available in this shared library, and consuming them from a dependent project (in this case, it was from the engineering-docs project.
This PR includes some basic styling towards AOEU branding, using our base color palette and typography for starters. This will evolve over time, but the foundation has been set in general. Base Sass modules for colors and typography are available, documented and consumable by dependent projects (which can be seen in the engineering-docs project).
Once this PR has been merged in, we'll want to create some tasks for getting this published as a package that can be yard added to dependent projects. We will want to have a discussion about when will be the appropriate time to configure this project as a monorepo with independently versioned, reusable components so that dependent projects can consume versioned components from it without being forced to take potentially breaking changes when new versions of the library as a whole are published, which will be important long-term.
Once this project has been published, we will be able to add it as a dependency from the engineering-docs repository, which should allow it to be built and published for consumption (the chicken-and-egg scenario discussed here).

It looks like branch rules are setup for 1 code approval only.

@theantichris I fixed the branch protection rules.


Updating helm chart to for configurability and standardization

Since @sidguptajhs is currently out of the office and we would like to proceed with getting this great work out there, I'm undrafting this pull request and merging it upstream while leaving the current outstanding comments unresolved.  There will be a separate pull request to address these comments, after which we hope to release these changes for Voxel to use.
Thanks @sidguptajhs!


Issue in the example on .../keras/basic_classification page

The code below and explanation  pick up from your page https://www.tensorflow.org/tutorials/keras/basic_classification its no actually working. In your case is working for the image in the position 0, but no for the rest due to always is picking up/checking test_labels[i] where i in this case is 0, so always is comparing with test_labels[0] which is '9' (anckle boot).
If you try with test_image[1] , or test_image[2] , ..... you can check how the chart is no show the correct color (predicted/true label)
img = test_images[0]

predictions_single = model.predict(img)

plot_value_array(0, predictions_single, test_labels)
plt.xticks(range(10), class_names, rotation=45)
plt.show()

I only register this issue in order you can improve your documentation.
Thanks for you software.

@jjimenezcapi, In the above mentioned tutorial, test_labels[i], here i is the position of image in the dataset. Where, i=0,  ankle boot image and i=1 T-shirt/top image. Is it allowed to choose any of the image from dataset. Thanks!

Yes I know, but the issue is about the function plot_value_array
Its no possible to call it with another value that 0 for single predictions. It raised and unbound exception . Its only FYI

@jjimenezcapi Thanks for pointing this issue. Actually it was corrected recently, but the website is not updated. You could check the source code and google colab, both were updated and waiting for website to get update.
As you mentioned, In the website it shows
plot_value_array(0, predictions_single, test_labels)

In the source codes, it was updated and shows as
plot_value_array(1, predictions_single[0], test_labels)

I am closing this issue as it was resolved. Thanks for your contribution.


x/website:

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

$ go version
go 1.11

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
mac系统

What did you do?
我知道runtime里面有监听goroutine的处理，当一个goroutine运行时间比较长就会移入global队列中，我但是当每个P执行完成之后又会从global往回拿goroutine。如果我的创建了多个goruntine时候，并且每个groruntine里面都是for {}，go程序就会出问题。

What did you expect to see?
我希望runtime里面监听goroutine的模块中，加入for { }检测。如果有for{}.应该多去创建thread
What did you see instead?

The template was only partially filled, and in chinese. Sorry, but we can't understand.


unusual url string crashs is py3

I installed the current master by pip install zipfile in a recent python3 conda environment
base_url = 'http://............<IP_ADDRESS>:8082'
request.get(base_url)
crashes
and ends with an UnidodeError
python3.6/encodings/idna.py",
line 165, in encode
raise UnicodeError("label empty or too long")
UnicodeError: label empty or too long
May be you can catch this?

For posterity, the complete traceback is this:
>>> requests.get(base_url)
Traceback (most recent call last):
  File "/Users/cory/.pyenv/versions/3.6.0/lib/python3.6/encodings/idna.py", line 165, in encode
    raise UnicodeError("label empty or too long")
UnicodeError: label empty or too long

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/cory/Documents/Python/requests_org/requests/requests/api.py", line 72, in get
    return request('get', url, params=params, **kwargs)
  File "/Users/cory/Documents/Python/requests_org/requests/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/Users/cory/Documents/Python/requests_org/requests/requests/sessions.py", line 493, in request
    prep.url, proxies, stream, verify, cert
  File "/Users/cory/Documents/Python/requests_org/requests/requests/sessions.py", line 666, in merge_environment_settings
    env_proxies = get_environ_proxies(url, no_proxy=no_proxy)
  File "/Users/cory/Documents/Python/requests_org/requests/requests/utils.py", line 692, in get_environ_proxies
    if should_bypass_proxies(url, no_proxy=no_proxy):
  File "/Users/cory/Documents/Python/requests_org/requests/requests/utils.py", line 676, in should_bypass_proxies
    bypass = proxy_bypass(netloc)
  File "/Users/cory/.pyenv/versions/3.6.0/lib/python3.6/urllib/request.py", line 2616, in proxy_bypass
    return proxy_bypass_macosx_sysconf(host)
  File "/Users/cory/.pyenv/versions/3.6.0/lib/python3.6/urllib/request.py", line 2593, in proxy_bypass_macosx_sysconf
    return _proxy_bypass_macosx_sysconf(host, proxy_settings)
  File "/Users/cory/.pyenv/versions/3.6.0/lib/python3.6/urllib/request.py", line 2566, in _proxy_bypass_macosx_sysconf
    hostIP = socket.gethostbyname(hostonly)
UnicodeError: encoding with 'idna' codec failed (UnicodeError: label empty or too long)

I don't think there's much we can do about this. The error is coming out of the standard library (specifically, in the urllib proxy_bypass function). It's present only on Python 3, which feels the need to call socket.gethostbyname. This function will automatically IDNA-encode a unicode hostname, even in situations like this where it's simply not necessary, and its IDNA encoder correctly rejects this.
The only way we can fix this is by moving to a much smarter URL handling implementation that normalizes URLs in some form. The best candidate is hyperlink, but hyperlink also barfs on this for a similar reason (it tries to IDNA-encode and fails).
This means that at best we could fix this by extending hyperlink with a URL host normalizer and then handle it. However, the WHATWG URL specification also appears to forbid this form of URL. If it does I'm not sure why, as Chrome normalizes it (though Safari does not).
Given the amount of work required to do this, I don't see any reason to tolerate it. The URL is just spectacularly far away from anything that can reasonably be expected to work, so I'm inclined to just close this as a won't fix.

I'm encountering this for a URL of the format:
<EMAIL_ADDRESS>and length of 132 characters.

@johnpaulhayes That's still not an issue with the requests library, but as I'm also running into it I figure I'll drop an update.
It's not the total length of the url that seems to do it, just a section of it. The idna encoder seems to break on urls when the first part of the host name is greater than 64 characters long. For whatever reason, it's including the key and secret in there as well. So either avoid python3 or avoid long "key:secret@example" strings (likely by avoiding long api keys) until the underlying functions are fixed. I submitted a bug for it to the python tracker yesterday.

For those interested in the issue on the python side
https://bugs.python.org/issue32958


Updating time bound creates a log entry in time unit that uses it

This seems to be really hard to do because there is no database table that combines time units and time bounds together in some way, like there is between localities and species (at lest I haven't found one)


setOpacity fixes for IE

This issue was imported from Closure Library's previous home at http://closure-library.googlecode.com
The link to the original issue is:
https://code.google.com/p/closure-library/issues/detail?id=251

This issue is being closed as a preparation step before archiving the repository.  See the README for more detail.


feat: add tpl to miw ingress

Description
This PR allows to use template values for ingress hosts.
We have the requirement to dynamically create the hosts.
E.g. this would allow to add variables like .Release.Name and .Release.Namespace to the host:
ingress:
  enabled: true
  tls:
  - hosts:
    - "{{ .Release.Name }}.{{ .Release.Namespace }}.example.org"

Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

Marco Lecheler<EMAIL_ADDRESS>Mercedes-Benz Tech Innovation GmbH (ProviderInformation)

Hi Marco, thank you for your contribution. Please change the target branch to develop.

rebased to get rid of branch diff main...develop - now only the initially desired commits are contained in the PR again


Addon wont start because /dev/* is read only (Operation not permitted)

Description of problem:
There seem to be a problem with the combination of Supervisor & Zigbee2mqtt that causes problems with both Serial Port or Socat setup.
Creating this issue to correlate multiple issues created to try and pinpoint the best solution.
According to #24 the new Supervisor 2021.02.06 introduced new code that might cause this: https://github.com/home-assistant/supervisor/commit/b8a976b3440c57bc6cd3f8617afcc632f57906ff
Zigbee2mqtt add-on version (if edge, please report commit hash):
n/a
Your entire configuration from the frontend (with sensitive fields redacted):
n/a
Running platform (details from Suypervisor > System)
Please make sure you post your details around Core & Supervisor & Operating System below
// Example
Core: core-2021.2.2
Supervisor: supervisor-2021.02.6
Operating System: HassOS 5.4

Related issues:
#26 #24 https://github.com/danielwelch/hassio-zigbee2mqtt/issues/535

Ms de info Marius !

And also linking this where there are some sort of work arounds.
https://community.home-assistant.io/t/hass-io-on-synology-dsm-native-package/125559/1477

just tried on a fresh system (5.11), restored the backup and immediately failed :/ same issue, /dev/ttyXXX is readonly and in this weird 'audio' group.
/dev/serial/by-id/xxx -> shows correct file permissions, but since it's only a symlink to /dev/ttyXXX, add-on still won't start.

so i followed this guys tutorial , and my stick now works and zigbee 2 mqtt also .
back in business :))
https://github.com/Koenkk/zigbee2mqtt/issues/320

@ciotlosm after doing a clean install and NOT restoring from backup, add-on works as expected. there's sth wrong with the update procedure and not the add-on itself

After clean install I receive error:
"Error: Error while opening serialport 'Error: Error: Operation not permitted, cannot open /dev/ttyAML2'"

I confirm that installing the latest version of Supervisor on Synology and then reverting back to 2017.1.7 still keeps /dev/* to be read-only or I dunno what but that's my error.
Zigbee2MQTT:error 2021-02-13 16:41:43: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
    at Znp.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
    at Generator.next (<anonymous>)
    at /app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
    at new Promise (<anonymous>)
    at __awaiter (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
    at SerialPort._error (/app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
    at /app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12

Running the zigbee2mqtt outside of hass.io e.g. by manually installing docker image on my Synology confirmed to be working just fine. Pity that all the devices have to be re-paired and then renamed in Home Assistant but at least I can get my stuff working again.

I think the supervisor is doing something funky with permissions. I upgraded OS and I upgraded the supervisor (running on a RPI4) and I have none of these problems. Might be worth asking on an issue in https://github.com/home-assistant/supervisor/issues

@ciotlosm after installing latest OS from scratch and only restoring the zigbee2mqtt add-on configuration I got it up and running. file permissions still seem to be completely borked, but since it works I can't truly say what was the issue

Running the zigbee2mqtt outside of hass.io e.g. by manually installing docker image on my Synology confirmed to be working just fine. Pity that all the devices have to be re-paired and then renamed in Home Assistant but at least I can get my stuff working again.

I an quite new to everything, can you maybe explain how this is done or where I can find a tutorial to follow

You need to start with MQTT Broker installation
https://www.youtube.com/watch?v=w2eLoQHzQS0&ab_channel=BeardedTinker
Then install zigbee2mqtt using this tutorial (highly recommend using their frontend, after installation check this page)
https://www.youtube.com/watch?v=HbkXQErileU&ab_channel=BeardedTinker
After that, you need to go to the home assistant and add new integration with the MQTT name.
I think this part may be in one of the videos above.

I Have the same problem:
CREATED DECONZ ADAPTER
Zigbee2MQTT:error 2021-03-25 14:01:43: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-03-25 14:01:43: Failed to start zigbee
Zigbee2MQTT:error 2021-03-25 14:01:43: Exiting...
Zigbee2MQTT:error 2021-03-25 14:01:43: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
at Driver. (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/driver.js:159:28)
at Generator.next ()
at /app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/driver.js:8:71
at new Promise ()
at __awaiter (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/driver.js:4:12)
at SerialPort. (/app/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/driver.js:157:45)
at SerialPort._error (/app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
at /app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!
To my understanding hassio internally launches the add-ons as docker containers. According to docker inspect -f '{{ .Mounts }}' [container-id of zigbee2mqtt] the device /dev/ttyACM0 doesn't seem to be mapped to the container.
Perhaps it would help to launch the zigbee2mqtt container with the docker flag '--privileged'. Perhaps this is means disable "Protection mode" at Home Assistant - https://developers.home-assistant.io/docs/add-ons/security/?


Clean up

Pick up on and resolve comments left for pull request reviews

From PR #159
Use of 'all reports' and similar variations within text - consistent use of COUNTER Reports and Standard Views of the COUNTER Reports throughout.

From PR #160
Use 'if called for' consistently versus 'if requested' when referring to called for elements and attributes

From PR #161
Add note that trailing zeros will usually be omitted

From PR #166
Clarify that report providers lacking a Registry record MUST NOT include a value in line 13 of report headers

From PR #171
Clarify that access type for the item holds in all circumstances (i.e. an article can't be open for one user and controlled for another), and that an investigation would be controlled even if the user doesn't have access to the full text (so 1 total item investigation, 1 no license)

From PR #178
Delete appendix D and recode subsequent appendices

From PR #186

add Data_Type to TR_B series because this now includes reference works

From PR #188
Use definition of full content database from appendix in cop body

From PR #191

revise images 3.a, 3.b, 3.c, 3.e


deleting node modules

Hi @vedprakashnautiyal ,
This repository contains node_modules, which is not usually a good practice to have in repository, because It is much bigger in size.
I have deleted it and any repository which contains package.json and one who clones the repository can install node_modules by giving command npm i or npm install
Also I have added correct path of node_modules in .gitignore file, so that It will not get push when any change ins done in node_modules.
Thanks for your attention!

Hi @vedprakashnautiyal ,
Why the build is failing ? because of node_modules ? But in general practice node_modules is not present, Can you let me know why is it happening ?

Hi @vedprakashnautiyal , This repository contains node_modules, which is not usually a good practice to have in repository, because It is much bigger in size. I have deleted it and any repository which contains package.json and one who clones the repository can install node_modules by giving command npm i or npm install Also I have added correct path of node_modules in .gitignore file, so that It will not get push when any change ins done in node_modules.
Thanks for your attention!

Thanks for your contribution, develop build...........
Yeah I forgot to add gitignore file......

And about the build failing, the project was incomplete while it was incorrectly deployed on netlify.........So I thought about improving the project as whole. Thanks for pointing out the best practices


WordPress plugin wrong info

Hello,
The current WordPress plugin states:
Next up spin up your Ghost installation, create a user, or sign in, if you already have an account, navigate to http://yourblogadress/ghost/debug/, and import the posts from the file.
This is not correct and should point out that you need to use 'Labs' within the admin panel.
Apart from that it still works great. Thanks.

Hello!
This script has nothing to do with the Ghost WordPress plugin. You should report the problem there. I've fixed the instructions in the README for this tool though!


lobster: init at unstable-2020-01-22

Motivation for this change
I picked the darwin bits from #59128.
Could someone please trigger a darwin build? not sure if this is still relevant:
https://github.com/NixOS/nixpkgs/pull/59128/commits/1e8d9c20e5b2c554e5a33f17ac3cf455da147f48#diff-d82c125fb3539f785cdbfe6eec27d90dR20-R27
Things done

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

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

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

Closes #59128

@GrahamcOfBorg build lobster

lobster on x86_64-darwin — No attempt

well duh... I put platforms = linux :man_facepalming:
Let's try now

@GrahamcOfBorg build lobster

Rebased, updated, added a test
ping @worldofpeace

Result of nixpkgs-review pr 78562 1

1 package built:
- lobster


support for pytorch 1.3.0

first, this is a great package! it seems like to bring the only cool part of tensorflow (tf.data) to pytorch. Thanks for the effort.
Is torch 1.3.0 supported in the current release?

Sorry for late reply and thanks for your interest.
Yes, it should be supported out of the box, no major changes were introduced as far as I can tell. If anything is broken due to PyTorch update, hit me up with an issue, thanks.

great to know. I would suggest to update the badges on the readme then to make people aware


Create a landing page for the in person training

What the issue is about
We often host live sessions, and in those we ask attendees to start with the main page.
Right now main page info is very scarce.

Instead would be awesome to have a page accessible via codelab.fun/start, which would mention the following things:

Welcome to this course
It is self-paced, you don't need to wait for any special instructions, start now
Start with TypeScript, or if you know it already, start with Angular

Where to start
Root codelab routes are defined in app-routing.module.ts

Hi,
I'd like to work on this one !

@nik72619c Go for it, ping me with any questions


Refactor: Move logging level method to utils

Summary
Provide a brief overview of the changes and the issue being addressed.
Explain the rationale and any background necessary for understanding the changes.
List dependencies required by this change, if any.
The log-level conversion method would be used by reminder too, so moving this to utils.
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[x] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[x] Added comments to complex or tricky code sections.
[x] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 39.316%. remained the same
when pulling c962132eddf54dad782c7ab69a10453ab438212c on Vyom-Yadav:refactor-move-log-level-convertor
into e68fcce36136bd2a9822846458282e26a13619bf on stacklok:main.

@JAORMX I don't want to add all these dependencies to the reminder package:
$ go list -f '{{- range .Imports}}{{println .}}{{end -}}' github.com/stacklok/minder/internal/logger
context
encoding/json
fmt
github.com/ThreeDotsLabs/watermill/message
github.com/google/uuid
github.com/rs/zerolog
github.com/rs/zerolog/log
github.com/stacklok/minder/internal/config/server
github.com/stacklok/minder/internal/engine/actions/alert
github.com/stacklok/minder/internal/engine/actions/remediate
github.com/stacklok/minder/internal/engine/entities
github.com/stacklok/minder/internal/engine/errors
github.com/stacklok/minder/internal/engine/interfaces
github.com/stacklok/minder/internal/util
github.com/stacklok/minder/pkg/api/protobuf/go/minder/v1
google.golang.org/grpc
google.golang.org/grpc/metadata
google.golang.org/grpc/status
io
os
path
path/filepath
time

On the other hand utils package has:
$ go list -f '{{- range .Imports}}{{println .}}{{end -}}' github.com/stacklok/minder/internal/util
bytes
context
crypto/tls
database/sql
encoding/json
errors
fmt
github.com/google/uuid
github.com/itchyny/gojq
github.com/rs/zerolog
github.com/signalfx/splunk-otel-go/instrumentation/github.com/lib/pq/splunkpq
github.com/stacklok/minder/internal/db
github.com/stacklok/minder/internal/util/jsonyaml
github.com/stacklok/minder/pkg/api/protobuf/go/minder/v1
google.golang.org/grpc
google.golang.org/grpc/codes
google.golang.org/grpc/credentials
google.golang.org/grpc/credentials/insecure
google.golang.org/grpc/status
google.golang.org/protobuf/encoding/protojson
google.golang.org/protobuf/reflect/protoreflect
google.golang.org/protobuf/types/known/timestamppb
html/template
io
io/fs
net/http
net/url
os
path/filepath
reflect
regexp
strconv
strings
text/template
time


update signup email

Coverage decreased (-0.02%) to 76.723% when pulling 72ccb35646b67b4f8e9eef9ecfbd08460366cc79 on piamancini-patch-5 into c5ac4bab21665318c6dbaaf4afd401d96c76efd0 on master.

Coverage decreased (-0.02%) to 76.728% when pulling e9d7e76b2d79f98f5a4499c519ab8bafa4ffdad4 on piamancini-patch-5 into c5ac4bab21665318c6dbaaf4afd401d96c76efd0 on master.


Added Win sound in a Game.

fined issue :- #138
Added Win Sound in the Game. if the Player is win or draw.

@iamparas0  merged this pull request

@Dharshini3011 Merged this pull request.

@iamparas0  please merge this pull request.

assign me this task

@Dharshini3011 please merged this pull request


Multiple instances of Gesture Handler were detected.

Hello, i am having issues and i checked https://docs.swmansion.com/react-native-gesture-handler/docs/next/troubleshooting but i dont understand what i should really do.
* What went wrong:
Execution failed for task ':react-native-gesture-handler:assertNoMultipleInstances'.
> java.lang.Exception:
  [Gesture Handler] Multiple instances of Gesture Handler were detected. Only one instance of react-native-gesture-handler can be installed in a project. You need to resolve the conflict manually. Check out the documentation: https://docs.swmansion.com/react-native-gesture-handler/docs/troubleshooting#multiple-instances-of-gesture-handler-were-detected

  Conflict between:
  - C:\Users\Abdullah\Desktop\Programming\company\Chappie\Chappie\node_modules\react-native-gesture-handler\package.json
  - C:\Users\Abdullah\Desktop\Programming\company\Chappie\Chappie\node_modules\showtime-tab-view\node_modules\react-native-gesture-handler\package.json

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
java.lang.StackOverflowError (no error message)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 42s
7 actionable tasks: 2 executed, 5 up-to-date

@abdullahIsa hi, you should check your react-native-gesture-handler version and ensure it more than v2.0.0

@abdullahIsa hi, you should check your react-native-gesture-handler version and ensure it more than v2.0.0

ah thanks, working now, i added this package.json
"overrides": {
    "react-native-gesture-handler": "^2.9.0"
}

is there any particular reason why the lib is frozen to 2.8.0 ?
    "react-native-gesture-handler": "~2.8.0",

I'm using ^2.5.0 and the lib has reached 2.9. Maybe a version bump here ?


cannot layer binutils

I'm trying to install binutils:
$ rpm-ostree install binutils
[...]
error: Checkout binutils-2.40-13.fc39.x86_64: Hardlinking b0/5c0ba45128dbfb28a8089c44e19f93cd0e4531678f017696f69515b916f6c3.file to ld: File exists

afaics this is because the file exists already in the image:
$ podman run -it ghcr.io/ublue-os/silverblue-nvidia:39 ls -l /usr/bin/ld
lrwxrwxrwx. 1 root root 20 Jan 15 15:37 /usr/bin/ld -> /etc/alternatives/ld

$ podman run -it ghcr.io/ublue-os/silverblue-nvidia:39 ls -l /etc/alternatives/ld
lrwxrwxrwx. 1 root root 15 Jan 15 15:37 /etc/alternatives/ld -> /usr/bin/ld.bfd

$ podman run -it ghcr.io/ublue-os/silverblue-nvidia:39 ls -l /usr/bin/ld.bfd
ls: cannot access '/usr/bin/ld.bfd': No such file or directory

it's a symlink to /etc/alternatives/ld, which itself points to /usr/bin/ld.bfd, which doesn't exist.
The symlinks are created here:
https://github.com/ublue-os/nvidia/blob/98c79efbd4f1e929df1dc4416bb701bb9a319969/post-install.sh#L9-L10
I'm wondering if these lines are still relevant, as the file they're linking to doesn't exist anyway?

Can confirm this bug. I cannot install gcc

Any reason distrobox couldn't be used to access this package?

Any reason distrobox couldn't be used to access this package?

It could, but then I'd need to install VS Code also in the same distrobox. If I'm working on a project with lots of exotic dependencies, I would go this route, but in my case I only needed golang (depends on binutils), so I figured it's simpler to just layer it.

I switched to Fedora Silverblue with manually installed nvidia drivers. It is not silver bullet, but it works better in this simple case

You could also create your own image based on silverblue-nvidia, like here: https://github.com/andreasgerstmayr/os-images/blob/main/images/silverblue-nvidia/Containerfile

I believe this a bug related to a workaround done in one (or a few) of the ublue-os Containerfiles.  My understanding is we do need this symlink at some point in our image build process, but it probably should not get left behind on the image.

A confirmation that this is working would be great!

I just tested it, works great!
Thank you @bsherman for resolving this issue :100:


Unused variable marker in pattern match

A la Haskell, writing the Roy
data Maybe a = Nothing | Just a
data Tree a = Nil | Tree (Tree a) a (Tree a)
let rootValue t = match t
  case Nil = Nothing
  case (Tree _ v _) = Just v

should produce JS in which no new variables are introduced for the left and right subtree in the second case of the pattern match.  Instead, it treats _ as a variable name, producing
var Nothing = function(){};
var Just = function(a){this._0 = a};
var Nil = function(){};
var Tree = function(Tree, a, Tree){this._0 = Tree;this._1 = a;this._2 = Tree};
var rootValue = function(t) {
    return (function() {
        if(t instanceof Nil) {
            return new Nothing();
        } else if(t instanceof Tree) {
            var _ = t._0;
            var v = t._1;
            var _ = t._2;
            return new Just(v);
        }
    })();
}

It's a bit unfortunate that the underscore is a valid JS variable name, so we'd want another character for this in Roy.  Relatively unobtrusive keyboard characters that are not valid variable names include -, ~, and .
The _ should also be usable on its own to accept any pattern at the end of a list of matches.

Looks like this has worked since 0197c09513677efdb79775c3a84a409ed3b08210


Tron script rolls back to Windows 11 Classic Command bar

Hi.
I'm using Tron script latest version on Windows 11 22H2 (22621.3880), and after full execution, and after rebooting, after opening File Explorer I see Tron rolled back to Classic Windows 11 command bar, and disables the new design of the File Explorer with Tabs.
I usually like the new design rather than the legacy one, but I see Tron disables it.
And I know it's Tron because I already ran another 7 scripts for debloating and optimizing, and after execution, those scripts didn't disable the new design of File Explorer with tabs.
I really hope that if new version is uploaded, Tron implements a way to let user select if they want the legacy File Explorer design (Windows 11 22H2+) or want to stay in the modern one.

Hi @Rayden-Berzerk409 , if you manually launch O&O ShutUp10 (in tron/resources/stage_4_repair/disable_windows_telemetry), does it allow you to change the design back?
This isn't intentional behavior by Tron, I suspect it may be a change that O&OShutUp10 makes.

I'm having the same problem

restoring o&o to default settings did not fix the problem.

Could this be related to the removal of "modern apps"?

@vocatus please re-open this sissue

@Git-North did you fix it ?


A better way to find globally installed packages

...also echoes an info string when there is nothing to do

...waiting for CI tests to complete

needs more work, obviously


Add bundle name to metadata json

Currently the name used by crc is the directory name contained in the
crcbundle file. crc also guesses it from the crcbundle file, it takes
the name of the bundle without the extension.
Having a clear name property and the fact that the metadata file can be
read by only extracting the first bytes of the bundle, we can remove
this ambiguity.

I would like when crc uses a bundle that it unpacks only the metadata to get the name, then create the directory, then unpack everything in without looking at the structure of the initial archive.
...
Also, I would like to change the bundle name to openshift-4.6.1. So that I can have a collection of bundle like openshift-x and okd-x.

It seems you want to put crc in control of the target directory name it uses to unpack the bundle content. This name would depend on some metadata specific to the bundle (is it openshift or okd? which version?). This seems to be an argument against adding "name": "crc_libvirt_4.6.1" to the metadata though, as you'd then want crc to ignore this?

This name would depend on some metadata specific to the bundle (is it openshift or okd? which version?).

Yes

This seems to be an argument against adding "name": "crc_libvirt_4.6.1" to the metadata though, as you'd then want crc to ignore this?

crc will not ignore it but use it as the bundle name instead of the filename, instead of a directory name. If we want to rename the bundle for crc, we would need to rename it here, in snc.

If we want to rename the bundle for crc, we would need to rename it here, in snc.

Is it useful to let snc mandate where the bundle should be extracted to? We could change crc extraction code to always extract foo.crcbundle to crc_$hypervisor_$openshift_version for now rather than using the default name used when creating the tarball. This also can all be inferred from the bundle metadata, and does not require any changes snc side. Is there some additional benefit I'm missing?

If we choose this pattern this will prevent us from running variations of an openshift bundle. For instance, we could have a bundle openshift-4.6.1.libvirt, okd-4.6.1.libvirt and a bundle openshift-4.6.1.libvirt+srikrishna

I was merely describing how we can slightly change crc to keep exactly the same behaviour as currently, while moving toward what you describe. Once crc takes control of the naming of the directory the bundle is unpacked to, it can do ${product}-${product-version}.${hypervisor} if that's what we want.
The +srikrishna example is interesting as this is not something which can be currently done nicely, which means a new field would be needed in the bundle metadata anyway. Your suggestion is to have a bundle-directory-name, but maybe an extra-version field would be more useful as this is also needed if we want to differentiate multiple bundles which are made for the same openshift version (such as what we did for 4.6.1)?

My suggestion is to give a clear name to each bundle, and not let the consumer guess it like today. Consumer can do what they want but the creator of the bundle gives it a name when building it and today, the name is crc_libvirt_4.6.1.

If we add that name, and this name matches the name of the directory in the tarball, and if we make it mandatory to keep the directory structure and use that name, fine with me.
If we add that name, but also change crc to ignore this name, and make it use its own naming instead, I would say it's pointless to add a name field to snc.

If we add that name, and this name matches the name of the directory in the tarball, and if we make it mandatory to keep the directory structure and use that name, fine with me.

This is exactly the first case!

Thinking some more about this, I wonder if this really is required, or if things could be improved solely on crc side?

When crc gets a .crcbundle file and uncompresses it, it knows which dir the bundle metadata was uncompressed to, so it does not have to guess it from the .crcbundle filename (even if this is what it's doing at the moment).
When we have an already existing VM, and crc needs to get to the bundle metadata, it guesses the path from the bundle name recorded in ~/.crc/machines/crc/config.json. If we don't want to rely on guessing the path, we can fallback on 1., or we could record the path to the bundle metadata file in that config.json file. I'd favour the latter
I think the only remaining case is when the bundle is not embedded, and bundle name is different from the tarball directory structure. We don't support this very well at the moment, if at all, but I'm not sure adding a name to the bundle would make a big difference?

I think the only remaining case is when the bundle is not embedded, and bundle name is different from the tarball directory structure. We don't support this very well at the moment, if at all, but I'm not sure adding a name to the bundle would make a big difference?

Yes you're right, it is only for us. It is just to ease our life and it removes one more ambiguity/bug.

After reading https://github.com/code-ready/snc/pull/267#issuecomment-730221705 (use case - 2) to get the metadata info from the bundle you have it extracted and right now in second run we don't run extraction because the cache exist and to get the info about that cache we make use of the BundleName which is part of  ~/.crc/machines/crc/config.json so are you suggesting that after this change we always run extraction code (even just extract the metadata bit) and then get the cache info?

are you suggesting that after this change we always run extraction code (even just extract the metadata bit) and then get the cache info?

No. I would like to refactor completely the bundle package. Have a proper repository struct like:
type BundleRepository interface {
 Install(path string) *Bundle, error
 Get(name string) *Bundle, error
 Delete(name string) error
}

BundlePath should probably not be used outside of the cmd/crc package and all the pkg code should rely on the bunde name and use the repository if needed.

Is it useful to let snc mandate where the bundle should be extracted to?

it is however the responsibility of the snc bundle and it's metadata to identify and name. The use of a name seems a very valid approach.
However, are you suggestion a more complex:
  Version: '4.6.2',
  Product: "ocp"

and then rely on crc to combine these elements? I do not see the need for CRC to maintai such logic. Also consider that the bundle can be consumed outside of crc, and in that case a 'name' seems a very valid identifier to extract to mean one thing. Details can be added where you see fit and even duplicated, as nothing prevents:
  Name: "openshift-4.6.2",
  Version: "4.6.2',
  Product: 'ocp'

The idea of a BundleRepository is in line how we thought of the cache being used. a simple iteration over the directories (or getting the name from the metadata) in that case is sufficient allows flexibility outside our usecase, like a "custom-websphere-4.6.2" to identify an image maintained outside our team, and still being listed without too much logic. details can be added where people see fit.

Is it useful to let snc mandate where the bundle should be extracted to?

it is however the responsibility of the snc bundle and it's metadata to identify and name. The use of a name seems a very valid approach.
However, are you suggestion a more complex:
  Version: '4.6.2',
  Product: "ocp"

and then rely on crc to combine these elements?

Nope, this was asked before, the plan is to use the name as is in crc
https://github.com/code-ready/snc/pull/267#issuecomment-729050906

The idea of a BundleRepository is in line how we thought of the cache being used. a simple iteration over the directories (or getting the name from the metadata) in that case is sufficient allows flexibility outside our usecase, like a "custom-websphere-4.6.2" to identify an image maintained outside our team, and still being listed without too much logic. details can be added where people see fit.

Just one thing to keep in mind, 'simple iteration over directories' is not free (though it's a lot faster with SSDs). This is not going to be a bottleneck with crc, so not worth a lengthy discussion :)

It doesn't engage us too much. We can still remove it easily.


Write-DbaDataTable Give different example

No reason to include a "not recommended" example.

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[x] Documentation
[ ] Build system

Purpose
Noticed all the examples in this command are using the import command for CSV files. To add a bit of color I'm replacing an example that refers to a method we don't actually recommend using. I see no reason to have that example.
The example provided utilizes Invoke-DbaQuery and simply shows pulling a dataset from a given source and writing it to a new table (auto generated).

Appveyor must be getting sick...that is a lot of failures (none of which have anything to do with this change).

totally! it was bad off for a bit there. looks ok now 🎉


WebApp:staticwebapp - add support for linking existing function app (bring your own functions)

Is your feature request related to a problem? Please describe.
Azure Static Web Apps is adding the ability to link a Static Web App to an existing Azure Functions app. This requires gestures in Az CLI to add and remove the link.
Describe the solution you'd like
Link:
az staticwebapp functions link -g $StaticWebAppGroup -n $StaticWebAppName --function-resource-id $FunctionsResourceId

Unlink:
az staticwebapp functions unlink -g $StaticWebAppGroup -n $StaticWebAppName

Additional context
Needed for Static Web Apps GA

Thanks for your feedback. We will check and consider for future milestones .
@panchagnula FYI


Not getting any image on error although path specfied

On rspec errors, I get a message
Screenshot: [some file path]

However, there's no file.
I've got the following gem versions:
capybara (2.1.0)
  mime-types (>= 1.16)
  nokogiri (>= 1.3.3)
  rack (>= 1.0.0)
  rack-test (>= 0.5.4)
  xpath (~> 2.0)
capybara-screenshot (0.3.14)
  capybara (>= 1.0, < 3)
  launchy

@axlekb @mattheworiordan I can confirm that axlekb's workaround fixed it for me as well.
Let me know if I can help you guys any further into investigating what the issue might be.
Running on this stack:
capybara (2.4.4)
rspec (3.1.0)
poltergeist (1.5.1)
capybara-screenshot (1.0.3)
phantomjs (<IP_ADDRESS>)

@axlekb would you mind trying the Gem using branch poltergeist-fix without the workaround to see if it works for you?  You should be able to do something like this in your Gemfile:
gem 'capybara-screenshot', git: 'https://github.com/mattheworiordan/capybara-screenshot', branch: 'poltergeist-fix'

@mattheworiordan - The FULL page screenshot works!  On failure, the png/html file locations are not printed to the output though.

Actually - Hold that.  I'm actually getting full page PNG screenshot with 1.0.3 and 1.0.4 without the workaround.  Still missing png/html file locations.
With branch: 'poltergiest-fix', getting a screenshot, but it's cut-off and no file location.
capybara (2.4.4)
rspec (3.1.0)
poltergeist (1.5.1)
capybara-screenshot (1.0.3 or 1.0.4)
phantomjs (1.9.7)

@karlingen - what issue were you having?
For me, the only remaining issue is the file locations in the output.

@axlekb the issue I had before your workaround was that it did not save any png file, eventhough I called screenshot_and_save_page.
What do you mean with "missing png/html file locations."? Are they supposed to be written out when running the specs?

@axlekb Oh, I have not noticed that.

@axlekb can you grab me a sample of your test output without the screen shots i.e. where it fails please?  I will try and replicate soon.

Here's the output.  Both screenshots were generated:
$ rspec spec/features/unauthorized_user_sees_error_spec.rb

Failures:

  1) Dummy Test to see .png and .html output
     Failure/Error: expect(1).to eq(0)

       expected: 0
            got: 1

       (compared using ==)
     # ./spec/features/unauthorized_user_sees_error_spec.rb:11:in `block (2 levels) in <top (required)>'

Finished in 34.06 seconds (files took 27.28 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/features/unauthorized_user_sees_error_spec.rb:8 # Dummy Test to see .png and .html output

Top 1 slowest examples (31.99 seconds, 93.9% of total time):
  Dummy Test to see .png and .html output
    31.99 seconds ./spec/features/unauthorized_user_sees_error_spec.rb:8

Randomized with seed 52215


⚠ Bofrost.de has degraded performance

In 36876c7, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1121 ms

Resolved: Bofrost.de performance has improved in 4fecf02.


Drop support for PHP 7.4 and fixed deprecation warnings

I think this will require a new major version once this is merged

there were issues with this code and we stopped using the library in order to use something custom


Quick indication in settings menu whether a function is active at all

Description of the new feature / enhancement
I'd like to see e.g. the Color Picker entry being greyed out if the function isn't active.
Scenario when this would be used?
When looking at the setting screen, the menu on the left would be easier to navigate if I could directly see which functions I have active vs. those I already disabled.
Supporting information
No response

Duplicate of #14129

Issue is a duplicate
Thank you for your issue! We've linked your report against another issue to centralize the thread.
Thanks for helping us to make PowerToys a better piece of software.

Aww I didn't see this dup. Sorry. As this is a duplicate let's close it.


spawn react-scripts ENOENT

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
18.17.0
Amplify CLI Version
12.1.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
/var/folders/8r/95d5dqn56_l5cn7nqrdhm47h0000gn/T/asystPaie/report-1689845743490.zip
I am trying to deploy a React app but I am getting  this error spawn react-scripts ENOENT
Expected behavior
Deployment successful
Reproduction steps

Deploy manually
Initialize the project using amplify unit
Then deploy it using amplify publish

Project Identifier
/var/folders/8r/95d5dqn56_l5cn7nqrdhm47h0000gn/T/asystPaie/report-1689845743490.zip
Log output

# Put your logs below this line
✖ There was an error pulling the backend environment dev.
🛑 EACCES: permission denied, mkdir '/Users/asyst/Desktop/Asyst/erp-paie-frontend/amplify/.temp'

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: c39459ea-feaa-4734-accb-dce803f9e576

✔ Successfully pulled backend environment dev from the cloud.

    Current Environment: dev

┌──────────┬─────────────────┬───────────┬───────────────────┐
│ Category │ Resource name   │ Operation │ Provider plugin   │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Hosting  │ amplifyhosting  │ No Change │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Hosting  │ S3AndCloudFront │ No Change │ awscloudformation │
└──────────┴─────────────────┴───────────┴───────────────────┘

No changes detected

? Do you still want to publish the frontend? Yes
frontend build command execution error
Error: spawn react-scripts ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:476:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn react-scripts',
  path: 'react-scripts',
  spawnargs: [ 'build' ]
}
🛑 spawn react-scripts ENOENT

Resolution: Please report this issue at https://github.com/aws-amplify/amplify-cli/issues and include the project identifier from: 'amplify diagnose --send-report'
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
🛑 spawn react-scripts ENOENT

Resolution: Please report this issue at https://github.com/aws-amplify/amplify-cli/issues and include the project identifier from: 'amplify diagnose --send-report'
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: 45458bfb-90f8-4e4d-ac1b-9a3c300273e7

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @WCanirinka, thank you for reaching out.  Can you confirm your project settings point to the appropriate distribution directory? amplify/.config/project-config.json. Additionally, check if the BuildCommand is set to the appropriate commands such as npm run build or pnpm build? if not we can modify this by either editing this file manually or stepping through amplify configure project
note: If you do not see the amplify/.config folder, we will need to open .vscode/settings.json and set amplify/.config as false.

Closing due to inactivity


Google maps plugin on Android fails to center initial location when surface size is changed.

Steps to Reproduce
Running the following test fails when using Flutter master: https://github.com/flutter/plugins/blob/main/packages/google_maps_flutter/google_maps_flutter/example/integration_test/google_maps_test.dart#L428
The test runs successfully when the following line is removed https://github.com/flutter/plugins/blob/main/packages/google_maps_flutter/google_maps_flutter/example/integration_test/google_maps_test.dart#L428
await tester.binding.setSurfaceSize(const Size(800.0, 600.0));

Logs
06-27 08:46:06.083: I/flutter(22833): The following TestFailure was thrown running a test:
06-27 08:46:06.083: I/flutter(22833): Expected: <1100>
06-27 08:46:06.083: I/flutter(22833):   Actual: <540>
06-27 08:46:06.083: I/flutter(22833): When the exception was thrown, this was the stack:
06-27 08:46:06.083: I/flutter(22833): #4      main.<anonymous closure> (file:///tmp/cirrus-ci-build/packages/google_maps_flutter/google_maps_flutter/example/integration_test/google_maps_test.dart:464:7)
06-27 08:46:06.083: I/flutter(22833): <asynchronous suspension>
06-27 08:46:06.083: I/flutter(22833): #5      testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:171:15)
06-27 08:46:06.083: I/flutter(22833): <asynchronous suspension>
06-27 08:46:06.083: I/flutter(22833): #6      TestWidgetsFlutterBinding._runTestBody (package:flutter_test/src/binding.dart:841:5)
06-27 08:46:06.083: I/flutter(22833): <asynchronous suspension>
06-27 08:46:06.083: I/flutter(22833): This was caught by the test expectation on the following line:
06-27 08:46:06.083: I/flutter(22833):   file:///tmp/cirrus-ci-build/packages/google_maps_flutter/google_maps_flutter/example/integration_test/google_maps_test.dart line 464
06-27 08:46:06.083: I/flutter(22833): The test description was:
06-27 08:46:06.083: I/flutter(22833):   testInitialCenterLocationAtCenter
06-27 08:46:06.084: I/flutter(22833):

cc @dnfield @cyanglaz

The issue is that virtual display changes size based on the current physcial screen size: https://github.com/flutter/engine/blob/main/shell/platform/android/io/flutter/plugin/platform/VirtualDisplayController.java#L47-L74, so GoogleMap uses the new virtual display size. On the other hand, the GoogleMap flutter widget doesn't know virtual display has resized.
This leads to test trying to compare values based on 2 different sizes.
We can do 1 of the following:

Revert the code that resizing the Virtual Display. This will crash user that set a virtual display size that is bigger than the current screen size. This crash is the default Android behavior and I think it is OK to align the behavior with Android.
Update the test so that the surface size is smaller than the physical screen. Even we can probably find a very small number to ensure the size is smaller than the screen, this is still not a good solution as it doesn't cover all the cases.

I think reverting the code that resizes for now is fine. But we should still file a bug for this. In general, we should avoid letting Dart code cause native crashes - it ends up breaking hot reload workflows and results in poor DX and UX.

Fixed with https://github.com/flutter/plugins/pull/6097


Inclusion of Python and R colors

As in alternative to JS/SVG/CSS color, for fairness, in all times.

TKinter http://www.science.smith.edu/dftwiki/index.php/Color_Charts_for_TKinter
Pyxplot http://pyxplot.org.uk/current/doc/html/ch-color_charts.html
PyX https://pyx-project.org/manual/colorname.html
R https://www.datanovia.com/en/blog/awesome-list-of-657-r-color-names/

I would like to work on this.


Move kube-scheduler related resources into kubescheduler pkg

How to categorize this PR?

/area dev-productivity testing quality
/kind enhancement
/priority normal
What this PR does / why we need it:
After #2731, there were still resources/code related to kube-scheduler scattered in other packages/places. With this PR, we move them into the kubescheduler package as well. This includes

Resources created in the shoot (RBAC roles for Kubernetes 1.13)
Prometheus scrape configuration
AlertManager alerting rules
fluent-bit parsers and filters

Please note that the only things it does not include are the Grafana dashboards. @wyb1 might have some ideas how to achieve the same for them in the future.
Which issue(s) this PR fixes:
Part of #2754
Special notes for your reviewer:
/assign @timebertt @wyb1 @Kristian-ZH @vlvasilev
Release note:

NONE

@wyb1 Thanks, strange, I haven't experienced it. I will take a look.

@wyb1 fixed, PTAL

/status author-action

@timebertt @wyb1 please take another look, I've incorporated your suggestions


Allow free rotation of the atlas

Before submitting a pull request (PR), please read the contributing guide.
Please fill out as much of this template as you can, but if you have any problems or questions, just leave a comment and we will help out :)
Description
What is this PR

[ ] Bug fix
[x] Addition of a new feature
[ ] Other

Why is this PR needed?
Some slices may have been taken at an angle, rotating the atlas allows viewing and registering to non-orthogonal slices of the atlas.
What does this PR do?
Provides a UI to rotate the atlas based on yaw, pitch and roll. This allows the user to find the correct 2D slice to register to, even if it's not aligned with the atlas axes.
Checklist:

[x] The code has been tested locally
[x] Tests have been added to cover all new functionality (unit & integration)
[x] The code has been formatted with pre-commit

Thanks for taking a look!

I did some user testing and found UX improvements that might be worth addressing as separate issues (maybe you have already):
* users can select a sample image, and then delete the layer in napari, and then cause an index error when selecting an image in the plugin.

* the same can happen if you delete the atlas-related layers in napari and then select a new atlas in the plugin

This has been on my list of things to address, I'm not happy with how fragile it is at the moment. I haven't validated starting from "scratch" without re-opening napari. I'll make an issue.

* if I click the rotate button in not-grid mode, it additionally toggles to grid mode - is that intended?

This was a hacky way to reset the view, otherwise the rotated atlas doesn't quite look right. I'll come back to it and see if there's a better way of refreshing the canvas without toggling grid mode.


feat: Adding fee parameter to CoreAccessor operations

Overview
Adding fee parameter to CoreAccessor operations

Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Codecov Report

Merging #1484 (70de3df) into main (a6ac321) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

:exclamation: Current head 70de3df differs from pull request most recent head 5983169. Consider uploading reports for the commit 5983169 to get more accurate results

@@            Coverage Diff             @@
##             main    #1484      +/-   ##
==========================================
- Coverage   55.20%   55.17%   -0.03%
==========================================
  Files         203      203
  Lines       12125    12135      +10
==========================================
+ Hits         6693     6696       +3
- Misses       4768     4776       +8
+ Partials      664      663       -1

Impacted Files
Coverage Δ

api/gateway/state.go
0.00% <0.00%> (ø)

nodebuilder/state/mocks/api.go
11.45% <0.00%> (ø)

nodebuilder/state/state.go
7.14% <0.00%> (ø)

state/core_access.go
16.53% <0.00%> (-0.20%)
:arrow_down:

share/ipld/get.go
92.18% <0.00%> (-1.24%)
:arrow_down:

share/eds/byzantine/bad_encoding.go
69.00% <0.00%> (+3.00%)
:arrow_up:

header/core/listener.go
58.49% <0.00%> (+5.66%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add new product tile

Add product tile component - it might replace product item component in the future.

Screenshots

Pull Request Checklist

[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] Changes are mentioned in the changelog.

After fixing two issues this PR can be merged

done


Error: Could not find a version that satisfies the requirement mlx>=0

I followed the installation instructions provided in the document, but encountered an error.
ERROR: Could not find a version that satisfies the requirement mlx>=0.1 (from mlx-lm) (from versions: none)
ERROR: No matching distribution found for mlx>=0.1

conda 24.1.2
pip 23.3.1 (python 3.11)
Apple M1 Max

i just updated the installation instruction, you can try again now!

windows 11
same issue

windows 11

mlx is a mac silicon only framework so i dont think this would work on windows 11

I got the same Error:
Python version: Python 3.11.0
OS: MacOS
ERROR: Ignored the following versions that require a different python version: 1.21.2 Requires-Python >=3.7,<3.11; 1.21.3 Requires-Python >=3.7,<3.11; 1.21.4 Requires-Python >=3.7,<3.11; 1.21.5 Requires-Python >=3.7,<3.11; 1.21.6 Requires-Python >=3.7,<3.11
ERROR: Could not find a version that satisfies the requirement mlx>=0.1 (from mlx-lm) (from versions: none)
ERROR: No matching distribution found for mlx>=0.1

I have tried python 3.8.9  python 3.12.2 python 3.8.9  but all failed.

I think you have an incompatible MacOS version or machine.
Note that this issue only for MacOS >= 13.3 and the Mac needs to run Apple Silicon (M1/M2/M3) chip. Can you confirm that on your end?

I got the same Error:
Apple M2
macOS 14.3
ERROR: Ignored the following versions that require a different python version: 1.21.2 Requires-Python >=3.7,<3.11; 1.21.3 Requires-Python >=3.7,<3.11; 1.21.4 Requires-Python >=3.7,<3.11; 1.21.5 Requires-Python >=3.7,<3.11; 1.21.6 Requires-Python >=3.7,<3.11
ERROR: Could not find a version that satisfies the requirement mlx>=0.1 (from mlx-lm) (from versions: none)
ERROR: No matching distribution found for mlx>=0.1

Device: MBP 2023, Apple M2 Pro, MacOS 14.3.1 (23D60)
Python: 3.11.5
I got a similar error:
ERROR: Could not find a version that satisfies the requirement mlx>=0.1 (from mlx-lm) (from versions: none)
ERROR: No matching distribution found for mlx>=0.1

Hi @teojs & @MrFrankChen are you guys installing with normal pip? can you try to install with conda or pip install chat-with-mlx?

Hi @teojs & @MrFrankChen are you guys installing with normal pip? can you try to install with conda or pip install chat-with-mlx?

Thank you! I found a solution here "https://github.com/ml-explore/mlx/issues/200", created an environment with a native Python, and then it works.

I got same question
Device: MBP 2023
System: Sonoma 14.0
Python: conda 23.1.0  Python 3.11.8
Finnaly i solve the problem.
Reason: mlx
Solve: stack overflow solution
Simple solution command: CONDA_SUBDIR=osx-arm64 conda create -n native-mlx-chat python=3.11 -c conda-forge
use the command create a new conda env. and finnaly it works for me.

I had the same issue and I think it happens only to conda user. I fixed the issue by specify the platform to be "osx-arm64" when create the env:
CONDA_SUBDIR=osx-arm64 conda create -n mlx-chat python=3.11
conda activate mlx-chat
conda config --env --set subdir osx-arm64
then python -m pip insall -e . should be ok.
Reference: https://stackoverflow.com/questions/65415996/how-to-specify-the-architecture-or-platform-for-a-new-conda-environment-apple


Webserver does not shut down when main process is killed

Currently there's a separate Thread for the webserver.

Nevermind, shutting down the bot via ctrl-c works. It didn't work due to issues with supervisor.
See here how to solve that supervisor issue.


Replace ROSE with bedtools

Description of feature
As commented in #5, we should check if it is possible to remove the ROSE codebase of 620 lines and replace it by some bedtools processes.
          @LeonHafner we should investigate if we can replace this with a sequence of `bedtools` commands, which would reduce the amount of code drastically

Originally posted by @nictru in https://github.com/nf-core/tfactivity/issues/5#issuecomment-2077152326

I just went through the logic of ROSE again and as far as I can tell, it builds TSS loci based on the start of all transcripts in the genepred file, then removes all fully contained candidate regions and then merges all candidate regions within a certain range. Then it reverts the merging for all regions overlapping more than 2 unique TSSs.
Based on this, I would suggest a workflow like this:

Keep the GTF to genepred conversion as it is, as it is helpful for transcript extraction (except step 2 is easily possible based on GTF)
Convert the genepred file to a bed file, which resembles the TSS windows (depending on strand, either start+/-tss_window or end+/-tss_window, can probably be done using GAWK or BIOAWK nf-core modules
bedtools subtract -a candidates.bed -b tss.bed -f 1
bedtools merge -d 12500 -i subtracted.bed
Don't have an idea yet about the reverting of the regions with more than 2 TSS overlaps (is it even necessary?)

I think it is good to mention that the removal of regions close to TSS is most likely done to exclude promoter regions. If we would also want to investigate candidate promoter regions, we would only have to invert this logic. For this we would have to replace bedtools subtract with bedtools intersect in step 4.


nixos: Fix systemd-initrd-simple test

This has been broken since 246d09fea28c85de7a2f6223fad6927429c3697b
/cc @lheckemann
Description of changes
Since 246d09fea28c85de7a2f6223fad6927429c3697b, we've been getting this error because of the change to how qemu-vm.nix defines the root FS.
error: The option `nodes.machine.fileSystems."/".autoResize' has conflicting definition values:
       - In `makeTest parameters': true
       - In `/root/nixpkgs/nixos/modules/virtualisation/qemu-vm.nix': false
       Use `lib.mkForce value` or `lib.mkDefault value` to change the priority on any of these definitions.

This can be fixed by changing the test to do it the same way.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

@ofborg test systemd-initrd-simple


python3Packages.formbox: init at 0.1.0

Motivation for this change
I am using this to embed comments to my personal web log.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

2 packages built:

python38Packages.formbox
python39Packages.formbox

Thanks!


Allow gossiping to continue across sessions

When a node restarts, it should start gossiping about data which was previously being gossiped, but hadn't yet completed.

roadmap#102 should probably be implemented before this.

Won't do.


Unable to connect to peers in Bodies stage

Describe the bug
I'm running a reth/lighthouse validator node on goerli. After reaching 98.2% of the Bodies stage reth has been unable to connect to peers for ~12 hours. It stays at 0 peers connected and whenever it establishes a session with a peer it's immediately followed by a disconnect command for the session. I have tried restarting reth.
Steps to reproduce
I'm running the reth/lighthouse on a spare laptop with the following specs:

32GB Dual Channel DDR4 at 2666MHz (2x16GB)
1 TB M.2 SSD
2 TB 2.5" Solid State Hybrid Drive
4.1 GHz i7-875OH (2.2 up to 4.1 GHz - 9MB Cache - 6 cores - 12 threads)

Reth, lighthouse-beacon and lighthouse-validator are running as services in /etc/systemd/system/ with the following configuration (*** for possibly sensitive fields):
Reth:
[Unit]
Description=Reth Execution Client (Goerli Test Network)
After=network.target
Wants=network.target

[Service]
User=reth
Group=reth
Type=simple
Restart=always
RestartSec=5
Environment="RUST_LOG=info"
ExecStart=/usr/local/bin/reth node \
  --datadir /var/lib/reth \
  --authrpc.jwtsecret=***/jwt.hex \
  --authrpc.addr <IP_ADDRESS> \
  --authrpc.port 8551 \
  --http --http.api "admin,debug,eth,net,trace,txpool,web3,rpc" \
  --chain goerli \
  --metrics <IP_ADDRESS>:9001

[Install]
WantedBy=default.target

Lighthouse beacon
[Unit]
Description=Lighthouse Consensus Client BN (Goerli Test Network)
Wants=network-online.target
After=network-online.target

[Service]
User=lighthousebeacon
Group=lighthousebeacon
Type=simple
Restart=always
RestartSec=5
ExecStart=/usr/local/bin/lighthouse bn \
  --network goerli \
  --datadir /var/lib/lighthouse \
  --http \
  --execution-endpoint http://localhost:8551 \
  --execution-jwt ***/jwt.hex \
  --checkpoint-sync-url https://sync-goerli.beaconcha.in \
  --metrics \
  --purge-db

[Install]
WantedBy=multi-user.target

Lighthouse validator
[Unit]
Description=Lighthouse Consensus Client VC (Goerli Test Network)
Wants=network-online.target
After=network-online.target

[Service]
User=lighthousevalidator
Group=lighthousevalidator
Type=simple
Restart=always
RestartSec=5
ExecStart=/usr/local/bin/lighthouse vc \
  --network goerli \
  --datadir /var/lib/lighthouse \
  --suggested-fee-recipient *** \
  --graffiti ***

[Install]
WantedBy=multi-user.target

Node logs
Jul 06 14:38:15 pop-os reth[23682]: 2023-07-06T20:38:15.562190Z  INFO reth::node::events: Forkchoice updated head_block_hash=0x4facb1b909211629059eaf11679096a90f796c91ecf0d2388ef05530a2411467 safe_block_hash=0x61a5bc045be226d986cb4db401c9031559e9e43d5afbe698d3af9e83fc613576 finalized_block_hash=0x2e1d00d5c555d4ead1f8d0635c5a1ee54035b5affe079deca5477754f861d052 status=Syncing
Jul 06 14:38:17 pop-os reth[23682]: 2023-07-06T20:38:17.360695Z  INFO reth::cli: Status connected_peers=0 stage=Bodies checkpoint=98.2% eta=unknown
Jul 06 14:38:23 pop-os reth[23682]: 2023-07-06T20:38:23.282389Z  INFO net: Session established remote_addr=<IP_ADDRESS>:20303 client_version=erigon/v2.40.1-stable-94b4cee5/linux-amd64/go1.18.1 peer_id=0x57cd06afc853a6c9a11c0b6d576105b496ffe4f2b7a5a605d5eae2f77f26e42edd55906aa89dc7bab6c6e742c7c19d235f817f714e99808eaa0cbf86c386c0e9 total_active=1
Jul 06 14:38:25 pop-os reth[23682]: 2023-07-06T20:38:25.447449Z  INFO reth::node::events: Forkchoice updated head_block_hash=0x5765c1f29c3c065682b4ddcdaf05d8cee6422a2b72257d9e328c515da46de0af safe_block_hash=0x61a5bc045be226d986cb4db401c9031559e9e43d5afbe698d3af9e83fc613576 finalized_block_hash=0x2e1d00d5c555d4ead1f8d0635c5a1ee54035b5affe079deca5477754f861d052 status=Syncing
Jul 06 14:38:34 pop-os reth[23682]: 2023-07-06T20:38:34.164544Z  INFO net: Session established remote_addr=<IP_ADDRESS>:30304 client_version=Geth/v1.11.6-stable-ea9e62ca/linux-amd64/go1.20.3 peer_id=0x7f47bbd5e7cb2516d027bec110b837c423bfab3772741287fa8ee54a638fb1e67630865ecb44b060223327432bdd71eda2415dad34651f07fec245e8c61fad5d total_active=1
Jul 06 14:38:37 pop-os reth[23682]: 2023-07-06T20:38:37.903726Z  INFO reth::node::events: Forkchoice updated head_block_hash=0x369aec49f4bc156bacd825e5680d554103d4697107e1652057bb047f3226acb9 safe_block_hash=0x61a5bc045be226d986cb4db401c9031559e9e43d5afbe698d3af9e83fc613576 finalized_block_hash=0x2e1d00d5c555d4ead1f8d0635c5a1ee54035b5affe079deca5477754f861d052 status=Syncing
Jul 06 14:38:47 pop-os reth[23682]: 2023-07-06T20:38:47.360791Z  INFO reth::cli: Status connected_peers=0 stage=Bodies checkpoint=98.2% eta=unknown
Jul 06 14:38:48 pop-os reth[23682]: 2023-07-06T20:38:48.963981Z  INFO reth::node::events: Forkchoice updated head_block_hash=0xa58d75350176143134970ae39784b5e83458b38561e5e90456fb73350da19e6a safe_block_hash=0x61a5bc045be226d986cb4db401c9031559e9e43d5afbe698d3af9e83fc613576 finalized_block_hash=0x2e1d00d5c555d4ead1f8d0635c5a1ee54035b5affe079deca5477754f861d052 status=Syncing
Jul 06 14:39:17 pop-os reth[23682]: 2023-07-06T20:39:17.361301Z  INFO reth::cli: Status connected_peers=0 stage=Bodies checkpoint=98.2% eta=unknown
Jul 06 14:39:18 pop-os reth[23682]: 2023-07-06T20:39:18.823117Z  INFO net: Session established remote_addr=<IP_ADDRESS>:30304 client_version=Geth/v1.11.6-stable-ea9e62ca/linux-amd64/go1.20.3 peer_id=0x7f47bbd5e7cb2516d027bec110b837c423bfab3772741287fa8ee54a638fb1e67630865ecb44b060223327432bdd71eda2415dad34651f07fec245e8c61fad5d total_active=1
Jul 06 14:39:18 pop-os reth[23682]: 2023-07-06T20:39:18.891256Z  INFO net: Session established remote_addr=<IP_ADDRESS>:30303 client_version=Nethermind/v1.19.2+42ba08b7/linux-x64/dotnet7.0.5 peer_id=0xbbe8ea836cc682a582811894a692dc526234535d1a902e503a6f34f6ca9c3ca4f8b7aaee46de4eece51ea5bc2649be014f24cf32d5781e612931faa801e9d04d total_active=1
Jul 06 14:39:19 pop-os reth[23682]: 2023-07-06T20:39:19.081241Z  INFO net: Session established remote_addr=<IP_ADDRESS>:40303 client_version=Nethermind/v1.17.2+4faa7314/linux-x64/dotnet7.0.4 peer_id=0x001cfb117d33c83c4cd137690563eca9609da02e33b9fe41feb79995a65df26063755eac848f4bca01750c1b13be435ab730e102145351a5fa1b171ba86d5702 total_active=2
Jul 06 14:39:19 pop-os reth[23682]: 2023-07-06T20:39:19.356246Z  INFO net: Session established remote_addr=<IP_ADDRESS>:30303 client_version=Geth/v1.11.6-stable/linux-amd64/go1.20.3 peer_id=0x6fbc0c561a412cbc2e2195936b165e9713386a712c5188b96ba03b067de0adc8047ff2927123ef9718dd163eb07d287db352c9b771588fe611daee207767666b total_active=2
Jul 06 14:39:22 pop-os reth[23682]: 2023-07-06T20:39:22.546349Z  INFO net::session: Received disconnect command for session reason=Some(DisconnectRequested) remote_peer_id=0x001cfb117d33c83c4cd137690563eca9609da02e33b9fe41feb79995a65df26063755eac848f4bca01750c1b13be435ab730e102145351a5fa1b171ba86d5702
Jul 06 14:39:27 pop-os reth[23682]: 2023-07-06T20:39:27.709133Z  INFO reth::node::events: Forkchoice updated head_block_hash=0xaf567cf21651eceb53bf61055eb0baf805d801c772345e6532489a8ab80416a0 safe_block_hash=0x61a5bc045be226d986cb4db401c9031559e9e43d5afbe698d3af9e83fc613576 finalized_block_hash=0x2e1d00d5c555d4ead1f8d0635c5a1ee54035b5affe079deca5477754f861d052 status=Syncing
Jul 06 14:39:30 pop-os reth[23682]: 2023-07-06T20:39:30.666734Z  INFO net::session: Received disconnect command for session reason=Some(DisconnectRequested) remote_peer_id=0x6fbc0c561a412cbc2e2195936b165e9713386a712c5188b96ba03b067de0adc8047ff2927123ef9718dd163eb07d287db352c9b771588fe611daee207767666b
Jul 06 14:39:47 pop-os reth[23682]: 2023-07-06T20:39:47.360866Z  INFO reth::cli: Status connected_peers=0 stage=Bodies checkpoint=98.2% eta=unknown
Jul 06 14:39:49 pop-os reth[23682]: 2023-07-06T20:39:49.795273Z  INFO reth::node::events: Forkchoice updated head_block_hash=0xf90aa579a46f8683a59395e2909b94f868194cd75cfb75251ceb1050d085f10b safe_block_hash=0x61a5bc045be226d986cb4db401c9031559e9e43d5afbe698d3af9e83fc613576 finalized_block_hash=0x2e1d00d5c555d4ead1f8d0635c5a1ee54035b5affe079deca5477754f861d052 status=Syncing
Jul 06 14:40:03 pop-os reth[23682]: 2023-07-06T20:40:03.911608Z  INFO net: Session established remote_addr=<IP_ADDRESS>:30304 client_version=Geth/v1.11.6-stable-ea9e62ca/linux-amd64/go1.20.3 peer_id=0x7f47bbd5e7cb2516d027bec110b837c423bfab3772741287fa8ee54a638fb1e67630865ecb44b060223327432bdd71eda2415dad34651f07fec245e8c61fad5d total_active=1
Jul 06 14:40:17 pop-os reth[23682]: 2023-07-06T20:40:17.360588Z  INFO reth::cli: Status connected_peers=0 stage=Bodies checkpoint=98.2% eta=unknown
Jul 06 14:40:21 pop-os reth[23682]: 2023-07-06T20:40:21.636743Z  INFO net: Session established remote_addr=<IP_ADDRESS>:30303 client_version=Geth/v1.11.6-stable/linux-amd64/go1.20.3 peer_id=0xe050cc5f3dfa32cbdb3c10fdd5fa071a5910f6f07f53d319ea7c4f6739c962f86b060806f0610df454beccfb85cd9440b0131845d5a65852b18e5a30e534e3e1 total_active=1
Jul 06 14:40:38 pop-os reth[23682]: 2023-07-06T20:40:38.395298Z  INFO net::session: Received disconnect command for session reason=Some(DisconnectRequested) remote_peer_id=0xe050cc5f3dfa32cbdb3c10fdd5fa071a5910f6f07f53d319ea7c4f6739c962f86b060806f0610df454beccfb85cd9440b0131845d5a65852b18e5a30e534e3e1
Jul 06 14:40:47 pop-os reth[23682]: 2023-07-06T20:40:47.360526Z  INFO reth::cli: Status connected_peers=0 stage=Bodies checkpoint=98.2% eta=unknown
Jul 06 14:40:48 pop-os reth[23682]: 2023-07-06T20:40:48.938402Z  INFO net: Session established remote_addr=<IP_ADDRESS>:30304 client_version=Geth/v1.11.6-stable-ea9e62ca/linux-amd64/go1.20.3 peer_id=0x7f47bbd5e7cb2516d027bec110b837c423bfab3772741287fa8ee54a638fb1e67630865ecb44b060223327432bdd71eda2415dad34651f07fec245e8c61fad5d total_active=1
Jul 06 14:40:51 pop-os reth[23682]: 2023-07-06T20:40:51.420309Z  INFO reth::node::events: Forkchoice updated head_block_hash=0xc9a66879ff259d82babee1491a7469934118edacb5edbb045e0e7d8172f4ca1a safe_block_hash=0x61a5bc045be226d986cb4db401c9031559e9e43d5afbe698d3af9e83fc613576 finalized_block_hash=0x2e1d00d5c555d4ead1f8d0635c5a1ee54035b5affe079deca5477754f861d052 status=Syncing

Platform(s)
Linux (x86)
What version/commit are you on?
reth Version: 0.1.0-alpha.1
What database version are you on?
Current database version: 1
Local database version: 1
If you've built Reth from source, provide the full command you used
No response
Code of Conduct

[X] I agree to follow the Code of Conduct

Similar thing happened at different stage. I have been at 98% for about 3 days now without being able to connect to peers:

sorry to hear that,
there have been reports that peering is especially bad on goerli for some reason
could you try sepolia as an alternative? should only take a few hours

Syncing testnets can be very very hard because of the low quality peerset. I have been unable to peer on Goerli myself, but getting peers on Sepolia without issue.
For more context, would it be possible if you could screenshot the graphs of the "Disconnect reason" pie on the Grafana dashboard? (filter out too many peers as it likely takes up 99% of the pie)

Thanks for your responses. Will probably move to Sepolia then. I'm attaching the Grafana "Disconnect reason" panel with "too many peers" filtered out.

DisconnectRequested: 2519
SubprotocolSpecific: 1594
ClientQuitting: 402
AlreadyConnected: 309
UselessPeer: 13

Interesting, I don't really see DisconnectRequested that often on other networks, @mattsse do you off-hand know any reason peers would disconnect with this reason? My only guess would be that peers would want to disconnect from us with this reason if 1) they only want synced nodes, 2) they find us to be low quality for some reason? i.e. poor latency, unsure if any nodes filter on this rn or 3) we have a low reputation for some reason

I have a similar issue, though my grafana pie-graph only is labeled $x-series. This is the stock dashboard, so not sure how mine has different labels. As you can see, once I hit sync finished after IndexAccountHistory step was completed, all peers disconnect and then I can't seem to establish connections that the other side doesn't drop anymore. More info about my setup here: https://github.com/paradigmxyz/reth/discussions/3369
Link to grafana dashboard snapshot: https://snapshots.raintank.io/dashboard/snapshot/C80oDckicKcftBzSE4D3NNkjE13nP6T9?orgId=2&refresh=30s

Nevermind, this is fixed after using latest master instead of 0.1.0-alpha.3. Probably due to recent bugfix https://github.com/paradigmxyz/reth/pull/3783

Yep exactly! Sorry about that folks. Closed by #3783.


Get rid of "sl, sh, sa, dl, dh, da, pl, ph, pa", deliver the numbers programatically.

Each set provides low, high, and average, and we have a method (list_low_high_avg()) that can produce those numbers. We don't need a long dict for storing data.

Done as a part of issue_006.


[Release-1.26] - Bump kine to v0.10.2

Backport fix for Bump kine to v0.10.2

#8112

Verified kine bump on 1.26 branch using go.mod:
https://github.com/k3s-io/k3s/blob/release-1.26/go.mod
github.com/k3s-io/kine v0.10.2


add Switzerland to country selection

add Switzerland to country selection and document Swiss cantons as regions
CATEGORY
Choose one

[ ] Bug Fix
[x] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[x] Documentation

SUMMARY
Add Switzerland to the documentation and to the country map drop-down menu
requires: apache-superset/superset-ui-plugins#260
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

Go to the charts list
Click on the "Birth in France by department in 2016" link
under "Options" in the "Country Name" drop-down menu, select "Switzerland"

Expected
The borders of the cantons of switzerland should appear in pale gray.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS

Codecov Report

Merging #8592 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #8592   +/-   ##
======================================
  Coverage    66.5%   66.5%
======================================
  Files         450     450
  Lines       23120   23120
  Branches     2453    2453
======================================
  Hits        15376   15376
  Misses       7595    7595
  Partials      149     149

Impacted Files
Coverage Δ

superset/assets/src/explore/controls.jsx
42.18% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Move stats to impl.stats, change some visibility.

Will remove StatsContextFactory, Tag, TagKey, TagValue under stats package, and use new APIs in tags package in the next PR.

Codecov Report

Merging #510 into master will not change coverage.
The diff coverage is 100%.

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

@bogdandrutu tags impl has already been moved to impl/tags: https://github.com/census-instrumentation/opencensus-java/tree/master/core_impl/src/main/java/io/opencensus. This PR is meant to move stats impl package to the same location with tags.

It will be incompatible with Trace so @dinooliva can you make a call if that is acceptable?

Rebased against mainline.

Trace changed to the same implementation so it is fine to merge this PR.

Got it. Rebased again... should be ready to merge now.

Thanks!


Remove Scala compiler from libraryDependencies

I cannot use sbt-heroku in Scala 3 project due to this error:[info] [error] sbt.librarymanagement.ResolveException: Error downloading org.scala-lang:scala-compiler:3.0.1
[info] [error]   Not found
[info] [error]   Not found
[info] [error]   not found: /Users/yyu/.ivy2/local/org.scala-lang/scala-compiler/3.0.1/ivys/ivy.xml

Actually I didn't know why scala-compiler had been added to libraryDependencies 🤔
I add Scala 3 + akka-http test
Work around:

https://github.com/y-yu/kindle-clock/blob/4d0877076cd95bbe0d75046f0691327680fad908/build.sbt#L158-L163

How do I do to run CI? 🤔

https://github.com/heroku/sbt-heroku/commit/1bd2bbd87143ad25e8329ef38f92a2a636acc243
🤔

@Malax
Please check Circle CI setting of this repository 🙏

I will remove akka dependencies in test due to the license change: https://github.com/akka/akka/pull/31561 .

Closing this PR because this repository will be archived. See https://github.com/heroku/heroku-jvm-application-deployer for an alternative CLI to deploy locally compiled Scala applications.


Extract validators

The library contains a list of input validators (e.g. validate period end after start, SSIN checksum, ...).
Smals uses another library for validation, based on Bean Validation annotations: https://www.ict-reuse.be/nl/service/smalsutils-validation . These annotations are added to the generated code by adding "x-[...]-extra-annotation" properties in the OpenAPI document.
I suggest to:

define a standard way how input validation errors can be propagated in a way the rest-problem-java library can handle them
extract validators out of the rest-problem-java library
(optional) refactor/improve a common validation library

OK to extract to belgif-rest-problem-validator maven module within the same repo for now?

I'd prefer to move it out of the repo before we're starting to use the library to avoid developers using it already and then having to support it. Until then, it can remain in and we can ignore it during testing.

The RequestValidator overlaps with this subset of the Smals validation library:

SSIN
enteprise number
establishment unit number
incomplete date

The RequestValidator additionally implements these cross-parameter validations:

period
exactlyOneOf
anyOf
zeroOrAllOf
zeroOrExactlyOneOf
equal
nullOrEqual

and these dynamic or context-dependent validations:

refData
reject
require
range
minimum
maximum

At first sight, cross-parameter validations and dynamic or context-dependent validations seem not well suited for the Smals validator approach with x-extra-annotation? I think both libraries could coexist.
In any case, we can initially extract the RequestValidator to a separate belgif-rest-problem-validator module within the repo.

OK, will need some more analysis which can be done later. Maybe both programmatic and declarative (annotation) validations can be combined in a single library.
Period validation could be doable with an annotation if a schema of time-v1 is used, but probably not for query params.


Metrictype -- appallingly incomplete documentation

Type of issue
Typo
Description
None of the arguments are explained. No example usage. I'm trying to dig down from https://learn.microsoft.com/en-us/python/api/azure-mgmt-consumption/azure.mgmt.consumption.operations.usagedetailsoperations?view=azure-python to work out how to get the parameters I need, Metrictype appears to be the only option, but the drill down to this page is completely useless.
Page URL
https://learn.microsoft.com/en-us/python/api/azure-mgmt-consumption/azure.mgmt.consumption.models.metrictype?view=azure-python
Content source URL
https://github.com/MicrosoftDocs/azure-docs-sdk-python/blob/main/docs-ref-autogen/azure-mgmt-consumption/azure.mgmt.consumption.models.Metrictype.yml
Document Version Independent Id
a167a816-7f9b-ff42-c4b3-d3c1e233087b
Article author
@lmazuel
Metadata

ID: 89187bc8-1b55-1ae1-fc17-616f2ba00336
Service: consumption

Thanks for the feedback, we’ll investigate asap.

FYI @rohit-ganguly
Looks like enum descriptions don't get included in the MS Learn docs: https://learn.microsoft.com/en-us/python/api/azure-mgmt-consumption/azure.mgmt.consumption.models.metrictype?view=azure-python
Github.io docs do include the generated descriptions: https://azuresdkdocs.blob.core.windows.net/$web/python/azure-mgmt-consumption/10.0.0/azure.mgmt.consumption.models.html#azure.mgmt.consumption.models.Metrictype

Including enum descriptions is a feature request I can get tracked on the Learn docs generation side, but it doesn't sound like that's the actual feedback here, and while that would be an improvement overall, in this particular case the descriptions don't shed any light anyway.
Does >None of the arguments are explained refer to this?

That is indeed a weird look. At first I had no idea why those args were there, then I recognized them as the arguments you can give the Enum constructor when you're defining an Enum functional-style. I'm not sure why the docs generation process ends up putting those there or if they're present for all Python enums on Learn, but I do see that on the Github.io docs, some enums them and some don't, and I'm not sure why. For example, the doc you linked for this particular enum doesn't have them, but for these enums in azure.mgmt.wev.v2021_01_15 they do.
Does anyone have any insight here?

@nickwalkmsft enum value doc is infered from the original spec (Swagger or TypeSpec). So it all come back to the spec author. For instance for the link you share where it's not there:
https://github.com/Azure/azure-rest-api-specs/blob/981a44d26823fc6056b30fc1008c23d25beb5aff/specification/web/resource-manager/Microsoft.Web/stable/2018-02-01/Provider.json#L28-L37
And for the doc where they are here:
https://github.com/Azure/azure-rest-api-specs/blob/981a44d26823fc6056b30fc1008c23d25beb5aff/specification/consumption/resource-manager/Microsoft.Consumption/stable/2019-05-01/consumption.json#L3250-L3273
So I agree with @kristapratico assessment that the feedback here is the lack doc for the enum. But it does assume indeed that the initial spec author did the right thing. And in his particular case, it happens it was available and it got lost in processing.


add function to return locales

Hi Chris, i needed a function to return the list of the locales, does this help Linguist in general?
cheers

This is nice <3 <3 <3


Button View in Your space

Good morning, I have a problem, when I want to open the 3d model for AR the view in your space button does not appear.
Does anyone know what happened?
Browser Affected

[ x] Chrome, version: xx.x.xxxx.xx
[ ] Edge
[ ] Firefox
[ ] IE
[ ] Safari

OS

[x ] Android
[ ] iOS
[ ] Linux
[ ] MacOS
[ ] Windows

AR

[ ] WebXR
[ ] SceneViewer
[ ] QuickLook

I think you forgot to fill out the rest of the issue template. I have absolutely no idea what you mean, and no way to reproduce the behavior. Can you give details please?

Closing as no repro.