LACNIC related IP address raise an exception

when querying (using lookup_rdap) an IP that is registered under the LACNIC RIR, it raises an HTTPLookupError exception.
input examples that fail:
<IP_ADDRESS>
<IP_ADDRESS>
Traceback:
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1317, in do_open
encode_chunked=req.has_header('Transfer-encoding'))
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1229, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1275, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1224, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1016, in _send_output
self.send(msg)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 956, in send
self.connect()
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1392, in connect
server_hostname=server_hostname)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 412, in wrap_socket
session=session
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 853, in _create
self.do_handshake()
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 1117, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1051)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/amir/code/mydro/saucepan/env/lib/python3.7/site-packages/ipwhois/net.py", line 706, in get_http_json
data = self.opener.open(conn, timeout=self.timeout)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 531, in open
response = meth(req, response)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 641, in http_response
'http', request, response, code, msg, hdrs)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 563, in error
result = self._call_chain(*args)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 755, in http_error_302
return self.parent.open(new, timeout=req.timeout)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 525, in open
response = self._open(req, data)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 543, in _open
'_open', req)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1360, in https_open
context=self._context, check_hostname=self._check_hostname)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1319, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1051)>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1317, in do_open
encode_chunked=req.has_header('Transfer-encoding'))
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1229, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1275, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1224, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1016, in _send_output
self.send(msg)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 956, in send
self.connect()
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1392, in connect
server_hostname=server_hostname)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 412, in wrap_socket
session=session
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 853, in _create
self.do_handshake()
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 1117, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1051)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/amir/code/mydro/saucepan/env/lib/python3.7/site-packages/ipwhois/net.py", line 706, in get_http_json
data = self.opener.open(conn, timeout=self.timeout)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 531, in open
response = meth(req, response)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 641, in http_response
'http', request, response, code, msg, hdrs)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 563, in error
result = self._call_chain(*args)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 755, in http_error_302
return self.parent.open(new, timeout=req.timeout)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 525, in open
response = self._open(req, data)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 543, in _open
'_open', req)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1360, in https_open
context=self._context, check_hostname=self._check_hostname)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1319, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1051)>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1317, in do_open
encode_chunked=req.has_header('Transfer-encoding'))
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1229, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1275, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1224, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1016, in _send_output
self.send(msg)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 956, in send
self.connect()
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1392, in connect
server_hostname=server_hostname)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 412, in wrap_socket
session=session
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 853, in _create
self.do_handshake()
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 1117, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1051)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/amir/code/mydro/saucepan/env/lib/python3.7/site-packages/ipwhois/net.py", line 706, in get_http_json
data = self.opener.open(conn, timeout=self.timeout)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 531, in open
response = meth(req, response)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 641, in http_response
'http', request, response, code, msg, hdrs)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 563, in error
result = self._call_chain(*args)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 755, in http_error_302
return self.parent.open(new, timeout=req.timeout)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 525, in open
response = self._open(req, data)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 543, in _open
'_open', req)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1360, in https_open
context=self._context, check_hostname=self._check_hostname)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1319, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1051)>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1317, in do_open
encode_chunked=req.has_header('Transfer-encoding'))
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1229, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1275, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1224, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1016, in _send_output
self.send(msg)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 956, in send
self.connect()
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/http/client.py", line 1392, in connect
server_hostname=server_hostname)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 412, in wrap_socket
session=session
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 853, in _create
self.do_handshake()
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ssl.py", line 1117, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1051)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/amir/code/mydro/saucepan/env/lib/python3.7/site-packages/ipwhois/net.py", line 706, in get_http_json
data = self.opener.open(conn, timeout=self.timeout)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 531, in open
response = meth(req, response)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 641, in http_response
'http', request, response, code, msg, hdrs)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 563, in error
result = self._call_chain(*args)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 755, in http_error_302
return self.parent.open(new, timeout=req.timeout)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 525, in open
response = self._open(req, data)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 543, in _open
'_open', req)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1360, in https_open
context=self._context, check_hostname=self._check_hostname)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/urllib/request.py", line 1319, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1051)>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/amir/code/mydro/saucepan/saucepan/utils/ip_check_lib.py", line 45, in get_basic_registration_data
results = ip_whois.lookup_rdap(depth=1)  # returns RIR data
File "/Users/amir/code/mydro/saucepan/env/lib/python3.7/site-packages/ipwhois/ipwhois.py", line 321, in lookup_rdap
rate_limit_timeout=rate_limit_timeout
File "/Users/amir/code/mydro/saucepan/env/lib/python3.7/site-packages/ipwhois/rdap.py", line 771, in lookup
rate_limit_timeout=rate_limit_timeout
File "/Users/amir/code/mydro/saucepan/env/lib/python3.7/site-packages/ipwhois/net.py", line 788, in get_http_json
rate_limit_timeout=rate_limit_timeout, headers=headers
File "/Users/amir/code/mydro/saucepan/env/lib/python3.7/site-packages/ipwhois/net.py", line 788, in get_http_json
rate_limit_timeout=rate_limit_timeout, headers=headers
File "/Users/amir/code/mydro/saucepan/env/lib/python3.7/site-packages/ipwhois/net.py", line 788, in get_http_json
rate_limit_timeout=rate_limit_timeout, headers=headers
File "/Users/amir/code/mydro/saucepan/env/lib/python3.7/site-packages/ipwhois/net.py", line 794, in get_http_json
url))
ipwhois.exceptions.HTTPLookupError: HTTP lookup failed for http://rdap.lacnic.net/rdap/ip/<IP_ADDRESS>.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/init.py", line 1034, in emit
msg = self.format(record)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/init.py", line 880, in format
return fmt.format(record)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/init.py", line 619, in format
record.message = record.getMessage()
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/init.py", line 380, in getMessage
msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
File "/Users/amir/code/mydro/saucepan/saucepan/utils/ip_check_lib.py", line 276, in
x.get_basic_registration_data()
File "/Users/amir/code/mydro/saucepan/saucepan/utils/ip_check_lib.py", line 62, in get_basic_registration_data
logging.warning('failed to query RIR DB for ip registration', e)
Message: 'failed to query RIR DB for ip registration'
Arguments: (HTTPLookupError('HTTP lookup failed for http://rdap.lacnic.net/rdap/ip/<IP_ADDRESS>.'),)

@kessler2 Any update? Were you able to try the steps @6d6178 described?

Closing due to inactivity and failure to reproduce. If anyone has this same issue, I will reopen.


Is it possible to install this extension to Chrome from source code directly?

I just found the extension disappeared from my chrome. I came here and noticed the announcement. I really like this extension for my daily leetcode practices. I'm wondering if it's possible to install it on my chrome from source code directly?
Really appreciate your contribution and totally understand your time limitation.
Thanks first. :)

Thank you for loving my extension. The answer of your question is YES. You can import extension code by enable chrome developer mode in chrome://extensions, and click "load unpacked  extension", load leetcode-ext folder


zio2 RC6

migration to ZIO2 RC6

Is this released somewhere @justcoon ?

@Fristi , probably not
@toxicafunk can you release this version?

Should be released now. Sorry for the delay.

At which repository has this been published?

There was an error at the publishing step, but its fixed now!
coursier fetch dev.zio::zio-metrics-prometheus:2.0.0-RC6
https://repo1.maven.org/maven2/dev/zio/zio-metrics-prometheus_2.13/2.0.0-RC6/zio-metrics-prometheus_2.…
  100.0% [##########] 3.7 KiB (7.3 KiB / s)
https://repo1.maven.org/maven2/io/prometheus/simpleclient/0.12.0/simpleclient-0.12.0.pom
  100.0% [##########] 1.9 KiB (26.6 KiB / s)


Set minimum range

Is there a way to define a minimum range? Preventing the user from selecting a smaller range than what is configured?

Nope, It is not possible to configure a range once Rangebar is created and then dynamically bound the user within that range

Actually it is possible please check my other answer: https://github.com/oli107/material-range-bar/issues/172#issuecomment-535051056


Support handling of the server rate limits

As per title, this PR adds support for handling the rate limits when sending events to the Sentry server. There are obvious limitations of this implementation due to the fact that the status of the rate limits does not persist across handling multiple server requests, but at least within the lifecycle of a single request issues like keeping flooding the server should now be avoided

thanks for this @ste93cry ! 🚀


Modifying the dbname (mysql) fails.

Post a successful provisioning of a MySQL DB, if the db name is modified on a running system the new DB is not provisioned.
Modifying the db name back to the original does not cause the system to reestablish a working connection to the existing DB.
Steps (local dev):

Establish initial DB func (MyDbConfig) Name() string { return "testdb" }
Insert/Query works
Rename func (MyDbConfig) Name() string { return "testdb2" }
Insert/Query fails
Rename back func (MyDbConfig) Name() string { return "testdb" }
Insert/Query fails call to verb mysql.query failed: failed to get database "testdb": database testdb does not match expected type of mysql

@bradleydwyer I can not reproduce this in the latest main. Could you verify if it has been fixed in some of the recent refactorings?

I don't see this on latest either. Will close.


Which Zig version is used?

0.13. Typically the latest released. Obviously might me some small lag in support after a new release

@mitchellh Thanks, Unfortunate I used Zig master for my project


Missing method (?) - Get Followed Artists

Hi
There is a method that I cannot seem to find in the SpotifyAPI-NET which I need in a project. The method is Get Followed Artists method (https://developer.spotify.com/documentation/web-api/reference/follow/get-followed/). Is it missing or is it just me having problems finding it?
Regards
/scream4me

https://github.com/JohnnyCrazy/SpotifyAPI-NET/blob/f4b3e9fe401b4979a1e6af8635dad9e0b87dfaf8/SpotifyAPI.Web/SpotifyWebAPI.cs#L621-L634

Hi
Thanks for your quick reply. As I thought, it was there but I missed it. I was looking at the docs at https://johnnycrazy.github.io/SpotifyAPI-NET/web/follow.html and didn't see it.
Keep up the good work with SpotifyAPI-NET!
/scream4me

Ah, yea, it's missing there. Gonna add it, thanks :)


"Dâmbureni", "Durăști" are listed in the drop-down menu

Description:
When user writes "Dâmbureni" and "Durăști" the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Dâmbureni"

Expected results
The location appears in the drop-down menu as "Dâmbureni, Alba (Bistra)"

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Durăști"

Expected results
The location appears in the drop-down menu as "Durăști, Alba (Bistra)"


Misleading error in case of duplicated dependency in pyproject.toml

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
git clone https://gist.github.com/traversaro/5a3ce5afe0eb4eb7e5474582273fa624 piximwe
cd piximwe
pixi run start

this results in the error:
traversaro@IITBMP014LW012:~/piximwe$ pixi run start
  × could not find pixi.toml or pyproject.toml which is configured to use pixi

however, pyproject.toml is configured to use pixi, simply there is the error in the metadata (in particular there is a duplicated dependency). If instead one does pixi init ., there is a much more descriptive error:
traversaro@IITBMP014LW012:~/piximwe$ pixi init .
  × failed to parse project manifest
    ╭─[pyproject.toml:14:1]
 13 │ numpy = "*"
 14 │ numpy = "*"
    · ┬
    · ╰── duplicate key `numpy` in table `tool.pixi.dependencies`
 15 │
    ╰────

Issue description
See reproducible example.
Expected behavior
It would be great to have a more descriptive error if a dependency is duplicated.

Problem found by @flferretti

The problem is not present if pixi.toml is used, for example with:
[project]
name = "piximws"
version = "0.1.0"
description = "Add a short description here"
authors = ["Silvio Traversaro<EMAIL_ADDRESS>channels = ["conda-forge"]
platforms = ["linux-64"]

[tasks]
start = "echo"

[dependencies]
numpy = "*"
numpy = "*"

pixi run start results in a clear error:
traversaro@IITBMP014LW012:~/piximws$ pixi run start
  × failed to parse project manifest
    ╭─[pixi.toml:14:1]
 13 │ numpy = "*"
 14 │ numpy = "*"
    · ┬
    · ╰── duplicate key `numpy` in table `dependencies`
    ╰────

Yes, this seems like this could use an improvement for sure!

That is an interesting one.
This is a toml error, so would you expect pixi to always report toml errors of pyproject.toml? Even if it is not used as a pixi manifest?
E.g. this will give you the same result:
[project]
name = "my_project"
requires-python = ">=3.9" # <<<
requires-python = ">=3.9" # <<<
dependencies = [
    "numpy",
]

[tool.pixi.project]
channels = ["conda-forge"]
platforms = ["linux-64", "osx-arm64", "osx-64", "win-64"]

As in, it will not be read as a valid toml file so pixi skips it as a viable option currently.

Duplicate of https://github.com/prefix-dev/pixi/issues/1777


[SPARK-13761] [ML] Remove remaining uses of validateParams

What changes were proposed in this pull request?
Cleanups from [https://github.com/apache/spark/pull/11620]: remove remaining uses of validateParams, and put functionality into transformSchema
How was this patch tested?
Existing unit tests, modified to check using transformSchema instead of validateParams

CC: @hhbyyh Could you please take a look at this? Thanks!

Test build #53447 has started for PR 11790 at commit 3f02142.

Looks good.

Test build #53447 has finished for PR 11790 at commit 3f02142.

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

Merged build finished. Test PASSed.

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

@hhbyyh Thanks for reviewing it!  I'll merge it with master


CORS file headers are absent

The CORS header configuration is absent and prevents files accessed using CORS. A simple fix for this is to add the following to the api_site settings.py file:
CORS_ALLOW_HEADERS = [     'accept',     'accept-encoding',     'authorization',     'content-type',     'content-disposition',     'dnt',     'origin',     'user-agent',     'x-csrftoken',     'x-requested-with', ]
The headers specified are all of the defaults found here and the addition of the "content-disposition" header item is what makes the file access work with CORS.

This was tested working for commit #3e3ee37 but seems to break for the latest commit #93dcfe6. I am not sure where the break occurs.


1.0a2 release

With -n and -r and area calculation.

This was done! https://github.com/planetlabs/fio-planet/releases/tag/1.0a2


changed file name for windows compatibility

fixes #52

Thank you very much for fixing this issue, @ruisebastiao! 👍


Fix some phpdoc

Q
A

Type
improvement

BC Break
no

Fixed issues

Summary

Raising psalm level locally and analyzing tests directory made some issues appear:
ReplaceRoot allowing Expr:
https://github.com/doctrine/mongodb-odm/blob/f225a0cfc5ba878aba3e32b7f5fd70facc2d4eee/tests/Doctrine/ODM/MongoDB/Tests/Aggregation/Stage/ReplaceRootTest.php#L45-L49
Bucket::groupBy allowing string:
https://github.com/doctrine/mongodb-odm/blob/f225a0cfc5ba878aba3e32b7f5fd70facc2d4eee/tests/Doctrine/ODM/MongoDB/Tests/Aggregation/Stage/BucketTest.php#L20-L22
With ClassMetadata I was getting:
ERROR: InvalidArgument - tests/Doctrine/ODM/MongoDB/Tests/QueryTest.php:418:30 - Argument 2 of Doctrine\ODM\MongoDB\Query\Query::__construct expects Doctrine\ODM\MongoDB\Mapping\ClassMetadata<object>, Doctrine\ODM\MongoDB\Mapping\ClassMetadata<Documents\User> provided (see https://psalm.dev/004)
        new Query($this->dm, new ClassMetadata(User::class), $this->getMockCollection(), ['type' => -1], []);

Making it covariant I think it makes sense as it is in doctrine/persistence.

Thanks @franmomu!


Simplify and refactor SQLTokenGenerator

For #3139.

Pull Request Test Coverage Report for Build 470

242 of 265 (91.32%)  changed or added relevant lines in 30 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 65.797%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/encrypt/EncryptConditionEngine.java
4
5
80.0%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/SQLRewriteEngine.java
47
50
94.0%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/token/generator/collection/impl/TableTokenGenerator.java
5
10
50.0%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/token/generator/optional/impl/InsertEncryptColumnFromMetadataTokenGenerator.java
15
29
51.72%

Totals

Change from base Build 425:
0.02%

Covered Lines:
9759

Relevant Lines:
14832

💛  - Coveralls


fix: 3387 - energy and energyKJ confusion fix

Impacted file:

nutrition_page_loaded.dart: forces energy as energyKJ

What

Depending on the country, the order and the list of nutrients vary.
There is a bit of confusion as for historical reasons, we have both energy (in KJ) and energyKJ (erm... in KJ) in off, but in off-dart we only have energyKJ (or the other way around)
At least for Canada, there's no energyKJ, only energy, that should match with energyKJ but does not.
Should probably be rather fixed in off-dart; here it's only a quick fix for Smoothie.

Fixes bug(s)

Fixes: #3387
Fixes: #3397
Fixes: #3398
Fixes SMOOTHIE-1G9
Fixes SMOOTHIE-1GA

Thank you @M123-dev for the review!
I don't know how much you can consider that "a good catch" as it's a bug I probably created...


Spawn Issue

Describe the bug
The time you first spawn in the world, every grass and branch in the spawn area breaks resulting in a lot of dropped seeds and sticks which causes quite some lag
Expected behavior
Grass and branches shouldnt when loading in
Screenshots

Note: I believe this is happening because the spawn village spawns in and while replacing the previous land it breaks the grass.

i added something that will detect the mass amount of things dropped and remove them but also I will be trying to fix this

Will be fixed when ported to neoforge but it's basically fixed rn

gonna try to fix this in the upcoming api

will be fixed in our api 1.0.0 v 1.21.1


How can I access PDFViewerApplication?

I installed pdf.js in my web application using webpack and npm to get pdfjs-dist package.
I can't find a way to access this PDFViewerApplication in the fashion that it says in this FAQ answer

Checking out the files I could see that App.js exports this function, but I get an error when I try to import it directly. But so none of the exported object from 'pdfjs-dist' provide that.
How can I access this function?

The default viewer, i.e. the one found at https://mozilla.github.io/pdf.js/web/viewer.html, is purposely not included in https://github.com/mozilla/pdfjs-dist; please refer to https://github.com/mozilla/pdf.js/issues/5609#issuecomment-68530552 and https://github.com/mozilla/pdf.js/issues/7203#issuecomment-210510569.
Please keep the following, as mentioned in e.g. https://mozilla.github.io/pdf.js/getting_started/ and https://github.com/mozilla/pdf.js/wiki/Setup-pdf.js-in-a-website, in mind:

However, we do ask if you plan to embed the viewer in your own site, that it not just be an unmodified version. Please re-skin it or build upon it.

Hence we don't want to make it too simple to use it directly. Instead there's a number of viewer components (which are also used by the default viewer) available, that can be used to create a custom viewer.
Please find examples of using the viewer components at https://github.com/mozilla/pdf.js/tree/master/examples/components, and that the necessary files for a custom viewer is already being distributed in https://github.com/mozilla/pdfjs-dist/tree/master/web (i.e. available through e.g. NPM).
Closing as answered.

Thanks for the reply, I checked out the components folder, but if I follow it I got an error since I don't have access to PDFPageView (source), which should be packaged in pdfjs-dist, right?.
I tried to require the file you told me
import { PDFViewer } from 'pdfjs-dist/web/pdf_viewer';

But that generates an error
ReferenceError: document is not defined at Object.defineProperty.value (/mypackage/node_modules/pdfjs-dist/web/webpack:/external/webL10n/l10n.js:34:1)

Since the various viewer components are (currently) added to the global PDFJS object, I'm assuming that simply doing import 'pdfjs-dist/web/pdf_viewer'; should work directly with the e.g. the pageviewer example. Is that not the case?
Or, you could probably do something like import { PDFJSViewer } from pdfjs-dist/web/pdf_viewer; and use PDFJSViewer.PDFPageView (in place of PDFJS.PDFPageView in the example).
However, without a complete (runnable) example, as mentioned in e.g. https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md, it's very difficult (or even impossible) to tell what might be wrong.

Hi @JRigotti ,
Have you got any solution for your problem?
I'm also facing the same issue.
thanks in advance!!

@RaviGprec no, I gave up and started importing the pdf.js script through a <script> tag

Hi @JRigotti ,
Have you tried anything?

I don't think so, as far as I know pdf.js only supports .pdf files and base64 encoded strings

feeding PDF content means, I'll give pdf to viewer.js in uint8array format. This uint8array data is coming from server.  So will that work fine?
viewer.js is taking DEFUALT_URL (file path). I want to give uint8array instead of default_url (as my files are coming from server as arraybuffer format and are  being converted uint8array format.)
Thanks in advance!!
Regards,
Ravi Kumar

@JRigotti, I Solved the .pdf isseu on my webserver by rerouting "*.pdf" extensions to a Mvc controller in an ASP.NET web app to return FileResult(byte[], contentType) which works well to load pdfs out of Azure blob storage

I have wrote a post introduced works codes about "How to get and learn PDFViewerApplication from PDF.js“, you can view that post, this is my post URL https://www.libertynlp.com/index.php/2022/06/02/how-to-get-and-learn-pdfviewerapplication-from-pdfjs/


HOSTEDCP-1328: Add Ability to Encrypt VM OS Disks

What this PR does / why we need it:
Adds the ability to encrypt the OS disks in the Azure VMs, using a DiskEncryptionSet resource. The DiskEncryptionSet ID can be passed in when creating a new Hosted Cluster or creating a new NodePool.

Note: this PR is also enabling encryption at host in addition to the server side encryption through the DiskEncryptionSet. See this link for more details.

Which issue(s) this PR fixes:
Fixes HOSTEDCP-1328
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[x] This change includes docs.
[ ] This change includes unit tests.

/test verify
/test unit
/test images

/test verify
/test unit
/test images

/test verify
/test images
/test unit

/lgtm

Just for reference - I added upstream documentation as part of the work for this PR here.

/test e2e-kubevirt-aws-ovn


refactor: Find and fix vulnerable dependencies

Use this link to re-run the recipe: https://app.moderne.io/recipes/org.openrewrite.java.dependencies.DependencyVulnerabilityCheck?organizationId=RklOT1M%3D

This was not producing a clean CVE scan despite the overrides.


feat: add support Application Default Credentials for google-cloud-storage

Tihs PR adds setting to use Application Default Credentials for authentication of google-cloud-storage.
reference:

https://cloud.google.com/docs/authentication/application-default-credentials
https://googleapis.dev/nodejs/storage/latest/Storage.html#Storage-examples

Alternatively we could use ADC if no clientEmail || privateKey` are provided?

Alternatively we could use ADC if no clientEmail || privateKey are provided?

Would you mind elaborating? I am not an expert when it comes to GCP.

Would you mind elaborating? I am not an expert when it comes to GCP.

From docs:

ADC searches for credentials in the following locations:
GOOGLE_APPLICATION_CREDENTIALS environment variable
User credentials set up with the Google Cloud CLI
The attached service account, as provided by the metadata server

By simply not providing credentials to Storage() constructor we instruct it to use one of the above three methods. The 2nd and 3rd scenarios are most common in my experience - SDK knows where to find local credentials, and it will also check the GCP metadata server for the Service Account information (this is used for Workload Identity auth in GKE - the recommended way to authenticate with GCP. Very similar to AWS's IAM roles for service accounts/IRSA)

@all-contributors add @nakatanakatana for code

This PR was superseded by https://github.com/ducktors/turborepo-remote-cache/pull/68


Mention the included SwiftCheck dependency in Readme.md

SwiftCheck is brilliant. Congratulations!
I discovered it, almost by accident, and it's just what the doctor ordered :+1:
regards,
Daniel

I've been meaning to do something more general than that and create a repository that serves as a "master README" with brief summaries of each framework and a TypeLift-specific bug tracker/bulletin board.

@CodaFi is there a slack.com team or other live venue for discussing typelift's frameworks? Or do you prefer working through github?

We haven't set anything up yet, so no.  For now it's all GH and Twitter.

an alternative to a bespoke slack team, which only take 2 mins to set, would be:
https://functionalprogramming.slack.com/messages/swift/

https://typelift.slack.com is available :)

Taken!

Yikes. My checking whether it was free obviously was a bad move. I've still got the web page open. Should I close the web page? (and we'll cross our fingers :)
Or should I proceed and transfer ownership?

I probably should have been more specific: I just signed up and took it myself.

Brill! Well done.
Think I'll get myself an invite :)

from slack.com:

Allowing email signup
If email signup is enabled for your team, new members will be able to create an account on their own.
Team Owners can manage this option under Team Sign Up Mode on the Team Settings page.

I know.  I wish slack would allow public domains, so it's invite only unles you have another suggestion (I'm not entirely familiar with how this works anyways).

pretty simple. You enable email signup from Team Settings page and then you'll get a email from slack when a user sign's up.

Which domains?

typelift.slack.com, if I understand your question...

@CodaFi Signing myself up now…

Then it may just be best to stick to GH for now.  We're not big enough as an organization to warrant a full-scale chat yet.  Just open issues and we'll chat in there.

If you want an invite just shoot me an email (devteam DOT codafi over in gmail land).

looks like this hack is the solution:
https://github.com/outsideris/slack-invite-automation
@CodaFi email sent. let me know if it doesn't get through.

Closing this due to lack of action.
Thank you for raising the issue.  Hopefully we'll become big enough one day to warrant this kind of thing.


Refactorings

See commits for the list of changes. Probably easiest to review them one by one 😬

I have some problems understanding what the deleted files (in commits all: remove redux and styles: extract text styles, use norddruck font) were for. Why aren't they needed anymore?

Well, they were responsible for the "real app" workflow. But we have to rewrite that anyway, so I removed it for now. If we need some stuff, git has a backup.

Ok then, thanks for refactoring!

Thanks for reviewing :)


Cocoapods v1.8.0 fix

Fixed issue where wrong source was used. In Cocoapods v1.8.0
Updated version to v1.0.4
Updated gemspec to bundler v2.0.2
Added Gemfile.lock

@feldan eyalbe4 take a look, please

Please someone merge!
We're bumping into https://github.com/jfrog/cocoapods-art/issues/33

Please merge this. I can't use Cocoapods v1.8.1

This is blocking me from using cocoapods v1.8.1 also

We will review and release this one soon.
Thank you @Tripwire999!

This is a blocker for me too. Please merge.

@Tripwire999,
Thank you for creating this PR!
Can you please join our contributors community by signing JFrog's CLA so that we can merge your code?

@eyalbe4 I checked the document you send through the link but i'm not interested in joining the JFrog contributers community especially if it requires me signing a legal contract.

@Tripwire999,
We are not allowed to accept code contributions without having the contributor sign the CLA.

yeowzers
Strangulation by red-tape!
@eyalbe4 How about if @Tripwire999 says "I hereby donate this code to the universe."
Then you would be able to create your own identical branch and merge that.
i.e. YOU become the contributor (and @Tripwire999 contributes to YOUR contribution, not to cocoapods-art repo directly).
@Tripwire999 would you be okay with this...?

@p-i- Sure :) I don't mind! But I won't sign a contract for a few lines of code I added.
"I hereby donate this code to the universe."

@Tripwire999 thanks for your donating your code! I took and created #37, as we need this to be fixed for our project

@torfinnberset Cool :)


Connecting i2c to EDA/ECL

Hi niru-5
Thank you for working on this library! It has made working on my project much easier.
Just wanted to double check if there is a need to connect ECA/ECL lines on the MPU9250 to the SCL/SDA of my RPI as that contains information of the magnetometer? I've seen some other tutorials that requires us to do this but in the README it doesn't say that.
Found this from here: https://makersportal.com/blog/2019/11/11/raspberry-pi-python-accelerometer-gyroscope-magnetometer

Hi,
As far as I understand, EDA/ECL lines are for including mag in the I2C communication as well. However, the library does this through the MPU, so I don't see the need to include EDA/ECL lines.
Thank You
Niru

Sounds good! Thanks!


find a bug for tensorflow\cc\framework\gradients.cc

size_t dx_index = 0;
for (const Edge* e : n->in_edges()) {
if (e->IsControlEdge()) continue;
if (dx_index == dx.size()) {
return errors::Internal(
"Invalid gradient output index: ", dx_index, " size: ", dx.size());
}
TF_RETURN_IF_ERROR(
BackpropAlongEdge(dx[dx_index++], {e->src(), e->src_output()}));
}
above code,  when   dx have different  in_edges() order. Edge is unsortd set, dx is vector

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

It has been 15 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 30 days with no activity and the awaiting response label was assigned. Is this still an issue?

We are closing this issue for now due to lack of activity. Please comment if this is still an issue for you. Thanks!


Help command doesn't subclass HelpCommand

Description

Lancebot's current help command doesn't subclass HelpCommand, unlike Python's. The former should be changed to match the latter because subclassing HelpCommand is the preferred way of creating custom help commands.
Reasoning

This wouldn't change anything for the end user, but internally, the bot will be able to do things like ctx.send_help(ctx.command)
Proposed Implementation

Replace Lancebot's help command with Python's new help command.
Additional Details

I think we should also consider moving the help command to bot-core instead because it is common functionality for all bots.
Would you like to implement this yourself?

[x] I'd like to implement this feature myself
[ ] Anyone can implement this feature

This comment also mentions that changes to Python's help command should also be applied here, but the changes in python-discord/bot#519 (which refactored Python's help command to subclass HelpCommand) hasn't made it to Lancebot yet.

Isn't the real solution here having an integrated HelpCommand in bot-core that the two bots both use? Since I imagine the logic is extremely similar, if not the exact same across the two bots. This is part of python-discord/bot-core#85. So I guess that's the real solution to this issue.

It's not a good idea have the same logic in two (or more) places, why don't move the logic to a common place? like a module?

Sorry, I didn't  read your comment @TizzySaurus well.  Yes, that is better.

Duplicate of https://github.com/python-discord/sir-lancebot/issues/470


There is a problem with nodemon

I developed a project on top of this, and a few months ago I started having this problem. For a while I though it was a bug on my end, but after downloading a fresh clone of this project it seems I can replicate the bug. Here is the output of running docker-compose up on the first example, 01-express-nodemon:

Starting 01expressnodemon_web_1 ...
Starting 01expressnodemon_web_1 ... done
Attaching to 01expressnodemon_web_1
web_1  |
web_1  | ><EMAIL_ADDRESS>start /src
web_1  | > nodemon -L app/bin/www
web_1  |
web_1  |
web_1  | /usr/local/lib/node_modules/nodemon/node_modules/update-notifier/index.js:2
web_1  | const spawn = require('child_process').spawn;
web_1  | ^^^^^
web_1  | SyntaxError: Use of const in strict mode.
web_1  |     at Module._compile (module.js:439:25)
web_1  |     at Object.Module._extensions..js (module.js:474:10)
web_1  |     at Module.load (module.js:356:32)
web_1  |     at Function.Module._load (module.js:312:12)
web_1  |     at Module.require (module.js:364:17)
web_1  |     at require (module.js:380:17)
web_1  |     at Object. (/usr/local/lib/node_modules/nodemon/bin/nodemon.js:15:1)
web_1  |     at Module._compile (module.js:456:26)
web_1  |     at Object.Module._extensions..js (module.js:474:10)
web_1  |     at Module.load (module.js:356:32)
web_1  |
web_1  | npm ERR! Linux 4.10.0-33-generic
web_1  | npm ERR! argv "node" "/usr/local/bin/npm" "start"
web_1  | npm ERR! node v0.10.38
web_1  | npm ERR! npm  v2.11.1
web_1  | npm ERR! code ELIFECYCLE
web_1  | npm ERR<EMAIL_ADDRESS>start: nodemon -L app/bin/www
web_1  | npm ERR! Exit status 8
web_1  | npm ERR!
web_1  | npm ERR! Failed at the<EMAIL_ADDRESS>start script 'nodemon -L app/bin/www'.
web_1  | npm ERR! This is most likely a problem with the app package,
web_1  | npm ERR! not with npm itself.
web_1  | npm ERR! Tell the author that this fails on your system:
web_1  | npm ERR!     nodemon -L app/bin/www
web_1  | npm ERR! You can get their info via:
web_1  | npm ERR!     npm owner ls app
web_1  | npm ERR! There is likely additional logging output above.
web_1  |
web_1  | npm ERR! Please include the following file with any support request:
web_1  | npm ERR!     /src/npm-debug.log
01expressnodemon_web_1 exited with code 1

I'm still seeing this issue

I am also seeing odd nodemon errors when attempting to run the 01-express-nodemon example in a clean install.  I've glanced over the chevdor proposals, and yes that makes the nodemon errors disappear, by not running nodemon at all.  Not really a fix (and profuse apologies if I have that wrong, I'm learning this stuff too...)
My error messages:
$   docker-compose up
Creating 01expressnodemon_web_1 ...
Creating 01expressnodemon_web_1 ... done
Attaching to 01expressnodemon_web_1
web_1  |
web_1  | ><EMAIL_ADDRESS>start /src
web_1  | > nodemon -L app/bin/www
web_1  |
web_1  |
web_1  | /usr/local/lib/node_modules/nodemon/lib/config/exec.js:159
web_1  |     .map(ext => ext.replace(/^\./, ''))
web_1  |               ^
web_1  | SyntaxError: Unexpected token >
web_1  |     at Module._compile (module.js:439:25)
web_1  |     at Object.Module._extensions..js (module.js:474:10)
web_1  |     at Module.load (module.js:356:32)
web_1  |     at Function.Module._load (module.js:312:12)
web_1  |     at Module.require (module.js:364:17)
web_1  |     at require (module.js:380:17)
web_1  |     at Object.<anonymous> (/usr/local/lib/node_modules/nodemon/lib/config/load.js:8:12)
web_1  |     at Module._compile (module.js:456:26)
web_1  |     at Object.Module._extensions..js (module.js:474:10)
web_1  |     at Module.load (module.js:356:32)

Update:  I'm continuing to play with this, and totally got it running correctly with a single line of code change.  In the file docker-compose-nodejs-examples/01-express-nodemon/Dockerfile simply change the first line from:
FROM node:0.10.38
to a more modern docker image .  I chose
FROM node:9.2.0
When I did that WITHOUT any other changes within the 01-express-nodemon repository, the code ran without errors.  Note there are other warnings, e.g. jade --> pug, but that can all be fixed.

We have modernized this project, please check if the issue still persists in the new version and re-open if necessary. Thanks for your contribution! :)


Code review is not enforced to merge into main

(I'm also assuming that the main branch is not protected if this is true)

@lisunshiny thanks for the callout. I haven't spent any time double checking the settings. I just now added a branch rule for reviews, but we should probably check all the settings. Let's discuss.


Update contracts and meta-balena

For building AGX Orin 64GB draft releases

lgtm

@balena-ci I self-certify!


Merge pull request #1 from cba85/master

Test

Please don't use this repository for your tests. Be respectful.


Attribution for Maxmind GeoIP

Per the terms of Maxmind GeoIP EULA we must provide attribution. https://www.maxmind.com/en/geolite2/eula
You must provide attribution of your use to MaxMind (an example of attribution: “This product includes GeoLite2 data created by MaxMind, available from https://www.maxmind.com“).

Fixed in master branch.


Hi, Can you please let me know how you converted the raw data on the SDD website to the format used in the code.

This would really help if you can share converted data
Thanks

I have shared the pre-processed data files for the SDD train/val/test sets. Hope this helps!

I have shared the pre-processed data files for the SDD train/val/test sets. Hope this helps!

Hello, thank you for your excellent work, I am trying to convert the data in another dataset into the format required by P2T, could you please share your preprocessing code for SDD to me? Thank you very much!

Hi, could someone help me with deploying the code? I failed many times when I tried to run the train model. I do not konw what cause the problem. I want to get the specific description or readme markdown file of the code. Thank you!


failed to load tsx files while activating support for tsx files

i am trying to add support for typescript and jsx files (tsx) in vue components (ant-design-vue) with storybook.
but getting the error in express module
TypeError: Router.use() requires a middleware function
ERR!     at Function.use (D:\RD-2.0 storybook\antwithvite\vue-tsx\node_modules\express\lib\router\index.js:457:11)
ERR!     at Object.start (D:\RD-2.0 storybook\antwithvite\vue-tsx\node_modules\storybook-builder-vite\index.js:43:12)
ERR!     at processTicksAndRejections (internal/process/task_queues.js:95:5)

if there is a workaround kindly let me know.

Please provide a minimal reproducible example.

Closing this since there's been no response.


Fix example app

@pardom
Some fixes for plumb-example.

Fix building with Android Studio
Fix crash on rotate to landscape
Fix subscription management

Good call on the subscription check. Added that, addressed formatting, gradle structure, and added the "DO NOT MODIFY" comment to the top of all generated files. :v:


Sign-in Unknown Error

NAME: InternalServerError
CODE: ER_BEFORE_DML_VALIDATION_ERROR
MESSAGE: Unknown error
level: critical
InternalServerError: Unknown error
at new InternalServerError (/var/www/ghost/versions/2.14.3/node_modules/ghost-ignition/lib/errors/index.js:77:23)
at Object.handleStoreError (/var/www/ghost/versions/2.14.3/core/server/web/shared/middlewares/api/spam-prevention.js:27:25)
at module.exports. (/var/www/ghost/versions/2.14.3/node_modules/express-brute/index.js:84:19)
at tryCatcher (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/util.js:16:23)
at Promise.errorAdapter [as _rejectionHandler0] (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/nodeify.js:35:34)
at Promise._settlePromise (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/promise.js:566:21)
at Promise._settlePromise0 (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/promise.js:690:18)
at _drainQueueStep (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/async.js:138:12)
at _drainQueue (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/async.js:131:9)
at Async._drainQueues (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/async.js:147:5)
at Immediate.Async.drainQueues (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:810:20)
at tryOnImmediate (timers.js:768:5)
at processImmediate [as _immediateCallback] (timers.js:745:5)
Error: ER_BEFORE_DML_VALIDATION_ERROR: The table does not comply with the requirements by an external plugin.
at Query.Sequence._packetToError (/var/www/ghost/versions/2.14.3/node_modules/mysql/lib/protocol/sequences/Sequence.js:47:14)
at Query.ErrorPacket (/var/www/ghost/versions/2.14.3/node_modules/mysql/lib/protocol/sequences/Query.js:77:18)
at Protocol._parsePacket (/var/www/ghost/versions/2.14.3/node_modules/mysql/lib/protocol/Protocol.js:278:23)
at Parser.write (/var/www/ghost/versions/2.14.3/node_modules/mysql/lib/protocol/Parser.js:76:12)
at Protocol.write (/var/www/ghost/versions/2.14.3/node_modules/mysql/lib/protocol/Protocol.js:38:16)
at Socket. (/var/www/ghost/versions/2.14.3/node_modules/mysql/lib/Connection.js:91:28)
at Socket. (/var/www/ghost/versions/2.14.3/node_modules/mysql/lib/Connection.js:502:10)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at TCP.onread (net.js:601:20)
--------------------
at Protocol._enqueue (/var/www/ghost/versions/2.14.3/node_modules/mysql/lib/protocol/Protocol.js:144:48)
at Connection.query (/var/www/ghost/versions/2.14.3/node_modules/mysql/lib/Connection.js:200:25)
at /var/www/ghost/versions/2.14.3/node_modules/knex/lib/dialects/mysql/index.js:161:18
at Promise._execute (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/debuggability.js:313:9)
at Promise._resolveFromExecutor (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/promise.js:483:18)
at new Promise (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/promise.js:79:10)
at Client_MySQL._query (/var/www/ghost/versions/2.14.3/node_modules/knex/lib/dialects/mysql/index.js:155:12)
at Client_MySQL.query (/var/www/ghost/versions/2.14.3/node_modules/knex/lib/client.js:206:17)
at Runner. (/var/www/ghost/versions/2.14.3/node_modules/knex/lib/runner.js:155:36)
at Runner.tryCatcher (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/util.js:16:23)
at Runner.query (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/method.js:15:34)
at /var/www/ghost/versions/2.14.3/node_modules/knex/lib/runner.js:61:21
at tryCatcher (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/util.js:16:23)
at /var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/using.js:185:26
at tryCatcher (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/var/www/ghost/versions/2.14.3/node_modules/bluebird/js/release/promise.js:512:31)

This is bug not asking for help

If you believe this is a bug, could you please include some reproducible steps so that we can determine what's causing it, and how we might fix it? :relaxed:

It's a bug. I'm running into it now and will try to isolate it.
It has to do with MySQL strict mode from what I can gather. @beraybentesen posted the fix on the Ghost Forum as being due to missing primary keys in the brute and migrations_lock tables.
My setup is unique and unsupported (Kubernetes, MySQL 8.0.11 InnoDB Cluster with MySQL Router), so I'm going to try to reproduce it in a simpler environment.

@adamelliotfields If the database is not intended to clustering, there is no problem like this. Single instance DBs work fine. I installed on single instance MySQL Server on Azure and no problem occurred. However, when I install on clustering-enabled solutions like IBM Compose, the error occurs. So I think the Ghost team must document this problem.

I confirmed your fix worked. Here are the necessary changes the Ghost team would have to make:
https://github.com/TryGhost/Ghost/blob/2.18.3/core/server/data/schema/schema.js
brute: {
+   key: {type: 'string', maxlength: 191, nullable: false, primary: true},
-   key: {type: 'string', maxlength: 191},

https://github.com/TryGhost/knex-migrator/blob/v3.2.6/lib/index.js
return self.connection.schema.createTable('migrations_lock', function (table) {
+   table.string('lock_key', 191).nullable(false).primary();
-   table.string('lock_key', 191).nullable(false).unique();

Yeah, we should document that the group replication plugin is not supported atm, because this plugin requires to have a not-nullable primary key for each table, which is not the case yet. This should be independent of running MySQL 5 or 8.
A feature request in the forum is the best place to put it for now 👍
If somebody from the community wants to work on this, it requires to write migration scripts for the target tables.


nixos/udev: allow /bin/sh in udev rules

Using /bin/sh in udev rules is fine (as it's guaranteed to point to a (bash) shell on NixOS), and actually is better than hardcoding absolute paths, at least in cases where these rules are also added to the (systemd-based) initrd (via boot.initrd.services.udev.rules).
To allow this, we need to update the check routine that assembles the list of files needing fixup, to explicitly exclude /bin/sh occurences.
To do this, we convert the pattern to a PCRE regex (which requires "/" to be escaped), and add (?!/bin/sh\b) as a negative lookahead.
This subsequently allows udev rules to (start using) /bin/sh again, so they'll work in-initrd.
To test, I edited an existing NixOS VM test, adding services.udev.packages = [ pkgs.bcache-tools ]; to its config.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[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/)
24.05 Release Notes (or backporting 23.05 and 23.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

[x] Fits CONTRIBUTING.md.

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

First commit says:

Using /bin/sh in udev rules is fine (as it's guaranteed to point to a
(bash) shell on NixOS), and actually is better than hardcoding absolute
paths, at least in cases where these rules are also added to the
(systemd-based) initrd (via boot.initrd.services.udev.rules).

Can you explain why /bin/sh is problematic for systemd-based initrd?

First commit says:

Using /bin/sh in udev rules is fine (as it's guaranteed to point to a
(bash) shell on NixOS), and actually is better than hardcoding absolute
paths, at least in cases where these rules are also added to the
(systemd-based) initrd (via boot.initrd.services.udev.rules).

Can you explain why ${bash}/bin/sh is problematic for systemd-based initrd? (EDIT: mixed up ${bash}/bin/sh vs /bin/sh.)

systemd-in-initrd doesn't copy entire store paths, but only binaries. I'm not sure if this is documented in greater detail somewhere, but it's visible in the options (and how they're set) in nixos/modules/system/boot/systemd/initrd.nix.

According to 581226cfb456b4c116594f1b79f45945703a4a4c, the /bin/sh -> ${bash}/bin/sh change in bcache-tools was needed to fix services.udev.packages = [ bcache-tools ]. Is that not true anymore?
I don't have bandwith to look into this right now. Although I look forward to a systemd initramfs, just be careful not to break the non-systemd initrd in the meantime :-)

According to 581226c, the /bin/sh -> ${bash}/bin/sh change in bcache-tools was needed to fix services.udev.packages = [ bcache-tools ]. Is that not true anymore?

Yes, this was needed because the regex in the "udev checking phase" was too strict. One of the two commits in here is relaxing it to (also) allow (only) /bin/sh.

I don't have bandwith to look into this right now. Although I look forward to a systemd initramfs, just be careful not to break the non-systemd initrd in the meantime :-)

We should have /bin/sh in the old initrd too, and the test I ran with the non-systemd initrd.

Thanks. I don't have any objections.


fix command execution in running chain commands

fix command execution in running chain commands

Thank you! I did some slight modifications and pushed to main.
https://github.com/Josh-XT/AGiXT/commit/f54297ecc47f4d66355a8037ebe0004e2b7f7f17


Integrate Mixnet with Waku network backend

In https://github.com/logos-co/nomos-node/pull/318, I’ve integrated mixnet only with libp2p backend. It should be also integrated with Waku backend.

In #318, I’ve integrated mixnet only with libp2p backend. It should be also integrated with Waku backend.

We do not need to support waku anymore for the time being. If we have everything ready in libp2p we can even ditch it.

We do not need to support waku anymore for the time being. If we have everything ready in libp2p we can even ditch it.

Good. I think our libp2p backend is 95% ready. 5% is optimization and unknown stuff :) Then, I'd say we can postpone this issue.


Refactor Style component into many smaller pieces

Note for release notes: this PR is co-authored with @Weibye <3
Objective

The Style component is monolithic and poorly named (it only controls layout). This makes it hard to work with and reason about.
Fixes #5511.
Fixes #6286.

Changelog

broke the Style UI component into many small components
added the FlexboxLayoutQuery, FlexboxLayoutQueryItem and FlexboxLayoutChanged helper types to make recomputing layouts easier

Migration Guide
Up to date as of 76557be5f80473547d0bfcb4de857d0d78f77046
The Style-component has been removed. In its place, there are several new components:

LayoutControl
FlexContainer
FlexItem
SizeConstraints
Spacing

Previous location
New location

Style.direction: Direction
:exclamation: Removed. Bevy does not currently support multiple text-directions :exclamation:

LayoutControl

Style.position_type: PositionType
LayoutControl.position: Position

Style.position: UiRect
LayoutControl.inset: Inset(UiRect)

Style.overflow: Overflow
LayoutControl.overflow: Overflow

Style.display: Display
LayoutControl.display: Display

FlexContainer

Style.flex_direction: FlexDirection
FlexContainer.direction: Direction

Style.flex_wrap: FlexWrap
FlexContainer.wrap: Wrap

Style.align_items: AlignItems
FlexContainer.align_items: AlignItems

Style.align_content: AlignContent
FlexContainer.align_content: AlignContent

Style.justify_content: JustifyContent
FlexContainer.justify_content: JustifyContent

Style.gap: Gap(UiRect)
FlexContainer.gap: Gap(UiRect)

FlexItem

Style.align_self: AlignSelf
FlexItem.align_self: AlignSelf

Style.flex_grow: f32
FlexItem.flex_grow: f32

Style.flex_shrink: f32
FlexItem.flex_shrink: f32

Style.flex_basis: Val
FlexItem.flex_basis: Val

Spacing

Style.margin: UiRect
Spacing.margin: UiRect

Style.padding: UiRect
Spacing.padding: UiRect

Style.border: UiRect
Spacing.border: UiRect

SizeConstraints

Style.size: Size
SizeConstraints.suggested: Size

Style.min_size: Size
SizeConstraints.min: Size

Style.max_size: Size
SizeConstraints.max: Size

Style.aspect_ratio: Option<f32>
SizeConstraints.aspect_ratio: Option<f32>

Queries
Any queries that previously queried all of Style should now instead use the FlexLayoutQuery.
// old
fn my_system(q: Query<&Style>) { .. }
// new
fn my_system(q: Query<FlexlayoutQuery>) { .. }

Most of the time however, you'd likely want to query for the more specific layout components you need.
Change detection
If you previously relied on detecting when something on Style changed you can now instead use the FlexLayoutChanged type.
// old
fn my_system(q: Query<.., Changed<Style>>) { .. }
// new
fn my_system(q: Query<.., Changed<FlexLayoutChanged>>) { .. }

Small related changes
Various helper methods on TextBundle have been removed for consistency with other bundles in the engine. Construct these explicitly, or use a trait extension method to redefine them if you prefer this style.

I'd suggest only migrating the ui example for now. It's complex enough to show the use of this new api without being too complex.

This should probably be done in a future PR just to not let this one grow too much, but doing this for TextStyle would probably be done too.

I'm a bit concerned that it will reduce discoverability of all the style parameters.

We can group the components under a module, so they are listed in rendered documentation.

Been thinking a bit about this recently, so here's some deeper reasoning and context:
Let's consider the use case of us implementing borders: (#3991)

We want to support creating borders on rects.
This should support border width, border radius, color / material and a few other properties.
Rendering of the border and layouting of the border should be the same. I.e there should only be 1 source of truth for setting these properties.

Option 1

To set border width, user sets the border property in Style
To set border color, border radius, the user sets the properties on some completely different component BorderComponent

This has the downside of splitting concerns across multiple components without providing consistency.
Option 2

All border-related properties are moved into BorderComponent and out of Style
Adding a border to a node is now simple as only a single component is concerned.
During layouting, we query the BorderComponent.rect to feed the data into the layout calculation

The end-user experience is better in this situation, but it does fragment Style.
Option 3

All Style-properties are fragmented fully.
BorderWidthComponent, BorderColorComponent, BorderRadiusComponent are introduced.
In order to setup borders on nodes, some or all of these components must be present

End user experience is much more verbose, but this is technically closer to how CSS actually operates.

I think option 2 or 3 is the best way to go as they provide much more consistency, and they pave the way to unlock more style functionality that isn't related to layouting.
Option 3 is probably the best if, and only if we manage to build higher level ergonomics on top, but that is something that has to come later. We can start with path 2, then go to 3 later.
My conclusion is that we need this merged to unlock the way forward.

How does one handle reusable styles when its fragmented into multiple components like this? Perhaps a separate monolithic style bundle? 🤔Internally I'm still debating if styles should be attached to entities or if they should be treated more like materials that live inside of the asset system.

How does one handle reusable styles when its fragmented into multiple components like this? Perhaps a separate monolithic style bundle? 🤔Internally I'm still debating if styles should be attached to entities or if they should be treated more like materials that live inside of the asset system.

Here's how I'm picturing it at a high level:

The style-components are completely fragmented. Their job is only to tell layouting and rending of what these nodes should look like right now. They just store the runtime data.
We have some asset that defines a theme. Likely using scenes, but behaves like css. This asset stores targets and the styling data to be applied to them.
A theming-plugin / system is responsible for getting the theme-asset as input, queries for the nodes specified, then inject new data to the various style-component.
Rendering and layouting is run, in which they simply query for the style-components they need to look at.

The heavy lifting will be done by the theming-plugin, and we should try to aim for a design that separates theme from style.

I would suggest to reorder the migration table a bit to have all flexbox layout stuff together.

How does one handle reusable styles when its fragmented into multiple components like this? Perhaps a separate monolithic style bundle?

The "store each style as an entity" model in https://github.com/bevyengine/rfcs/pull/1 would work well with more scattered styling components. It's also fully extensible to user-defined styles.

This can be considered ready for review :)

Rebased on top of current main. Will start addressing feedback.

@alice-i-cecile Please update the description with the following:
Migration Guide
The Style component has been removed. In its place, there are several new components:

Layout
FlexLayout
PositionType
Offset
SizeConstraints
Spacing
Overflow

Previous location
New location

Style.display: Display
Layout

Style.position_type: PositionType
PositionType

Style.direction: Direction
:exclamation: Removed. Bevy does not currently support multiple text-directions ❗

Style.flex_direction: FlexDirection
FlexboxLayout.direction

Style.flex_wrap: FlexWrap
FlexboxLayout.wrap

Style.align_items: AlignItems
FlexboxLayout.align_items

Style.align_self: AlignSelf
FlexboxLayout.align_self

Style.align_content: AlignContent
FlexboxLayout.align_content

Style.justify_content: JustifyContent
FlexboxLayout.justify_content

Style.flex_grow: f32
FlexboxLayout.flex_grow

Style.flex_shrink: f32
FlexboxLayout.flex_shrink

Style.flex_basis: Val
FlexboxLayout.flex_basis

Style.position: UiRect
Offset

Style.margin: UiRect
Spacing.margin

Style.padding: UiRect
Spacing.padding

Style.border: UiRect
Spacing.border

Style.size: Size
SizeConstraints.suggested

Style.min_size: Size
SizeConstraints.min

Style.max_size: Size
SizeConstraints.max

Style.aspect_ratio: Option
SizeConstraints.aspect_ratio

Style.overflow: Overflow
Overflow

I would suggest that FlexboxLayout is split into FlexContainerLayout and FlexChildLayout:

FlexContainerLayout would have flex_direction, flex_wrap, align_items, align_content, justify_content (and gap from Taffy 0.2 if you add support for that).
FlexChildLayout would have flex-basis, flex-grow, flex-shrink and align-self.

There will likely be lots of nodes that use only 1 set of these but not the other. Especially in the future if more layout modes get added.

This is what the migration guide looks like with these changes:
Migration Guide
The Style component has been removed. In its place, there are several new components:

FlexContainerLayout
FlexChildLayout
PositionType
Offset
SizeConstraints
Spacing
Overflow

Previous location
New location

Style.direction: Direction
:exclamation: Removed. Bevy does not currently support multiple text-directions ❗

Style.display: Display
FlexContainerLayout.hide_from_layout: bool

Style.flex_direction: FlexDirection
FlexContainerLayout.direction: Direction

Style.flex_wrap: FlexWrap
FlexContainerLayout.wrap: Wrap

Style.align_items: AlignItems
FlexContainerLayout.align_items: AlignItems

Style.align_content: AlignContent
FlexContainerLayout.align_content: AlignContent

Style.justify_content: JustifyContent
FlexContainerLayout.justify_content: JustifyContent

Style.align_self: AlignSelf
FlexChildLayout.align_self: AlignSelf

Style.flex_grow: f32
FlexChildLayout.flex_grow: f32

Style.flex_shrink: f32
FlexChildLayout.flex_shrink: f32

Style.flex_basis: Val
FlexChildLayout.flex_basis: Val

Style.position_type: PositionType
PositionType

Style.position: UiRect
Offset(UiRect)

Style.margin: UiRect
Spacing.margin: UiRect

Style.padding: UiRect
Spacing.padding: UiRect

Style.border: UiRect
Spacing.border: UiRect

@Weibye Your latest grouping looks pretty good to me. I have a few comments:

I think Display (or whatever it ends up being called) should be separate from FlexContainerProps, as it applies to leaf nodes too.
I think Display should be an enum rather than a boolean. This aids readability and it self-documenting. You could always have builder/setter methods that accept a boolean if that's desirable.
I think you should consider grouping Display with Position. As I see it, these are really the two most fundamental properties that apply to every single node. I don't know if bevy supports scrolling, but it would also make sense to me to group the property for that with these two if it does.
The alignment properties apply to Grid too, so long term it might make sense to split them into their own components (container and child). But probably that's not worth worrying about for now?

FlexboxLayout could be split between containers properties and item properties:

https://www.w3schools.com/css/css3_flexbox_container.asp
https://www.w3schools.com/css/css3_flexbox_items.asp

Ha I was basing my comment above on the PR description, but it seems it changed since?
@Weibye if that's the case I would prefer to replace your "child" notion in flex box by "item" which is more standard
@alice-i-cecile could you update the description to reflect the latest state? thanks!

Yep! I will. Moving this to draft until I do so. May be a bit: I'm without a desktop for two weeks, and this isn't the sort of work I really want to tackle while travelling.

I think you should consider grouping Display with Position. As I see it, these are really the two most fundamental properties that apply to every single node. I don't know if bevy_ui supports scrolling (Overflow in CSS), but it would also make sense to me to group the property for that with these two if it does.

What should this groping be called?
pub struct ???
{
    pub UiRect offset; // alternatively revert back to `pub UiRect position;`
    pub Display display;
    pub Overflow overflow; // potentially, at a later time
}

Does it make sense to do the following renames?

FlexContainerLayout -> FlexContainer
FlexChildLayout -> FlexItem

Brought this up to speed on main

Gap is now a standalone component which I'm not sure if is the correct approach.
@nicoburns Do you think this instead belongs within either FlexContainer or FlexItem?

Renamed FlexContainerLayout -> FlexContainer
Renamed FlexChildLayout -> FlexItem
Renamed PositionType ->  Position to adhere to CSS specification.

Specs: https://developer.mozilla.org/en-US/docs/Web/CSS/position

Renamed Offset -> Inset to adhere to CSS specification.

It more correctly describes the behaviour
Specs: https://developer.mozilla.org/en-US/docs/Web/CSS/inset
The same change was done in taffy (but not yet released): https://github.com/DioxusLabs/taffy/issues/271

@Weibye Would you be able to make another table (like the one in the first post) representing the latest state of this PR?
I'd suggest that Gap probably belongs with FlexContainer for now. It also applies to the future GridContainer, but that is also true of the alignment properties in FlexContainer.

For context, the styles for CSS Grid will look like (new properties marked in bold):
GridContainer:

Property
Explanation

grid-template-columns
The track sizing functions of the grid's explicit columns

grid-template-rows
The track sizing functions of the grid's explicit rows

grid-auto-rows
Track sizing functions for the grid's implicitly generated rows

grid-auto-columns
Track sizing functions for the grid's implicitly generated columns

grid-auto-flow
Whether auto-placed items are placed row-wise or column-wise. And sparsely or densely.

gap
The size of the vertical and horizontal gaps between grid rows/columns

align-content
Align grid tracks within the container in the inline (horizontal) axis

justify-content
Align grid tracks within the container in the block (vertical) axis

align-items
Align the child items within their grid areas in the inline (horizontal) axis

justify-items
Align the child items within their grid areas in the block (vertical) axis

GridItem:

Property
Explanation

grid-row
The (row) grid line the item starts at (or a span)

grid-column
The (column) grid line the item end at (or a span)

align-self
Align the item within it's grid area in the inline (horizontal) axis. Overrides align-items.

justify-self
Align the item within it's grid area in the block (vertical) axis. Overrides justify-items.

@Weibye Would you be able to make another table (like the one in the first post) representing the latest state of this PR?

Yes, will do but I'd like to get rid of the "display as boolean" (FlexContainer.hide_from_layout) first.

Migration Guide
Up to date as of 76557be5f80473547d0bfcb4de857d0d78f77046
The Style-component has been removed. In its place, there are several new components:

LayoutControl
FlexContainer
FlexItem
SizeConstraints
Spacing

Previous location
New location

Style.direction: Direction
:exclamation: Removed. Bevy does not currently support multiple text-directions ❗

Style.position_type: PositionType
LayoutControl.position: Position

Style.position: UiRect
LayoutControl.inset: Inset(UiRect)

Style.overflow: Overflow
LayoutControl.overflow: Overflow

Style.display: Display
LayoutControl.display: Display

Style.flex_direction: FlexDirection
FlexContainer.direction: Direction

Style.flex_wrap: FlexWrap
FlexContainer.wrap: Wrap

Style.align_items: AlignItems
FlexContainer.align_items: AlignItems

Style.align_content: AlignContent
FlexContainer.align_content: AlignContent

Style.justify_content: JustifyContent
FlexContainer.justify_content: JustifyContent

Style.align_self: AlignSelf
FlexItem.align_self: AlignSelf

Style.flex_grow: f32
FlexItem.flex_grow: f32

Style.flex_shrink: f32
FlexItem.flex_shrink: f32

Style.flex_basis: Val
FlexItem.flex_basis: Val

Style.margin: UiRect
Spacing.margin: UiRect

Style.padding: UiRect
Spacing.padding: UiRect

Style.border: UiRect
Spacing.border: UiRect

Style.size: Size
SizeConstraints.suggested: Size

Style.min_size: Size
SizeConstraints.min: Size

Style.max_size: Size
SizeConstraints.max: Size

Style.aspect_ratio: Option<f32>
SizeConstraints.aspect_ratio: Option<f32>

Queries
Any queries that previously queried all of Style should now instead use the FlexLayoutQuery.
// old
fn my_system(q: Query<&Style>) { .. }
// new
fn my_system(q: Query<FlexlayoutQuery>) { .. }

Most of the time however, you'd likely want to query for the more specific layout components you need.
Change detection
If you previously relied on detecting when something on Style changed you can now instead use the FlexLayoutChanged type.
// old
fn my_system(q: Query<.., Changed<Style>>) { .. }
// new
fn my_system(q: Query<.., Changed<FlexLayoutChanged>>) { .. }

@Weibye Your table is missing gap :)

@Weibye Your table is missing gap :)

Fixed!

The way the constraints data is structured seems wrong to me.
In Flex you usually access the constraints one axis at a time but the current API makes that awkward and fragile.
For example, look at the text_constraint function in the widget/text.rs:
pub fn text_constraint(min_size: Val, size: Val, max_size: Val, scale_factor: f64) -> f32 {
    match (min_size, size, max_size) {
       (_, _, Val::Px(max)) => scale_value(max, scale_factor),
       // ..
    }
}

called with:
text_constraint(
      layout.size_constraints.min.width,
      layout.size_constraints.suggested.width,
      layout.size_constraints.max.width,
      scale_factor,
 )

With the constraints data stored per-axis:
pub struct LengthConstraint {
    pub min: Val,
    pub max: Val,
    pub suggested: Val,
}

it's much more natural:
pub fn text_constraint_2(length_constraint: LengthConstraint, scale_factor: f64) -> f32 {
    match length_constraint {
        LengthConstraint { max: Val::Px(max), .. } => scale_value(max, scale_factor),
        // ..
    }
}

text_constraint(layout.size_constraints.width, scale_factor)

In Bevy that is the worst it gets at the moment, but in Taffy there are lots of tangled sections like:
 if constants.node_inner_size.main(constants.dir).is_none() && constants.is_row {
            child.target_size.set_main(
                constants.dir,
                child.size.main(constants.dir).unwrap_or(0.0).maybe_clamp(
                    child.resolved_minimum_size.main(constants.dir).into(),
                    child.max_size.main(constants.dir),
                ),
            );
        } else {
            child.target_size.set_main(constants.dir, child.hypothetical_inner_size.main(constants.dir));
        }

where most of the complexity would just vanish with some sort of per-axis interface.

I agree with that. @Weibye, do you think we should implement that now, or fix it upstream first?

I agree with that. @Weibye, do you think we should implement that now, or fix it upstream first?

If possible I'd prefer getting this merged in its current state, then tackle that in a separate PR so that discussion can take place more focused, and we can get some movement on these refactors.
I do think we should fix the axis separation upstream first, then fix it here after.

I do think we should fix the axis separation upstream first, then fix it here after.

I'm not even completely convinced that this would an improvement for Taffy. It's true that accessing lots of values in a single axis is awkward atm. But equally it makes accessing both components of the same value easy, and that does happen a lot too. For example, applying aspect ratio is a single method call on Size<T> atm and would be pretty awkward to do if the two components were separated.

There should probably be a different type for border and padding, as it doesn't make sense to give either of those an auto value.

Closing out: this isn't going to be worth rebasing. I still think we should do this, but it's not sufficiently motivated until we have multiple layout algorithms.


Test powerful runner

TL;DR
Please replace this text with a description of what this PR accomplishes.
Type

[ ] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/flyteorg/flyte/issues/
Follow-up issue
NA
OR
https://github.com/flyteorg/flyte/issues/

only works in ghe: https://docs.github.com/en/actions/using-github-hosted-runners/using-larger-runners


Recover from race condition in ActiveSupport::Cache::FileStore

While using ActiveSupport::Cache::FileStore as a cache in Rails, there is a chance of race condition that will throw errors during cache write.
This is due to how atomic write is implemented in rails and it will fail on File#rename due to missing directory/file. Here:
https://github.com/rails/rails/blob/main/activesupport/lib/active_support/core_ext/file/atomic.rb#L50
File#rename will throw SystemCallError, we recover and return value instead.
For more info, please view:
https://github.com/rails/rails/pull/44151
Error from Cheddar.me:
https://appsignal.com/cheddar-payments/sites/61dc6ccf2cf81d516196d1e9/exceptions/incidents/646?timestamp=2023-02-01T23%3A53%3A01Z

@svanhesteren atomic_write in rails creates a temporary cache file and after that renames it.
So, in case of two processes encounter same partial that should be cached they both try to cache it:

First process -> creates a temporary cache folder/file -> renames it
Second process -> notices that temporary cache folder/file is already present -> tries to rename it, when it was already renamed and fails.

So this solution, basically stops second process from failing and returning an error to the end user - by recovering from error and returning an actual value (simulate cache miss in a way).


[mentioning] Do all repositories need access to the PAT of org admin?

In order to get the mentioning working, we need to create an organizational wide secret with the PAT with org admin rights.
This means that all outside collaborators have access to the PAT and can add a little workflow to display the token. This is already a problem for 'normal' users in an organization, but even more for outside collaborators.
I understand the PAT is needed for the outside-collaborators repository with the definations of the groups and outside collaborators. With protected branches this is also no problem.
Question
Do the other repositories also need a PAT with org admin rights?
Context
I'm working for Philips with >2000 developers...

Hi @JeroenKnoops
Thanks for pointing out this sort of vulnerability 👍🏻
I could actually add it up to the ⚠ Known limitations/issues section.

Do the other repositories also need a PAT with org admin rights?
A PAT with full repo scope is needed for the mentioning mechanism of the automated repos. Non-automated repos do not need any PAT, although the PAT as I've formulated the framework is organization-wide.

One could circumvent this by:

Creating local PAT for each automated repo, but I'm afraid that the user owning the PAT should remain an org admin. Thus, the vulnerability persists. A PAT should be required even if the script responsible for mentioning would be running locally to the repo as we still need to grab information from the central repo dashboard.
Not using the mentioning mechanism but only the centralized managing of outside collaborators.

When GitHub will provide the possibility to trigger workflows with webhooks (see FAQ), we will be able to get rid of the specific local triggering workflow.
I haven't looked into trying to fix this vulnerability outright yet; I might be fiddling with this in the next days. However, if you have suggestions, please don't hesitate to show up!
Thanks again!

Another possibility to get around the PAT would  be designing an equivalent GitHub APP, I suppose.

Indeed, that would be a good approach.
I will try to get it working in our GitHub App / Lambda setup. ( https://github.com/philips-labs/terraform-aws-github-runner )
If I get it to work, I will create a similar PR here.

Actually I have no experience with GitHub Apps, so that would really help out.

@JeroenKnoops with a second thought I could do the following: instead of propagating the information from the automated repos to the central dashboard, we can isolate the processing within the locally to the repositories thus without needing any PAT. As a result, we will still need a PAT for running the main scripts in the central dashboard but, in this case, the PAT is not required to be organization-wide. Access to the dashboard is granted only to org admins.


Update README.md

The URL's lead to github's / absolute path, for example: github.com/docs/guides.

Coverage remained the same at 100.0% when pulling 087a5e20585e1442c4064759d324e534b151a911 on PepijnSenders:patch-1 into f05b0038c3b3f427ea26f40fbac5a922fdf11b0b on pburtchaell:master.

Coverage remained the same at 100.0% when pulling 087a5e20585e1442c4064759d324e534b151a911 on PepijnSenders:patch-1 into f05b0038c3b3f427ea26f40fbac5a922fdf11b0b on pburtchaell:master.

@PepijnSenders The URLs do work as is. Are you experiencing issues?

Closing this PR because links already work. If this is not the case, please reopen and explain the issues you are experiening.


fix(a11y): fix a11y issues

Summary

Address Accessibility Issues in SDS Components

Resolved various accessibility (A11y) issues within the SDS components.
#691 #692 #693 #694 #695 #696 #697 #698 #699 #700 #701 #702 #703 #704 #705 #706

Introduce New Style Variables

Added two new style variables: base-border-pressed and accent-border-pressed.

Update Button Component Styles

Updated the styles of the Button component to align with the latest Figma designs and spacing values.
#779

Enhance Dropdown Component

Added a new PopperPlacement prop to the Dropdown component for improved placement control.
#786

Refactor InputToggle Styles

Refactored the styles of the InputToggle component for better maintainability and consistency.

Nice job @masoudmanson !! A few comments to work through, but overall looking good!

Thank you, @clarsen-czi!
I’ve addressed all the design review comments. Could you please review the PR again when you have a moment? 😬

Nice job @masoudmanson , nearly there! Just have one small change to make.

Thanks again @clarsen-czi 🙏🏻😬 The bug has been fixed!


Update requirements to add sklearn minimum version

Signed-off-by: Sunish Sheth<EMAIL_ADDRESS>

The integration tests are failing it appears.

Once we merge this should we revert #13? Would no longer be needed if we enforce >=1.1

No we cannot. This is a requirement for the example repo. Users can still use whatever they want, including old sklearn versions. We should support that.


vanjs-jsx Fragment missing

Hi @Tao-VanJS, I'm getting this error:
Uncaught SyntaxError:
The requested module '/node_modules/.vite/deps/vanjs-jsx_jsx-dev-runtime.js?v=6fa83af3'
does not provide an export named 'Fragment'

Perhaps including something in compileOptions or the jsx-runtime would fix this? Let me try and let you know later ;)
Btw, I'm using the default bare example converted to JSX
import "./app.css";
import van from "vanjs-core";
import vanjsLogo from "./vanjs.svg";
import viteLogo from "/vite.svg";
import { Counter } from "./counter";
const app = document.getElementById("app")!;

const App = () => {
  return (
    <>

      <Counter />

Click on the Vite and VanJS logos to learn more

    </>

  );
};

van.add(app, <App />);

@cqh963852, could you take a look at this?

@cqh963852 sorry to bother you, I believe you need to export something like this
// vanjs-jsx/src/index.js
import van from "vanjs-core";
export function createState(v) {
    return van.state(v);
}

export const Fragment = (props) => props.children; // <<<<<<<<<<<<< THIS

export { default as createElement, default as jsx, default as jsxDEV } from "./createElement";

Another option would be something like Solid has implemented with "jsx": "preserve" and not rely on React's usage of className and htmlFor. But that's just an opinion, we might want to accommodate both React devs and new comers.

"jsx": "preserve"

solidjs has its own babel transform.
I tend to fork the react's compiler to do this work.

className and htmlFor

I can understand your expectation.
Do you mean it to be more like writing html?

A react compiler example

A solidjs example

For those looking for a working solution, check out the:

vite-starter-vanjs-ssr-jsx (express, vite, vanjs, van-plate) featuring SSR , SSG and JSX;
vite-starter-vanjs-ssr (express, vite, vanjs, van-plate) featuring SSR and SSG.

Powered by vite-plugin-vanjs.


blank dashboard

everything seems to be working i do
./restart-dashing -b /home/sysadmin/.gem/ruby/gems/dashing-1.3.7/bin/dashing
and then i can connect to a blank page host:8005/icinga2 it just has the icinga2 icon on the top left, no widgets. looking at cat ./log/thin.log i can see it pulling objects from my icinga instance just isnt doing anything with them?

Strange. Browser type and version? Might be a local javascript caching issue. Or - what does the browser dev console say?
Btw - 1.2.0 provides a systemd service file in tools/systemd. You might want to try that one out too.

Any feedback?

Hey, I've got the same error. When I use Firefox on Ubuntu 16.04 it works perfectly.
On a Windows 7 machine with IE 11 it does not work.
If you need some other information, just ask. Hopes this helps.

AFAIK Dashing is not supported by IE as described here Shopify/dashing#193

I've seen that @bodsch talked about webrick and puma in the past. I don't know how much effort it would be to drop thin and use a different server. If you find something reasonable to support, your PRs could be added to v2.x.

@dnsmichi o.O me?
okay, i plan a test with puma, but not with webrick ;)
puma is a simple replacement for thin and easy to implement.

I'm waiting for someone to hack puma into here.

Please continue in #47 which acts as a general issue to replace thin with something else, or find any other solution.


Reactivity  VS object with non-writable non-configurable property

Version
3.0.5
Reproduction link
https://codesandbox.io/s/vue-3-proxy-over-object-with-non-writable-non-configurable-property-56z7n?file=/src/components/HelloWorld.vue
Steps to reproduce
Create an object with non-writable, non-configurable property and wrap it with reactive() proxy
setup() {
    const inner = { a: 1, b: 2 };
    let outer = {};
    Object.defineProperty(outer, "prop", {
      value: inner,
      writable: false,
      configurable: false,
    });

    outer = reactive(outer); // coment this line to fix the issue

    return {
      outer,
    };
  },

What is expected?
Proxy returned should conform to the ECMA specification - Invariants of the Essential Internal Methods
Specifically the one for Get method:

If P was previously observed as a non-configurable, non-writable own data property of the target with value v, then [[Get]] must return the SameValue.

So the proxy returned by reactive should not make object stored in prop property reactive proxy or change it's value in any other way...
What is actually happening?
Object stored in prop property is converted into reactive proxy and browsers throw an error when accessed from template:
Firefox: TypeError: proxy must report the same value for the non-writable, non-configurable property '"prop"'
Chrome: TypeError: 'get' on proxy: property 'prop' is a read-only and non-configurable data property on the proxy target but the proxy did not return its actual value (expected '#<Object>' but got '[object Object]')

You can use markRaw to tell Vue to skip any property:
Object.defineProperty(outer, "prop", {
      value: markRaw(inner),
      writable: false,
      configurable: false,
    });

You can use markRaw to tell Vue to skip any property:
Object.defineProperty(outer, "prop", {
      value: markRaw(inner),
      writable: false,
      configurable: false,
    });

That is nice workaround for easy example like this but what if you get some complicated (and maybe nested) structure from some 3rd party lib totally independent from Vue?
The fact that same code worked just fine in Vue 2 (leaving the prop non-reactive) is making it even worse as people will start migrating and now the code is suddenly not working and throwing strange errors they don't understand. At least some note in migration guide would be great. Warning in migration build would be even better....

That is nice workaround for easy example like this but what if you get some complicated (and maybe nested) structure from some 3rd party lib totally independent from Vue?
The fact that same code worked just fine in Vue 2 (leaving the prop non-reactive) is making it even worse as people will start migrating and now the code is suddenly not working and throwing strange errors they don't understand. At least some note in migration guide would be great. Warning in migration build would be even better....

was getting this same issue with ethersjs Provider objects. wrapping it with markRaw before assignment solved the issue.  solved the error

Also ran into the same issue with Ethersjs library, markRaw solved it, thanks @snwokenk

@snwokenk you save me, been days trying to figure out that.
For those having this error 'get' on proxy: property 'provider' is a read-only .... you should wrap the provider with markRaw like:
const web3 = new Web3Provider(wallet.provider, 'any');
provider = markRaw(web3);

@octavioamu  thx

This is becoming a problem for us because of how an external library generates code. More specifically https://github.com/timostamm/protobuf-ts. The code it generates uses some cases of defineProperty to create reflection information.
This isn't something we can easily overwrite to put markRaw everywhere, as we'd have to do some fancy search-replace on the generated code to replace everywhere this appears in every class that is generated (which is a lot for us!)
This causes issues because we want to make these classes reactive, which does work, but as soon as we try to read this reflection information we get these errors and it isn't available to us. It's also a pain in unit tests, because when jest tries to diff between the actual/expected values, if either was made reactive then the diff will fail with the same error and we can't actually see what was wrong.
The possible fix for this was closed for an unknown reason, can that be revisited? (see https://github.com/vuejs/core/pull/3025)

Using markRaw isn't a solution, even in the OPs use case, according to the official documentation of markRaw and the warning given there. In example given in before, an inner property is to be marked as raw prior to making the containing object reactive. Hence, the markRaw is lost according to the very similar example in the documentation.
I'm running into this issue as part of a library when trying to prevent expensive conversions of data into its reactive counterpart by tracking the provided data and the results in a weak map for runtime caching. A single unique object is assigned to the source and later also to the result so that multiple provisions of the same source can detect a cached promise for the pending conversions as well as provisions of a result can find additional data that has been put in cache next to the result.
However, due to this bug all this caching doesn't work for the cache key - that unique object - isn't kept raw I assume.

We are facing the same issue, and neither markRaw nor toRaw is a viable solution for us. Additionally, we have our own proxy system that correctly handles this scenario, and we haven't observed any negative impact on performance. Therefore, I think that #3025 should be revisited.
By the way, here is our implementation of the get trap:
https://github.com/V4Fire/Core/blob/fe6d90858e089cec1f157bbbecdb39d5823bd97e/src/core/object/watch/engines/proxy.ts#L254


Fixed for issue#38208

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

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

The new test cases are set to @DoNotRecord(skipInPlayback = true), the reason for ffollowing as：
https://dev.azure.com/azure-sdk/public/_build/results?buildId=3393330&view=results