Documentation feedback

This is a tracking issue for feedback on the new documentation at https://docs.astral.sh/uv/

https://docs.astral.sh/uv/concepts/python-versions/#adjusting-python-version-preferences
it is not clear with what subcommand i can use --python-preference only-managed to set it permanently.

We don't have a commands to modify a persistent configuration file — you can put it in a uv.toml or pyproject.toml per

https://docs.astral.sh/uv/configuration/files/
https://docs.astral.sh/uv/reference/settings/#python-preference

Thanks for the feedback though! Sounds like we should link to the persistent configuration documentation here.

A little suggestion: add the use of generate-shell-completion to First steps with uv
I habitually use --help to see what commands I can use.
Then I realized that there was no completion command, and didn't search for it until I want to open an issue!😝
PS: I don't understand why it should be hidden in --help. Except for this command, the outputs of help and --help are almost identical!

I'm not sure why it's hidden — I copied this from Ruff. I think it might be because it shifts the indent for the rest of the commands way to the right and dramatically reduces the space we have for concise documentation.

Maybe we can improve the uvx to uv tool transition in the guide https://github.com/astral-sh/uv/issues/6334#issuecomment-2302439899

On getting-started/installation/#standalone-installer it says

When uv is installed via the standalone installer, self-updates are enabled

This sounded to me as if uv would automatically update itself (like many GUI apps do), but it seems this is not the case. I guess it just means uv self update is not available at all unless the standalone installer was used. I think wording here could be improved to clarify that.
By the way, I added this to my crontab to get auto-updates:
00  * * * * uv self update

Minor confusion for me in https://docs.astral.sh/uv/concepts/tools/, emphasis mine:

Tools can also be installed with uv tool install, in which case their executables are available on the PATH — an isolated virtual environment is still used but it is not treated as disposable.

...

When running a tool with uvx or uv tool run, a virtual environment is stored in the uv cache directory and is treated as disposable.

For uv tool, the venv is, or is not treated as disposable?
Furthermore, what does it mean "disposable" in this context?

Maybe we can improve the uvx to uv tool transition in the guide https://github.com/astral-sh/uv/issues/6334#issuecomment-2302439899

One suggestion would be to reiterate in the CLI reference docs for uv tool run that it's also available as uvx. Users might end up there via google searches and not be aware that there's an alias.
Another thing is that in the tool concepts page, it directly references uvx in these ways:

Tools can be invoked without installation using uvx ...
When running a tool with uvx or uv tool run, a virtual environment is stored...

In both these cases, the implicit assumption is that the user knows that uvx is an alias for only uv tool run and that it invokes the tool instead of installing it (hence the x, rather than r, which is what one would intuitively think would be the alias). But the only way to know these distinctions is to have carefully read the tools guide section of the docs first, and not all users may end up on the guide page first and read things in the exact order they're shown in the sidebar 😅.

(Thanks for the feedback everyone, I'll attempt to address all that)
We should talk about defining constraints in the pyproject.toml in the project concept per https://github.com/astral-sh/uv/issues/6425

@gusutabopb let me know if #6468 is sufficient!
@minusf and @prrao87 I've attempted to address those in:

https://github.com/astral-sh/uv/pull/6474 and
https://github.com/astral-sh/uv/pull/6455

Hi! I hope this is the correct place, but I would request examples for:
Other indexes[#](https://docs.astral.sh/uv/#other-indexes)

uv is also known to work with JFrog's Artifactory, the Google Cloud Artifact Registry, and AWS Code Artifact.

I ask because this does not work from my existing pyproject.toml:
my-custom-package = {version = "0.0.5", source = "my-pip-repo-happens-to-be-gcp-artifact-registry"}
# ...

[[tool.poetry.source]]
name = "my-pip-repo-happens-to-be-gcp-artifact-registry"
url = "https://us-west2-python.pkg.dev/my-gcp-org/hello/simple/"
priority = "explicit"

I add auth to the config by running:
$ pip install keyring
$ pip install keyrings.google-artifactregistry-auth
$ gcloud auth application-default login
$ poetry config http-basic.my-pip-repo-happens-to-be-gcp-artifact-registry oauth2accesstoken "$(gcloud auth print-access-token)"

Finding the equivalent of that last line for uv is what has me stumped.
I'm similarly interested in jfrog examples, but this is the one I can provide the most specific details on.

The FastAPI guide needs to be updated to reflect the changes introduced to the default behavior of uv init in version 0.4.0. The current docs still say a src -based layout would be created: https://docs.astral.sh/uv/guides/integration/fastapi/#initializing-a-fastapi-project

uv can be installed on Windows using winget, but this isn't mentioned in the docs. Could/should it be added as an alternative installation method along with homebrew etc?

I'm not sure why there's a python-version file if this information is also in the pyproject.toml.

The docs mention a UV_INSTALL_DIR variable, but that doesn't work. There's no such variable in the installer.

The documentation about running scripts using the inline metadata (link) doesn't mention support for specifying the dependency sources via the tool.uv.sources section, but it does seem to support it when I run, for example:
# /// script
# requires-python = ">=3.12"
# dependencies = [
#     "requests",
# ]
# [tool.uv.sources]
# requests = { git = "https://github.com/psf/requests.git", tag = "v2.32.2" }
# ///

import requests

print(requests.__version__) # 2.32.2 (2.32.3 is the latest)

I think the documentation can be explicit about officially supporting (or not supporting) it.

@shunichironomura thanks! I think we need to create a separate "Scripts" concept page because that's way too advanced for the "guide" documentation.

Would be nice to have information on whether virtual workspaces (no project and build-system sections in pyproject.toml?) like Cargo are supported.

That is still an application that has its own python code from what I can tell. The Cargo virtual workspaces just combine related packages together, where there isn't necessarily one "main" binary.
Taking from the workspace example in uv docs,
albatross
├── packages
│   ├── bird-feeder
│   │   ├── pyproject.toml
│   │   └── src
│   │       └── bird_feeder
│   │           ├── __init__.py
│   │           └── foo.py
├── squirrel-feeder
│   │   ├── pyproject.toml
│   │   └── src
│   │       └── squirrel_feeder
│   │           ├── __init__.py
│   │           └── foo.py
│   └── seeds
│       ├── pyproject.toml
│       └── src
│           └── seeds
│               ├── __init__.py
│               └── bar.py
├── pyproject.toml
├── README.md
└── uv.lock

imagine bird-feeder and squirrel-feeder were equally important packages with the common seeds dependency.
And just to be clear, I'm not asking this feature to be implemented, only clarification on whether or not it is supported because the documentation page explicitly refers to Cargo.

I have a couple questions about the lockfile after reading the docs on it.
Is the uv.lock file specified anywhere? I looked at https://docs.astral.sh/uv/concepts/projects/#project-lockfile and expected to find a schema or a link to a schema or specification for what can go in uv.lock.
The reason I'm looking for a schema / specification is that I would like to be able to parse uv.lock files so that I can add a uv.lock parser Syft.
My other question is whether you expect the uv.lock file to remain stable, or whether there is planned work to change or extend its schema.

The Cargo virtual workspaces just combine related packages together, where there isn't necessarily one "main" binary.

@scimas Virtual projects were removed in #6720 (from the docs at least - cannot quickly find other pointers)

@scimas -- Yeah that layout is fully supported. You can create a pyproject.toml at the root that is not itself linked to any Python code, and just lists workspace members and dependencies, i.e., a virtual workspace root as in Cargo.
@astrojuanlu -- We removed most mentions of "virtual" since it wasn't a familiar concept, but the idea of a project that just lists members and dependencies is still supported.

@willmurphyscode -- It's not documented anywhere, only implicitly in code. We don't have any planned changes but I'm sure it will change over time (it's also versioned). Separately, if PEP 751 is approved (which I've been very involved in), we'll likely migrate to whatever the approved format is, if it works for uv.

The section Non-editable installs led me to a mistake.
It mentions the following:

By default, uv installs projects and workspace members in editable mode...

And then:

In the context of a multi-stage Docker image, --no-editable can be used to include the project in the synced virtual environment from one stage, then copy the virtual environment alone (and not the source code) into the final image.

The problem is that, if I understand correctly, this is only true if the project was created as a library (uv init --lib).
An app project doesn't seem to be installed as editable by default in the venv (contrary to what the previous quote says).
Since the example Dockerfile shown there is clearly for an application, it got me confused for a while.
I suggest to make it more clear that only library projects are installed in the environment, regardless of the flag --no-editable.

https://github.com/astral-sh/uv/issues/5605#issuecomment-2340069888 :

I'm not sure why there's a python-version file if this information is also in the pyproject.toml.

@zanieb I would also like to know this.

@debnath-d The .python-version file can be read by other tools like GitHub Actions to determine which version to install. The version file pins to a single version whereas the pyproject.toml field is intended to define a range of versions supported by your application or library (per the Python standards).

@debnath-d The .python-version file can be read by other tools like GitHub Actions to determine which version to install. The version file pins to a single version whereas the pyproject.toml field is intended to define a range of versions supported by your application or library (per the Python standards).

For me, if you use uv init --lib, it makes sense to have requires-python and .python-version. But if you use uv init --app, I think it isn't useful (requires-python is not required and you already have .python-version).
It's the same feeling I have when I use uv init --app and the description field is added to my application with a default value I'll never use.
If requires-python could be used by child packages it'd be okay, but when you run uv init --lib inside a project, another pyproject.toml with a requires-python is created. For example, in my .NET repositories, I define the .NET version of all packages in a root file (similar to pyproject.toml).
BTW, pyproject.toml can also be used with GitHub Actions.

It would be great if you:

Add some example(s) of a larger and more complex project/workspace.
If you add an example of how to use Hatchling build hooks.

I think it would be great if there a page about how to migrate from poetry.

In the documentation about configuration, I find it confusing that many settings can be set in both tool.uv and tool.uv.pip (and they seem to have the same description).
What is the difference? Is there inheritance? Should I set them in both places?
List of the 23 impacted settings at the time of writing

allow-insecure-host
compile-bytecode
config-settings
dependency-metadata
exclude-newer
extra-index-url
find-links
index-strategy
index-url
keyring-provider
link-mode
no-binary
no-build
no-build-isolation
no-build-isolation-package
no-index
no-sources
prerelease
reinstall
reinstall-package
resolution
upgrade
upgrade-package

@mdegis you can track that at #5200
@Rogdham please see https://docs.astral.sh/uv/configuration/files/#configuring-the-pip-interface

It'd be good to mention in the working on projects section of the guide, perhaps under the "running commands" part, that you need to include a build system or the library won't be available. This is a pretty confusing footgun that lost me most of a day while trying to work out why pytest wouldn't find my library.
The only mention of this I can find is an easy-to-misread sentence under the build systems part of Concepts -> Projects.

👍 sorry to hear that @yaleman — that change was made after we wrote most of the documentation and I've been meaning to rewrite the project documentation to account for that.

@Rogdham please see https://docs.astral.sh/uv/configuration/files/#configuring-the-pip-interface

Thank you for this, much helpful! Maybe just add a link to it in https://docs.astral.sh/uv/configuration/files/#configuring-the-pip-interface?
A small note in each field of pip config saying that it inherits would be ideal, but I understand that this is quite some work for little benefit.

Thanks for your work on the project.
It would greatly help to write a way to change these environment variables. I am a bit lost how to change UV_TOOL_DIR to something different. In other words, change the result of uv tool dir
https://docs.astral.sh/uv/configuration/environment/
Here in the documentation it says to change the environment variable but nowhere on how to do that
https://docs.astral.sh/uv/concepts/tools/#tools-directory

https://docs.astral.sh/uv/guides/tools/
In this page, the documentation reads
"The uvx command invokes a tool without installing it."
Then a few lines down it says:
"When uvx ruff is invoked, uv installs the ruff package which provides the ruff command."
So does uvx install the package or not? Thank you for your work on this project :)

https://docs.astral.sh/uv/guides/integration/github/
Do I have to specify enable-cache in a separate caching workflow step, or do I simply add it to the original setup-uv step?
- name: Enable caching
  uses: astral-sh/setup-uv@v3
  with:
    enable-cache: true

Will this cache both Python and dependencies?

How do I actually work with the uv.lock file?
I have pushed it to the repo, and are now pulling it on another computer. If I do uv.sync then the uv.lock file is emptied to reflect (the empty) pyproj.toml. But I want the opposite, that all the packages in uv.lock are installed to pyproj.toml?

The dependencies are primarily specified in pyproject.toml, then uv sync updates uv.lock with the exact versions of what it installed. The uv.lock file is not meant to be manually edited.

In addition to the poetry migration guide requested above, migration guides for pipenv, requirements.txt, and even direct from the environment would be helpful. It took too long to find that the -r requirements.txt semantics from pip install works with uv add.
Really a nit -- The concept pages are very in the weeds with details about the CLI. Being more opinionated on the patterns/anti-patterns of python project/dep/version/tool management with uv and focusing on concepts that influence user decisions (e.g. do I use ux tool or install a dev dependency) in the concepts guides would be helpful. Like for tools, the "Execution vs installation" section is the really critical "concept" there.

Would be nice to clarify the "packages with independent requirements" case. The "when (not) to use workspaces" section conflates

Actual use cases for workspaces:

https://github.com/astral-sh/uv/blob/94fc35edd91bf9773470db08a82925c066693f6d/docs/concepts/workspaces.md?plain=1#L152-L165

Use cases not well suited for workspaces

https://github.com/astral-sh/uv/blob/94fc35edd91bf9773470db08a82925c066693f6d/docs/concepts/workspaces.md?plain=1#L167-L168
It would be nice if the latter were more clearly explained, specifically the "independent/loosely related packages with possibly conflicting dependencies". The docs give an example of a "path dependency", but that seems to be targeted to a root member depending on a subpackage, which maybe isn't even needed. And the potential overlap with Dependency Groups is unclear.
Maybe a dedicated page (and, dare I say, another name?)

The dependencies are primarily specified in pyproject.toml, then uv sync updates uv.lock with the exact versions of what it installed. The uv.lock file is not meant to be manually edited.

My question was not how to edit the lock file, but how to let it dictate the dependencies of a project.

I don't quite understand. The lockfile is created from the pyproject.toml. The pyproject.toml dictates the dependencies of the project; the lockfile is downstream of that.

@charliermarsh Thank you for taking the time, and sorry for creating confusion.
From the documentation:

Unlike the pyproject.toml which is used to specify the broad requirements of your project, the lockfile contains the exact resolved versions that are installed in the project environment. This file should be checked into version control, allowing for consistent and reproducible installations across machines.

I understand how this important for two reason, knowing the exact packages and version used for every commit in the project, and if anyone want to fork or clone a project and replicate the environment.
So say that I fork SomeRepo, that contains a uv.lock, to a new machine and want to have the exact resolved versions that was installed in the project environment by the creator of SomeRepo. How do I interact with uv.lock to replicate the project environment as described in the file?
Reading the documentation it is described how uv.lock is generated (or how we avoid it to be changed), but it doesn't detail how uv.lock is used by uv.

So say that I fork SomeRepo, that contains a uv.lock, to a new machine and want to have the exact resolved versions that was installed in the project environment by the creator of SomeRepo. How do I interact with uv.lock to replicate the project environment?

Maybe uv sync --frozen is what you're looking for @bjornasm?

I think it would be better to have a chapter to introduce how to integrate uv into existing projects, or to improve the user experience of using uv to replace the tools it claims to replace.
Taking me as an example, I use pip/requirements.txt to maintain the dependencies of existing projects, use pyenv to manage multiple versions of Python interpreters, and use virtualenvwrapper to manage virtual environments. When I heard about the all-in-one tool uv, I was excited, but the next second I was frustrated: I had to figure out the details of UV to gradually replace these tools

If anybody is looking to get started with migrating from poetry to uv, I documented the approach I took here: https://github.com/astral-sh/uv/issues/5200#issuecomment-2468319391.

So say that I fork SomeRepo, that contains a uv.lock, to a new machine and want to have the exact resolved versions that was installed in the project environment by the creator of SomeRepo. How do I interact with uv.lock to replicate the project environment?

Maybe uv sync --frozen is what you're looking for @bjornasm?

Thank you, that seems what I am after!

Could you please provide information on the best way to install PyTorch with GPU support in a project that is portable across different systems and can be easily upgraded

Hi guys, I just wanted to report that the Discord invitation link provided here in the documentation is expired.

As a Chinese language user, I would like to inquire whether the UV community's documentation requires internationalization translation, and I am willing to contribute a Pull Request for the Chinese translation of the UV documentation.

Hey @GiovanniGiacometti — that link works for me still, are you sure?
@Muzych I appreciate the offer! I'm not quite sure how we'd maintain that — we make frequent changes to the documentation. What do you think the long-term plan for that would be?

Hello, my idea is to first complete the internationalization translation based on the current version, and then make minor adjustments to the details once UV's performance is stable. What do you think about this approach?

Hey @GiovanniGiacometti — that link works for me still, are you sure?嘿——那个链接对我来说还能用，你确定吗？
@Muzych I appreciate the offer! I'm not quite sure how we'd maintain that — we make frequent changes to the documentation. What do you think the long-term plan for that would be?我感谢您的提议！我不太确定我们该如何维护——我们的文档经常变动。您认为这方面的长期计划会是什么样的呢？

Hello, my idea is to first complete the internationalization translation based on the current version, and then make minor adjustments to the details once UV's performance is stable. What do you think about this approach?

A surprising behaviour I've noticed, that I couldn't see documented and possibly good to capture somewhere:
uv sync creates and uses .venv in the parent directory, when the parent directory contains pyproject.toml, and even if the current directory also has a pyproject.toml.

uv sync creates and uses .venv in the parent directory, when the parent directory contains pyproject.toml, and even if the current directory also has a pyproject.toml.

I think this should only be the case if the current directory is a workspace member of the parent directory.

Hello, my idea is to first complete the internationalization translation based on the current version, and then make minor adjustments to the details once UV's performance is stable. What do you think about this approach?

We'll be making large, frequent adjustments to the documentation. I'm concerned it will go out of date. Let's discuss this over in a dedicated issue https://github.com/astral-sh/uv/issues/9606

I think this should only be the case if the current directory is a workspace member of the parent directory.

In my case I hadn’t set up a workspace.

@tekumara that sounds like a bug, could you open an issue with a reproduction?

https://docs.astral.sh/uv/guides/scripts/ doesn't explain where uv creates environments and how to clean up them after.

Hello,
I came across a broken link while reading the documentation, so I thought I'd crawl the whole site to check.
The following are 404 pages:

url: Where the broken link is located
link: The URL of the broken link
text: The anchor text, just to make it easier to find the link on the page

url
link
text

0
https://astral.sh/blog/ruff-v0.5.0#changes-to-e999-and-reporting-of-syntax-errors
https://docs.astral.sh/ruff/rules/open-sleep-or-subprocess-in-async-function/
open-sleep-or-subprocess-in-async-function

1
https://astral.sh/blog/ruff-v0.5.0#changes-to-e999-and-reporting-of-syntax-errors
https://astral.sh/blog/`https:/docs.astral.sh/ruff/rules/blocking-os-call-in-async-function/`
blocking-os-call-in-async-function

2
https://astral.sh/blog/ruff-v0.5.0#changes-to-e999-and-reporting-of-syntax-errors
https://docs.astral.sh/ruff/rules/trio-async-function-with-timeout/
trio-async-function-with-timeout

3
https://astral.sh/blog/ruff-v0.5.0#changes-to-e999-and-reporting-of-syntax-errors
https://docs.astral.sh/ruff/rules/trio-unneeded-sleep/
trio-unneeded-sleep

4
https://astral.sh/blog/ruff-v0.5.0#changes-to-e999-and-reporting-of-syntax-errors
https://docs.astral.sh/ruff/rules/trio-zero-sleep-call/
trio-zero-sleep-call

5
https://astral.sh/blog/ruff-v0.5.0#changes-to-e999-and-reporting-of-syntax-errors
https://docs.astral.sh/ruff/rules/misplaced-bare-raise`/
misplaced-bare-raise

6
https://astral.sh/blog/ruff-v0.0.276
https://astral.sh/blog/settings.md#include
include

7
https://docs.astral.sh/uv/reference/build_failures/
https://docs.astral.sh/uv/pip/compatibility.md#pep-517-build-isolation
build isolation by default

8
https://docs.astral.sh/uv/reference/build_failures/
https://docs.astral.sh/uv/reference/settings.md#dependency-metadata
provide dependency metadata manually

9
https://astral.sh/blog/ruff-v0.2.0
https://docs.astral.sh/ruff/rules/trio-timeout-without-await
trio-timeout-without-await

10
https://astral.sh/blog/ruff-v0.2.0
https://docs.astral.sh/ruff/rules/trio-async-function-with-timeout
trio-async-function-with-timeout

11
https://astral.sh/blog/ruff-v0.2.0
https://docs.astral.sh/ruff/rules/trio-unneeded-sleep
trio-unneeded-sleep

12
https://astral.sh/blog/ruff-v0.2.0
https://docs.astral.sh/ruff/rules/trio-zero-sleep-call
trio-zero-sleep-call

Code to reproduce (or if you want to run this periodically):

import advertools as adv
import pandas as pd

adv.crawl(
    url_list="https://astral.sh/",
    output_file="astral.jsonl",
    follow_links=True)

crawldf = pd.read_json("astral.jsonl", lines=True)

error_urls = crawldf[crawldf['status'].ne(200)]['url']
linksdf = adv.crawlytics.links(df)

linksdf[linksdf['link'].isin(error_urls)]

Thanks!

@eliasdabbas cool thank you! cc @dhruvmanila for Ruff's documentation.

@zanieb it still may worth to mention it somewhere in the middle, or link to relevant cleanup docs. I assume uv users are advanced enough to care.

Hi! I noticed the documentation about configuring alternative indexes seems to be outdated and incomplete: https://docs.astral.sh/uv/guides/integration/alternative-indexes/

It doesn't mention anything about [[tool.uv.index]] settings, which are useful
In Environment variables, UV_EXTRA_INDEX_URL is said to be deprecated, but in the alternative indexes page it is used.

Also the Environment variables page doesn't explain how to properly authenticate to alternative indexes other than embedding the credentials in the URL
Have a good day!


What versions of Visual Studio are supported and outdated documentation?

What versions of Visual Studio are supported? I tried in VS 2015 but it fails to load the SDK project.
Also the documentation doesnt line up with the latest version of the MessageMedia dlls. Can you please update the documentation?

Unfortunately, we don't support multiple versions of the SDK project yet. The current SDK project uses the .NET standard project format which VS2017 supports natively. If you're looking to contribute, feel free to build a version for VS 2015 or if you're trying to use the SDK to send messages, my advice would be looking at the "Installing via NuGet" section of the readme.
The documentation has been updated. Thanks for pointing that out!


Reusing scripts for live resources & no more deploy buttons

This DRAFT PR is here to save us from the Deploy button rabbit hole and put us back in track with powershell.
The Deploy Button approach has considerable caveats. Some of them being:

The forms they generate don't provide a lot of tooling to explain how to fill these properties.
The forms they generate require considerable knowledge to feel its properties.
They appear to be simple at a first glance, but they require considerable documentation to make them viable for general users.

Instead of continuing to go the route of Deploy Buttons, we can re-use the PowerShell programs that have been made available in out TS/JS SDK just as well as they exist in the other languages' SDKs, and which have already been documented once at the root of the project, and only make reference to these tools in the test folders, where contributors will surely check. Other general consumers should be safe by ignoring these and simply following the available Azure documentation to create any resources for their own programs, without having to worry about the specific needs of our integration tests.
This PR does the same change on all of the other projects that have test-resources.json.
Once this is merged, the following issues will be solved:

Closes #7532 , since it will be OK to keep template parameters in the ARM templates.
Closes #7366 , since the new indications will suffice.
Closes #7365 , since the new indications will suffice.
Closes #7364 , since the new indications will suffice.
Closes #7363 , since the new indications will suffice.
Closes #6647 , since there will be no remaining pending tasks.

@xirzec part of the idea behind the deploy button was to make it easier for other devs, even in our own team, to be able to have the exactly configured resources to run all of the tests. When we started working with the deploy button, the powershell code existed for CI, but it wasn't ready to be used standalone for these deployments. The deploy button worked, and it seemed like we could use it for collaborators to have things ready for them to run the live tests and do their changes. Over time, Heath and Daniel Jurek have made this powershell tool, and the docs around it, useful for more than just CI ! So that solves the underlying problem behind the deploy button.

@danieljurek
Hi hi! So,

I'm not sad to see the actual buttons go, but I am sad to see the concept of the button go away.

I like the theory of the button as being a turn-key deployment for our customers (we can always write better or more extensive documentation for contributors, but my experience with ARM templates so far suggests that we should hide them from end-users as much as possible -- even having to figure out what the "Object ID" of a service principal is can send you down an hours-long rabbit hole of insane errors with zero documentation in the ARM reference). I'd be interested in exploring ways that we can get the same kind of thing, where anyone who lands on our NPM page can have a quick path to getting a free resource created and some credentials to play with it in Node or maybe even in a browser playground?
I've made this issue to continue the conversation with a more general perspective. Seems like other languages would benefit from this:

Issue regarding deploy buttons in general, but more specifically with the samples and the test readmes: https://github.com/Azure/azure-sdk/issues/1247
Issue specifically related to the guidelines for the main package's readmes: https://github.com/Azure/azure-sdk/issues/1248

Also, I'm not sure I'm a fan of repeating the same information in so many places. These READMEs only show up here, so why not create this information in a central place and link to it? It seems like it will become a pain to have so many README's with mainly the same information. They really only differ in the environment variables that are used in each package. When we sort out the integration/unit difference, we will have to go back and edit all of these. Maybe we could use our GitHub wiki?

@ramya-rao-a what do you think of moving our samples' and test's readmes into a common location?

I am in agreement with @willmtemple regarding having a single location with most of the instructions that are now being added as test readme. The individual test readme should have

pointer to the central location
env variables that the tests for the particular project need
anything that is specific to the particular project

like the fact that in service bus, the queue/topic/subscription gets created automatically for each test
or that service bus and event hubs do not have recordings

I would expect the central location to be the Contributing.md file we have in the root of this repo.  There is a section called Building. We can have a section called Testing right after that. We should take care to not put too much text here. I'll add comments to the app config readme being added in this PR on things I believe we should keep and those that we can skip

@ramya-rao-a Hi! I believe I've followed all of your feedback in this PR. Please review it again! Let me know if I missed or misinterpreted anything 🖖

@ramya-rao-a I believe I have addressed all of your feedback so far. Please review again!


View IP and show pop-up

What the program do ?
View IP and show pop-up
In what programming language it is written?
batch script

:)


[Low Priority Question] How to get Miri working with -Zprofile Flag?

Hi.
I have a niche use case that requires compiling and running a few
million test cases. I'm looking for ways to reduce the compile time
while running both coverage analysis (currently grcov) and miri.
I ultimately figured out that I can run cargo test with -Zprofile
and cargo miri test in an "normal" environment without having to run
cargo clean between the 2 commands. This saves significant amount of
time, and makes our project feasible.
However, my original plan was to:

Modify Miri at
https://github.com/rust-lang/miri/blob/master/src/bin/miri.rs#L82-L91
so that the compilation will continue after interpretation and
write out interpretation results into a file (latter not
implemented yet).
if let Some(return_code) = miri::eval_main(tcx, entry_def_id, config) {
             // std::process::exit(
             //     i32::try_from(return_code).expect("Return value was too large!"),
             // );
         }
     });

     // compiler.session().abort_if_errors();

     Compilation::Continue

Run the modified Miri (cargo miri test) with the grcov flags given in:
https://github.com/mozilla/grcov#example-how-to-generate-gcda-files-for-a-rust-project
export CARGO_INCREMENTAL=0
export RUSTFLAGS="-Zprofile -Ccodegen-units=1 -Copt-level=0 -Clink-dead-code -Coverflow-checks=off -Zpanic_abort_tests -Cpanic=abort"
export RUSTDOCFLAGS="-Cpanic=abort"

Run the instrumented binary to gather coverage without compiling
twice.

Gather both coverage and Miri interpretation result.

The original plan fails while compiling the target library:
error[E0463]: can't find crate for `profiler_builtins`
  |
  = note: the compiler may have been built without the profiler runtime

For more information about this error, try `rustc --explain E0463`.
error: could not compile `cfg-if` due to previous error
warning: build failed, waiting for other jobs to finish...
error: build failed

I'm curious as to what is causing this failure?
While it is not a critical issue for us, the original plan is still
preferable as cuts the compile time, our largest bottleneck, in
half.
I understand this is a very odd use case, so I don't mind if you
prioritize other issues over this one.

I'm curious as to what is causing this failure?

Miri needs to compile a separate sysroot to get MIR for all functions. This sysroot is probably compiled without profiler support.

Run the instrumented binary to gather coverage without compiling twice.

Miri and regular execution require separately compiled programs. They use different sysroots and compilation options. You can use CARGO_TARGET_DIR to set a separate target dir for miri and regular execution, removing the need to clear anything (not that cargo clean should be necessary anyway I think), but you will need to compile once for regular execution and once for miri unless you avoid the cargo miri wrapper and manually compile a sysroot suitable for both miri and regular execution.

I also agree that cargo clean is not necessary. Even without
CARGO_TARGET_DIR Miri seems to generate a separate target directory
by default.
As of now, cfg(miri) and Windows targets are not in scope. We are
only targeting 64bit Linux and we don't generate any test cases with
cfg(miri).
Thank you for the suggestions! They make sense to me as cargo-miri --print sysroot does contain profiler libraries, but the
~/.cache/miri/HOST/ does not. I'll give them a try.

As of now, cfg(miri) and Windows targets are not in scope. We are
only targeting 64bit Linux and we don't generate any test cases with
cfg(miri).

What I am saying is that there are cfg(miri) in the standard library and other crates (e.g. hashbrown). The Miri sysroot is build with cfg(miri). If you want to use a single build (and hence a single sysroot) you thus will end up building a regular binary with cfg(miri), which is an entirely untested and unsupported configuration.

cargo-miri --print sysroot

cargo-miri --print sysroot does not really make much sense as a command... (and it shows an ICE for me). Maybe you mean miri --print sysroot, but that is just the default rustc sysroot which is unsuited for Miri. cargo miri sets an appropriate sysroot when invoking miri.

Thanks for the clarification; I agree that would not be avoidable.

cargo-miri --print sysroot

is a typo. I meant cargo-miri rustc --print sysroot. This prints out the same thing as

miri --print sysroot

This is not very actionable on our side, so I am going to close the issue. There currently are no plans to officially support using the Miri sysroot for building a real executable. If concrete questions come up about how Miri's sysroot handling works, feel free to reopen, open a new issue, or ask on Zulip!


False positive for MethodCallWithoutArgsParentheses

If I have a local variable in scope with the same name as a method I want to call, I have two options:

Write self.foo instead of foo
Write foo() instead of foo

Both clarify to ruby that this foo is a send node. The second option though isn't respected when there is a local variable in scope

Expected behavior
This code does not generate an offense with the cop in question
$ cat ex.rb
def foo
  puts 'Hiya'
end

bar = 1
foo = bar
result = foo()

$ rubocop --only MethodCallWithoutArgsParentheses ex.rb
Inspecting 1 file
.

1 file inspected, no offenses detected

Actual behavior
It tells me to remove the parenthesis but I want to write foo() and not self.foo
$ cat ex.rb
def foo
  puts 'Hiya'
end

bar = 1
foo = bar
result = foo()

$ rubocop --only MethodCallWithoutArgsParentheses ex.rb
Inspecting 1 file
C

Offenses:

ex.rb:7:13: C: Style/MethodCallWithoutArgsParentheses: Do not use parentheses for method calls with no arguments.
result = foo()
            ^

1 file inspected, 1 offense detected

RuboCop version
0.49.1

Should there also be a ShadowingInstanceMethod, like there's ShadowingOuterLocalVariable? 🤔

As an additional note, this also has semantically incorrect autocorrect behavior:
Given that we have a method and lvar like so:
def correct
  true
end

correct = false

Before autocorrect:
puts "Prints true? #{correct || correct()}" # => Prints true? true

After autocorrect:
puts "Prints true? #{correct || correct}" # => Prints true? false

I imagine encountering it is semi-rare, but it happened to me recently. :(

This is not the most common code, but I believe the false positive is still valid (and the advice causes a semantic change!) and could be detected by examining the local variables in scope. @Drenmi's suggestion might make sense for most people, though every time I've actually done this it's been helpful--usually to avoid some name forced upon me by a dsl or to do some kind of local memoization without using an ivar.
Is there a local variable scope helper in rubocop? If there is something that can give you a list of what's in scope easily, this should be pretty easy to avoid.


Animation

In SVG it is possible to do something such as:
<ellipse id="E" cx="90" cy="90" rx="30" ry="40" fill="#448">
<animate attributeName="rx" dur="5s" values="20;90;20" repeatCount="indefinite"/>
<animate attributeName="ry" dur="5s" values="30;60;30" repeatCount="indefinite"/>
</ellipse>
where the animation run continuously.  Cannot get a similar effect out of element.animate.  Thanks

Hmm... I have the same question. @ghost have you figured out the answer yet ? I am having the same question as you.

You could always create a callback that starts the animation on completion. Or as in the example create a pure markup animation.

ahaan got you, but the markup animation is not supported in all the
browsers.


Update README.md

Implement the solution discussed here: https://github.com/EngoEngine/engo/issues/178
Closes #213

This needs a final round of review, free for anyone to do so also free for @paked @EtienneBruines to merge it in.

@otraore Woo!


Datafiles configurable actions

Description
This PR is adding a configurable datafiles actions. Such actions can be configured through the config file and do not need any additional custom code. Actions can call any URL through a POST call and have a configurable label and icon.
Motivation
Site admins have the need to configure and customize the datafiles actions to their IT infrastructure. For example, adding a button that produced a notebook ready to load the dataset and the selected files. This work is the first attempt to provide such functionality
Changes:
Please provide a list of the changes implemented by this PR

datasets/datafiles/datafiles*
datasets/datafiles-actions/datafiles*

Tests included

[ ] Included for each change/fix?
[ ] Passing? (Merge will not be approved unless this is checked)

Documentation

[ ] swagger documentation updated [required]
[ ] official documentation updated [nice-to-have]

official documentation info
If you have updated the official documentation, please provide PR # and URL of the pages where the updates are included
Backend version

[ ] Does it require a specific version of the backend
which version of the backend is required:

Examples of the new setup


A way to rename chrono graphql types ?

Im currently using the provided graphql scalar output types for things like NaiveDate and NaiveDateTime, these work well however soon i will have to implement types which are compatible with an existing ruby/rails graphql service, for 99% of types this is fine but for inbuilt types like Datetimes it becomes problematic:
An ISO8601 datetime type using the current async graphql chrono types is called NaiveDateTime however in ruby the equivalent type is called ISO8601DateTime this causes issues when using graphql mesh or schema stitching.
I'm wondering if there is a way to rename the NaiveDateTime type to ISO8601DateTime in my codebase ?
I have seen the documentation for custom scalar types using the Scalar! macro but not sure how this can be done for an external type like chrono NaiveDateTime

Hi @sunli829 i got round to testing the new function, however it returns a compiler error, I'm using it as follows (simplified)
 Schema::build(Query, EmptyMutation, SubscriptionRoot)
.override_name::<NaiveDateTime>("ISO8601DateTime")
.finish();

Compiler returns the following error
error[E0632]: cannot provide explicit generic arguments when `impl Trait` is used in argument position
  --> src/graph/schema.rs:35:30
   |
35 |             .override_name::<NaiveDateTime>("ISO8601DateTime")
   |                              ^^^^^^^^^^^^^ explicit generic argument not allowed

error: aborting due to previous error

I also tried the new type marco, it doesn't seem to rename the actual output type on the schema.
so for something like

Sorry, I found that my previous implementation was incorrect, and I realized that renaming a type is very difficult, so I will delete the SchemaBuilder::override_name function.

Released in v2.7.2 🙂

Tested the new macro options and works perfectly. Many Thanks :smile:  ... closing the issue

@dhendrie91 @sunli829
Do we have any way to rename it without introducing a new struct?


RFC: Unsafe Storage

Up to this point, swift-nonempty has compiler-proven, safe storage for its underlying collection. This has the ultimate benefit of not having to unsafely unwrap values anywhere, but it comes with a number of downsides:

We currently maintain a lot of logic around pretending a head element and a tail collection are a single, baked collection. This includes index math code, and it turns out it has some bugs!
We can't always vend out the raw collection type, since we hold onto the head element outside its collection and not every collection provides a conformance that allows re-insertion of that head element.
We pay a performance cost. While _modify semantics improves this, we ultimately can't be as performant as code that merely holds onto a single collection under the hood.

This PR converts the project to a simpler, less-safe storage of the underlying collection. A few notes:

This introduces a failable initializer init?(rawValue:).
This removes all logic we maintained around connecting the head and tail properties together. All conformance code merely forwards things on to the underlying collection, unsafely unwrapping elements where applicable. This means all this code is potentially a fatal error waiting to happen, but at least the behavior is more apt to be correct when it doesn't crash.
It is no longer possible to provide the "safe" init(head:tail:) initializer for every collection because it's not possible to prepend just any collection with an element. This seems like an acceptable loss.
NonEmpty is now raw-representable (using its failable initializer). This is nice for Point-Free's routing.

This PR also provides an alternative fix for #4 (and #17) and could get us closer to #19...

I'm glad you've gone down this route. I have my own version of a NonEmptyArray that I use and it's based off of https://github.com/khanlou/NonEmptyArray which uses the same kind of "unsafe" but realistically safe implementation.
I like your implementation more because it's more generic and you can use it for things other then arrays.

💯 for this


open in browser

for some reason my open in browser packet does not want to work, did I download the wrong one? is there something else I need to be doing?

Make sure you are right-clicking on the index.html file and not the sketch.js file.
We can only open html files in the browser, these then call JavaScript (sketch.js in our case) files.
Any chance this is what was happening?

Yes that was the issue thank you!

Had this same issue, thanks!


lat and lon attributes for an orbit?

Having .lat and .lon as attributes might allow one to get the latitude and longitude coordinates of an orbit from its position vector.
If one gets the position vectors in the inertial frame of the attractor (for eg: for an orbit around the Earth, orbit.r would give the position vector in the Earth's inertial frame - GCRS), converts those to be with respect to a non-inertial frame (eg: ITRS for Earth as the attractor), one might then get the lat and lon values.
Using astropy, the conversion might boil down to just a few lines of implementation.
This might simplify some logic in groundtracks.py where the logic for Earth has already been implemented here and future efforts related to latitude and longitude coordinates.
Any ideas/suggestions on this would be helpful.
Thanks!

I think this would be a good enhancement... however we would need to clarify some definitions.
It's not clear what latitude we would be referring to: planetocentric latitude? or planetodetic latitude? If we have the ellipsoids of all bodies, then giving the planetodetic latitude would match people's expectations more I think (one rarely wants the planetocentric latitude).
And about the longitude, what meridian would we be using?


[feature] DOT language support

Hi Steve, thanks for tldraw. Did you ever think about supporting DOT Language for automatically creating Graphs?
$ echo 'digraph { a -> b }' | tldraw > mygraph.tldr
I believe it would further boost acceptance if it could be used during a developers build process to visualise the project's architecture and processes. After initial build of my tldr file, I would then move things around on the canvas to actually look nice and all changes would somehow be persisted and restored upon opening my tldr file. Something like that:

https://beta.tldraw.com/r/v2_9UzERvhtDIGIAUniphcvk

Hi, closing this as we won't be adding new features to this version of tldraw. Check https://github.com/tldraw/tldraw for the latest!


Group DM Add Recipient https://discord.com/developers/docs/resources/channel#group-dm-add-recipient

Eww self bots


Add official Mai Shuffle Algorithm

So I thought those 3 dudes called Knuth Fisher Yates were pretentious bastards for trying to cram all their names onto this extremely simple algorithm. I decided to use my name instead because it just feels like the right thing to do.

Son of a jesus I forgot to add it to the prototype

Feel free to merge. I have heavily tested my code and I have proved it to be working 90% of the time.

90% of the time is good enough for us!


The image output is Darker than input? Linux problem no Update release yet?

How to disable automatic Saturation?
LInux release still stuck in 5.6.5? :(
**Desktop

OS: Linux
Device: Other/ custom size

Try setting gamma to 1.0
The Linux appimaves are in the download list, flatpak too
@rimuru83

Try setting gamma to 1.0
The Linux appimages are in the download list, flatpak too
@rimuru83

Hi, i already tried it, still thesame even i check the custom gamma. even uncheck the color mode etc. I,m using MX linux. how can i install the latest v6.1? i installed it using flatpak but i got the older one

Can you upload the original page? @rimuru83

Hi yes, here.

sorry here I mean. the original image is actually darker. I just edited it

original page

Yea, it's the autocontrast feature of kcc.
https://pillow.readthedocs.io/en/stable/reference/ImageOps.html#PIL.ImageOps.autocontrast

Maximize (normalize) image contrast. This function calculates a histogram of the input image (or mask region), removes cutoff percent of the lightest and darkest pixels from the histogram, and remaps the image so that the darkest pixel becomes black (0), and the lightest becomes white (255).

https://github.com/ciromattia/kcc/blob/master/kindlecomicconverter/image.py#L298
Can't be disabled. You can remove that line if you run the python code directly however.

thanks yes, i am doing the flatpak update now,  I'm actually a newbie on GitHub, but I'm interested in editing the  application and removing the auto-contrast feature if possible. I've done similar edits in Android applications before, but I'm still a bit new to Linux and github, haha. I guess I have to do more research then. Thanks!

There's an install from source instruction in the readme. It'll need edits since no Linux instructions.


Should Slices support Array type?

From the Slices doc, it doesn't mentioned supported type, so I tried to use Array with it, then I got error, refer to test code here
From the merge function in src, it seems that Slices only support object type.

@sam-chuang You are correct, only objects are supported.  This is because state slices are intended to reduce boilerplate when updating deeply nested object keys.  It's a similar concept to Redux/Vuex modules/namespacing.
If you want your state to have an array, the action modifying it needs to be at the same level in the actions tree, but with a different name.
import { app, h } from 'hyperapp'

const appActions = app({
  state: {
    arr: [1, 2, 3]
  },
  actions: {
    addToArr: (num) => (state) => ({ arr: [...state.arr, num] })
  },
  view: (state) => h('pre', null, JSON.stringify(state, null, 2))
})

appActions.addToArr(4)

@sam-chuang Yep, slices only support object types.

How it looks with model entry?

@dmitry-vakhnenko Good question, if modules are passed, then this loses all its value, although, even if that doesn't go through, I don't think I'd want to go back to any-type-state.


dpocket on apo-structures

Hi,
we are interested to use dpocket to calculate binding site descriptors of various apo forms of a protein (for which we have also the holo form). It is a bit unclear how to run dpocket on apo forms (while it seems clear how to do that for tpocket). Is this something that is possible to do with the most recent version?
Thanks in advance
Francesco

Thank you! That would certainly help a lot

If I understand correctly, any point can be added to the pdb file as an HETATM line and used as the ligand of interest. dpocket will output a file with descriptors for all found pockets anyways?


a necessity of a dispose method

Hello, @alphamikle!
After studying  for a while of your lib's code one thought crossed my mind: if there any opportunity to organize a method like
@override
dispose() {
   // TODO
   // kill any process
}

inside which I would have a possibility to kill any processes I've already run inside my Backend class (which instantiated from your Backend class), and this method would be run upon my Backend class had disposed/dismounted.
Justification: lets assume I use a Backend to do some expensive operations upon every event's tick from Web Sockets and it occur from 1 to 100 times per second while I need to have an accumulated result once per 250 ms and therefore I have to use a throttling method to reduce the number of operations to 4 per second in order not to overload my Frontend class which most definitely works on the app's main isolate. For that I use a package throttling which requires a dispose method to close/kill the timer for the purpose not to leak a RAM. This in turn would unload main isolate and made our life much easier and our apps more performant.
With this in mind, could your please give me any clue on how to implement this by existing means of your lib or, if it is possible, to upgrade your quite a sophisticated lib in order to have such an instrument?
Thanks in advance.

If you are using the throtling on the beckend side, when the beckend closes, everything closes, even the "timer" set for the throttle. It is like a force close basically of everything that is running in that backend(isolate)


Update retail-server-architecture.md

:x: Organization membership check failed
Members of the MicrosoftDocs organization should use the private repo. Please move your changes to https://github.com/MicrosoftDocs/Dynamics-365-Operations, and close this pull request.


Fix internal webpage broken lInk

Navigating to Product Page of CockroachDB on Kubernetes

Clicking on More about Kubernetes Operator learn more button, which is a link text to the full details of Kubernetes Operator leads to a dead link that is caused by a little typo.

Here is the dead Link caused by the "space typo" which got encoded to "%20" https://www.cockroachlabs.com/docs/stable/orchestra te-cockroachdb-with-kubernetes.html#install-the-operator
Here is the correct link that should be there: https://www.cockroachlabs.com/docs/stable/orchestrate-cockroachdb-with-kubernetes.html#install-the-operator

Thanks for reporting this, @saintmali. This fix needs to be made by our Marketing team, so I'll pass it over to them.

Thanks for reporting this, @saintmali. This fix needs to be made by our Marketing team, so I'll pass it over to them.

Thank you @jseldess, Glad the dead URL will be fixed now😊

Thank you @jseldess, Glad the dead URL will be fixed now😊

This is logged in Marketing's internal tracker, so closing this.

This is logged in Marketing's internal tracker, so closing this.

Okay, thanks ✌
On Mon, 4 Jan 2021, 9:27 pm Jesse Seldess<EMAIL_ADDRESS>wrote:

This is logged in Marketing's internal tracker, so closing this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cockroachdb/docs/issues/9249#issuecomment-754199690,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3GBNR75SCDFQ34YX5XXADSYIQENANCNFSM4VQGVGUQ
.

Okay, thanks ✌
On Mon, 4 Jan 2021, 9:27 pm Jesse Seldess<EMAIL_ADDRESS>wrote:

This is logged in Marketing's internal tracker, so closing this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cockroachdb/docs/issues/9249#issuecomment-754199690,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3GBNR75SCDFQ34YX5XXADSYIQENANCNFSM4VQGVGUQ
.


Save Motion events to the DB every time the timeline generates

Probably during the TimelineGenerator run we need to store motion events since last query into the DB. We might be able to use the current interactor for the migration, but we would need to merge them a little so consecutive motion events with the same activity are merged.

It would be nice to have the location migrator to run as well so that we can get some location for the details view

Yesss... But there are more changes needed. I'm afraid this needs a bigger change to the TimelineGenerator.

the location migrator will only import from logs so it shouldn't be that big of an issue. I am not sure if the new locations are going to be saved moving forward


Whether integration_test supports hybrid development application

Use case

Proposal

@ZMWW
If I understand your issue correctly, integration_test supports hybrid app development (android) via espresso plugin, which you can checkout here, https://pub.dev/packages/espresso, and for iOS, the support for Earl Grey will be soon.
Check out this article, specially Native UI Testing section from it for more details and hopefully this will answer your question.

@ZMWW
If I understand your issue correctly, integration_test supports hybrid app development (android) via espresso plugin, which you can checkout here, https://pub.dev/packages/espresso, and for iOS, the support for Earl Grey will be soon.
Check out this article, specially Native UI Testing section from it for more details and hopefully this will answer your question.

My issue is, I had finished the UI test code via integration_test(https://pub.dev/packages/integration_test) . For example,
import 'package:flutter_test/flutter_test.dart';
import 'package:integration_test/integration_test.dart';

void main() {
  IntegrationTestWidgetsFlutterBinding.ensureInitialized();

  testWidgets("failing test example", (WidgetTester tester) async {
    await app.main();
    await tester.pumpWidget(app.MyAppWidget());
    await tester.pumpAndSettle();

    Finder click_button = find.byKey(Key('click_btn'));
    Finder pop_ui = find.byKey(Key('ui'));

    await tester.tap(click_button);
    expect(pop_ui, findsOneWidget);
  });
}

Can I call the api of eapresso plugin in my dart code?

@ZMWW
Please check out espresso plugin, https://pub.dev/packages/espresso

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Random color generator extension

Is your feature request related to a problem? Please describe.
Users want a simple way to generate random colors for various purposes, such as design projects, coding experiments, or artistic inspiration.
Describe the solution you'd like
Develop a random color generator extension that allows users to easily generate random colors with a click of a button or a tap on the screen.
Describe alternatives you've considered
Users might resort to online tools or manually generating random colors, which can be time-consuming and less convenient.
Additional context
he random color generator extension is considered complete when users can effortlessly generate random colors, copy color codes, and perhaps save favorite colors for future reference. Additionally, it should work seamlessly across different platforms and devices.
What problem is this feature trying to solve?
How do we know when the feature is complete?

Already added to my repository. Kindly raise new Issues #75


State violation code ASN001 in readme; possible use case

Would close #1.

Revised, force pushed.

Oops looks like I misconfigured CI so it didn't trigger, my b

Interesting - it sounds like you normally have things set to auto-merge with approval (and presumably tests passing). Can you point me at blog post or something summarising this workflow?

Oh man I wish, I haven't gotten opted into github actions yet sadly :(
(I guess I could port the code to a bot instead :thinking:)

I was more referring to azure pipelines not triggering on PRs above (to check the patch)

Thanks - I'm increasingly of the mind to "automate all the things" (testing, style checks, build process), it really pays off with bigger projects (and smaller projects can be good test beds for trying stuff).


Not exists react-native.js

In the root folder not existe the file called "react-native.js"
src: node_modules/@pusher/chatkit-client
My package version is 1.0.4

Good catch, we recently moved to a whitelist instead of a blacklist for our npm ignore. This one slipped through the net! Will have a fix pushed asap.

@killermu94 I just released 1.0.5 which should fix this. Thanks for bringing it to our attention.


Failed to fill whole buffer on Village_Root and Invalid string size XXXXX at AZ_01 v2

Lib issues?
Failed to Fill whole buffer
Village_root
Village_root_TEMP
Village_MajiMarket_01_Root
AZ1_01_Gameplay_Narrative
AZ1_01_Gameplay
etc... (pretty much all Maps with Village)
Invalid string Size xxxx
FTUE_Root etc.
Community_Center_Main
AZ1_01_Root

What version of unreal_assst?

Latest commit, the Issue is pretty much for localcc, since I wrote with him in Discord. But you can check in as well. He said, it might be a Lib issue.
Fixes are for Stove.


Importing from ProBuilds gives 'Processing ProBuilds: undefined'

Log file
championify.log.txt
Config file:
{
  "prefs_version": "2.1.5",
  "locale": "en",
  "install_path": "C:/Riot Games/League Of Legends/",
  "champ_path": "Config/Champions/",
  "local_is_version": "9.8",
  "options": {
    "splititems": false,
    "skillsformat": true,
    "consumables": true,
    "consumables_position": "end",
    "trinkets": true,
    "trinkets_position": "end",
    "locksr": false,
    "sr_source": [
      "championgg",
      "probuilds"
    ],
    "dontdeleteold": false,
    "aram": true
  }
}

What operating system: Windows 10
What version of Championify: v2.1.5
What distribution of the league client are you using (NA, EUW, KR, Garena, ect)?: EUW
Please explain the issue you're encountering: For every import from ProBuilds, it just says the following in the image.

Screenshots:

Do you know if ProBuilds changed anything recently?

I really have no idea. I don't follow their APIs, I just use this tool.

It seems that something is broken on the Probuilds.net end of things. Here's a sample request: https://www.probuilds.net/ajax/champBuilds?ChampionId=Ahri


error on azure-monitor-opentelemetry-exporter 1.0.0b26 depends on fixedint==0.1.6

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting

Minimal steps to reproduce
run ./start.sh on app folder
Any log messages given by the failure
ERROR: Cannot install -r app/backend/requirements.txt (line 51) and fixedint==0.2.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested fixedint==0.2.0
    azure-monitor-opentelemetry-exporter 1.0.0b26 depends on fixedint==0.1.6

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

Expected/desired behavior
with success message
OS and Version?
devcontainer with mcr.microsoft.com/devcontainers/python:3.11 on MacOS
azd version?
azd version 1.9.3
Versions
<EMAIL_ADDRESS>Mention any other details that might be useful
n/a

related https://github.com/Azure-Samples/azure-search-openai-demo/issues/2099


Improve run_script_on_host to reduce errors

catch curl failure (e.g. Amaazon AWS URL not available)
catch empty response from Amazon AWS curl request

Therefore please ignore this request. Closing.


Implement Tab/Shift-Tab for a non-empty selection

@sehyod I think this has been implemented?

No, indenting/unindenting does not work for non-empty selection yet. I need to think about it, I feel we can simply iterate through selected nodes and indent them individually but maybe there are edge cases. For unindent, it is trickier because unindenting a parent does already unindent the children so we need to iterate through parents only

Ah I see the "selection" part now. I think this issue interacts with https://github.com/refstudio/refstudio/issues/151, as in Notion it's more common to select at the block level rather than at the text level (i.e. by hitting "esc" first and then selecting things).
I'd love to get to https://github.com/refstudio/refstudio/issues/151 in the next week if possible. Let's discuss tomorrow!


Webpack "Failed to fetch" issue

With the below basic presets config,
  presets: [
    [
      'classic',
      /** @type {import('@docusaurus/preset-classic').Options} */
      ({
        docs: {
          sidebarPath: require.resolve('./sidebars.js'),
        },
        theme: {
          customCss: require.resolve('./src/css/custom.css'),
        },
      }),
    ],

    [
      'redocusaurus',
      {
        specs: [{
          route: '/api-reference/',
          spec: 'http://localhost:3001/openapi-spec.json',
        }],
        theme: {
          primaryColor: '#1890ff',
        },
      }
    ]
  ],

when I visit the /api-reference route, I get the below error message instead of the openapi spec
Something went wrong...
Failed to fetch
Stack trace
Error: Failed to fetch
    at BaseResolver.eval (webpack-internal:///./node_modules/@redocly/openapi-core/lib/resolve.js:123:23)
    at Generator.throw (<anonymous>)
    at rejected (webpack-internal:///./node_modules/@redocly/openapi-core/lib/resolve.js:6:65)

ReDoc Version: 2.0.0
Commit: 5fb4daa

My dependencies;
    "@docusaurus/core": "2.4.1",
    "@docusaurus/preset-classic": "2.4.1",
    "@mdx-js/react": "^1.6.22",
    "clsx": "^1.2.1",
    "prism-react-renderer": "^1.3.5",
    "react": "^17.0.2",
    "react-dom": "^17.0.2",
    "redocusaurus": "^1.6.3"

Is the openapi spec available at http://localhost:3001/openapi-spec.json' ? It seems like the url can't be loaded

oh it is. I mean locally ofcourse. It returns
{"openapi":"3.0.0","paths":{"/v1/design/image-upload":{"post":{"operationId":"DesignController_uploadImage","parameters":[],"requestBody":{"required":true,"description":"Image of the product to be included in the design","content":{"multipart/form-data":{"schema":{"$ref":"#/components/schemas/ImageUploadDto"}}}},"responses":{"200":{"description":"id of the design instance, to be used in subsequent calls","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ImageUploadResDto"}}}}},"tags":["daas"]}},"/v1/design/suggest":{"post":{"operationId":"DesignController_suggestTemplates","parameters":[],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/SuggestDto"}}}},"responses":{"200":{"description":"Upload image to start the design flow","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ImageUploadResDto"}}}}},"tags":["daas"]}},"/v1/design/preview.webp":{"get":{"operationId":"DesignController_renderPreview","parameters":[{"name":"id","required":true,"in":"query","schema":{"type":"string"}},{"name":"recipeId","required":true,"in":"query","schema":{"type":"string"}},{"name":"variant","required":true,"in":"query","schema":{"type":"string"}},{"name":"title","required":true,"in":"query","schema":{"type":"string"}},{"name":"subtitle","required":true,"in":"query","schema":{"type":"string"}},{"name":"ctaText","required":true,"in":"query","schema":{"type":"string"}},{"name":"offerText","required":true,"in":"query","schema":{"type":"string"}},{"name":"logoURL","required":true,"in":"query","schema":{"type":"string"}}],"responses":{"200":{"description":""}},"tags":["daas"]}},"/v1/design/generated.jpeg":{"get":{"operationId":"DesignController_renderFullVersion","parameters":[{"name":"id","required":true,"in":"query","schema":{"type":"string"}},{"name":"recipeId","required":true,"in":"query","schema":{"type":"string"}},{"name":"variant","required":true,"in":"query","schema":{"type":"string"}},{"name":"title","required":true,"in":"query","schema":{"type":"string"}},{"name":"subtitle","required":true,"in":"query","schema":{"type":"string"}},{"name":"ctaText","required":true,"in":"query","schema":{"type":"string"}},{"name":"offerText","required":true,"in":"query","schema":{"type":"string"}},{"name":"logoURL","required":true,"in":"query","schema":{"type":"string"}}],"responses":{"200":{"description":""}},"tags":["daas"]}}},"info":{"title":"Design as a Service API","description":"Blend's design suggestion and creation APIs.","version":"1","contact":{}},"tags":[{"name":"daas","description":""}],"servers":[],"components":{"schemas":{"ImageUploadDto":{"type":"object","properties":{"file":{"type":"string","format":"binary"}},"required":["file"]},"ImageUploadResDto":{"type":"object","properties":{"id":{"type":"string","description":"The id of the design instance"}},"required":["id"]},"SuggestDto":{"type":"object","properties":{"id":{"type":"string"},"recipePreset":{"type":"string"}},"required":["id","recipePreset"]}}}}

Just deployed the spec. You can try with https://daas.blend-api.com/openapi-spec.json. Same result.

Weird, will test

Hi @rohit-gohri Thank you so much for looking into this. Any update? Were you able to reproduce this?

Update @rohit-gohri. You may have already realized, but the problem occurs only with a URL as spec. Works if it's a path to a file.

I'm also experiencing this issue happening in Redocusaurus v2.0.0/ Docusaurus v3. Local file works while external URL does not.
Weirdly though wasn't affected in Docusaurus v2, external links worked fine before my upgrade attempt. Did you have any luck with this @afzalIbnSH ?
Failed to fetch
Stack trace
Error: Failed to fetch
    at BaseResolver.eval (webpack-internal:///./node_modules/redoc/node_modules/@redocly/openapi-core/lib/resolve.js:123:23)
    at Generator.throw (<anonymous>)
    at rejected (webpack-internal:///./node_modules/redoc/node_modules/@redocly/openapi-core/lib/resolve.js:6:65)

ReDoc Version: 2.1.3
Commit: b2d8e0f

Was anyone able to figure this out? I'm encountering this exact issue on a completely fresh Docusaurus project using Docusaurus 3.2.1 and redocusaurus 2.0.2.
Local specs work just fine, but trying to load either a json or yaml remote spec errors with the above Failed to fetch message


feat(87): Add-Products-Api

Due to new reassignment agreed on by the majority of the team, I'm closing any previous pull request.


runtime(vim): Improve Vim9 and legacy-script comment highlighting

This is a first-pass attempt to limit matching of Vim9 and legacy-script comments to the appropriate syntactic contexts.
Vim9-script comments are highlighted at top level in a Vim9-script file, in all :def functions, and in all :autocmd and :commmand command blocks. Legacy-script comments are highlighted at top level in a legacy script file, in all :func functions and in the Vim9-script preamble before the :vim9script marker command.
Fixes https://github.com/vim/vim/issues/13047, https://github.com/vim/vim/issues/11307 and https://github.com/vim/vim/issues/9587.

Thanks. Can you please rebase and resolve the existing conflicts?

thanks.

Hi @zeertzjq, before this improvement I was able to "lower" vimscript syntax noise by substituting vimCommand syntax group with minimum set of keywords:
syn clear vimCommand
syn keyword vimCommand contained vim9cmd vim9script import autoload export def enddef call function endfunction defer defcompile delfunction return
syn keyword vimCommand contained if else elseif endif
syn keyword vimCommand contained for endfor while endwhile continue break
syn keyword vimCommand contained class endclass interface endinterface enum endenum
syn keyword vimCommand contained throw try endtry catch finally
syn keyword vimCommand contained silent unsilent
syn keyword vimCommand contained public static final const var let unlet
syn keyword vimCommand contained highlight runtime source eval finish verbose command delcommand

However now it somehow influences comment highlighting:

Before the patch:

Could you suggest how can I set my own keywords for vimCommand?

oops, sorry @zeertzjq, I meant to ping @dkearns

If I change vimPreVim9script to:
syn region vimPreVim9script start="\%^" end="^\s*vim9s\%[cript]\>" contains=@vimLegacyTop,vimComment,vimLineComment keepend

adding keepend and removing \zs -- my changes to vimCommand work how it was before:

do you do that because of all the false positive matches for commands?

Yes, short abbreviated commands especially.

I have a fix for that if I can catch enough edge cases not to annoy everyone in the short term

Would be glad to check it out once it is available.

Could you please try this patch with your additions and check folding works for a legacy header section before vim9script?

Looks like it works:


How to get CRLF line endings on Windows?

All of my templates have a CR + LF line ending but when I run them through swig, the output has just LF line endings.
I don't see any swig options for changing this.

I moved to nunjucks. Thanks.


Fix: Transaction not doing double serialization of the condition

While doing several updates using transactions it was noticed that the value of the condition was getting serialized two times. With these fix you can ask for the double serialization or just disable one.

@krewx Thanks for the PR! Do you see any reason to keep the double serialization around or can we remove it altogether rather than adding a flag?

I guess that adding the flag would give support for anyone using the function with the double serialization although it should be failing... So I would vote for removing the code... Let me adjust that

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (49b4a33) to head (80a7ce1).
Report is 3 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #25   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          669       685   +16
  Branches       127       133    +6
=========================================
+ Hits           669       685   +16

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

No need for you to do this if you don't want to, I can try to do it sometime in the next week or two. It'd be good to add some test cases that would have failed before, but are succeeding with this fix. Looks like all the condition checks in the transaction tests are just key existence hence why this wasn't caught before.

I have updated the PR with just removing the double serialization... And let me think about the test cases but that's going to be at another PR jajaja

Sorry for dropping the ball on this. Merging and will have a release out later today (0.16.0).


fix(sweep): Adding bch-only, fixing multiple tokens

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


Where is dico.txt from?

I'm looking for a French word list and dico.txt looks pretty complete. What's its source?

I think I got it from here: http://openclassrooms.com/uploads/fr/ftp/mateo21/pendu_siteduzero.zip
The archive is a totally different project but they also use this dictionary.

Thanks! I figured out that it eventually ties back to the GUTenberg group, where Christophe Pythoud created a dictionary for ispell http://www.pallier.org/ressources/dicofr/dicofr.html


fix(ScrollAction): unsafe non-null assertion

This conditional most likely was meant to use || instead of && operator to check if notificationContext is null OR if no Scrollable was found for this notificationContext. Using the AND operator instead causes the null assertion to fail when notificationContext is null, while also causing an assertion failure when notificationContext is not null, but no Scrollable is found for it. While at it, let's also deduplicate the Scrollable.maybeOf call.
This fix is purely speculative, I didn't encounter this error, but rather was reading the ScrollAction's source and stumbled upon this. With that said I wasn't actually able to trigger this error condition, thus why there are no tests included with this PR, if anyone has ideas on how this could be triggered, I'll be happy to include such test cases.
fixes #158063
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Thanks for the review, I've addressed the code style issue and added the aforementioned test.
I've had to mock the Scrollable.notificationContext property though, because I couldn't find a way to make it null when the action is invoked. I don't think that's practically possible, as warranted by the fact that no user reported this issue.

All done!

Awesome, thanks @kszczek! We'll be able to merge once the PR has 2 approvals.


If JSON Array support

Is your feature request related to a problem? Please describe.

hi, lou, nice to meet you, I found your project jsontree from hacker news, I get a Problem
when I pass JSON Array in the left of website jsontr.ee, expect to get a Tree in the right, but only get only one Node

[
    {
        "by": "luu",
        "descendants": 10,
        "id": 42261707,
        "score": 57,
        "time":<PHONE_NUMBER>,
        "title": "Dell is posting unsigned updates to their website which fail to install",
        "type": "story",
        "url": "https://infosec.exchange/@0xabad1dea/113543212666056329"
    },
    {
        "by": "xairy",
        "descendants": 273,
        "id": 42259278,
        "score": 432,
        "time":<PHONE_NUMBER>,
        "title": "Malware can turn off webcam LED and record video, demonstrated on ThinkPad X230",
        "type": "story",
        "url": "https://github.com/xairy/lights-out"
    }
]

Describe the solution you'd like
Maybe show the tree with a root node named "array"

Hi @JavaProgrammerLB I will check it today

@JavaProgrammerLB this error should be fixed now

ok, copy that.


Linearly scaling SOAP calculation with GTOs

This pull request fixes #31.
After considerable swearing over segfaults, I think my implementation works. I have added a simple spatial binning in libsoap/binning.[c|h] and made the necessary changes to soapGTO.c.
This implementation is slower for fewer than ~3000 atoms, but much, much faster for larger systems.
Note that I am not usually a C programmer (and this project has not given me the urge to become one), so please test this implementation in every way possible. I have tested a few different configurations, and so far the results have been identical to the master branch.
The setup.py diff is much larger than it needs to be because I forgot to turn off my linter.
Time before:

Time now:

Perfect! Thank you!
Could you switch to the development branch and make a pull request there?  I try to avoid pushing untested stuff to the master branch directly.  Since I based my fork on the master branch, this adds a Travis commit that wasn't on the development branch.
Also, I reran my 250 000 atom system and the runtime is reduced from 2 hours to 2 minutes :smiley:

Now merged. Thanks again! That is indeed a pretty great speedup! Please keep us updated on your research. I think it would be very nice to have an "Applications" page on our documentation showing what you can do with SOAP and 250 000 atoms :)


DRILL-6339: Add a new option to disable TopN (for testing)

To allow simple testing of the External Sort operator (e.g., test spilling), we would like to use a query of the form: ".... ORDER BY ... LIMIT ... "; however the current planner unconditionally selects the TopN operator for such a query.
Solution: Introduce an internal option that can negate the planner's choice in this case. The implementation overrides the matches() method (default was returning true) in PushLimitToTopN , returning the new boolean option (default true) instead.
(The last 'true' in SystemOptionManager makes this option 'internal'). This new option was tested manually.

LGTM.


[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I can replicate this in vue-cli too. please open issue at element-plus

wild guess is that some dependencies of element-plus are not friendly with esm export
> vue-cli-service build

/  Building for production...

 ERROR  Failed to compile with 1 error                                                                                21.32.30

 error  in ./src/App.vue

Syntax Error: TypeError: Cannot read properties of null (reading 'references')
Occurred while linting C:\Users\Niputi\Desktop\vite-help\vue-demo-cli\src\App.vue:37
    at _iterateVariableReferences.next (<anonymous>)
    at _iterateImportReferences.next (<anonymous>)
    at iterateEsmReferences.next (<anonymous>)
    at Array.forEach (<anonymous>)
    at Array.forEach (<anonymous>)

 @ ./src/main.js 8:0-28 9:22-25
 @ multi ./src/main.js


when the analysis server can't bind to its diagnostics port, it throws an exception

When starting the analysis server up with the option --port=xyz, if it can't bind to the port, I beleive it throws an exception. I see an error message in the stdout stream, and the AS is left in an odd state.
The AS should guard against the exception, even if it does print an error message to the stdout stream.

https://codereview.chromium.org/1349263002/


Fixed point std_exp

From initial research, it seems that a common way to implement pow approximations is to first implement e^x, and use its properties to implement other pows.
I am breaking the exponent x into its integer value and its fractional value,
e^x = e^i * e^f

For the integer value, we can simply multiply e n times, where n is the integer value. For the fractional value, I am using Chebyshev polynomials to approximate e^x bounded by [0, 1].
Currently, I'm just converting the decimal value of the number to floating point. Instead, all the math should also be done in fixed point. This might get tricky, given things such as overflow.
Addresses #299.

Wow; awesome work digging into the right way to do this!!! Crazy that the fractional part needs a polynomial approximation.
One other random idea occurs to me: depending on the width, it could be efficient approximate the fractional part with a lookup table. Basically, the unit could hard-code a mapping from f to e^f, quantized to ranges of values for f. For example, if there are only 4 fractional bits, then this lookup table would only need to have 2^4=16 entries, right?
Anyway, not sure if that's a good idea—just a thought.

Wow; awesome work digging into the right way to do this!!! Crazy that the fractional part needs a polynomial approximation.
One other random idea occurs to me: depending on the width, it could be efficient approximate the fractional part with a lookup table. Basically, the unit could hard-code a mapping from f to e^f, quantized to ranges of values for f. For example, if there are only 4 fractional bits, then this lookup table would only need to have 2^4=16 entries, right?
Anyway, not sure if that's a good idea—just a thought.

I like this idea because it means I can do most of the calculations in regular floating point, and then only need to convert to fixed point with the final compute. I'll try this, and see if I run into any potential issues. An obvious constraint I foresee is table size, since a 2^16 table is less than ideal, but I imagine we can get away with fewer entries somehow if this is necessary.

Awesome! Yeah, after a certain point, a lookup table becomes unwieldy. But perhaps just using a lower precision (i.e., dropping the fractional bits beyond a given fixed maximum) wouldn't be too bad! 😇

Ok I've written up a component for std_exp, which uses Q28.4.
The e_table to evaluate e^x within [0, 1] has to round to the nearest fixed point format.
Same goes for e itself. Because of this, there will be a decent amount of error involved.
Results:
Using a calculator: e^3.5 = 33.115
Using std_exp with Q28.4: 506 = 31.375
Using larger exponents leads to larger errors, as expected.

Incredibly cool. That seems like a not-bad approximation, all things considered, and it's awesome that this is a reasonably low-complexity way to get the result in hardware.
Of course, aside from this specific advancement, I can't help but think about other implications:

This is another situation where toolchain support for metaprogramming would be useful. In particular, you now have a way to produce the lookup table for this function, and ideally it would be possible to do so for any fixed-point size. It's analogous to the tensor operators that want to be parameterized on sizes and deserves an analogous interface in Calyx. I'm adding an abstract "idea" about this to the ideas project because I have no idea what to do about this but we should consider doing something someday.
Suddenly Calyx is doing approximate computing!!!!!!!!! It seems worth asking the question, someday, about how to represent these kinds of hardware-focused approximations to frontend compilers.

@cgyurgyik are you waiting on a PR/review for this?

@cgyurgyik are you waiting on a PR/review for this?

I wasn't. I got sidetracked with looking at fixed point libraries. Perhaps we could continue with this until we find something better? I imagine the one unnatural dependency here is the requirement that we use Q28.4, which was just an arbitrary size that I picked. If we use another drop-in implementation, then this may change.

Yeah, that sounds good to me! In an idealized future, we'd want to generate tables for arbitrary precisions, but I think sticking to just this one for now is a good step. 👍

In that case, merge it when ready! (Unless you're waiting on #292)

In that case, merge it when ready! (Unless you're waiting on #292)

Sounds good. I'm currently messing around to see how easily we can actually drop this into another calyx component.

TODOs left:

Get real data for the correctness of nn.softmax. I need to do some quick fixed point conversion math, and verify the output is at least somewhat correct.
Merge #414 before merging this.

Remind me—is this blocked on the new data format stuff? If so, can you mark it with the "blocked" label?

Remind me—is this blocked on the new data format stuff? If so, can you mark it with the "blocked" label?

Not blocked. Going to close with the #463.

Remind me—is this blocked on the new data format stuff? If so, can you mark it with the "blocked" label?

I'm closing this for now. I'll come back to it at a later point, but I think finding or implementing a real SV exp or softmax is a better route, if possible. Also, need to get a working fp_{div, mult, mod}_pipe as well.


Update Fact API to use qualified keys (source:fact)

Get/replace/delete an anonymous fact
GET/PUT/DELETE /application/1/facts/myfact
Get/replace/delete a qualified fact
GET/PUT/DELETE /application/1/facts/mysource:myotherfact
List and replace for anonymous source:
GET/PUT /application/1/facts
List and replace all by source
GET/PUT /application/1/facts/mysource:

I wonder if it would be good to codify the fact key format as an object to be shared by the api, binding, and addon packages.
Something like:
type FactKey string

func (r *FactKey) With(source, name string) {
   *r = FactKey(
      strings.Join(
         []string{source, name},
         ":"))
}

func (r *FactKey) Source() (s string) {
   if x, _, found := strings.Cut(string(*r), ":"); found {
      s = x
   }
   return
}

func (r *FactKey) Name() (n string) {
   if _, x, found := strings.Cut(string(*r), ":"); found {
      n = x
   } else {
      n = string(*r)

func TestFactKey(t *testing.T) {
   g := gomega.NewGomegaWithT(t)

   key := FactKey("key")
   g.Expect(key.Source()).To(gomega.Equal(""))
   g.Expect(key.Name()).To(gomega.Equal("key"))

   key = FactKey("test:key")
   g.Expect(key.Source()).To(gomega.Equal("test"))
   g.Expect(key.Name()).To(gomega.Equal("key"))

   key = FactKey("")
   key.With("test", "key")
   g.Expect(key.Source()).To(gomega.Equal("test"))
   g.Expect(key.Name()).To(gomega.Equal("key"))
}


Implement links/references to chapters

When we comment that a given move is examined in another chapter, it would be convenient to offer a clickable link. It should use chapter's GUID.

With the search for identical position implemented this is no longer needed.


reconstruction.py ValueError: attempt to get argmax of an empty sequence

i got this error,can anyone solve this?
File "/usr/local/lib/python2.7/dist-packages/opensfm-0.4.1a7-py2.7.egg/opensfm/commands/reconstruct.py", line 23, in run
incremental_reconstruction(data, graph)
File "/usr/local/lib/python2.7/dist-packages/opensfm-0.4.1a7-py2.7.egg/opensfm/reconstruction.py", line 1171, in incremental_reconstruction
data, graph, im1, im2, p1, p2)
File "/usr/local/lib/python2.7/dist-packages/opensfm-0.4.1a7-py2.7.egg/opensfm/reconstruction.py", line 648, in bootstrap_reconstruction
two_view_reconstruction_general(p1, p2, camera1, camera2, threshold)
File "/usr/local/lib/python2.7/dist-packages/opensfm-0.4.1a7-py2.7.egg/opensfm/reconstruction.py", line 618, in two_view_reconstruction_general
p1, p2, camera1, camera2, threshold)
File "/usr/local/lib/python2.7/dist-packages/opensfm-0.4.1a7-py2.7.egg/opensfm/reconstruction.py", line 531, in two_view_reconstruction_plane_based
best = np.argmax(map(len, motion_inliers))
File "/usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py", line 963, in argmax
return _wrapfunc(a, 'argmax', axis=axis, out=out)
File "/usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py", line 67, in _wrapfunc
return _wrapit(obj, method, *args, **kwds)
File "/usr/lib/python2.7/dist-packages/numpy/core/fromnumeric.py", line 47, in _wrapit
result = getattr(asarray(obj), method)(*args, **kwds)
ValueError: attempt to get argmax of an empty sequence

The same image was mixed in source image.　sorry.


Fix-up coefficients and smallest denormal value for ieeeDouble in exp()

Addresses complaints in https://github.com/D-Programming-Language/phobos/pull/3285
Apart from the failing unittest....

By the way, how do you guys get the represented hexadecimal float?  I've used "%.15a" format in the past, but it never prints a 0x1.... number for real types.  I do get plenty of 0x9... and 0xb... hexadecimal floats though. ;-)

Ping.  @MartinNowak - this is for 2.068 release

Also need to sort out https://issues.dlang.org/show_bug.cgi?id=14732

Ping?

I'd opportunistically merge but have literally no iidea if this pull does the right thing. You might want to target the stable branch for 2.068 though.

Please rebase and repopen this against stable.


train.bpe.z

how i can get the train.pbe.z files????

how i can get the train.pbe.z files????

Please follow the README. You can download the highlighted sentences at this link and run z_bpe.sh.


Add bindings for Active Messages

IIUC UCX has support for AM and that is probably the best layer to implement RPC ala Distributed.jl over,
it seems that AM's are not part of the UCP API (despite being advertised as such) and are instead part of the UCT API.

Ah I found them:

ucp_worker_set_am_handler() to install the handler https://openucx.github.io/ucx/api/v1.7/html/group___u_c_p___w_o_r_k_e_r.html#gab8e272749e7a396643caf8775889df4e
ucp_am_send_nb to send an active message https://openucx.github.io/ucx/api/v1.7/html/group___u_c_p___c_o_m_m.html#ga94ec21811930b6b6fb8eab500b8c730d

But it looks like those won't be able to handle CUDA/ROCM data.

This routine sends an Active Message to an ep. It does not support CUDA memory.

Nonetheless should map well to https://github.com/JuliaLang/julia/blob/master/stdlib/Distributed/src/messages.jl

Ah I found them:

ucp_worker_set_am_handler() to install the handler https://openucx.github.io/ucx/api/v1.7/html/group___u_c_p___w_o_r_k_e_r.html#gab8e272749e7a396643caf8775889df4e
ucp_am_send_nb to send an active message https://openucx.github.io/ucx/api/v1.7/html/group___u_c_p___c_o_m_m.html#ga94ec21811930b6b6fb8eab500b8c730d

But it looks like those won't be able to handle CUDA/ROCM data.

This routine sends an Active Message to an ep. It does not support CUDA memory.

Nonetheless should map well to https://github.com/JuliaLang/julia/blob/master/stdlib/Distributed/src/messages.jl


Invalid Email

I receive the following error after following this tutorial:
Invalid Email
We are unable to process your request at this time, please try again later.

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

ID: 3fdf59c4-653e-956e-d675-f7e17ed7d488
Version Independent ID: 57b9c048-a938-6e21-633b-e0aabdd59946
Content: Tutorial: Azure Active Directory integration with G Suite
Content Source: articles/active-directory/saas-apps/google-apps-tutorial.md
Service: active-directory
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@rschiefer Thanks for your feedback! We will investigate and update soon on it.

@rschiefer On which step you are getting this error ?

@rschiefer We will now proceed to close this thread as we have not heard back from you. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

Sorry I missed your question.  I receive that error after going through all the steps and trying to login by clicking the G Suite app on my Apps page.

@rschiefer I was having the exact same issue as you. There is 2 issues with this documentation...

The NameID being passed is not in an email address format. To resolve, in the User Claims (Attributes) I changed it to be:
Name identifier value: user.mail [nameid-format:emailAddress]
Whilst G Suite may support auto provisioning by default, you need to turn it on from the Azure AD Provisioning side. So if you're trying to test your SSO setup, make sure your user already exists in G Suite if provisioning in Azure AD has not been turned on.

So I changed "Unique User Identifier" attribute to "user.mail" and everything started working.  The only weird thing now is when I go back to the SSO setup for GSuite it has reverted back to "user.userprincipalname" but everything still works.
Thanks for the help.

I was using the new UI.

@rschiefer Can you please submit the ticket with us and then we can check it why this is happening?


Point annotations are not being downloaded.

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Expected Behaviour

I am annotating a single video and I have used the point annotation tool to mark a few keypoints in some frames. However, after saving my annotations and then clicking 'dump annotations', the point coordinates are not being saved. I tried with many formats but none of them save the point annotations. Other shapes such as bounding boxes are being saved. The point coordinates are expected to be saved.
Current Behaviour

Keypoint coordinates are not being dumped.
Possible Solution

Steps to Reproduce (for bugs)

Upload a single video task.
Using the 'point annotation tool' and 'shape' option (not track) mark a few keypoints in the frames.
Click save annotations.
Dump annotations.

Context

I am trying to annotate keypoints for people in the video frames.

We have to use the 'CVAT for video' save option.