Workflow is sometimes interrupted

Pre-requisites

[X] I have double-checked my configuration
[X] I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
[X] I have searched existing issues and could not find a match for this bug
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened? What did you expect to happen?
A CronWorkflow running every 10 minutes occasionally gave the error `Stopped with strategy 'Terminate'' and detected cronworkflows_concurrencypolicy_triggered. We checked the workflow executed immediately afterwards and found no elements triggering concurrencyPolicy.
Failed Workflow
monitor-argo-workflows-1734498600.txt
Workflow immediately after
monitor-argo-workflows-1734498000.txt
Looking at the failed workflow, it is interrupted 10 seconds after start (2024-12-18T05:00:10Z), but has not met the next schedule (2024-12-18T05:10:00Z) of CronWorkflow.
    monitor-argo-workflows-1734498000-4221058204:
      id: monitor-argo-workflows-1734498000-4221058204
      name: monitor-argo-workflows-1734498000(0)
      displayName: monitor-argo-workflows-1734498000(0)
      type: Pod
      templateName: main
      templateScope: local/monitor-argo-workflows-1734498000
      phase: Failed
      message: "workflow shutdown with strategy:  Terminate"
      startedAt: "2024-12-18T05:00:00Z"
      finishedAt: "2024-12-18T05:00:10Z"
      progress: 0/1
      nodeFlag:
        retried: true

Version(s)
v3.6.2
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflow that uses private images.
apiVersion: argoproj.io/v1alpha1
kind: CronWorkflow
metadata:
  name: monitor-argo-workflows
spec:
  suspend: false
  schedule: "*/10 * * * *"
  timezone: "Asia/Tokyo"
  concurrencyPolicy: Replace
  startingDeadlineSeconds: 60
  workflowSpec:
    entrypoint: main
    activeDeadlineSeconds: 480
    templates:
      - name: main
        retryStrategy:
          retryPolicy: Always
        container:
          name: main
          image: public.ecr.aws/docker/library/busybox:latest
          command: [echo]
          args: ["hello world"]
          resources:
            limits:
              cpu: 100m
              memory: 32Mi
            requests:
              cpu: 100m
              memory: 32Mi

Logs from the workflow controller
I got this from cloudwatch, so the format may not be what it is supposed to be
---
| @timestamp | pod | log |
| --- | --- | --- |
| 2024-12-18 05:00:41.020 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:41.019Z" level=info msg="Successfully request 'edge-workflow/monitor-argo-workflows-1734498000' to be deleted" |
| 2024-12-18 05:00:41.001 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:41.001Z" level=info msg="Deleting garbage collected workflow 'edge-workflow/monitor-argo-workflows-1734498000'" |
| 2024-12-18 05:00:15.395 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:15.394Z" level=info msg="cleaning up pod" action=deletePod key=edge-workflow/monitor-argo-workflows-1734498000-main-4221058204/deletePod |
| 2024-12-18 05:00:10.435 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.435Z" level=info msg="Queueing Failed workflow edge-workflow/monitor-argo-workflows-1734498000 for delete in 30s due to TTL" |
| 2024-12-18 05:00:10.394 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.394Z" level=info msg="archiving workflow" namespace=edge-workflow uid=ca75c8ee-0609-4f16-994c-7fe168f8f1eb workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.376 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.376Z" level=info msg="Workflow update successful" namespace=edge-workflow phase=Failed resourceVersion=410659688 workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.364 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.364Z" level=info msg="cleaning up pod" action=deletePod key=edge-workflow/monitor-argo-workflows-1734498000-main-4221058204/deletePod |
| 2024-12-18 05:00:10.358 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.358Z" level=info msg="cleaning up pod" action=terminateContainers key=edge-workflow/monitor-argo-workflows-1734498000-main-4221058204/terminateContainers |
| 2024-12-18 05:00:10.354 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.354Z" level=info msg="Running OnExit handler: exit-handler" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.354 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.354Z" level=info msg="Updated phase Running -> Failed" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.354 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.354Z" level=info msg="Updated message  -> Stopped with strategy 'Terminate'" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.354 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.354Z" level=info msg="Marking workflow completed" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.354 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.354Z" level=info msg="Marking workflow as pending archiving" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.353 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.352Z" level=info msg="Task-result reconciliation" namespace=edge-workflow numObjs=0 workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.353 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.353Z" level=info msg="node changed" namespace=edge-workflow new.message="Unschedulable: 0/8 nodes are available: 1 node(s) had untolerated taint {quipper.dev/karpenter: deprecated-amd64-no-disruption-nodepool}, 3 node(s) didn't match Pod's node affinity/selector, 4 node(s) had untolerated taint {eks.amazonaws.com/compute-type: fargate}. preemption: 0/8 nodes are available: 8 Preemption is not helpful for scheduling." new.phase=Pending new.progress=0/1 nodeID=monitor-argo-workflows-1734498000-4221058204 old.message= old.phase=Pending old.progress=0/1 workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.353 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.353Z" level=info msg="Terminating pod as part of workflow shutdown" namespace=edge-workflow podName=monitor-argo-workflows-1734498000-main-4221058204 shutdownStrategy=Terminate workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.353 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.353Z" level=info msg="node monitor-argo-workflows-1734498000-4221058204 phase Pending -> Failed" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.353 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.353Z" level=info msg="node monitor-argo-workflows-1734498000-4221058204 message: workflow shutdown with strategy:  Terminate" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.353 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.353Z" level=info msg="node monitor-argo-workflows-1734498000-4221058204 finished: 2024-12-18 05:00:10.353200692 +0000 UTC" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.353 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.353Z" level=info msg="Stopped with strategy 'Terminate'" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.353 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.353Z" level=info msg="node monitor-argo-workflows-1734498000 phase Running -> Failed" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.353 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.353Z" level=info msg="node monitor-argo-workflows-1734498000 message: Stopped with strategy 'Terminate'" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.353 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.353Z" level=info msg="node monitor-argo-workflows-1734498000 finished: 2024-12-18 05:00:10.353807224 +0000 UTC" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:10.351 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:10.351Z" level=info msg="Processing workflow" Phase=Running ResourceVersion=410659555 namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.475 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.474Z" level=info msg="Update retry attempt 1 successful" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.475 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.474Z" level=info msg="Workflow update successful" namespace=edge-workflow phase=Running resourceVersion=410659555 workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.436 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.436Z" level=warning msg="Error updating workflow: Operation cannot be fulfilled on workflows.argoproj.io \"monitor-argo-workflows-1734498000\": the object has been modified; please apply your changes to the latest version and try again Conflict" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.436 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.436Z" level=info msg="Re-applying updates on latest version and retrying update" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.423 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.422Z" level=info msg=reconcileAgentPod namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.422 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.422Z" level=info msg="Created pod: monitor-argo-workflows-1734498000(0) (monitor-argo-workflows-1734498000-main-4221058204)" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.422 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.422Z" level=info msg="TaskSet Reconciliation" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.411 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.411Z" level=info msg="stopping 'monitor-argo-workflows-1734498000'" namespace=edge-workflow workflow=monitor-argo-workflows |
| 2024-12-18 05:00:00.280 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.279Z" level=info msg="stopping 'monitor-argo-workflows-1734498000'" namespace=edge-workflow workflow=monitor-argo-workflows |
| 2024-12-18 05:00:00.164 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.164Z" level=info msg="was unable to obtain node for , letting display name to be nodeName" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.164 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.164Z" level=info msg="Retry node monitor-argo-workflows-1734498000 initialized Running" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.164 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.164Z" level=info msg="was unable to obtain node for , letting display name to be nodeName" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.164 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.164Z" level=info msg="Pod node monitor-argo-workflows-1734498000-4221058204 initialized Pending" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.164 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.164Z" level=warning msg="couldn't get boundaryTemplate through nodeName monitor-argo-workflows-1734498000(0)" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.163 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.163Z" level=warning msg="Node was nil, will be initialized as type Skipped" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.161 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.161Z" level=info msg="Task-result reconciliation" namespace=edge-workflow numObjs=0 workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.161 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.161Z" level=info msg="Updated phase  -> Running" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.152 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.152Z" level=info msg="Processing workflow" Phase= ResourceVersion=410659527 namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
---

Logs from in your workflow's wait container
kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

| 2024-12-18 05:00:00.436 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.436Z" level=warning msg="Error updating workflow: Operation cannot be fulfilled on workflows.argoproj.io \"monitor-argo-workflows-1734498000\": the object has been modified; please apply your changes to the latest version and try again Conflict" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |
| 2024-12-18 05:00:00.436 | workflow-controller-987cc9b94-fr88f | time="2024-12-18T05:00:00.436Z" level=info msg="Re-applying updates on latest version and retrying update" namespace=edge-workflow workflow=monitor-argo-workflows-1734498000 |

The logs indicate that a conflict occurred while updating the workflow. Is it possible that the current workflow was terminated somewhere else?

Thanks for confirming.
No elements were found to interrupt this Workflow.
The Workflow manifest attached to the body of the Issue is for this and the immediate runtime, but it did not take long enough for the ConcurrencyPolicy to have any impact.


Imported data from wakatime doesn't match the actual data.

Describe the bug
When I am trying to import the data from wakatime , I am not getting the full information, just part of it. It can be seen by checking the total time. On wakatime I get the following output
, while on my self hosted instance of wakapi this.

Same goes for the whole statistics, it doesn't match the data provided in the wakatime dashboard.
It seems, it can't insert all the imported hearbeats into sqlite database.
Mar 08 11:43:17 ip-******* wakapi[26507]: 2022-03-08T11:43:17.82956296Z [WARN ] failed to insert imported heartbeat, already existing? - too many SQL variables
Mar 08 11:43:18 ip-******* wakapi[26507]: 2022-03-08T11:43:18.111405612Z [WARN ] failed to insert imported heartbeat, already existing? - too many SQL variables
Mar 08 11:43:18 ip-******* wakapi[26507]: 2022-03-08T11:43:18.119789307Z [WARN ] failed to insert imported heartbeat, already existing? - too many SQL variables
Mar 08 11:43:18 ip-******* wakapi[26507]: 2022-03-08T11:43:18.425061063Z [INFO ] downloaded 31872 heartbeats for user 'Fom123' (6134 actually imported)

Same problem was in the #206 issue. It was resolved by setting app.import_batch_size to 50, so I have tried to set it to 20 and still I haven't got the whole statistics.

Now I see the following in the logs:
Mar 08 13:18:43 ip-******* wakapi[27378]: 2022-03-08T13:18:43.827091656Z [INFO ] downloaded 31872 heartbeats for user 'Fom123' (28440 actually imported) but with no warnings.
Why is this actually imported thing happens?
System information

Wakapi version: 2.2.4
Linux: Ubuntu 20.04.3 LTS
Docker: no
Database: sqlite

Thanks for that super detailed bug report! First of all, please note that WakaTime and Wakapi will never show the same total time. That is due to the fact that they estimate that time differently, see our FAQ. Unfortunately, there is no right or wrong here and we can't for sure know precisely what the actual, true coding time was, only judging by heartbeats. Calculations are just heuristic.
If there is a discrepancy between heartbeats downloaded and heartbeats actually inserted, but no warning, it might be due to the fact that duplicates have been filtered, see here: https://github.com/muety/wakapi/blob/85515d6cb551a20f574e26300466425470c0bb18/services/heartbeat.go#L62
Two heartbeats are considered duplicates of each other of the following of their properties have identical values: user_id, entity, type, category, project, branch, language, is_write, time. Would be interesting to know of WakaTime API returns duplicates (by that definition), but I don't see any other reason.
Btw., WakaTime import will (hopefully) be refactored soon, see https://github.com/muety/wakapi/issues/323.
Moreover, if it's not too much of a hassle for you, I'd recommend to use MySQL or Postgres as a database in favor of SQLite as there have been a few problem with SQLite in the past (including the one you came across).

Thanks, I understand now. However, I think there should be warning about using sqlite in FAQ

It's not really like you shouldn't use SQLite, but I'd rather prefer a "proper" DMBS as the recommended way (mentioned here) for people with technical affinity.


Add {attempt} expansion to configuration

Is your feature request related to a problem? Please describe.
I only want to be emailed by SLURM when the job that I submit fails on its last retry.
Describe the solution you'd like
I want to be able to configure this in my profile's config.yaml:
restart-times: 1
cluster:
  sbatch:
     --account XXX
     --partition XXX
     $(if (({attempt} == 2)) ; then echo '--mail-type FAIL --mail-user<EMAIL_ADDRESS>; fi)
     # ...

But trying to expand {attempt} throws a NameError.
Describe alternatives you've considered
I used the solution from this issue ( https://github.com/snakemake/snakemake/issues/742 ). I'm creating a new issue, since they're asking for this feature in cluster config, which is deprecated. I want this in profile configuration
What currently works: In my profile's config.yaml:
restart-times: 1
resources:
  - attempt=0 # this doesn't correspond to the retry attempt. That needs to be manually set in the snakefile
cluster:
  sbatch:
     --account XXX
     --partition XXX
     $(if (({resources.attempt} == 2)) ; then echo '--mail-type FAIL --mail-user<EMAIL_ADDRESS>; fi)
     # ...

My snakefile:
rule test:
  output:
    'test.txt'
  resources:
    attempt = lambda wildcards, attempt: attempt
  run:
    assert False

This only emails me on the second attempt. But I have to insert the attempt resources into every rule for which I wish this to be true.

Does setting default-resources work?

@SichongP The current solution with resources works but is hacky, I'm asking for a solution that doesn't involve using resources but can access 'attempts' directly.


Add a self pruning layer to gcp exporter delta stores

PR Description
The GCP exporter tracks delta -> counter metric accumulations in memory over the life cycle of the alloy instance it runs on. When used in clustering mode this can cause issues,

Only one alloy instance will be incrementing counters at any given time
All alloy instances will maintain any counter state they have because the exporter only prunes when it is being scraped
✅ target flips from an alloy instance with counter state -> one with no counter state (prometheus treats this as a counter reset)
❌ target flips from an alloy instance with counter state -> one with previous counter state

This PR introduces a wrapper over-top of the the delta counter stores which does periodic pruning in the event the delta store is not in use. Since we cannot infer if the exporter instance is in use it will slowly prune this over the delta store TTL window which is 30 minutes by default. This at closes the window of time in which we are open to an incorrect data scenario in the event targets rebalance.
This is a work around until https://github.com/grafana/alloy/issues/399 is completed at which point each alloy instance should only be maintaining an instance of the exporter if it's actually in use.
PR Checklist

[x] CHANGELOG.md updated
[ ] Documentation added
[x] Tests updated

@mattdurham could you take another pass at this?

Sorry was on vacation but back now, looking


Publication's Limit condition

Shouldn't we check for the Publication and ExclusivePublication's backpressure condition in the following way? Otherwise, we could write beyond the publication limit.
inline std::int64_t offer(
concurrent::AtomicBuffer& buffer,
util::index_t offset,
util::index_t length,
const on_reserved_value_supplier_t& reservedValueSupplier)
{
...
const std::int64_t limit = m_publicationLimit.getVolatile();
...
if (position + length < limit)

It was an arbitrary decision but we decided to limit on beginning and not end of a message.

But the limit isn't the slowest subscription? Writing past the pub limit will overwrite data not yet read by at least one subscription. No?

The limit is only 1/2 a term greater than slowest consumer and we have 3 terms.

1/2 term is the case for network publication and 1 term for IPC.

Indeed! sorry ;[


Using Docker for Software Development

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #19684

Hi,
Thanks for this pull request (PR).
Unfortunately, we are closing this PR, because we do not believe it adds a significant improvement.  This content would be better placed in the main index.md for Docker.
Feel free to submit another PR which targets the file mentioned above.
Thank you


Set requirements to more flexible version

The current requirements makes it such as installing makes it incompatible with newer pytorch or transformers version
They should be set to minimal requirements

Hey Nicolas, apologies for the late response-just did this with version 0.3.0!


[Workers] Request for clarification of anti-abuse protection

Which Cloudflare product does this pertain to?
Workers
Existing documentation URL(s)

https://developers.cloudflare.com/workers/platform/limits/#request

Section that requires update
Request
What needs to change?
The Request section does currently not mention that you'll see firewall entries with worker as rule ID when the Workers anti-abuse protection has kicked in.
Currently customers may be quite confused when they suddenly see a lot of worker firewall entries, as they won't know that it's caused by the anti-abuse protection.
Here's an recent example of a customer who suddenly saw a lot of worker firewall entries, but wasn't aware that it was caused by the anti-abuse protection:

Here's the response I gave for reference:

How should it change?
The Request section should include that the internal worker firewall rule is used by the Workers anti-abuse protection. Currently the worker firewall rule is nowhere mentioned in the documentation, so customers running into it may be a bit confused and not know what to do about it.
Additional information
Not necessarily related to the documentation, but I would suggest Cloudflare to implement some kind of automatic notification when the anti-abuse protection has kicked in for a customer.
If for example, a customer is using Workers a lot internally for mission-critical work, it would help a lot if Cloudflare immediately notified them of traffic being too high and that they should immediately contact Cloudflare for a limit raise. Currently, Cloudflare will just drop a lot of requests without any notification, leaving customers completely clueless.

While I can't address your note in Additional Information, #6425 should address your change request.

This has been documented, and a feature request is being tracked internally.

Since this is done from a documentation perspective, closing out the issue from our repo.

This issue has been documented, and a fix is being tracked internally.


Simplify URLs of categorys and tags

categories/category1/category1.html
categories/category1/category1/index.html
->
categories/category1.html
tags/tag1/tag1.html
tags/tag1/tag1/index.html
->
tags/tag1.html
Simplify URLs of categorys and tags.

Please use the forum (https://discourse.gohugo.io/) for questions and troubleshooting. We prefer to use GitHub for verified bugs and vetted enhancements. Thanks.


Integration test fails: pyodbc cannot be added using global init script

There is an issue with the integration pipeline. When adding the ms odbc driver to databricks workspace, there is an error with accessing the /api/2.0/dbfs/put and is sometimes temp unavailble.
See e.g. this PR run:
https://github.com/atc-net/atc-dataplatform/actions/runs/3274325343/jobs/5403711433#step:7:46
See e.g. this PR run (Temp unavailable):
https://github.com/atc-net/atc-dataplatform/actions/runs/3274325343/jobs/5401303625

I consider to rewrite how the pipeline installs the odbc driver. We could might do it under the setup job (where mounting also happens in the moment)

https://status.azure.com/en-us/status/history/

An issue could be the following: The databricks workspace creates an underlying Storage account. Storage accounts deployment have been flaky lately. If the underlying db storage account is incorrectly deployed - there will be an issue for the databricks workspace (and API) to access the containers.

See this PR went well (21 okt. 2022 11:48): https://github.com/atc-net/atc-dataplatform/actions/runs/3295801247/jobs/5435829693

https://status.azure.com/en-us/status/history/

I see the same error as stated in the Status page.

Successful deployment 24. october: https://github.com/atc-net/atc-dataplatform/actions/runs/3274325343/jobs/5464960560.
Unfortunately it failed again afterwards.

The PR #190 gives the integration resources and resourcegroup a uniqueid. In this way we are able to circumvent the microsoft resource issue.


add openocd argument and raspboot device vars

Where applicable the altered makefile targets "raspboot", "jtagboot", and "openocd" were built and tested with hardware.

Resubmitted with correct signature. Thank you!

LGTM. Thanks!


[Feature Request]: Create a profile Dashboard for the Users signed in

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I will create a profile dashboard for the users, There is nothing happens when user logs in the website. The profile page is empty, and meses up the ui
Use Case
The users and login features of the website will have some meaning after this imlemented, Users will be able to see there score and other information , ther fav coursess , etc.
Benefits
No response
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC-EXT contributor
[X] I'm a HACKTOBERFEST contributor
[X] I have starred the repository

@samar12-rad go ahead. display all the images(registered through Google auth) and details that he/she entered while registering.including mail, phone, dob, height, weight. also, give the edit option to all of it.

@samar12-rad If you aware of doing thing, kindly tag me and message, so i can assign you for this.

@samar12-rad hello. Kindly react upper message

Yes, i will do it

pls assign me this @jeevan10017


create a binary distribution of the r0vm

Building the risc0 repository requires machines with a lot of memory and processing power. To serve those with lower-powered systems (and for convenience), we should distribute r0vm as a binary. At the very least, we should support macOS and Linux distributions (.deb and/or .rpm?).
It would be great to somehow wrap the starter template so that users running prover.run() calls into r0vm --elf ... without having to configure their starter templates.
If anyone has other ideas, feel free to chime in!

WASI or WASM r0vm could be a useful library too

note, closed because we need to discuss this internally


add s390x support to Debian base images

depends on https://github.com/ocurrent/ocaml-version/pull/37 and https://github.com/avsm/ocaml-dockerfile/pull/57

pushed to live


Extension not working correctly

If I try to share the code on the left i get an Error, see rightside.
I tried re-Installing the extension to its most recent version (v1.1.1).
Need any additional Information just DM me on dc or ask here
Greeting HyperBuilder

Use the "Set a Webhook" command through the Command Palette to reconfigure it, using it checks for any invalid input, if it still errors out let me know.

Use the "Set a Webhook" command through the Command Palette to reconfigure it, using it checks for any invalid input, if it still errors out let me know.

Reconfiguring it still gives exactly the same Error as before.
Doesnt give me invalid input warnings

Reconfiguring it still gives exactly the same Error as before.
Doesnt give me invalid input warnings

Alright, I'll look into it tomorrow and let you know if I manage to fix it.

Alright, I'll look into it tomorrow and let you know if I manage to fix it.

I've found the issue! The module I use to generate Hastebin links is breaking, it used to work before and when I released the 1.1.0 update, but it looks like it's too outdated now. I'm going to be looking into alternatives and I'll let you know how it goes.

I've found the issue! The module I use to generate Hastebin links is breaking, it used to work before and when I released the 1.1.0 update, but it looks like it's too outdated now. I'm going to be looking into alternatives and I'll let you know how it goes.

In release 1.1.2 I've removed the ability to share long code with Hastebin (this is planned to be temporary), and made it so if code is under 2000 characters it can still be shared to Discord. I'll look into Hastebin alternatives or fixes for a future update and bring the feature back.

In release 1.1.2 I've removed the ability to share long code with Hastebin (this is planned to be temporary), and made it so if code is under 2000 characters it can still be shared to Discord. I'll look into Hastebin alternatives or fixes for a future update and bring the feature back.

If the Hastebin feature is not the issue, please let me know.

If the Hastebin feature is not the issue, please let me know.


GitHub Actions Importer - Bamboo Migrations

Summary
GitHub Actions Importer helps users plan, forecast, and automate the migration of their existing CI/CD pipelines to GitHub Actions. With this update, we will be adding support for Bamboo. Bamboo users can migrate their pipelines to GitHub Actions easily and for free using the official GitHub CLI.
Intended Outcome

Simplify the pipeline migration process for Bamboo users by automating manual and tedious steps
Reduce the potential for errors during migration and speed up development teams

How will it work?
Users will be able to migrate existing Bamboo pipelines to GitHub Actions using the audit, forecast, dry-run, and migrate subcommands of gh actions-importer

🚢 This has shipped: https://github.blog/changelog/2023-05-22-github-actions-importer-bamboo-server-and-data-center-migrations-public-beta/.


main tag is confusing

We have a main git tag which also happens to be the name of the default branch.
This causes confusion and git warnings/errors:
warning: refname 'main' is ambiguous.`

I propose to create a new tag on the same ref and delete the main tag.

cc @rsahita

I have created an alternate tag "test" on the same ref - but I cannot delete the tag using the refs/tag/main handle - perhaps since @jjscheel created that (it shows as a verified tag and does not give me the option to delete the tag on Github either).


[Candidate 3v3 Nocky Mountains ZH v2] Some trees look odd

Observed behaviour
Some trees look odd. They have a dark shade in them.
Expected behavior
Trees look natural.
Screenshots

as designed dense Maple trees look like this in ZH


Integrating AWS DocumentDB as a vector storage method

Description
This change adds a vector store integration for AWS Document DB. @vidur2 and I saw an issue opened to ask for this integration in the LangChain repository and believed that LLamaIndex users would find it useful as well given that we were using it for a project. There are no new dependencies, this integration just requires the pymongo library.
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[x] Yes
[ ] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[x] Yes
[ ] No

Type of Change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Added new unit/integration tests
[] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

Our unit tests require one to input their own AWS credentials to run. In order to avoid exposing AWS secrets, we didn't include ours as part of the PR. Is there some way we can get approved without having these tests pass?

The tests should mock out API requests, or should be skipped properly if creds are missing

The tests should mock out API requests, or should be skipped properly if creds are missing
Should be fixed.

@logan-markewich is there anything else we need to add so that this can be merged? thanks for guiding us through the process

@prajwalsaokar the tests were a little wonky -- we need to mark them as skip (which is what I did), if we aren't going to mock the API calls. Also cleaned up a few other things, should be good to go now

@prajwalsaokar ngl the tests are pretty borked -- do you mind taking a look and ensuring either
a) things are properly mocked (api calls, etc.)
b) things are properly skipped when not mocked and things are missing
c) that tests actually work (I was hitting all kinds of errors actually haha)

@prajwalsaokar ngl the tests are pretty borked -- do you mind taking a look and ensuring either a) things are properly mocked (api calls, etc.) b) things are properly skipped when not mocked and things are missing c) that tests actually work (I was hitting all kinds of errors actually haha)

We just tried the tests on two machines, they should work it's just a bit of hassle to set them up because you need a DocumentDB instance and an EC2 instance thats connected to the DB instance with the correct networking config for the tests to run properly. Could you send over the errors you're getting?

We also think we implemented skipping correctly, but we didn't come up with a  way to skip the tests if the EC2 configuration isn't correct since that's not visible to LlamaIndex. Can you clarify what changes you think we should make on the skip/mock front?

It looks like we should follow something like Cosmos or Postgres. They simply try to connect to DB and if there is a failure, they set a "*_not_available" variable which is used to skip the test. From a quick glance at tests written for a few vector stores, it doesn't look like mocking the API calls is typically done. I'll leave it up to Logan to provide requirements for the merge, but just wanted to leave this comment first.

Correct, usually you can do some sort of check and based on the condition, skip or not.
Mocking would allow the tests to actually run,  in cicd, but it's usually more work (hence why other vectordbs don't have it)
I'll leave it up to you since this is your integration 👍🏻 either is fine by me
Once cicd passes here I will merge

Seems there is an incorrect import, maybe take a double check
For example, should be from llama_index.core.schema import...

Tests are still failing with the same import error 😓 Does these actually run locally for you? I'd be very surprised if they did. I'll push a fix

Thanks Logan for the help. Thank you Prajwal and Vidur for your contribution. I will try this out soon.

Thank you so much for all the help Logan, this was my first open source contribution and I learned a lot throughout this process. I'm very grateful for the time you spent ensuring that this integration could go through.


Added knex.migrate.to and knex.migrate.before

Like described in https://github.com/tgriesser/knex/issues/506
Example usage in test:
describe('1234_my_change migration', function() {
  //First set the db in the state before the migration we're testing
  before(function() {
    return db.migrate.before('1234_my_change.js')
  })

  describe('up', function() {
    //Trigger `up` to be run
    before(function() {
      return db.migrate.to('1234_my_change.js')
    })

    it('created my_table', function() {
      return knex.schema.hasTable('my_table')
        .then(function(exists) {
          assert(exists)
        })
    })
  })

  describe('down', function() {
    //Trigger `down` to be run
    before(function() {
      return db.migrate.before('1234_my_change.js')
    })

    it('dropped my_table', function() {
      return knex.schema.hasTable('my_table')
        .then(function(exists) {
          assert(!exists)
        })
    })
  })
})

I also cleaned up the migration integration tests a bit. Isolated the tests for each method more and made sure that they each clean up after themselves.
Questions:

Should the name of the version be the complete filename? E.g. do you say knex.migrate.to('12345678_my_thing.js') or knex.migrate.to('12345678')? I prefer the first one, as there is no checks AFAICS whether the integer part is unique.

Let me know if there is anything you want me to look at.

Would be great to have this work synced up with the discussion in #279 and the resulting code proposal in #617 which amongst other things does some refactorings to avoid some of the code duplication that happens when new migration methods like these ones are added.

Can we have this, please?

@carera See discussion in https://github.com/tgriesser/knex/pull/617 I think

Any update on the status of this?  Would be amazing to have. I'd be happy to take over the PR to finish out the tooling if it's necessary.

Hi, I started going through old pull requests and get them merged if possible or close otherwise if they are not going to be finished.
@sebastianseilund do you think this is still relevant and useful feature to have? If so, conflicts needs to be fixed and documentation of the new feature added to index.html.

Still should be synced up with the discussion in #617 as they require similar extensions to the underlying migration methods, but probably makes sense as a feature request still.
Also still related to whether all of the migration work will move to https://github.com/knex/arctic as @bendrucker has indicated before or whether the current migration system is still open to extensions.

i could definitely use this feature

I took another route and created knex adapter and cli for unzug. It already handles "upto" and downto" logic. The only things to implement were support for batches and nice cli: knex-migrate

anyone working on this?

Closing due to inactivity, if someone likes to implement / fix this, please open another PR an link to this.

@elhigu such a shame that this request got closed just as the other https://github.com/knex/knex/pull/617
we really need "up to" and "down to" methods, just as in https://github.com/tj/node-migrate#running-migrations
with git backing all the version control - you really want to jump from version to version and not do separate up and downs in between.
So such functionality seems highly required these days! Please reopen and finalize!
@sebastianseilund if you are still alive could you post a new PR rebased to the latest changes? :) thanks

@elhigu such a shame that this request got closed just as the other https://github.com/knex/knex/pull/617
we really need "up to" and "down to" methods, just as in https://github.com/tj/node-migrate#running-migrations
with git backing all the version control - you really want to jump from version to version and not do separate up and downs in between.
So such functionality seems highly required these days! Please reopen and finalize!
@sebastianseilund if you are still alive could you post a new PR rebased to the latest changes? :) thanks

@gpetrov Alive, but haven't used Knex in several years. You're welcome to finish up the work here :)

@gpetrov Alive, but haven't used Knex in several years. You're welcome to finish up the work here :)

@gpetrov It is implemented and should be working. I finally have some time and will check out the API part of it to see if there are issues with it.

@gpetrov It is implemented and should be working. I finally have some time and will check out the API part of it to see if there are issues with it.

@gpetrov So this is more granular than what we have right now, which is moving single migration at a time? If that is the case, feel free to finish this PR, then it could be merged.

@gpetrov So this is more granular than what we have right now, which is moving single migration at a time? If that is the case, feel free to finish this PR, then it could be merged.

Yes indeed @kibertoad we need more gradual from, to in sequence indeed, it is shame to loose the good code here, so I will see what I can do.
But are you ready with the whole conversion to classes of Knex? Don't want to rewrite afterwards :)

Yes indeed @kibertoad we need more gradual from, to in sequence indeed, it is shame to loose the good code here, so I will see what I can do.
But are you ready with the whole conversion to classes of Knex? Don't want to rewrite afterwards :)

@gpetrov We've been doing lots of work in that direction lately, and are mostly done. I think https://github.com/knex/knex/pull/4253 is one of the last major pieces, but I don't think you would be hitting that place within the scope of this change.

@gpetrov We've been doing lots of work in that direction lately, and are mostly done. I think https://github.com/knex/knex/pull/4253 is one of the last major pieces, but I don't think you would be hitting that place within the scope of this change.


Would like an infinite scrolling example demo

now , there is only a Pull down refresh demo, but the load more function is more useful

Thank you for your quick respones.
It will be great If we could have a TabBarView + Pull Up + Pull Down + Animation radicator sample.

When will have this sample?

cc @HansMuller for Material components

CC @filiph would you like to offer one of Dev Rel's infinite scrolling examples either as a standalone demo, or within the gallery?

Great suggestion. I'm not going to get to this before I/O, though (May 7-9). Hope that's okay.
Right now the only real infinite scrolling example is bloc_complex, which — as the name suggest — is way more complex than most people would want. Other samples with infinite scrolling in them are not useful for the infinite-scrolling part (they often just create random items with a seed, so not a very real-world use case) — they have been built to show other features.

@filiph ETA on this?


Add from_async_reader to simplify integration with tokio

I'm working on an asynchronous web framework for Rust, Salt, and one of my current tasks is to make consuming and producing JSON ergonomic.
Currently, I have this:
https://github.com/mehcode/salt-rs/blob/69cd12b27953f8b602023d8884ceede5dc628535/examples/json.rs#L40-L51
fn index(ctx: Context) -> impl Future<Item = Response, Error = Error> {
    io::read_to_end(ctx, Vec::new()).from_err().and_then(|(_, buffer)| {
        future::done(serde_json::from_slice(&buffer)).from_err()
    }).and_then(|body: RequestBody| {
        future::done(serde_json::to_string(&json!({
            "id": 20u8,
            "name": body.name,
        }))).from_err()
    }).map(|s| {
        Response::with(s).with_header(header::ContentType::json())
    })
}

It'd be very convenient if serde_json could parse JSON from an tokio_io::AsyncRead (in addition to a Read as it currently does).
Here's an example of the improvement possible with this PR:
https://github.com/mehcode/salt-rs/blob/ad4eaada4107f6f496f722a906d670a4afa3a97c/examples/json.rs#L22-L31
fn index<'a>(ctx: Context) -> impl Future<Item = Response> + 'a {
    serde_json::from_async_reader(ctx).and_then(|(_, body): (_, RequestBody)| {
        future::done(serde_json::to_string(&json!({
            "id": 20u8,
            "name": body.name,
        })))
    }).map(|s| {
        Response::with(s).with_header(header::ContentType::json())
    })
}

@dtolnay Sorry it took so long to respond. I did see your messages on IRC.

If we consider an ideal future for tokio ..
#[async]
fn index(ctx: Context) -> Result<Response> {
    let (_, buffer) = await!(io::read_to_end(ctx, Vec::new()))?;
    let body: RequestBody = serde_json::from_slice(&buffer)?;

    // [...]
}

That's still not good enough. We have serde_json::from_reader for dealing directly with io::Read.
fn index(ctx: Context) -> Result<Response> {
    // If we pretend that `Context` is not `AsyncRead`
    let body: RequestBody = serde_json::from_reader(ctx)?;

    // [...]
}

As tokio::AsyncRead is std::io::Read I'm actually hoping specialization can allow serde_json::from_reader to transparently work on AsyncRead.
#[async]
fn index(ctx: Context) -> Result<Response> {
    let body: RequestBody = await!(serde_json::from_reader(ctx))?;

    // [...]
}

That is my ideal here. I understand that as serde-json is 1.x it can't easily depend on 0.x dependencies.
Perhaps when tokio is at the point of enabling the ideal we could add a unstable or nightly feature flag here that would allow it to be added here without compromising the 1.x?

In line with those ideas, a blanket impl in an external library could look like this. What do you think?
#[async]
fn index(ctx: Context) -> Result<Response> {
    let body: RequestBody = await!(ctx.map_bytes(serde_json::from_slice))?;

    // [...]
}

I think the tokio ecosystem has room for a high-quality library for composing async read and write with other operations, sort of like what byteorder's extension traits do for ordinary read and write.


VUE_APP_FATHOM_SITE_ID bug on yarn serve

Describe the bug
A bug appears on my startup application, Template execution failed: ReferenceError: VUE_APP_FATHOM_SITE_ID is not defined
To Reproduce
Steps to reproduce the behavior:

Clone the repo onto your machine
Install the node version v10.19.0 with nvm
Execute with yarn serve
See error

Expected behavior
Screenshots
You should see something like the image below

Desktop (please complete the following information):

OS: MacOS - Catalina 10.15.6 (19G73)
Version v10.19.0

Additional context
I'll keep trying to execute, if for some reason i find out what is going on I'll close the issue or create a PR 👍

@yagoazedias thanks for posting this.
I guess you'll need to define that ENV variable in order for this to work. I suppose I could put a .env file in the repo with a blank value for that. You could do the same or just run VUE_APP_FATHOM_SITE_ID='' yarn serve
Alternatively, you could also remove the bit of HTML that references that in index.html (at the bottom). It's only used to pass along the Fathom Analytics Site ID to a script tag

Dear,
I created the .env file and added :
VUE_APP_FATHOM_SITE_ID='';

and it fixes the issue.
Best Regards
Youssef

or remove that html in /public that worked too.

well that didn't work as when I went to delete the app posted
Failed to delete "logger": fathom is not defined

I take it back.  They were deleted despite the error message.  All an all this Fathom analytics was a distraction.  Is it really necessary?  Maybe you can make it optional and off by default.

@dkebler I've pushed an update. Fathom should be ignored in dev mode.


sr7 dashboard show WARN :If it should be allowed add it to hystrix.dashboard.proxyStreamAllowList.

2020-08-17 08:51:46.351 WARN 11636 --- [io-19000-exec-8] ashboardConfiguration$ProxyStreamServlet : Origin parameter: http://localhost:18000/actuator/hystrix.stream is not in the allowed list of proxy host names. If it should be allowed add it to hystrix.dashboard.proxyStreamAllowList.
thank you !

What's the issue?

hello  @spencergibb
run url:
http://localhost:19000/hystrix/monitor?stream=http%3A%2F%2Flocalhost%3A18000%2Factuator%2Fhystrix.stream
console show info:
2020-08-17 08:51:46.351 WARN 11636 --- [io-19000-exec-8] ashboardConfiguration$ProxyStreamServlet : Origin parameter: http://localhost:18000/actuator/hystrix.stream is not in the allowed list of proxy host names. If it should be allowed add it to hystrix.dashboard.proxyStreamAllowList.

I also encountered this warning

In hystrix-dashboard project add this to application.yml
hystrix:   dashboard:     proxy-stream-allow-list: '*'
In hystrix-service add this to application.yml
management:   endpoints:     web:       exposure:         include: '*'
I found this question on stackoverflow: https://stackoverflow.com/questions/59738969/unable-to-connect-to-command-metric-stream-in-hystrix-dashboard-issue

As suggested in the comment above and in the docs, it is something you need to configure. The warning just informs about that.

this will work for version 2.2.9.RELEASE


Linting

Adding npm standard library to do automatic linting when Travis CI runs. Also, I recommend creating a pre-commit hook by creating the file .git/hook/pre-commit, making it executable, and putting this content into it.

:tada: This PR is included in version 1.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Game crashes when fireball spawns?

crash-2023-08-03_18.42.10-server.txt

Will be fixed in a hotfix 1.3.6


Adjust level, term to new ocw-to-hugo format

Pre-Flight checklist

[x] Testing

[x] Changes have been manually tested

What are the relevant tickets?
Related to https://github.com/mitodl/ocw-to-hugo/pull/398
What's this PR do?
level was changed to an array so this PR changes it to output one level link per item in the array. Additionally, term was changed to not include a year anymore, and year was added with the corresponding year.
How should this be manually tested?
Convert a course with the latest ocw-to-hugo and view a course with this PR. The level in the course info on the course home page should look the same as before, with a link to the search page. The text next to "As Taught In" should be a semester and a year, looking exactly like it did before

Actually, a caveat here.  After approving this I tested it with an ocw-studio published course and the build failed:
[start:course:hugo] Error: Error building site: failed to render pages: render of "page" failed: execute of template failed: template: pages/single.html:14:7: executing "pages/single.html" at <partialCached "mobile_course_info.html" .>: error calling partialCached: execute of template failed: template: partials/mobile_course_info.html:5:5: executing "partials/mobile_course_info.html" at <partial "course_info.html" (dict "context" . "inPanel" true)>: error calling partial: "/home/gumaerc/Code/ocw-hugo-themes/course/layouts/partials/course_info.html:56:30": execute of template failed: template: partials/course_info.html:56:30: executing "partials/course_info.html" at <$courseData.level>: range can't iterate over

It seems we need to make changes to the ocw-course starter in ocw-hugo-projects to match what was done here.  If those changes aren't made before this PR is merged and pushed to RC, builds there will start to fail.

@gumaerc all set


Add JUnit output format

This PR adds (or rather brings back) an ability to save homebrew-test-bot test results in JUnit format.
Most of the code is copied from the previous version (from https://github.com/Homebrew/homebrew-test-bot/pull/355) with some small adjustments:

All JUnit related code moved to lib/junit.rb
JUnit reporter supports filtering tests by name (currently is saves results only for audit and test)

See https://github.com/Homebrew/brew/pull/11578#pullrequestreview-689543802

I've removed all the extra data (we could easily bring it back when needed from this or from the previous one PR, thanks git!)
And here's an example of junit report for command brew test-bot --only-formulae --junit hello zzz:
<?xml version='1.0'?>
<testsuites>
  <testsuite name='brew-test-bot.big_sur' timestamp='2021-06-29T22:12:46+01:00'>
    <testcase name='audit hello --online --git --skip-style' status='failed' time='23.11467' timestamp='2021-06-29T22:13:47+01:00'>
      <failure message='failed: brew audit hello --online --git --skip-style'/>
    </testcase>
    <testcase name='test hello' status='failed' time='3.29637' timestamp='2021-06-29T22:14:24+01:00'>
      <failure message='failed: brew test --verbose hello'/>
    </testcase>
  </testsuite>
  <testsuite name='brew-test-bot.big_sur' timestamp='2021-06-29T22:14:41+01:00'>
    <testcase name='audit zzz --online --git --skip-style' status='passed' time='98.960434' timestamp='2021-06-29T22:14:51+01:00'/>
    <testcase name='test zzz' status='passed' time='2.836198' timestamp='2021-06-29T22:16:41+01:00'>
    </testcase>
  </testsuite>
</testsuites>


Added an example for i2c

I added an example to find all addresses of connected i2c devices.
It's a little arbitrary in which it does not show any outside effect; one is meant to run it step by step and inspect the final values with gdb.

I do have a bit more comprehensive I2C scanner here:
https://github.com/stm32-rs/nucleo-f042k6/blob/master/examples/i2c_scanner.rs
But I'd be happy to take this one if there were a few more comments middle section about how this works.


Added note about embedded images to AttachmentSizeOver parameter in Set/New-TransportRule

https://github.com/MicrosoftDocs/OfficeDocs-Exchange/issues/1635

Docs Build status updates of commit d96db8a:
:clock10: Full build: the average full build time is 17 min(s) 40 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit d96db8a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-TransportRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-TransportRule.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Enforce exclusive memory access to delegate in ClientRequest

This is to ensure Swift 4's Memory Safety model - Enforce Exclusive Access to Memory
(Ref: https://github.com/apple/swift-evolution/blob/master/proposals/0176-enforce-exclusive-access-to-memory.md)
Motivation and Context
Encountered the following crash with message Simultaneous accesses to 0x7f16a000a938, but modification requires exclusive access  on delegate?.prepareForRedirect() in ClientRequest
Simultaneous accesses to 0x7f16a000a938, but modification requires exclusive access.
Previous access (a modification) started at Kitura-netPackageTests.xctest`<unavailable> + 254605 (0x562b9e62028d).
Current access (a read) started at:
0    libswiftCore.so                    0x00007f16e23bb840 swift_beginAccess + 510
1    Kitura-netPackageTests.xctest      0x0000562b9e620da1 <unavailable> + 257441
2    Kitura-netPackageTests.xctest      0x0000562b9e622ee1 <unavailable> + 265953
3    Kitura-netPackageTests.xctest      0x0000562b9e621006 <unavailable> + 258054
4    Kitura-netPackageTests.xctest      0x0000562b9e622f2b <unavailable> + 266027
5    libswiftCore.so                    0x00007f16e223f490 withUnsafePointer<A, B>(to:_:) + 12
6    libswiftCore.so                    0x00007f16e23a40c0 withUnsafeMutablePointer<A, B>(to:_:) + 9
7    Kitura-netPackageTests.xctest      0x0000562b9e62036b <unavailable> + 254827
8    Kitura-netPackageTests.xctest      0x0000562b9e61ad9c <unavailable> + 232860
9    Kitura-netPackageTests.xctest      0x0000562b9e6bea0d <unavailable> + 903693
10   Kitura-netPackageTests.xctest      0x0000562b9e693bb2 <unavailable> + 727986
11   Kitura-netPackageTests.xctest      0x0000562b9e69bc1c <unavailable> + 760860
12   Kitura-netPackageTests.xctest      0x0000562b9e685fef <unavailable> + 671727
13   Kitura-netPackageTests.xctest      0x0000562b9e69bc71 <unavailable> + 760945
14   Kitura-netPackageTests.xctest      0x0000562b9e6bcce8 <unavailable> + 896232
15   Kitura-netPackageTests.xctest      0x0000562b9e6bd021 <unavailable> + 897057
16   Kitura-netPackageTests.xctest      0x0000562b9e6bcd35 <unavailable> + 896309
17   Kitura-netPackageTests.xctest      0x0000562b9e6bcf65 <unavailable> + 896869
18   Kitura-netPackageTests.xctest      0x0000562b9e6354ed <unavailable> + 341229
19   libdispatch.so                     0x00007f16e3003337 <unavailable> + 287543
20   libdispatch.so                     0x00007f16e300f82a <unavailable> + 337962
21   libdispatch.so                     0x00007f16e300ffdd <unavailable> + 339933
22   libdispatch.so                     0x00007f16e301268a <unavailable> + 349834
23   libpthread.so.0                    0x00007f16e1d9b6db <unavailable> + 30427
24   libc.so.6                          0x00007f16e041d850 clone + 63
Fatal access conflict detected.

This PR provides a fix for the above crash by creating a shallow copy of delegate ensuring memory safety.
Checklist:

[x] I have submitted a CLA form
[x] If applicable, I have updated the documentation accordingly.
[x] If applicable, I have added tests to cover my changes.

@nethraravindran I'm a little confused.  Is this change really making a shallow copy of delegate?  It looks to me like it creates a strong reference to the weak var delegate (CurlInvokerDelegate is a class protocol).

OK, so if it's the latter (delegate is accessed within the closure that mutates it) then shouldn't this always fail?  Perhaps this is down to the vagaries of dynamic enforcement (SE-0176 implies dynamic may have to be used when the variable is captured in a closure).
I guess I'm happy with this, I'd be happier if I understood what was going on better, but since this fixes a problem and I can't see evidence of any downside, I'm in.


[GPU/Hide unrelated maps] Hide GoTR area inside Kalphite Lair

Type
Incorrect behavior
Operating System
Linux
OS Version
Arch Linux
Bug description
With Hide unrelated maps enabled in the GPU plugin, the edge of the Temple of the Eye area is still visible from the eastern side of the Kalphite Lair. Note that draw distance needs to be set to at least 44 and extended map loading to at least 2 to see it.
Screenshots or videos

RuneLite version
RuneLite version: <IP_ADDRESS>
Launcher version: 2.6.10
Logs
No response

This is addressed by #18099


⚠ SOAP Platform (ETU) has degraded performance

In 307911f, SOAP Platform (ETU) (https://soap-etu.six-group.com/healthcheck) experienced degraded performance:

HTTP code: 503
Response time: 10178 ms

Resolved: SOAP Platform (ETU) performance has improved in 850a5be.


Code gets unfolded during typing (Python)

Issue Type: Bug
I usually have my code folded at the method level (when I'm creating a class) and I believe after the latest release, depending on what you're typing, VS Code will unfold all the methods after the line that was being modified.
It only unfolds when there's a syntax error that occurs as you're modifying the code. For example, a mismatched bracket in a list. Note that this type of syntax error is bound to happen as you're modifying the code. Next thing I know, before I can close that bracket, all the methods are unfolded :(
I appreciate your support.
Thanks,
Eduardo
VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:40:02.816Z)
OS version: Windows_NT x64 10.0.17763
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12 x 2592)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.76GB (17.42GB free)

Process Argv
--crash-reporter-id b9bc0b0a-2a6b-45f4-a7e6-cbcf9e10bfbc

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

gitignore
cod
0.7.0

githistory
don
0.6.19

gitlens
eam
11.7.0

kite
kit
0.147.0

git-graph
mhu
1.30.0

python
ms-
2021.12.1559732655

vscode-pylance
ms-
2022.1.1

jupyter
ms-
2021.11.1001550889

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.4

live-server
ms-
0.2.12

vscode-qt-for-python
sea
1.1.7

simple-rst
tro
1.5.1

pyqt-integration
zho
0.2.0

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
vscop804cf:30404767
vs360:30404995
vsrem710:30416614
vsccppwtstudy:30421978

I think this has the same underlying cause as #137890. There is a pending fix, #139779, which should fix this problem.

Thanks for the response, Pieter!
Still on the code folding topic, if I may suggest, you guys should consider some sort of settings that can be saved (like the one from MATLAB below). I find it extremely useful for large code files. There's also a hot key combination to fold and unfold based on the saved settings, such as "CTRL" + "SHIFT" + "+" and "CTRL" + "SHIFT" + "-".
Regards,
Eduardo

Guys! Please fix this issue! It's driving me insane. Every time I accidentally delete a matching bracket, parenthesis, or quotation mark, it unfolds the entire code after the line where it occurred. I'm being super careful when typing those. But every now and then... BOOM!! 😵💫

Please fix this issue. Pretty please?

One un-ideal possible workaround: Change Editor: Folding Strategy from auto to indentation.

Thanks ProceduralCode! It seems to work well!

Marking as duplicate of https://github.com/microsoft/vscode/issues/137890


📖 🏗 🔧Enable access of interactive demo hosted in remote server

"3. Try interactive with demo" button in "Quick start guide" is a dynamic link which is composed by :

Demo's remote server URL (which should be configurable).
Environment secret of current environment in Portal.
Evaluation server url which demo can communicate with for its FeatBit SDK.

So:

I modified the code which recomposes the link of "3. Try interactive with demo" button.
I added configurable params in environment.ts and environment.prod.ts. Because demo's url and evaluation server are different and depend on how users construct their network.
I updated docker-compose-dev.yml file that we can pass two enviroment's params from docker-compose.

PS:
I also added the number before each "Get Started" item. This is feedback from testing users.

This won't work, you need to modify dockerfile to set the two new env variables


Call rust functions from a cretonne function

Is it possible to call a rust function from a cretonne function? Does it have the same overhead as a normal function call?

Cretonne is not a virtual machine, it is just a compiler that generates native machine code. It can call C and Rust functions.


Record Collection

Challenge Name

https://www.freecodecamp.com/challenges/record-collection
Issue Description

All test cases should be passed！
Browser Information

Browser Name, Version: Version 58.0.3029.96 (64-bit)
Operating System:  Mac OS Sierra 10.12.4 (16E195)
Mobile, Desktop, or Tablet: Desktop

Your Code

// Setup
var collection = {
    "2548": {
      "album": "Slippery When Wet",
      "artist": "Bon Jovi",
      "tracks": [
        "Let It Rock",
        "You Give Love a Bad Name"
      ]
    },
    "2468": {
      "album": "1999",
      "artist": "Prince",
      "tracks": [
        "1999",
        "Little Red Corvette"
      ]
    },
    "1245": {
      "artist": "Robert Palmer",
      "tracks": [ ]
    },
    "5439": {
      "album": "ABBA Gold"
    }
};
// Keep a copy of the collection for tests
var collectionCopy = JSON.parse(JSON.stringify(collection));

// Only change code below this line
function updateRecords(id, prop, value) {

  var obj = collection[id];
  if(prop === 'tracks') {
    if(obj[prop]===undefined) {
       obj[prop] = [];
    }
    if(value !== '') {
      obj[prop].push(value);
    }

  } else {
    if(value === '') {
      delete obj[prop];
    } else {
      obj[prop] = value;
    }
  }

  return collection;
}

// Alter values below to test your code
updateRecords(2548, "tracks", "");

Screenshot

The problem is that you forgot to fully implement the last rule

If value is empty (""), delete the given prop property from the album

Your code only checks value === '' when the prop does not equal 'tracks'.
To fix this move the empty value check before checking whether prop equals 'tracks.
if(value === '') {
    delete obj[prop];
} else if(prop === 'tracks') {
    if(obj[prop]===undefined) {
        obj[prop] = [];
    }
    if(value !== '') {
        obj[prop].push(value);
    }
} else {
    obj[prop] = value;
}

Hi,
Thanks for reporting this issue.
Here are some next steps that you should follow before we can help you with your query:

Check these troubleshooting steps first.
Please use the Chat Rooms or try looking through our forum for help with a specific challenge and any coding assistance.

IMPORTANT:
Please NOTE that this tracker is for reporting bugs and enhancements to freeCodeCamp's code base only.
Happy Coding!


fix(lane_change): skip safety check for stopping vehicles

Description
Before this change, we can not change lane if the stopping vehicle is behind of a traffic light stop line.
To fix this issue, I change the parameters for getting parked object function.

Related links

Tests performed
TIER IV INTERNAL TEST
Tested in planning simulator
Before:

After:

Notes for reviewers

Interface changes
Nothing.

Effects on system behavior
If stopping vehicles are behind of traffic light stop line, it will be plan lane change.

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

I will merge this PR after checking internal test.


HDDS-8440. Ozone Manager crashed when failed to delete FSO bucket.

What changes were proposed in this pull request?
Use proper class for typecast while reading from cache. Added OmDirectoryInfo for reading directory info cache value to determine whether bucket is empty or not.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8440
How was this patch tested?
Create/Delete directory and FSO bucket and adding some delay in rocks db insertion so that values are read from cache.

Thanks @ashishkumar50 for working on this.
Please reuse existing code by extracting it into a generic class and creating parameterized instances for OmKeyInfo and OmDirectoryInfo.

@adoroszlai , Thanks for the review, I have updated to reuse the existing code.


[TextField] Safari scrolls to top on password field focus with "filled" and "standard" variants

Steps to reproduce
Link to live example: (required)
https://github.com/user-attachments/assets/90dcfa48-2617-45bd-80f2-4c0dca1a46f3
Steps to Reproduce:
1.	Go to the TextField demo page on MUI’s website.
2.	Scroll to any TextField with type="password" and set to the “filled” or “standard” variant.
3.	Click on the password field in Safari (on iOS 17 or macOS).
4.	Observe that the page briefly scrolls to the top of the viewport as Safari displays the password suggestion prompt.
Current behavior
In Safari, when focusing on a TextField with type="password" in either the “filled” or “standard” variant, the page flashes to the top as Safari’s password suggestion prompt appears. This behavior does not occur with the “outlined” variant.
Expected behavior
The page should remain stable and not scroll when the password field is focused, regardless of the variant in use.
Context
This issue affects the usability of forms with password fields in Safari by causing unexpected scrolling behavior. The issue appears to be related to Safari’s password suggestion feature, affecting both mobile and desktop Safari users.
Your environment

npx @mui/envinfo
 System:
    OS: macOS 14.6.1 / iOS 17
  Binaries:
    Node: 20.16.0
    npm: 10.8.1
  Browsers:
    Safari: 17.6 (macOS), iOS Safari (iOS 17)
  npmPackages:
    @mui/material: ^6.1.6
    react: ^18.2.0

Search keywords: TextField password scroll Safari, TextField password field Safari bug, Safari scroll to top password field, MUI TextField password variant issue

I am curious. Does it happen with native HTML input?

I am curious. Does it happen with native HTML input?

I will try to reproduce the issue in HTML now.

Clicking on the label causes the scroll but clicking on the input does not. 🤔
Helps are welcome.


Allow prallel container removal

What type of PR is this?
/kind feature
What this PR does / why we need it:
Similar to the pod sandbox removal we now allow removing container in parallel goroutines.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

crictl: allow to remove containers in parallel go routines.

@kubernetes-sigs/cri-tools-maintainers PTAL


Intermittent NoCredentialsError('Unable to locate credentials')

Describe the bug

We've got a set of ec2 instances (2 to 10) that performs some tasks related to s3 buckets. More precisely: they copy files from an external location to an s3 bucket, and download from that bucket afterwards (grosso modo)
Those ec2 instances have an aws iam Role to provide them with access to the s3 bucket. That particular Role has the policy S3FullAcess from amazon.
From time to time (once or twice a day, when we do daily hundreds of thousands of those operations), the error "Unable to locate credentials" appear)
The ec2 instance that reports the error has done several ops of the kind flawlessly, and after the error is raised, it performs subsequent operations well.
The ec2 instances typically last for a few hours before being terminated and replaced.

Steps to reproduce

Can't reproduce it, because it happens only from time to time

Expected behavior

I expect all the ops regarding s3 work well, provided that the ec2 instances has the right role, and in 99.5% of the times it's like that.

Debug logs
Full stack trace by adding
import botocore.session
botocore.session.Session().set_debug_logger('')

to your code.
I'll update this issue when I got the logs

@JoeZ99 - Thank you for your post. Along with the debug logs can you please provide your ec2 instance type ?

@swetashre , I'm having tremendous trouble to get the logs. Putting them in place in our system is not that easy, and once they're in place, I gotta hunt down the instance before aws kill it iself :-) That's to explain why it's taking sometime to get the logs.
the instance I can tell you know: it's t3a.small
Also I've seen this error on other aws service, which is the PutMetricData operation, on an t2.medium instance. Of course I can assure you that it happens only from time to time, and most of the time the PutMetricData op works perfectly.
This is the stacktrace of the op I just mentioned as seen by sentry:
  File "botocore/client.py", line 316, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "botocore/client.py", line 622, in _make_api_call
    operation_model, request_dict, request_context)
  File "botocore/client.py", line 641, in _make_request
    return self._endpoint.make_request(operation_model, request_dict)
  File "botocore/endpoint.py", line 102, in make_request
    return self._send_request(request_dict, operation_model)
  File "botocore/endpoint.py", line 132, in _send_request
    request = self.create_request(request_dict, operation_model)
  File "botocore/endpoint.py", line 116, in create_request
    operation_name=operation_model.name)
  File "botocore/hooks.py", line 356, in emit
    return self._emitter.emit(aliased_event_name, **kwargs)
  File "botocore/hooks.py", line 228, in emit
    return self._emit(event_name, kwargs)
  File "botocore/hooks.py", line 211, in _emit
    response = handler(**kwargs)
  File "botocore/signers.py", line 90, in handler
    return self.sign(operation_name, request)
  File "botocore/signers.py", line 160, in sign
    auth.add_auth(request)
  File "botocore/auth.py", line 357, in add_auth
    raise NoCredentialsError

This is the args of the first call first call botocore/client.py (line 316, in _api_call):

args | []
-- | --
kwargs | {MetricData: [{}], Namespace: 'Celery'}
operation_name | 'PutMetricData'
py_operation_name | 'put_metric_data'
self | <botocore.client.CloudWatch object at 0x7f21f806bf28>

When attempting to retrieve credentials on an Amazon EC2 instance that has been configured with an IAM role, Boto3 will make only one attempt to retrieve credentials from the instance metadata service before giving up. You can increase this value to make Boto3 retry multiple times before giving up. For this you can use AWS_METADATA_SERVICE_NUM_ATTEMPTS
https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html
For this issue i would recommend creating a ticket to AWS Support as this can be an issue with ec2 instance. So the ec2 team can also look at it.


Downloading old & new video from CBS

Trying to download http://www.cbs.com/shows/supergirl/video/A0lquInjZ_k4vup_O4OAweMnPdRsnJAE/supergirl-solitude/ or any other "old" video clip. Leads to "http://once.unicornmedia.com/now/media/progressive/bb0b18ba-64f5-4b1b-a29f-0ac252f06b68/77a785f3-5188-4806-b788-0893a61634ed/468fb310-a585-11e4-bfdb-005056837bc7/e3697f96-9aa1-43f2-9a63-f86a6640f26b/content.mp4", but that has 401 Unauthorized. But that is not all. On new videos youtube-dl downloads a m3u8 list instead of a video.
By the way Old: 18th of March and before; New:19th of March and after

I have the same issue when trying to download the Late Show.

C:\Users\Raradra\Documents>youtube-dl -v "http://www.cbs.com/shows/the-late-show-with-stephen-colbert/video/U6B47sA7bcL1OliOF9n_i6_llXVZLM6r/the-late-show-3-17-2016-william-h-macy-melissa-rauch-isaac-mizrahi-/"
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.cbs.com/shows/the-late-show-with-stephen-colbert/video/U6B47sA7bcL1OliOF9n_i6_llXVZLM6r/the-late-show-3-17-2016-william-h-macy-melissa-rauch-isaac-mizrahi-/']
[debug] Encodings: locale cp1250, fs mbcs, out cp852, pref cp1250
[debug] youtube-dl version 2016.03.18
[debug] Python version 2.7.10 - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg N-77883-gd7c75a5, rtmpdump 2.4
[debug] Proxy map: {}
[CBS] the-late-show-3-17-2016-william-h-macy-melissa-rauch-isaac-mizrahi-: Downloading webpage
[ThePlatform] of9zYH1kUpJS: Downloading SMIL data
[ThePlatform] of9zYH1kUpJS: Checking video URL
[ThePlatform] 93677179-2d99-4ef4-9e17-fe70d49abfbf: Downloading m3u8 information
[ThePlatform] of9zYH1kUpJS: Downloading JSON metadata
[debug] Invoking downloader on u'http://once.unicornmedia.com/now/media/progressive/bb0b18ba-64f5-4b1b-a29f-0ac252f06b68/77a785f3-5188-4806-b788-0893a61634ed/468fb310-a585-11e4-bfdb-005056837bc7/93677179-2d99-4ef4-9e17-fe70d49abfbf/content.mp4'
ERROR: unable to download video data: HTTP Error 401: Unauthorized
Traceback (most recent call last):
File "youtube_dl\YoutubeDL.pyo", line 1627, in process_info
File "youtube_dl\YoutubeDL.pyo", line 1569, in dl
File "youtube_dl\downloader\common.pyo", line 344, in download
File "youtube_dl\downloader\http.pyo", line 58, in real_download
File "youtube_dl\YoutubeDL.pyo", line 1929, in urlopen
File "urllib2.pyo", line 437, in open
File "urllib2.pyo", line 550, in http_response
File "urllib2.pyo", line 475, in error
File "urllib2.pyo", line 409, in _call_chain
File "urllib2.pyo", line 558, in http_error_default
HTTPError: HTTP Error 401: Unauthorized

See this issue: https://github.com/rg3/youtube-dl/issues/8893

This issue is already fixed and fix will be incorporated in the next version of youtube-dl.


Create Shape Using JButton in Java GUI

Don't add codes.
Add resources like free certification courses, roadmaps, notes, etc

Okay thank you brother thanks for suggestions
On Mon, 17 Oct 2022, 11:34 p.m. Kishan Kumar Rai, @.***>
wrote:

Don't add codes.
Add resources like free certification courses, roadmaps, notes, etc
—
Reply to this email directly, view it on GitHub
https://github.com/kishanrajput23/Programming-Resources/pull/87#issuecomment-1281264972,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARHBPGYGADVSCKFZ654I5PDWDWIMTANCNFSM6AAAAAARHJ3WKQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Can't build Apktool-master

Just what the title says...
org.jf.dexlib2.AccessorTest > testAccessors FAILED
junit.framework.AssertionFailedError: expected:<12> but was:<1>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:277)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at junit.framework.Assert.assertEquals(Assert.java:201)
at org.jf.dexlib2.AccessorTest.testAccessors(AccessorTest.java:125)

OS? Java version?
Can't duplicate here.

Windows 7 SP1 x64
JRE 8 Update 45 (64-bit)

Can you try building this tool? - https://github.com/JesusFreke/smali
Apktool updated to 2.0.6, which introduced this unit-test which is failing for you. I want to eliminate the possibility that I introduced the problem or if it also resides in the upstream repo.

Well a while ago I built this branch successfully:
https://github.com/iBotPeaches/Apktool/tree/3208624bf683a982ea8d23aa7d05a249e14c8c3c

Yeah, that doesn't matter much. I merged an entire new upstream version into master, which probably introduced this change.

Got the same result with the above project:
http://oi59.tinypic.com/242de.jpg

Okay thanks!
Must be a Windows issue with smali.

Stack Trace:
http://oi57.tinypic.com/122f4zo.jpg

:brut.apktool:apktool-lib:processTestResources UP-TO-DATE
:brut.apktool:apktool-lib:testClasses UP-TO-DATE
:brut.apktool:apktool-lib:test UP-TO-DATE
:brut.apktool:apktool-lib:check UP-TO-DATE
:brut.apktool:apktool-lib:build UP-TO-DATE
:brut.apktool.smali:dexlib2:accessorTestGenerator:assemble UP-TO-DATE
:brut.apktool.smali:dexlib2:accessorTestGenerator:compileTestJava UP-TO-DATE
:brut.apktool.smali:dexlib2:accessorTestGenerator:processTestResources UP-TO-DATE
:brut.apktool.smali:dexlib2:accessorTestGenerator:testClasses UP-TO-DATE
:brut.apktool.smali:dexlib2:accessorTestGenerator:test UP-TO-DATE
:brut.apktool.smali:dexlib2:accessorTestGenerator:check UP-TO-DATE
:brut.apktool.smali:dexlib2:accessorTestGenerator:build UP-TO-DATE
:brut.apktool:apktool-cli:fatJarPrepareFiles UP-TO-DATE
:brut.apktool:apktool-cli:fatJar

BUILD SUCCESSFUL

Total time: 58.52 secs
C:\Users\Connor\Desktop\Projects\Apktool>

:dexlib2:generateAccessorTestDex
:smali:signArchives SKIPPED
:smali:assemble
:smali:build
:dexlib2:processTestResources UP-TO-DATE
:dexlib2:testClasses
:dexlib2:test
:dexlib2:check
:dexlib2:build

BUILD SUCCESSFUL

Total time: 37.211 secs
C:\Users\Connor\Desktop\Projects\smali>

This is Java 1.8.0_31 on Windows 8.1 Pro. Closing as "cannot duplicate".


Update Version

Version String should be updated with every change in the branch to users can tell what version they have.

Hi David - can you close this PR on your end, changes have already been made to newt that supercede this.

Thanks!
On 18 Feb 2017, at 10:40, David G. Simmons wrote:

Closed #28.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mynewt-newt/pull/28#event-968048640


Fix map fitBounds() when size is constrained

Coverage decreased (-0.1%) to 89.749% when pulling 17624c2e6cd4bfad61c84ddc2fcf5a22155505a8 on fix_fitbounds into 446d15ad45f99f100e74a72b5a205302e63a69d5 on master.


focus-last.py cycles only last two windows

There's MAX_WIN_HISTORY in the script, however, AFAICT it's to handle deleted/closed windows.
I've an idea how to implement this with some timeout reading the communication socket, so that multiple invocations could be used to cycle stack-like through windows.
(I'm filing an issue, in case someone else had more time than me :-)

@nicoe is the author of that script.

MAX_WIN_HISTORY is there in order to prevent the window list to grow indefinitely and only for that.
Of course I don't see any problem with the change your suggesting (I just happen to rarely having to go farther then the previous window).

@Werkov
I understand focus-last to be exactly that, switch to the previously focussed window.
Wouldn't https://github.com/altdesktop/i3ipc-python/blob/master/examples/i3-cycle-focus.py be closer to what you're after?

Thanks for notifyin me about this, it is closer to my use case indeed. (I just need to adjust the delay properly and s/container\.props\./container\./ to work with my version of i3. Since issue is covered with i3-cycle-focus.py, I'm closing this issue.


Enable Users to Report Issues with the metadata

As a data catalogue user
I want a clear and easy way to report issues related to the data (e.g., broken links, incorrect contact details)
So that I can quickly alert the team about problems and help ensure the data catalog remains accurate and reliable.
Acceptance Criteria:

A "Report an Issue" button/link is displayed prominently next to data contact information fields (request access, ask a question, data owner).
The button/link is consistently placed on all dataset pages.
When the "Report an Issue" button is clicked, a form should appear allowing users to select the type of issue (e.g., broken link, incorrect owner, outdated contact) or allow the user to provide the issue details.
The form should have a free-text field where users can provide additional details about the issue.
The form must include fields to collect the user’s contact details (optional) for follow-up if necessary.
The form automatically pre-fills with the relevant dataset information (e.g., dataset name, current contact details) to reduce user effort and improve the accuracy of issue reporting.
After submitting the issue, the user should see a confirmation message stating that their report has been sent.
An automated notification is sent to the relevant dataset owner (if this exists), request originator, the data catalogue team when an issue is reported, including the dataset name, issue type, and user-provided details.

We could borrow from this design, adapting the language

If we want to use GOV.UK Notify I've created a placeholder template which can be edited as needed.
https://www.notifications.service.gov.uk/services/c7a2ad47-e115-4652-b50a-cf05abdc88b8/templates/cc802e26-d308-433b-b523-40ff6a62f8c8
Template ID cc802e26-d308-433b-b523-40ff6a62f8c8

GOV.UK Notify template which can be used to send to the issue reporter
https://www.notifications.service.gov.uk/services/c7a2ad47-e115-4652-b50a-cf05abdc88b8/templates/faf487a0-4d2e-4b9e-a22d-6322f7f7217c
Template ID faf487a0-4d2e-4b9e-a22d-6322f7f7217c

Notify API keys for testing and live have been added to github & 1password as env secrets as NOTIFY_API_KEY

We have found an issue with the notify service where by urls ending with )are incorrectly rendered. We have opened an issue and are currently awaiting an ETA on a fix.


Initial side navigation implementation for Developer Journey

This is the initial set of changes to have a basic
side navigation feature for devjourney. It does everything
that clicking on the table of content items do. The side
navigation bar remains fixed while scrolling. Also,
the top navigation bar has also been set to remain fixed,
making navigation between pages easier.
Signed-off-by: Nazim Uddin Bhuiyan<EMAIL_ADDRESS>I have been unable to publish it so far due to github pages build error. However, it does work locally. @arianneb Please see if you face the same problem while publishing through gh pages.
Here is a screenshot of how it looks like:

@rwy0717 @arianneb I have been able to figure out why my website was not publishing.  Here is the website: https://nbhuiyan.github.io/b9/

Very nice! I'm happy accepting this PR as-is, but here are some thoughts on future patches:

The sidebar should collapse somehow if the user is on their phone.
The sidebar should be generated from either the document itself, or if not possible, a yaml data file.
The sidebar should use scrollspy to follow the user through headings.
I'm not 100% on the top bar sticking to the top of the screen, especially on the phone. It's very fat. Maybe we can slim it down, or display it only on an upwards scroll?

Actually, can you get rid of the old TOC in this PR?

A few comments:

when you click on an item, the top nav bar hides the heading, so it's not immediately apparent that you've gone to the right place. can we fix this?
can we make it a little wider?
as Robert suggested, please delete the original TOC
the side bar isn't auto generated from the headings? @nbhuiyan

Thanks for the feedback. I have removed the TOC at the top. You may view the current state of changes here: https://nbhuiyan.github.io/b9/BuildARuntime.html
While this is just an initial set of changes to have a working side navigation bar, I had a lot in mind that I wanted to implement, but didn't because all of this is new to me. I thought that having a basic sidebar to work on and improve in an iterative manner would be better than trying to do all of it at once.
To address @rwy0717 's comments:

The sidebar should collapse somehow if the user is on their phone.
I agree. It could be a major inconvenience to have it in the way on smaller screens.
The sidebar should be generated from either the document itself, or if not possible, a yaml data file.
Yes, I agree.
The sidebar should use scrollspy to follow the user through headings.
That is going to be a really neat feature!
I'm not 100% on the top bar sticking to the top of the screen, especially on the phone. It's very fat. Maybe we can slim it down, or display it only on an upwards scroll?
I did that since I was having issues with the sidebar not filling the entire height when scrolling past the top. Slimming it down would be good, but I am not sure how much work it is going to be to make it appear when scrolling up.

To address @arianneb 's comments:

when you click on an item, the top nav bar hides the heading, so it's not immediately apparent that you've gone to the right place. can we fix this?
Yes, I noticed the issue and was trying to figure out how to fix it using page anchors. I left it unfixed for this PR since we first needed to settle on whether we wanted to have the top bar fixed or not.
can we make it a little wider?
I kept it narrow to make it easier to deal with on mobile displays. We can make it wider when we make it collapsible.
as Robert suggested, please delete the original TOC
Done
the side bar isn't auto generated from the headings?
Not yet.

I will open an issue to track these.


[BUG]: Issues with Recording Knowledge in the Database

How are you running AnythingLLM?
Docker (local)
What happened?
The content contains special characters, making it impossible to save in the knowledge database.

Are there known steps to reproduce?
No response

This is not what that error means. This means the backend crashed while processing the document. Are you running this locally on Docker or using some other service like Render or Railway to run this?
Often, this can happen if the container reaches its CPU/memory limit and kills the background process for the collector script.

This is not what that error means. This means the backend crashed while processing the document. Are you running this locally on Docker or using some other service like Render or Railway to run this?
Often, this can happen if the container reaches its CPU/memory limit and kills the background process for the collector script.

Okay.
But!
It seems that when an unexpected error occurred, the data was not deleted, even though I had already removed it from the "My Documents" page. Perhaps some additional conditions need to be added to the process.


--live-stream not supported in the docker image

When I pass the --live-stream flag to the docker container, I get the following message:
$ env INPUT_PATH=. OUTPUT_PATH=./output docker-compose run manim --livestream
Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "/usr/local/lib/python3.7/site-packages/manimlib/stream_starter.py", line 38, in __new__
    return Scene(**kwargs)
  File "/usr/local/lib/python3.7/site-packages/manimlib/scene/scene.py", line 37, in __init__
    self, **self.file_writer_config,
  File "/usr/local/lib/python3.7/site-packages/manimlib/scene/scene_file_writer.py", line 44, in __init
    self.init_output_directories()
  File "/usr/local/lib/python3.7/site-packages/manimlib/scene/scene_file_writer.py", line 49, in init_o
    module_directory = self.output_directory or self.get_default_module_directory()
  File "/usr/local/lib/python3.7/site-packages/manimlib/scene/scene_file_writer.py", line 95, in get_de
    filename = os.path.basename(self.input_file_path)
AttributeError: 'SceneFileWriter' object has no attribute 'input_file_path'

Manim is now running in streaming mode. Stream animations by passing
them to manim.play(), e.g.
>>> c = Circle()
>>> manim.play(ShowCreation(c))

>>> c = Circle()
>>> manim.play(ShowCreation(c))
Traceback (most recent call last):
  File "<console>", line 1, in <module>
NameError: name 'manim' is not defined
>>>

I would have expected that I would be able to find the stream in ./output
Environment:
Docker on NixOS. Versions:
$ docker --version
Docker version 19.03.2, build 6a30dfca03664a0b6bf0646a7d389ee7d0318e6e
$ docker-compose --version
docker-compose version 1.24.1, build 4667896
$ uname -a
Linux AquaRing 5.3.5 #1-NixOS SMP Mon Oct 7 17:01:58 UTC 2019 x86_64 GNU/Linux

Livestreaming seems to have been broken in general since scene_file_writer.py was added, and also due to some changes to how directory constants were set. I am currently looking into fixing this, will have a PR up soon.


Fixed portal object misidentification.

The inner mesh was being marked as a portal rather than the wrapper Object3D.

Good catch!


Increase event insertion batch size

To make it less likely that events are added outside of the replacing
postgres transaction we increase the batch size. Should help in case
multiple pods are updating the events at the same time.
See https://github.com/gnosis/gp-v2-services/issues/444
Test Plan
CI

Locally made a new test that inserts 10k invalidation events.