"az cosmosdb create" too many 503 error responses

This is autogenerated. Please review and update as needed.
Describe the bug
Error during cosmosdb create in West Central US.  Cosmos DB partially creates but the state is offline and Overview indicates Failed to refresh the collection list
Command Name
az cosmosdb create
Errors:
The command failed with an unexpected error. Here is the traceback:

Error occurred in request., RetryError: HTTPSConnectionPool(host='management.azure.com', port=443): Max retries exceeded with url: /subscriptions/[...]/resourceGroups/1st-sless-app/providers/Microsoft.DocumentDB/databaseAccounts/1stslessappdb/operationResults/[...]?api-version=2015-04-08 (Caused by ResponseError('too many 503 error responses',))
Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/opt/az/lib/python3.6/site-packages/urllib3/connectionpool.py", line 731, in urlopen
    body_pos=body_pos, **response_kw)
  File "/opt/az/lib/python3.6/site-packages/urllib3/connectionpool.py", line 731, in urlopen
    body_pos=body_pos, **response_kw)
  File "/opt/az/lib/python3.6/site-packages/urllib3/connectionpool.py", line 731, in urlopen
    body_pos=body_pos, **response_kw)
  File "/opt/az/lib/python3.6/site-packages/urllib3/connectionpool.py", line 711, in urlopen
    retries = retries.increment(method, url, response=response, _pool=self)
  File "/opt/az/lib/python3.6/site-packages/urllib3/util/retry.py", line 399, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='management.azure.com', port=443): Max retries exceeded with url: /subscriptions/eb290dda-cf74-40ab-926b-691ffc1957e7/resourceGroups/1st-sless-app/providers/Microsoft.DocumentDB/databaseAccounts/1stslessappdb/operationResults/93eb5f6a-0d66-4f7a-be15-ee416528e3dc?api-version=2015-04-08 (Caused by ResponseError('too many 503 error responses',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/msrest/universal_http/requests.py", line 137, in send
    **kwargs)
  File "/opt/az/lib/python3.6/site-packages/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/opt/az/lib/python3.6/site-packages/requests/sessions.py", line 646, in send
    r = adapter.send(request, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/requests/adapters.py", line 507, in send
    raise RetryError(e, request=request)
requests.exceptions.RetryError: HTTPSConnectionPool(host='management.azure.com', port=443): Max retries exceeded with url: /subscriptions/[...]/resourceGroups/1st-sless-app/providers/Microsoft.DocumentDB/databaseAccounts/1stslessappdb/operationResults/[...]?api-version=2015-04-08 (Caused by ResponseError('too many 503 error responses',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 523, in execute
    raise ex
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 581, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 574, in _run_job
    six.reraise(*sys.exc_info())
  File "/opt/az/lib/python3.6/site-packages/six.py", line 693, in reraise
    raise value
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 551, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 289, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/__init__.py", line 453, in default_command_handler
    return op(**command_args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/custom.py", line 87, in cli_cosmosdb_create
    docdb_account = async_docdb_create.result()
  File "/opt/az/lib/python3.6/site-packages/msrest/polling/poller.py", line 183, in result
    self.wait(timeout)
  File "/opt/az/lib/python3.6/site-packages/msrest/polling/poller.py", line 201, in wait
    raise self._exception  # type: ignore
  File "/opt/az/lib/python3.6/site-packages/msrest/polling/poller.py", line 152, in _start
    self._polling_method.run()
  File "/opt/az/lib/python3.6/site-packages/msrestazure/polling/arm_polling.py", line 390, in run
    self._poll()
  File "/opt/az/lib/python3.6/site-packages/msrestazure/polling/arm_polling.py", line 415, in _poll
    self.update_status()
  File "/opt/az/lib/python3.6/site-packages/msrestazure/polling/arm_polling.py", line 447, in update_status
    self._response = self.request_status(self._operation.location_url)
  File "/opt/az/lib/python3.6/site-packages/msrestazure/polling/arm_polling.py", line 470, in request_status
    return self._client.send(request, header_parameters, stream=False, **self._operation_config)
  File "/opt/az/lib/python3.6/site-packages/msrest/service_client.py", line 336, in send
    pipeline_response = self.config.pipeline.run(request, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/msrest/pipeline/__init__.py", line 197, in run
    return first_node.send(pipeline_request, **kwargs)  # type: ignore
  File "/opt/az/lib/python3.6/site-packages/msrest/pipeline/__init__.py", line 150, in send
    response = self.next.send(request, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/msrest/pipeline/requests.py", line 72, in send
    return self.next.send(request, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/msrest/pipeline/requests.py", line 137, in send
    return self.next.send(request, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/msrest/pipeline/__init__.py", line 150, in send
    response = self.next.send(request, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/msrest/pipeline/requests.py", line 193, in send
    self.driver.send(request.http_request, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/msrest/universal_http/requests.py", line 328, in send
    return super(RequestsHTTPSender, self).send(request, **requests_kwargs)
  File "/opt/az/lib/python3.6/site-packages/msrest/universal_http/requests.py", line 140, in send
    raise_with_traceback(ClientRequestError, msg, err)
  File "/opt/az/lib/python3.6/site-packages/msrest/exceptions.py", line 51, in raise_with_traceback
    raise error.with_traceback(exc_traceback)
  File "/opt/az/lib/python3.6/site-packages/msrest/universal_http/requests.py", line 137, in send
    **kwargs)
  File "/opt/az/lib/python3.6/site-packages/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/opt/az/lib/python3.6/site-packages/requests/sessions.py", line 646, in send
    r = adapter.send(request, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/requests/adapters.py", line 507, in send
    raise RetryError(e, request=request)
msrest.exceptions.ClientRequestError: Error occurred in request., RetryError: HTTPSConnectionPool(host='management.azure.com', port=443):Max retries exceeded with url: /subscriptions/[...]/resourceGroups/1st-sless-app/providers/Microsoft.DocumentDB/databaseAccounts/1stslessappdb/operationResults/[...]?api-version=2015-04-08 (Caused by ResponseError('too many 503 error responses',))

To Reproduce:
Issue the command:

az cosmosdb create -g {} -n {}

Expected Behavior
Successful creation of Cosmos DB
Environment Summary
Linux-4.15.0-1041-azure-x86_64-with-debian-stretch-sid
Python 3.6.5
Shell: bash

azure-cli 2.0.63

Additional Context

This looks like a temporary service issue and I was not able to repro. If you are still seeing this error, please reopen.

I still see the problem when I deploy a new Cosmos DB account. Deployed using an ARM template from PowerShell that indicated a successful deployment.

Partial deployment output without giving up too much info about environment:
    "mode": "Incremental",
    "provisioningState": "Succeeded",
    "timestamp": "2019-09-19T23:04:19.4101361Z",
    "duration": "PT23M3.5751283S",
    "correlationId": "78a0d6e9-41e9-4ccf-84f5-b32c07c43133",
    "providers": [
      {
        "namespace": "Microsoft.DocumentDB",
        "resourceTypes": [
          {
            "resourceType": "databaseAccounts",
            "locations": [
              "westus"
            ]
          }
        ]
      }
    ],

and
    "operationId": "CAAE9BA31E33805A",
    "properties": {
      "provisioningOperation": "Create",
      "provisioningState": "Succeeded",
      "timestamp": "2019-09-19T23:04:17.8095322Z",
      "duration": "PT22M55.9169518S",
      "trackingId": "3216843a-22d5-44ea-84ee-d50341eb84d3",
      "statusCode": "OK",


[Bug/Minor]: New Plugin Tool Items Disappear After Checking for Updates

Bug Description
The new buttons added in the "Community Plugins" tab disappear after you "check for updates".
Relevant Screenshot
Initially:

Then:

To Reproduce

Open the "Community Plugins" tab with D&C enabled.
Hit "Check for Updates".
The new buttons added will disappear.

Obsidian Version
1.0.4
Which editor are you using?

[X] New Editor
[ ] Legacy Editor

Checklist

[X] I updated to the latest version of the plugin.

This is something I ran into during development. Unfortunately, without increased reliance on obsidian internals I don't think it's possible to work around. You can bring the buttons back by simply clicking on the community tab again (even though you're already on it, it triggers a refresh).
This is something several other plugins suffer from, like the changelog plugin and the hotkeys plugin.

Alas, I did wonder if that were the case! Thanks for the great update!


NG: Specify path formats for StorageDriver implementation

We need to make a decision about ensuring paths used with the StorageDriver are absolute (rooted with a "/"). The issue here is that paths returned by the API differ based on how the driver likes to store them. Here is an example annoying test failure:
FAIL: /Users/sday/go/src/github.com/docker/docker-registry/storagedriver/testsuites/testsuites.go:436: DriverSuite.TestStatCall

/Users/sday/go/src/github.com/docker/docker-registry/storagedriver/testsuites/testsuites.go:457:
    c.Assert(fi.Path(), check.Equals, filePath)
... obtained string = "/qtbsaclradbgmdiytcwloabveajbeyhx/ggpaoucltdjjnskrjtmdzgmbejydtgiy"
... expected string = "qtbsaclradbgmdiytcwloabveajbeyhx/ggpaoucltdjjnskrjtmdzgmbejydtgiy"

OOPS: 0 passed, 1 FAILED
--- FAIL: Test (0.00s)

What should the driver do? Should it try to normalize the path? Should the paths in the failure above be equivalent? Do we need to provide functions for path comparison?
Much of the problems described above are avoided if we only allow absolute paths.
@BrianBland @AndreyKostov

We'll consider this closed for now. We may want to open a documentation bug in docker/distribution, but the bulk of the work is completed.


Release 0.1.1

Coverage remained the same at 97.94% when pulling 265c09c25562327048293e5be440c4f173d7dadc on 0.1.1 into 9a5a1dc60c8b62e02b83e6d36b9f4570ea522b21 on master.


Syntax errors causing BIG-IP <IP_ADDRESS>.0-1645 image testing overcloud connected to fail for health monitors

Title: Syntax errors causing BIG-IP <IP_ADDRESS>.0-1645 image testing overcloud connected to fail for health monitors
Attachments:

health_monitor_failures.txt

Details: Test failures due to syntax reference in health monitor testing

Agent Version
8.3.1
Operating System
CentOS 7
OpenStack Release
Liberty
Bug Severity
2 - this appears to be a syntax error in the tests themselves
Description
Continued repeat of:
buildbot@3e95f61b8a5a:~/f5-openstack-lbaasv2-driver/systest$ ___ ERROR at setup of TestHealthMonitors.test_create_health_monitor_empty_tenant_id_field ____
th_mbash: ___: command not found
buildbot@3e95f61b8a5a:~/f5-openstack-lbaasv2-driver/systest$ test_health_monitor_admin.py:53: in resource_setup
bash: test_health_monitor_admin.py:53:: command not found
buildbot@3e95f61b8a5a:~/f5-openstack-lbaasv2-driver/systest$     protocol='HTTP', protocol_port=80)
e_setup
bash: syntax error near unexpected token `)'
buildbot@3e95f61b8a5a:~/f5-openstack-lbaasv2-driver/systest$ base.py:215: in _create_listener
rotocol_porbash: base.py:215:: command not found
buildbot@3e95f61b8a5a:~/f5-openstack-lbaasv2-driver/systest$     cls._wait_for_load_balancer_status(cls.load_balancer.get('id'))
cbash: syntax error near unexpected token `cls.load_balancer.get'
buildbot@3e95f61b8a5a:~/f5-openstack-lbaasv2-driver/systest$ base.py:208: in _wait_for_load_balancer_status
se.py:bash: base.py:208:: command not found
buildbot@3e95f61b8a5a:~/f5-openstack-lbaasv2-driver/systest$     operating_status=operating_status))
tus
 bash: syntax error near unexpected token `)'
buildbot@3e95f61b8a5a:~/f5-openstack-lbaasv2-driver/systest$ E   TimeoutException: Request timed out
)
Ebash: E: command not found
buildbot@3e95f61b8a5a:~/f5-openstack-lbaasv2-driver/systest$ E   Details: Wait for load balancer ran for 60 seconds and did not observe 575ff7aa-837e-490e-9080-f73fcbc52ebb reach ACTIVE provisioning status and ONLINE operating status.
isionibash: E: command not found
buildbot@3e95f61b8a5a:~/f5-openstack-lbaasv2-driver/systest$  ERROR at setup of TestHealthMonitors.test_create_health_monitor_for_another_tenant_id_field _
bash: ERROR: command not found
buildbot@3e95f61b8a5a:~/f5-openstack-lbaasv2-driver/systest$ test_health_monitor_admin.py:53: in resource_setup
lth_bash: test_health_monitor_admin.py:53:: command not found
buildbot@3e95f61b8a5a:~/f5-openstack-lbaasv2-driver/systest$     protocol='HTTP', protocol_port=80)
sbash: syntax error near unexpected token `)`

Deployment
Standard testlab overstack connected with BIGIP-<IP_ADDRESS>.1645 image build.

@mattgreene @dflanigan, Sorry, this also applies to this bug as well... the syntax error is a fish that's striped due to a Makefile bug I had locally.  It just so happens to only have impacted these tests in a loop.


[Index] Don’t verify mangled names of declarations in invalid decl contexts

The added test case crashed because we were trying to verify the mangled name of the artifactID parameter, because the parameter is not marked as invalid. But the mangled name of that parameter contains the name of the enum case, which is invalid. Thus, the mangled name contained errors and didn’t pass verification.
To fix the crash, don’t verify mangled names in decl contexts that are invalid.
rdar://128092323

@swift-ci Please smoke test


[Event Request] Codeunit 99000757, Function UpdateUnitCostOnProdOrder

We need a new Publisher in Codeunit 99000757, Function UpdateUnitCostOnProdOrder:

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Support for Nodejs 18.18.2 as Nextjs 14.0.0 requires more than 18.17

          Hi everyone, we now have Node 18 available in the default Docker image for all builds! The version is pinned to `18.13.0`, which you can leverage by simply adding the `nvm use 18` command to your build spec.

Unfortunately, you will not be able to use Live Updates with Node 18 - So you will not be able to use any other minor/patch version of Node 18. This is because of a limitation with Amazon Linux 2, where Node 18 needs to be built from source. We have however built 18.13.0 from source and baked that into the image.
If you need any other minor/patch version of Node 18, please install it from source like so:
nvm install -s 18.x.x

Please note though that this will increase your build time.
Originally posted by @Narrator in https://github.com/aws-amplify/amplify-hosting/issues/3109#issuecomment-1509264093

https://github.com/vercel/next.js/issues/57214 refer to this @Narrator

Hi @adarsh-drishya 👋 , thanks for raising this!
We are actively working on supporting Next 14 based apps on Amplify Hosting. Today, our compute runtime for SSR apps uses Node 16 by default and we are tracking this breaking change for Next 14 and are working on supporting Node 18 in the runtime.
We will keep you posted with any updates on this thread.

Hi @adarsh-drishya 👋 , thanks for raising this!
We are actively working on supporting Next 14 based apps on Amplify Hosting. Today, our compute runtime for SSR apps uses Node 16 by default and we are tracking this breaking change for Next 14 and are working on supporting Node 18 in the runtime.
We will keep you posted with any updates on this thread.

Node 16 is no longer maintained anyways, node 18 better be default. Thanks

As of last week, the v20 has entered LTS. Is that compatible with Amazon Linux 2023 and available through nvm?

@theo-staizen I believe not - I've been able to work around limitations on the default build image (AWS's Amazon Linux 2), but the runtime still runs on node 16, and there seems to be no way to customize that.
If anyone's been able to find a way around this please share!

Hi @adarsh-drishya 👋 , thanks for raising this!
We are actively working on supporting Next 14 based apps on Amplify Hosting. Today, our compute runtime for SSR apps uses Node 16 by default and we are tracking this breaking change for Next 14 and are working on supporting Node 18 in the runtime.
We will keep you posted with any updates on this thread.

Why not just use node 20, its the LTS not node 18

Hey @Jay2113, is it possible to get any indication as to when support for node 18/20 will be released? Just a general idea if we're talking about days, weeks or months.
If not, I'll need to start to hack around the problem to get my application deployed again, which for obvious I would rather not do 😛
Thanks and have a great week! ✨

Hi @adarsh-drishya 👋 , thanks for raising this!
We are actively working on supporting Next 14 based apps on Amplify Hosting. Today, our compute runtime for SSR apps uses Node 16 by default and we are tracking this breaking change for Next 14 and are working on supporting Node 18 in the runtime.
We will keep you posted with any updates on this thread.

+1

+1
We are also really waiting for node >18.17 support for NextJS 14. 😬

+1

+1

+1

+1

+1

Hey folks! Here is the working solution: https://github.com/aws-amplify/amplify-hosting/issues/3779#issuecomment-1789305362

@CoDanny at least I was able to get the app running back again. Sure it has to be fixed, but as a prelimenary solutioin I think it is worth trying.

@tarasowski some apps might work. However, the runtime node is not 18 so you can expect runtime errors  for sure. You might not have hit them yet or you app happens to not use the features that touch them but I would advise people to wait until the amplify team moves the runtime before updating to next 14

Hi All (@tarasowski, @CoDanny , @adarsh-drishya) - The runtime environment has been updated to support Node 18.
To deploy, use a custom build image with Node v18.17. The hosting compute runtime will use the corresponding version of Node used to build the application. An example image to test/use with is: public.ecr.aws/docker/library/node:18.17.0.
We are prioritizing an update to the build image that will remove this custom image dependency.

Hi All (@tarasowski, @CoDanny , @adarsh-drishya and others) 👋🏻 - The runtime environment has been updated to support Node 18.
To deploy, use a custom build image with Node v18.17. The hosting compute runtime will use the corresponding version of Node used to build the application. An example image to test/use with is: public.ecr.aws/docker/library/node:18.17.0.

@siegerts it only works with node 18.17.0 doesn't it? I just tried with node 20.9.0 and got the following error in the deploy step:

@stefanofa Yes, correct. Currently, to Node 18.

Can confirm too that I am able to deploy my application with NextJS 14 now, after sorting our some other build issues! Thanks @siegerts ❤

Can anyone share their amplify.yaml please? I understand the part when it is necessary to use public.ecr.aws/docker/library/node:18.17.0 as a base image. When should we npm -i -g @aws-amplify/cli? is it prebuild phase or / build / frontend / etc. Or all?
Context of my issue: https://github.com/aws-amplify/amplify-hosting/issues/3779#issuecomment-1792985986

It'd be great to see 18.18.2 available, not just 18.17.0. There are few closed CVEs in 18.17.0, according to release notes.

It'd be great to see 18.18.2 available, not just 18.17.0. There are few closed CVEs in 18.18.2, according to release notes.

@kachkaev I tried using version 18.18.2 and the build was successful. However, I am not sure whether the runtime used after deployment is actually 18.18.2 or 18.17.0.

@stefanofa, good to know! How did you get @aws-amplify/cli when using<EMAIL_ADDRESS>That's the only combination of versions that work for me in build image settings:

Bumping any of these versions leads to build failure.

@kachkaev I'm not sure it will work, but have you tried removing the Amplify CLI version override?
I'm just using the following config:

However, I do not have a backend environment associated with the app on amplify, so if you do, the problem may depend on that.

Yeah I tried removing overrides, but then I get this warning when building backend:
[WARNING]: /codebuild/output/src123/src/my-project/amplify.sh: line 45: amplify: command not found

and then this error when building frontend (next.js app):
Module not found: Can't resolve '../../aws-exports'

(this refers to ./src/aws-exports.js)
I guess that lack of @amplify/cli during build means that amplify pull --appId ... does not run and therefore the file with credentials is missing.
That is healed when I define Amplify CLI override with build settings but it only works for Node 18.13.0 as base image and Amplify CLI 12.5.2. Bumping any of these breaks the build 🤷

I had a setup working just fine earlier this week running Node.js 20 for both the Build and Deploy using a custom build image (node:20-bullseye), but now it is broken. This is pretty frustrating.

I had a setup working just fine earlier this week running Node.js 20 for both the Build and Deploy using a custom build image (node:20-bullseye), but now it is broken. This is pretty frustrating.

@casewalker the compute may have been defaulting to Node 16 in that case since 20 is/was not available. So your build was running with 20, but the runtime compute was 16. Is it possible to bump down to 18 as mentioned above and try? Also is this with Next 14?

@casewalker the compute may have been defaulting to Node 16 in that case since 20 is/was not available. So your build was running with 20, but the runtime compute was 16. Is it possible to bump down to 18 as mentioned above and try? Also is this with Next 14?

I am almost certain it was not running on 16, that it was indeed running on Node 20. Firstly, I am using Node's builtin fetch (without having node-fetch installed or imported), and this was only introduced in Node 18. Secondly, I have defined my engine to be >=20 in my package.json and I have the line engine-strict=true in .npmrc.
I deployed this code without issue earlier this week, and now with identical code (only updating unrelated environment variables) it fails on the deploy stage stating that Node 20 is not supported. So it seems pretty conclusive to me that I was able to run Node 20 previously (and it is still running because the new deploy failed), and now I cannot.
I can probably downgrade to Node 18. But why shouldn't Amplify support the Node 20 runtime?

@casewalker Thanks for following up. Do you mind opening a new issue with this information? That way we have all of the information regarding your app to investigate.

@casewalker the compute may have been defaulting to Node 16 in that case since 20 is/was not available. So your build was running with 20, but the runtime compute was 16. Is it possible to bump down to 18 as mentioned above and try? Also is this with Next 14?

I am almost certain it was not running on 16, that it was indeed running on Node 20. Firstly, I am using Node's builtin fetch (without having node-fetch installed or imported), and this was only introduced in Node 18. Secondly, I have defined my engine to be >=20 in my package.json and I have the line engine-strict=true in .npmrc.
I deployed this code without issue earlier this week, and now with identical code (only updating unrelated environment variables) it fails on the deploy stage stating that Node 20 is not supported. So it seems pretty conclusive to me that I was able to run Node 20 previously (and it is still running because the new deploy failed), and now I cannot.
I can probably downgrade to Node 18. But why shouldn't Amplify support the Node 20 runtime?

I have to agree with what was said here. I'm pretty sure I was running 20.8.0 previously last week. Here's my screenshot to prove it:

Now when I try to redeploy this exact same version I get this error:

There was somekind of validation added to the deploy phase of AWS Amplify. Why was that necessary? I'm slightly annoyed because our app was suppose to go live after this weekend.

@casewalker & @em1l1000, are these Next 14 apps?
The update that I posted was above is in reference to the Node 18 compute runtime requirement from Next 14. If these were Next apps <14 than then may have been building with Node > 16 but the execution in the compute runtime was using Node 16. This stopped working with Next 14 since the the minimum required versions bumped as per this issue title. Previously, there was not building/runtime environment matching - it was Node 16 by default.
As per @Jay2113's comment initially -

Today, our compute runtime for SSR apps uses Node 16 by default and we are tracking this breaking change for Next 14 and are working on supporting Node 18 in the runtime.

@em1l1000, this new validation is trying to match the build and compute runtimes with a compatible/supported Node version. This is now throwing the Error with 20 since you are using Node 20 in your build but that is not supported yet as a version in the compute runtime.
In both scenarios, although the build may have been using a different version of Node, the compute runtime for SSR apps was using Node 16 by default.
I hope that this helps. For Node 20 support I have opened a separate feature request to track -https://github.com/aws-amplify/amplify-hosting/issues/3785 .

@casewalker & @em1l1000, are these Next 14 apps?
The update that I posted above is in reference to the Node 18 compute runtime requirement from Next 14. If these were Next apps <14 than they may have been building with Node > 16 but the execution in the compute runtime was using Node 16 - this could be checked by logging out the Node version during SSR compute to the CloudWatch log stream. This stopped working with Next 14 since the the minimum required versions bumped as per this issue title. Previously, there was not building/runtime environment matching - it was Node 16 by default for the runtime.
As per @Jay2113's comment initially -

Today, our compute runtime for SSR apps uses Node 16 by default and we are tracking this breaking change for Next 14 and are working on supporting Node 18 in the runtime.

@em1l1000, this new validation is trying to match the build and compute runtimes with a compatible/supported Node version. This is now throwing the Error with 20 since you are using Node 20 in your build but that is not supported yet as a version in the compute runtime.
In both scenarios, although the build CI/CD may have been using a different version of Node, the compute runtime for SSR apps was using Node 16 by default.
I hope that this helps. For Node 20 support I have opened a separate feature request to track -#3785 .

I'm running version 13.5.6. I actually tried to upgrade to 14 last week but ran into this issue:

This error only occurred during runtime (the build and deploy didn't show any error). I was asking the guys in the next.js discord channel why this was happening and they said that it's because of my node version that's outdated. But I was confused because this node version I'm using (20.8.0) is fairly recent so I was showed them exactly what I'm showing you in my post right up here ==> my docker is running 20.8.0. I then reverted back to 13.5.6 because I couldn't figure out what was wrong. We're one week later and I now understand that this is the AWS Amplify compute runtime that's apparently using node v16 by default.
Couple of comments:

It would be nice if there was some mechanism to drive the compute runtime version.
Also, I couldn't find any documentation on this. It's through the posts here that I learned that there's a difference between build time and run time node version.

I have used a custom image 18.17.0 but my build is still failing with Module not found: Can't resolve '../src/aws-exports' .  I guess I would love to see someone's amplify.yml with a backend.  Here is mine:
version: 1
backend:
phases:
build:
commands:
- curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
- unzip awscliv2.zip
- ./aws/install
- '# Execute Amplify CLI with the helper script'
- npm install -g @aws-amplify/cli
- amplifyPush --simple
- amplify version
frontend:
phases:
preBuild:
commands:
- aws codeartifact login --tool npm --repository academy --domain skillquest --domain-owner XXXXXXXXXX --region us-east-1
- npm ci
- echo "# Running frontend build" > .env
- echo "NEXT_PUBLIC_CLOUDFRONT_COOKIE_DOMAIN=$NEXT_PUBLIC_CLOUDFRONT_COOKIE_DOMAIN" >> .env
build:
commands:
- npm run build
artifacts:
baseDirectory: .next
files:
- '/*'
cache:
paths:
- node_modules//*
  Everything runs fine on the backend but during the frontend build I get.

023-11-04T23:12:22.115Z [INFO]: # Completed phase: preBuild
# Starting phase: build
# Executing command: npm run build
2023-11-04T23:12:22.330Z [INFO]: > build
> next build
2023-11-04T23:12:22.905Z [INFO]: ⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
2023-11-04T23:12:22.911Z [INFO]: Attention: Next.js now collects completely anonymous telemetry regarding usage.
2023-11-04T23:12:22.911Z [INFO]: This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
2023-11-04T23:12:23.004Z [INFO]: ▲ Next.js 14.0.1
2023-11-04T23:12:23.005Z [INFO]: - Environments: .env
2023-11-04T23:12:23.005Z [INFO]: Creating an optimized production build ...
2023-11-04T23:13:08.308Z [WARNING]: Failed to compile.
2023-11-04T23:13:08.313Z [WARNING]: ./api/apolloClient.js
Module not found: Can't resolve 'src/aws-exports'
https://nextjs.org/docs/messages/module-not-found

@shawnseaton any success with these versions  - https://github.com/aws-amplify/amplify-hosting/issues/3773#issuecomment-1793149762

@shawnseaton any success with these versions - #3773 (comment)?

I tried limiting Amplify to 12.5.2 like in the referenced comment (I can't limit to node 18.13 as I need at least 18.17 for Next 14 support) and it still received the same error message.  It is like
- amplifyPush --simple
is not generating the amplify aws-exports for the backend environment.

I created a custom build image and built&deployed it from Amplify and succeeded in running Next.js14 with Amplify Hosting.
Dockerfile of build image looks like this
FROM amazonlinux:2023

RUN dnf install -y tar gzip unzip git

# aws-cli
RUN curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
RUN unzip awscliv2.zip
RUN ./aws/install

# nvm
RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash

# node
RUN . ~/.nvm/nvm.sh && nvm install 18.17.0

RUN echo -e "\
export NVM_DIR=\"\$HOME/.nvm\"\n\
[ -s \"\$NVM_DIR/nvm.sh\" ] && \. \"\$NVM_DIR/nvm.sh\"\n\
" >> ~/.bashrc

ENTRYPOINT [ "/bin/bash" ]

After building the Dockerfile and pushing it to public ECR, I specified it in the build image of amplify and built & deployed it.

The amplify.yml did not need to be changed in any particular way
version: '1.0'
applications:
  - appRoot: frontend
    frontend:
      phases:
        preBuild:
          commands:
            - npm ci
        build:
          commands:
            - npm run build
      artifacts:
        baseDirectory: .next
        files:
          - '**/*'
      cache:
        paths:
          - node_modules/**/*
          - .next/cache/**/*

Am using Nextjs 14.0.1 , even though it requires   node: '>=18.17.0' , it still deployed  for me using the node 18.13 public image public.ecr.aws/docker/library/node:18.13.0 and haven't run into any errors yet

In stead of using nvm or installing different versions, of node would a better fix be to have a newer default images available for amplify like Amazon Linux 2023/2024

Thanks @siegerts for continuing to track this issue. I posted a related question on Discord here.

I finally got it working with Next.js 14.0.1 and Node 18.18.2.  Thanks to @AkihiroTakamura for setting me in the right direction.  I needed to also install amplify to get the backend working (Auth/GraphQL APIs that I already had before) so I modified the dockerfile to this:
`FROM amazonlinux:2023
RUN dnf install -y tar gzip unzip git
aws-cli
RUN curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" &&
unzip awscliv2.zip &&
./aws/install
nvm and node
RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
Install node, npm and the global package
RUN echo 'export NVM_DIR="$HOME/.nvm"' >> $HOME/.bashrc &&
echo '[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"' >> $HOME/.bashrc &&
echo '[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"' >> $HOME/.bashrc &&
. $HOME/.nvm/nvm.sh &&
nvm install 18.18.2 &&
npm install -g @aws-amplify/cli
Start bash with NVM loaded
ENTRYPOINT [ "/bin/bash", "--login" ]`
and then uploaded to ECR public as suggested.
Then I changed my build settings to point to this container image in ECR public.
public.ecr.aws/<your_alias>/node:18.18.2
All is now working! Thank you guys!

Glad that you have found a working solution @shawnseaton!
While a custom docker image technically works, it’s too tedious to set up in each team for such a trivial need as running Next.js. This is a very popular framework, so I wish that Amplify team prioritises its built-in support for all of us. Hope that we can all benefit from the solution you have shared, just via an official image of some sort.
Amplify team, please find resources to resolve this problem – it’s quite massive given the popularity of Next.js 🙏

I finally got it working with Next.js 14.0.1 and Node 18.18.2. Thanks to @AkihiroTakamura for setting me in the right direction. I needed to also install amplify to get the backend working (Auth/GraphQL APIs that I already had before) so I modified the dockerfile to this:
`FROM amazonlinux:2023
RUN dnf install -y tar gzip unzip git
RUN curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" && unzip awscliv2.zip && ./aws/install
RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
RUN echo 'export NVM_DIR="$HOME/.nvm"' >> $HOME/.bashrc && echo '[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"' >> $HOME/.bashrc && echo '[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"' >> $HOME/.bashrc && . $HOME/.nvm/nvm.sh && nvm install 18.18.2 && npm install -g @aws-amplify/cli
ENTRYPOINT [ "/bin/bash", "--login" ]`
and then uploaded to ECR public as suggested.
Then I changed my build settings to point to this container image in ECR public.
public.ecr.aws/<your_alias>/node:18.18.2
All is now working! Thank you guys!

I tried the same and i get  the below error in provision phase
[SINGLE_BUILD_CONTAINER_DEAD: Build container found dead before completing the build. Build container died because it was out of memory, or the Docker image is not supported]

Just want to say thanks for the quick turnaround on supporting v18 and Next.js 14. After lots of tinkering, I've got everything working at our org.
That being said, it seems like there are many issues with AWS Amplify that are deeply concerning. The fact that the node LTS release was not supported for so long is a little ridiculous. Hopefully AWS can add support for node 20 in a more reasonable timeframe. Issues like this make Amplify feel like an afterthought, has AWS decided that it is not viable as a product and moved it into minimal maintenance?
We would like to invest further in Amplify as it's a pretty good fit for what we're doing, but it's dubious right now whether it's a smart place to put our money.

Reading about the problems installing nodejs 18.17.0 on Amazon Linux 2, I also decided to create a custom image, like @AkihiroTakamura .
I took this as my base Dockerfile and adapted it as necessary.  One could also take the Dockerfile from the provision step of an Amplify build in the AWS Console.

I finally got it working with Next.js 14.0.1 and Node 18.18.2. Thanks to @AkihiroTakamura for setting me in the right direction. I needed to also install amplify to get the backend working (Auth/GraphQL APIs that I already had before) so I modified the dockerfile to this:
FROM amazonlinux:2023 RUN dnf install -y tar gzip unzip git RUN curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" && unzip awscliv2.zip && ./aws/install RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash RUN echo 'export NVM_DIR="$HOME/.nvm"' >> $HOME/.bashrc && echo '[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"' >> $HOME/.bashrc && echo '[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"' >> $HOME/.bashrc && . $HOME/.nvm/nvm.sh && nvm install 18.18.2 && npm install -g @aws-amplify/cli ENTRYPOINT [ "/bin/bash", "--login" ]
and then uploaded to ECR public as suggested.
Then I changed my build settings to point to this container image in ECR public.
public.ecr.aws/<your_alias>/node:18.18.2
All is now working! Thank you guys!

I tried the same and i get the below error in provision phase
[SINGLE_BUILD_CONTAINER_DEAD: Build container found dead before completing the build. Build container died because it was out of memory, or the Docker image is not supported]

The reason that it is failing is that you built an ARM image on your Apple Silicon Mac.  You need to build an Intel image with this command.
docker build . --platform linux/amd64

@

I finally got it working with Next.js 14.0.1 and Node 18.18.2. Thanks to @AkihiroTakamura for setting me in the right direction. I needed to also install amplify to get the backend working (Auth/GraphQL APIs that I already had before) so I modified the dockerfile to this:
FROM amazonlinux:2023 RUN dnf install -y tar gzip unzip git RUN curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" && unzip awscliv2.zip && ./aws/install RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash RUN echo 'export NVM_DIR="$HOME/.nvm"' >> $HOME/.bashrc && echo '[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"' >> $HOME/.bashrc && echo '[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"' >> $HOME/.bashrc && . $HOME/.nvm/nvm.sh && nvm install 18.18.2 && npm install -g @aws-amplify/cli ENTRYPOINT [ "/bin/bash", "--login" ]
and then uploaded to ECR public as suggested.
Then I changed my build settings to point to this container image in ECR public.
public.ecr.aws/<your_alias>/node:18.18.2
All is now working! Thank you guys!

I tried the same and i get the below error in provision phase
[SINGLE_BUILD_CONTAINER_DEAD: Build container found dead before completing the build. Build container died because it was out of memory, or the Docker image is not supported]

The reason that it is failing is that you built an ARM image on your Apple Silicon Mac. You need to build an Intel image with this command.
docker build . --platform linux/amd64

Thanks man, that worked,
But what are your build settings

version: '1.0'
applications:
  - appRoot: frontend
    frontend:
      phases:
        preBuild:
          commands:
            - npm ci
        build:
          commands:
            - npm run build
      artifacts:
        baseDirectory: .next
        files:
          - '**/*'
      cache:
        paths:
          - node_modules/**/*
          - .next/cache/**/*

?? same as above

Hi All 👋🏻 - Just to follow up again -
The Amazon Linux 2023 (AL2023) build image is now available in the Edit build image settings. This will remove the need for the custom build image workaround from above. You can select this as the image for your Next 14 apps instead.


[SwiftASTContext] Hoist LoadOneModule.

This way we can call it from other context(s).

@swift-ci please test and merge


Attempting to attach a system clock monitor fails on Linux

When calling sol_platform_add_system_clock_monitor() I get
WRN:sol-platform ./src/lib/common/sol-platform-linux-common.c:844 sol_platform_register_system_clock_monitor() Could not register a timer to watch for system_clock changes.
WRN:sol-platform ./src/lib/common/sol-platform.c:552 monitor_add_and_register() r (-22) < 0

I'm running Fedora 21 32-bit with kernel 4.1.13-100.fc21.i686.

32bits issue. Thanks for pointing.
Check proposed fix in PR #1354

The fix is not merged. Check: fc2efe4af2476488a62b85216aa08e072b0cae6f


Shall IRIs start with http or https?

What is the best practise for IRIs? Shall we have https://serlo.org/1495 or http://serlo.org/1495?

IMHO: https since http links just look wrong in my opinion ;) From my quick research, both approaches are fine and used, so 🤷♂

I have started a question on SO about this: https://stackoverflow.com/questions/70403827/iris-shall-http-or-https-be-used ...

https://stackoverflow.com/a/70404017/1165155 -> we are fine with https


Iris's load and load_cubes utilities return a CubeList with its elements in random order

When loading a dataset that has multiple cubes, load() and load_cubes() will return a CubeList with its elements in random order. This makes it harder for following code to be reproducible: indexing into the list isn't guaranteed to always provide the same cube.
Perhaps there is a good reason CubeList is inherently unordered, but since list (from which it derives) is inherently ordered, I feel it's better to have it be ordered, so that there are no surprises.

The cause seems to in the iris.fileformats.netcdf.load_cubes function, where it calls the .values() method of the various CFGroup objects.
One solution could be (untested) to make CFGroup._cf_variables a collections.OrderedDict (and perhaps the other attributes of CFGroup as well).
Potentially, this may also apply for various other dicts, or even the MutableMapping base class of CFGroup.

I'd assert this is a feature not a bug – CubeLists are, and should be expected to be, unordered (think pre-Python 3.6 dictionary keys). If you wish to reproducibly select a cube from the CubeList you should use a Constraint that's defined by metadata of interest and extract from the CubeList using that Constraint. This is a generally more robust approach than indexing.

Ah, right. I got thrown off by its name and parent class (list), and of course methods like append and insert are inherently ordered. I guess it's more a multi-set type of class.
Thanks, I'll use the constraint route.

Hmmm, I think once loaded cubelists are ordered aren't they?  If I do:
new_cubelist = iris.cube.Cube([cube.collapsed('foo', iris.analysis.MEAN) for cube in old_cubelist])

then I can expect the order in my new cubelist to be consistent with the old.
However, I think I'd always be nervous about assuming a particular order in a freshly loaded cube, regardless of how iris.load is written.  What happens if another process changed your NetCDF file on disk since you last used it?

Thanks @evertrol for this issue. Much appreciated! :+1:
We've never intended the Cubes within a CubeList to in any specific order. This was a design choice from outset of iris, and we'd be hesitant to enforce an ordering - simply because there is no obvious way to do it in a way that everyone would agree with.
So the deal is that you can't rely on any particular ordering - if you consider it random, then that's a pretty safe assumption to make. We've left the ordering down to the user to decide, if that matters to them, post loading. As @DPeterK mentioned, use a constraint to refine and extract the cubes that you care about, rather than indexing - indexing is a very weak contract, there is no guarantee that the same cube will be at the same index when comparing independent loads of the same file/s.
@evertrol If you don't mind, I'm going to close this issue. However, if you feel that you want to re-open it as a means to force an open discussion on Cube ordering within a CubeList, then please do so, and the community will take it from there :smile:

Not a problem having this issue closed. It's mostly arguing semantics, and I wouldn't expect to see an API change/rename. As DPeterK remarks, it's mostly a dict keys style (or dict values, if items can be repeated).
Is it worth to put a remark in the documentation about it, either (or both) at the main reference documentation page or the load_cubes() reference documentation?

@evertrol Thanks.
That seems like a happy compromise to me, so I'm going to re-open this issue with the task of updating the documentation and/or doc-strings to highlight the orders of cubes returned within a CubeList so that it isn't a surprise to users.

This has been addressed in @stephenworsley 's PR: #3370 so I'm going to close this issue

Hiya all - see this issue is closed (and reasoning above). See also that the docs are nicely explicit about lack of inherent order.
However... is there any option/feeling re option of adding a keyword to iris.load such that a user can get a sorted list out if iris.load ends up returning a cube list ?
Straw API
cube_list = iris.load(my_file.nc, sort_order=<something>)
where  could be (say) one of following:

a set of common keywords (e.g. ["alphabetical", ...])
an option for (say) a user-defined function to determine this (with docs giving some sample functions implementing say alphabetical based on cube.name, reverse alphabetical, field size in bytes, ...)
other?

Whichever of these is used, there could be a default sort_order=None (or similar) default to preserve the current unsorted behaviour as default.
Use-case for this:
I'm trying to use a notebook to document development of scripts to wrangle some ~nasty data which results in a cube list.
Notebooks of course not natively the best for diffing generally (thanks to several of you I know there are lots of tools to help with this!).
But in this case the cubelist being unordered adds needless extra diff line noise I could do without, and quite a lot of it as I'm using html-formatted output.
Not a major issue - but enough of a niggle that I thought worth poking this issue.
Cons
Realise there may be a -1 (more?) aspect in that anything like this may encourage people to index in to the sorted cubelist. Leading to opaque code etc. I hereby solemnly swear never to!.
Moot, but FWIW I do agree as with original poster that this is a bit of a gotcha given list in CubeList name, especially as you can even ~rely on dicts' sort order!
Overall
IMO would be nice if there were a ~easy option to allow sorting for use-cases like this. Perhaps by making the default unsorted it wouldn't become something people would rely on too much (indexing etc), but could be opted into by those who need it.

Could you sort your CubeList yourself after loading? For example:
cubes.sort(key=lambda cube: cube.var_name)

Definitely! Perfect, thanks Jon! For my use-case this makes my request ignorable, as I can sort after loading but before printing.


One azurite storage is used by every connector.

Bug Report
Describe the Bug
Instead of having one unique azurite for every connector.
When creating one storage azurite for every connector in the following way:
azuriteX:
    container_name: azuriteX
    image: mcr.microsoft.com/azure-storage/azurite
    ports:
        - 1000X:10000
    environment:
        AZURITE_ACCOUNTS: companyXassets:keyX

When transfer is starting there are an error in the way due to following explication.

Consumer connector: if bucket is not created yet then will be created.
Provider connector: gets its own file
Provider connector: tries to put the file in consumer bucket (thinking that is located in local azurite, that´s wrong because azurite storages are different located)
Consumer connector: loops indefinitely waiting for file to be storaged in its own bucket, this will never occur.

Expected Behavior
Provider connector gives the content of the file to consumer connector and this one puts the file/content wherever it desires, not expecting for provider connector to put the file somewhere.
Observed Behavior
Mentioned before.
Steps to Reproduce
Mentioned before.
Context Information

OS: Ubuntu 20.04.5 LTS
WebBrowser used: Firefox, the last one at the moment to write this issue.

Detailed Description
Mentioned before.
Possible Implementation
Provider connector gives data/file/content/etc to consumer connector and this last one saves data/file/content/etc wherever it desires.

@aramirezarsys That is definitely not a bug, but was done to keep things simple at the beginning. The value that multiple azurite instances would provide was deemed insignificant compared to the increased deployment and testing complexity.
You are definitely welcome to contribute a more elaborate solution with multiple instances, we'd be happy to have it. However, be advised that that could also affect the testing.


Inference on single video

Hi,
Thank you for your work. I'm making code to allow for easy testing of caption generation on user videos. Can you tell me how I can generate captions for my own videos?
What features are required? is there a feature generation code I can use? what is the command to run inference on my own videos?
Thanks

Hi @nikky4D ,
Thanks for your interest in our work! To generate captions for videos from ActivityNet Captions:
bash scripts/translate_greedy.sh anet_re_init_2019_10_01_11_34_22 val

as described in https://github.com/jayleicn/recurrent-transformer#inference-with-pre-trained-model. To generate captions for user videos, you may follow a similar procedure, but need t to provide corresponding files.
The features used for our model is provided by https://github.com/salesforce/densecap#annotation-and-feature, the feature extraction code is inside this repo https://github.com/LuoweiZhou/anet2016-cuhk-feature. You may find more details there.
 I am also happy to help! : )
Best,
Jie

Hey @jayleicn
Thanks for providing the info, however, the repo you linked https://github.com/LuoweiZhou/anet2016-cuhk-feature, doesn't have clear instructions on how to extract the features. Is it possible for you to provide some help here?

Sorry, I did not extract the features myself so I am not able to confidently reply to your request. You may ask the original authors for clear instructions.

@amil-rp-work  did you succeed running inference on a single video? If yes can you please share me some details on what should I do to run inference on single video(my video)?

@DesaleF Hi, I have ran inference on a single video. You can do it by following steps:

Refer to the format of the annotation of anet to mark the start and end point of the event in your video.
Refer to the code anet2016-cuhk and anet2016-cuhk-feature to extract the features of your video.
Run the pre-trained model on the extracted features to generate the caption.

@wanghao14  Thank you very much! I followed your steps and now I extracted the features. But I couldn't find any pretrained model on this repo. did you train by yourself or get pretrained model somewhere? if you train the model, could you please share the trained model?
Also the feature extraction code from anet2016-cuhk-feature doesn't work for me out of the box. I did some tweak and it worked but still for some video it fails to extract the feature.

@DesaleF
did you succeed running inference on a single video? If yes can you tell me where can I find the pretrained model ?


console: figure out parent/child spans should be displayed

While #9 is more focused on the data collection side of things, this issue is concerned with how parent/child relationships should be rendered in the console. Possible approaches:

@hawkw suggests that something like htop's tree mode would be useful.
being able to dynamically highlight an individual task and view its tree would be also helpful, as @tobz suggested.

Some inspiration:

htop tree mode:

pstree(1):

tracing-tree:

reqray:

Jaeger tree + timeline view:

I think a tree-mode would probably end up being a different view mode from the top(1)-style task list view we have currently. It would also be nice to have a way to highlight one task in the list view and see just its parent context, which we could add to the current view pretty easily, I think. Might be good to start with that before writing a tree-mode?

A timeline view would definitely be awesome, but maybe for the MVP we start by showing the "current state" as a backtrace type view and go from there?

A timeline view would definitely be awesome, but maybe for the MVP we start by showing the "current state" as a backtrace type view and go from there?

yup, that's what i'm thinking as well. now that #13 gave us the ability to highlight individual tasks in the top tasks view, we have a nice way to select a task and expand it to show the full context.
tree and timeline views would be really nice to have in a future iteration!


Extend wordlist to have different kinds of words

Must be able to look up the kind of a word.

unknown / other
noun, singular
noun, plural
verb

Can be build with:
https://wordnet.princeton.edu/download/current-version

Currently looking at using a model because wordnet covers about 15% of the Contextionary.

Closing as obsolote.


Crop the middle of an image

How do you crop the centre of an image using jimp into a square?
I tried the following:
userBanner.crop(userBanner.bitmap.width / 2 , userBanner.bitmap.height / 2, bg.bitmap.width, bg.bitmap.height)
Though it returned an error, is there a correct way to do it?

UP!
I have the same problem.
I try to cut a 1920x1080px image.
photo.crop(0, 0, 1080, 1080); // whit x=0 & y=0 i have not problems.
when i try to put a value > 0 i get an error
photo.crop(photo.bitmap.width / 2, photo.bitmap.height / 2, 1080, 1080);
code:'ERR_OUT_OF_RANGE' eventName:'error' message:'The value of "offset" is out of range. It must be >= 0 and <= 8294396. Received 8294400'

UP!
I have the same problem.
I try to cut a 1920x1080px image.
photo.crop(0, 0, 1080, 1080); // whit x=0 & y=0 i have not problems.
when i try to put a value > 0 i get an error
photo.crop(photo.bitmap.width / 2, photo.bitmap.height / 2, 1080, 1080);
code:'ERR_OUT_OF_RANGE' eventName:'error' message:'The value of "offset" is out of range. It must be >= 0 and <= 8294396. Received 8294400'


Dockerize aplication

This PR implement docker to run mongo and run the project API.

https://hub.docker.com/_/mongo


Link not returning to original colour

If you click on a link in the top nav bar e.g "Team" the text of the link will change colour but this will not return back to the original white colour even if you scroll back up the page.

Is it a similar behaviour to this: Issue #12
If so, then there is a code snippet in the second comment, some javascript to release the focus of the button pressed.
I thought the fix was merged long ago. I will try to have a look this weekend.

Yep same issue.

I post here the workaround, please let me know if it works as expected. I will try to push it later.
Workaround (see Issue #12 ):

open js/agency.js
add the following

$(".btn-xl").mouseup(function(){
    $(this).blur();
})

$(".page-scroll").mouseup(function(){
    $(this).blur();
})

reload


Header's tag is wrapped incorrectly under certain situations on windows platform

Environment

ruby: ruby 2.0.0p598 (2014-11-13) [i386-mingw32]
redcarpet: 3.1.2 & 3.2.2, others maybe
pygments.rb: 0.6.1
os: windows 7 & XP (it works well under Linux)

Issues: missing headers' start tag or end tag
When rendering markdown text with "pygments" highlighter, sometimes start tag or end tag of the header would get lost and the output html is shown badly.
For example, look at this code (issue one), missing the end tag of h2:
## 退出 =>
退出
....
And this one (issue two) losts start tag:
## 退出 ## => 退出

.
I encountered this problem when parse markdown file with Jeklly originally.
Test Code
I have used above code to debug "Redcarpet::Markdown.new.render" function
Guessing
At first, I thought it resulted from Jekyll or pygments.rb's highlighting function.
But when debugging, I found both generated the right highlighted code, and after redcarpet parsing, the header's tag got lost (I don't know how redcarpet parses markdown text).
By far, it occurred only if write markdown mixed with Chinese text and English text. To my surprised, it generates the good html when delete several characters in both files. And on Linux it won't do so.
Besides, if don't use highlighter, the generated header's tag is correct.
Do you know why ?

btw, it's a little difficult to reproduce the issue, but it always find me once I write a very long post mixed with two languages.

I have come across the same problem on Windows.  In my case, HTML was generated with no opening  tag:
Customer Credit Card

This particular part of the markdown is simply:
 #### Customer Credit Card

The problem seems to be caused by some earlier problem in the markdown, however I'm unable to locate the cause.
(I will attempt to narrow down a smaller test case).

I came across this problem too. Missing start tag or end tag. But when I used no extension of redcarpet       everything is fine ! I also notice that when I insert a space in Vectors(向量) between s and ( the missing
 is back.

os: windows 7
redcarpet (3.2.3)

How weird.

I found a simple source code to reproduce this issue.
require 'redcarpet'

class TestRenderer < Redcarpet::Render::HTML
  def emphasis(text)
    "a" * 117
  end
end

markdown = Redcarpet::Markdown.new(TestRenderer)

puts markdown.render("*a*\n# aaa")

# expected:
a

# actual:   a

This problem is caused by failing bufprintf, because MinGW's vsnprintf doesn't support C99. I'll send PR to fix this bug:smile:

Thanks guys for reporting and @nitoyon for fixing it! :heart: :blue_heart: :yellow_heart: :green_heart: :purple_heart:


Kim 164906617 super user migrations

Description
Adds a column is_superuser to the users table.
Adds all current Truss engineers as superusers (except two who have not been added yet as office_users).
Reviewer Notes
The user is created in middleware when the officeuser is created (not in migrations), so running prod migrations does not show user data, so this is difficult to verify.
When I ran the local migration, it seemed to pass, but it is not setting is_superuser to true for me locally, although it did for @mikena-truss when she tried it out.  Please uncomment the query in the local migration and see if the is_superuser value gets applied locally.
Setup
To check locally, uncomment the query in the local_migration file.
If you already have your local db set up, run make db_dev_migrate.  Then check your db to find 1) a new is_superuser column. 2) SELECT * FROM users WHERE login_gov_email =<EMAIL_ADDRESS> and see is_superuser set to true
Code Review Verification Steps

[ ] Secure migrations have been tested using bin/run-prod-migrations - Note: does not show users table data because it's created in middleware instead of migrations.
[ ] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

Aaah!  Thank you @lynzt - that makes sense- I thought it was something like that. . .


Filterable MultiSelect loses dropdown label.

@lukefirth commented on Mon Jul 30 2018

Detailed description

Is this issue related to a specific component?

Filterable MultiSelect

What did you expect to happen? What happened instead? What would you like to see changed?

It's not currently in the designkit (as far as I could see). The multi-select behaviour is problematic and different when filterable, in that it removes the dropdown label.
This is fine when the user is actively typing to filter down results, but leaves it looking confusing once some items have been selected - with the component reading: "(1x) Filter"
What I'd like to see changed: The dropdown label is returned when focus is not applied, making the component semantically readable and consistent with the non-filterable variant. When focus is applied the label could be replaced with the 'filter' message.

What version of the Carbon Design System are you using?
9

Additional information

Screenshots or code

Notes

@joshblack commented on Mon Jul 30 2018
Hi @lukefirth! 👋 Thanks so much for taking the time to make this issue 😄
Quick question, is this for the React.js implementation of this component?

@lukefirth commented on Tue Jul 31 2018
Hey @joshblack thanks for getting back so soon. 👋
This is indeed! Link to the specific component in storybook

This issue seems to be resolved, but please re-open if I have interpreted the problem incorrectly


frontend: Stabilization for e2e tests

Stabilized e2e Cypress test for Data Pipelines project. No regression are expected, because only tests are changed and some attributes are added/changed in Components html templates.
Tested local build, linking built lib to UI and manual validation for different screen, e2e tests executed headless and headed and seems there is no problems. ESLint executed successfully and there no issues.
Issue: #1769

Can you please add a short list of the changes you made? It's a bit hard to tell just from the diff.

@ivakoleva I agree with you, but not totally. I don't agree that in this way responsibilities are shifted to reviewers because all of us are working in the best interests of the project and no one is trying to workaround something or push bad code, or not working code in production.
Everything is done in the best interests of the projects and to make easier for all members in the project to develop and contribute in a stable environment.

One thing that I need to mention is that with this PR e2e tests execution time is almost at the limit with ~53mins while the CI/CD job limit is 1h.
Maybe we will need to allocate a specific gitlab runner with increased resources (one more CPU), because execution  artefacts (videos, images, hars) compression takes around 15mins.
With increased resources I believe we will go down to 40-45mins, because local execution finish in about 18mins.


Problem with solarian in combat tracket

The solarian's data don' appear in the combat tracker
Screenshots

Technical details (please complete the following information):

OS: Windows 10
Foundry Version: 11.306
SFRPG Version:  0.24.2

Can you test without modules? This is likely a UI mod issue.

You right, Thank you


[YUNIKORN-1760] Update website for v1.3 release

What is this PR for?

version the doc v1.3.0
Update the v1.3.0 downloads in the both download pages.
Translation of release note v.1.3.0
Announce bar is updated

What type of PR is it?

[ ] - Bug Fix
[ ] - Improvement
[ ] - Feature
[x] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[x] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1760
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

Links of Yunikorn images are not correct.
I will update them after the images are uploaded to the docker hub.


Upgrade Ruma to 0.8

Do you want to continue working on this? The main todo is changing all the references in request / response types to corresponding owned types (str -> String, UserId -> OwnedUserId, ...).

Superseded by #21.


now i cant message again

const wbm = require('wbm');
wbm.start().then(async () => {
const phones = ['target number'];
const message = 'test';
await wbm.send(phones, message);
await wbm.end();
}).catch(err => console.log(err));
first time use this module i can send message, but now i cant send message again

Hello, I just tested and it seems to work. I am using wbm version 1.1.16. Could you provide more details about why it doesn't work for the second time?
Such as:

Node version
Wbm package version
Terminal output logs
Steps to reproduce

Also try to pass this option showBrowser: true, this way you can see the bot opening the browser and performing the task. To do this just pass an object as an argument to the wbm.start() function:
wbm.start({ showBrowser: true }).then(async () => {
    [...]
}).catch(err => console.log(err));

If you can also upload some screenshots of the browser reproducing the problem would be awesome.
Another thing is to check for console errors in the browser

Hi,
I have the same issue.
Sometimes the message is not sent.
The console output confirms that the message has been sent yet the is no message on WhatsApp.
When I use showBrowser - It opens the browser and shows the message but then closed the browser so I can't check the logs.
Is there a way I can keep the browser open after it has sent the message?
I have found that if the mobile number is invalid then it stops the process and I have to "logout" from the linked device and then link the device again.  This could take 2 or more attempts before a message is sent again.
Even though the message is reported as sent there is nothing in the chat history about the message.

Do you guys know how to start the program? it doesn't let me

Do you guys know how to start the program? it doesn't let me

I mean, do i need to add anything to the code that they uploaded to the reporisoty?

I just put in a mobile number and the code worked.
but then it just stopped working and now it will not send messages
Tony Ferguson
RITO Technologies
mobile<PHONE_NUMBER>
office<PHONE_NUMBER>/7
On Mon, Oct 18, 2021 at 4:30 PM lielarie @.***> wrote:

Do you guys know how to start the program? it doesn't let me
I mean, do i need to add anything to the code that they uploaded to the
reporisoty?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Briuor/wbm/issues/28#issuecomment-945836920, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACWMAIF2O2R66CAE76IZBBLUHQVPTANCNFSM5DMTMTIA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


stepfunctions describe_execution always returns "RUNNING"

Issue: When looking at the documentation for step-functions there was no mention of having to use SF_EXECUTION_HISTORY_TYPE to force it to change to a FAILED state. I worked this out by looking at the moto tests.
Link: https://docs.getmoto.org/en/latest/docs/services/stepfunctions.html
As has been done with SES there is a really nice intro to the documentation explaining how to use it.
Link: https://docs.getmoto.org/en/latest/docs/services/ses.html
This is less of a bug than an improvement for future users trying to mock out step functions.

Good shout @bfbenf - that should've indeed been part of the docs in the first place. We've updated the SFN page to show that SF_EXECUTION_HISTORY_TYPE can be used to get a failure result in all three methods (get, describe, list).


As a WHO employee we are responsible to create reports of Populated Countries in the World

The top N populated countries in the world where N is provided by the user.
The top N populated countries in a continent where N is provided by the user.
The top N populated countries in a region where N is provided by the user.

Subtasks:

Write SQL query to retrieve all countries by population.

Sort countries by population size.

Write SQL query for top N populated countries in world/continent/region

Allow user input for N value.

Output the report with the required fields.


python3.10-watchdog-2.1.8 failing to build on aarch64-darwin

Describe the bug
Both the 3.9 and 3.10 versions of watchdog are currently failing to build on aarch64-darwin systems.
Steps To Reproduce

Add pkgs.python30Packages.watchdog as a dependency:

{
  inputs = {
    nixpkgs.url = "github:nixos/nixpkgs";
    flake-utils.url = "github:numtide/flake-utils";
  };

  outputs = { self, nixpkgs, flake-utils }:
    flake-utils.lib.eachDefaultSystem (system:
      let
        pkgs = import nixpkgs { inherit system; };
      in
      {
        devShells.default = pkgs.mkShell {
          packages = [
            pkgs.python310Packages.watchdog
          ];
        };
      }
    );

Attempt to build the package

$ nix develop

Expected behavior
Expected it to build on aarch64-darwin.
Screenshots
N/A
Additional context
Here is the full error log.
Notify maintainers
@cillianderoiste
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"aarch64-darwin"`
 - host os: `Darwin 21.2.0, macOS 12.1`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.7.0`
 - channels(root): `"nixpkgs"`
 - channels(josh): `"darwin"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

The tests on this package are intense. The only way I was able to get it to build was by disabling several of them:
disabledTestPaths = [
  "tests/test_inotify_buffer.py"
  "tests/test_emitter.py"
  "tests/test_0_watchmedo.py"
  "tests/test_fsevents.py"
];

This issue is fixed by pr #171388:
$ nix-build $PWD -A python310Packages.watchdog
these 3 paths will be fetched (0.23 MiB download, 1.14 MiB unpacked):
  /nix/store/74cxyqnbjckr0f78g35g14sbgic02ywm-python3.10-watchdog-2.1.8
  /nix/store/q15fraqp7jdlbk9gslfxmski5d6ihcq2-python3.10-pathtools-0.1.2
  /nix/store/r6zvjf89l79rh7xflxzvphyhjghj66kj-python3.10-pyyaml-6.0
copying path '/nix/store/q15fraqp7jdlbk9gslfxmski5d6ihcq2-python3.10-pathtools-0.1.2' from 'https://cache.nixos.org'...
copying path '/nix/store/r6zvjf89l79rh7xflxzvphyhjghj66kj-python3.10-pyyaml-6.0' from 'https://cache.nixos.org'...
copying path '/nix/store/74cxyqnbjckr0f78g35g14sbgic02ywm-python3.10-watchdog-2.1.8' from 'https://cache.nixos.org'...
/nix/store/74cxyqnbjckr0f78g35g14sbgic02ywm-python3.10-watchdog-2.1.8