Use PEP 503 rules to validate upload filename

Fix #10030.

This fix looks good to me. :+1:

I see that one test - test_upload_fails_with_diff_filename_same_blake2 is failing, because it sends an sdist with a filename ending -fake.tar.gz, and parse_sdist_filename rejects fake as a version number. I would hope it's appropriate to just change the test.

Thanks for taking a look, TBH I totally forgot about this. I’m work on it this weekend.

I changed the test to use a valid version string, and also added a try-catch to _is_valid_filename so the endpoint does not crash with 500 when the input is invalid.

Are there tests that validate that a project name with a . in it can be uploaded?
I attempted to test the change. I followed the getting started guide, but the steps didn't work. I can report that issue separately.
This change looks right to me, especially if it's strictly more lenient.

There were not tests that validate anything except alphabets. I can probably add some.

I just confirmed that the change won't block uploading unmangled filenames:

But I do worry that it's allowing uploading files with mangled filenames. Worse, it allows uploading of duplicate artifacts that vary only by the mangled name:

At the very least, Warehouse should reject those duplicates.
A period is a valid character in the filename and in my opinion the preferred character, because that's the character that's used to separate the python packages that the distribution represents and it's also the character used in the project name. My preference would be for warehouse to simply require that flit (or whomever) to use an unmangled name.

When I tried downloading jaraco.develop and jaraco_develop, I got the same artifact:
jaraco.develop main $ pip-run -i http://localhost/pypi --no-deps jaraco.develop -- -c pass
Looking in indexes: http://localhost/pypi
Collecting jaraco.develop
  Downloading http://localhost:9001/packages/4f/a4/edf484a882d669833045a4eaa3aafeae150e2a44a2f22bc96c1a0d271f81/jaraco.develop-7.9.0-py3-none-any.whl (10 kB)
Installing collected packages: jaraco.develop
Successfully installed jaraco.develop-7.9.0
jaraco.develop main $ pip-run -i http://localhost/pypi --no-deps jaraco_develop -- -c pass
Looking in indexes: http://localhost/pypi
Collecting jaraco_develop
  Downloading http://localhost:9001/packages/4f/a4/edf484a882d669833045a4eaa3aafeae150e2a44a2f22bc96c1a0d271f81/jaraco.develop-7.9.0-py3-none-any.whl (10 kB)
Installing collected packages: jaraco-develop
Successfully installed jaraco-develop-7.9.0

I don't know if that's an arbitrary selection or based on the order that the two artifacts were uploaded.

A period is a valid character in the filename and in my opinion the preferred character

A period there is not valid, according to the current wheel spec:

In distribution names, any run of -_. characters (HYPHEN-MINUS, LOW LINE and FULL STOP) should be replaced with _ (LOW LINE). This is equivalent to PEP 503 normalisation followed by replacing - with _.

This was the outcome of this previous discussion. The doc on packaging.python.org is the canonical version (and PEP 427 has had a note added to point to that).
In which case, wheelhouse ought to reject jaraco.develop-7.9.0-py3-none-any.whl. Though I imagine we might want to be somewhat lax if that's what setuptools & wheel produce.
Of course, we could change the written spec (again) to reflect what setuptools/wheel/warehouse already do. It's an easy enough change to Flit. But I think both of the possible changes have other drawbacks:

If we allow . to stay, and just replace runs of -_ with _, then you get a different wheel filename depending on whether you start from the PEP 503 normalised name or from the un-normalised name. (Unless we change PEP 503 as well, which would also affect .dist-info directories).
If we normalise -_. to . instead of _, you avoid that kind of ambiguity, but retrospectively invalidate filenames of many existing wheels.

Looking back at the discussion that led to that change, most of the conversation was about the version part, not the name. @uranusjr made a PR which referenced the .dist-info specification for both name & version parts, and then in my PR I copied the details from there. It looks like neither I nor anyone reviewing it particularly noticed that it was a sizeable change to the rules on the name part.
It is still nice to have the same rules for normalisation in wheel filenames, sdist filenames and .dist-info directory names, though.

My preference would be for warehouse to simply require that flit (or whomever) to use an unmangled name.

IMO this would make duplication worse, because this means an identical wheel can have a myriad of names depending on how tools generate it. We’re focusing on the dot here, but this would also open doors for upper-case letters and continuous run of dashes and underscores, which setuptools does normalise right now. Its current normalisation (or mangling if you prefer) logic is entirely arbitrary, and there are absolutely no reason to use that as the standard behaviour, and I would advocate removing support for that entirely if we have not been doing it for like ten years.
My preference would be for warehouse to simply require that setuptools (or whomever) to use a properly normalised name, instead of doing things half-way. But that’s not really possible, so the next best thing is to allow both the normalisation logic that makes sense (which this PR does), and tolarete what setuptools is currently doing.

I agree - the specs and the implementations should agree. And there's a good argument to be made that a PEP 503 normalized name should be used anywhere an internal representation of the project name is needed. My concern is primarily with how this normalization is bleeding into the external experience. I'll open a new discussion to capture and discuss this concern.

The reason this “bleeds into the external experience” is how setuptools has been implementing the specifications wrong. What do you propose instead? The only way we can avoid any of this “bleeding into” is to either make setuptools’s current behaviour the standard, or prohibit what setuptools is currently doing and break thousands of people’s workflows. Both are inviable, as I already explained, so this is my proposal to make things work. What do you propose instead? Because at this point it seems like you are holding things back without any viable alternatives, for reasons that nobody else seems to agree with.

I propose the following:

Accept this change. I don't think this change is particularly harmful regardless of the outcome, except that it opens up the security vulnerability allowing a release's artifacts to be mutated.
Optionally, address the security vulnerability by disallowing artifact collisions based on the normalization rules.

Other actions I'd prefer to see:

PyPA should update (provisionally, for now) the sdist/wheel specs to soften the normalization standard for distribution artifacts and metadata filenames to match the Setuptools behavior. Why? There's nothing about PEP 503 that indicates that the normalization should apply to these targets and introducing the PEP 503 constraint of mangling names with . has problemmatic consequences.
flit (and other backends) should minimally mangle these names based on the softer normalization rules for distribution artifacts and metadata filenames.
I'll continue to follow up in the discussion thread. I've been busy and didn't realize how contentious this issue would be so I need to spend some more time on it. Perhaps the outcome is that the packaging ecosystem should mangle . characters in these artifacts, but that decision shouldn't be made lightly as an implied consequence of normalization within warehouse.

@uranusjr Thanks for the PR. I reviewed and wanted to make some modifications, hope you don't mind me pushing them. Summary of changes here:

2fcf144 - I made the error messages a bit more clear/detailed, and to be more like the original error here when the prefix didn't match. I also added comments acknowledging that the current behavior technically violates the wheel spec.
6a79492 - I added a test for the behavior which is violating the spec. I don't think we're in a place where PyPI can stop accepting filenames that don't conform to the spec right now, and want to ensure we don't accidently break users that are replying on this until we have time to make a decision and update tooling if necessary
ea0289c - I changed PyPI's behavior to consider canonical project names and versions in the filename when checking for duplicate filenames, rather than the explicit version in the filename. This should eliminate the undesired behavior that @jaraco noted above.

I'll leave this open for ~24 hours or so for folks in this thread to review, but I think this satisfies #10030 as well as other concerns raised here.

FWIW, it seems like the related Discourse discussion referred to above has been resolved in favor of adhering to the spec, and further explicitly specifying in pypa/packaging.python.org#1032 to also normalize uppercase to lowercase characters (which is the status quo in Warehouse as well as Setuptools, right?) while clarifying that implementations should tolerate the legacy behavior. I'm not sure something specific was decided about name collisions on upload, though (which seems to be a concern?)

Is there any update on progress for this issue?  I'm still having a problem when trying to upload a pep420 namespace package created with latest flit to testpypi.

add a section to the /help page similar to https://pypi.org/help/#file-name-reuse

Here's my attempt at that; feel free to adapt it. I've mentioned that the rules used to be more lax, but implied that they're strictly enforced now, which is not actually true. I think that the complexity of trying to explain that probably outweighs strict accuracy.

Why am I getting an "Invalid filename" error?
Package files uploaded to PyPI need to have names in a set format - your packaging tools should create files with suitable names by default. The filenames consist of a number of parts, separated by hyphens (-):

For source distributions: normalised project name and version. E.g. importlib_metadata-4.10.1.tar.gz
For wheels: normalised project name, version, build tag (optional), Python tag, ABI tag, and platform tag. E.g. importlib_metadata-4.10.1-py3-none-any.whl

Normalised project names are lowercase, with any runs of _-. characters replaced with a single _. Version numbers should be normalised as described in PEP 440. All parts are expected to consist only of ASCII characters.
These rules have become stricter over time, so you may see existing packages with names which would no longer be allowed for new uploads.

I incorporated the documentation addition. Thanks!

Closing this until we are more sure what to actually change in Warehouse. We can always reopen, although a new PR is probably preferred anyway due to conflicts.


[automation] updated files automatically.

This an automated PR to update files with new ones

Closing this PR because of conflicts with existing PR.


openstack benckmarker does not working; No BaseVirtualMachine subclass defined with the attributes:

I try to running perfkitbenchmarker at OpenStack on ussuri versions, I follow these below steps:
cd $HOME && git clone https://github.com/GoogleCloudPlatform/PerfKitBenchmarker.git
cd PerfKitBenchmarker/
pip install --upgrade pip
pip install -r requirements.txt
pip install -r perfkitbenchmarker/providers/openstack/requirements.txt
./pkb.py --cloud=OpenStack --machine_type=m1.medium --openstack_network=provider --benchmarks=ping --image='ubuntu1604'
but it gave an error; log is : http://paste.openstack.org/show/800534/
Do you have any idea?

It looks like the only operating systems defined for OpenStach are rhel7 and centos7
https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/blob/master/perfkitbenchmarker/providers/openstack/os_virtual_machine.py#L409
You can either use those OS, or submit a pull request to add ubuntu1604.

Okey thank you for your comment @jellyfishcake. I change from ubuntu1604 to centos7. It is working. But now, when i was iperf benckmarker, creteated centos7 virtual machines, ssh command has username ubuntu, http://paste.openstack.org/show/800621/ . I didint understand it, why?

Looks like the username on openstack is set with a flag. You can change that to be whatever you need.
https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/blob/master/perfkitbenchmarker/providers/openstack/os_virtual_machine.py#L72

Yes, it was wrong flag, but it is fixed. It works, thank you.


chore(main): release siyuan-plugin-picgo 1.11.2

:robot: A new release will be created
1.11.2 (2024-11-16)
Bug Fixes

make SiyuanPicGo singleton (e493573)
move file error (d949e50)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/terwer/siyuan-plugin-picgo/releases/tag/siyuan-plugin-picgo-v1.11.2 :sunflower:


add neccessary config file

Since Lime Survey version 4 a config.xml file is required within the plugin folder in order to install the plugin.
I added the config.xml file and updated the README.md file accordingly.


add sort to timeseries args

Codecov Report

Merging #262 (3fab47e) into main (34e0f72) will decrease coverage by 0.73%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #262      +/-   ##
==========================================
- Coverage   69.28%   68.55%   -0.74%
==========================================
  Files         117      117
  Lines        6284     6150     -134
  Branches      502      504       +2
==========================================
- Hits         4354     4216     -138
- Misses       1806     1809       +3
- Partials      124      125       +1

Impacted Files
Coverage Δ

pyEX/stocks/timeseries.py
32.72% <0.00%> (-7.28%)
:arrow_down:

pyEX/refdata/symbols/options.py
31.57% <0.00%> (-6.52%)
:arrow_down:

pyEX/refdata/symbols/futures.py
46.66% <0.00%> (-6.28%)
:arrow_down:

pyEX/refdata/symbols/crypto.py
53.84% <0.00%> (-6.16%)
:arrow_down:

pyEX/premium/stocktwits/__init__.py
26.66% <0.00%> (-4.59%)
:arrow_down:

pyEX/metadata/__init__.py
35.71% <0.00%> (-4.29%)
:arrow_down:

pyEX/refdata/ric.py
71.42% <0.00%> (-3.58%)
:arrow_down:

pyEX/refdata/isin.py
71.42% <0.00%> (-3.58%)
:arrow_down:

pyEX/account/__init__.py
61.29% <0.00%> (-3.42%)
:arrow_down:

... and 35 more

Continue to review full report at Codecov.

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


Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On       │ │  Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'

What is the location of your example repository?
No response
Which package or tool is having this issue?
Hydrogen
What version of that package or tool are you using?
2024.4.3
What version of Remix are you using?
2.0.4
Steps to Reproduce
npm create @shopify/hydrogen@latest
javascript
cd {package-name} && npm run dev
Expected Behavior
It should run the remix app locally.
Actual Behavior
It's showing an error
╭─ error ─────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On       │
│  Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'                         │
│                                                                                │
│  To investigate the issue, examine this stack trace:                                                │
│    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:239)                              │
│    at defaultLoad (node:internal/modules/esm/load:120)                                              │
│    at load (node:internal/modules/esm/loader:555)                                                   │
│    at moduleProvider (node:internal/modules/esm/loader:436)                                         │
│    at ModuleJob (node:internal/modules/esm/module_job:76)                                           │
│    at #createModuleJob (node:internal/modules/esm/loader:449)                                       │
│    at getJobFromResolveResult (node:internal/modules/esm/loader:261)                                │
│    at getModuleJob (node:internal/modules/esm/loader:242)                                           │
│    at import (node:internal/modules/esm/loader:474)                                                 │
│                                                                                │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────╯
Error: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file://
URLs. Received protocol 'c:'
Code: ERR_UNSUPPORTED_ESM_URL_SCHEME

Also seeing this issue

I'm getting the same error on a Windows device as well

Use WSL

I believe this is related to the pull request at https://github.com/Shopify/hydrogen/pull/2087. Just try downgrading @shopify/cli-hydrogen to 8.0.4, and it work.
@frandiox, @isaacroldan can you guys take a look?

I've encountered the same issue, even after downgrading to @shopify/cli-hydrogen 8.0.4.
Do you have any other solutions to fix the issue?

Can you try with "@shopify/cli-hydrogen": "8.1.1" and see if the dev command works on Windows?


Issues with Ruby Version Not Matching Gemfile Specification and Bundler Path on MACOSVentura

I am experiencing a mismatch between the Ruby version specified in my Gemfile and the Ruby version detected when running bundle install in my project. Despite setting the Ruby version to 2.3.8 (as confirmed by running ruby -v and rbenv versions), Bundler reports that my Ruby version is 2.6.10, which conflicts with my Gemfile specification.
Additionally, the which bundle command returns /usr/bin/bundle, indicating that Bundler is not using the version managed by rbenv but rather a system-wide version.
Steps to Reproduce:

I checked Ruby version with ruby -v, which outputs ruby 2.3.8p459 (2018-10-18 revision 65136) [-darwin22].
Run rbenv versions, showing * 2.3.8 (set by /Users/marialaura/.ruby-version).
Execute which ruby, outputting /Users/marialaura/.rbenv/shims/ruby.
Execute which bundle, outputting /usr/bin/bundle.
Run bundle install within my Ruby project directory, encountering the error: Your Ruby version is 2.6.10, but your Gemfile specified 2.3.8.

Environment:
macOS Ventura 13.6.5
Shell: zsh
rbenv version: rbenv 1.2.0
Ruby version: 2.3.8, set by rbenv
Bundler version:
*** LOCAL GEMS ***
Content of .zshrc:
#openssl
export PATH="/opt/homebrew/opt/openssl@1.0/bin:$PATH"
#openssl arm64
export<EMAIL_ADDRESS>export<EMAIL_ADDRESS>export<EMAIL_ADDRESS>#rbenv
export PATH="$HOME/.rbenv/bin:$PATH"
eval "$(rbenv init - zsh)"
local READLINE_PATH=$(brew --prefix readline)
local OPENSSL_PATH=$(brew --prefix<EMAIL_ADDRESS>export LDFLAGS="-L$READLINE_PATH/lib -L$OPENSSL_PATH/lib"
export CPPFLAGS="-I$READLINE_PATH/include -I$OPENSSL_PATH/include"
export PKG_CONFIG_PATH="$READLINE_PATH/lib/pkgconfig:$OPENSSL_PATH/lib/pkgconfi$
export RUBY_CONFIGURE_OPTS="--with-openssl-dir=$OPENSSL_PATH"
export PATH=$OPENSSL_PATH/bin:$PATH
export SDKROOT="$(xcrun --show-sdk-path)"
export PATH="$HOME/.rbenv/shims:$PATH"
$PATH: /Users/marialaura/.rbenv/shims:/Users/marialaura/.nvm/versions/node/v14.17.0/bin:/opt/homebrew/opt/openssl@1.0/bin:/Users/marialaura/.rbenv/shims:/Users/marialaura/.rbenv/bin:/opt/homebrew/opt/openssl@1.0/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System ...
Attempted Solutions:

I have confirmed the installation of rbenv and rehashed it.
I tried to ensure that the PATH is correctly set to prioritize the Ruby version managed by rbenv.
I installed Bundler for the specified Ruby version and executed rbenv rehash.
Despite these steps, the issue persists, and I'm seeking guidance on how to ensure that Bundler uses the correct Ruby version as specified by rbenv and my Gemfile.

Questions:

Is there a recommended approach to ensure that the correct Ruby version is used by Bundler in projects managed by rbenv?
Could there be a configuration issue in my environment that causes Bundler to detect a different Ruby version than the one rbenv manages?
Any help or suggestions would be greatly appreciated as I work to resolve this issue.

Hi, thank you for the detailed report and I'm sorry this wasn't easier for you. Hopefully it can be fixed quite easily.
The problem is that running bundle on your system goes straight to /usr/bin/bundle (your system ruby) rather than the rbenv "bundle" shim. This makes your bundle install error out because it always uses the system 2.6 ruby rather than the one you've selected.
To fix this, make sure that your currently selected ruby version has the bundler gem installed:
$ gem install bundler
$ rbenv rehash

The "rehash" command here might be optional, but it's a good way to ensure that rbenv shims get rebuilt.
After this, running which bundle should resolve to the rbenv shim instead of /usr/bin/bundle.
There are other two things I spotted that are not related to your immediate problem but might give you problems in the future:

Your project is using Ruby 2.3. This is a very old Ruby version that will have trouble compiling on recent versions of macOS and requires OpenSSL 1.0. Both Ruby 2.3 and OpenSSL are EOL (End of Life) and thus do not receive any security or build patches. Because of this, going forward it will be increasingly more difficult to install these versions of modern machines, especially newer versions of macOS. My suggestion is to find a way to upgrade the Ruby version in your project, preferably to 3.1 or newer.

Your PATH environment variable explicitly contains<EMAIL_ADDRESS>This should not be necessary, as Ruby 2.3 should compile without this being in your PATH. Having OpenSSL explicitly in your path might negatively affect other projects on your system or other compiled programs that might need a newer OpenSSL. In general, it's best to avoid hardcoding any specific version of a tool. You should try removing that entry from your PATH.

Hi @mislav,
First off, I'd like to extend my deepest thanks for your assistance both through email and on this forum. As I was meticulously going through the issues here, I made sure to consider the advice you've provided in past discussions. Your support has been invaluable!
Following your recommendation, I've removed the hardcoded<EMAIL_ADDRESS>entries from my .zshrc file. Here's the current state of things after making those changes:

ruby -v
ruby 2.3.8p459 (2018-10-18 revision 65136) [-darwin22]
openssl version
OpenSSL 3.2.1 30 Jan 2024 (Library: OpenSSL 3.2.1 30 Jan 2024)
which bundle
/usr/bin/bundle
which ruby
/Users/marialaura/.rbenv/shims/ruby
which gem
/Users/marialaura/.rbenv/shims/gem
gem install bundler
ERROR:  Could not find a valid gem 'bundler' (>= 0), here is why:
Unable to download data from https://rubygems.org/ - SSL_connect returned=1 errno=0 state=error: EC lib (https://api.rubygems.org/specs.4.8.gz)
$PATH
/Users/marialaura/.rbenv/shims:/Users/marialaura/.nvm/versions/node/v14.17.0/bin:/opt/homebrew/opt/openssl@3/bin:/Users/marialaura/.rbenv/shims:/Users/marialaura/.rbenv/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App...\

However, I've hit a snag when attempting to gem install bundler. I encountered an error

Running this doctor script: https://github.com/mislav/ssl-tools/blob/8b3dec4/doctor.rb

ruby doctor.rb
/Users/marialaura/.rbenv/versions/2.3.8/bin/ruby (2.3.8-p459)
OpenSSL 1.0.2u  20 Dec 2019: /opt/homebrew/etc/openssl
SSL_CERT_DIR=""
SSL_CERT_FILE=""

HEAD https://status.github.com:443
OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=error: EC lib

This is a really puzzling error. It hints to your Ruby's inability to make HTTPS requests, most likely due to the OpenSSL 1.0 installation being broken or Ruby's bindings to said OpenSSL being broken.
Do you remember how did you install OpenSSL 1.0 and how did you install Ruby 2.3 on this system?

Keep in mind that due to what I said above, it's entirely possible that your problem does not have a solution (at least, not one that you or I might find in a reasonable time).

Your project is using Ruby 2.3. This is a very old Ruby version that will have trouble compiling on recent versions of macOS and requires OpenSSL 1.0. Both Ruby 2.3 and OpenSSL are EOL (End of Life) and thus do not receive any security or build patches. Because of this, going forward it will be increasingly more difficult to install these versions of modern machines, especially newer versions of macOS.

These kinds of issues are expected to happen with EOL'd software. Regardless of whether you or I find a solution to this, I will close this thread soon, as it is not the goal of rbenv to help you flawlessly manage EOL'd versions of Ruby.

@mariaLauraDev If you're still running into issues, I built a paid product called Ruby on Mac that is guaranteed to properly install Ruby 2.3.8 and Bundler on your Mac. If this is for your job, you should be able to ask your manager to buy it for you. You'll need the "Ultimate" version for Ruby 2.3. Customers from Brasil get 40% off (I support Purchasing Power Parity).
If you decide to buy it, make sure to carefully read the documentation section called "Installing Ruby versions older than 2.6.10".
I'm also happy to answer any questions. My email is at the bottom of the Ruby on Mac site.

Keep in mind that due to what I said above, it's entirely possible that your problem does not have a solution (at least, not one that you or I might find in a reasonable time):

Your project is using Ruby 2.3. This is a very old Ruby version that will have trouble compiling on recent versions of macOS and requires OpenSSL 1.0. Both Ruby 2.3 and OpenSSL are EOL (End of Life) and thus do not receive any security or build patches. Because of this, going forward it will be increasingly more difficult to install these versions of modern machines, especially newer versions of macOS.

These kinds of issues are expected to happen with EOL'd software. Regardless of whether you or I find a solution to this, I will close this thread soon, as it is not the goal of rbenv to help you flawlessly manage EOL'd versions of Ruby.

I installed folowing this steps:

using arm64 arch
I saved this file in the downloads folder: https://raw.githubusercontent.com/rbenv/homebrew-tap/e472b7861b49cc082d1db0f66f265368da107589/Formula/openssl%401.0.rb
and commented out the "make, test" line in the script.
I ran in my terminal brew install<EMAIL_ADDRESS>I added echo 'export PATH="/opt/homebrew/opt/openssl@1.0/bin:$PATH"'  to my path
I installed ruby with flags: RUBY_CFLAGS="-w -DUSE_FFI_CLOSURE_ALLOC " RUBY_CONFIGURE_OPTS="--with-readline-dir=$(brew --prefix readline) --with-openssl-dir=$(brew --prefix openssl@1.0)" rbenv install 2.3.8

I really appreciate your technical assessment. After you told me that I could be facing an unsolvable problem, I tried to install it with asdf, and I succeeded! Thank you! I was going to keep trying for weeks to find a solution

I've created a repository to share all my discoveries and learnings, if it's useful to anyone else! I want to share it with the community as a way of saying thank you for all the collaboration I've received.
Repository: https://github.com/mariaLauraDev/install-ruby-2.x-macos-and-tips


Plot Passive LR(Norris) vs QBC (LR(Norris) Committee) vs US vs Yan active vs Raykar active

Add horizontal grid lines to the plot, it is starting to get hard to visually see who is doing well.


Issue with using the app

Is there an existing issue for this?

[X] I have searched the existing issues.

What's the problem?
Hello,
I've followed the install instructions given on that page, everything ran smoothly but when I tried to open the app, it just opens an empty Sniffnet window that closes just a few second after.
Then nothing more :(
Any clue what's going on?
Thanks for your help.
How did you install the app?
downloaded one of the provided packages
Operating System
Windows
Additional context
No response

Hi @Ucanspam maybe it's a problem with your graphical card.
Try setting the ICED_BACKEND=tiny-skia environment variable and let me know if it fixes the problem.

thanks for your quick reply Giuliano,
Hmm... how, where do I check that variable?

You can check this guide: https://www.howtogeek.com/787217/how-to-edit-environment-variables-on-windows-10-or-11/#how-to-edit-environment-variables

it works, congrats!
What is that variable for?
Can I keep it, should I remove it some day ?

The variable just tells Sniffnet to use a different graphical renderer for the user interface (tiny-skia over wgpu).
This is because your graphical card is probably not up to date or simply it doesn't support wgpu.
You can keep that variable, it's not a problem and it doesn't have any other consequence on your PC.

oh thx for the explanations.
My Asus laptop is 10 years old and it's true I can't update the nvidia driver anymore.
Thx for your support Giuliano.
Good evening ;)

I'm happy we made it work 🎉
Have a good day!


Uncaught TypeError: Cannot read properties of undefined (reading 'childNodes')

It keeps throwing this error as I try to add an item. Sometimes I cannot even Save the item, it just gets stuck there until I terminate the server.
Thanks for making this tool, I plan on using this as my Vocabulary Journal. Cheers : )

So just to confirm -- this happens when you click "Save" to add a new item? And the server doesn't show any errors? Can you maybe share the HTML file (or some minimal example where this happens) so I can try to reproduce the problem?

I downloaded empty.html and yes, it happens only when I try to add a new item, it also happens when I edit the about section.
It happens for sure when I try to add a new term and save it without filling the second term field. Its a weird glitch I am not sure what exactly is causing it.

About your first question - is the server supposed to show any errors? I only checked the browser's console, there are no errors on the terminal.
I ran using sed -n '/START OF editor.js$/,$p' empty.html | FILE=empty.html node

I have tried to reproduce this but no luck so far. I've tried with Safari/Chrome/Firefox on macOS and with Chrome/Firefox on Linux. Can you let me know which OS and browser you are using?

Hey, sorry I forgot to mention this information earlier, it's:
Version 1.40.107 Chromium: 103.0.5060.53 (Official Build) (64-bit)
Ubuntu 20.04.4 LTS x86_64
5.13.0-51-generic

I am not facing this issue anymore after downloading a new empty.html


JAM-1639:  Configure CORS based on nginx proxy header

! NOTE !
SR-868 will need to be merged for this to take effect. However, this still can be merged without it.
Goal
Restrict CORS to only the billups domains. This is challenging because the boohma app supports dynamically generated subdomains, and according to the W3 spec, the Access-Control-Allow-Origin header only supports either a single wildcard, XOR a list of domains (i.e. *.edge.boohma.com is not supported).
My solution was to use nginx and add a helper function to the TileStache server to look for a custom header in the request and set the Access-Control-Allow-Origin accordingly. This should work fine for us since the ELB only exposes the nginx reverse proxy server, but it could still be spoofed if the client sends an Origin header with the correct domain (which would be the case anyway)
Oh well, better than nothing, I suppose.
Testing
Copy the nginx/nginx.conf.sample to nginx/nginx.conf and modify with the following lines:
    # ... more configuration above ...

    upstream app_server {
        server unix:/var/gunicorn/gunicorn.sock fail_timeout=0;
    }

    # add this here...
    map $http_origin $cors_header {
        default "";
        "~^https?://.*\.local\.boohma\.com(:[0-9]+)?$" "$http_origin";
    }

    server {
        listen      9090 default deferred;
        server_name localhost;

        location / {
           # ... more headers here ... #
            proxy_set_header X-Proxy-Allow-Origin $cors_header; # add this here...
            proxy_pass       http://app_server;
        }
    }
}

Rebuild the docker image and container:
docker build -t tilestache .
docker-compose up -d

Configure your local DNS with an alias for localhost:
<IP_ADDRESS>  billups.local.boohma.com

Test using https://github.com/Billups/protomap. You will need to modify the locdots.js file by hand to set the tilestache URL. Try pointing protomap at your local TileStache host and then do the following:

go to http://localhost:<protomap_port>/locdots, observe the JS console is indicating a CORS error for each XHR Request sent by the client and the dots do not show up.
go to http://billups.local.boohma.com:<protomap_port>/locdots. Observe that the dots also show up and there are no CORS errors.

good solve for this Dylan.

I need to get Tile Stache working (Python 2 env for me locally) to start to PR these with you. I added Justin to this ticket, hoping maybe he can jump in and try it out as well. More of the team with a server running is a good thing!! cc: @justinhurlburt

Yeah I'll dive in.

@alexbaker-billups Have you tried running it via docker?
docker build -t tilestache .
docker run --name tilestache -p 9090:9090 -v $PWD/:/usr/src/ --rm tilestache


externalip-webhook prevents kubectl diff

Since the externalip-webhook does not specify any sideEffects its value defaults to unknown which prevents that
kuebctl diff ...

succeeds.
This error is shown
Error from server (BadRequest): admission webhook "validate-externalip.webhook.svc" does not support dry run

I think it is safe to just add sideEffects: None but I'm not 100% sure. Please let me know what you think.

/reopen

/remove-lifecycle rotten

/close


Added several medical device makers

Leica Biosystems
Diagnostic Grifols, SA.
Modulated Imaging
Promenade Software, Inc
NIPRO
Summit Medical Products

@beauwoods thanks for the PR. Do any of these vendors host a vulnerability disclosure policy on their own pages? If not, they'll need to be collapsed into a single entry. Please advise.

Leica Biosystems does.

Looks like this was resolved with #33 – closing.


✨ feat: added button to copy environment Id

@all-contributors
please add @cosmos-explorer for UI


Switch to dockerhub_release variable group

Once merged and #5 is fixed, we should have docker images in aswf org...

#5 has been fixed, I would need an approval to merge this!


Oracle-Database for Azure CLI support

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[*] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[*] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[*] My extension version conforms to the Extension version schema

For new extensions:

[*] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

Please fix CI issues

Please register your top level command group in src/service_name.json file.

Please run azdev linter oracle-database in your local environment. And provide the short option name as alias for the failed parameters by following this doc

This PR is planed to release on Monday 22 July


[ISSUE #4812] Set up Admin Endpoints v2

Fixes #4812
Motivation
Organize and optimize the code merged in https://github.com/apache/eventmesh/pull/4768, and implement v2 endpoints used for the new EventMesh Dashboard.
Modifications

Added PUT method to org.apache.eventmesh.runtime.admin.handler.AbstractHttpHandler#handle
Eliminated the step of getBytes in org.apache.eventmesh.runtime.admin.handler.AbstractHttpHandler#write
No need to construct HttpResponse with cross-origin headers in endpoint implementation code
Cleaned up various overloaded methods that were messy and non-hierarchical
For old endpoints, the path remains unchanged temporarily (endpoint path needs modification by Next.js Dashboard), suffix class names with V1, moved to v1 package; for new endpoints, use path /v2, do not suffix class names with V2, placed in v2 package.
Corrected incorrect naming of annotations such as @ConfigField
Implemented /v2/configuration endpoint, returning all Runtime configurations.

For detailed changes, refer to the naming of each commit.
Screenshots

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (JavaDocs)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

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

Project coverage is 16.20%. Comparing base (98b1ed1) to head (c14c936).
 Consider uploading reports for the commit 1930bbe to get more accurate results

Files
Patch %
Lines

...runtime/admin/handler/v2/ConfigurationHandler.java
0.00%
47 Missing :warning:

...esh/runtime/admin/handler/AbstractHttpHandler.java
0.00%
24 Missing :warning:

...apache/eventmesh/runtime/util/HttpRequestUtil.java
0.00%
15 Missing :warning:

...ache/eventmesh/runtime/util/HttpResponseUtils.java
0.00%
9 Missing :warning:

...pache/eventmesh/runtime/admin/response/Result.java
0.00%
8 Missing :warning:

...esh/runtime/admin/handler/AdminHandlerManager.java
0.00%
7 Missing :warning:

...mmon/config/convert/converter/ObjectConverter.java
53.84%
1 Missing and 5 partials :warning:

...me/admin/response/v2/GetConfigurationResponse.java
0.00%
6 Missing :warning:

...entmesh/runtime/admin/handler/v1/EventHandler.java
0.00%
5 Missing :warning:

...n/handler/v1/RedirectClientBySubSystemHandler.java
0.00%
5 Missing :warning:

... and 46 more

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #4813      +/-   ##
============================================
- Coverage     16.20%   16.20%   -0.01%
  Complexity     1710     1710
============================================
  Files           857      858       +1
  Lines         30883    30885       +2
  Branches       2685     2693       +8
============================================
  Hits           5005     5005
- Misses        25410    25412       +2
  Partials        468      468

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

LGTM


Stripping of name will have no effect if cached Fama-French exists

Pyfolio calls https://github.com/quantopian/empyrical/blob/master/empyrical/utils.py#L309 which reads the Fama-French factors from a cached file if it exists. Thus, users upgrading pyfolio and empyrical will get the error that  column 'Mom' does not exist, as the old name with the white-space is still in the cache.
The problem is in this PR: https://github.com/quantopian/empyrical/pull/63
CC @vikram-narayan

if you clear your local cache, this problem will be fixed; do you think it's worth adding a check for this particular case? happy to add one if you think so, just not sure how common the issue is

Yes, but a user will not know what to do and just receive a very odd error.


perf: add support to laravel 9

@Naoray
Is this package still maintained?

@lsnepomuceno I've not abonded this pkg yet and will continue to maintain it whenever I find the time to do it.
Regarding your PR:
I am not 100% confident that bumping the version will do the trick for upgrading to laravel v9. Will check within the next days.

Did you manage to follow up? Is this ok to upgrade now?

@1e4 sorry, I've not have the time nor the will to look into this. Since I didn't find the time during the last month and I don't use this package personally anymore, I will abandon it. Feel free to fork it and maintain your own version of it.


wiki runner: restoreDevonfwIde

Implement the command restoreDevonfwIde in the wiki runners.
The installDevonfwIde could be re-used. The step can be skipped if the IDE is already installed.
Parameters:

Tools to be installed within the devonfw IDE: string array
Optional: Version of IDE to install

Wiki Console
Installation of the latest devonfw IDE, including the option of installing a custom IDE version.
Wiki Editor
Nothing to do
Wiki VS Code
Nothing to do
Wiki Eclipse
Nothing to do

@GuentherJulian should this be the exact same as installDevenfwIde or should it be written from a perspective where the devonfw-ide should already be installed?

@GuentherJulian should this be the exact same as installDevenfwIde or should it be written from a perspective where the devonfw-ide should already be installed?

I think we could use the same text for both commands. We only differentiated that in the katacoda runner so that the user has not to set up the ide by himself. But in the wiki this is not needed I think. If the user has already installed the ide he can actually skip the part. So maybe just use the same template and add (for both commands) an hint that the user can skip this part of the tutorial if he already has an ide with the requiered tools.


README.md should say "Voice Assistant quickstarts" instead of "Voice-first virtual assistants quickstarts"

Describe the bug
This is a doc bug. README.md should say "Voice Assistant quickstarts" instead of "Voice-first virtual assistants quickstarts". Voice Assistants is the new term to describe APIs in the Microsoft.CognitiveServices.Speech.Dialog namespace.

Hi Darren,  since you are an MSFT employee, can you check to see if you have edit privileges?  If not, we will do this for you.  If you do, could you make the change?

@trrwilson Could you take a look on this?

@jhakulin @trrwilson @chrisbasoglu No problem, I'll take care of it on Monday.

@jhakulin @chrisbasoglu PR here (I can't add folks as reviewers). Please sign off

Closing the issue


Feature/cu mb5py4 hud controller refactor

HUD controller now uses #Defines for hierarchy related functionalities (more readable)

Task linked: CU-mb5py4 HUD Controller refactor


State machine

Summary

Implement state machine pattern in coordinator

State Machine
The state machine consists of the states Idle, Sum, Update, Sum2 and Error.

Tasks that are performed in the individual states
Idle

clears the round dictionary
updates the seed

Sum

generates a new round key pair
runs the sum phase (until the minimum number of sum massages is reached)
freezes the sum dictionary

Update

runs the update phase (until the minimum number of update massages is reached)

Sum2

runs the sum2 phase (until the minimum number of mask is reached)
performs the aggregation of masks and the unmasking of the final mask

Error

the transition into the Error state can only take place if all senders of the request channel have been dropped or the aggregation has failed
logs the error
in case of a ChannelError the state machine panics

Example:
You can find an example how to create and use the state machine in src/rust/bin/state-machine.rs
Missing parts:

In the current implementation, the state machine does not emit any protocol events. This will be added in #414.
I haven't added tests yet. I would like to add them in a follow up PR (after #414 is merged).
The implementation of phase timeouts, etc.
[x] A clean shutdown of the state machine.

Thanks for the feedback @janpetschexain 👍
I was busy fixing a bug in the state machine. (I forgot to call aggregator.aggregate in the update phase). I fixed it but now the aggregator is reinitialized twice (in Sum2 and idle state).
I'm not a big fan of my solution to be honest but I didn't want to change something on the aggregator in this pr.

Alright, I tried to implement all your suggestions.
What I have changed in the last commits:

renamed State to PhaseState
moved the SumDict, SeedDict, MaskDict and Aggregator into the respective PhaseStates

This allowed me to remove clear_round_dicts and the double reinitializtion of the Aggregator in the Sum2 and Init state

changed the return value of PhaseState::<S>::new() to Self

The main reason for this change is to simplify the testing of PhaseState. Before that change, I had to use match to access the inner value:

let state_machine = PhaseState<Idle>::new();
match state_machine {
	StateMachine::Idle(idle) => idle.method
}

To keep the next method of PhaseState simple, I have added #[derive(From)] to StateMachine, so that I can write

+ PhaseState::<Sum>::new(self.coordinator_state, self.request_rx).into()
// instead of
- StateMachine::Sum(PhaseState::<Sum>::new(self.coordinator_state, self.request_rx))

added an Unmask state to separate the unmasking code from the Sum2 state (maybe this separation is too much?)
added a Shutdown state to shutdown the state machine in the event of unrecoverable errors or intended program stops.
removed the panic for ChannelError
in the Shutdown state a clean shutdown of the request channel is performed to consume all unprocessed messages. At the moment this does not make much sense, since in the case of a ChannelError the request channel is empty, but in the future we may have such a case where the state machine is in the shutdown state and there are still unprocessed messages in the channel.

I'm looking forward to hearing your feedback.

We should either squash or clean the history up a bit before merging.

Closed because it is part of #421.


Archive module

User Story
As a user, I can archive a module after it is completed, so that I can old contacts will be hidden in a new semester.

This is good to have, but not crucial to our app. Closing due to lack of time to implement.


Added a sample config file and made metadata export to a json

@neon-cyan thats just nice little tweak. Merging this PR.
I will change the documentation to reflect JSON instead of text file being generated.
Thanks!


Easier way to find PowerBattery.dll

Since its location in the package has changed and probably will change again, check out https://www.powershellgallery.com/packages/LenovoBattery/0.2

I cannot distribute the dll with the release, because it would be a violation of Lenovo's license. The author of the project you posted just doesn't care.


[1.x] - feat(response): make the response method be more generic.

@surazdott nice package.
I hope this PR is of your liking.
Thanks.

@adrorocker Thanks for contributing to the project! Your work is greatly appreciated.


Get modo-bugs script working again

Travis tests have failed
Hey @silasary,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
TravisBuddy Request Identifier: 732f91d0-8edf-11ea-80eb-6b769f7cd14d


Unable to POST a transaction Bundle with nested collection Bundle entries

Duplicate of https://github.com/hapifhir/hapi-fhir/pull/5693


[Enhancement] skip text file desc part when file is not text format

What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes:

Fixes #
Problem Summary(Required):

This PR is trying to reduce plan size(in thrift format).
I was tring to setup a table with 600K small files, then it took about 3262ms seconds on CoordDeliverExec stage.

and from profile, we can see a lot of time is on thrift serialization

but from the profile, we can TextFileDesc part takes a lot of time, but that part is necessary only for text format.
so with this pr, the CoordDeliverExec can be reduced to 2664ms(whch is slightly improved)

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:disappointed: fail : 0 / 5 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/RemoteScanRangeLocations.java
0
5
00.00%
[108, 109, 131, 147, 148]


issue with adding 'rv_intercept' & 'rv_slope' to priors and fit

In the "fitting radial velocities" tutorial, when I try to add 'rv_intercept' and 'rv_slope' to the priors and fit, I get the following error:
KeyError                                  Traceback (most recent call last)
 in
1 # Run juliet:
2 dataset = juliet.load(priors = priorsLT, rvfilename='rvs_toi141.dat', out_folder = 'toi141_rvs_3planets')
----> 3 results = dataset.fit(n_live_points = 300)
~/anaconda/envs/python3/lib/python3.6/site-packages/juliet/fit.py in fit(self, use_dynesty, dynamic, dynesty_bound, dynesty_sample, dynesty_nthreads, n_live_points, ecclim, delta_z_lim, pl, pu)
716         return fit(self, use_dynesty = use_dynesty, dynamic = dynamic, dynesty_bound = dynesty_bound, dynesty_sample = dynesty_sample,
717                    dynesty_nthreads = dynesty_nthreads, n_live_points = n_live_points, ecclim = ecclim, delta_z_lim = delta_z_lim,
--> 718                    pl = pl, pu = pu)
719
720     def init(self,priors = None, input_folder = None, t_lc = None, y_lc = None, yerr_lc = None, \
~/anaconda/envs/python3/lib/python3.6/site-packages/juliet/fit.py in init(self, data, use_dynesty, dynamic, dynesty_bound, dynesty_sample, dynesty_nthreads, n_live_points, ecclim, delta_z_lim, pl, pu, ta)
1308                 for pname in self.posteriors.keys():
1309                     if data.priors[pname]['distribution'] != 'fixed':
-> 1310                         self.posteriors[pname] = np.median(out['posterior_samples'][pname])
1311                 posterior_samples = out['posterior_samples']['unnamed']
1312                 if 'pu' in out.keys():
KeyError: 'rv_intercept'

I have a similar issue (I think) when trying to include 'GP_sigma_rv' in a global model (in Incorporating Gaussian Processes tutorial).
KeyError                                  Traceback (most recent call last)
 in
62                       GPrveparamfile='GP_regressors_rv.dat')
63
---> 64 results = dataset.fit(n_live_points = 300)
~/anaconda/envs/python3/lib/python3.6/site-packages/juliet/fit.py in fit(self, use_dynesty, dynamic, dynesty_bound, dynesty_sample, dynesty_nthreads, n_live_points, ecclim, delta_z_lim, pl, pu)
716         return fit(self, use_dynesty = use_dynesty, dynamic = dynamic, dynesty_bound = dynesty_bound, dynesty_sample = dynesty_sample,
717                    dynesty_nthreads = dynesty_nthreads, n_live_points = n_live_points, ecclim = ecclim, delta_z_lim = delta_z_lim,
--> 718                    pl = pl, pu = pu)
719
720     def init(self,priors = None, input_folder = None, t_lc = None, y_lc = None, yerr_lc = None, \
~/anaconda/envs/python3/lib/python3.6/site-packages/juliet/fit.py in init(self, data, use_dynesty, dynamic, dynesty_bound, dynesty_sample, dynesty_nthreads, n_live_points, ecclim, delta_z_lim, pl, pu, ta)
1308                 for pname in self.posteriors.keys():
1309                     if data.priors[pname]['distribution'] != 'fixed':
-> 1310                         self.posteriors[pname] = np.median(out['posterior_samples'][pname])
1311                 posterior_samples = out['posterior_samples']['unnamed']
1312                 if 'pu' in out.keys():
KeyError: 'GP_sigma_rv'

Hi @jkteske,
Sorry for just returning to this! Your first problem turns out it has to do with the code in the tutorial trying to save the results of the linear trend to the same folder as the 3-planet fit. When a folder already exists, juliet by default loads the priors in the folder but defines internally the ones given by the user in the dictionary (i.e., the priors dictionary). This is a way of letting the user know that the input dictionary and the priors file in the folder are inconsistent (like what you just experienced). I just changed the fact that the tutorial uses the same name for both fits in https://github.com/nespinoza/juliet/commit/6e987471dd65c3ac04c98ffff145d93c360d8065 (sorry about that).
Your second issue is similar to the first one --- it stems because you probably ran that fit in the same folder as the one in the "Fitting RVs" tutorial, so the folder named toi141_rvs already exists (from the very first RV fit, with no GPs and no second planet) and produces the same problem. To ensure future users that do the same in the future don't get the error, I've just changed the name of the folder in the GP tutorial in this commit: https://github.com/nespinoza/juliet/commit/1fdfe09da9c36bbbc01df8fff0f3132bca819601.
Let me know if all this fixes your issues, so I can close this issue! Thanks for bringing those to my attention.
Best,
N.

Thank you thank you! These changes fixed the issues.

Fantastic! Glad to know it was all resolved at the end. Closing this issue then and, if you have any more questions and/or bugs, please feel free to open another issue!
N.


nixos/security: add size option to /run/wrappers

Description of changes
Add an option to configure the maximum size of /run/wrappers tmpfs. Note I've preserved the default behavior of allocating half the available ram as the max size of the tmpfs mount.
Motivation for change: all tmpfs mounts have configurable sizes except /run/wrappers. /run/wrappers takes up a 500ish kb on my system. There is no need for it to have a maximum allocated size of $RAM/2 which appears to be the default.
I understand that tmpfs allocates memory lazily, and it is unlikely that something is going to blow up the size of /run/wrappers. This option addition is mostly an attempt at consistency, since the other tmpfs mounts (like /dev/shm or /run) are max-size configurable.
Things done
I've tested this on my local NixOS install. It works for me.

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

LGTM if you prefix the second commit's message.

I squashed the second commit 👍

@ofborg test simple

Thanks!


docs/backend-system: add backend common deprecation section to migration docs

Fixes #27279

@Rugvip Thanks for updating the documentation with these pointers! One export that was missed was the Git helper. Here's a dead docs link referencing it and here a a few references in the wild.


Handtracking with edge device

Hello guys,
Can the hand tracking model be used on a device like raspberry pi with an edge device like Coral TPU?
Thanks

Hi @Masterythepua, Hand tracking model is currently not available on the Edge devices. MediaPipe has limited resources for new features. We will let you know if there is any specific update on this request.
You can refer to this issue #426 and #426(comment) for more information.  Thank you!

Hi @kuaashish
I use the handtracking model to achieve gesture control of raspberry pi
When I use the handtracking model with raspberry pi I have 10 FPS. Is there a way to increase the FPS to 15 or 20?

Hi @Masterythepua, This gives you better understanding #3158 (comment). Thank you!

Hi @Masterythepua, Thank you for the confirmation. Can we move this issue to close status if it does not need further assistance. Thank you!


chore: Bump Karpenter version

Fixes #N/A
Description

Bump karpenter version

How was this change tested?

N/A

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 12 (0.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 82.3%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/fake/cloudprovider.go
0
3
0.0%

pkg/cloudprovider/cloudprovider.go
0
9
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/providers/amifamily/ami.go
1
90.32%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
5352

Relevant Lines:
6503

💛  - Coveralls


[Feat]can add some more categories

Description
add some missed out and common categories:
1.Office and School Supplies
like stationery items Notebooks, pens, markers, and folders etc
2.Hobbies and Crafts
like Art Supplies( Paints, brushes, canvas, and sculpting tools.),DIY Craft Kits( Candle-making, knitting, and scrapbooking.) or Collectibles (Stamps, coins, and action figures.)
3.Sustainable and Eco-Friendly Products
like Reusable Household Products( Eco-friendly cleaning supplies, reusable straws, and bags.)
can you pls assign this to me
thanks
Screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

Hey @SanikaBhalerao1345 As of now, we do not need it. We will let you know in the future if there is a need. Please search for another issue and raise it, which I'm happy to assign to you.

Actually, I need to reach a total of 128 stars to get the Starstruck x2 badge achievement on my GitHub. Can you please help by Star our repository? ⭐


Download bits from an App

http://apidocs.cloudfoundry.org/226/apps/downloads_the_bits_for_an_app.html

Related thread:
<EMAIL_ADDRESS>

In bluemix, this feature is disabled.


Counter example is incorrect

The counter example comment mentioning a and b variables is incorrect. There is no use of such variables in that first example

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

ID: 77c58a78-a567-e99a-9eb7-62dddd1b90b6
Version Independent ID: 680a79bc-11de-39fc-43e3-e07dc762db18
Content: Expressions - Azure Pipelines
Content Source: docs/pipelines/process/expressions.md
Product: devops
Technology: devops-cicd
GitHub Login: @juliakm
Microsoft Alias: jukullam

@jsgoupil Thank you for the feedback.
The documentation has been updated and is pending review.


Fix play version

👍

Coverage remained the same at 90.323% when pulling aa615450b59f9b2781a11ad077e8297be492bd6c on kailuowang-patch-1 into 0e47ef93b70c2a7096967d82e6fde2c718606384 on release2_5.


[webview_flutter] iOS: Make webViewWebContentProcessDidTerminate invoke onWebResourceError

Description
onWebResourceError has been handling webContentProcessTerminated error, however, webViewWebContentProcessDidTerminate callback on iOS is not handled. This PR fixes that.
This will help apps to get a callback information when the webview content is not rendering; then those apps can choose to apply workarounds.
Related Issues
Fixes https://github.com/flutter/flutter/issues/61795
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Sorry to add to this but I'm a bit lost with where this issue ended up. Was it simply integration of this PR to signal the app? webViewWebContentProcessDidTerminate can happen not just because of memory pressure but because the webview the app specifically wants to save, but is offscreen for a while .. is offscreen. In other words it will happen to everything but short lived, on-screen, web views.
I think auto-reloading web views terminated by IOS should be an explicit plugin boolean (default false) to encourage the app to handle it.


feat: first pass at css module support for devtools

Going to have to punt on css modules for the time being. Ultimately it came down to swc's lack of maturity in bundling CSS modules. Will revisit in the future.


Fix: Incorrect encoding of an apostrophe

Update to line #15 to fix the incorrect encoding of an apostrophe.

@cryophobia : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good.


dclexperience Position 9, -2 : Ron's dialogue stops all of a sudden and dialogue box cannot be closed

Explorer Alpha build version:
(Version 0.3.335-g8f637032-main
(windows)
Issue Description:
Ron's dialogue stops all of a sudden and dialogue box cannot be closed:

Steps to reproduce:

Go to 9, -2
Talk to the robot

Expected behaviour:
Dialogue should be properly triggered
Current behaviour:
Dialogue stops all of a sudden
Reproduction rate:

[ ] < 10%
[ ]  < = 25%
[ ]  50%
[ ]  < = 75%
[x ]  100%

Severity:

[ ] Cosmetic
[ ] Minor
[x ] Medium
[ ] High
[ ] Critical
[ ] Blocker

Priority:

[ ] High
[x ] Medium
[ ] Low

Platforms / OS:

[x ] Windows 11
[ ] Windows 10
[ ] Mac Sonoma
[ ] Mac (specify the version on Additional Notes)

Fixed on latest
https://github.com/decentraland/unity-explorer/assets/139157886/ade035fa-49f4-46ef-81f7-440e5aa22a00


WIP: Add a new method to useTable for changing the filter operator dynamic…

Please provide enough information so that others can review your pull request:
This is a prototype of what a simplistic solution to #1373 could look like

Explain the details for making this change. What existing problem does the pull request solve?
This allows users to dynamically change the filter operator - for example a checkbox added inside of <Table.Column filterDropdown={...} /> could invert the operator from equals (eq) to not equal (ne), or it could trigger partial matching contains/ncontains instead of eq.
Test plan (required)

Use the changeFilterOperator helper to modify an operator for an existing filter dynamically
Observe the operator changing and the data on the page updating

Related to #1373

Any updates?


Get DeviceId of Samsung (Tizen) TV/Emulator

This is just a question and should be tagged as one.
Say I were to use the built-in template starters, hello-world or the blank app. Is there a way to get the deviceID of the TV (or the emulator) on which the app is deployed/running using the Tizen flavor?
For instance, the Api exposes the platform in use (as depicted in the screenHome.js file). Is there a way to get the deviceID flow there as well?
Platform example/snippet:
import { Api } from 'renative';

class ScreenHome extends React.Component {
    constructor() {
        super();
    }

    render() {
        return (
              <Text style={styles.textH3}>
                     {`platform: ${Api.platform}`}
              </Text>
              {/*<Text style={styles.textH3}>
                     {`platform: <deviceId>}`} --> How can I show deviceId here? Or device-specific info?
              </Text>*/}

        )
    }
}
export default ScreenHome;

https://developer.samsung.com/tv/develop/api-references/tizen-web-device-api-references/systeminfo-api
Tizen variable should be global in app.

Thank you @lukutism . How would that be used in the renative framework, like for instance the ScreenHome component?

Try
 componentDidMount(){ console.log(tizen.systeminfo)  }

Hello. I also wanted to be able to access the systeminfo API, but whenever I do something like of  alert(tizen.systeminfo) it does nothing, and whenever I try to use:
return new Promise((resolve, reject) => {
    resolve(tizen.systeminfo.getAvailableMemory())
})

It throws an error DetailReferenceError: tizen is not defined when running on the simulator. Any workarounds? How can I access this information?

Closing as answer has been provided, feel free to reopen if needed


Support default zoomLevel

Features:
I don't know if this is supported yet, but I have been trying to set a default zoomLevel. My first instinct was to set the scaleFactor prop, but to no avail. Something that worked somewhat was setting the scaleFactorMin, but this is not ideal since it does not allow the user to zoomOut further if necessary.
At the moment we use version 3.6.0. Is this issue something that is fixed in the lastest version? If not is this something that can be supported?

Can you not call zoomOnViewerCenter on ReactSvgPanZoom after the parent component has mounted?


Catch error?

How would you catch the error when the user doesn't have a webcam?

notsupported=“onUserHasNoWebcam”

Vincent Gabriel
Software Engineer
Please excuse my brevity, sent from my iPhone

On Dec 9, 2017, at 04:50, Md Mazedul Islam Khan<EMAIL_ADDRESS>wrote:
How would you catch the error when the user doesn't have a webcam?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@VinceG Can you please elaborate more or provide a complete example?

The component will emit an even if there is no webcam detected, all you have to do is listen on that event.

Vincent Gabriel
Software Engineer
Please excuse my brevity, sent from my iPhone

On Dec 9, 2017, at 10:25, Md Mazedul Islam Khan<EMAIL_ADDRESS>wrote:
@VinceG Can you please elaborate more or provide a complete example?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


appflowy: 0.7.1 -> 0.7.8

Update appflowy to the latest version

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Also you can add me as a maintainer if you like since I'm interested in keeping Appflowy up to date.

Hi, thanks a lot for your contribution ! I more than happy to hear that you're willing to get involved in maintaining appflowy, and I would like to add you as an extra maintainer. However, I couldn't find you in the maintainer list. Moreover, I think that it would be better (regarding what I've grasped of the nixpkgs workflow) for you to create a separated PR for that purpose !

Hi sorry for the late response.
I should be in the maintainers list since this commit was merged 3 weeks ago:
https://github.com/NixOS/nixpkgs/commit/3bdb9637ecd2cf126f329fa34367857a9dff11a6.
Maybe you have not pulled in the latest changes?

Well that's weird, my branch is old, but not that much either.
Never mind, I think creating a separated PR would still be better !

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4996


Allow use of ConnectionEvent in tests

Removed the final modifier on ConnectionEvent and made the constructor public so it can be used in tests.

Coverage remained the same at 93.635% when pulling 7707d01a952b0988f16c571509f397792062b6d5 on jebbench:remove_final_connectionEvent into 3d7c2c463ef96bfe77e4675c8610c4c107a5dc14 on nats-io:master.


GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

 Fast turn around! Thanks. It's been a while since I java'd but this looks like a reasonable approach. We'll see what Reuven thinks.

Run Java PreCommit

It looks like Reuven will be OOO and unable to review. @kennknowles could you take a look?

How come that the schema.proto (which I assume is the foundation for the SchemaApi used here) doesn't contain any notations about Options?


binary file included with source may violate licensing

The file reasoning/image/ype.pvm possibly contains SWI-Prolog code.
If true then redistributing that file might violate licenses of SWI-Prolog - e.g. if involving some modules licensed as GPL-2.

The file reasoning/image/ype.pvm in now removed
commit 715442630f40a7ace236890c77a6c3c62b5e45eb


chore(tests): add e2e tests to bootc repo

Signed-off-by: Vladimir Lazar<EMAIL_ADDRESS>What does this PR do?
Moves bootc e2e tests from PD to extension repo
What issues does this PR fix or reference?
https://github.com/containers/podman-desktop-extension-bootc/issues/117
https://github.com/containers/podman-desktop-extension-bootc/issues/162
How to test this PR?
Tests need to be run from PD repo with npm script after https://github.com/containers/podman-desktop/pull/5797 is merged into main repo

I've moved the test file into this repo as requested in https://github.com/containers/podman-desktop/pull/5797, obviously it cannot be compiled in this repo since it's missing all the dependencies, but the file is only stored here, it will be copied via npm script when executed from PD repo.

@cbr7 sign the commit please to pass DCO. Otherwise I would like to see this work on CI (if possible).

@odockal had to rebase to do it but managed it, but the linter requirements fail, which... of course they do since it's undefined code

@cdrage @deboer-tim I've added the test file to this repo as requested, but the linter build conditions all fail, which is normal since the rest of the test automation framework is in PD repo, so I'm not sure how you want to handle this in order to get it merged.
To be clear the current solution is just to store the tests in this repo, but CICD would pull both repos and copy the test file into the PD via npm script before running the tests.

@cdrage @deboer-tim I've added the test file to this repo as requested, but the linter build conditions all fail, which is normal since the rest of the test automation framework is in PD repo, so I'm not sure how you want to handle this in order to get it merged.
To be clear the current solution is just to store the tests in this repo, but CICD would pull both repos and copy the test file into the PD via npm script before running the tests.
Conversation and request for this can be found in containers/podman-desktop#5797

I'm assuming the long term plan is similar to the Podman Desktop API, where the Podman Desktop tests (or just the core test framework/classes) are published as their own module? If so, then at that point we'd be able to have a package.json dependency, yarn/lint would pick it up, and everything would be happy.
Prior to that point I'm ok with temporary ugliness to start getting the tests executing. e.g. I'd be ok to start if we filtered the /tests folder from linting and had a manual way to kick it off.  Then the tests themselves could be run and expanded on while we figure out how to automate and clean up.

@deboer-tim yes, that is correct. The plan is to move the test automation framework out of the podman desktop repo and publish it as it's own npm module, which can then be imported and used everywhere else.


[WEB] Color Family/Opacity of White doesn't change the background color of scaffold

Steps to Reproduce

Run flutter create bug.
Update the files as follows:Flutter Version 1.15.17
Add a backgroundcolor to a scaffold with a color of Colors.white30 or  any White that has an opacity.
Extra: Adding scaffoldBackgroundColor to Colors.white30 in MaterialApp doesn't work either.

Expected results:
A change of background color that uses Colors.white30
Actual results:
White Background color

Logs

  +34 ms] executing: [C:\Users\Vince\Downloads\Compressed\flutter_windows_v1.12.13+hotfix.8-stable\flutter/] git -c
log.showSignature=false log -n 1 --pretty=format:%H
[  +78 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +2 ms] 2294d75bfa8d067ba90230c0fc2268f3636d7584
[   +2 ms] executing: [C:\Users\Vince\Downloads\Compressed\flutter_windows_v1.12.13+hotfix.8-stable\flutter/] git fetch
https://github.com/flutter/flutter.git --tags
[+2873 ms] Exit code 0 from: git fetch https://github.com/flutter/flutter.git --tags
[   +3 ms] From https://github.com/flutter/flutter
            * branch                HEAD       -> FETCH_HEAD
[   +1 ms] executing: [C:\Users\Vince\Downloads\Compressed\flutter_windows_v1.12.13+hotfix.8-stable\flutter/] git
describe --match v*.*.* --first-parent --long --tags
[  +49 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[   +2 ms] v1.15.17-0-g2294d75bf
[  +11 ms] executing: [C:\Users\Vince\Downloads\Compressed\flutter_windows_v1.12.13+hotfix.8-stable\flutter/] git
rev-parse --abbrev-ref --symbolic @{u}
[  +39 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[   +1 ms] origin/beta
[   +1 ms] executing: [C:\Users\Vince\Downloads\Compressed\flutter_windows_v1.12.13+hotfix.8-stable\flutter/] git
ls-remote --get-url origin
[  +41 ms] Exit code 0 from: git ls-remote --get-url origin
[   +1 ms] https://github.com/flutter/flutter.git
[  +91 ms] executing: [C:\Users\Vince\Downloads\Compressed\flutter_windows_v1.12.13+hotfix.8-stable\flutter/] git
rev-parse --abbrev-ref HEAD
[  +39 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +1 ms] beta
[  +47 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[  +13 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +28 ms] executing: C:\Users\Vince\AppData\Local\Android\sdk\platform-tools\adb.exe devices -l
[  +27 ms] Exit code 0 from: C:\Users\Vince\AppData\Local\Android\sdk\platform-tools\adb.exe devices -l
[   +1 ms] List of devices attached
[  +15 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +235 ms] Generating
C:\Users\Vince\Documents\flutter_apps\bug\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[ +115 ms] Launching lib\main.dart on Chrome in debug mode...
[  +78 ms] Serving DevTools at http://<IP_ADDRESS>:50971

[   +7 ms] Updating assets
[ +106 ms] Syncing files to device Chrome...
[  +59 ms] Generating
C:\Users\Vince\Documents\flutter_apps\bug\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[  +48 ms] <- reset
[  +11 ms]
C:\Users\Vince\Downloads\Compressed\flutter_windows_v1.12.13+hotfix.8-stable\flutter\bin\cache\dart-sdk\bin\dart.exe
C:\Users\Vince\Downloads\Compressed\flutter_windows_v1.12.13+hotfix.8-stable\flutter\bin\cache\artifacts\engine\windows-
x64\frontend_server.dart.snapshot --sdk-root
C:\Users\Vince\Downloads\Compressed\flutter_windows_v1.12.13+hotfix.8-stable\flutter\bin\cache\flutter_web_sdk/
--incremental --target=dartdevc -Ddart.developer.causal_async_stacks=true --output-dill
C:\Users\Vince\AppData\Local\Temp\flutter_tool.1956e7e8-6d4f-11ea-8019-208984f64778\app.dill --libraries-spec
file:///C:/Users/Vince/Downloads/Compressed/flutter_windows_v1.12.13+hotfix.8-stable/flutter/bin/cache/flutter_web_sdk/l
ibraries.json --packages C:\Users\Vince\Documents\flutter_apps\bug\.packages -Ddart.vm.profile=false
-Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoi
d-closure-call-instructions --enable-asserts --track-widget-creation --filesystem-root
C:\Users\Vince\AppData\Local\Temp\flutter_tools.1956e7e9-6d4f-11ea-8019-208984f64778 --filesystem-scheme
org-dartlang-app --platform
file:///C:/Users/Vince/Downloads/Compressed/flutter_windows_v1.12.13+hotfix.8-stable/flutter/bin/cache/flutter_web_sdk/k
ernel/flutter_ddc_sdk.dill
[  +13 ms] <- compile org-dartlang-app:///web_entrypoint.dart
[+16355 ms] Syncing files to device Chrome... (completed in 16,477ms, longer than expected)
[   +1 ms] Synced 20.9MB.
[   +1 ms] <- accept
[ +536 ms] [CHROME]:
[   +1 ms] [CHROME]:DevTools listening on ws://<IP_ADDRESS>:51009/devtools/browser/96f7909a-039b-46bb-92ad-aaa6ab93a0ad
[+7259 ms] Debug service listening on ws://<IP_ADDRESS>:51051/Auh8cJOxiHs=

[ +379 ms] Debug service listening on ws://<IP_ADDRESS>:51051/Auh8cJOxiHs=
[   +2 ms] Warning: Flutter's support for web development is not stable yet and hasn't
[        ] been thoroughly tested in production environments.
[        ] For more information see https://flutter.dev/web
[   +2 ms]   To hot restart changes while running, press "r". To hot restart (and refresh the browser), press "R".
[   +1 ms] For a more detailed help message, press "h". To quit, press "q".

Analyzing bug...
No issues found! (ran in 2.1s)

[√] Flutter (Channel beta, v1.15.17, on Microsoft Windows [Version 10.0.18363.720], locale en-PH)
    • Flutter version 1.15.17 at C:\Users\Vince\Downloads\Compressed\flutter_windows_v1.12.13+hotfix.8-stable\flutter
    • Framework revision 2294d75bfa (2 weeks ago), 2020-03-07 00:28:38 +0900
    • Engine revision 5aff311948
    • Dart version 2.8.0 (build 2.8.0-dev.12.0 9983424a3c)

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at C:\Users\Vince\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 3.6)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 44.0.2
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)

[√] VS Code (version 1.43.1)
    • VS Code at C:\Users\Vince\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.8.1

[√] Connected device (2 available)
    • Chrome     • chrome     • web-javascript • Google Chrome 80.0.3987.149
    • Web Server • web-server • web-javascript • Flutter Tools

I'll try Switching to master channel if it fix the problem.

I found a fix/work around.  I had to change the color similar to Colors.white30. If anyone wants to close this, feel free. But the bug still remains to web platform. as for the mobile, it's fine anyway.


cannot import name '_validate_lengths'

Hello,
I am getting the following error:
cannot import name '_validate_lengths'

I think it relates to scikit-image

@stylianos-kampakis
https://github.com/slundberg/shap/issues/206#issuecomment-495263043

Thanks @nickwan! Currently we use skimage just for the color conversion code...so perhaps we can can find a way to do those conversions without getting the whole skimage dependency. That might be the best way to address these things long term.


Explorer & Designer not working

Describe the bug
Explorer & Designer do not work
To Reproduce

I have two tables, test & tbl1, it is shown below

when i open explorer, it wont show any tables, and in the designer if i create one using '+' symbol, immediately it closes, and not showing the field creation.

Expected behavior
need to show the explorer & designer to create tables and fields graphically.
and also check visualizer.
Environment (you can view the current version under Settings):

OS: windows 11
Version: surrealist 1.7.2

I'm having the same issue on macOS with M2. Versions 1.7.2 and 1.7.1. Database server is a remote one hosted via Fly.

@leefordjudes @myrkvi Could it be that you are running SurrealDB nightly?

@macjuul: No, I'm running the surrealdb/surrealdb:latest Docker image.

@leefordjudes @myrkvi Could it be that you are running SurrealDB nightly?

yes, i am running nightly version
1.0.0-beta.9+20230612.5c07a7b

Talked it over on the Discord server. The issue for me was that a table had a defined field of the type record(), which works with the version of SurrealDB on the server, but not for the local one that is running embedded in Surrealist. I.e. the syntax for that type has since changed.
Thank you, @macjuul! :)

@leefordjudes @myrkvi Could it be that you are running SurrealDB nightly?

yes, i am running nightly version 1.0.0-beta.9+20230612.5c07a7b

There's been a recent breaking change in SurrealDB nightly which has broken compatibility with Surrealist. Theres currently a patch version made by @bibaswan-bhawal which is compatible with nightly.
I'll see if its possible to support both ways and might include it in the next release if possible.

It might be possible if we query the DB version and conditonally pick the key names

It might be possible if we query the DB version and conditonally pick the key names

If I'm not mistaken it could be as simple as e.g. info.tables || info.tb, however I haven't had much time to look at your fork yet so I might be wrong


broken links and missing rvv_intrinsic_gen.py and misc inconsistencies

The files in the intrinsic_functions dir claim that they were generated by rvv_intrinsic_gen.py but I can find no such file.  I checked multiple riscv github trees and multiple compiler source trees.  It shouldn't be this hard to find it.
Most of the links between rvv-instrinsic-api.md and the intrinsic_functions/* files are broken.  Looks like the old file 04_* disappeared.  Also, the section labels in the instrinsic_functions files now have section numbers prepended.  And most (but not all) section labels changed -functions to -operations.  None of these changes are reflected in the rvv-instrinsics-api.md file.
I have a patch that mostly fixes this, except I ran into too many inconsistencies that I can't fix without the missing rvv_intrinsic_gen.py file and some discussion.
There are duplicate labels.  For instance
rohan:2097$ grep '###' * | grep 'unit-stride-op'
02_vector_loads_and_stores_functions.md:### [Vector Unit-Stride Load Functions](../rvv-intrinsic-api.md#74-vector-unit-stride-operations):
02_vector_loads_and_stores_functions.md:### [Vector Unit-Stride Store Functions](../rvv-intrinsic-api.md#74-vector-unit-stride-operations):
rohan:2098$

and
rohan:2071$ grep '###' * | grep loadstore
02_vector_loads_and_stores_functions.md:### [Vector Strided Load Functions](../rvv-intrinsic-api.md#75-vector-strided-loadstore-operations):
02_vector_loads_and_stores_functions.md:### [Vector Strided Store Functions](../rvv-intrinsic-api.md#75-vector-strided-loadstore-operations):
02_vector_loads_and_stores_functions.md:### [Vector Indexed Load Functions](../rvv-intrinsic-api.md#76-vector-indexed-loadstore-operations):
02_vector_loads_and_stores_functions.md:### [Vector Indexed Store Functions](../rvv-intrinsic-api.md#76-vector-indexed-loadstore-operations):
rohan:2072$

but rvv-intrinsic-api.md expects load and store to have separate labels.
Also, there is confusion with binary and unary bitwise operations which have the same section label.
rohan:2077$ grep '###' * | grep bitwise-logical
05_vector_integer_arithmetic_functions.md:### [Vector Bitwise Logical Functions](../rvv-intrinsic-api.md#125-vector-bitwise-logical-operations):
05_vector_integer_arithmetic_functions.md:### [Vector Bitwise Logical Functions](../rvv-intrinsic-api.md#125-vector-bitwise-logical-operations):
rohan:2078$

There are missing labels.  For instance
rohan:2072$ grep '###' * | grep '()'
03_vector_load_store_segment_instructions_zvlsseg.md:### [Vector Unit-Stride Segment Load Functions]():
03_vector_load_store_segment_instructions_zvlsseg.md:### [Vector Unit-Stride Segment Store Functions]():
03_vector_load_store_segment_instructions_zvlsseg.md:### [Vector Strided Segment Load Functions]():
03_vector_load_store_segment_instructions_zvlsseg.md:### [Vector Strided Segment Store Functions]():
03_vector_load_store_segment_instructions_zvlsseg.md:### [Vector Indexed Segment Load Functions]():
03_vector_load_store_segment_instructions_zvlsseg.md:### [Vector Indexed Segment Store Functions]():
rohan:2073$

There are section labels with corrupted back pointers.
rohan:2084$ grep '###' * | grep -v '()' | grep -v 'md#'
11_miscellaneous_vector_functions.md:### [Vector LMUL Extension Functions](../rvv-intrinsic-api.mdvector-lmul-extension-and-truncation-functions):
11_miscellaneous_vector_functions.md:### [Vector LMUL Truncation Functions](../rvv-intrinsic-api.mdvector-lmul-extension-and-truncation-functions):
rohan:2085$

This is also yet another duplicate label.
And while most labels had the "-functions" changed to "-operations", some still say -operations, and some now say neither, they just lost their suffix.  This can be handled without broken links.  This is just more of a quality-of-implementation issue as the naming differences make it harder to maintain the docs.
rohan:2091$ grep '###' * | grep -v '()' | grep -- -operations | wc
     58     320    9346
rohan:2092$ grep '###' * | grep -v '()' | grep -- -functions | wc
      8      39    1113
rohan:2093$ grep '###' * | grep -v '()' | grep -v -- -functions | grep -v -- -operations | wc
     14      86    1979
rohan:2094$

There are also section labels that are in the intrisics files but not referenced in the rvv-vector-api.md file.
11_miscellaneous_vector_functions.md:### [Vector Insertion Functions](../rvv-intrinsic-api.md#vector-insertion-functions):
11_miscellaneous_vector_functions.md:### [Vector Extraction Functions](../rvv-intrinsic-api.md#vector-extration-functions):

Also, extraction is misspelled here.
The labels that start with a number aren't working for me.  They go to the right file, but not the right label inside that file.  It isn't obvious what is wrong, but maybe they aren't being parsed as intended.  The labels that don't start with numbers do work.

This is part of our release milestone to open-source the intrinsic generator in SiFive. We will resolve this in the v1.0 release.


Setup ExternalName instances only for specified ports

For https://github.com/istio/istio/issues/13479
Not sure if this is the right way to go

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio
52cde0030c46937b4a350b681c21f5806d419b35
link
/test integ-istioio-k8s-tests_istio

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

/retest

sorry, i missed this pr.

/cherrypick release-1.5

@howardjohn: new pull request created: #20889

In response to this:

/cherrypick release-1.5

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