KeyError: 'dataset'

Please share the working pip list or pip freeze for Python 3.10
C:\ai1\MMAudio\venv\lib\site-packages\gradio\blocks.py:919: UserWarning: api_name predict already exists, using predict_1
  warnings.warn(
Running on local URL:  http://<IP_ADDRESS>:7860

To create a public link, set `share=True` in `launch()`.
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "C:\ai1\MMAudio\venv\lib\site-packages\uvicorn\protocols\http\h11_impl.py", line 403, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
  File "C:\ai1\MMAudio\venv\lib\site-packages\uvicorn\middleware\proxy_headers.py", line 60, in __call__
    return await self.app(scope, receive, send)
  File "C:\ai1\MMAudio\venv\lib\site-packages\fastapi\applications.py", line 1054, in __call__
    await super().__call__(scope, receive, send)
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\applications.py", line 113, in __call__
    await self.middleware_stack(scope, receive, send)
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\middleware\errors.py", line 187, in __call__
    raise exc
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\middleware\errors.py", line 165, in __call__
    await self.app(scope, receive, _send)
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\middleware\cors.py", line 85, in __call__
    await self.app(scope, receive, send)
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\middleware\exceptions.py", line 62, in __call__
    await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\_exception_handler.py", line 53, in wrapped_app
    raise exc
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\_exception_handler.py", line 42, in wrapped_app
    await app(scope, receive, sender)
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\routing.py", line 715, in __call__
    await self.middleware_stack(scope, receive, send)
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\routing.py", line 735, in app
    await route.handle(scope, receive, send)
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\routing.py", line 288, in handle
    await self.app(scope, receive, send)
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\routing.py", line 76, in app
    await wrap_app_handling_exceptions(app, request)(scope, receive, send)
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\_exception_handler.py", line 53, in wrapped_app
    raise exc
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\_exception_handler.py", line 42, in wrapped_app
    await app(scope, receive, sender)
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\routing.py", line 73, in app
    response = await f(request)
  File "C:\ai1\MMAudio\venv\lib\site-packages\fastapi\routing.py", line 301, in app
    raw_response = await run_endpoint_function(
  File "C:\ai1\MMAudio\venv\lib\site-packages\fastapi\routing.py", line 214, in run_endpoint_function
    return await run_in_threadpool(dependant.call, **values)
  File "C:\ai1\MMAudio\venv\lib\site-packages\starlette\concurrency.py", line 39, in run_in_threadpool
    return await anyio.to_thread.run_sync(func, *args)
  File "C:\ai1\MMAudio\venv\lib\site-packages\anyio\to_thread.py", line 56, in run_sync
    return await get_async_backend().run_sync_in_worker_thread(
  File "C:\ai1\MMAudio\venv\lib\site-packages\anyio\_backends\_asyncio.py", line 2505, in run_sync_in_worker_thread
    return await future
  File "C:\ai1\MMAudio\venv\lib\site-packages\anyio\_backends\_asyncio.py", line 1005, in run
    result = context.run(func, *args)
  File "C:\ai1\MMAudio\venv\lib\site-packages\gradio\routes.py", line 289, in api_info
    return gradio.blocks.get_api_info(config, serialize)  # type: ignore
  File "C:\ai1\MMAudio\venv\lib\site-packages\gradio\blocks.py", line 517, in get_api_info
    serializer = serializing.COMPONENT_MAPPING[type]()
KeyError: 'dataset'

@hkchengrex
Yes, it was an issue at my end. Thank you for creating this awesome tool, works good.
Appreciate you sharing with us.


module: fix command filename quoting

The commands would fail when the file names contain a '

Name a more pervasive problem than shell quoting.


Using 1-Click Child-Links from the menu does not add links

I installed the extension on TFS 2017 RTW (corporate on-premises deployment) and tried to use it - created templates and clicked the 1-Click Child-Links when creating work item. No links are being created. Read the guide on Marketplace multiple times, but could not figure out what I am missing.
Would you be able to point out what step I am missing?

This happens in almost every TFS web extension.  Need to add a polyfill if you want to support IE.


docs: Gitbook setup

- What I did

@Xlin123 setup Gitbook for this repo, I followed up and completed the LICENSE page.

Site preview
- How I did it
- How to verify it
- Description for the changelog
docs: Gitbook setup

Right now Gitbook is tracking this branch, once this is merged I will create a gitbook branch and configure it with the appropriate branch protection


Fixes #280: Implements acessibility rule for required input elements

Creates the rule react-a11y-required to assert that required input elements have the aria-required attribute set to true.
Fixes #280.

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

Looks good to me. I think with modern browsers it's redundant but I don't have a source on that and it's been awhile since I've been in the area.


Multiple Markers

Hello
Thanks For The Great Project
I Just Started Using This Project And I Want To Show Multiple Markers On My Map
Is There Any Way That I Can Do That?
And Also I Have To Set Center To User Location Is That Possible Or Not?
Thanks.

You can use one route of point A (user location) to point B, this moment not is possible multiple points, but PR is welcome!


FoBo Components - textAngular

Consider textAngular as a component in FoBo's Component sub module
http://textangular.com/
http://ngmodules.org/modules/textAngular
https://github.com/fraywing/textAngular

Will wait for ng2 and its component approach


Mat4x4 multiplication

The result the product of 4x4 matrix is here the transposed of the expected result...

I found the same issue

Sorry for responding so late, somehow I didn't notice the initial issue notification.
This is now fixed in 008e4e5.
I'm preparing a new release right now.


API for PN analyses?

Hi,
I'd like to use your PN analyses of current or previous versions of PIPE without using the GUI. Concretely, I want to use it in other languages or at least in other Java tools.  Is this possible? Do you have any info of how to do it?
Thanks in advance.
Salva

There is a branch of PIPE currently under development that enables
execution of PNs through an API, without the GUI, documented here:
https://github.com/sjdayday/PIPECore/wiki
I've used this API to call PNs from Python.
But it has no support yet for running the various types of analysis that
are supported under the GUI.
Hope that helps.
Steve
On Tue, Oct 18, 2016 at 5:35 AM, Salvador Tamarit<EMAIL_ADDRESS>wrote:

Hi,
I'd like to use your PN analyses of current or previous versions of PIPE
without using the GUI. Concretely, I want to use it in other languages or
at least in other Java tools. Is this possible? Do you have any info of how
to do it?
Thanks in advance.
Salva
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sarahtattersall/PIPE/issues/116, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACAHxiyjIZMwComnH2uHUdgu-cSgr2Rmks5q1L0bgaJpZM4KZvBf
.

--
Steve Doubleday
PhD candidate, Mathematical Behavioral Sciences
UC Irvine
<EMAIL_ADDRESS>818-648-8381

Hi @sjdayday,
first of all, thanks for your prompt answer. As I understand from the documentation and from what you are saying, this API only gives access to the PN animator and a few more functionalities, but it does not provide access to the analyses in what I'm interested. I'd need something like LOLA or similar PN tools (e.g. https://github.com/CvO-Theory/apt) but with your analyses. I can try to find alternatives, but I think that it could be interesting to provide this external interface in order to make PIPE even more useful.
Thanks again!
Salva

Hi Salva,
I agree that the analyses would be useful to add.  I think that's pretty
far in the future, at least for me.  Thanks for the feedback!
best,
Steve
On Tue, Oct 18, 2016 at 12:55 PM, Salvador Tamarit<EMAIL_ADDRESS>
wrote:

Hi @sjdayday https://github.com/sjdayday,
first of all, thanks for your prompt answer. As I understand from the
documentation and from what you are saying, this API only gives access to
the PN animator and a few more functionalities, but it does not provide
access to the analyses in what I'm interested. I'd need something like LOLA
or similar PN tools (e.g. https://github.com/CvO-Theory/apt) but with
your analyses. I can try to find alternatives, but I think that it could be
interesting to provide this external interface in order to make PIPE even
more useful.
Thanks again!
Salva
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sarahtattersall/PIPE/issues/116#issuecomment-254620635,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACAHxtX8l3VSo-uB5paqNdHWl-tIF0UQks5q1SROgaJpZM4KZvBf
.

--
Steve Doubleday
PhD candidate, Mathematical Behavioral Sciences
UC Irvine
<EMAIL_ADDRESS>818-648-8381


compute_HSweights does not work for strahler based weighting

An error is thrown when strahler based weighting is used via compute_HSweights().

This has been fixed now - problem was that the function computing strahler weights was unnecessarily calling river_network() when it was already computed.


Owner info resets to blank after opening one of the links on the Settings view

I added name, email and URL to the Owner section in the settings panel, then tapped the help link, and when I came back the Owner info had reset to blank. Repeated by re-entering and tapping the GitHub link.

I fixed this in 2.2. Thanks for the bug report!


Workflow hangs indefinitely during "ContainerCreating" if the Pod or Node unexpectedly dies

Summary
When a node is drained or pods are evicted from a node during the "ContainerCreating" step, the argo-workflow goes into a zombie state; perpetually waiting for the non-existent container to create.
Ideally at this stage argo would recognize the pod/node is no longer present and retry the task or report a failure for that workflow.
The easiest way to reproduce this error is to delete the pod during the "ContainerCreating" step after a workflow has been submitted.
Diagnostics
What Kubernetes provider are you using?
  I successfully ran this workflow pre- and post- capture of the logs without any other workflows being submitted.

 time="2021-03-29T20:55:26.792Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T20:55:26.793Z" level=info msg="Updated phase  -> Running" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T20:55:26.794Z" level=info msg="Steps node steps-tt9wq initialized Running" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T20:55:26.794Z" level=info msg="StepGroup node steps-tt9wq-196468504 initialized Running" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T20:55:26.794Z" level=info msg="Pod node steps-tt9wq-4247131649 initialized Pending" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T20:55:26.824Z" level=info msg="Created pod: steps-tt9wq[0].hello1 (steps-tt9wq-4247131649)" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T20:55:26.824Z" level=info msg="Workflow step group node steps-tt9wq-196468504 not yet completed" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T20:55:26.838Z" level=info msg="Workflow update successful" namespace=sandbox phase=Running resourceVersion=86320701 workflow=steps-tt9wq
 time="2021-03-29T20:55:36.792Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T20:55:36.793Z" level=info msg="Updating node steps-tt9wq-4247131649 message: ContainerCreating"
 time="2021-03-29T20:55:36.794Z" level=info msg="workflow active pod spec parallelism reached 1/1" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T20:55:36.794Z" level=error msg="error in entry template execution" error="Max parallelism reached" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T20:55:36.809Z" level=info msg="Workflow update successful" namespace=sandbox phase=Running resourceVersion=86320807 workflow=steps-tt9wq
 time="2021-03-29T20:55:46.811Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T20:55:46.812Z" level=info msg="Workflow pod is missing" namespace=sandbox nodeName="steps-tt9wq[0].hello1" nodePhase=Pending recentlyStarted=false workflow=steps-tt9wq
 time="2021-03-29T20:55:46.813Z" level=info msg="workflow active pod spec parallelism reached 1/1" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T20:55:46.813Z" level=error msg="error in entry template execution" error="Max parallelism reached" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T21:15:46.812Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T21:15:46.813Z" level=info msg="Workflow pod is missing" namespace=sandbox nodeName="steps-tt9wq[0].hello1" nodePhase=Pending recentlyStarted=false workflow=steps-tt9wq
 time="2021-03-29T21:15:46.813Z" level=info msg="workflow active pod spec parallelism reached 1/1" namespace=sandbox workflow=steps-tt9wq
 time="2021-03-29T21:15:46.813Z" level=error msg="error in entry template execution" error="Max parallelism reached" namespace=sandbox workflow=steps-tt9wq

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Maybe this is some interplay between parallelism and created nodes. However, I'm surprised we have not had a any other complaints about this as I would imagine it would pretty common.

@rysunder can you please run the workflow without parallelism (or until running nodes complete) and see if the third pod runs?

@rysunder can you please run the workflow without parallelism (or until running nodes complete) and see if the third pod runs?

@alexec We originally ran it without Max Parallelism set.  We tried to fix the issue by setting Max Parallelism to 100.  If that is what you meant by "without parallelism" then we have already tested that with the same effect.  Also "parallelism reached 1/1" is mentioned multiple times in the logs.
Is there any other information that may be helpful?

the controller will not schedule any pods where you reach parallelism - the example you attached has reached max parallelism - I want to know if disabling it allows those pods to scheduled which will help shed light on whether or not it is a bug with that feature, or something else

@sarabala1979 there may be two issues here:

Is max parallelism preventing scheduling until running pods complete? It's not clear to me if there is actually an issue here.
Is there some issue with ignoring or missing ContainerCreating? Those pods will be in Pending state.

the controller will not schedule any pods where you reach parallelism - the example you attached has reached max parallelism - I want to know if disabling it allows those pods to scheduled which will help shed light on whether or not it is a bug with that feature, or something else

@alexec Thank you for clarifying!
I removed parallelism from the controller.parallelism and controller.workflowDefaults.spec.parallelism on the EKS cluster and re-ran the tests.
Interestingly, the workflow did not hang indefinitely.  It would pause when the pod was yanked, but eventually recovered (usually within a handful of seconds) and complete the workflow successfully.  Below are the workflow-controller logs related to the workflow.
Paste the logs from the workflow controller:
kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name) | grep ${workflow}

 time="2021-03-31T21:31:37.357Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:31:37.357Z" level=info msg="Updated phase  -> Running" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:31:37.359Z" level=info msg="Steps node steps-98j8q initialized Running" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:31:37.359Z" level=info msg="StepGroup node steps-98j8q-1810041543 initialized Running" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:31:37.360Z" level=info msg="Pod node steps-98j8q-1363360536 initialized Pending" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:31:37.388Z" level=info msg="Created pod: steps-98j8q[0].hello1 (steps-98j8q-1363360536)" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:31:37.388Z" level=info msg="Workflow step group node steps-98j8q-1810041543 not yet completed" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:31:37.402Z" level=info msg="Workflow update successful" namespace=sandbox phase=Running resourceVersion=87577095 workflow=steps-98j8q
 time="2021-03-31T21:31:47.357Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:31:47.358Z" level=info msg="Workflow pod is missing" namespace=sandbox nodeName="steps-98j8q[0].hello1" nodePhase=Pending recentlyStarted=false workflow=steps-98j8q
 time="2021-03-31T21:31:47.384Z" level=info msg="Created pod: steps-98j8q[0].hello1 (steps-98j8q-1363360536)" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:31:47.384Z" level=info msg="Workflow step group node steps-98j8q-1810041543 not yet completed" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:31:57.386Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:31:57.387Z" level=info msg="Setting node steps-98j8q-1363360536 outputs"
 time="2021-03-31T21:31:57.387Z" level=info msg="Updating node steps-98j8q-1363360536 status Pending -> Running"
 time="2021-03-31T21:31:57.388Z" level=info msg="Workflow step group node steps-98j8q-1810041543 not yet completed" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:31:57.404Z" level=info msg="Workflow update successful" namespace=sandbox phase=Running resourceVersion=87577245 workflow=steps-98j8q
 time="2021-03-31T21:32:07.406Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:07.407Z" level=info msg="Updating node steps-98j8q-1363360536 status Running -> Succeeded"
 time="2021-03-31T21:32:07.408Z" level=info msg="Step group node steps-98j8q-1810041543 successful" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:07.408Z" level=info msg="node steps-98j8q-1810041543 phase Running -> Succeeded" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:07.408Z" level=info msg="node steps-98j8q-1810041543 finished: 2021-03-31 21:32:07.408360433 +0000 UTC" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:07.408Z" level=info msg="StepGroup node steps-98j8q-1877299114 initialized Running" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:07.408Z" level=info msg="SG Outbound nodes of steps-98j8q-1363360536 are [steps-98j8q-1363360536]" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:07.408Z" level=info msg="Pod node steps-98j8q-841259073 initialized Pending" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:07.431Z" level=info msg="Created pod: steps-98j8q[1].hello2a (steps-98j8q-841259073)" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:07.433Z" level=info msg="Pod node steps-98j8q-790926216 initialized Pending" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:07.457Z" level=info msg="Created pod: steps-98j8q[1].hello2b (steps-98j8q-790926216)" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:07.457Z" level=info msg="Workflow step group node steps-98j8q-1877299114 not yet completed" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:07.474Z" level=info msg="Workflow update successful" namespace=sandbox phase=Running resourceVersion=87577320 workflow=steps-98j8q
 time="2021-03-31T21:32:07.500Z" level=info msg="Labeled pod completed" namespace=sandbox pod=steps-98j8q-1363360536
 time="2021-03-31T21:32:17.432Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:17.434Z" level=info msg="Setting node steps-98j8q-841259073 outputs"
 time="2021-03-31T21:32:17.434Z" level=info msg="Updating node steps-98j8q-841259073 status Pending -> Succeeded"
 time="2021-03-31T21:32:17.434Z" level=info msg="Workflow pod is missing" namespace=sandbox nodeName="steps-98j8q[1].hello2b" nodePhase=Pending recentlyStarted=false workflow=steps-98j8q
 time="2021-03-31T21:32:17.435Z" level=info msg="SG Outbound nodes of steps-98j8q-1363360536 are [steps-98j8q-1363360536]" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:17.467Z" level=info msg="Created pod: steps-98j8q[1].hello2b (steps-98j8q-790926216)" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:17.467Z" level=info msg="Workflow step group node steps-98j8q-1877299114 not yet completed" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:17.482Z" level=info msg="Workflow update successful" namespace=sandbox phase=Running resourceVersion=87577412 workflow=steps-98j8q
 time="2021-03-31T21:32:17.511Z" level=info msg="Labeled pod completed" namespace=sandbox pod=steps-98j8q-841259073
 time="2021-03-31T21:32:27.470Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.472Z" level=info msg="Setting node steps-98j8q-790926216 outputs"
 time="2021-03-31T21:32:27.472Z" level=info msg="Updating node steps-98j8q-790926216 status Pending -> Succeeded"
 time="2021-03-31T21:32:27.473Z" level=info msg="SG Outbound nodes of steps-98j8q-1363360536 are [steps-98j8q-1363360536]" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.473Z" level=info msg="Step group node steps-98j8q-1877299114 successful" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.473Z" level=info msg="node steps-98j8q-1877299114 phase Running -> Succeeded" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.473Z" level=info msg="node steps-98j8q-1877299114 finished: 2021-03-31 21:32:27.473766129 +0000 UTC" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.473Z" level=info msg="Outbound nodes of steps-98j8q-841259073 is [steps-98j8q-841259073]" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.473Z" level=info msg="Outbound nodes of steps-98j8q-790926216 is [steps-98j8q-790926216]" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.473Z" level=info msg="Outbound nodes of steps-98j8q is [steps-98j8q-841259073 steps-98j8q-790926216]" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.473Z" level=info msg="node steps-98j8q phase Running -> Succeeded" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.473Z" level=info msg="node steps-98j8q finished: 2021-03-31 21:32:27.473908032 +0000 UTC" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.473Z" level=info msg="Checking daemoned children of steps-98j8q" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.473Z" level=info msg="Updated phase Running -> Succeeded" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.473Z" level=info msg="Marking workflow completed" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.473Z" level=info msg="Marking workflow as pending archiving" namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.474Z" level=info msg="Checking daemoned children of " namespace=sandbox workflow=steps-98j8q
 time="2021-03-31T21:32:27.493Z" level=info msg="Workflow update successful" namespace=sandbox phase=Succeeded resourceVersion=87577494 workflow=steps-98j8q
 time="2021-03-31T21:32:27.498Z" level=info msg="archiving workflow" namespace=sandbox uid=<uid> workflow=steps-98j8q
 time="2021-03-31T21:32:27.512Z" level=info msg="Labeled pod completed" namespace=sandbox pod=steps-98j8q-790926216
 time="2021-03-31T21:32:27.550Z" level=info msg="archiving workflow" namespace=sandbox uid=<uid> workflow=steps-98j8q
 time="2021-03-31T21:32:27.555Z" level=info msg="Queueing Succeeded workflow sandbox/steps-98j8q for delete in 1h0m0s"
 time="2021-03-31T21:32:27.556Z" level=info msg="Queueing Succeeded workflow sandbox/steps-98j8q for delete in 1h0m0s"

The next test I ran was to disable just the controller.workflowDefaults.spec.parallelism and leave the controller.parallelism set to what it was originally.  This resulted in hanging jobs!
Paste the logs from the workflow controller:
kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name) | grep ${workflow}

 time="2021-04-01T17:34:31.828Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-hrn66
 time="2021-04-01T17:34:31.829Z" level=info msg="Updated phase  -> Running" namespace=sandbox workflow=steps-hrn66
 time="2021-04-01T17:34:31.831Z" level=info msg="Steps node steps-hrn66 initialized Running" namespace=sandbox workflow=steps-hrn66
 time="2021-04-01T17:34:31.831Z" level=info msg="StepGroup node steps-hrn66-352772121 initialized Running" namespace=sandbox workflow=steps-hrn66
 time="2021-04-01T17:34:31.831Z" level=info msg="Pod node steps-hrn66-3293355422 initialized Pending" namespace=sandbox workflow=steps-hrn66
 time="2021-04-01T17:34:31.866Z" level=info msg="Created pod: steps-hrn66[0].hello1 (steps-hrn66-3293355422)" namespace=sandbox workflow=steps-hrn66
 time="2021-04-01T17:34:31.866Z" level=info msg="Workflow step group node steps-hrn66-352772121 not yet completed" namespace=sandbox workflow=steps-hrn66
 time="2021-04-01T17:34:31.879Z" level=info msg="Workflow update successful" namespace=sandbox phase=Running resourceVersion=88816984 workflow=steps-hrn66
 time="2021-04-01T17:34:41.802Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-hrn66
 time="2021-04-01T17:34:41.804Z" level=info msg="Updating node steps-hrn66-3293355422 message: ContainerCreating"
 time="2021-04-01T17:34:41.804Z" level=info msg="workflow active pod spec parallelism reached 1/1" namespace=sandbox workflow=steps-hrn66
 time="2021-04-01T17:34:41.804Z" level=error msg="error in entry template execution" error="Max parallelism reached" namespace=sandbox workflow=steps-hrn66
 time="2021-04-01T17:34:41.815Z" level=info msg="Workflow update successful" namespace=sandbox phase=Running resourceVersion=88817082 workflow=steps-hrn66
 time="2021-04-01T17:34:51.817Z" level=info msg="Processing workflow" namespace=sandbox workflow=steps-hrn66
 time="2021-04-01T17:34:51.819Z" level=info msg="Workflow pod is missing" namespace=sandbox nodeName="steps-hrn66[0].hello1" nodePhase=Pending recentlyStarted=false workflow=steps-hrn66
 time="2021-04-01T17:34:51.819Z" level=info msg="workflow active pod spec parallelism reached 1/1" namespace=sandbox workflow=steps-hrn66
 time="2021-04-01T17:34:51.819Z" level=error msg="error in entry template execution" error="Max parallelism reached" namespace=sandbox workflow=steps-hrn66

Finally, I disabled the controller.parallelism and re-enabled the controller.workflowDefaults.spec.parallelism.  The workflow recovered successfully when the pod or node was removed during the ContainerCreating step.
In summary, it appears to be an issue related to the controller.workflowsDefaults.spec.parallelism that results in zombie workflows when a pod/node is removed during the ContainerCreating step.

Can you please share your workflows-controller-configmap?

Can you please share your workflows-controller-configmap?

Can do!
 Name:         argo-workflow-controller-configmap
 Namespace:    argo
 Labels:       app.kubernetes.io/managed-by=Helm
               chart=argo-0.15.4
               heritage=Helm
               release=argo
 Annotations:  meta.helm.sh/release-name: argo
               meta.helm.sh/release-namespace: argo

 Data
 ====
 config:
 ----
 containerRuntimeExecutor: pns
 parallelism: 100
 artifactRepository:
   archiveLogs: true
   s3:
     bucket: <my-redacted-bucket>
     endpoint: s3.amazonaws.com
     insecure: false
     keyFormat: dev/{{workflow.creationTimestamp.Y}}/{{workflow.creationTimestamp.m}}/{{workflow.creationTimestamp.d}}/{{workflow.name}}/{{pod.name}}
     region: <region>
     useSDKCreds: true
 metricsConfig:
   enabled: true
   metricsTTL: 240m
   path: /metrics
   port: 8080
 persistence:
   archive: true
   archiveTTL: 90d
   connectionPool:
     maxIdleConns: 100
     maxOpenConns: 0
   mysql:
     database: argo_database
     host: <database-server-hostname>
     passwordSecret:
       key: password
       name: argo-mysql-config
     port: 3306
     tableName: argo_workflows
     userNameSecret:
       key: username
       name: argo-mysql-config
   nodeStatusOffLoad: false
 workflowDefaults:
   spec:
     affinity:
       podAffinity:
         preferredDuringSchedulingIgnoredDuringExecution:
         - podAffinityTerm:
             labelSelector:
               matchExpressions:
               - key: workflows.argoproj.io/completed
                 operator: In
                 values:
                 - "false"
             topologyKey: kubernetes.io/hostname
           weight: 100
         - podAffinityTerm:
             labelSelector:
               matchExpressions:
               - key: workflows.argoproj.io/workflow
                 operator: Exists
             topologyKey: kubernetes.io/hostname
           weight: 1
     nodeSelector:
       spot: "true"
     parallelism: 1
     securityContext:
       fsGroup: 123456789
     serviceAccountName: argo-sa
     tolerations:
     - effect: NoSchedule
       key: value
       operator: Equal
       value: "true"
     ttlStrategy:
       secondsAfterCompletion: 3600
       secondsAfterFailure: 3600
       secondsAfterSuccess: 3600
 sso:
   clientId:
     key: client-id
     name: argo-server-sso
   clientSecret:
     key: client-secret
     name: argo-server-sso
   issuer: https://login.microsoftonline.com/uid/v2.0
   rbac:
     enabled: true
   redirectUrl: https://argo-hostname.net/oauth2/callback
   scopes:
   - uid2/.default
   - email

 Events:  <none>

I'm not clear, there are two parallelism settings, data.parallelism and `data.workflowDefaults.spec.parallelism'. Removing which fixed the problem?

I'm not clear, there are two parallelism settings, data.parallelism and `data.workflowDefaults.spec.parallelism'. Removing which fixed the problem?

Removing data.workflowDefaults.spec.parallelism fixed the issue

Ok. Can you attach:

status.storedWorkflowTemplateSpec for the bad workflow.
status.storedWorkflowTemplateSpec for the good workflow.

Ok. Can you attach:

status.storedWorkflowTemplateSpec for the bad workflow.
status.storedWorkflowTemplateSpec for the good workflow.

More than happy to ... if I knew how to get that information.  Is there a quick how-to on it I could follow?

@alexec problem is the active pod is calculated based on node status (pending and running) In this scenario, the node  status is in pending status and parallelism is 1, so the controller is the exit from the parallel check.  podReconciliation is just continue if pod is missing and node status is pending.
Suggestions:

Introduce a new state for pod missing which needs to exclude from active pod count.

https://github.com/argoproj/argo-workflows/blob/4e450e250168e6b4d51a126b784e90b11a0162bc/workflow/controller/operator.go#L969-L980
https://github.com/argoproj/argo-workflows/blob/4e450e250168e6b4d51a126b784e90b11a0162bc/workflow/controller/node_counters.go#L9-L18


Animation effect breaks Disqus

Hi! Great template, I love it so far. I found one problem though. I set up the animation effect, add Disqus comments, and when I click the little bubble icon the Disqus page should show up as an Iframe. But when the animation effect is on, the page loads at the top.
I removed the body class and moved it to the first div in default.html layout and it is now working fine. I hope I didn't break anything I don't know of.

Thanks for reporting this, @84rn. I'll dig into it this evening to see what's going on. I don't believe moving the class to the first div should mess with anything, though I believe it will cause the footer to not be animated. I'll likely just add one more wrapping div that also envelopes the footer. I'll keep you posted. Thanks again!


interactive bots: Create Joinme bot.

@itstakenalr: Hey! Could you please take a look at the build errors here? We would love to get this merged! :) Thanks!

@eeshangarg I've fixed the errors, thank you!


Parameter recommendations

@pierluigiferrari : Hello pierluigiferrari   I am currently using ssd7 training face dataset， I want to do a real-time multi-face detection , video streaming size 600*800 , but I encountered a difficult point , As the surveillance camera hung on the wall, cause the face target size smaller.
Can you give me some advice about Training related parameters ,like scales , aspect_ratios , variances how to setting or more suggestion ?
Thanks in advance : )

Just a few quick points:

Since you're trying to detect faces only, which are roughly square, you could try going with aspect ratio 1:1 as the only aspect ratio.
When it comes to the sizes and the distribution of your anchor boxes across the images, there are two you want to make sure:

The anchor boxes should cover the scales of the ground truth boxes, so make the scaling factors however small you need to in order to cover the ground truth.
The smaller your objects (and thus your anchor boxes), the more anchor boxes you will want spatially in order to cover the whole image appropriately. How do you get more anchor boxes in the spatial dimensions? You increase the spatial dimensions of the convolutional predictor layers. I order to do that, you could experiment with making predictions from an earlier conv layer, e.g. conv3. Or you could remove one of the pooling layers, but then of course all predictor layers that come after it will quadruple in their spatial sizes.
Especially for this second point, you cannot get around really putting in the effort and calculating and maybe visualizing what your grid of anchor boxes looks like for a given predictor layer. And then you can answer the questions: Is this a good coverage of my input image? Do the sizes and aspect ratios of these anchor boxes make sense for the training data I have? Do these anchor boxes even lie within the receptive fields of their respective layers?

Over the next weeks I'll implement Focal Loss, which might improve SSD's results for small objects. I don't have the time to do it right now, but I will implement and try it out eventually.
When it comes to the input images size, you have the following problem: The smaller the objects are that you want to detect, the more important it becomes to use higher resolution images. This should be obvious: If you want to retain a certain level of detail of very small objects, the image resolution has to be appropriate. At the same time though, increasing image size makes your network drastically slower. I don't know what the answer is in your case. On the one hand, using 600*800 input (or as large as you can get, really) is great for the prediction quality, but at the same time you have to see up to what resolution your network can still make predictions at the frame rate you need, whatever that is.

@pierluigiferrari  Thank you for your reply , I will try your advice.


Clean up compiler warnings

More recent versions of solidity are issuing warnings about various deprecations.
These are not a safety concern, but it does look scary to new comers, so we should fix it.

Specifially, when running solc ./contracts/*.sol at version 0.4.17 or newer, you get this:
./contracts/Token.sol:20:5: Warning: No visibility specified. Defaulting to "public".
    function balanceOf(address _owner) constant returns (uint256 balance);
    ^--------------------------------------------------------------------^
./contracts/Token.sol:26:5: Warning: No visibility specified. Defaulting to "public".
    function transfer(address _to, uint256 _value) returns (bool success);
    ^--------------------------------------------------------------------^
./contracts/Token.sol:33:5: Warning: No visibility specified. Defaulting to "public".
    function transferFrom(address _from, address _to, uint256 _value) returns (bool success);
    ^---------------------------------------------------------------------------------------^
./contracts/Token.sol:39:5: Warning: No visibility specified. Defaulting to "public".
    function approve(address _spender, uint256 _value) returns (bool success);
    ^------------------------------------------------------------------------^
./contracts/Token.sol:44:5: Warning: No visibility specified. Defaulting to "public".
    function allowance(address _owner, address _spender) constant returns (uint256 remaining);
    ^----------------------------------------------------------------------------------------^
./contracts/StandardToken.sol:17:5: Warning: No visibility specified. Defaulting to "public".
    function transfer(address _to, uint256 _value) returns (bool success) {
    ^
Spanning multiple lines.
./contracts/StandardToken.sol:29:5: Warning: No visibility specified. Defaulting to "public".
    function transferFrom(address _from, address _to, uint256 _value) returns (bool success) {
    ^
Spanning multiple lines.
./contracts/StandardToken.sol:43:5: Warning: No visibility specified. Defaulting to "public".
    function balanceOf(address _owner) constant returns (uint256 balance) {
    ^
Spanning multiple lines.
./contracts/StandardToken.sol:47:5: Warning: No visibility specified. Defaulting to "public".
    function approve(address _spender, uint256 _value) returns (bool success) {
    ^
Spanning multiple lines.
./contracts/StandardToken.sol:53:5: Warning: No visibility specified. Defaulting to "public".
    function allowance(address _owner, address _spender) constant returns (uint256 remaining) {
    ^
Spanning multiple lines.
./contracts/HumanStandardToken.sol:33:5: Warning: No visibility specified. Defaulting to "public".
    function HumanStandardToken(
    ^
Spanning multiple lines.
./contracts/HumanStandardToken.sol:47:5: Warning: No visibility specified. Defaulting to "public".
    function approveAndCall(address _spender, uint256 _value, bytes _extraData) returns (bool success) {
    ^
Spanning multiple lines.
./contracts/HumanStandardTokenFactory.sol:11:5: Warning: No visibility specified. Defaulting to "public".
    function HumanStandardTokenFactory() {
    ^
Spanning multiple lines.
./contracts/HumanStandardTokenFactory.sol:19:5: Warning: No visibility specified. Defaulting to "public".
    function verifyHumanStandardToken(address _tokenContract) constant returns (bool) {
    ^
Spanning multiple lines.
./contracts/HumanStandardTokenFactory.sol:54:5: Warning: No visibility specified. Defaulting to "public".
    function createHumanStandardToken(uint256 _initialAmount, string _name, uint8 _decimals, string _symbol) returns (address) {
    ^
Spanning multiple lines.
./contracts/Migrations.sol:11:3: Warning: No visibility specified. Defaulting to "public".
  function Migrations() {
  ^
Spanning multiple lines.
./contracts/Migrations.sol:15:3: Warning: No visibility specified. Defaulting to "public".
  function setCompleted(uint completed) restricted {
  ^
Spanning multiple lines.
./contracts/Migrations.sol:19:3: Warning: No visibility specified. Defaulting to "public".
  function upgrade(address new_address) restricted {
  ^
Spanning multiple lines.
./contracts/SampleRecipientSuccess.sol:16:3: Warning: No visibility specified. Defaulting to "public".
  function receiveApproval(address _from, uint256 _value, address _tokenContract, bytes _extraData) {
  ^
Spanning multiple lines.
./contracts/HumanStandardToken.sol:54:46: Warning: "sha3" has been deprecated in favour of "keccak256"
        require(_spender.call(bytes4(bytes32(sha3("receiveApproval(address,uint256,address,bytes)"))), msg.sender, _value, this, _extraData));
                                             ^----------------------------------------------------^

@maurelian I would like to work on this

Please review the PR. Thanks !

@maurelian would you mind hitting the 'accept' button at https://gitcoin.co/funding/details?url=https://github.com/ConsenSys/Tokens/issues/85 to remit payment to @subramanianv ? thanks!

got it


Navigating sub-directories/buckets?

Once you dig into a bucket and retrieve the object contents, you just get a giant list of everything. When you're trying to read/list contents on a per-directory basis this proves difficult.
Any way or future plan to allow navigating through sub-directories (or buckets, if that's what they really are)?

I had the same issue yesterday.  The comment about sending a :delimiter to find_all in objects_extension.rb implies that is the way to do it, but the code doesn't parse the returned data correctly.
I ended up adding the following code locally to gain this functionality:
module S3
  class Bucket
    def directory_list(options = {})
      options = {:delimiter => "/"}.merge(options)
      response = bucket_request(:get, :params => options)
      parse_directory_list_result(response.body)
    end

    def parse_directory_list_result(xml)
      names = []
      rexml_document(xml).elements.each("ListBucketResult/CommonPrefixes/Prefix") { |e| names << e.text }
      names
    end
  end
end

And then just call it with
bucket.directory_list :prefix => "foo/bar/baz/"
Sorry its not a full blown pull request, but I don't have the time to make one right now.  You are, of course, welcome to do whatever you want with this.  I'd suggest also removing the documentation about :delimiter from objects_extension.rb, since its a bit of a red-herring.
Thanks for writing this module in the first place,
-Chris

Chouck, can you try to add some tests, and create a pull request for that?

I'm not really sure if that patch really solves the issue I was experiencing. I want to list just the top-level directories within a given bucket, then with each one of those, this patch becomes effective since you can take a given directory/sub-bucket and pass it into the directory_list method.

(sorry for spam)
To get objects within a given subdirectory this patch does not totally solve the problem, you still have to iterate over the entire collection and select just the objects you care about. ala ...
all_objects_in_my_bucket = s3_service.buckets.find('some bucket').objects
objects_grouped_by_sub_dir = s3_service.buckets.find('some bucket').directory_list(:prefix => 'some directory with many sub directories').inject({}) { |memo, dir|
  memo[dir] = all_objects_in_my_bucket.select { |o| o.key.include?(dir) }
  memo
}

There's got to be a better way.

True, but I think you and I are trying to solve different problems.
I have a huge tree of data and I wanted a list of sub-directories 3 layers down (which are dynamically generated, so I don't have a fixed list).  I don't want all of the files in each of those sub-directories, in fact, I only want one or two out of the thousands that are in each sub-tree.
If I'm understanding what you are saying, it sounds like you want something more like:
my_bucket = s3_service.buckets.find('some bucket')
prefix_list = my_bucket.directory_list(:prefix => 'some directory with many sub directories')
prefix_list.each { |prefix| objects_grouped_by_sub_dir[prefix] = my_bucket.objects.find_all(:prefix => prefix)}

Yes! Guess I should've dug in on the source some more. Thanks.

Sorry to resurrect an old thread but I needed this feature very much, any progress with this or a linked PR?  I wouldn't mind creating it!

Also I expanded on what @chouck created:
  class Bucket
    # this method recurses if the response coming back
    # from S3 includes a truncation flag (IsTruncated == 'true')
    # then parses the combined response(s) XML body
    # for CommonPrefixes/Prefix AKA directories
    def directory_list(options = {}, responses = [])
      options = {:delimiter => "/"}.merge(options)
      response = bucket_request(:get, :params => options)

      if is_truncated?(response.body)
        directory_list(options.merge({:marker => next_marker(response.body)}), responses << response.body)
      else
        parse_xml_array(responses + [response.body], options)
      end
    end

    private

    def parse_xml_array(xml_array, options = {}, clean_path = true)
      names = []
      xml_array.each do |xml|
        rexml_document(xml).elements.each("ListBucketResult/CommonPrefixes/Prefix") do |e|
          if clean_path
            names << e.text.gsub((options[:prefix] || ''), '').gsub((options[:delimiter] || ''), '')
          else
            names << e.text
          end
        end
      end
      names
    end

    def next_marker(xml)
      marker = nil
      rexml_document(xml).elements.each("ListBucketResult/NextMarker") {|e| marker ||= e.text }
      if marker.nil?
        raise StandardError
      else
        marker
      end
    end

    def is_truncated?(xml)
      is_truncated = nil
      rexml_document(xml).elements.each("ListBucketResult/IsTruncated") {|e| is_truncated ||= e.text }
      is_truncated == 'true'
    end
  end
end

This handles listing out directories when you run into a key limit (due to the S3 API MaxKeys hard limit of 1000 keys).  The request will recurse and grab all responses before parsing and returning them.  I also added the ability to return "clean directory names" (folder names only) in lieu of returning the entire key/path.


[BUG] unable to detach degraded V2 volume; keeps automatically (but incompletely) re-attaching

Describe the bug
If I create a V2 volume that is degraded (not enough replicas) and attach it to a node, it works fine the first time. I see nvme0n1 and dm-0 appear if I run cat /proc/partitions, and I can read/write the volume under /dev/mapper/vol. If I then detach the volume, it initially detaches (the devices disappear from the host), but then in the Lonhorn UI, it immediately goes back to saying it's attached to the host, and degraded, but the block devices are not actually present on the host.. If I click the detach button, nothing changes. It's still in this weird limbo state. If I force detach it, it appears to detach briefly, but then re-attaches, but again, it's not really attached -- there's no block device on the host.
Healthy V2 volumes work just fine (attach, detach, no problem). Degraded V1 volumes also work fine.
To Reproduce

On a 1 node cluster, create a V2 volume with replica level 3
Use the LH GUI to attach the volume to the node. Verify that the block device appears on the node by checking cat /proc/partitions and/or ls /dev/mapper/
Use the LH GUI to detach the volume. Check cat /proc/partitions and/or ls /dev/mapper/ and observe that the block device is gone.
Look at the state of the volume in the LH GUI. It should still (weirdly) be listed as attached on $hostname, even though the block device isn't present.
Try using the LH GUI to detach the volume. Nothing will happen (or, it might appear to briefly detach, then immediately re-attach).
Try using the LH GUI to force detach the volume. It will appear to briefly detach, then immediately re-attach again.
Despite the LH GUI saying the volume is attached, it won't really be attached (no block device is present on host).

Expected behavior
The volume detaches successfully and remains detached, until the user explicitly re-attaches it.
Support bundle for troubleshooting
supportbundle_4c24e4a0-5577-47fb-8e50-77f44df24739_2024-07-15T11-28-52Z.zip
Note that this supportbundle includes logs of reproducing this issue several times. The most recent attempt was made with a single 1GiB volume named v2-3r, created at 2024-07-15T11:25:56Z. Hopefully that helps to narrow things down.
Environment

Longhorn version: 1.6.2
Impacted volume (PV): v2-3r
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Harvester v1.3.1
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: v1.27.13+rke2r1

Number of control plane nodes in the cluster: 1
Number of worker nodes in the cluster: 0

Node config

OS type and version: Harvester v1.3.1 / SLE Micro 5.4
Kernel version: 5.14.21-150400.24.119-default
CPU per node: 10
Memory per node: 20GiB
Disk type (e.g. SSD/NVMe/HDD): SSD
Network bandwidth between the nodes (Gbps): N/A (only one node)

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): KVM
Number of Longhorn volumes in the cluster: 1

Additional context
Here's a video:
https://github.com/user-attachments/assets/a714274d-6355-4dd3-a4ae-bbb33dcf463a
This shows, on a single-node cluser:

Creating a single-replica healthy V2 volume (name: v2-1r), then successfully attaching and detaching it to and from the host.
Creating a three-replica degraded V2 volume (name: v2-3r), then successfully attaching it to the host, but failing to detach it as described in this issue.
Creating a three-replica degraded V1 volume (name: v1-3r), then successfully attaching and detaching it to and from the host.

You'll probably find all the above events in the attached supportbundle as well, but I can't say what the time indexes will be.

The reattachment after detaching a degraded v2 volume is caused by a bug of offline rebuilding. The offline rebuilding feature is removed from v1.7.0. I will resolve the issue in v1.6.3 rather than in v1.7.0. BTW, the offline rebuilding will be added back the later version.
@tserong Can you try v1.7.0-rc1 instead? Harvester v1.4.0 should pair with Longhorn v1.7.0. Thanks

@innobead Do we need to take time to fix the offline rebuilding bug in v1.6.3?

No need. It seems the issue has been fixed. Let's close this.


Warn on marking function with known side-effects with [PreferRecompute]

Right now, its possible to accidentally mark a method that relies on global/shared memory side-effects with [PreferRecompute]. The additional calls for recomputation will produce inconsistent output, and cause seemingly random gradients.
We should throw a warning if the compiler data-flow analysis detects a method with side-effects being marked recompute, and provide a way to suppress it if it is intentional (the user may be collecting statistics on how many times the method is recomputed, etc..)

Autodiff quality of life, putting in Q2 to reflect that


Docs

I noticed you dont support doc generation from code. Is this something you will add?

I personally haven't used automated doc generation for a long time, but it could be something interesting to look at. Is Doxygen still the standard tool for that?


datanode为只读状态，怎么解决呢

占用的磁盘是98%，但是我还剩下56g，整个磁盘是1.8t。

阈值为 5%
Disk remaining threshold at which DataNode is set to ReadOnly status
effectiveMode: restart
Datatype: double(percentage)
disk_space_warning_threshold=0.05


'garm-cli pool show' hides same values

So we have set Min Idle runners and Max Runners both to 20. The 20 in Min Idle Runners is hidden. When both values are different, both values are shown.
Before we also had Runner Bootstrap Timeout set to 20, in t his case both Min Idle Runners and Runner Bootstrap Timeout were empty.
Not really a big issue, but it was confusing why the settings were not correctly set at first, but it's just a display thing.
# garm-cli pool show f52a63ee-7af9-4a19-b7f0-4f1f67de1579
+--------------------------+----------------------------------------------------------+
| FIELD                    | VALUE                                                    |
+--------------------------+----------------------------------------------------------+
| ID                       | f52a63ee-7af9-4a19-b7f0-4f1f67de1579                     |
| Provider Name            | lxd_local                                                |
| Image                    | gh-ubuntu22-20230507-2.304.0-dockercache                 |
| Flavor                   | runner                                                   |
| OS Type                  | linux                                                    |
| OS Architecture          | amd64                                                    |
| Max Runners              | 20                                                       |
| Min Idle Runners         |                                                          |
| Runner Bootstrap Timeout | 10                                                       |

Ahh yes. This is due to AutoMerge being set to true in the cli:
https://github.com/cloudbase/garm/blob/main/cmd/garm-cli/cmd/pool.go#L505
I think we can disable AutoMerge for the second column. The AutoMerge option prevents printing the same row value on the same column. This is useful for the Instances row, where we may have multiple instances in a pool, and we don't want to have the first column contain the word Instances for each printed instance on the second column.
Testing it out.

This branch should take care of it: https://github.com/cloudbase/garm/pull/101


Converting Schema from STRING to JSON not working in pulsar function

I have a pulsar function, which will process the incoming STRING message convert it to JSON schema and publish it to output topic. Then pulsar sink will process it and saving into postgres db.
Implementation for the pulsar functions
context.newOutputMessage({pulsarsinkinputtopic}, Schema.JSON(POJO.class)).value().sendAsync();
To Reproduce
Steps to reproduce the behavior:

create a pulsar function and pulsar sink for postgres
upload a json schema for sink input topic
then produce message from java client
check the function log. showing error as class not found exception

Note: I tried Pulsar sink input topic accepts JSON Schema .

@Esakkimuthu991 Could you please provide the detailed stacktrace of the class not found exception? This is very useful for troubleshooting the problem.

Sorry for late response. The problem was occurred due to the jar generation. Now it resolved

Hi Easkkimuthu992,
How do you solve the issue? I have similar issue while using the class JSONSchema . Cam you give me a hand?


Vimeo integration

currently its upload the file in one request
we need to convert to multi part upload as Dailymotion support this with endpoint /rupload
i attach the pdf to the protocol is described in this NGinx upload module as they required: Resumable uploads over HTTP. Protocol specification.pdf


Add basic quickstart guide to readme

This adds a readme for #1
I based it off tests/Spec.hs and mainly consists of wrapping it in prose with links to some relevant external documentation of SendGrid or other Haskell libs.

Looks great, thanks!


Tracking issue: Tests with default checks disabled

In #263 we had to disable default checks in some tests to keep them working the same way. The affected tests are:

[ ] src/test/cbmc/CodegenConstValue/main.rs
[x] src/test/cbmc/DynTrait/boxed_closure.rs
[x] src/test/cbmc/DynTrait/dyn_fn_param.rs
[ ] src/test/cbmc/FunctionCall_Ret-Param/main.rs
[x] src/test/cbmc/PointerOffset/Stable/main.rs
[x] src/test/cbmc/PointerOffset/Unstable/main.rs
[ ] src/test/cbmc/Pointers_OtherTypes/main.rs
[x] src/test/cbmc/Strings/main.rs
[x] src/test/cbmc/SwitchInt/main.rs
[x] src/test/cbmc/Whitespace/main.rs
[x] src/test/firecracker/virtio-block-parse/main.rs

#335 removed the --no-memory-safety-checks flag in DynTrait/boxed_closure.rs

https://github.com/model-checking/rmc/pull/373 resolves DynTrait/dyn_fn_param.rs

#647 fixed the following tests:

src/test/firecracker/virtio-block-parse/main.rs
src/test/rmc/PointerOffset/Stable/main.rs
src/test/rmc/PointerOffset/Unstable/main.rs
src/test/rmc/Strings/main.rs
src/test/rmc/SwitchInt/main.rs
src/test/rmc/Whitespace/main.rs


add sds client/server example for manual testing

@wenchenglu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d113cffc4b999576459d0c4bfd598cedff9a6797
link
/test istio-unit-tests

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

done

/lgtm
We could add the server code to this package: https://github.com/istio/istio/tree/master/security/pkg/workload
This package holds libraries for interactions between node agent and workload for delivering key/cert, trust bundles, etc.

@wenchenglu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
aa0a2956f7077d12a0bc25d071e7abd2b2057c07
link
/test e2e-bookInfo

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

@wenchenglu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
aa0a2956f7077d12a0bc25d071e7abd2b2057c07
link
/test e2e-bookInfo

prow/e2e-simpleTests.sh
aa0a2956f7077d12a0bc25d071e7abd2b2057c07
link
/test e2e-simple

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

@myidpt
good point, will have a follow up cl to refactor this to library in the directory you suggested

Are there plans to aggregate SDS with regular xDS? Specifically, are there
any consistency issues with secrets not being available for routes?
On Tue, Feb 27, 2018, 10:37 AM Wencheng Lu<EMAIL_ADDRESS>wrote:

@myidpt https://github.com/myidpt
good point, will have a follow up cl to refactor this to library in the
directory you suggested
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/3803#issuecomment-368980549, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJGIxjRqbQ62gPk3BygceyJ9NU9YiBuAks5tZEsZgaJpZM4SUUrM
.

@wenchenglu That sounds good to me.

@kyessenov I think currently we don't plan to aggregate SDS with xDS. For the consistency issue, I guess we are still implementing the SDS on Envoy. I think it's reasonable to start with having Envoy disable the upstream traffic relying on the key/certs.

@kyessenov
This is solely for the bootstrap path to get key/cert locally from a local node agent. I don't expect aggregatingg SDS with xDS in this path. Once key/cert got bootstrapped for the workload, we might be able to aggregate SDS for remote key/cert exchange with other xDS if needed.
although I am not sure what you meant by "any consistency issues with secrets not being available for routes"?

For the 'client' side - it would be great to try it out by changing the envoy bootstrap file, so we can get a
test with the secret watcher disabled and real envoy getting secrets from the node agent. This may solve
quite a few problems, excited to see it moving ahead !

@wenchenglu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
12872ee1e944aa2736042b2e8cfabcff69f80962
link
/test e2e-simple

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

@myidpt @wenchenglu The consistency issue I have in mind is that if any LDS (or RDS?) resource references a secret that's not delivered through SDS, then those LDS/RDS resources get rejected by envoy. If they don't get rejected, envoy would blackhole the traffic since secrets are not delivered at the same time.

@kyessenov
Thanks for bringing up the consistency issue. This PR is mostly for bringing up SDS server on the node agent side. We will have a separate effort to address the client (Envoy) side regarding the LDS/RDS issue. @mangchiandjjoe is working on that. We can have this discussion separately.


Bump identity.org.mgt.version in pom.xml

Purpose
$subject

PR builder [7.x.x] started
Link: https://github.com/wso2/product-is/actions/runs/5335326307

PR builder [7.x.x] completed
Link: https://github.com/wso2/product-is/actions/runs/5335326307
Status: failure

PR builder [7.x.x] started
Link: https://github.com/wso2/product-is/actions/runs/5336420288

PR builder [7.x.x] completed
Link: https://github.com/wso2/product-is/actions/runs/5336420288
Status: success


Support for Discord.js V13

Any plans for making this compatible with discord.js version 13 that is currently in development? When I try to react to the message, nothing happens.

Hello! When discord.js v13 will be available as a stable release, I will add the support of course :+1:
As this a development release for now, apart from specific cases or testing bots, I think it should not be used for production bots.
Do you need it in a near future? I don't know if we can support both versions easily.

I would like to have it in the future, but I don't need it ASAP. I can wait until v13 becomes a stable release. I don't currently need support for v13, since production code is still written in v12. As for now, I have temporarily disabled the tic-tac-toe command for my bot's development for v13 of discord.js.

As the version 13 of discord.js is now out, I started to look into it. But I'm quite disappointed that it only supports Node 16+ which is not a LTS version. My module is intended to be used by all, I can't force all module users to use Node 16 for now. And I don't quite agree with the way the discord.js creators think.
Check the discussion on it on their repository: discordjs/discord.js#5119
BUT I will try to add support for both v12 and v13 and fix the bug you mentionned.
AND I'm waiting for a feedback from the discord.js team or the release of Node 16 in LTS (end of 2021).

Ah okay, thanks for the update. I do want to mention one thing I forgot, in case you haven't added it in the prototype; I am listening to interaction events instead of message events, which means that you would have to take in account for both slash commands and/or regular messages.

I have just writing a new issue on this subject yes! Check it here: #56

Version 3 of the module is now out with discord.js v13 support!
More info on the release here: https://github.com/utarwyn/discord-tictactoe/releases/tag/v3.0.0


Timinig issues with SystemJS

Hello,
when loading mdl with Systemjs the material.js is executed before the dom is ready. The stuff from window.addEventListener('load'.... is not executed at all. I think it's a timing issue. Do you plan to solve this issue or what is your proposal to be able to load mdl with Systemjs?
Thanks a lot.

Please use StackOverflow for support and integration assistance. This tracker is only for problems with the code provided by Material Design Lite.
Since your question is specifically about how we interact with some other JS code that isn't something we are able to support here.
Thank you.


Unclear explanation about operator precedence in concepts/conditionals

There's this bit of code in the Conditionals part of the syllabus that seems to be missing some brakets so that the explanation makes sense.
if (num >= 0 && num < 1) {
  // ...
}

// The inner brackets are obsolete because relational operators
// have higher precedence than logical operators.
if (num >= 0 && num < 1) {
  // ...
}

Thanks for creating the issue, I had this on my todo list as well. The inner brackets in the bottom example were removed by the auto-formatting. To make them stick, a prettier ignore block needs to be added.

If someone works on this, be aware that there might be multiple places where this same content (and issue) occurs. Please search to check for this and fix it in all the places if necessary.

Hello All,
I made a search to find any other places where this same content (and issue) occurs, but didn't find other than the issue mentioned, I solved it and made a pull request #1734


Spell Check: "Becaus" to "Because"

Loving this new initiative.

Thank you @asadrefai!  💜🧡


Small "scripting-sensitive" bug which expose some JS function

Challenge Add Borders Around your Elements has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
When  I write "do", the phone-simulator image on right is exposing this function:
if (loopProtect.protect({ line: 1 })) break; ; }
loopProtect.protect({ line: 1, reset: true });
````
The problem comes from the "do" keyword which messes with js I guess?

P.S I am trying to learn JS through your platform and... can you explain what the function does? Keeping proper length for each line to fit the phone-image? It would be of great help to me to know more

My code:
```html
do
<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.

```

I believe the problem is that you're using the command do which is part of the do...while statement. The editor is trying to protect you from creating an infinite loop which may crash the browser.

As @zelite said, this is because the editor is looking for a do function in JS.


SHOULD throw if time has an invalid value?

Describe the Bug
If an invalid value for time is given, HTTP.toEvent silently defaults it to the current time in UTC.
Steps to Reproduce
Use the following snippet:
const event = HTTP.toEvent({
  headers: {
    'Content-Type': 'application/json',
    'ce-id': '0815',
    'ce-specversion': '1.0',
    'ce-type': 'my.event.type',
    'ce-source': 'my.event.source',
    'ce-time': 'some invalid time string',
  },
  body: {}
})

Check the resulting event:
{
  //...
  id: '0815',
  specversion: '1.0',
  type: 'my.event.type',
  source: 'my.event.source',
  time: 2021-02-16T17:27:34+01:00 // defaulted date.now
}

Expected Behavior
As with the other issues I opened regarding (silent) defaulting, I think HTTP.toEvent should not do this. I think it would be more appropriate to either fail fast on invalid input or take the original value with a subsequent event.validate() failing (maybe also thinking about strict mode as for instance in event.cloneWith).
In case of new CloudEvent(...) I agree that it makes sense to provide defaults.
Additional context
Origin of this behavior seems to be here:
https://github.com/cloudevents/sdk-javascript/blob/6be3b2751401e529fce6ccf8a406a057472c10a9/src/parsers.ts#L68

In case of new CloudEvent(...) I agree that it makes sense to provide defaults.

I don't. I was suprised to find this. The field is optional - silently setting it is absolutely wrong imho and other SDKs don't do it (at least the Java one).

not stale


Update fastify/http-proxy for sec-eng issue

Signed-off-by: Zack Layne<EMAIL_ADDRESS>Related Issue:  stolostron/backlog#25312, stolostron/backlog#25313, stolostron/backlog#25345
Description of changes

Updated @fastify/http-proxy backend dep

/hold

/cherrypick release-2.4

/unhold


Support for running ROSMOD nodes with gdb

We have added valgrind support which is (somewhat) helpful for finding memory leaks and the like - but not as helpful in pinpointing what caused crashes or other issues.

Target systems need to have gdbserver installed
Host system (rosmod server) needs to have gdb-multiarch installed
start target programs with gdbserver :<port number> <program> <args>, e.g.
gdbserver :9092 rosmod_actor --config Node_1.config

They will not do anything until a gdb connects to them
start server process with gdb-multiarch <same binary executed on the remote target> followed by target remote <ip address>:<gdb server port>, e.g.
gdb-multiarch rosmod_actor
(gdb) target remote <IP_ADDRESS>:9092
...
(gdb) continue

Currently we have no way to send data to these processes or provide their output to the user - which would be needed for interactive debugging.  We will probably have to just spawn them with GDBServer and then let the user do  the debugging manually.
Note: The user will need to manually copy the rosmod_actor binary from the target to the server so that gdb-multiarch can load it.

Because of this, we will probably want to not start every ROSMOD node with gdbserver, but instead ask which node the user would like to debug.

I've added the ability to spawn a single node with gdbserver - which will put it on port 9092, this means that after the experiment starts you'll need to (from the ROSMOD server computer) run:
scp -i <key location> <user>@<host ip>:<path to rosmod_actor> .
# eg.
scp -i /home/jeb/.ssh/id_rsa_jetsontk1 debian@<IP_ADDRESS>:/opt/ros/kinetic/bin/rosmod_actor .
gdb-multiarch ./rosmod_actor
(gdb) target remote <host ip>:9092
...
(gdb) continue

which will get the rosmod_actor executable from the target architecture, connect to the running process and then tell it to continue execution - you can also do other things like stepping through, setting breakpoints, running to a line, etc.
Note: if you don't know where the rosmod_actor executable is on the target system, you can ssh into it, then run
source /opt/rosmod/setup.bash
which rosmod_actor

note: currently the execution of gdbserver is somehow messing with the StopExperiment plugin so those processes may need to be manually stopped (the plugin executes successfully and it copies the logs, but doesn't correctly stop the processes)

The plugin will (if you select to run a rosmod node with gdb) give you the specific instructions for connecting to the gdbserver - the commands (highlighted in black / green) are copy and paste-able into your terminal for execution directly.


How do i make the bot request maps?

I Can't figure this out, i have dug into the stuff in vscode
await game.request_map()
How do i make it request a map i want?

request_map() methods takes one argument - the map you want to request. It should be either Bonk1Map, Bonk2Map or OwnMap class that can be received from fetch_b1_maps(), fetch_b2_maps() and fetch_own_maps() methods in BonkBot class.

Also keep it mind that currently there's no support for bonk 1 maps (which will be added in the future), so basically you can only suggest bonk 2 maps (they also include own maps).


Update 1.2.1 for faster re-builds

See PR https://github.com/meteor/meteor/pull/5747
which was merged to current 1.3 as https://github.com/meteor/meteor/commit/a576bda03a584dda3ac5e6200bb207008cefd482

Honestly, backporting changes does not seem appropriate to me. In my opinion, we should better provide 1.3 beta releases (one branch for all the 1.3 releases?), to stick as much as possible to upstream.

Hi Thomas ( @TPXP )
you are right, I would not try to backport and I am already on the beta track for 1.3 on ARMs.
If I got it right, the linked merge just touches 2 files in a minor way. If this would drastically reduce rebuild times when running meteor on small boards, wouldn't this be a benefit?
Thanks for some more feedback
Tom

Hi Tom,
I definitely agree on the fact that this will be a great improvement, but why not release it with 1.3? This seems more logical to me, and more in accordance with upstream, and will avoid to have to ask "Hey! Which 1.2.1 version are you using?" if an issue pops up.
I understand it can seem a bit too rigorous, but I think we should be as close as possible to upstream because this makes it easier to track changes. I mean, even if it is a small change, it messes up a little bit more the things, and opens the way to deeper changes that are going to make it harder for our users to get help as we change things on our own.
Upstream is a kind of reference, that's why I think it is important to stay as close as possible to it!
Thomas

Hi Thomas
I normally would agree to your upstream policy (as close as possible) but I just think about that feature before this big coming 1.3 update from meteor. 1.3 will change meteor in many many parts so that 1.2.1 might be some long existing release for a number of users / developers.
That is the only reason why I think about to include that patch. If it would be just 1.2.2 which is in front of us, I never would think about some backwards patches.
Hard to take the right decision
Tom

I don't think the changes are that much radical, at least the changelog does not mention breaking changes (except maybe Cordova, but it's it going to change a lot of things on our side?). So in my opinion porting 1.3 should not take a long time. Furthermore, there is no urgent need for this (nobody actually asked for it..), so why not waiting 1.3?
Anyway creating a 1.2.2 pseudo release seems to me as a very bad option because it will really introduce a confusion between our users and upstream users. I cannot help but imagine some comments on help requests like "Oh, you got 1.2.2. How is that possible?", making it - again - harder to get help.
Maybe we can find a compromise by providing a patch file, that the user can apply? This way the user is aware of this, so he knows what he is doing. ☺

I will check again the changes to 1.3 if I have interpreted too excesive their changes ... If so, I would really like that ;-) and we will just build the next 1.3
In addition to just mark another hint in section "README/Good to know" would be far enough for this patch (like a cherry-pick)

I think this issue is less relevant / might be closed with 1.3 having been released today and I think this repo's target will be to follow up with building that instead of focussing on 1.2.1.

As we currently working out the 1.3 - I will follow @TPXP  and @rjhllr  and do not invest in that issue. Anyone like or need please check out 1.3 from our fork which will be available soon.
Thanks supporting us.


[AIRFLOW-3241] Remove Invalid template ext in GCS Sensors

Remove template_ext = ('.sql',)
Fix Docstrings (Incorrect connection name and indentation)

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-3241

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

It uses google_cloud_storage_conn_id instead of google_cloud_conn_id

Docstrings have unncessary indentation which causes the docs to not parse it

The GCS sensor also contains an incorrect template extension

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes flake8

Codecov Report

Merging #4076 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4076   +/-   ##
=======================================
  Coverage   77.88%   77.88%
=======================================
  Files         199      199
  Lines       15957    15957
=======================================
  Hits        12428    12428
  Misses       3529     3529

Continue to review full report at Codecov.

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


Constraint files

Hi, @dspsandbox Thanks for your work and for sharing your knowledge- I am also from a physics background this is very helpful for me. I would like to ask where can i download the Red-Pitaya 125-14 constraints file? as the provided link seems not to be working.
Thanks

Hi @Gmotion94, I am glad to hear that the tutorial is useful to you. The constraints file is here; FPGA-Notes-for-Scientists/sdc/redpitaya-125-14.xdc
BR,
Pau

@dspsandbox another issue I'm having is that the suggested prebuilt board agnostic is "PYNQ rootfs arm v2.6" however on the link: http://www.pynq.io/board.html/ the minimum is 2.7, not 2.6 any suggestions on that?

Hi Paul
May i please bother you again: so i have followed all the instructions on tutorial 1(LED_BLINK) on Vivado up-to generating the bitstream file (overlay)

However when i program the Red-Pitaya with the overlay image i'm getting an error.


FileDecoration.propogate does not work on some URIs

VS Code Version: 1.74.3
OS Version: MacOS

Observer the following behavior when  in my extension, using FileDecorationProvider API - propagate property works only if:

Decorated and parent node resourceUris has same URI scheme.
URIs consist only of scheme and path. Wherever I add fragment or query it stops propagating.

Before I go on and prepare example extension, is this an expected behavior or a bug?

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.74.3. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

is this an expected behavior or a bug?

Maybe ;-) The fragment isn't part of the document's identify, the query arguably is. Tho, I believe in other cases we ignore both. @bpasero please help me recall what we did in other, related cases like file events etc? Do we ignore both or just fragment?

We typically use the TernarySearchTree and I see no use of the extra option to ignore query and fragment, so I actually think for these cases we respect both query and fragment:
https://github.com/microsoft/vscode/blob/e120d5a1252f6a9b32732c6781e781087b3bebdb/src/vs/platform/files/common/files.ts#L830-L841
https://github.com/microsoft/vscode/blob/e120d5a1252f6a9b32732c6781e781087b3bebdb/src/vs/platform/files/common/fileService.ts#L215
Even when it comes to workspace folders where we use it to find out if a file is inside a workspace or not we seem to respect it:
https://github.com/microsoft/vscode/blob/e120d5a1252f6a9b32732c6781e781087b3bebdb/src/vs/platform/workspace/common/workspace.ts#L332

Thanks. Looks like workspaces ignore them but usually we are "strict"

Oh yeah, I misread, indeed workspace is different here...

Looks like that came in from https://github.com/microsoft/vscode/pull/146859

Closing this as designed


Missing terminal new window not working properly despite https://github.com/microsoft/vscode/issues/10121

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.89
OS Version: Linux RHEL 9 based

Steps to Reproduce:

Not reproducible as its not possible

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.90.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

pls create a new issue with repro steps, your expectation,and what's actually happening


unit-test needs to be updated

unit-test needs to be updated
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/setup-go@v1. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

Node 12 has been out of support since April 2022, as a result we have started the deprecation process of Node 12 for GitHub Actions. We plan to migrate all actions to run on Node16 by Summer 2023.


buttonColor prop not working on selected radio button

Here is my code:
            <RadioForm                 formHorizontal={true}                 labelHorizontal={true}                 radio_props={radio_props}                 initial={-1}                 onPress={(value) => {                   setOutsideRadio(value);                 }}                 buttonColor={'gold'}                 labelColor={'gold'}               />             </View>
I would expect the button color to be gold but the selected radio button defaults to blue:

Let me know if that is an actual issue or just user error!

Ohh turns out selectedButtonColor is a prop as well! Thanks!


Update SMS Templates

Is your feature request related to a problem? Please describe.
Update approved SMS templates
https://docs.google.com/spreadsheets/d/1Mt9_UI7LN3kuybaYocJkV8iRgbYfFefn_cuv5GJDcyo/edit?usp=sharing

https://docs.google.com/spreadsheets/d/1Mt9_UI7LN3kuybaYocJkV8iRgbYfFefn_cuv5GJDcyo/edit?usp=sharing
The sms templates have been approved. Kindly test this in one of the environments.

Updated SMS templates required from Day 1 https://docs.google.com/spreadsheets/d/1Mt9_UI7LN3kuybaYocJkV8iRgbYfFefn_cuv5GJDcyo/edit?gid=423958552#gid=423958552


[core] Download tracker rename

Renamed the downloads tracker to remove the internal from its name as it apparently prevents the package from being published: https://github.com/npm/validate-npm-package-name/issues/49.
Also removed the unnecessary index.js file.

remove the internal from its name

I believe the issue is with "download" that we renamed to "downloads" 😁

I believe the issue is with "download" that we renamed to "downloads", at least from what works 😁

Honestly, I couldn't care less now that it works, but I do hope they will update their docs


pgvector.Vector vs. []float32

What is the benefit of using pgvector.Vector type instead of directly using []float32 with pgx v5 driver? I haven't tried but it looks like   []float32 would work as well.

Hi @acim, []float32 already maps to the real[] Postgres type.

But would []float work with database vector type?

I can confirm this worked with pgx5.

It'll work in places where there's implicit conversion from real[] to vector, but not everywhere (remove newVector from the SELECT call in the tests to see).


Add words "public domain"

I always need to look up that CC0 == Public Domain.   Added it.

Very good point, thanks!


Next.js server side rendering warning, need to provide

Discussed in https://github.com/supabase/supabase/discussions/2368

Originally posted by mstibbard July 15, 2021
I'm currently trying out supabase auth and Next.js and it's been fantastic so far! However, when running yarn dev I occasionally get the following warning in the terminal.
When server rendering, you must wrap your application in an <IdProvider> to ensure consistent ids are generated between the client and server.
Is this ID not provided by the Auth.UserContextProvider?
pages/_app.tsx
import '../styles/globals.css';
import { supabase } from '../utils/supabaseClient';
import { ThemeProvider } from 'next-themes';
import type { AppProps } from 'next/app';
import { Auth } from '@supabase/ui';

export default function MyApp({ Component, pageProps }: AppProps) {
  return (
    <Auth.UserContextProvider supabaseClient={supabase}>
      <ThemeProvider attribute='class'>
        <Component {...pageProps} />
      </ThemeProvider>
    </Auth.UserContextProvider>
  );
}

and
../utils/supabaseClient
import { createClient } from '@supabase/supabase-js';

const supabaseUrl: string = process.env.NEXT_PUBLIC_SUPABASE_URL!;
const supabaseAnonKey: string = process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!;

export const supabase = createClient(supabaseUrl, supabaseAnonKey);
```</div>

Does not look like a UI lib issue. Although I'll follow it in Discussions

I came across this looking for something else, but this is (or was) required by radix-ui components @MildTomato - which is why users of the lib may hit this if they don't have that provider.


if there is only one device connected via adb, don't ask for a serial ?

If adb device return only one device, we can assume it's the good one and use its serial ?
I think it's pretty convenient to be able to just run the script as is without having to do extra steps (simple and fast, I agree) to get the device serial every time.
I would be glad to do a pull request to add that feature, I just wanted to know your opinion about it ?

I have a version with awk, tell me if that's a problem I can switch to sed it will just to take more space

Hey @mirsella,
Thanks for bringing this up. It's been a while since I wrote this script, but I do remember thinking of automatically fetching the serial and then fetching the snaps. I think the reason why I did not implement that feature was because of some issues with ADB and the Android device not being authorized as shown in the screenshot below:

But I'm not 100% sure that's was the reason why I did not implement that feature though.
Feel free to create a PR and I'll test it out. If it does not create any issue I'll go ahead and merge it :+1:

I have a version with awk, tell me if that's a problem I can switch to sed it will just to take more space

awk should be fine

Instead of using adb without -s, I thought of setting the SERIAL variable to the serial of the only connected device if only one is connected, so this problem shouldn't apply.
I'll create a pull request soon.
Thanks !


[Bug] On rancher server upgrade and roll back, downstream clusters webhook version needs to be downgraded

Information about the Cluster
Rancher Server Setup

Rancher version: v2.7.4 upgraded to v2.7-head 0bcf068  rolled back to 2.7.2
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1, v1.25.6, v1.4.5 Hardened

Proxy/Cert Details: Self-signed

Information about the Cluster

Kubernetes version: 1.25 RKE2 and RKE1 node driver clusters
Cluster Type (Local/Downstream): 1 etcd, 1 cp, 1 worker

Describe the bug
When we upgrade and roll back rancher server from v2.7.4 >> v2.7-head >> v2.7.4 or v2.7.2 >> v2.7.3 >> v2.7.2 , downstream clusters webhook version is not upgraded but the local cluster webhook version is downgraded to the required version.
To Reproduce

Install rancher on version 2.7.4
Create a custom RKE1 and RKE2 cluster with the specs mentioned above.
Install rancher backup/restore chart version in the local cluster with config set to S3
Take a backup from the rancher backup/restore page and the backupfile gets saved in the s3.
Upgrade rancher server to v2.7-head
Rollback to 2.7.4 by following the docs
Bring down the nodes of current rancher local cluster
Migrate rancher to v2.7.0 by following instructions here https://ranchermanager.docs.rancher.com/v2.7/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/restore-rancher-launched-kubernetes-clusters-from-backup

Result
Once the migration is successful, and rancher is installed if we navigate to downstream clusters, we notice the webhook version stays at the version of v2.7-head and is not compatible with the local cluster webhook version.
Expected Result
Webhook on downstream clusters stay compatible with local cluster

Fix is going to be an update for the script https://github.com/rancherlabs/support-tools/tree/master/remove-webhook

Release note here handled by: https://github.com/rancher/rancher/issues/41730#issuecomment-1601373796

Verified on a roll back from v2.7.4 >> v2.7-head fda4d4d >> v2.7.4

Webhook on downstream clusters after running the script is restored to the min version 2.0.4+up0.3.4

Verified on a roll back from v2.7.1 >> v2.7-head fda4d4d >> v2.7.1

Webhook on downstream clusters is removed.

Ran the script by providing the rancher url, api token:
read -s RANCHER_TOKEN && export RANCHER_TOKEN
read -s RANCHER_URL && export RANCHER_URL
bash adjust-downstream-webhook.sh --insecure-skip-tls-verify


chore: ignore empty condition in type restriction definitions

Description
The validation rule should only apply to the condition in a RelationReference (which is used for type restrictions) if the condition is not empty (e.g. ""). This ensures that is the case.
References

Review Checklist

[x] I have clicked on "allow edits by maintainers".
[x] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[x] I have added tests to validate that the change in functionality is working as expected

diff on the OpenAPI is alright - it's a false positive.


Weird "{" bug in grammar file javascript section.

In the top part of the grammar, where you would define your JavaScript helper functions, etc. - it seems like it is trying to match the number of open and closing "{" / "}" quite 'literally'.
I have a case where I got an extra opening "{" - but it is inside a javascript string literal, so it is not an actual "{"
This is the code:
{
var g = "{" // <- ha!
}
And this is the error: Line 1, column 1: Expected code block, comment, end of line, identifier or whitespace but "{" found.

There is also a hack around this, you just need to add a closing "}" somewhere (e.g. inside a comment) var g = "{"; //  } <- hacked! But I think this should be fixed.

Sorry, I just noticed this line in the documentation:

Curly braces in the initializer code must be balanced.

So this is probably a known behaviour, in that case - please feel free to close this issue.

Duplicate of #89.


Export PDF code blocks are not legible in dark mode

Is the bug present when using the default Obsidian theme?
No
Is the bug present when snippets and plugins are disabled?
Yes
Minimal theme version
6.1.17
Describe the bug
Steps to reproduce

Show Debug Info > Sandbox Vault
Add a code block, like so:

Export to PDF. The code block is legible.

Switch to light mode

Export PDF again. Code block is still legible

Now install Minimal theme and use it, use light mode, export PDF, code block still legible

Switch to dark mode, export PDF again. Code block is not legible

Expected

Dark Mode Export PDF should have legible code block

Actual

Dark Mode Export PDF does not have legible code block

Debug info
SYSTEM INFO:
Obsidian version: v1.1.8
Installer version: v1.1.8
Operating system: Windows 10 Pro 10.0.22621
Login status: logged in
Catalyst license: none
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: Minimal v6.1.17
Snippets enabled: 0
Restricted mode: off
Plugins installed: 0
Plugins enabled: 0
RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.

Same issue for in-line code, just to remind.


Use of render in docs

https://polymer.github.io/lit-html/guide/index.html demonstrates using lit's render function.
https://polymer.github.io/lit-html/guide/writing-templates.html includes multiple examples of writing your own render function.
This feels confusing given the naming. Is one supposed to be instead of the other? Are they supposed to do similar things?
Feels like the render functions in the "writing templates" doc should be called something else.

Duplicate of #277

Ah, yes


remove should be optimized

With JsonPtr we walk the tree from the root, since we have information about every parent node, there is an opportunity for a more optimized implementation based on prepare/patch

interesting benchmark
posFromPtr:
  Collected 1000000 samples in 2.3879 s
  Average time: 0.0016 ms
  Stddev  time: 0.0002 ms
  Min     time: 0.0001 ms
  Max     time: 0.0207 ms
270
traverse:
  Collected 1000000 samples in 1.9752 s
  Average time: 0.0012 ms
  Stddev  time: 0.0001 ms
  Min     time: 0.0000 ms
  Max     time: 0.0255 ms
270
parent:
  Collected 1000000 samples in 1.9107 s
  Average time: 0.0011 ms
  Stddev  time: 0.0000 ms
  Min     time: 0.0000 ms
  Max     time: 0.0051 ms

Working backwards is as slow as the opposite with all those string comparisons but faster than splitting the string.

fixed in 472561e5dd28f88fc9945f488872055fb26711c5 . It need a benchmarks.

Code that got discarded, it used an iterator
iterator posFromPtr(tree: JsonTree; path: string; n: NodePos; noDash = true): NodePos =
  # Warning: must break from the iterator manually when nilNodeId is returned.
  var n = n
  yield n
  var cur = ""
  var last = 1
  while last <= len(path):
    var first = last
    while last < len(path) and path[last] != '/':
      inc(last)
    let last1 = last == len(path)
    copyTokenToBuffer(cur, path, first, last)
    case n.kind
    of opcodeObject:
      unescapeJsonPtr(cur)
      n = rawGet(tree, n, cur)
      if not n.isNil: yield NodePos(n.int-2)
      yield n
    of opcodeArray:
      var i = getArrayIndex(cur)
      if i == -1:
        if not noDash and last1: yield NodePos(n.int+n.operand); break
        else: raiseSyntaxError(path)
      block searchLoop:
        for x in sonsReadonly(tree, n):
          if i == 0:
            n = x
            break searchLoop
          dec i
        yield nilNodeId
    else: yield nilNodeId
    inc(last)

proc remove*(tree: var JsonTree, path: JsonPtr) =
  ## Removes `path`.
  var insertPos: seq[PatchPos] = @[]
  for x in posFromPtr(tree, path.string, rootNodeId):
    if x.isNil: break
    insertPos.add x.PatchPos
  var n = insertPos.pop().int
  if insertPos.len > 0 and kind(NodePos insertPos[^1]) == opcodeKeyValuePair:
    n = insertPos.pop().int
  let diff = span(tree, n).int32
  while insertPos.len > 0:
    let pos = insertPos.pop().int
    let distance = tree.nodes[pos].operand - diff
    tree.nodes[pos] = toNode(tree.nodes[pos].kind, distance)
  let oldfull = tree.nodes.len
  for i in countup(n, oldfull-diff-1): tree.nodes[i] = tree.nodes[i+diff]
  setLen(tree.nodes, oldfull-diff)

proc posFromPtr(tree: JsonTree; path: string): NodePos =
  result = nilNodeId
  for x in posFromPtr(tree, path.string, rootNodeId):
    result = x
    if x.isNil: break


Build for SemigroupMonoidProposal

See https://prime.haskell.org/wiki/Libraries/Proposals/SemigroupMonoid#Writingcompatiblecode

I send this pull request, as the build failed for me with ghc-8.4.3 due to this Semigroup issue.

Thanks! I think it is ok to just lock the base and semigroups version to GHC 8.4+, but will make a release with this PR because I am too lazy ;)


Create data source in a provider

Hi,
I would like to be able to create data sources instead of resources only in a terraformer provider. In the case of the keycloak provider, when we create a keycloak_realm, keycloak creates automatically some keycloak_openid_clients in the master realm and some keycloak_openid_clients in every realm created.
At the moment, my provider imports all these resources as resources, and it works; but only if they already exist. When I try to apply the resulting terraformer import to a new installation, it doesn't work because I have some conflicts for all these openid_clients, because the new IDs are not equal to the old ones.
In terraform_utils, we only can create NewResource, not NewData... Maybe I could workaround this by using a PostConvertHook and transform some resources in datasources, but I don't think that it would be a good pattern (and what would I do for the tfstate ?).
Regards,
Pierre

Maybe connecting between resources can help you here
See example here https://github.com/GoogleCloudPlatform/terraformer/blob/master/providers/aws/aws_provider.go#L49-L139
Terraformer can connect between resources in terraform style ${provider_resource_type.resource_name.id}

Yes I know, I am already doing such connections (https://github.com/GoogleCloudPlatform/terraformer/blob/master/providers/keycloak/keycloak_provider.go#L100-L122), but that's not enough, when creating a resource triggers the creation of other resources (with different IDs than the one we had imported).


sap.m.Select can be activated and changed while deactivated with spacebar in Internet Explorer

In this sample when running in Internet Explorer
http://plnkr.co/edit/ZUWTMeF7YbAfZdx5S9EM?p=preview
the select control can be selected by the mouse and then by pressing spacebar the option list pops-up.
This can then be changed even though the control is not enabled.
In other browsers, Chrome, Firefox and Edge this doesnt happen.
Can you please investigate.

Tried with some older libraries - this issue seems to have appeared with the 1.32 release.

For reference the version of IE was 11.0.14

@njames Thanks for reporting this issue, it is a good repro. Internal reference<PHONE_NUMBER>.

The issue is fixed in the following OpenUI5 versions:
1.38
1.36.1
1.34.5
1.32.11
Just to mention that the root cause of the issue is an Internet Explorer 11 (IE 11) bug. IE 11 focus non-focusable elements via click. Hopefully, this issue has been fixed in the new Microsoft Edge browser.
I have created a code snippet to reproduce this issue:
http://jsbin.com/golewu/edit?html,css,output

Thank you @arleytriana


Hours stuck on pressing up/down hours arrows

I'm Submitting a ...

[X] Bug report
[ ] Feature request
[ ] Support request

Steps to Reproduce
Go to demo page
Select time, then press on up/down links for hours til hours get stuck.
Chrome 61 on macOS
e.g. stuck at 3am

Safari 11 on macOS
e.g. stuck at 1am

Expected Results
Hours should increase/decrease with clicking on hours buttons.
Actual Results
Hours gets stuck increase/decrease with clicking on hours buttons.

This is weird. I just tried this on my Mac with Chrome 61 and Safari 11 and it works. I tried clearing my cache in Chrome before it as well.
@lukeaus could you try clearing your cache? Idk what else could be wrong.

Thanks for getting back to me @simeg.
Yeah it's weird. I just tried on both browsers using the steps to reproduce and now it works.
I haven't looked at the code but there must be something going on as it happened in 2 different browsers.

Yeah, that it's happening in two browsers speaks for something else being wrong, you're correct.
Anyway, closing this for now since it's working for you.

OK. Let's see if anyone else runs into this one.