Re-instate pagination

The new API uses cursor based pagination which should give use what we need to re-implement the pagination options and methods in v2.

Still working on this.

Still working on this.

Please :)

Hi,
Any development? tks

Hi, Could you please let me know if the next() method has been implemented in v2? Thanks.

Hey everyone! Thanks for the patience on this feature — it's taken me a while to find some spare time to work on this.
Good news though: pagination will be available in the next release! 🎉
The v2 version of pagination will use the same API that was used in v1, while addressing some of the quirks that v1 had in regards to the limit option when used with pagination.
I'll have more details available once the next release is published.
Thanks!

Hi,
Great news. thank you very much for your support!

Hey folks! Just wanted to let everyone know that v2.0.0-rc3 is now available, and includes pagination support. (Sorry it took me so long!)
The v2 version of pagination uses the same two methods that v1 used:

hasNext() -> bool - returns true/false if there are additional images that can be shown.
next() - fetches the next set of images.

In addition, v2.0.0-rc3 adds a new option: apiLimit: number.
This option can be used to control how many images are requested from the Instagram API, overriding the limit option when set. This is especially useful when using the filter option, where you may want to display 10 images, but need to fetch more than 10, since some will be filtered out.

Unused Image Pooling
Internally, Instafeed.js will pool unused images (when apiLimit > limit), and transparently treat those unused images as "pagination" data.
So if you set apiLimit: 10 and limit: 1, Instafeed.js will fetch up to 10 images from the Instagram API, and then insert 1 into the page, saving 9 into the internal pool.
At that point, hasNext() will return true, and next() will continually fetch 1 more image (based on limit: 1) from the 9 unused images, until 0 are left.
Once all the pooled images have been displayed, hasNext() will return true if the Instagram API provided a pagination cursor during the initial request, and next() will fetch the next set of 10 images (based onapiLimit: 10) from the API, starting the process over.
Hopefully this extra functionality can cover some edge cases that v1 had!

Please give RC3 a shot and let me know if you run into any issues!

Hey folks! Just wanted to let everyone know that v2.0.0-rc3 is now available, and includes pagination support. (Sorry it took me so long!)
The v2 version of pagination uses the same two methods that v1 used:

hasNext() -> bool - returns true/false if there are additional images that can be shown.
next() - fetches the next set of images.

In addition, v2.0.0-rc3 adds a new option: apiLimit: number.
This option can be used to control how many images are requested from the Instagram API, overriding the limit option when set. This is especially useful when using the filter option, where you may want to display 10 images, but need to fetch more than 10, since some will be filtered out.
Unused Image Pooling
Internally, Instafeed.js will pool unused images (when apiLimit > limit), and transparently treat those unused images as "pagination" data.
So if you set apiLimit: 10 and limit: 1, Instafeed.js will fetch up to 10 images from the Instagram API, and then insert 1 into the page, saving 9 into the internal pool.
At that point, hasNext() will return true, and next() will continually fetch 1 more image (based on limit: 1) from the 9 unused images, until 0 are left.
Once all the pooled images have been displayed, hasNext() will return true if the Instagram API provided a pagination cursor during the initial request, and next() will fetch the next set of 10 images (based onapiLimit: 10) from the API, starting the process over.
Hopefully this extra functionality can cover some edge cases that v1 had!
Please give RC3 a shot and let me know if you run into any issues!

Good News!
Thank you, I will try to implement!


Which front end framework should we use?

My initial thought is to use Flutter, but there are probably a number of other options which may be easier to work with?
We should stay within the following constraints :

The framework should support iOS and android
The framework should have python bindings, or be easily controllable through python

Two open source python based frameworks that come to mind are:

Beeware

I have an affinity for beeware since I've contributed to this in the past. Generally, the support for different native elements are pretty limited, but we may not need some of the advanced elements anyway.

Kivy
Kivy offers a uniform interface for all applications and better element support than the beeware project


Masks and other jquery interactions with inputs don't work inside wizard

I've found an issue when I tried to use some scripts in input texts inside the Wizard div.
When I try to interact with textboxes and jquery functions, like a Datepickers, maskedits, autocompletes, these scripts don't work inside the wizard area. It's not cause any errors, but simply don't work.
Checking the jquery.steps.js code, I tought I've found the cause.
In this part of code:
// Transform the wizard wrapper and remove the inner HTML
wizard.attr("role", "application").empty().append(stepsWrapper).append(contentWrapper)
.addClass(options.cssClass + " " + options.clearFixCssClass + verticalCssClass);
the Wrappers are removed and after appended again. I've removed the empty() command to check, and created two forms.
Other test I made, was add the script to the textbox after this line. So, It works fine. But I added part of my code to do it, and it's not a good practice.
So, basically, on the page, outside wizard, all of scripts and textboxes works very well. Inside the wizard, all of then stops working.
I've created a Fiddler with an example:
http://jsfiddle.net/strikegamer/3bWm3/
Some idea how I can fix this? Or is a real bug?

@rstaib I tried as you've mentioned in the StackOverflow answer.  First jQuery steps then the  google places-autocomplete but it simply does nothing.
Any help regarding this ??

First you need to initiate the steps and then execute the code.

Here you find the fixed example on JsFiddler.
Thanks!!!


Travis ci icon

Hi :)
Can you change the travis icon to puth the one they have now  ?
I have a link to that :) https://www.dropbox.com/s/tmzyv2h69cgjxu8/travis-ci (1).svg?dl=0
thanks a lot :D

Originally, file-icons did use Travis CI's logo as an icon. Users found the icon difficult to distinguish at such a small size, and in some cases, it was almost unrecognisable. Using the letter T instead proved to be a satisfactory alternative.
This was a long time ago, and the original Travis icon that was originally used was dropped from the icon-font before my involvement with the project started. However, you can still use the SVG that you've provided by adding the following snippet to your stylesheet:
.travis-icon::before {
	content: "";
	background: url("/PATH/TO/YOUR.SVG") center no-repeat;
	background-size: contain;
}

I'm unable to access Atom at the moment, so I can't double-check the code above to verify that it displays correctly. So if you have any further problems adding it, please let me know. =)
By the way, you don't need to upload SVG files to Dropbox or any other file uploading service. =) You can embed the SVG's source code with Markdown:
```svg
*copy+paste*
```

Only upload the file if the SVG is truly massive in size (over 1.0 MBs, for example). You'll sometimes find SVGs that have been improperly exported from graphics editing software, which can sometimes grow to ridiculous sizes.

Hi :)
Thanks for the answer, I will believe you on the size of the icon and save some troubles for my eyes :D
Cheerz


long_description_content_type=text/markdown doesn't always work

This page does not show correctly rendered markdown: https://pypi.org/project/datasette/

The setup.py file looks like this:
https://github.com/simonw/datasette/blob/fb988ace7c7e2bee5ac142a0eab22431d0675a77/setup.py#L13-L18
setup(
    name='datasette',
    description='An instant JSON API for your SQLite databases',
    long_description=get_long_description(),
    long_description_content_type='text/markdown',
    author='Simon Willison',

According to @ambv on Twitter this is caused by a bug: https://twitter.com/llanga/status/984866099886895104 "There's a bug now where you need to upload just the tar.gz first with Twine and only then upload the rest of the files."

@di will know which bug I'm talking about.

Yep, this is due to building with an old version of wheel which incorrectly sets the Metadata-Version field. Should be fixed by a pip install wheel==0.31.0 and then building/uploading a new distribution.

That worked - I ran pip install wheel==0.31.0 before doing python setup.py bdist_wheel and the result was this page with the markdown correctly formatted: https://pypi.org/project/datasette/

I might have a similar problem: https://pypi.org/project/shortcountrynames/
The markdown rendering worked for me in other projects and I think I have wheel=0.31.0
Requirement already up-to-date: wheel in ./venv/lib/python3.6/site-packages (from -r requirements.txt (line 3)) (0.31.0)
Repo: https://github.com/rgieseke/shortcountrynames

@rgieseke Lookng at the latest release for that project, the Description-Content-Type field is not making it to PyPI.
Can you confirm that you have setuptools>=38.6.0 and twine>=1.11.0 as well?

I have the same problem: https://pypi.org/project/ConceptNet/5.6.2/ . Repo: https://github.com/commonsense/conceptnet5
I have setuptools 39.0.1, twine 1.11.0, and wheel 0.31.0, and I ran python setup.py sdist upload.
I even deleted ConceptNet 5.6.1 and incremented the version to 5.6.2 when I updated all the above dependencies. However, I'm not just going to keep incrementing the version number for the sake of PyPI.

@di Updating setuptools did the trick! Thanks for the quick reply and so much for the PyPI update!
@rspeer You can use the https://test.pypi.org/ instance to test as well ... (and delete tags later or re-try)

Apparently python setup.py sdist upload is the problem. I will open a new issue about the fact that it's extremely non-obvious that you have to use "twine". (I know there's documentation that says so... but it's not the documentation that's linked to when you're looking for how to set your project description.)

@rspeer Can you link us to the documentation that showed you to use python setup.py sdist upload?

https://docs.python.org/3.6/distutils/packageindex.html#the-upload-command
Also a decade of habit. If you want to change people's habits, you could at least tell them they need to change.

To clarify something: I'm not claiming that PyPI is linking to the Python documentation. PyPI links to packaging.python.org, of course. However, one way that people learn about PyPI in the first place is the Python documentation, where PyPI is described as that place that setup.py upload uploads to.
If you want to update people's understanding about how to upload Python packages, talking about it on your own blog and mentioning Twine twice on a very long documentation page isn't enough. You need to make getting the new tools part of the new PyPI user experience.

I actually have this problem right now, and using both wheel==0.31.0 and wheel==0.32.1 (latest at the time of posting) both break the markdown formatting

Hi @osilkin98, can you link to the release with a broken description? Can you tell us how you uploaded the release to PyPI?

@di I was typing out a response documenting how to replicate the issue and in doing so I realized that the version of wheel that was being used during the setup was installed to python3.6's packages, but the one I installed and upgraded was installed to python3.7.
I fixed the issue simply by verbosely running python -m pip install --upgrade wheel in my virtual environment. My apologies for any confusion.

This problem is still occurring when running python setup.py sdist bdist_wheel and twine upload from a windows machine.
Tested ubuntu 18.04 and windows 10.  Ubuntu uploads everything fine, but running the exact same commands from a windows machine causes the above issue to appear with the exact same files.
setuptools, wheel, and twine are all at or beyond the levels specified in the above comments, and are at the same level for both machines.

@scruffystuffs Can you point me to a distribution on PyPI that you've uploaded that has this problem?

Uploaded from Windows
Uploaded from Ubuntu
The files for these distributions should be identical, other than the version number, yet they render entirely differently on the project page.
If any more info is needed, let me know and I will be happy to provide it.

@scruffystuffs Looking at the metadata of the source distribution of your package, it has Windows-style line endings in the Description, so it looks like you've having the same issue as https://github.com/pypa/setuptools/issues/1440

I'm still experiencing this issue trying to upload a package on Linux (Ubuntu):
Python 3.6.8
pip 19.3.1
twine 2.0.0
setuptools 41.6.0
wheel 0.33.6

setup.py
      long_description=readme,
      long_description_content_type="text/markdown",

running:
python3 setup.py sdist bdist_wheel
python3 -m twine upload --repository-url https://upload.pypi.org/legacy/ dist/*

error
HTTPError: 400 Client Error: The description failed to render in the default format of reStructuredText. See https://pypi.org/help/#description-content-type for more information. for url: https://upload.pypi.org/legacy/

@di please advise

@wesinator Can you attach the distributions you're trying to upload?

@wesinator Can you attach the distributions you're trying to upload?

attached:
domainbigdata-0.1.tar.gz
domainbigdata-0.1-py3-none-any.whl.zip

The problem is likely in your license= argument. It seems to include the entire text of the GPL v3, which contains double newlines. That breaks setuptools by rendering the metadata invalid and unparseable.
It's possible to indicate that the license is GPL v3 in a machine-readable way using a classifier such as License :: OSI Approved :: GNU General Public License v3 or later (GPLv3+) (which I see this project includes).  The license= argument can then be omitted (or a simple summary), as it is meant to be

Text indicating the license covering the distribution where the license is not a selection from the “License” Trove classifiers"

The problem is likely in your license= argument. It seems to include the entire text of the GPL v3, which contains double newlines. That breaks setuptools by rendering the metadata invalid and unparseable.
It's possible to indicate that the license is GPL v3 in a machine-readable way using a classifier such as License :: OSI Approved :: GNU General Public License v3 or later (GPLv3+) (which I see this project includes). The license= argument can then be omitted (or a simple summary), as it is meant to be

Text indicating the license covering the distribution where the license is not a selection from the “License” Trove classifiers"

@jamadden I already have that exact classifier - https://github.com/wesinator/domainbigdata-python/blob/c4c3b12a37ba6e86931f0c4575406cf42cdcd090/setup.py#L23
also, not sure why the error would say description when the issue is actually the license.
If that's true then the error needs to be way more granular so I know what the f is actually happening.

@wesinator It's a bug: https://github.com/pypa/setuptools/issues/1390

The problem is likely in your license= argument. It seems to include the entire text of the GPL v3, which contains double newlines. That breaks setuptools by rendering the metadata invalid and unparseable.

btw, the license was pulled directly from https://www.gnu.org/licenses/gpl-3.0.txt
Ok, removing license seems to have fixed it.
@jamadden thanks for the tip

running into similar issues with my team for relative links

Relative links are not currently supported: https://github.com/pypa/readme_renderer/issues/163


ios build: module 'audioplayers' not found

Hello, when i run the command "flutter build ios" or try to "Archive", i get the same error that some of you guys has been faced of: "module audio players not found".
I know there is already four closed issues about that error, but none of the solutions has worked for me. Luan, you've said that it could be relationed with project's configurations. Can you give me a example or more informations about that? . I'm truly desperate.

OS: ios.
OS version: Big Sur.
flutter version: 1.22.4.
audioplayers version: 17.

Try:
flutter clean
rm -rf build
rm -rf ~/.pub-cache

flutter pub get

And try running again. That seems like an env issue. Take a look at our new github action, it builds the example app correctly on ios. Can you build the example app?

Added a section on our FAQ for this since it's a very common issue people have: https://github.com/luanpotter/audioplayers/pull/834

Closing due inactivity, if there is more info that you can add to the issue, comment here and we can re open the issue.

there are still problems on audioplayers: ^0.18.3

I've figured out what was going on. When you run the pod install command, the dependencies are not added on podfile. You need to delete the podfile previously generetated, open the project on vscode, run the flutter pub get command, and then run the app. When you run the app, the podfile is created with the dependencies and you will be able to build the project on xcode. basically, if you use Windows to developer your app, you need tu run the app on the Mac before you build it on xcode.


[BUG] Bloxstrap doesnt start up, gets stuck in"Configuring Roblox"

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
Just about, 2-3 hours ago, my roblox was doing find, now when i started up it gets stuck in Configuring Roblox, and it doesnt stop. I've seen some reports about this and havent seen anything helpful.

Bloxstrap Log
N/A

Any way to fix this? Uninstalling and re-installing didnt work aswell.


Unable to create WASM/WASI node pool using az aks nodepool add

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks nodepool add Extension Name: aks-preview. Version: 0.5.94.
Errors:
The command failed with an unexpected error. Here is the traceback:
cannot import name 'case_insensitive_dict' from 'azure.core.utils' (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\azure\core\utils\__init__.pyc)
Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 112, in handler
  File "C:\Users\raorugan\.azure\cliextensions\aks-preview\azext_aks_preview\_client_factory.py", line 35, in cf_agent_pools
    return get_container_service_client(cli_ctx).agent_pools
  File "C:\Users\raorugan\.azure\cliextensions\aks-preview\azext_aks_preview\vendored_sdks\azure_mgmt_preview_aks\_container_service_client.py", line 375, in agent_pools
    from .v2022_07_02_preview.operations import AgentPoolsOperations as OperationClass
  File "C:\Users\raorugan\.azure\cliextensions\aks-preview\azext_aks_preview\vendored_sdks\azure_mgmt_preview_aks\v2022_07_02_preview\__init__.py", line 9, in <module>
    from ._container_service_client import ContainerServiceClient
  File "C:\Users\raorugan\.azure\cliextensions\aks-preview\azext_aks_preview\vendored_sdks\azure_mgmt_preview_aks\v2022_07_02_preview\_container_service_client.py", line 19, in <module>
    from .operations import AgentPoolsOperations, FleetMembersOperations, FleetsOperations, MaintenanceConfigurationsOperations, ManagedClusterSnapshotsOperations, ManagedClustersOperations, Operations, PrivateEndpointConnectionsOperations, PrivateLinkResourcesOperations, ResolvePrivateLinkServiceIdOperations, SnapshotsOperations, TrustedAccessRoleBindingsOperations, TrustedAccessRolesOperations
  File "C:\Users\raorugan\.azure\cliextensions\aks-preview\azext_aks_preview\vendored_sdks\azure_mgmt_preview_aks\v2022_07_02_preview\operations\__init__.py", line 9, in <module>
    from ._operations import Operations
  File "C:\Users\raorugan\.azure\cliextensions\aks-preview\azext_aks_preview\vendored_sdks\azure_mgmt_preview_aks\v2022_07_02_preview\operations\_operations.py", line 19, in <module>
    from azure.core.utils import case_insensitive_dict
ImportError: cannot import name 'case_insensitive_dict' from 'azure.core.utils' (C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\azure\core\utils\__init__.pyc)

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az aks nodepool add --resource-group {} --cluster-name {} --name {} --node-count {} --workload-runtime {}

Expected Behavior
Environment Summary
Windows-10-10.0.22621-SP0
Python 3.10.4
Installer: MSI

azure-cli 2.37.0 *

Extensions:
aks-preview 0.5.94
containerapp 0.3.8

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

route to CXP team

@raorugan Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update.

@raorugan I am unable to reproduce this issue at my end. I could see that you are using an older version of azure-cli 2.37.0 * . Could you please use the most recent version of AzCLI and test again ?
Also I would recommend you to use the most recent version of aks-preview extension.

az extension update -n aks-preview

this was helpful! we can close the issue

@raorugan Thanks for getting back. We will now proceed with closure of this GitHub issue. If you need any further assistance on this issue in future, please feel free to reopen this thread. We would be happy to help.


Tutorial about using GloBI to create species interaction networks

Tutorial should be published on website of Alien CSI, but still it is not and no idea when it will be uploaded.
@jrhillae proposes to publish it on our INBO tutorial website. It is deposited already on zenodo.
@jrhillae: could you please provide the link? Is it a PDF I suppose?
As I am a fan of the DRY (Don't Repeat Yourself) principle, a very brief tutorial mentioning the link to the zenodo document will be enough. We do something similar in some other tutorials.

@damianooldoni : This is the link (automatically resolving the latest version) : https://doi.org/10.5281/zenodo.7576207

Thanks @jrhillae. Great. I give you a 🟢 to add a new short INBO tutorial 👍
Technically speaking, writing a tutorial is simple, especially in this case. Please, follow the instructions and add me as reviewer of the PR when done. Thanks a lot for your contribution.


Feat/pristine

fixes #6

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


chore(main): release metamask-testing-tools 1.2.4

:robot: I have created a release beep boop
1.2.4 (2024-05-27)
Bug Fixes

fix pnpm mismatch (893db70)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/hugomrdias/metamask/releases/tag/metamask-testing-tools-v1.2.4 :sunflower:


v0.1.6: Overriding sub-setting category nulls other inherited settings (#4348)

Very similar to the issue described in https://github.com/astral-sh/ruff/issues/4348. I have a root dir with a file that looks a bit like:
proj/.ruff.toml:

[lint.isort]
section-order = ["standard-library", "common_pkgs", "third-party", "same_subcomp"]
[lint.isort.sections]
"common_pkgs" = ["numpy", "behave", ]
"same_subcomp"= []

proj/subdir/.ruff.toml:

extend = "../.ruff.toml"
[lint.isort.sections]
"same_subcomp" = ["<pattern>"]

Using a command such as ruff proj/subdir/<some_file> returns me an error like:

warning: section-order contains unknown section: UserDefined("common_pkgs")

Which means that isort.sections is being completely overwritten, when I expected to only overwrite the value of "same_subcomp". I can also confirm that the sorting of imports is not behaving as expected, as it will put numpy in the middle of the third party, when I want it to have its own block.
If this is the intended behavior, which I assumed it wasn't given issue #4348, is there a simple way I can achieve my intended behavior without copying the definition of common_pkgs to the .ruff.toml in every subdir?
Thanks in advance.

Yeah, I think this should probably be considered a bug.

Hi, I see that the PR is approved and checks are green. What would be the ETA on this bugfix delivery?

@LTourinho -- Sorry for the delay, we decided to defer this to v0.4 because we need to figure out a way to allow extended configs to unset these.

@LTourinho -- Sorry for the delay, we decided to defer this to v0.4 because we need to figure out a way to allow extended configs to unset these.

No problem. Is the suggestion of setting to an "empty" object too bad in that regard? (The comment I made on the PR)

Hi @charliermarsh, as the PR was closed, what are the plans on fixing this issue?

Hi @charliermarsh, as the PR was closed, what are the plans on fixing this issue?

Sorry that was not intentional. I cleaned up my stale branches and thought it's safe to delete any branch starting with charliemarsh. I restored the branch and reopened the PR.

Thanks Micha, I meant to ask about that too :)

Hi guys, is there a reason this was postponed to 0.5? No agreement on how to unset values?

Hi guys, is there a reason this was postponed to 0.5? No agreement on how to unset values?

There was no specific reason other than time constraints.

0.4 was focused on the parser, we punted other breaking changes to 0.5 which we expect to release in the next few weeks.

To confirm the behavior change. We'll now start merging the following options:

per_file_ignores
extend-per-file-ignores (Do we still need the extend?)
flake8_import_convention_options.aliases
flake8_import_convention_options.extend_aliases
flake8_import_convention_options.banned_aliases
flake8_import_convention_options.banned_from
flake8_tidy_imports.banned_api
isort.sections

I'm not sure whether the new behavior is correct for all settings, or at least it becomes less clear why we would still need the extend- options when "extending" becomes the new default for tables.
The new CombineOptions allows us to use different merging behaviors for different settings, but I'm worried this will be confusing.

Hi, I see that the previous solution pull request was closed. Is there no alternatives? Is this being picked up in any way?

Unfortunately, I know of no alternative. We aren't actively working on this right now but are open to ideas. As little as I like that, a short-term solution could be an extend option. This comment explains why the other PR was closed)

Could there be a different keyword?
Then the breaking functionality would only happen to those who explicitly use the new keyword.

Could there be a different keyword? E.g.: merge-into = "../.base_ruff.toml"

I would prefer not to but I won't rule it out. Either way, deciding on adding a different extension strategy isn't something we want to do slightly because it adds a lot of complexity and also makes it harder for users to understand what's happening.

Related (duplicate?) #7696


Filter with "Dynamically search all filter values" enabled selects all values if you select only one specific

There is a dashboard with filters. There is a filter with "Dynamically search all filter values" - it is important to enable this feature for the filter.  If you type an exact value in the filter box (when only one value is suggested), and then select the suggested value, all values will be selected instead.
This error didn't exist in Superset 1.5.3 but exists in 2.1.0.
How to reproduce the bug

Go to SQL Lab
Type a query:

select ('Chip') as name
union all
select ('Dale') as name

Save as a dataset
Create an empty dashboard
Add a filter on column 'name' to the dashboard
Enable "Dynamically search all filter values" for the filter and save fiters
Now type "Chip" in the filter box - its is important to enter enough characters to only one suggestion to be made. If more the one suggestions are shown, the bug doesn't reproduce.
In a moment all values will be selected instead of "Chip", which is not correct.

Expected results
Only one value should be selected
Actual results
All values are selected instead
Screenshots

Environment

browser type and version: Chrome 112.0.5615.138
superset version: 2.1.0 (doesn't reproduce in 1.5.3)
python version: 3.8
node.js version: N/A
any feature flags active: None

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[X] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[X] I have reproduced the issue with at least the latest released version of superset.
[X] I have checked the issue tracker for the same issue and I haven't found one similar.

We encountered the same.
When the Dynamically search all filter values is ticked in the filter, input a unique value results in a thousand being selected.
When activated, it makes a check on the cache
{
  "datasource": {
    "id": 1997,
    "type": "table"
  },
  "force": false,
  "queries": [
    {
      "filters": [
        {
          "col": "OFFER_ID",
          "op": "ILIKE",
          "val": "%1aad4ce5a3168f49%"
        }
      ],
      "extras": {
        "having": "",
        "where": ""
      },
      "applied_time_extras": {},
      "columns": [
        "OFFER_ID"
      ],
      "metrics": [],
      "orderby": [
        [
          "OFFER_ID",
          true
        ]
      ],
      "annotation_layers": [],
      "row_limit": 1000,
      "series_limit": 0,
      "order_desc": true,
      "url_params": {
        "native_filters_key": "hZfvKcnkPHcIk8mx_aRM8m-CyMqIJ47t0AxfXiy-mfKuhBNmmL3WEc0wD8-ufqmX"
      },
      "custom_params": {},
      "custom_form_data": {}
    }
  ],
  "form_data": {
    "enableEmptyFilter": false,
    "defaultToFirstItem": false,
    "multiSelect": true,
    "searchAllOptions": true,
    "inverseSelection": false,
    "datasource": "1997__table",
    "groupby": [
      "OFFER_ID"
    ],
    "adhoc_filters": [],
    "extra_filters": [],
    "extra_form_data": {},
    "metrics": [
      "count"
    ],
    "row_limit": 1000,
    "showSearch": true,
    "url_params": {
      "native_filters_key": "hZfvKcnkPHcIk8mx_aRM8m-CyMqIJ47t0AxfXiy-mfKuhBNmmL3WEc0wD8-ufqmX"
    },
    "inView": true,
    "viz_type": "filter_select",
    "type": "NATIVE_FILTER",
    "force": false,
    "result_format": "json",
    "result_type": "full"
  },
  "result_format": "json",
  "result_type": "full"
}

Response:
{"result": [{"cache_key": "4e97d83bceb40003f1bd3becb38d00ef", "cached_dttm": "2023-05-30T14:30:54", "cache_timeout": 86400, "applied_template_filters": [], "annotation_data": {}, "error": null, "is_cached": true, "query": "SELECT \"OFFER_ID\" AS \"OFFER_ID\"\nFROM\n  (SELECT *\n   FROM reporting_daily) AS virtual_table\nWHERE lower(\"OFFER_ID\") LIKE lower('%1aad4ce5a3168f49%')\nGROUP BY \"OFFER_ID\"\nORDER BY \"OFFER_ID\" ASC\nLIMIT 1000", "status": "success", "stacktrace": null, "rowcount": 1, "from_dttm": null, "to_dttm":<PHONE_NUMBER>000.0, "label_map": {"OFFER_ID": ["OFFER_ID"]}, "colnames": ["OFFER_ID"], "indexnames": [0], "coltypes": [1], "data": [{"OFFER_ID": "1aad4ce5a3168f49"}], "result_format": "json", "applied_filters": [{"column": "OFFER_ID"}], "rejected_filters": []}]}

Environment

Google Chrome - Version 113.0.5672.126 (Official Build) (arm64)
Superset Version: 2.1.0 via Helm
Feature flags:

  FEATURE_FLAGS = {
          "ALERT_REPORTS": True,
          "ALLOW_ADHOC_SUBQUERY": True,
          "ENABLE_TEMPLATE_PROCESSING": True,
          "DASHBOARD_NATIVE_FILTERS": True,
          "DASHBOARD_CROSS_FILTERS": True,
          "DASHBOARD_CACHE": True,
          "GENERIC_CHART_AXES": True,
          "SQLLAB_BACKEND_PERSISTENCE": False
      }

Is there a workaround? E.g. disabling the "select all" option?

Was fixed for me in 2.1.1.

This is likely fixed by now, and is pretty out of date if not. If people are still encountering this in current versions (3.x) please open a new Issue or a PR to address the problem. ... or I guess we can re-open this if nothing has changed. That last comment has me optimistic, so I'll close this :)


Grudle deamon error

Hello. I'm trying to solve the gradle launch problem for the second week and can't find a solution
gradle --stacktrace
Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------

FAILURE: Build failed with an exception.

* What went wrong:
java.lang.ExceptionInInitializerError (no error message)

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

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

* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Exception is:
org.gradle.api.GradleException: Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------

FAILURE: Build failed with an exception.

* What went wrong:
java.lang.ExceptionInInitializerError (no error message)

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

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

	at org.gradle.launcher.daemon.bootstrap.DaemonGreeter.parseDaemonOutput(DaemonGreeter.java:34)
	at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(DefaultDaemonStarter.java:152)
	at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(DefaultDaemonStarter.java:135)
	at org.gradle.launcher.daemon.client.DefaultDaemonConnector.doStartDaemon(DefaultDaemonConnector.java:210)
	at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(DefaultDaemonConnector.java:204)
	at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:128)
	at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:138)
	at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:92)
	at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:51)
	at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:173)
	at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:291)
	at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:264)
	at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:33)
	at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
	at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
	at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
	at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:257)
	at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:191)
	at org.gradle.launcher.Main.doAction(Main.java:33)
	at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60)
	at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37)
	at org.gradle.launcher.GradleMain.main(GradleMain.java:23)

Whats problem? How solve?(((

Can you try running your build with --no-daemon and see what happens?
Could you be affected by #3117 or #7448?

@BDAinc Can you run gradle -version?

@BDAinc Can you run gradle -version?

Gradle 4.4.1
Build time:   2012-12-21 00:00:00 UTC
Revision:     none
Groovy:       2.4.15
Ant:          Apache Ant(TM) version 1.10.5 compiled on August 27 2018
JVM:          1.8.0_201 (Oracle Corporation 25.201-b09)
OS:           Linux 4.20.11-042011-generic amd64

Can you try running your build with --no-daemon and see what happens?
Could you be affected by #3117 or #7448?

FAILURE: Build failed with an exception.

What went wrong:
java.lang.ExceptionInInitializerError (no error message)

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

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

@BDAinc I think you're running into the same thing as here: https://github.com/gradle/gradle/issues/7831#issuecomment-442652048
You're using a version of Gradle that was built somewhere else and has custom patches to it. I suspect you're installing the default from Debian, which has this problem.
Please install Gradle from one of our official locations: https://gradle.org/install/

@BDAinc I think you're running into the same thing as here: #7831 (comment)
You're using a version of Gradle that was built somewhere else and has custom patches to it. I suspect you're installing the default from Debian, which has this problem.
Please install Gradle from one of our official locations: https://gradle.org/install/

thx for you help
I unpacked the archive as specified in the installation instructions, run the command export PATH=$PATH:/opt/gradle/gradle-5.4/bin
gradle-v check still shows version 4.4.1
what's wrong?

@BDAinc I think you're running into the same thing as here: #7831 (comment)
You're using a version of Gradle that was built somewhere else and has custom patches to it. I suspect you're installing the default from Debian, which has this problem.
Please install Gradle from one of our official locations: https://gradle.org/install/

thx for you help
I unpacked the archive as specified in the installation instructions, run the command export PATH=$PATH:/opt/gradle/gradle-5.4/bin
gradle-v check still shows version 4.4.1
what's wrong?

so I changed it .bashrc adding export PATH=$PATH:/opt/gradle/gradle-5.4/bin
the version is still old

change order to
export PATH=/opt/gradle/gradle-5.4/bin:$PATH

otherwise (i.e for PATH=$PATH:/opt/gradle/gradle-5.4/bin) the first binary - if there is any in $PATH - is selected

change order to
export PATH=/opt/gradle/gradle-5.4/bin:$PATH

otherwise (i.e for PATH=$PATH:/opt/gradle/gradle-5.4/bin) the first binary - if there is any in $PATH - is selected

its work! but i see new problem
i run command cordova build and see
hecking Java JDK and Android SDK versions
ANDROID_SDK_ROOT=undefined (recommended setting)
ANDROID_HOME=/usr/lib/android-sdk (DEPRECATED)
Subproject Path: CordovaLib
Subproject Path: app
Starting a Gradle Daemon (subsequent builds will be faster)

> Configure project :app
WARNING: The specified Android SDK Build Tools version (24.0.0) is ignored, as it is below the minimum supported version (28.0.3) for Android Gradle Plugin 3.3.0.
Android SDK Build Tools 28.0.3 will be used.
To suppress this warning, remove "buildToolsVersion '24.0.0'" from your build.gradle file, as each version of the Android Gradle Plugin now has a default version of the build tools.
Observed package id 'build-tools;24.0.0' in inconsistent location '/usr/lib/android-sdk/build-tools/debian' (Expected '/usr/lib/android-sdk/build-tools/24.0.0')
Already observed package id 'build-tools;24.0.0' in '/usr/lib/android-sdk/build-tools/24.0.0'. Skipping duplicate at '/usr/lib/android-sdk/build-tools/debian'
Observed package id 'build-tools;24.0.0' in inconsistent location '/usr/lib/android-sdk/build-tools/debian' (Expected '/usr/lib/android-sdk/build-tools/24.0.0')
Already observed package id 'build-tools;24.0.0' in '/usr/lib/android-sdk/build-tools/24.0.0'. Skipping duplicate at '/usr/lib/android-sdk/build-tools/debian'
Observed package id 'build-tools;24.0.0' in inconsistent location '/usr/lib/android-sdk/build-tools/debian' (Expected '/usr/lib/android-sdk/build-tools/24.0.0')
Already observed package id 'build-tools;24.0.0' in '/usr/lib/android-sdk/build-tools/24.0.0'. Skipping duplicate at '/usr/lib/android-sdk/build-tools/debian'
File /home/anonim/.android/repositories.cfg could not be loaded.
Checking the license for package Android SDK Build-Tools 28.0.3 in /usr/lib/android-sdk/licenses
Warning: License for package Android SDK Build-Tools 28.0.3 not accepted.
Checking the license for package Android SDK Platform 28 in /usr/lib/android-sdk/licenses
Warning: License for package Android SDK Platform 28 not accepted.

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Failed to install the following Android SDK packages as some licences have not been accepted.
     build-tools;28.0.3 Android SDK Build-Tools 28.0.3
     platforms;android-28 Android SDK Platform 28
  To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
  Alternatively, to transfer the license agreements from one workstation to another, see http://d.android.com/r/studio-ui/export-licenses.html

  Using Android SDK: /usr/lib/android-sdk

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

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

BUILD FAILED in 44s
/media/anonim/01D4C6F2C6169120/PROJECTS/PLANSTER/PRODUCTIONS/MOBILE/Planster31/platforms/android/gradlew: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Failed to install the following Android SDK packages as some licences have not been accepted.
     build-tools;28.0.3 Android SDK Build-Tools 28.0.3
     platforms;android-28 Android SDK Platform 28
  To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
  Alternatively, to transfer the license agreements from one workstation to another, see http://d.android.com/r/studio-ui/export-licenses.html

  Using Android SDK: /usr/lib/android-sdk

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


[BUG] crc start fails on crc-driver-libvirt version

Same or similar issue here: https://github.com/crc-org/crc/issues/3951
General information

OS: Linux
Did you run crc setup before starting it? Yes
Running CRC on: Laptop

CRC version
CRC version: 2.32.0+54a6f9
OpenShift version: 4.14.8
Podman version: 4.4.4

CRC status
DEBU CRC version: 2.32.0+54a6f9
DEBU OpenShift version: 4.14.8
DEBU Podman version: 4.4.4
DEBU Running 'crc status'
Machine does not exist. Use 'crc start' to create it

CRC config
- consent-telemetry                     : yes
- cpus                                  : 10
- disk-size                             : 96
- memory                                : 28672
- pull-secret-file                      : /home/jefrankl/pull-secret.json

Host Operating System
NAME="Red Hat Enterprise Linux"
VERSION="8.5 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.5"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.5 (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/red_hat_enterprise_linux/8/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.5
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.5"

Steps to reproduce

crc start --log-level debug

Expected
OpenShift Local Starts Up Successfully
Actual
OpenShift Local fails on /home/jefrankl/.crc/bin/crc-driver-libvirt version
Logs
Before gather the logs try following if that fix your issue
$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug

See output below
crc cleanup
INFO Removing vsock configuration
INFO Removing 'crc' network from libvirt
INFO Removing /etc/NetworkManager/dnsmasq.d/crc.conf file
INFO Using root access: Removing NetworkManager configuration file in /etc/NetworkManager/dnsmasq.d/crc.conf
[sudo] password for jefrankl:
INFO Using root access: Executing systemctl daemon-reload command
INFO Using root access: Executing systemctl reload NetworkManager
INFO Removing /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf file
INFO Using root access: Removing NetworkManager configuration file in /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf
INFO Using root access: Executing systemctl daemon-reload command
INFO Using root access: Executing systemctl reload NetworkManager
INFO Removing crc daemon systemd socket units
INFO Removing crc daemon systemd service
INFO Removing crc's virtual machine
INFO Removing crc libvirt storage pool
INFO Removing CRC Specific entries from user's known_hosts file
INFO Removing hosts file records added by CRC
INFO Removing pull secret from the keyring
INFO Removing older logs
Cleanup finished

crc setup
INFO Using bundle path /home/jefrankl/.crc/cache/crc_libvirt_4.14.8_amd64.crcbundle
INFO Checking if running as non-root
INFO Checking if running inside WSL2
INFO Checking if crc-admin-helper executable is cached
INFO Checking if running on a supported CPU architecture
INFO Checking if crc executable symlink exists
INFO Creating symlink for crc executable
INFO Checking minimum RAM requirements
INFO Checking if Virtualization is enabled
INFO Checking if KVM is enabled
INFO Checking if libvirt is installed
INFO Checking if user is part of libvirt group
INFO Checking if active user/process is currently part of the libvirt group
INFO Checking if libvirt daemon is running
INFO Checking if a supported libvirt version is installed
INFO Checking if crc-driver-libvirt is installed
INFO Installing crc-driver-libvirt
INFO Checking crc daemon systemd service
INFO Setting up crc daemon systemd service
INFO Checking crc daemon systemd socket units
INFO Setting up crc daemon systemd socket units
INFO Checking if systemd-networkd is running
INFO Checking if NetworkManager is installed
INFO Checking if NetworkManager service is running
INFO Checking if /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf exists
INFO Writing Network Manager config for crc
INFO Using root access: Writing NetworkManager configuration to /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf
INFO Using root access: Changing permissions for /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf to 644
INFO Using root access: Executing systemctl daemon-reload command
INFO Using root access: Executing systemctl reload NetworkManager
INFO Checking if /etc/NetworkManager/dnsmasq.d/crc.conf exists
INFO Writing dnsmasq config for crc
INFO Using root access: Writing NetworkManager configuration to /etc/NetworkManager/dnsmasq.d/crc.conf
INFO Using root access: Changing permissions for /etc/NetworkManager/dnsmasq.d/crc.conf to 644
INFO Using root access: Executing systemctl daemon-reload command
INFO Using root access: Executing systemctl reload NetworkManager
INFO Checking if libvirt 'crc' network is available
INFO Setting up libvirt 'crc' network
INFO Checking if libvirt 'crc' network is active
INFO Starting libvirt 'crc' network
INFO Checking if CRC bundle is extracted in '$HOME/.crc'
INFO Checking if /home/jefrankl/.crc/cache/crc_libvirt_4.14.8_amd64.crcbundle exists
Your system is correctly setup for using CRC. Use 'crc start' to start the instance

crc start --log-level debug
DEBU CRC version: 2.32.0+54a6f9
DEBU OpenShift version: 4.14.8
DEBU Podman version: 4.4.4
DEBU Running 'crc start'
DEBU Total memory of system is<PHONE_NUMBER>8 bytes
DEBU No new version available. The latest version is 2.32.0
DEBU Checking file: /home/jefrankl/.crc/machines/crc/.crc-exist
INFO Using bundle path /home/jefrankl/.crc/cache/crc_libvirt_4.14.8_amd64.crcbundle
DEBU Checking if systemd-resolved.service is running
DEBU Running 'systemctl status systemd-resolved.service'
DEBU Command failed: exit status 3
DEBU stdout: * systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
DEBU stderr:
INFO Checking if running as non-root
INFO Checking if running inside WSL2
INFO Checking if crc-admin-helper executable is cached
DEBU Running '/home/jefrankl/.crc/bin/crc-admin-helper-linux --version'
DEBU Found crc-admin-helper-linux version 0.5.2
DEBU crc-admin-helper executable already cached
INFO Checking if running on a supported CPU architecture
DEBU GOARCH is amd64 GOOS is linux
INFO Checking if crc executable symlink exists
INFO Checking minimum RAM requirements
DEBU Total memory of system is<PHONE_NUMBER>8 bytes
INFO Checking if Virtualization is enabled
DEBU Checking if the vmx/svm flags are present in /proc/cpuinfo
DEBU CPU virtualization flags are good
INFO Checking if KVM is enabled
DEBU Checking if /dev/kvm exists
DEBU /dev/kvm was found
INFO Checking if libvirt is installed
DEBU Checking if 'virsh' is available
DEBU 'virsh' was found in /usr/bin/virsh
DEBU Checking 'virsh capabilities' for libvirtd/qemu availability
DEBU Running 'virsh --readonly --connect qemu:///system capabilities'
DEBU Found x86_64 hypervisor with 'hvm' capabilities
INFO Checking if user is part of libvirt group
DEBU Checking if current user is part of the libvirt group
DEBU Current user is already in the libvirt group
INFO Checking if active user/process is currently part of the libvirt group
INFO Checking if libvirt daemon is running
DEBU Checking if libvirtd service is running
DEBU Running 'systemctl status virtqemud.socket'
DEBU Command failed: exit status 3
DEBU stdout: * virtqemud.socket - Libvirt qemu local socket
   Loaded: loaded (/usr/lib/systemd/system/virtqemud.socket; disabled; vendor preset: disabled)
   Active: inactive (dead)
   Listen: /run/libvirt/virtqemud-sock (Stream)
DEBU stderr:
DEBU virtqemud.socket is neither running nor listening
DEBU Running 'systemctl status libvirtd.socket'
DEBU libvirtd.socket is running
INFO Checking if a supported libvirt version is installed
DEBU Checking if libvirt version is >=3.4.0
DEBU Running 'virsh -v'
INFO Checking if crc-driver-libvirt is installed
DEBU Checking if crc-driver-libvirt is installed
DEBU Running '/home/jefrankl/.crc/bin/crc-driver-libvirt version'
DEBU Command failed: exit status 1
DEBU stdout:
DEBU stderr: /home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_7.1.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
/home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_7.7.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
/home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_8.0.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
/home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_7.8.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
/home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_7.2.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
/home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_6.10.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
/home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_7.3.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
DEBU failed to run executable /home/jefrankl/.crc/bin/crc-driver-libvirt: exit status 1
DEBU exit status 1
WARN Preflight checks failed during `crc start`, please try to run `crc setup` first in case you haven't done so yet
exit status 1

crc start --log-level debug log also on Gist: https://gist.github.com/ultraJeff/8c1e24c3d4a2e0d705a06e0be5d39d68

@ultraJeff you need to update your RHEL-8 system because latest version of libvirt is 8.0.x for RHEL-8 after update when you try again it should fix this issue.

DEBU stderr: /home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_7.1.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
/home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_7.7.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
/home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_8.0.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
/home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_7.8.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
/home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_7.2.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
/home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_6.10.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
/home/jefrankl/.crc/bin/crc-driver-libvirt: /lib64/libvirt.so.0: version `LIBVIRT_7.3.0' not found (required by /home/jefrankl/.crc/bin/crc-driver-libvirt)
DEBU failed to run executable /home/jefrankl/.crc/bin/crc-driver-libvirt: exit status 1

This indicates no matching libvirt library on the machine can be found. As mentioned, please update your system.

We have a preflight checking the libvirt version, we forgot to bump it to 8.0.0, I've opened a PR to address this.


ipk

请问这个可以生成ipk文件安装吗？ 更新下载二进制文件 怎样解压缩 是直接解压缩上传换文件 还是需要命令解压 请具体的说一下 谢谢 谢谢

There is no ipk file since this is not a package. To use it, please follow the instructions on the README. Download the .tgz package from releases to openWRT. Then proceed to run the commands. The first command in the README will extract the contents to the correct locations.


Update/Add alpine:3.18

Tool name
alpine:3.18
Tool license
https://pkgs.alpinelinux.org/packages
Add or update?

[X] Add
[ ] Update

Desired version
3.18
Approximate size
No response
Brief description of tool
No response
URL for tool's homepage
https://alpinelinux.org/
Provide a basic test case to validate the tool's functionality.
No response
Platforms where you need the tool

[ ] Azure DevOps
[X] GitHub Actions

Runner images where you need the tool

[X] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Can this tool be installed during the build?
No response
Tool installation time in runtime
No response
Are you willing to submit a PR?
Yes

Hello @Kielek!
I'll add it soon.

Image rollout of Ubuntu images for the Standard Runners done.


New package: ONSAS v0.0.1

Registering package: ONSAS
Repository: https://github.com/ONSAS/ONSAS.jl
Created by: @mvanzulli
Version: v0.0.1
Commit: 28633d90ffa9837db898c721a70de29dab5f5458
Reviewed by: @mvanzulli
Reference: https://github.com/ONSAS/ONSAS.jl/commit/28633d90ffa9837db898c721a70de29dab5f5458#commitcomment-107003028
Description: An Open Nonlinear Structural Analysis Solver in Julia

Hi, thanks @ViralBShah for answering me via slack. Is this ready to be merged ?


Feature: Highlighting to console

This cleans up the console to support undefined, null and adds simple syntax highlighting.
/cc @kenwheeler

Well done


[Install issue]: Rust settings in Orjson v3.10.7

What happened?
installation error due to rust requirement settings in orjson v3.10.7

Versions
chromadb-client v0.5.4.dev0
Relevant log output
Preparing metadata (pyproject.toml) did not run successfully.
55.00   │ exit code: 1
55.00   ╰─> [6 lines of output]
55.00       Checking for Rust toolchain....
55.00
55.00       Cargo, the Rust package manager, is not installed or is not on PATH.
55.00       This package requires Rust and Cargo to compile extensions. Install it through
55.00       the system's package manager or via https://rustup.rs/

Take a look at this: https://github.com/ijl/orjson/issues/509

@Jonathanjordan21, new binary wheels should be available now. Can you test the install?

Closing as upstream issue - let me know however if I should re-open here.


Tasks to continue running after swarm crash

By default, when a framework fails, Mesos will terminate any tasks started by a framework
The failovertimeout parameter allows the tasks to continue running for this number of seconds after the swarm manager dies.  Mesos documentation recommends setting this value to 1 week time.
The frameworkid allows to specify a unique id. If Swarm manages to reconnect with the same task ID it had before the crash then mesos will reassigned the tasks to it. The ID must follow the mesos format for IDs (i.e. b2853a78-7cba-455a-99c7-d73bb5cbda95-0024). Refer to mesos for ID formats.
Signed-off-by: Guillermo Rodriguez<EMAIL_ADDRESS>

Note, this is the separation of the changes proposed in the PR #2067
This PR only updates the mesos timeout and frameworkid for task resilience.
The changes to modify the Dockerfile only are now in PR #2344

@Spritekin Looks good. I also think the curl stuff should have a separate PR.  I suggest you close #2067

@Spritekin not sure the help message for the timeout is clear enough, how about:
keep the tasks lunched by this framework, running for this number of seconds in case this Swarm manager crashes ....
what did you mean by "recover by restarting with the same framwrodk id " ?  I'm not sure we should refer to the HA/recovery flow in the help of this parameter.

@ezrasilvera
Closed PR 2067.
Will try to rephrase. The problem is both parameters are very related. The main concept is:
Mesos identifies a framework by its ID. All tasks started by the framework are assigned to that ID. If the framework crashes the tasks keep assigned to that ID for the failover_timeout seconds (default 0 means they are stopped immediately). If you restart a framework with the same framework id before the framework_timeout elapses, then the tasks are reassigned.
Now, about HA, it doesn't work with mesos because of contradicting behaviours.
a. when you start swarm mesos will assign it a unique ID. So if you start three swarm in HA mode, each will have its own ID. Then, when you start tasks, they will start with the leader ID. But if the leader crashes then mesos can't reassign them to the new elected leader because they have different IDs.
b. So then I tried to start three swarm with the same ID, the first one took leadership, then the other two were waiting. But when mesos sent offers, instead of being sent to the leader they are sent to the last framework connected with that ID (which happens not to be the leader) so the leader never receives offers so it is unable to launch tasks. The solution in this case would be to allow a secondary swarm to reroute offers to the leader.
In any case, my HA is to quickly detect problems in swarm using a Marathon health checks and restart quickly. That's where the curl requirements get in but then that's another story.

@ezrasilvera
Ok, I have adjusted the help text. Please tell me if its a bit clearer.

@Spritekin I agree that the to get HA like capabilities (i.e., detect failure and restart a new Swarm master) you need both PRs . This doesn't mean, however, that one can't use each of this separately for whatever reason he wants to :-)
For example, I can see why people would like to explicitly set the farmeworkID even without th erestart scenario.

that's why I thought that in the help we shouldn't refer to a specific use-case of the parameter but simply to what the parameter does

@ezrasilvera
Removed specific use case text from the help strings.

@ezrasilvera
Why are the checks failing? Doesn't seem caused by this change.

@Spritekin I think it's not related to your changes. You can see that other builds failed as well. I just push again from time to time to initiate the build (you can use --no-edit and --amend so no real commit is needed)

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "mesos-failover-timeout" git@github.com:Spritekin/swarm.git somewhere
$ cd somewhere
$ git rebase -i HEAD~5
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

@ezrasilvera @jimenez
What now! I don't see a problem in the documentation and it says its failing!
I like this project but I don't have time for being stopped by nonexistent errors. Please ask someone to fix the build system.
Luck!

Aaaaaarggggg....

Closing. Pulled an invalid ticket


feat: fetch proxy configuration from NPM if any

Fixes #8

Coverage increased (+0.3%) to 98.355% when pulling 88417f99b3a53666cfbcfbf86611495835afe97f on aslushnikov:fetch-env-from-npm into e0d07a9350568b3a0c3bb28dafd3766206961a02 on Rob--W:master.

Instead of adding new getEnv(...) calls everywhere, could you modify the getEnv to fall back to npm_config_* if needed?
And please add some unit tests as well.

Instead of adding new getEnv(...) calls everywhere, could you modify the getEnv to fall back to npm_config_* if needed?

Not all proxy-related env variables are mirrored in NPM config, e.g. there's no such thing as npm_config_all_proxy. I can whitelist allowed values in getEnv, but having these ad-hoc feels straight-forward.

And please add some unit tests as well.

My bad! Done.

Not all proxy-related env variables are mirrored in NPM config, e.g. there's no such thing as npm_config_all_proxy

I see. There is no 1:1 relation between the variable names used here and the one used by npm.
Could you use the npm_config_ variants as a fallback? The HTTPS_PROXY (etc) variable is the more common form, so they should be preferred over the npm_config variants.

And please add some unit tests as well.

My bad! Done.

Thaanks!

Could you use the npm_config_ variants as a fallback? The HTTPS_PROXY (etc) variable is the more common form, so they should be preferred over the npm_config variants.

I was driven by an opposite logic: preferring npm_config_* over default variants since they're more specific.
I consider the following use case: I have HTTPS_PROXY somewhere in my .bashrc for general-purpose web surfing, and if NPM doesn't work for some reason with these settings then I go figure all the npm-config business. WDYT?

Could you use the npm_config_ variants as a fallback? The HTTPS_PROXY (etc) variable is the more common form, so they should be preferred over the npm_config variants.

I was driven by an opposite logic: preferring npm_config_* over default variants since they're more specific.
I consider the following use case: I have HTTPS_PROXY somewhere in my .bashrc for general-purpose web surfing, and if NPM doesn't work for some reason with these settings then I go figure all the npm-config business. WDYT?

This sounds reasonable. I also looked up the origin of the npm config documentation, and found that it was introduced here: https://github.com/npm/npm/pull/6525
In that implementation, the default value of npm_config_*proxy is unset, to allow the underlying (request) library to observe the standard *_PROXY environment variable. If npm_config_*proxy is set, the *_proxy environment variable is shadowed.
In your current patch, you're using the npm-specific environment variables before falling back to the normal ones, i.e.:

npm_config_[proto]_proxy
npm_config_proxy
[proto]_proxy
all_proxy

Could you swap 2 and 3, so that the protocol-specific environment variables take precedence over the ultimate fallback?

Could you swap 2 and 3, so that the protocol-specific environment variables take precedence over the ultimate fallback?

Indeed, good catch! Done.

is there anything else I can do?

Thanks for your patch. Is there anything else before I publish an update?

Thanks for your patch. Is there anything else before I publish an update?

No, I don't think so. Once you release a new version, we'll bump it right away in Playwright.
Thank you!


BUG: removing a key used in the filename via onyo edit results in ERROR

If I remove a key used in the filename, an (unhelpful) error is thrown.
Contents:
❱ onyo cat dp/Alex\ Waite/headphones_sennheiser_SR27.faux
type: headphones
make: sennheiser
model: SR27
serial: faux

I then use onyo edit to remove the serial field.
(onyo) aqw@hrududu in /tmp/yope on git:master
❱ onyo edit dp/Alex\ Waite/headphones_sennheiser_SR27.faux
Changes:
Save changes? No discards all changes. (y/n) y
ERROR: Command '['git', 'commit', '-m', 'edit: dp/Alex Waite/headphones_sennheiser_SR27.faux\n\n--- Inventory Operations ---\nModified assets:\n\t- dp/Alex Waite/headphones_sennheiser_SR27.faux\n']' returned non-zero exit status 1.

This is in contrast to onyo new which provides a meaningful error message and prompts me to re-edit:
❱ onyo new --edit
ERROR: Asset missing value for required field 'serial'.

The upshot is that Onyo does the right thing on error. The exit code is 1, the edited file is unmodified, and the repository is completely clean, with no commit or staging.

This actually closely related to #411. Issue being: validation upon edit is done in the wrong spot.


FTRL maths displayed messy

In this doc https://www.tensorflow.org/api_docs/python/tf/keras/optimizers/Ftrl the math is messed up
see https://snipboard.io/my0uSb.jpg
using chrome browser

@dirknbr,
I have tried different browsers and did not observe any difference in the page. Could you please point out what needs to be corrected? Thanks!

as per the screenshot, the \abs bit is in red and not rendered correctly

This error is due to mistake in parentheses, it should be abs(z_{i}) instead of abs{z_{i}}. I'd like to fix this but I can't get that file version correctly since it's on different tag. Could you plz tell how can I get the correct file version in my local repository.

@dirknbr,
Closing this issue as it is resolved in the nightly version.
Please feel free to re-open if mistaken. Thanks!


[resotocore] multiple head/tail piped into another don't preserve expected order

Description
Take this example where the first search returns three results of which I was interested in the middle one. So I said, give me the last two and of those give me the first tail -2 | head -1. Instead I got a result that shouldn't even be part of the resultset after the first tail anymore.
> search<EMAIL_ADDRESS>kind=aws_ec2_instance, id=i-0af2561eb64b7ab79, name=salt1, age=1yr9mo, cloud=aws, account=eng-production, region=us-west-2
kind=onelogin_user, id=11740939, name=lukas, age=7yr4mo, last_update=1mo4d, cloud=onelogin, account=df12611ab51a9890888ea5f9a354087ad472a41493950610ddbe9af8042f53c0, region=us
kind=slack_user, id=U02EUHR63, name=lukas, age=3mo23d, last_update=3mo23d, cloud=slack, account=D2iQ, region=members
> search<EMAIL_ADDRESS>| tail -2 | head -1
kind=aws_ec2_instance, id=i-0af2561eb64b7ab79, name=salt1, age=1yr9mo, cloud=aws, account=eng-production, region=us-west-2
> search<EMAIL_ADDRESS>| tail -2
kind=onelogin_user, id=11740939, name=lukas, age=7yr4mo, last_update=1mo4d, cloud=onelogin, account=df12611ab51a9890888ea5f9a354087ad472a41493950610ddbe9af8042f53c0, region=us
kind=aws_ec2_instance, id=i-0af2561eb64b7ab79, name=salt1, age=1yr9mo, cloud=aws, account=eng-production, region=us-west-2
> search<EMAIL_ADDRESS>| tail -2 | head -1
kind=aws_ec2_instance, id=i-0af2561eb64b7ab79, name=salt1, age=1yr9mo, cloud=aws, account=eng-production, region=us-west-2
> search<EMAIL_ADDRESS>| head -1
kind=aws_ec2_instance, id=i-0af2561eb64b7ab79, name=salt1, age=1yr9mo, cloud=aws, account=eng-production, region=us-west-2

Version
2.0.0a17
Environment
No response
Steps to Reproduce
No response
Logs
No response
Additional Context
No response

I can confirm: successive head and tail (head -xx | tail -xx or tail -xx | head -xx) commands are currently not supported and lead to a wrong result.


Supporting Newer Versions of GO

This pr creates 2 new files that allow this repo to integrate with the new way that go build tools work, as well as fixing a small inclusion issue in regards to capitalization of the string. Built and tested with Go 1.17.3.
This pr is the result of an issue I had setting up the repo for development  with 1.7.1 so I decided to upgrade it to support 1.17.3, this is my first project working in go so please be patient. I have partially tested for this code to work and have observed no issues with the web-server, but I have yet to fully test the code (it will be a week or more before I can do so). That warning being given I am fairly certain that these changes will not break the current code base, assuming you upgrade go, so I'm submitting this pr.

Heya, thanks for the PR. I've gone ahead and updated the codebase to build with the latest version of Go myself, so this won't merge cleanly anymore. You should be good to use the code in master now tho.


Update README.md

issue #46 solved in this PR

Also, you can use the sintax closes #issue number and it will automatically close the issue when merged 👍

Hi @ANURAG-PATHAK, thank you for fixing this issue 👍. Just left a comment so let me know what you think.
The PR #50 has the same change as this one, but I believe this one was open first, so it should be merged, IMO 🙂.

resolved conversation in #52

Note: #52 is also by @ANURAG-PATHAK

Thank you for the contribution 👍 This PR has now been superseded, so I will close


5.64: Default overlay for Street Fighter 6 hides character-specific indicators

When using the Street Fighter 6 scoreboard, character-specific indicators such as Manon’s stocks and Jamie’s drinks are hidden by the extra info bar
For instance, in this screenshot, Ryu’s Denjin Mode indicator would be hidden

Reference SF6 screens:

Fixed in 5.65


Incorrectly styled segments in Notifications Preferences.

In Preferences > Notifications, you see this:

This should now be fixed with the latest changes to master. Could you confirm it is fixed by using the lates darkreader.css?

Confirmed fixed.


Tracking issue: Performance with large message sizes on Node.js

We recently investigated performance with the BigTable client library on Node.js and discovered some performance issues (CPU usage, latency) with large message sizes. This is a tracking issue for the relevant fixes

[x] Need performance test-coverage for large message sizes (1B-1KB-10KB-1MB-max_limit)
[ ] Performance fixes

[X] Upgrade to protobufjs@6 (https://github.com/grpc/grpc/pull/10204)
[X] Performance improvements (https://github.com/grpc/grpc/pull/10416)
[x] Release these performance fixes
[ ] Investigate the outstanding 2.5X performance difference on large message sizes vs. REST
[ ] Investigate performance improvements in core TLS code

Another item on the list should probably be improvements to the core TLS code. Using TLS has a greater performance hit than it probably should.

I have created benchmarks to test latency with response messages of various sizes. The data from those benchmarks can be found here: http://performance-dot-grpc-testing.appspot.com/explore?dashboard=5717648100818944. As you can see, according this benchmark, JSON over HTTP is significantly slower than proto over gRPC, and this difference scales with message size.
I would not claim that these benchmarks definitively indicate that gRPC is faster that REST, but I no longer believe that we can trust the old benchmark indicating a "2.5x performance difference" in the other direction.

As it stands, right now we have two different benchmarks with different results. We still need a disposition on the benchmark that shows the 2.5x performance difference – I think you can reproduce this too. Since it is reproducible, it would be good to show why it is not relevant – or to fix the issue(s), if it is relevant.


CUDA: an illegal memory access was encountered on hybridized yolo model

Step to reproduce

build mxnet-cu101 from source based off mxnet 1.7.0 branch
gluoncv 0.7

from gluoncv import model_zoo, data, utils
from matplotlib import pyplot as plt
import mxnet as mx
from mxnet import gluon

net = model_zoo.get_model('yolo3_darknet53_coco', pretrained=True, ctx=mx.gpu())
net.hybridize()
x = mx.nd.random.uniform(shape=(1, 3, 1000, 1000), ctx=mx.gpu())
_, scores, _ = net(x)
print(scores.shape)
net.export("yolo")

deserialized_net = gluon.nn.SymbolBlock.imports("yolo-symbol.json", ['data'], "yolo-0000.params", ctx=mx.gpu())
image = mx.nd.random.normal(shape=(1, 3, 1000, 1000), ctx=mx.gpu())
print(deserialized_net(image))

CUDA: Check failed: e == cudaSuccess: an illegal memory access was encountered
[21:53:46] src/resource.cc:279: Ignore CUDA Error [21:53:46] src/storage/./pooled_storage_manager.h:97: CUDA: an illegal memory access was encountered

[21:53:46] src/resource.cc:331: Ignore CUDA Error [21:53:46] src/common/random_generator.cu:70: Check failed: e == cudaSuccess || e == cudaErrorCudartUnloading: CUDA: an illegal memory access was encountered

It works fine when I use CPU or mxnet-cu101 1.6 pip wheel

@stu1130 could you help verify if this still happens with the master branch?

@szha sure but I ran into this error on master branch
/home/ubuntu/mxnet_master/tools/dependencies/openblas.sh: line 35: patchelf: command not found

This is the command I used
tools/staticbuild/build.sh cu101

@szha sure but when I build mxnet from source I ran into the error.
+++ patchelf --set-rpath '$ORIGIN' --force-rpath libopenblas.so
/home/ubuntu/mxnet_master/tools/dependencies/openblas.sh: line 35: patchelf: command not found

This is the command I used.
tools/staticbuild/build.sh cu101

@stu1130 how about installing patchelf?

@leezu thanks! It works

It seems gluoncv 0.7 doesn't work with mxnet 2.0. Is the gluoncv 0.7 the latest version I can get?
Traceback (most recent call last):
  File "demo_yolo.py", line 10, in <module>
    from gluoncv import model_zoo, data, utils
  File "/home/ubuntu/.local/lib/python3.5/site-packages/gluoncv/__init__.py", line 8, in <module>
    from . import data
  File "/home/ubuntu/.local/lib/python3.5/site-packages/gluoncv/data/__init__.py", line 4, in <module>
    from . import transforms
  File "/home/ubuntu/.local/lib/python3.5/site-packages/gluoncv/data/transforms/__init__.py", line 5, in <module>
    from . import image
  File "/home/ubuntu/.local/lib/python3.5/site-packages/gluoncv/data/transforms/image.py", line 6, in <module>
    from mxnet import nd
ImportError: cannot import name 'nd'

That is surprising as I can still import nd from a build on the master branch.

@szha
I built v1.8.0, v1.7.0 to reproduce this issue. and I can confirm that still happens.
But it works fine when I use prebuild package 1.6.0.post0 from pypi.
I have same issue in my code. After I turned hybridize on, it will produce this error. But with off, everything works fine.

@szha
I built v1.8.0, v1.7.0 to reproduce this issue. and I can confirm that still happens.
But it works fine when I use prebuild package 1.6.0.post0 from pypi.
I have same issue in my code. After I turned hybridize on, it will produce this error.  Try uninstalling all mxnet packages (you probably have multiple insatlled?) and installing again

@troyliu0105 it just means that you managed to corrupt your python profile. Try uninstalling all mxnet packages (you probably have multiple insatlled?) and installing again

@leezu actually, I created different anaconda env and duplicated source code directory for each build. So, I think they are isolated.

@leezu actually, I created different anaconda env and duplicated source code directory for each build. So, I think they are isolated.

Sorry, but as you experience the issue of importing, it means that your environment is broken. You can try using pip install -e . to install while in the incubator-mxnet/python directory

Sorry, but as you experience the issue of importing, it means that your environment is broken. You can try using pip install -e . to install while in the incubator-mxnet/python directory

@leezu 😂，that's not the issue I encountered. I think you confused me with the one opened this issue.

@leezu 😂，that's not the issue I encountered. I think you confused me with the one opened this issue.

Ok. I thought you talk about the ImportError: cannot import name 'nd' issue described above.

Ok. I thought you talk about the ImportError: cannot import name 'nd' issue described above.

@szha I build the most recently master branch. cuz gluoncv is not compatible with mxnet 2.0 (can't pass version assert), so I use previous exported weight to test like below:
from gluoncv import model_zoo, data, utils
from matplotlib import pyplot as plt
import mxnet as mx
from mxnet import gluon
deserialized_net = gluon.nn.SymbolBlock.imports("yolo-symbol.json", ['data'], "yolo-0000.params", ctx=mx.gpu())
image = mx.nd.random.normal(shape=(1, 3, 1000, 1000), ctx=mx.gpu())
print(deserialized_net(image))

and this issue still occurs.

@szha I build the most recently master branch. cuz gluoncv is not compatible with mxnet 2.0 (can't pass version assert), so I use previous exported weight to test like below:
from gluoncv import model_zoo, data, utils
from matplotlib import pyplot as plt
import mxnet as mx
from mxnet import gluon
deserialized_net = gluon.nn.SymbolBlock.imports("yolo-symbol.json", ['data'], "yolo-0000.params", ctx=mx.gpu())
image = mx.nd.random.normal(shape=(1, 3, 1000, 1000), ctx=mx.gpu())
print(deserialized_net(image))

and this issue still occurs.

Any updates ? Got the same problem for mxnet 1.7.

@waytrue17 and I also had this issue with mxnet 1.7

I can confirm that the issue only occurs at yolo3_darknet53_coco but not yolo3_darknet53_voc

This issue still exists in  mxnet-cu102==1.8.0.post0


Forms: Check if map has a FeatureFormDefinition

Summary of changes

When a Map is opened, a check is performed to see if any of its FeatureLayers contains a FeatureFormDefinition. If none exists, an alert dialog is shown informing the user.
Bumps SDK version to pick up the latest changes

thanks @sorenoid


Fix cloud functions podspec.

This will fix compilation errors when doing a pod install because this package has static framework dependencies.
The error namely:
    [!] The 'Pods-Runner' target has transitive dependencies that include static frameworks: (FirebaseFunctions, FirebaseCore, FirebaseAuth, FirebaseDatabase, and FirebaseFirestore)

@kroikie sure thing. will bump version and add a note in the CHANGELOG.

@westoque Thanks for noticing these, I've been experiencing this dependency issue for a while and hopefully this solves it
FYI did you perhaps bump the wrong package by mistake? It looks like the updated changelog in firebase_auth not cloud_functions. Would love it if you could bump and release cloud_functions when you get a moment
Cheers

@cdharris thanks for the correction! made the changes and pushed.
cc: @kroikie


Pookam90 patch 1 (VECTOR PRIVATE PREVIEW)

do-not-merge

@Pookam90,
Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.
We'll close this PR. Thank you.


Grading Next / Prev keyboard shortcuts

It would be great to be able to go to the next points field with a single keyboard press while grading labs or quizzes.
Perhaps N for next and P for previous. I initially though of the up and down arrows, but they already have meaning for number inputs.

Completed this in the latest commit


Refactor Container Logs Elasticsearch Index Name creation to generate less indexes

Currently we just use the Kubernetes Namespace name as the indicator for index names of container logs inside elasticsearch: container-logs-${record['namespace_name']}-${Time.at(time).strftime("%Y.%m")}
The problem is that with having many PR environments we create a new index for each PR environment even though they only have a couple of hundred log entries. This makes the elasticsearch slow.
Therefore we would like to change the index name to separate between the environment type (where we currently have production and development):

container-logs-${lagoon-projectname}-${lagoon-environmenttype}-${Time.at(time).strftime("%Y.%m")}

In order to do this we're missing two essential pieces in the payload of the container logs:

lagoon project name
lagoon environment type

Fluentd has the possibility to inject the labels of the namespace into the payload of the container logs, therefore the plan is:

[ ] Inject the Lagoon ProjectName, EnviornmentName, EnvironmentType as a label into the Kubernetes Namespace when we create the namespace, but also when we redeploy (in order to handle namespaces that don't have the labels yet, but also in case the environment type change)
[ ] create a script that add/updates the labels in all the namespaces created by lagoon
[ ] Update the Fluentd config https://github.com/amazeeio/lagoon/blob/master/services/logs-forwarder/.lagoon.multi.yml#L223-L228 to check for these new variables and if they exist use them instead of the current way (but provide a fallback to use the old system, plus also for namespaces that are not created by lagoon - like default)

possible fluentd plugin for pod/namespace data to container logs - https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter

@tobybellwood
yes, we're using that already, or better: the openshift image we use: https://github.com/amazeeio/lagoon/blob/master/docker-compose.yaml#L394 uses it for us :)

heh!  nothing to see here, carry on


I want to create new pull requests sorry

I want to create new pull requests sorry

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


Add playbook action to enrich the Prometheus alert KubeJobFailed

Motivation
This is a common Prometheus alert and we should enrich it out of the box.

@wahajXgrid , I Just created a PR for that yesterday

I created 2 separate actions


Adding pkg dev key, pdf, png, and thumbnails for new package dev cheatsheet

Contributed Cheat Sheet Information
Cheat Sheet Name: Package Development
1 sentence description of the contents:  N/A
Your Name (as you want to be credited on the website):  N/A
A link to your github/website (optional):  N/A
A link to relevant package documentation (optional):  N/A
Date created/updated (Month YYYY format):  July 2022

Please be sure you've included the Creative Commons License:

[X] Add CC-BY-SA Your Name to copywrite under the Creative Commons on the cheat sheet

Check that you have done the following:

[X] Used descriptive file names, something like package-name.pdf or task-name.pdf and did not include "cheat sheet" in the title.
[X] Included a PDF file of entire cheat sheet.
[X] Included a PNG file of the first page size 1100 x 850 in the pngs folder (for the website thumbnail).
[X] Included a Keynote or PowerPoint or similar file in the relevant folder (helps translators who want to translate your cheat sheet).

Resolves #45 I think

Thank you!


Change the dependency specifier

Codecov Report

Merging #10 (bb20f51) into master (3a61034) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
@@           Coverage Diff           @@
##           master      #10   +/-   ##
=======================================
  Coverage   89.74%   89.74%
=======================================
  Files           2        2
  Lines         234      234
=======================================
  Hits          210      210
  Misses         24       24

Flag
Coverage Δ

unittests
89.74% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Top posts in sidebar

Another idea (lurked in WordPress) came to my mind. A list of "top posts".
I could be a separate (optional, probably disabled by default) section in the sidebar, displayed probably between Posts and Tags. It would be powered by the weight mechanism added to particular posts (added and updated occasionally by hand, based on number of hits or whatever else) . While the same weight value (or lack of) for 2 or more posts they should be sorted by date descending.
It would be required to change the "Posts" header to "Recent Posts" and to add "Top Posts" (probably using Title from _index.md for the "Posts" name).
WDYT?

It can be easily implemented using weight
---
title:
...
weight: 1
---

If you need this feature, add it.

It would be required to change the "Posts" header to "Recent Posts" and to add "Top Posts"

Yes, It should be changed manually

I would like to have it in my blog, so if it is not problematic to implement I will be happy to see it in Zzo :).
It should be rather disabled by default to do not confuse existing users of your theme.

It can be done with .ByWeight keyword thanks for the Hugo
I'll commit code after I fixed another issue.

I committed the code!
You can set weight front-matter.
You should set it 1 or above

Oops, I misunderstood.
You mean display top post in the sidebar.
I’ll do it tomarrow.
I’m going to sleep now

Yes, another lists in the sidebar :).
Sleep well ;-)

I added another list in the sidebar.
Follow the below steps.

In your params.toml file,

...
enableSidebarPostsByOrder = true

Add a new i18n item to your i18n file. e.g: root/i18n/en.toml

...
[posts-by-order]
other = "MY TOP POSTS"

Add new front-matter order to your post md file.

---
title:
...
order: 1
---

I've just tested it and it works great, thanks!
Two small suggestions:

Maybe it would be good to add [posts-by-order] entry to the *.toml provided in your theme by default (to have it localized by default once enabled)?
Having no pages in order found it the list header could be omitted (the same as for series, tags, ...).

Btw, having commits related to some GitHub issue you could put [#184] somewhere in the commit message. Thanks to that, it will be referenced in that issue (and there will be a link from the commit to it). It would be useful to people trying to get more information about the implementation of a given feature/bug fix.

I was tried to do that.
But it closes the issue automatically

Maybe you wrote fixes #XX. Just #XX shouldn't close it. I propose to try it again - maybe it was a bug then.

I'll try again here

#xx close issue automatically.
Maybe it's a bug or intended behavior.
Anyway, I did your suggestions https://github.com/zzossig/hugo-theme-zzo/issues/184#issuecomment-588179493

It is intended. You requested to close it:

See here for the supported keywords
if you don't want to close it just put #184 and there will be a reference.

It's good information! Thanks

You made my life easier by fixing this.