Errors due to channel filter sent by storefront queries

What I'm trying to achieve
Setting up a Saleor instance with 3.0 backend and 3.0 storefront.
Steps to reproduce the problem

Follow the instructions to setup a basic demo configuration of backend, database and storefront with 3.0 branches.
Build the storefront with npm run build -> when collecting static props, requests being sent to the backend fail. The backend rejects queries being sent by the frontend because it does not expect the queries to include a "channel" filter.

I could quickfix this by removing the channel filter from the storefront (see my comment on a related issue in the storefront) Then, I could set up the system. However, then I run into the next problem, which is very similar:

Try opening a category page, like in the demo shop via "ACCESSORIES" or "GROCERIES" in the top left corner.
The dev console reports an error "400 - bad request" on the graphql request to the backend.

What I expected to happen
I expect the current state of branch 3.0 of backend and storefront to work well together. As channels are a feature to be included in saleor 3.0 I guess it is correct that the frontend includes the channel filter. In this case the backend should accept it.
Screenshots and logs
This error gets reported several times when trying to build the storefront with npm run build:
2021-07-06 15:44:05 > WARNING django.request Bad Request: /graphql/ [PID:14:ThreadPoolExecutor-44_0]
2021-07-06 15:44:05 > INFO saleor.graphql.errors.handled A query had an error [PID:13:ThreadPoolExecutor-1_0]
2021-07-06 15:44:05 > graphql.error.base.GraphQLError: Argument "filter" has invalid value {channel: $channel, inCollection: $collectionId, inCategory: $categoryId, filterableInStorefront: true}.
2021-07-06 15:44:05 > In field "channel": Unknown field.

After quickfixing the ShopAttributeQuery, when trying to open a category page:
2021-07-07 09:17:11 > WARNING django.request Bad Request: /graphql/ [PID:14:ThreadPoolExecutor-86_0]
2021-07-07 09:17:11 > INFO saleor.graphql.errors.handled A query had an error [PID:12:ThreadPoolExecutor-1_0]
2021-07-07 09:17:11 > Traceback (most recent call last):
  File "/app/saleor/graphql/views.py", line 283, in execute_graphql_request
    response = document.execute(  # type: ignore
  File "/usr/local/lib/python3.9/site-packages/graphql/backend/core.py", line 32, in execute_and_validate
    return execute(schema, document_ast, *args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/graphql/execution/executor.py", line 113, in execute
    exe_context = ExecutionContext(
  File "/usr/local/lib/python3.9/site-packages/graphql/execution/utils.py", line 113, in __init__
    variable_values = get_variable_values(
  File "/usr/local/lib/python3.9/site-packages/graphql/execution/values.py", line 74, in get_variable_values
    raise GraphQLError(
2021-07-07 09:17:11 > graphql.error.base.GraphQLError: Variable "$filter" got invalid value {"attributes": [], "categories": ["Q2F0ZWdvcnk6MjA="], "channel": "default-channel", "collections": [], "price": {"gte": null, "lte": null}}.
2021-07-07 09:17:11 > In field "channel": Unknown field.

System information
Saleor version:

[ ] dev (current master)
[x] 3.0
[ ] 2.11
[ ] 2.10

Storefront version:

[ ] dev (current master)
[x] 3.0
[ ] 2.11
[ ] 2.10

Operating system:

[ ] Windows
[x] Linux
[x] MacOS
[ ] Other

yliyyi

Okay I have a workaround now, which feels kinda dirty. The issue is that the backend does not expect the channel field on the ProductFilter and on the AttributeFilter. However, the value of the channel field is being used by these filters. Hence, I just added the field to the filter. Adding it in the fields attribute of the Meta subclass is not possible, as the filter model Attribute and Product do not have an attribute named channel. Hence, I added the field as custom filter without effect:
(graphql/attribute/filters.py)
class AttributeFilter(MetadataFilterBase):
    ...
    channel = django_filters.CharFilter(method="noop_filter")

    def noop_filter(self, queryset, name, value):
        return queryset
    ...

And exactly the same in the ProductFilter in graphql/product/filters.py.
Additionally, there are several requests that do not use the channel filter yet but only request the "default channel" to be used. This is problematic in the demo database, as this contains two channels. The get_default_channel() helper function in channel/utils.py however raises an exception in case there's more than one channel. So I replaced this line
channel = Channel.objects.get() with this line channel = Channel.objects.get(slug="default-channel") in order to retrieve the default channel, no matter how many other channels there are.
This hard-coded string should be replaced by some environment variable though.
This feels like a dirty workaround but it gets the current 3.0 branch to work. I really hope there won't be any further problems like this... otherwise, awesome piece of software! :)
I leave this issue open as a note for the staff because they probably want their demo shop fixed in the official codebase.

It is correct that the API doesn't accept channel in the filter inputs - we introduce this change in order to simplify the API and provide the channel param only once in the top-level query, for example:
{
  products(channel: "default-channel", filter: {search: "hoodie"}, first: 5) {
    edges {
      node {
        name
      }
    }
  }
}

Before you had to provide it twice - in the top-level query and in the filter input.
The storefront got broken after this change and we're now working on a fix that will remove usages of the channel param in filter inputs in the storefront queries. As you said - fixing it for now in the backend is kind of "dirty" and overall, I wouldn't recommend it, but if it works for you to run it locally, it's fine. Just remember to remove these changes after we release the fix in the storefront.

Should be fixed now on master: https://github.com/mirumee/saleor-storefront/pull/1072


Link issue on Windows

Currently running into some link issues with the malloc hooking which we should investigate and fix.
These are the link errors one gets. Happens both with LLD and MSVC's linker:
         lld-link: error: duplicate symbol: calloc in librpmalloc_sys-6320f0a329f3e257.rlib(rpmalloc.o) and in api-ms-win-crt-heap-l1-1-0.dll
         lld-link: error: duplicate symbol: free in librpmalloc_sys-6320f0a329f3e257.rlib(rpmalloc.o) and in api-ms-win-crt-heap-l1-1-0.dll
         lld-link: error: duplicate symbol: malloc in librpmalloc_sys-6320f0a329f3e257.rlib(rpmalloc.o) and in api-ms-win-crt-heap-l1-1-0.dll
         lld-link: error: duplicate symbol: realloc in librpmalloc_sys-6320f0a329f3e257.rlib(rpmalloc.o) and in api-ms-win-crt-heap-l1-1-0.dll

Disabling ENABLE_OVERRIDE again solves this on Windows. Though on Mac we need to have it enabled otherwise we run into rpmalloc compile issues


What is the actual timeout for a DNS renewal ?

Hello,
I am having a tough time trying to renew a let's encrypt certificate via win-acme.
It has failed 2 times already, alleging timeout.
 Domain:             www.gerencial.fsp.usp.br
 Record:             _acme-challenge.www.gerencial.fsp.usp.br
 Type:               TXT
 Content:            "GfovYyZmDNcVzJqW49vaxWMsyjczFKJTItdF-i3puQ8"
 Note 1:             Some DNS control panels add quotes automatically. Only one set is required.
 Note 2:             Make sure your name servers are synchronised, this may take several minutes!

 Please press enter after you've created and verified the record

 [INFO] Answer should now be available at _acme-challenge.www.gerencial.fsp.usp.br
 [INFO] Preliminary validation looks good, but ACME will be more thorough...
 [WARN] First chance error calling into ACME server, retrying with new nonce...
 [EROR] Authorization timed out

Could you please clarify what is the maximum waiting time for this ?
Thank you.

Hi @niloct, it seems like you're running an older version of the software, perhaps you can try the latest version? And maybe it would also provide some more helpful information on the screen if you use the --verbose switch at startup. As for the timeout, I suspect that's something happening on the server side.

Indeed @Wouter, I was running v<IP_ADDRESS>, and updating to the current
version solved the issue, because it reused the old nonce that timeout made
useless.
Thanks.
On Mon, Mar 8, 2021 at 4:49 PM Wouter Tinus<EMAIL_ADDRESS>wrote:

Hi @niloct https://github.com/niloct, it seems like you're running an
older version of the software, perhaps you can try the latest version? And
maybe it would also provide some more helpful information on the screen if
you use the --verbose switch at startup. As for the timeout, I suspect
that's something happening on the server side.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/win-acme/win-acme/issues/1778#issuecomment-793027505,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALVMJ7JCB3RHPLWOXUXW63TCUS6BANCNFSM4YZ64NCQ
.

--
Nilo César Teixeira
<EMAIL_ADDRESS>(55) (11) 98571-5314


MicrobeAnnotator Installation Warning

Hi,
I am in the process of installing MicrobeAnnotator v2.0.5. During the installation process I ran into the following warning at Step 11 (Processing GenBank files).
/rhome/anandab/.conda/envs/microbeannotatorV2/lib/python3.7/site-packages/Bio/GenBank/Scanner.py:1798: BiopythonParserWarning: Structured comment not parsed for YP_009176966. Is it malformed?                      BiopythonParserWarning,                                                                                /rhome/anandab/.conda/envs/microbeannotatorV2/lib/python3.7/site-packages/Bio/GenBank/Scanner.py:1798: BiopythonParserWarning: Structured comment not parsed for YP_009176967. Is it malformed?                      BiopythonParserWarning,                                                                                /rhome/anandab/.conda/envs/microbeannotatorV2/lib/python3.7/site-packages/Bio/GenBank/Scanner.py:1798: BiopythonParserWarning: Structured comment not parsed for YP_009176968. Is it malformed?                      BiopythonParserWarning,                                                                                /rhome/anandab/.conda/envs/microbeannotatorV2/lib/python3.7/site-packages/Bio/GenBank/Scanner.py:1798: BiopythonParserWarning: Structured comment not parsed for YP_009176969. Is it malformed?                      BiopythonParserWarning,                                                                                /rhome/anandab/.conda/envs/microbeannotatorV2/lib/python3.7/site-packages/Bio/GenBank/Scanner.py:1798: BiopythonParserWarning: Structured comment not parsed for YP_009176970. Is it malformed?                      BiopythonParserWarning,                                                                                /rhome/anandab/.conda/envs/microbeannotatorV2/lib/python3.7/site-packages/Bio/GenBank/Scanner.py:1798: BiopythonParserWarning: Structured comment not parsed for YP_009176971. Is it malformed?                      BiopythonParserWarning,                                                                                2022-04-29 11:55:08,912 [INFO]: Finished
Do think this warning can lead to issues while executing MicrobeAnnotator for annotations?
If you would like I can share the log file generated during installation
Thank you for developing this great tool!

I received the same warings.

Hello any update, this can safely ignored??


Fix SingleStoreIO performance test job

Followup of #24290
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

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

run seed job

Run Java SingleStoreIO Performance Test

R: @AdalbertMemSQL

R: @ahmedabu98


Add support for Logitech G110 keyboard

Is it possible to add partial support for this keyboard? I know that it's a little bit old device, but still can use some features from Aurora. Backlight lacks of green LEDs from RGB palette, and can change color and brightness for all keys simultaneously, but otherwise using the same api with other logitech keyboards. If you need any help with testing with this device, feel free to ask me.

Support for it should come with monochrome support.


python 3.10 support

waiting for pytorch 1.11 to support python 3.10 as pytorch does not support it yet
https://github.com/pytorch/pytorch/issues/66424
https://github.com/pytorch/pytorch/milestone/26


Add Swift

Currently the way some ops with odd syntax are added is a bit janky, this is fixable using f-strings to define their emit (see: text_to_int, text_len, print, repeat).

This needs main merged to work with the readonly IR and also some tests.


Model training results are not reproducible

In your model, I fixed the random seed in the global, and also fixed the random seed when initializing the weight, and fixed the order of DataLoader data reading according to the pytorch official website document, why the results of each training are different, the code is as follows, I hope to answer the doubts, thank you very much
#global seed
seed = 3
torch.manual_seed(seed)

def init_weights(model, seed=3):
    torch.manual_seed(seed)
    if isinstance(model, torch.nn.Linear):
        torch.nn.init.xavier_uniform_(model.weight)
        model.bias.data.fill_(0.01)

#DataLoader

def seed_worker(worker_id):
    worker_seed = torch.initial_seed() % 2**32
    numpy.random.seed(worker_seed)
    random.seed(worker_seed)
g_cuda = torch.Generator(device='cuda')
g.manual_seed(3)

train_data_loader = DataLoader(data_and_labels, batch_size=batchSize, num_workers=workers,
        worker_init_fn=seed_worker, generator=g)

Hi @ADamon912,
I'm not sure which results you are referring to, given that we do not have a specific paper for this package alone (and do not report results in the repo here). Please be more specific about which of our datasets you are using, which version of torch you are running our models on, etc.
If you are referring to results of training ACTIVA (a different model) with ACTINN, please open an issue in the ACTIVA repo.
I'll be closing the issue for now, but please feel free to open another issue in the appropriate repo, or to reopen the issue here providing which of our experiments you are trying to reproduce :)


Fixes some issues

Not quite finished, have to be able to parse variables used in project()

Ok, finished, ready for testing and merge.

Have to test this PR a day or two before merge. After this I'll work on build directories.

@zalox this PR is ready for merge. Tested on most platforms.

Merging this now as this PR is most likely more stable than master.


Does Scrapper handle concurrency?

Kudos to the Scrapper team, this saved me a ton of work trying to fix a how Playwright handles memory (50 pages would eat up 128GB of RAM and go OOM)..
Wanted to know how Scrapper handles concurrent calls and wanted to suggest updating the documentation so that is explained..

@dustyatx Sure! Thanks for the kind words about Scrapper. Yes, it handles concurrent calls. You can see how in the code - it's made to be easy to understand. Great idea about updating the docs to explain this better. We'll consider it for sure! If you have more questions or suggestions, feel free to share. Thanks for your support!


Running pytest on flask 1.0 (ModuleNotFoundError: No module named 'flask.json.tag'; 'flask.json' is not a package)

Expected Behavior
When I run pytest on my code it should complete all tests successfully. This does work fine in 0.12.2.
Actual Behavior
After upgrading to flask 1.0 I get a strange error when running pytest. I was hoping you might have some insight
Traceback (most recent call last):
  File "/Volumes/Storage/Users/claygorman/.pyenv/versions/3.6.4/envs/testproj-1/lib/python3.6/site-packages/_pytest/config.py", line 371, in _importconftest
    mod = conftestpath.pyimport()
  File "/Volumes/Storage/Users/claygorman/.pyenv/versions/3.6.4/envs/testproj-1/lib/python3.6/site-packages/py/_path/local.py", line 668, in pyimport
    __import__(modname)
  File "/Volumes/Storage/Users/claygorman/.pyenv/versions/3.6.4/envs/testproj-1/lib/python3.6/site-packages/_pytest/assertion/rewrite.py", line 213, in load_module
    py.builtin.exec_(co, mod.__dict__)
  File "/Volumes/Storage/clay-dev/testproj/tests/conftest.py", line 13, in <module>
    from testproj import create_app
  File "/Volumes/Storage/clay-dev/testproj/testproj/__init__.py", line 8, in <module>
    from flask import Flask
  File "/Volumes/Storage/Users/claygorman/.pyenv/versions/3.6.4/envs/testproj-1/lib/python3.6/site-packages/flask/__init__.py", line 21, in <module>
    from .app import Flask, Request, Response
  File "/Volumes/Storage/Users/claygorman/.pyenv/versions/3.6.4/envs/testproj-1/lib/python3.6/site-packages/_pytest/assertion/rewrite.py", line 213, in load_module
    py.builtin.exec_(co, mod.__dict__)
  File "/Volumes/Storage/Users/claygorman/.pyenv/versions/3.6.4/envs/testproj-1/lib/python3.6/site-packages/flask/app.py", line 34, in <module>
    from .sessions import SecureCookieSessionInterface
  File "/Volumes/Storage/Users/claygorman/.pyenv/versions/3.6.4/envs/testproj-1/lib/python3.6/site-packages/_pytest/assertion/rewrite.py", line 213, in load_module
    py.builtin.exec_(co, mod.__dict__)
  File "/Volumes/Storage/Users/claygorman/.pyenv/versions/3.6.4/envs/testproj-1/lib/python3.6/site-packages/flask/sessions.py", line 21, in <module>
    from flask.json.tag import TaggedJSONSerializer
ModuleNotFoundError: No module named 'flask.json.tag'; 'flask.json' is not a package
ERROR: could not load /Volumes/Storage/clay-dev/testproj/tests/conftest.py

Environment

Python version: 3.6.4
Flask version: 1.0
Werkzeug version: 0.14.1

I can't reproduce it. Can you try it in your own python interpreter?
>>> from flask.json.tag import TaggedJSONSerializer

Please use Stack Overflow for questions about your own code. This tracker is for issues related to the project itself. Be sure to include a minimal, complete, and verifiable example.


Interpreter exception behavior

Presently when a python exception is encountered causes the interpreter to drop out and exit with a python stack trace.
New behavior should be to:
1. close the current file stream being interpreted,
2. switch input to stdin,
3. display the python exception (and possibly stack trace),
4. set Debug to True in the Continuation

Implementing under branch: matching-1-issue03


[macOS] Called not implemented method: setPlayerMode

Hello,
It seems that the implementation of the method got lost with the current version 1.0.0. It worked fine with 0.20.1.
Due to the fact that the same implementation is used on iOS, i think the same problem exists there too.
Regards

Good catch. Player mode is irrelevant on iOS, but we should have a no-op handler to avoid errors.
https://github.com/bluefireteam/audioplayers/pull/1162

Hello,
Any chance for a release with this fix this or next week ?
Regards

Can confirm that this is fixed with version 1.0.1.


@Fannovel16  ->Bullshit folders !

ComfyUI Revision: 1647 [1ffa8858] | Released on '2023-11-04'
@Fannovel16
Currently, all models are in many multi sub folders and since last version all folders names are not same.
And many are not in your folder but in ComfyUI_windows_portable/ckpts... bad
I have a backup of all models from last version and tried to place in new folders. Working but no way for some, need to download again.

Why don't put all models in ckpts, that all ?
And like it's models, to be smart, they must be in ComfyUi/models/ckpts
DWpreprocesseur doesn't work anymore with new ComfyUI
`Error occurred when executing DWPreprocessor:
Unknown C++ exception from OpenCV code
File "D:\ComfyUI_windows_portable\ComfyUI\execution.py", line 153, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
File "D:\ComfyUI_windows_portable\ComfyUI\execution.py", line 83, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
File "D:\ComfyUI_windows_portable\ComfyUI\execution.py", line 76, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
File "D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux\node_wrappers\dwpose.py", line 58, in estimate_pose
out = common_annotator_call(cb, image, include_hand=detect_hand, include_face=detect_face, include_body=detect_body, image_and_json=True, resolution=resolution)
File "D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux\utils.py", line 52, in common_annotator_call
np_result = model(np_image, output_type="np", detect_resolution=detect_resolution, **kwargs)
File "D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux\node_wrappers\dwpose.py", line 54, in cb
result = model(image, **kwargs)
File "D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux\src\controlnet_aux\dwpose_init_.py", line 184, in call
poses = self.detect_poses(detected_map)
File "D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux\src\controlnet_aux\dwpose_init_.py", line 171, in detect_poses
keypoints_info = self.dw_pose_estimation(oriImg.copy())
File "D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux\src\controlnet_aux\dwpose\wholebody.py", line 55, in call
det_result = inference_detector(self.session_det, oriImg)
File "D:\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux\src\controlnet_aux\dwpose\cv_ox_det.py", line 107, in inference_detector
output = session.forward(outNames)`

Yes, we changed something,  and the default folder shoud in comfyui_controlnet_aux/ckpts/(some subfolders), and you can change comfyui_controlnet_aux/ckpts/ to you own config path using config.yaml  with annotator_ckpts_path: 'D:/ComfyUI_windows_portable/ComfyUI/models/ckpts'.Bisides, Some models might in comfyui_controlnet_aux/src/cptks at previous version, you can move them to your own config path.

And the reason that I didn't put all models in one folder just because many people  in China have difficulty to download models via scripts, these subfolders can help them to find models in huggingface.

Vielen Dank, es funktioniert :-)


SourceKitLSPTests: avoid forced unwrapping

Avoid forced unwrapping and instead add assertions that the diagnostics
are received.  This aids bring up on a new platform when the LSP may not
respond properly.

@swift-ci please test

@swift-ci please test

@swift-ci please test

rdar://99561865

@swift-ci please test

@ahoppen ping


Add an example project to the new package template

All Flutter packages should include an example project that demonstrates how to use the packages.
Typically developers create a Flutter project under /example for this purpose.
Flutter should automatically create a new Flutter project under /example when creating a new Flutter package using the Flutter tool.
By adding this subproject, more developers are likely to implement an example project, and it alleviates the need for every package developer to manually create this subproject for every new package.

This is already implemented for Flutter plugins, so this is way trivial.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.10 to before v5.12.11",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=45dd9943fce08f1b38352ff9453682253bdf19b7",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=047fd16015a79180771650aa6ce71f68b2c23368"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "45dd9943fce08f1b38352ff9453682253bdf19b7",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "047fd16015a79180771650aa6ce71f68b2c23368",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "ASoC: core: Fix Null-point-dereference in fmt_single_name()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.12.11 by commit 047fd16015a79180771650aa6ce71f68b2c23368, it was introduced in version v5.10 by commit 45dd9943fce08f1b38352ff9453682253bdf19b7. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001038


JSDoc comment templates/scaffolding may not use formatter newlines

Not that you should fix it in this PR, but it seems like a bug that we don't have this for JSDoc comments.
Originally posted by @jakebailey in https://github.com/microsoft/TypeScript/pull/52298#discussion_r1083166870
        return JsDoc.getDocCommentTemplateAtPosition(getNewLineOrDefaultFromHost(host, /*formatSettings*/ undefined), syntaxTreeCache.getCurrentSourceFile(fileName), position, options);

To clarify out of context, "this" is formatSettings. I think this is just a plumbing problem.


Order of alternatives

It was recently pointed out to me that ABNF alternatives as described in section 3.2 of RFC 5234 are unordered.
https://tools.ietf.org/html/rfc5234#section-3.2
What this means is that you can't use a first-match-wins algorithm, because all alternatives have the same priority. But this is how the AlternativeLexer class is currently implemented.
What are some better ways to parse alternatives, other than first-match-wins?

I added a class GreedyAlternativeLexer that implements the following strategy:

Try to read each alternative in no particular order
Back out of successful matches, but remember the best match
(Greedy matching: the longest match is the best match)
Return the best match, or a null reference if none of the alternatives match


onBuild command from @netlify/plugin-nextjs  Fails

Describe the bug
My repo uses yarn workspaces.
I'm building into a custom directory.
The build works, but then the plug-in fails because the files already exist.
To reproduce
Oh boy.

Needs a repo with workspaces, and the next app in say /packages/app/foo.

Set the build directory in the next ui to  /packages/app/foo/out

Set the build command to yarn workspace mypackage build

watch as it fails with this error

...
10:45:02 PM: info  - using build directory: /opt/build/repo/packages/app/ontologies/.next
10:45:02 PM: info  - Copying "static build" directory
10:45:02 PM: info  - No "exportPathMap" found in "next.config.js". Generating map from "./pages"
10:45:02 PM: info  - Launching 7 workers
10:45:02 PM: info  - Exporting (0/2)
10:45:03 PM: info  - Exporting (2/2)
10:45:03 PM: Export successful. Files written to /opt/build/repo/packages/app/ontologies/out
10:45:03 PM: Done in 27.00s.
10:45:03 PM: Done in 27.69s.
10:45:04 PM:
10:45:04 PM: (build.command completed in 28.6s)
10:45:04 PM:
10:45:04 PM: ────────────────────────────────────────────────────────────────
10:45:04 PM:   3. onBuild command from @netlify/plugin-nextjs
10:45:04 PM: ────────────────────────────────────────────────────────────────
10:45:04 PM:
10:45:04 PM: Detected Next.js site.

Yep pilot error sorry!


Improved: List and Grid (OFBIZ-11345)

According to the definition in widget-form.xsd the use of a combination of a form with type="list" is deprecated in favour of a grid.
Refactor various list forms into grids.
Refactor various list form references in screens.
Modified:
InvoiceScreens.xml: from form ref to grid ref
InvoiceForms.xml: from form definition with list ref to grid definition with list ref
additional cleanup

This again contains changes actively removing separating blank lines, which makes the files less readable.
If you are really interested in getting the functional changes into the codebase, why do you still introduce those changes and mix it up with the functional changes?

I did several of them and often crossed issues afterward, botched work relying on committers to assume, closing


Add initial checkin for openebs chart

Signed-off-by: kmova<EMAIL_ADDRESS>
Thank you for contributing to kubernetes/charts. Before you submit this PR we'd like to
make sure you are aware of our technical requirements and best practices:

https://github.com/kubernetes/charts/blob/master/CONTRIBUTING.md#technical-requirements
https://github.com/kubernetes/helm/tree/master/docs/chart_best_practices

For a quick overview across what we will look at reviewing your PR, please read
our review guidelines:

https://github.com/kubernetes/charts/blob/master/REVIEW_GUIDELINES.md

Following our best practices right from the start will accelerate the review process and
help get your PR merged quicker.
When updates to your PR are requested, please add new commits and do not squash the
history. This will make it easier to identify new changes. The PR will be squashed
anyways when it is merged. Thanks.

/assign

Thank you @unguiculus I have updated the PR with some change to the label and value (conventions changed)

/ok-to-test

@unguiculus - still working on few more comments, which I will try to push with my next commit:

refactor the "affinity" section
refactor to remove the if blocks around serviceAccount, still trying to find out if this could be done.
update the readme

Hi @unguiculus. incorporated the comments. thank you!

ping @unguiculus  .. Looking forward to your feedback.

Hi @unguiculus. Checking if you have any changes required after @kmova 's comments

/unassign

Removed the storage classes and updated NOTES.txt with details on creating storage class.

@unguiculus - moved openebs to stable after incorporating the changes. Thanks!

/lgtm


Deploy to github pages with Travis (or Github actions)

Travis CI can publish to Github pages as part of its deploy step: https://docs.travis-ci.com/user/deployment/pages/
Use this to publish new docs whenever changes are merged, instead of having to do it by hand. It may be useful to use the gh-pages branch instead of master for this purpose, although it's not clear if the directory structure needs to change in that case.

This issue should be used for two other tasks as well:

Transfer to @corewa-rs organization
Separate the website out of this repo (some kind of static site generator that just links to docs.rs + crates.io instead of generating it inline)


DRAFT-3 - Move UI application into the UI submodule

The UI application class is currently within the general project.
Move this into the UI submodule instead.

Already done.


Improve search logic in feature inventory screen

Task/Issue URL: https://app.asana.com/0/1198194956794324/1208633884628758/f
Description
Improve the (internal) feature flag inventory screen search logic:
Before:

searches would filter feature flags that match the search text
After:
searches filter feature flags that match the search text, but:

if match is a top-level features, all sub-features are also considered a match (even if their name doesn't match)
if match is a sub-feature, parent feature is also considered a match (even if its name doesn't match)

Steps to test this PR
Test

[ ] install from this branch, open app -> settings -> feature flag inventory
[ ] search for a sub-feature by name
[ ] verify sub-feature and its parent top-level feature are displayed
[ ] search for a top-level feature by name (eg. autofill)
[ ] verify the top-level feature and ALL its sub-features are displayed
[ ] smoke test enable/disable features

#5232  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @aitorvs and the rest of your teammates on  Graphite


about scroll bar

When there are 16 or 17 messages on the screen, the scroll bar will jump to the top when switching sessions and coming back,like this

I cannot reproduce, which browser and OS are you using?

im use edge 96. in windows

Did you update the scroll-distance prop?

No, I not use this prop.  you can't emerge ?

I couldn't reproduce on Edge using Windows.
Could you check if you have the same issue with other browsers, like Google Chrome?

OK, if you don't repeat it I don't think it's a very important issue I'll close it. By the way, I use windows


Background color not changing in onlyLabel mode

Version of the component: 2.1
Swift version: 3
iOS version: 10.1
Device: iPhone 7
Xcode version: 8.1

You can reproduce this issue in your example project, by just changing the backgroundColor of default state from clear to white. Background color of selected item is not changing.

I think this was fixed in the newest version, works fine for me (2.1.2 from Cocoapods).

Hi @onurays. Please check the last version. Lemme know if it's not fixed

@xergic, @serejahh Unfortunately the problem still exists.
When view created, states are correct (white is selected):

Changing selection for the first time is also OK:

However, after changing the selection again, defaultBackground is gone:

I will also try to debug your code as soon as possible.

It would be great if you create a PR fixing the bug

Hello, @onurays looks like I have found the source of this bug. So soon I'll create PR to fix this issue.


Fix user registration and login

Fixed a variety of minor issues to get user registration and login to work.

@Nunie123 All changes looks good  to me . I have left some questions regarding username and email.


add public service controller for manage loadbalancer service

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:

/kind feature
/sig network

What this PR does / why we need it:
This controller focuses on automating the management of LoadBalancer services
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/lgtm


Write a Ruby program to print fibonacci series without recursion

Description
Write a Ruby program to print fibonacci series without recursion
Input  : 5
Output : 0 1 1 2 3

How to contribute

Save the solution in PrintFibonacciSeriesWithoutRecursion.rb file
Add PrintFibonacciSeriesWithoutRecursion.rb file in print-fibonacci-series-without-recursion folder

assign this issue to me!

!assign

Hey @sksachin7z2,
This issue has been assigned to you for more than 15 days.
We are unassigning you from this issue.
If you are still interested in contributing to this issue, please get auto-assigned on the issue by commenting !assign again.
Thanks for your contributions :)

!assign


Updating feature branch with latest changes from ORIGIN develop

Hey @sampie777 --
Just completed some work to get the latest branch of the working websocket-obs-java a bit closer to the latest version.  There's been a bit of work that has aligned with the work you've done.
Merged from HEAD on develop, currently https://github.com/Twasi/websocket-obs-java/commit/f2532e0a0985a24c72afb4fe43456bd54ebc130c
There's a lot here but 99% of it is just merge.  The key things I noticed while doing the merge was:

maxTextMessageSize option in OBSCommunicator has been completely removed (this should be good!)
startStreaming and stopStreaming options have been added upstream.
A separate @OnWebSocketError handler was written for OBSCommunicator--this just has some minor impact.

I took this, built it, and then build obs-scene-que off this build.  Things look stable.
This should get us SUPER close to being able to recombine this branch to master and eliminate the forked logic--but I'm not going to touch that right now.  I have a few other things I need to do.
Side note: I'm having a couple of failing tests in obs-scene-que but I think they're unrelated.  LMK if you see any errors there.

Closing this--there are a lot more changes to be merged now unfortunately.

Closing this--there are a lot more changes to be merged now unfortunately.

@cbrews Thank you for the effort. As you already saw, upstream starts to differ a lot from this version. I've decided not to spend more time updating the upstream version (from Twasi) or trying to get 'in sync' with it, for several reasons.
One note that I want to address is that removing maxTextMessageSize actually is problematic, as the default value is 64*1024 I think. I've had user run into problems because this size is to small for large scene collections.

@cbrews Thank you for the effort. As you already saw, upstream starts to differ a lot from this version. I've decided not to spend more time updating the upstream version (from Twasi) or trying to get 'in sync' with it, for several reasons.
One note that I want to address is that removing maxTextMessageSize actually is problematic, as the default value is 64*1024 I think. I've had user run into problems because this size is to small for large scene collections.


Parallelize the code

http://blog.dominodatalab.com/simple-parallelization/

This is done :)

See #27


Depreciate Deoxys Encryption

This adds explicit disallowing of Deoxys for encryption, however decryption will still be supported.
This fixes #116.

It looks like a crutch) Maybe add an extra feature to add the deoxis algorithm.
#[cfg(feature = "deoxysII256")]
DeoxysII256,

I wanted to keep this functionality within the core library fully, but I'll look into doing it this way too :)


Doesn't work save command on MacOS

Trying add ldkt to my Unity project
After adding a command to ldtk, it doesnt parse levels and error with command is showed in unity (that command isn't added)

Unity 2022.3.31f1
Ldtk 1.5.3

For your command, you'll need that "$1" added to the end of it like it's pointing out.
Join the discord and I can give some greater hands-on help. Also there're previous resources for other mac users having some issues in there 🙂


How to create a good goal-metric

@GeorgLink In the focus area template, I want to link to an example/directions/criteria for how to write a good goal-metric.  Do you have something like that?

I have not been keeping track of whether we were creating "good" goal-question-metric relationships. We might be trailblazers who set the standard for the CHAOSS project.
Below is not a definitive answer, but my thoughts on goal-question-metric formulation. I inform my musings through Basili, Caldiera, and Rombach.
A good goal should detail:

Issue (e.g., Diversity and Inclusion)
Object (e.g., Project and Community Places)
Viewpoint (e.g., Community)
Purpose (e.g., Understand)

Goal: Understand the diversity and inclusion of project and community places from the viewpoint of community members.
A question may address (with examples):

How can we characterize project and community places (i.e., the object) with respect to the understanding diversity and inclusion?

What project and community places are used by a community?
What do we know about the people at these places?

How can we characterize the attributes of project and community places (i.e., the object) with respect to diversity and inclusion?

What demographics are represented at the project and community places?
Has the composition of demographics changed over time?

How do we evaluate the characteristics of project and community places (i.e., the object) that are relevant to understanding diversity and inclusion?

Are we meeting our diversity and inclusion goals?
Is the diversity and inclusion improving?

On the Resource Pages, we would then provide qualitative and quantitative ways to answer the questions. These methods for answering are the metrics.
I'm CCing CHAOSS members who might have experience with formulating goal-question-metric relationships and can help us: @germonprez @sgoggins @dicortazar @klumb @jgbarah @BenLloydPearson

This is great , thank you.

I mentioned this issue in the weekly meeting today. We may have other
CHAOSS members join us tomorrow to discuss with us how to write good
goal-question-metrics.

Closing based on:  https://github.com/chaoss/wg-evolution/issues/18
Please open new issue if needed.


NO-JIRA: tekton pac customizations after pipeline tasks update

Konflux bot is not updating the customized pipeline code with new available task definitions and requires reconfiguring customization, will check more with the konflux team.

/lgtm

/lgtm
/approve


Document image crate integration on docs.rs

Right now the image feature in jxl-oxide crate is disabled on docs.rs. Because of that the docs on the integration do not show up on docs.rs at all. This PR fixes that.
Details
doc_auto_cfg is a nightly rustdoc feature, so it's only enabled for docs.rs to make it possible to build the docs for this crate on stable. All ways of documenting conditional features are currently nightly-only, but are also widely used so they're unlikely to outright break.
You can preview the generated documentation with this command: cargo +nightly rustdoc --open --features=image -- --cfg=docsrs
It looks like this:

A point release including this would be very welcome, so that I could promote the integration on social media and link to the docs.rs page directly.


Bug in PhpArrayScanner

Hi!
PhpArrayScanner overrides translations that have already been edited via the admin interface.
The issue is in the createLanguageLineIfDoesntExist() method of Brackets\CraftablePro\Translations\Repositories\LanguageLineRepository. It only checks if the translation line exists, but not which specific languages it contains.
Proposed solution
What works for me is swapping the order of the parameters of the array_merge() function in the createLanguageLineIfDoesntExist() method - $languageLine->text = array_merge([$language => $text], $languageLine->text).
If there is a translation of the given string in the DB, the values from DB will override the values from the scanned lang files.

Hi @Matte478
this issue was also fixed in the latest release 🤗


Fix dwalk default output

dwalk should have been printing the summary to the screen by default.
The reason it was only happening when verbose was set was because
there were a couple of bugs in the mfu_flist_print_summary function.
MFU_LOG_INFO was not set by default, and it was requiring VERBOSE to
be set in order to use MFU_LOG_INFO log/print statements. So
mfu_flist_print_summary would print nothing unless the debug level
was set to VERBOSE. Also, mfu_flist_print_summary does not need
to be called in dwalk.c, because it is already called in mfu_flist_walk.

@dsikich The mfu_flist_print_summary was being from mfu_flist_walk, so the flist summary was printing twice. But based on our conversations I'm going to remove that call, and just put it in the tool itself.

@adammoody code is updated.

Thanks!  Looks good to me.


Add new committer Simon

@simon824 Hi, Simon, please check your information is correct.

@simon824 Hi, Simon, please check your information is correct.

LGTM, thanks.

Thanks @ruanwenjun and congrats @simon824


add: built in api support is added, as an example GET /api/health-check endpoint is added

Hi @mehmetsefabalik ,
Could you add feature usage documentation?

Hi @mehmetsefabalik ,
Could you add feature usage documentation?

this is the feature of nextjs, it is well documented in nextjs docs. So the user of this boilerplate is supposed to read this feature from nextjs docs.

Hi @mehmetsefabalik ,
Could you add feature usage documentation?

this is the feature of nextjs, it is well documented in nextjs docs. So the user of this boilerplate is supposed to read this feature from nextjs docs.

We can still point to related documentation links 👍

Hi @mehmetsefabalik ,
Could you add feature usage documentation?

this is the feature of nextjs, it is well documented in nextjs docs. So the user of this boilerplate is supposed to read this feature from nextjs docs.

We can still point to related documentation links 👍

done

Hi @mehmetsefabalik, thank you for your contribution. I noticed that only get requests are handled by the custom server side. Since you are adding the api routes support, can you check the server files to handle other http methods?
server/index.ts#L34
I'm guessing changing this line from .get() to .all() might be enough.

Hi @mehmetsefabalik, thank you for your contribution. I noticed that only get requests are handled by the custom server side. Since you are adding the api routes support, can you check the server files to handle other http methods?
server/index.ts#L34
I'm guessing changing this line from .get() to .all() might be enough.

done

Thank you for contribution @mehmetsefabalik


Adds: MANIFEST_FILE_NAME var as input to the github action

Adds MANIFEST_FILE_NAME to the input of github action.

@korvyashka I think you can close this PR


Obsoletion notice: excretion

During the generic subset review, we propose to obsolete 'excretion'. The reason for obsoletion is that this term groups unrelated processes, and has been used inconsistently.
Children will re-housed as follows:

defecation -> digestive process
micturition -> ok, already under 'renal system process'
'renal phosphate excretion' -> ok, already under 'renal system process'
'renal potassium excretion' -> ok, already under 'renal system process'
'renal sodium excretion' -> ok, already under 'renal system process'
'urate salt excretion' -> move under 'renal system process'; change label to 'renal urate salt excretion'
Thanks, Pascale

Why not simply tag as do-not-annotate?
I agree this groups many different mechanisms but this is true for many processes in GO. It would be good to have a prospective idea of what we see GO looking like in 5-10 years so other ontologies can make plans and create a separate ontology e.g for physiology.

Note: we previously went through a round of confusion about the scope of the term "excretion" and how it related to "renal system" as it pertains to GO:0003014 renal system process; see #16143

4 out of the 5 children of excretion are renal excretion processes; the 5th is 'defecation', which seems out of place.
Also, if you look at annotations to 'excretion', it seems to have been confused with 'secretion' in some cases.
I am happy to create a 'renal excretion' term to group the specific compounds excreted (potassium, sodium, etc). We could also reuse the 'excretion' term for this, when annotations are corrected.

Note that there is also 'GO:0044062 regulation of excretion'; should either be obsoleted or renamed, to be consistent with what we decide for 'excretion'.

Decision on ontology call

[ ] keep excretion, add DO NOT annotate
[ ] move defecation under digestive system process

Thanks, Pascale

Defecation: also add 'part of digestion'  -see https://en.wikipedia.org/wiki/Defecation

I am still not sure 'excretion' is correctly placed; https://www.britannica.com/science/excretion refers to excretion as elimination of waste in all organisms, even microbes, which would NOT make it a systems process.
I'll leave it as is for now.
Thanks, Pascale

Note: we previously went through a round of confusion about the scope of the term "excretion" and how it related to "renal system" as it pertains to GO:0003014 renal system process; see #16143

4 out of the 5 children of excretion are renal excretion processes; the 5th is 'defecation', which seems out of place.
Also, if you look at annotations to 'excretion', it seems to have been confused with 'secretion' in some cases.
I am happy to create a 'renal excretion' term to group the specific compounds excreted (potassium, sodium, etc). We could also reuse the 'excretion' term for this, when annotations are corrected.

Could you make this 'renal excretion' term? I could use it to rehouse my annotation which is essentially getting rid of a toxin via excretion.

Sure

Thanks!

Hi Helen,
Trying at add that renal excretion process, I just noticed that the definition of what would be the children terms is
" The elimination by an organism of [potassium or some compound] in the urine."
Is this OK? Should we change it to  "The elimination by an organism of [some compound] through the renal system."

Also - would  ' renal excretion' be different from 'GO:0097254 renal tubular secretion'? Def: "Secretion of substances from peritubular capillaries into the renal tubules to be incorporated subsequently into the urine. Substances that are secreted include organic anions, ammonia, potassium and drugs. "

Also - would ' renal excretion' be different from 'GO:0097254 renal tubular secretion'? Def: "Secretion of substances from peritubular capillaries into the renal tubules to be incorporated subsequently into the urine. Substances that are secreted include organic anions, ammonia, potassium and drugs. "

Good question - perhaps by tweeking the definition......I will have a look

If we could change:
'GO:0097254 renal tubular secretion' to "Secretion of substances from peritubular capillaries (or surrounding hemolymph in invertebrates) into the renal tubules to be incorporated subsequently into the urine. Substances that are secreted include organic anions, ammonia, potassium and drugs. "
That would work for me.

If we could change:

if we made that change, then we dont need the new term? And 'renal x excretion' could go under that term, with a similar change in the definition?

Yes. That seems correct (well, I am 96-99% sure).

Hi @RLovering
Does that work for you?
ie

[ ] change def 'GO:0097254 renal tubular secretion' to "Secretion of substances from peritubular capillaries (or surrounding hemolymph in invertebrates) into the renal tubules to be incorporated subsequently into the urine. Substances that are secreted include organic anions, ammonia, potassium and drugs. "
[ ] move 'renal urate salt excretion', 'renal phosphate excretion', 'renal sodium excretion', 'renal potassium excretion' under that term
[ ] fix definitions of the 4 terms above, to match that of 'renal tubular secretion', ie "Secretion of [urate salt/phosphate/sodium/potassium] from peritubular capillaries (or surrounding hemolymph in invertebrates) into the renal tubules to be incorporated subsequently into the urine. "
Thanks, Pascale

sounds good to me ;)

@pgaudet
I removed the two existing excretion annotations for C. elegans; these were to genes that acted too far upstream.
However, in looking over the C. elegans literature, I think there are other genes that would warrant annotations to 'excretion'; this may be true for other invertebrates, as well.
See this paper for example:
https://pubmed.ncbi.nlm.nih.gov/25740900/
The rhr genes are annotated to transport and transporter activity, but that's not quite capturing the full story of the biology.  An additional annotation to 'excretion', or an otherwise invertebrate-appropriate term, seems warranted.

Hi @vanaukenk
Maybe in this case we can create directly 'ammonia excretion'? It would be more informative than just 'excretion', and ww could keep the 'do not annotate' tag on 'excretion'.
Would that work?

[ ] Also need to look at regulation terms

Thanks @pgaudet
I'll annotate the relevant transporters to ammonia excretion.
However, it looks like we may also need transporter and transport terms specific to ammonia, based on Fig. 8 in this paper:
https://pubmed.ncbi.nlm.nih.gov/26872996/
What do you think?  I can create a separate ticket for that, if you like.

We have several MFs:

GO:0008519 ammonium transmembrane transporter activity
GO:0015251 ammonium channel activity
GO:0015398 high-affinity secondary active ammonium transmembrane transporter activity
GO:0015400 low-affinity secondary active ammonium transmembrane transporter activity
and for BP:
GO:0072488 ammonium transmembrane transport
GO:0140157 ammonium import across plasma membrane
Do you need other more specific terms?

(rhr-2 is annotated to some of these by IEA and IBA, http://amigo.geneontology.org/amigo/gene_product/WB:WBGene00004359)
Thanks, Pascale

@pgaudet
Yes, and with the first paper I had annotated to those terms but I now think that's not correct. I think the idea here, based on Figure 8 in the paper above, is that these transporters are specifically transporting NH3 rather than NH4+.

I see, that's interesting! It looks like this could be a channel, specifically- see intro of the paper you mention, (PMID:26872996)

The gaseous form of ammonia, NH3, on the otherhand, cannot be actively transported across biomembranes, but requires a partial pressure gradient (ΔPNH3) and ideally a NH3-permeable channel for transmembrane passage. In animals, such NH3-channels have been identified to be glycosylated proteins belonging to the Rhesus-protein family.

The term  'GO:0015251   ammonium channel activity' has no references and no annotations, but when I search UniProt for 'ammonium/ammonia chanel' I get RHAG (Q02094), also mentioned in your paper (as well as the other Rhesus transporters RHBG and RHCG). One of the papers cited in the entry clearly mentions NH3 transport, PMID:22012326
E. coli amtA and amtB are also part of the same gene family - the mechanism of transport for this has been nicely studied in PMID:32662768, and shown to involve deprotonation of NH4 and transport of NH3 separately. Interestingly, the authors write "Despite this key general and biomedical importance, so far, no consensus on the pathway and mechanism of biological ammonium transport has been reached."
Anyhow:

It seems like whatever term we use/create, all this family should be annotated the same way.
Even though the substrate transported could be NH3, which we could create a term for,  the BP possibly corresponds to ammonium transport, since NH3 is unlikely to be in this form in the cell, I suppose it gets reprotonated rapidly.
On the other hand, if we are not sure whether the protein transports ammonium or ammonia, I dont see that we can create a grouping term that would capture that lack of knowledge. In the original paper you cite, the authors also are not unequivocal about which form is transported. We could keep ammonia and make a comment about the mechanism of transport that could involve deprotonation.

What do you think?
Thanks, Pascale

Yes, this is actually really interesting!
Based on the mechanism proposed in PMID:32662768 and the figure in the accompanying comment (PMID: 32840481):

maybe the appropriate thing to do at this point is to not add new ammonia transport/transporter terms, but instead keep the ammonium transport/transporter terms as is, create 'ammonium excretion' rather than 'ammonia excretion', and converge on consistently including the corresponding 'ammonia' terms as synonyms. EXACT or BROAD, though?
Right now in the ontology we have:
ammonium transmembrane transporter activity
EXACT: ammonia transmembrane transporter activity
ammonium channel activity
no synonyms
ammonium transmembrane transport
BROAD: ammonia transport
ammonium import across plasma membrane
no synonyms
proposed: ammonium excretion (instead of ammonia excretion?)

I would go for 'related' synonyms, as ammonia is not more general (broader) than ammonium.
I'll add xref to http://www.tcdb.org/search/result.php?tc=1.A.11. Based on that TCDB entry, all ammonia transporters should merge, this corresponds to a single family with a single mechanism.


Unconfigured lifecycle state management

Hi again @norro!
Yesterday, I had a meeting with @chcorbato , and we talked about the case where a lifecycle node transits to ErrorProcessing.
Following the documentation and the lifecycle node diagrams, if a node has an error it transits to ErrorProcessing. Then, based on this processing result, it can go to the Finalized state or Unconfigured state. Do you think that the system_modes must manage the unconfigured state of the lifecycle nodes? This management covers this situation and the start-up situation, where the nodes are in the unconfigured state.
Thank you!

Hi again @norro!
Yesterday, I had a meeting with @chcorbato , and we talked about the case where a lifecycle node transits to ErrorProcessing.
Following the documentation and the lifecycle node diagrams, if a node has an error it transits to ErrorProcessing. Then, based on this processing result, it can go to the Finalized state or Unconfigured state. Do you think that the system_modes must manage the unconfigured state of the lifecycle nodes? This management covers this situation and the start-up situation, where the nodes are in the unconfigured state.
Thank you!

This is in the context of our exemplary case of the laser_driver error. We want to elaborate on the layered approach we discussed in the last MROS meeting. This is how I interpret our desired design (please comment if something is not correct or clear):

First the laser_driver code for handling errors tries to recover from the error in the ErrorProcessing transition state.

(from here it is a related but different issue #48)

If it does not succeed (I guess that means node does not transition to Active), the ModeManager tries to recover from the error using the feature/rules. For this, @jginesclavero is adding a rule in the SystemModes file of our system.
If there is no rule, or there is but after applying it the alternative MODE(s) of the laser_driver are not reached either,  the ModeManager reports to the Metacontroller that the corresponding (sub)system(s) MODE(s) are not reachable.
(see issue for the continuation of the handling of errors at the higher layers)

I agree with 1. and 2.
However, the mode manager will not actively report that a certain mode is not available. With https://github.com/micro-ROS/system_modes/issues/43, however, it will be possible for the meta control to get the information, which modes are available.
This is also a question of timing for the following reason: Any state/mode transition will take some time (miliseconds to seconds, maybe), even in the normal, non-failure case. So it is not entirely clear, when someone (the mode manager? metacontrol?) should decide, that a transition or rule didn't work out and other actions have to be taken. I think this kind of decision, how long to wait for a node to recover or a rule to take effect, is best placed in the metacontrol, since this is probably task-specific.

This is also a question of timing for the following reason: Any state/mode transition will take some time (miliseconds to seconds, maybe), even in the normal, non-failure case. So it is not entirely clear, when someone (the mode manager? metacontrol?) should decide, that a transition or rule didn't work out and other actions have to be taken. I think this kind of decision, how long to wait for a node to recover or a rule to take effect, is best placed in the metacontrol, since this is probably task-specific.

Very good point indeed, so far we are not accounting for timing issues.
How do we include timing constraints for node management? These could be considered metacontrol requirements for the robotic application:

How should these requirements be defined? Language, relation to MROS metamodel @darkobozhinoski and ontology @rsanz @estherag
Where should they be defined?
I think we should have a discussion about this on the next meeting @darkobozhinoski, ideally with the input of all ROS developers/architects in MROS
@gavanderhoorn @marioney @wasowski @fmrico @jginesclavero @lbajo @ralph-lange

This implies the incorporation of some timestamping and temporal [interval] reasoning. We can incorporate some concepts from e.g. UML2 or UML MARTE.

However, the mode manager will not actively report that a certain mode is not available. With #43, however, it will be possible for the meta control to get the information, which modes are available.

I agree. So the current design proposal is that Mode Manager just inform about available and reachable modes, and Metacontrol is responsible for inferring from that about the success of reconfiguration actions.
See below for how to model that reasoning.

This is also a question of timing for the following reason: Any state/mode transition will take some time (miliseconds to seconds, maybe), even in the normal, non-failure case. So it is not entirely clear, when someone (the mode manager? metacontrol?) should decide, that a transition or rule didn't work out and other actions have to be taken. I think this kind of decision, how long to wait for a node to recover or a rule to take effect, is best placed in the metacontrol, since this is probably task-specific.

Very good point indeed, so far we are not accounting for timing issues.

How do we include timing constraints for node management? These could be considered metacontrol requirements for the robotic application:

How should these requirements be defined? Language, relation to MROS metamodel @darkobozhinoski and ontology @rsanz @estherag

This implies the incorporation of some timestamping and temporal [interval] reasoning. We can incorporate some concepts from e.g. UML2 or UML MARTE.

@rsanz can you point to the specific concepts?
I think we need to specify some modelling requirements (see below) to evaluate which concepts we need.

Where should they be defined?
I think we should have a discussion about this on the next meeting @darkobozhinoski, ideally with the input of all ROS developers/architects in MROS
@gavanderhoorn @marioney @wasowski @fmrico @jginesclavero @lbajo @ralph-lange

Modelling reqs for reconfiguration actions and timing

Metacontroller needs info on how long a reconfiguration action can take, to decide its success or failure. This depends on:

type of reconfiguration action: mode change, re-mapping, deploy node (we decided all nodes would be deployed, req for mode manager)
the node/ susbsystem reconfigured

We could provide this information in the MROS model of the system (Darko's metamodel) as we are doing with the QAs, but I think it is more related to the specific software components that to the application logic.
We could define default values in the MRSO metacontroller to assume when no info is provided.
E.g. assume node mode change takes up to 2secs, and subsystem mode change can take up to 5secs
@jginesclavero @lbajo @marioney @fmrico what numbers are reasonable for navigation2 nodes?


chore(main): release 1.25.0

:robot: I have created a release beep boop
1.25.0 (2024-07-18)
Features

implement GenerateApiKey (#460) (1371155)

Bug Fixes

make sure to clean up caches and stores that can be leaked in tests (#461) (f98bcd9)

Miscellaneous

add dev docs snippets for storage client (#457) (769cfc8)
make sure push-to-main has test session token too (#462) (268e771)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/momentohq/client-sdk-go/releases/tag/v1.25.0 :sunflower:


Leverage notification progress for long running operations

See this issue for more information:
https://github.com/Microsoft/vscode/issues/44090
We'll have to wait until its released, though.

Closing as dupe of https://github.com/Microsoft/vscode-azureappservice/issues/455


Format of negative Byte gives different results in ScalaJs and Scala

Formatting of negative Byte gives different results in JVM and JS:
println(s"%02x".format(133.toByte))

JVM 85 vs JS ffffff85
Also applies to Short.
Introduced by 000fb141b309e7567f2458e32f003281122948a5. The commit also changed the unit tests to use incorrect values, so maybe there's a good reason behind this behavior. If it cannot be fixed, would be at least good to document, for example, in http://www.scala-js.org/doc/semantics.html.

Yes, it is as-designed. It is a consequence of "Runtime type tests are based on values" in the Semantics, though a non-obvious one. We should indeed document it.

Moved to an issue on the website to document the discrepancy. Closing here.


Excalidraw does not work with the Dark Reader plugin for dark mode, can it work with the Dark Reader plugin for dark mode?

Excalidraw has its own dark mode so it may be colliding. Either way, I'd suggest putting excalidraw.com into exclusion list and use our own instead. We support system theme as well (from top left menu).
What Dark Reader plugin are you using (what browser/ browser extension) and how are you toggling it the dark mode (using a keyboard shortcut)?

chrome used

The Chrome browser used

I've figured out how to adjust it, thank you for your reply.


Duplicated city labels

http://localhost:8080/flat/#9/17.8598/-98.4595
These cities fall right on a tile boundary, so they get labeled twice:

Actually, it's happening elsewhere. Here's one that's not on a tile boundary:

I think instead I need to increase shield-min-distance, perhaps? Actually, in 6d0fe2a54ff470e9ecd326398ed5c0f7303d97de I have shield-min-distance in there twice. Hmm.

Strange, I'll take a look later and see if I can replicate it.
On Friday, October 2, 2015, Alan McConchie<EMAIL_ADDRESS>wrote:

Actually, it's happening elsewhere. Here's one that's not on a tile
boundary:
[image: screen shot 2015-10-02 at 6 01 56 pm]
https://cloud.githubusercontent.com/assets/1212178/10260704/9a8c1610-6930-11e5-9394-9aaaa78ae460.png
I think instead I need to increase shield-min-distance, perhaps?
Actually, in 6d0fe2a
https://github.com/stamen/terrain-classic/commit/6d0fe2a54ff470e9ecd326398ed5c0f7303d97de
I have shield-min-distance in there twice. Hmm.
—
Reply to this email directly or view it on GitHub
https://github.com/stamen/terrain-classic/issues/35#issuecomment-145190814
.

--
-Chris L Henrick
MFA, Design & Technology
Parsons, The New School For Design
http://chrishenrick.com
Github: @clhenrick https://github.com/clhenrick Twitter:
@chrislhenrick https://twitter.com/chrislhenrick
“Whenever I see an adult on a bicycle, I no longer despair for the future
of the human race.”
— H.G. Wells

@almccon think this is resolved via cecbc0b could you verify on your end?


Force discovery of git repository in parent folder

VS Code recently made a change such that when you launch code from a subfolder it does not automatically load the git repository in the parent folder. This was done to prevent user confusion in some cases, and is discussed in more detail in the VS Code source control FAQ:
https://code.visualstudio.com/docs/sourcecontrol/faq#_why-isnt-vs-code-discovering-git-repositories-in-parent-folders-of-workspaces-or-open-files
Due to how our repository is structured, many folks working on azd launch code from within cli/azd (the root of the tree for the CLI) and this new setting means that you get a toast out of the box asking you if you want to load the repository or not. If you ignore this toast, the source control manager doesn't work (since VS Code doesn't assoicate the folder with the git repository in the parent).
We already have a settings.json in cli/azd/.vscode to support this type of workflow, so let's go ahead and set this value to say "yes, please load the repository in the parent for me" since this is the behavior we want.
While in the area, I sorted the settings in this file.

Azure Dev CLI Install Instructions
Install scripts
MacOS/Linux

May elevate using sudo on some platforms and configurations

bash:
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978 --version '' --verbose

pwsh:
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/uninstall-azd.ps1' -OutFile uninstall-azd.ps1; ./uninstall-azd.ps1
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/install-azd.ps1' -OutFile install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978' -Version '' -Verbose

Windows
PowerShell install
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/uninstall-azd.ps1' > uninstall-azd.ps1; ./uninstall-azd.ps1;"
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978' -Version '' -Verbose;"

MSI install
powershell -c "irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/azd-windows-amd64.msi' -OutFile azd-windows-amd64.msi; msiexec /i azd-windows-amd64.msi /qn"

Standalone Binary

Linux -

x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/azd-linux-amd64.tar.gz
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/azd-linux-arm64.tar.gz

MacOS -

x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/azd-darwin-amd64.zip
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/azd-darwin-arm64.zip

Windows - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/azd-windows-amd64.zip

MSI

https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1978/azd-windows-amd64.msi

Container
docker run -it azdevcliextacr.azurecr.io/azure-dev:pr-1978

Documentation

learn.microsoft.com documentation

title: Azure Developer CLI reference (preview)
description: This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
author: hhunter-ms
ms.author: hannahhunter
ms.date: 04/18/2023
ms.service: azure-dev-cli
ms.topic: conceptual
ms.custom: devx-track-azdevcli
Azure Developer CLI reference (preview)
This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
azd
The Azure Developer CLI (azd) is an open-source tool that helps onboard and manage your application on Azure
Options
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
  -h, --help         Gets help for azd.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth: Authenticate with Azure.
azd config: Manage azd configurations (ex: default Azure subscription, location).
azd deploy: Deploy the application's code to Azure.
azd down: Delete Azure resources for an application.
azd env: Manage environments.
azd init: Initialize a new application.
azd monitor: Monitor a deployed application.
azd package: Packages the application's code to be deployed to Azure. (Beta)
azd pipeline: Manage and configure your deployment pipelines.
azd provision: Provision the Azure resources for an application.
azd restore: Restores the application's dependencies.
azd template: Find and view template details.
azd up: Provision Azure resources, and deploy your project with a single command.
azd version: Print the version number of Azure Developer CLI.

azd auth
Authenticate with Azure.
Options
  -h, --help   Gets help for auth.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth login: Log in to Azure.
azd auth logout: Log out of Azure.
Back to top

azd auth login
Log in to Azure.
Synopsis
Log in to Azure.
When run without any arguments, log in interactively using a browser. To log in using a device code, pass
--use-device-code.
To log in as a service principal, pass --client-id and --tenant-id as well as one of: --client-secret,
--client-certificate, or --federated-credential-provider.
azd auth login [flags]

Options
      --check-status                           Checks the log-in status instead of logging in.
      --client-certificate string              The path to the client certificate for the service principal to authenticate with.
      --client-id string                       The client id for the service principal to authenticate with.
      --client-secret string                   The client secret for the service principal to authenticate with. Set to the empty string to read the value from the console.
      --federated-credential-provider string   The provider to use to acquire a federated token to authenticate with.
  -h, --help                                   Gets help for login.
      --redirect-port int                      Choose the port to be used as part of the redirect URI during interactive login.
      --tenant-id string                       The tenant id or domain name to authenticate with.
      --use-device-code                        When true, log in by using a device code instead of a browser.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth: Authenticate with Azure.
Back to top

azd auth logout
Log out of Azure.
Synopsis
Log out of Azure
azd auth logout [flags]

Options
  -h, --help   Gets help for logout.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth: Authenticate with Azure.
Back to top

azd config
Manage azd configurations (ex: default Azure subscription, location).
Synopsis
Manage the Azure Developer CLI user configuration, which includes your default Azure subscription and location.
Available since azure-dev-cli_0.4.0-beta.1.
The easiest way to configure azd for the first time is to run azd init. The subscription and location you select will be stored in the config.json file located in the config directory. To configure azd anytime afterwards, you'll use azd config set.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
Options
  -h, --help   Gets help for config.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config get: Gets a configuration.
azd config list: Lists all configuration values.
azd config list-alpha: Display the list of available features in alpha stage.
azd config reset: Resets configuration to default.
azd config set: Sets a configuration.
azd config unset: Unsets a configuration.
Back to top

azd config get
Gets a configuration.
Synopsis
Gets a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config get <path> [flags]

Options
  -h, --help   Gets help for get.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config list
Lists all configuration values.
Synopsis
Lists all configuration values in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config list [flags]

Options
  -h, --help   Gets help for list.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config list-alpha
Display the list of available features in alpha stage.
azd config list-alpha [flags]

Options
  -h, --help   Gets help for list-alpha.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config reset
Resets configuration to default.
Synopsis
Resets all configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable to the default.
azd config reset [flags]

Options
  -h, --help   Gets help for reset.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config set
Sets a configuration.
Synopsis
Sets a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config set <path> <value> [flags]

Examples
azd config set defaults.subscription <yourSubscriptionID>
azd config set defaults.location eastus

Options
  -h, --help   Gets help for set.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config unset
Unsets a configuration.
Synopsis
Removes a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config unset <path> [flags]

Examples
azd config unset defaults.location

Options
  -h, --help   Gets help for unset.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd deploy
Deploy the application's code to Azure.
azd deploy <service> [flags]

Options
      --all                   Deploys all services that are listed in azure.yaml
  -e, --environment string    The name of the environment to use.
      --from-package string   Deploys the application from an existing package.
  -h, --help                  Gets help for deploy.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd down
Delete Azure resources for an application.
azd down [flags]

Options
  -e, --environment string   The name of the environment to use.
      --force                Does not require confirmation before it deletes resources.
  -h, --help                 Gets help for down.
      --purge                Does not require confirmation before it permanently deletes resources that are soft-deleted by default (for example, key vaults).

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd env
Manage environments.
Options
  -h, --help   Gets help for env.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

Back to top

azd env get-values
Get all environment values.
azd env get-values [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for get-values.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env list
List environments.
azd env list [flags]

Options
  -h, --help   Gets help for list.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env new
Create a new environment.
azd env new <environment> [flags]

Options
  -h, --help                  Gets help for new.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env refresh
Refresh environment settings by using information from a previous infrastructure provision.
azd env refresh [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for refresh.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env select
Set the default environment.
azd env select <environment> [flags]

Options
  -h, --help   Gets help for select.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env set
Manage your environment settings.
azd env set <key> <value> [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for set.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd init
Initialize a new application.
azd init [flags]

Options
  -b, --branch string         The template branch to initialize from.
  -e, --environment string    The name of the environment to use.
  -h, --help                  Gets help for init.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment
  -t, --template string       The template to use when you initialize the project. You can use Full URI, <owner>/<repository>, or <repository> if it's part of the azure-samples organization.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd monitor
Monitor a deployed application.
azd monitor [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for monitor.
      --live                 Open a browser to Application Insights Live Metrics. Live Metrics is currently not supported for Python apps.
      --logs                 Open a browser to Application Insights Logs.
      --overview             Open a browser to Application Insights Overview Dashboard.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd package
Packages the application's code to be deployed to Azure. (Beta)
azd package <service> [flags]

Options
      --all                  Deploys all services that are listed in azure.yaml
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for package.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd pipeline
Manage and configure your deployment pipelines.
Options
  -h, --help   Gets help for pipeline.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd pipeline config: Create and configure your deployment pipeline by using GitHub or Azure Pipelines.
Back to top

azd pipeline config
Create and configure your deployment pipeline by using GitHub or Azure Pipelines.
azd pipeline config [flags]

Options
      --auth-type string        The authentication type used between the pipeline provider and Azure for deployment (Only valid for GitHub provider). Valid values: federated, client-credentials.
  -e, --environment string      The name of the environment to use.
  -h, --help                    Gets help for config.
      --principal-name string   The name of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-role string   The role to assign to the service principal. (default "contributor")
      --provider string         The pipeline provider to use (github for Github Actions and azdo for Azure Pipelines).
      --remote-name string      The name of the git remote to configure the pipeline to run on. (default "origin")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd pipeline: Manage and configure your deployment pipelines.
Back to top

azd provision
Provision the Azure resources for an application.
Synopsis
Provision the Azure resources for an application.
The command prompts you for the following values:

Environment name: The name of your environment.
Azure location: The Azure location where your resources will be deployed.
Azure subscription: The Azure subscription where your resources will be deployed.

Depending on what Azure resources are created, running this command might take a while. To view progress, go to the Azure portal and search for the resource group that contains your environment name.
azd provision [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for provision.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd restore
Restores the application's dependencies.
azd restore <service> [flags]

Options
      --all                  Restores all services that are listed in azure.yaml
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for restore.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd template
Find and view template details.
Options
  -h, --help   Gets help for template.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template list: Show list of sample azd templates.
azd template show: Show details for a given template.
Back to top

azd template list
Show list of sample azd templates.
azd template list [flags]

Options
  -h, --help   Gets help for list.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Find and view template details.
Back to top

azd template show
Show details for a given template.
azd template show <template> [flags]

Options
  -h, --help   Gets help for show.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Find and view template details.
Back to top

azd up
Provision Azure resources, and deploy your project with a single command.
azd up [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for up.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd version
Print the version number of Azure Developer CLI.
azd version [flags]

Options
  -h, --help   Gets help for version.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top