Overwriting readonly task variable 'agent.jobstatus'. Alternative

I've just noticed the following warning in my pipeline
##[warning]Overwriting readonly task variable 'agent.jobstatus'. This behavior will be disabled in the future. See https://github.com/microsoft/azure-pipelines-yaml/blob/master/design/readonly-variables.md for details.

As far as I know, DevOps hasn't provided a good way to cancel a build from a task.
The only options I found were

Set a variable and have ALL subsequent task check the variable (honestly I'm not ever doing this again, it's way too error prone and painful)
Change the agent.jobstatus variable to canceled

  echo "##vso[task.setvariable variable=agent.jobstatus;]canceled"
  echo "##vso[task.complete result=Canceled;]DONE"

This allows me to check if files were changed in certain paths in my git repo and if not I skip the build. Path filters on build trigger is NOT a viable option.
It has saved considerable build and dev time by making this change.
Now I am worried that readonly variable will remove the ability to cancel jobs (for whatever reason, path change is just 1 example).
If readonly variables go forward, what solutions can you provide to allow to cancel a job?

You should be able to do this by hitting an endpoint - https://docs.microsoft.com/en-us/rest/api/datafactory/pipelineruns/cancel
With that said, this is a bit of a weird pattern; our canceled state generally means "cancelled by user" - this is actually an explicit decision on our end https://github.com/microsoft/azure-pipelines-tasks/pull/11845 - so I don't see us officially supporting this via a task or an agent primitive.
cc/ @vtbassmatt to fact check me on this one

You should be able to do this by hitting an endpoint - https://docs.microsoft.com/en-us/rest/api/datafactory/pipelineruns/cancel

The problem is that would cancel the whole pipeline, I have 10 different jobs running in a single pipeline. I have 1 pipeline for PR validation which build/tests a bunch of various folder/project in the monorepo.
I don't especially need the build to be "canceled", simply that it will stop running further tasks and not be marked as failed.

Even if I split the various build in a separate pipeline (which I really would like to avoid), I still wouldn't be able to precisely determine whether to process the build or not (like I mentioned before, path filters on builds is not precise enough).
Additionally, once all my checks are completed, I need to run a release, only when ALL the checks are completed.
I'm not even sure I can mark a release to combine multiple build into 1 release and make sure they're all present AND using the same commit hash.
Assuming that's possible, I'm pretty sure path filters would break that.
From my research when I was looking into a way to cancel builds from a task, I can tell there were a lot of people relying on canceling agent.jobstatus leaving all those people without any alternative mechanism.
Maybe instead of "cancel" it could expose a function to skip the rest of the build or mark it passed, but not processing any further tasks.
Something like
echo "##vso[build.complete result=Succeeded;]"

You can't cancel a single job, because what would that mean for the broader pipeline's status? @damccorm is correct that cancellation is generally user initiated. It also must come from the server (hence the suggestion to call the cancel API) so that it fans out across all running and future jobs. There is also no "early return" concept for a job, though I'm not opposed to that one in principle.
The correct way to implement this pattern is to do your check, set a variable (if single-job) or output variable (if the answer affects multiple jobs), and check that variable in the condition for subsequent tasks. Something like:
steps:
- script: |
    # compute "should I continue" somehow
    echo ##vso[task.setVariable variable=continue]true
- task: foo@1
  condition: and(succeeded(), eq(variables.continue, 'true'))
- task: bar@1
  condition: and(succeeded(), eq(variables.continue, 'true'))

Overwriting system variables was never supported and was always documented as not working. We didn't always enforce that in the context of a single job, which was a mistake on our part. The correct way to change a job's status is to use ##vso[task.complete] (and if one went through that supported path, it would be obvious that the job can't be canceled - that was correctly blocked).

The correct way to implement this pattern is to do your check, set a variable (if single-job) or output variable (if the answer affects multiple jobs), and check that variable in the condition for subsequent tasks. Something like:

I have gone down that route in the past and honestly it's a real mess, whenever you have more than a handful of task and/or task group, it becomes really hard to read and reason how the tasks behave and make sure to not forget any of the tasks to check that variable.
Maybe it's easier to see in yaml, but I'm still using classic editor for the pipeline.
I completely understand your stance on cancelling and in a lot ways I agree.
I used cancel really only because it was the only method I could find for an early return/completion of a build on a specific agent.

I re-read what I wrote, and I realized it may not have come across exactly how I meant it. First of all, thanks for the feedback! I agree that this is way easier to see in YAML and doesn't map very well to classic.
Let me do some thinking about an "early cancel" function, which would solve a lot of people's problems here without overcomplicating our model.

Thanks!
I'm not sure why you closed the issue, but I hope you'll keep me posted.
I'm don't think I still have access, but I remember having to do something similar when I was working on Chakra.
You might be able to access their build definitions
https://github.com/microsoft/ChakraCore
I did use the solution of setting a variable and having every task check that variable

There's not much value in keeping this open; we don't track backlog items in this repo.

So the readonly change was shipped and no solution for an early return has been provided. Now all my jobs trying to stop are failing.
Please tell me you considered an alternative to support this use case?

Could this be configurable? I'm currently overwriting Build.SourceBranch because I need GitVersion extension to run against a repo that I additionally check out. GitVersion uses this variable to get target branch when run with /output buildserver and and there is no other way to set it this case.
This setup is a part of our unit test for GitVersion to make sure that changes to it's configuration file(s) do not bring in unforeseen consequences across multiple repos. To simulate the real build environment I need to run this as an extension which uses  /output buildserver and not just script around it.

@AArnott might be able to take a feature request for GitVersioning (I'm assuming that's the one you mean).
Nothing stops you from overwriting the environment variable itself for a given step. We just won't let you alter the underlying pipeline variable. Something like:
steps:
- task: GitVersioning@1
  inputs:
    foo: bar
  env:
    BUILD_SOURCEBRANCH: (your preferred value)

Here's my current solution:
For Pull Request Validation:

For every place I would normally cancel the build, create a new pipeline and use Path Filters and PR triggers to determine if the pipeline should run
For me this meant breaking down my 1 pipeline with 5 jobs into 11 pipelines (1 with 2 jobs)

For Continuous integration, I couldn't use that strategy because I need to trigger a release after the build (couldn't find a way to make a release depend on multiple builds with path filters).
So instead I have 1 pipeline that checks for files changed in various folder and adds Build Tag to the build.
Then I defined my release to trigger depending on the build tags and various stages depend on individual build tag to do build & tests then have a gated deployment

@AArnott might be able to take a feature request for GitVersioning (I'm assuming that's the one you mean).

Sorry, should've make it clear: https://github.com/GitTools/GitVersion . It has three extensions:

Deprecated: https://marketplace.visualstudio.com/items?itemName=gittools.gitversion
Stable: https://marketplace.visualstudio.com/items?itemName=gittools.usegitversion
vNext: https://marketplace.visualstudio.com/items?itemName=gittools.gittools

I'm in the middle of figuring out migration paths from GitVersion 4.x (no extension, runs as a part of build script) and "Deprecated" to "Stable" or "vNext".

Nothing stops you from overwriting the environment variable itself for a given step. We just won't let you alter the underlying pipeline variable.

That would be awesome, unfortunately I just tested it and it doesn't work:
- task: gittools.gitversion.gitversion-task.GitVersion@5
  displayName: GitVersion
  inputs:
    configFilePath: $(config)
    additionalArguments: /targetpath $(target_path)
  continueOnError: true
  env:
    BUILD_SOURCEBRANCH: refs/heads/FOO
    BUILD_SOURCEBRANCHNAME: FOO

Result:
Applicable build agent found: 'VsoAgent'.
Branch from build environment: refs/heads/feature/some-branch

The code reading env. var in GitVersion is pretty simple, so I guess something else is going on.

Tested with bash task - no luck:
- bash: |
    echo "BUILD_SOURCEBRANCH: $BUILD_SOURCEBRANCH"
    echo "BUILD_SOURCEBRANCHNAME: $BUILD_SOURCEBRANCHNAME"
  env:
    BUILD_SOURCEBRANCH: refs/heads/FOO
    BUILD_SOURCEBRANCHNAME: FOO

Result:
##[debug]noProfile=true
##[debug]noRc=true
##[debug]check path : /home/vsts/work/_tasks/Bash_6c731c3c-3c68-459a-a5c9-bde6e6595b5b/3.163.1/task.json
##[debug]adding resource file: /home/vsts/work/_tasks/Bash_6c731c3c-3c68-459a-a5c9-bde6e6595b5b/3.163.1/task.json
##[debug]system.culture=en-US
##[debug]failOnStderr=false
##[debug]workingDirectory=/home/vsts/work/1/s
##[debug]check path : /home/vsts/work/1/s
##[debug]targetType=inline
##[debug]script=echo "BUILD_SOURCEBRANCH: $BUILD_SOURCEBRANCH"
echo "BUILD_SOURCEBRANCHNAME: $BUILD_SOURCEBRANCHNAME"
Generating script.
##[debug]which 'bash'
##[debug]found: '/bin/bash'
##[debug]Agent.Version=2.165.0
##[debug]agent.tempDirectory=/home/vsts/work/_temp
##[debug]check path : /home/vsts/work/_temp
========================== Starting Command Output ===========================
##[debug]which '/bin/bash'
##[debug]found: '/bin/bash'
##[debug]/bin/bash arg: --noprofile
##[debug]/bin/bash arg: --norc
##[debug]/bin/bash arg: /home/vsts/work/_temp/ba9f22f7-83e2-4293-95a9-378d42222d0c.sh
##[debug]exec tool: /bin/bash
##[debug]arguments:
##[debug]   --noprofile
##[debug]   --norc
##[debug]   /home/vsts/work/_temp/ba9f22f7-83e2-4293-95a9-378d42222d0c.sh
/bin/bash --noprofile --norc /home/vsts/work/_temp/ba9f22f7-83e2-4293-95a9-378d42222d0c.sh
BUILD_SOURCEBRANCH: refs/heads/feature/some-branch
BUILD_SOURCEBRANCHNAME: some-branch

@vtbassmatt - I think in the agent, we convert pipeline variables to environment variables after we set the supplied environment variables for a task.

@jtpetty d'oh, didn't realize that.
@beatcracker I can temporarily disable this change in your account while you figure out an upgrade strategy. What's your organization name? (That would be https://dev.azure.com/<orgname>.)

@vtbassmatt I'm not clear on how this feature is rolled out: currently I only get warnings, but it still works. However if you could postpone cut-off, that would be fantastic. Would you mind if I drop you an email on<EMAIL_ADDRESS>(or any other address) ? I'd rather not share an organization name here.
@jtpetty Thanks, that's pretty much explains it. Is there any chance that I could create an issue on this, so this behavior could be changed?

Hey @beatcracker you can email my work address<EMAIL_ADDRESS>with your org name.
We're probably not going to change the variable override behavior. Despite the fact that I didn't know the precise details, I can virtually guarantee there are dozens of customers depending on the exact behavior today.

I think in the agent, we convert pipeline variables to environment variables after we set the supplied environment variables for a task.

That still shouldn't stop you from defining env vars within the task itself. Like this:
- bash: |
    export BUILD_SOURCEBRANCH=refs/heads/FOO
    export BUILD_SOURCEBRANCHNAME=FOO
    echo "BUILD_SOURCEBRANCH: $BUILD_SOURCEBRANCH"
    echo "BUILD_SOURCEBRANCHNAME: $BUILD_SOURCEBRANCHNAME"

I just want to clarify that if I have a pipeline with say 15 tasks but on the 5th task I check some value that determines that I do not want to proceed further that I now have to set and check a variable in the subsequent 10 tasks and remember to do that on any next task I create? There is no way to cancel or return success early without running through every task? I guess we could have two agent jobs and have the second job check a variable from the first and not run but that is also cumbersome because variables/task work from the first job I would have to duplicate in the second job because of the separation of data in jobs.

The execution model is that each step gets a shot at executing and makes its own decisions about what to do. So, there's no one-liner to model an early, successful return. If it helps, keep in mind that every step already has a default condition it's checking. That condition is succeeded(). Your override would be and(succeeded(), not(eq(variables['mycheckvar'], 'true'))).

It seems having two agent jobs should clean it up once we can switch to yaml and pass variables between jobs. Thank you @vtbassmatt  !

@vtbassmatt you mentioned "Let me do some thinking about an "early cancel" function, which would solve a lot of people's problems here without overcomplicating our model."
Have you thought about it? Seems like a lot of people are requesting this feature.
The suggestion of using and(succeeded(), not(eq(variables['mycheckvar'], 'true')))
is cumbersome in classic.

We discussed it and thought through some designs. It doesn't rank on our current list of priorities unfortunately.

Is there a way to turn off this behavior that stops BUILD_SOURCEBRANCH from being modified on Azure DevOps Server 2022 Update 2 patch 1?


CVE-2023-5129

Your program uses libwebp, make sure to update it to fix CVE-2023-5129 which is currently making the rounds.

pulled the latest libwebp source, hopefully this covers it


Fix fancy quotes in a code sample.

@scovetta,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@scovetta : Thanks for your contribution to the Azure documentation! The author, @YuriDio, has been notified to review your proposed change.

Looks good.
#sign-off


Replaced ghodss/yaml with sigs.k8s.io/yaml [dev-v3]

What this PR does / why we need it:
This PR proposes a replacement of github.com/ghodss/yaml with it's forked version maintained by SIG community. The replaceable library has low-to-none support activity unlike the latter. The SIG version is marked as a permanent fork. We believe the new Helm branch (v3) could benefit from using the Kubernetes community-maintained version on a long-term run as yaml parser is a key component of Helm chart rendering engine.
This commit locks sigs.k8s.io/yaml dependency version on 1.1.0 which is backwards compatible with ghodss/yaml 1.0.0 (this statement needs a remark: strictly speaking, the change is breaking: see the relevant comments: https://github.com/ghodss/yaml/issues/50#issuecomment-465777941 and https://github.com/ghodss/yaml/issues/50#issuecomment-511004721, but after a deep dive, Helm and it's dependencies are believed to be backwards compatible with the change).
This change also resolves the outdated dependency version lock for ghodss/yaml (currently 1.0.0) and makes it possible to port changes from https://github.com/helm/helm/pull/6010 to dev-v3.
Signed-off-by: Oleg Sidorov<EMAIL_ADDRESS>Special notes for your reviewer:
I was asked to port changes from https://github.com/helm/helm/pull/6010 to dev-v3. If this change makes sense, porting the fix would be a pretty trivial follow-up step.
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[x] this PR has been tested for backwards compatibility

@adamreese or @bacongobbler can one of you take a look at this as well? This is a major dependency change that looks like it is ok, but I want two maintainers to sign off on it just to be sure


Support for GitHub Issue creation and syncing of tasks

This partially implements issue creation and syncing of tasks / exercises. It needs to be revised before merging.
Fixes #302

Closing in favor of #595, since I wasn't able to push to this PR (access denied).


How to use in browser?

Is there a possibility to use delegated-events in an old-school way? Something like this:
<script src="/path/to/delegated-events.js"></script>

window.on(...)
window.off(...)
window.fire(...)

The package's main file entry points to dist/index.umd.js. If you copy that file out of the package, or clone the repository and run npm run build, you can reference it with a script tag.
The functions are exported on a delegated-events global.
window['delegated-events'].on(…)


state: Verify DNS configuration

Introduce state.verify_dns() to verify desire DNS configurations with
current.

Wait on PR #374


Having an issue with adding service monitoring.

When I try to monitor an application, for example Redis, I'm having issues.
My config:
*docker-compose.yml:
prometheus:
image: stefanprodan/swarmprom-prometheus
environment:

JOBS=redis-exporter:9121

*prometheus.yml:
job_name: 'redis-exporter'
dns_sd_configs:
names:
'tasks.redis-exporter'
type: 'A'
port: 9121
*compose-redis.yml:
version: '3'
networks:
mon_net:
external: true
services:
redis:
image: redis
networks:

mon_net
ports:
"6379:6379"
deploy:
mode: global

redis-exporter:
image: oliver006/redis_exporter
networks:

mon_net
ports:
"9121:9121"
deploy:
mode: global

When I run the monitoring stack and then compose-redis:
Prometheus goes up and down all the time.
Log shows:
level=error ts=2018-02-19T16:49:15.594740858Z caller=main.go:582 err="Error loading config couldn't load configuration (--config.file=/etc/prometheus/prometheus.yml): parsing YAML file /etc/prometheus/prometheus.yml: unknown fields in alertmanager config: job_name"
I have no idea how to fix this or what I did wrong.
Any help would be appreciated.
Sorry for posting in the wrong place at first.
Thanks

Thanks for reporting this, please wait 10 minutes for the new image swarmprom-prometheus:v2.2.0-rc.0 to be published on Docker Hub and give it a run. You should delete the old image from your Swarm cluster.

Hi
Sorry I was on my way home, couldn't test sooner.
Did a quick local install on my computer at home.
I think it's working now!

It's communicating with the exporters now, though they are not giving me any data except for how many times they have fetched the data. I suppose there is still something wrong with the link between my Redis and Redis-exporter.
However my original issue seems to be solved.

Also the dockerd-exporters seem to be offline, they are running though when I check with 'docker service ls'. It might have been me testing quickly.
I will test when I'm back at my internship tomorrow.
Thanks a lot for your help.

Forgot to enable the experimental mode, that's most likely why the daemon is "offline".


Migrate senzing/senzingapi-runtime-beta to senzing/senzingsdk-runtime-beta

See https://github.com/senzing-garage/template-go/issues/176
Change
observe/Dockerfile:ARG IMAGE_FINAL=senzing/senzingapi-runtime-beta:latest

Pull requests:

https://github.com/senzing-garage/observe/pull/114


feat(telemetry): track more daemon errors

Description
Track some more cache / daemon related errors.

We actually do have a global cell 😄 so we don't need to thread it.
But in my experience instrumenting this, it turns out we use it at most of the levels anyway, and if we do thread it we get the extra information of the parent / child event relationship, so it's nicer to do it that way.
But if there is something super deep, we don't have to thread it, we can just create an event from there and send it.


fix: improve footer visibility for copyright text and social links

What happened?
When scrolling down to the footer, the copyright text and social links are partially covered by the language change button and chat button, making them difficult to view.
What was done

Adjusted the layout and spacing of footer elements to ensure visibility.
Centered

How to Test

Scroll down to the footer on any page.
Verify that the copyright text and social links are fully visible.
Ensure that the language change button and chat button no longer obstruct footer content.

Additional Notes
This fix addresses the visibility issue but may require further adjustment if additional elements are added to the footer in the future.
Video Demonstration
https://github.com/user-attachments/assets/0f5106b6-1de1-4fc3-b07c-47dc27d3eb2f

fixes #162

Gentle Reminder 🚨🚨
GSSoC-Ext 24 is going to complete in 2 Days. '
Complete your assigned Issues and PR reviews before time to get Points on Leaderboard. '
It was a great experience working with you all, Don't forget to ⭐ star the Repo (only 12 with 62 forks 💔) .
Thanks💗 for your valuable contributions!

Gentle Reminder 🚨🚨
PA and Mentor nominations have been started for GSSoC-Ext 2k24. '
Do share your experiences and connect on Socials. '
It was a great experience working with you all
Thanks💗 for your valuable contributions!


python example with aws loadbalancer connection stuck

Expected behavior
hope connect to broker through LB  like directly connect
2018-12-20 17:36:10.667 INFO  ConnectionPool:63 | Created connection for pulsar://localhost:6650
2018-12-20 17:36:10.668 INFO  ClientConnection:285 | [<IP_ADDRESS>:56428 -> <IP_ADDRESS>:6650] Connected to broker
2018-12-20 17:36:10.671 INFO  HandlerBase:53 | [persistent://public/default/test-topic, ] Getting connection from pool
2018-12-20 17:36:10.671 INFO  ConnectionPool:63 | Created connection for pulsar://ip-172-31-xx-xx.cn-north-1.compute.internal:6650
2018-12-20 17:36:10.673 INFO  ClientConnection:285 | [172.31.xx.xx:45238 -> 172.31.xx.xx:6650] Connected to broker
2018-12-20 17:36:10.678 INFO  ProducerImpl:155 | [persistent://public/default/test-topic, ] Created producer on broker [172.31.xx.1xx:45238 -> 172.31.xx.xx:6650]
2018-12-20 17:36:10.725 INFO  ProducerImpl:467 | [persistent://public/default/test-topic, pulsar-cluster-1-1-11] Closed producer

Actual behavior
2018-12-20 17:36:54.006 INFO  ConnectionPool:63 | Created connection for pulsar://pulsar-internal-xx:6650
2018-12-20 17:41:08.502 INFO  ClientConnection:285 | [172.31.xx.xx:44014 -> 172.31.xx,xx:6650] Connected to broker
2018-12-20 17:41:08.508 INFO  HandlerBase:53 | [persistent://public/default/test-topic, ] Getting connection from pool
2018-12-20 17:41:08.510 INFO  ConnectionPool:63 | Created connection for pulsar://ip-172-31-xx-xx.cn-north-1.compute.internal:6650
2018-12-20 17:41:08.512 INFO  ClientConnection:285 | [172.31.xx.xx:45246 -> 172.31.xx.xx:6650] Connected to broker
2018-12-20 17:41:08.516 INFO  ProducerImpl:155 | [persistent://public/default/test-topic, ] Created producer on broker [172.31.xx.xx:45246 -> 172.31.xx.xx:6650]
2018-12-20 17:41:08.565 INFO  ProducerImpl:467 | [persistent://public/default/test-topic, pulsar-cluster-1-1-12] Closed producer

when connect to broker through aws LB the connection stucks for about 5mins
Steps to reproduce
produce every time
System configuration
Pulsar version: 2.2.0
should I adjust some config with LB?

@lxkaka - can you try to telnet ip-172-31-xx-xx.cn-north-1.compute.internal 6650?

@sijie, thanks for reply.  telnet no problem
  import pulsar
 # this is one of borker ip
  add = 'pulsar:// ip-172-31-xx-xx.cn-north-1.compute.internal:6650'
 #  this is lb dns
  add1 = 'pulsar://pulsar-internal-611b37bee1faecc4.elb.cn-north-1.amazonaws.com.cn:6650'
  client = pulsar.Client(add1)

when use lb dns, the connection stucks shows above

@lxkaka can you telnet the lb dns?

@sijie telnet the lb with timeout sometimes. More likely this is the lb problem?

@sijie I found the problem.  For example broker 1 can not telnet broker 1 through network elb.

@lxkaka have you fixed the problem?

@sijie In real case  we consume or produce messages not in the instance with broker, so thers is no problem. You may close this. Thanks

closed the issue as discussion above


Bad Output Results

Hello!
I try to implement cartographer ros in a rotating SICK laser but I cannot get it work.
Here is my link "https://github.com/athtest800/cartographer_ros"
I use my custom "demo_slam_3d.launch" file with the included "houses.bag" file in the bag folder.
Is there a solution? or the SICK laser, due to its low point density, is not suitable for cartographer?
Thank you.
Ath

There are many Sick lasers with different resolutions, could you specify?
You started with the 3D algorithm, for this you need at least ~4 rows, more are better.
I'd recommend to start with the 2D algorithm first if your data permits.


ENH use current user for docker executor to avoid root permissions mangling

Currently, files created or modified within Docker containers are often owned by root, leading to permission issues when users try to manipulate these files outside the container. This requires additional steps to manage files during testing because we need to run a docker container to add/remove files. By allowing Docker to run with the current user's permissions, we streamline the development workflow so files are interoperable between local context and docker context.

Effort to finesse this not worth it at the moment


Queues in multiple connections

In my queue.php config I have multiple connections (redis is a connection on db0 redis and watchfolders on db1 redis)
Pulse only shows the redis:default queue but not the others, even the ones that uses the same connection redis.

I have my supervisor with the different artisan:work's in another "container-pod" (different to the one accepting http request), working as intended and getting all jobs etc.

It should be something related to tenancy https://tenancyforlaravel.com/  :( I will investigate further


Roll Flutter Engine from 34ece7a4abac to b9aa2b727a14 (4 revisions)

https://github.com/flutter/engine/compare/34ece7a4abac...b9aa2b727a14
2023-04-25<EMAIL_ADDRESS>Made sure not to turn on wide gamut support without impeller. (flutter/engine#41460)
2023-04-25<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from 5bc9_eyVcLoMrWvdO... to JKHSUjf-qEr0ZMdEi... (flutter/engine#41493)
2023-04-25<EMAIL_ADDRESS>Roll Skia from 1bed4228ea3b to f6f0c4b5ee98 (7 revisions) (flutter/engine#41492)
2023-04-25<EMAIL_ADDRESS>[Impeller] Fixed blit command missing tracking and added mock vulkan for tests (flutter/engine#41408)
Also rolling transitive DEPS:
fuchsia/sdk/core/mac-amd64 from 5bc9_eyVcLoM to JKHSUjf-qEr0
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jsimmons@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


How to get a video link without a watermark?

how to get a video link without a watermark?

waiting


Add examples for fakes

Will update when fake goes GA.

Yes, will add links from azcore and the README.md files for other SDK modules (e.g. here).

/check-enforcer override


Does LexicMap gives result with paried end fastq data and abundance score ?

I have paired end data out of illumina in fastq format
like file_R1.fastq and file_R2.fastq
Does LexicMap gives result with paried end fastq data and abundance score ?
I have indexed my reference database as per lexicMap protocol

Does LexicMap support short reads?
LexicMap is mainly designed for sequence alignment with a small number of queries (gene/plasmid/virus/phage sequences) longer than 200 bp by default.

Dear @arpit20328, LexicMap is not designed for paired-end short reads.  And no abundance information is outputted.
If you're looking for metagenomic profiling tools, have a look at my KMCP


Replaced obsolete mime types

Sincerely,
https://www.maxcdn.com/one/tutorial/mime-types
https://www.rfc-editor.org/rfc/rfc4329.txt

Thanks hero


Change key length to 2048 due to Imperva change

https://docs.imperva.com/bundle/cloud-application-security/page/release-notes/2021-09-05.htm#RSAkeylengthlimitforcustomcertificates

There is a better solution


[Bug]  I can't open vrcx.

It is not working for me. I have already reinstalled it 2 times, but vrcx won't open..
I click on the icon and nothing happens. When i click again, it says VRCX is already open, but there s no vrcx windows.
I have downloaded latest version, still nothing has changed

which version of vrcx are you running?
Nightly or Stable?

also if you haven't check the tray icon at the bottom of your taskbar and double click it.

about version idk.. i just downloaded these 2 files, opened them, it said vrcx download is finished and thats it

everything was alright yesterday, today smth happenned

about version idk.. i just downloaded these 2 files, opened them, it said vrcx download is finished and thats it

you only need to download one of the files, the zip is portable installation while the exe is a installer version, try going to your vrcx installation directory and running vrcx manually, if it still says vrcx is already open open task manager (Ctrl + Shift + Esc) and navigate to the Details tab and manually close all instances of VRCX.exe and try again

I tried to do this, but it didnt open. I have noticed that when i click on vrcx it appears in the task manager, and after about 40 sec it disappears from there

like it closes itself

like it closes itself

its possible that the upgrade to .net 8 in the latest release is missing the runtime, try installing the .net 8 desktop runtime from Microsoft .net 8 and restart your pc
Direct link here
https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-8.0.1-windows-x64-installer

well.. i did everything you said and nothing changed:(
idk whats the problem..

can you go to %AppData%\..\Roaming\VRCX\logs and post the latest log file? should be called VRCX.log

which one?

the first one

hmm interesting, vrcx is reporting no issues, not sure what the issue could be.

:,(

werfault apperars before vrcx closes in task manager

werfault apperars before vrcx closes in task manager

do you happen to have a crash dump from vrcx? these usually are located in %AppData%\..\Local\CrashDumps

can you check the direct path?

yep

can you upload the latest version, sort by date and send the most recently generated .dmp file.

this?

yes vrcx.exe.15152

VRCX.exe.15152.dmp

try rebooting your computer and running windows update, if the issue persists try running these commands in an administrative windows command prompt or windows terminal

regsvr32.exe /u ntdll.dll
regsvr32.exe ntdll.dll
then reboot again and attempt to start vrcx

if neither of the suggestions work its time for you to run system file checker, open command prompt as adminstrator as seen by the picture above and run
sfc /scannow

For a wrap up for this, the dump indicates that your windows system integrity is damaged and the reported fault is in ntdll.dll which is a core windows system component if neither of the provided fixes work then you will have to reinstall windows or attempt a higher level repair such as using windows DISM

sounds bad:( thank you so much anyways..

I have the same issue as @ladyc0libri . When I go to open VRCX from the system tray, the window does not appear. Attempting to re-open will say that VRCX is already running. I forced closed the process from task manager. I even checked my system with /sfc scannow. It reported corrupt files but fixed them. My VRCX log looks the same as theirs.
I opened the devtools window by right clicking the system tray icon, and checked the screen coordinates in the console. It seems to be off the screen? The y coordinate seems to be putting the window below the taskbar.

Inside the %appdata%/VRCX/VRCX.json file contains an entry as such, "VRCX_LocationY": "1066". If I change y coordinate from 1066 to 0, it temporally fixes the bug.
I'm thinking the program should, when starting up, check if the initial coordinates is going to put it off screen. If true, then reset the coordinates to 0.
Windows 10 Pro, build 19045.3930
VRCX 2023.12.24
VRCX.log

I have the same issue as @ladyc0libri . When I go to open VRCX from the system tray, the window does not appear. Attempting to re-open will say that VRCX is already running. I forced closed the process from task manager. I even checked my system with /sfc scannow. It reported corrupt files but fixed them. My VRCX log looks the same as theirs.
I opened the devtools window by right clicking the system tray icon, and checked the screen coordinates in the console. It seems to be off the screen? The y coordinate seems to be putting the window below the taskbar.

Inside the %appdata%/VRCX/VRCX.json file contains an entry as such, "VRCX_LocationY": "1066". If I change y coordinate from 1066 to 0, it temporally fixes the bug.
I'm thinking the program should, when starting up, check if the initial coordinates is going to put it off screen. If true, then reset the coordinates to 0.
Windows 10 Pro, build 19045.3930 VRCX 2023.12.24
VRCX.log

this is a unrelated issue, your vrcx remains working as expected, in ladyc0libri case their vrcx copy completely crashes because of a integrity violation within windows, as for your issue with vrcx this can be fixed by holding windows key + arrow up after clicking on vrcx in task manager to bring it back into focus, this is a common issue with desktop applications on windows especially when using a multi monitor setup, the json is updated based on a timer when you resize or close the window as to save on write spam.

I'm not sure if this is the reason, but smth doesn't allow me to run a windows update. I got 0x80070643 error
Microsoft has confirmed a massive error 0x80070643 (can be designated as ERROR_INSTALL_FAILURE) when installing the KB5034441 update on Windows 10 and Windows 11 version 21H2; the error does not appear to appear in newer versions of the system.

btw in cmd it says No damage to the component store was detected.
The operation was completed successfully.

i did, got the Error: 1 Invalid function.
(Dism /Online /Cleanup-Image /StartComponentCleanup)
Dism /Online /Cleanup-Image /RestoreHealth this one was ok

attempt to run vrcx, again if its not we cannot help you any further as the issue is caused by your system.


Steps { and } should not be used for step / code blocks

ISSUE - In release v1.8, steps { and } are introduced to define steps and code blocks. This adds convenience and powerful automation when used with if/for/while/popup/frame.
The idea is replacing { with
// start of code block
{casper.then(function() {

And replacing } with
})}; // end of code block

The above replacements and some tracking logic will automatically take care of CasperJS code blocks formatting. However, as { and } can also be used in JavaScript to define code blocks, there can be situations where developers want to define custom functions or events which above auto-replacement will break their code. Unless they use js step to explicitly tell TagUI to treat that line as pure JavaScript and not to parse it as a TagUI step.
There should be a better way so that developers do not have to type js { or js } to explicitly treat the line as JavaScript, and normal users can define step/code blocks easily. Maybe checking [ and ] instead as the single character on the line as markers for start and end of step/code block.

Reclassifying more appropriately as a bug because v1.8 may break the original design of users who have used { and } to mean traditional JavaScript code blocks.

Thinking through, it seems that there is probably no existing use case which will encounter an issue with the above auto-replacement to casper context blocks. This is because lines in the automation flows are already by default in casper context.
Developers wanting to add custom functions would have to define them in tagui_header.js. Unless they manually close the casper context, define them, and reopen casper context. In that case using js step to explicitly declare as JavaScript code would work.
Readme should officially include js step. This should be a good balance between pro-developers flexibility and quick prototyping convenience.

Closing and changing to enhancement category - adding js step officially to readme documentation.


[DOCS] Update clustering docs

Change Logs
Update clustering docs.

Add a section on compaction vs clustering.
Add a section on clustering usecases - picked up from https://medium.com/@simpsons/storage-optimization-with-apache-hudi-clustering-aa6e23e18e77
Separate out strategies from async indexing.

Impact
Docs update.
Risk level (write none, low medium or high below)
low
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@codope, could you please add a section on Flink clustering? IMO, the Flink clustering is popularly used by community users.

could you please add a section on Flink clustering? IMO, the Flink clustering is popularly used by community users.

@danny0405 Could you help here? Maybe in a separate follow-up PR if not this one?

@codope, I have left one comment for the clustering plan strategy. PTAL.

@SteNicholas Do you have intreast for the Flink clustering document?

@danny0405, yes. Could the document of the Flink clustering be added in clustering.md? cc @codope

or cc @bhasudha if we can mere this, I'll do another run and pick it up from here.


feat(#177): Hide node in XmlClass

Hide XmlClas#node field inside XmlClass. Incapsulation.
Closes: #177.

History:

feat(#177): remove the 'node' method from XmlClass
feat(#177): simplify XmlClass
feat(#177): make XmlClass look better
feat(#177): remove redundant suppressings
feat(#177): remove Node class usage from XmlClassProperties

PR-Codex overview
Focus of this PR:
This PR adds a new method asDocument() to the XmlNode class and updates the XmlClassProperties and XmlClass classes to use the new method.
Detailed summary:

Added a new method asDocument() to the XmlNode class.
Updated the XmlClassProperties class to use the asDocument() method.
Updated the XmlClass class to use the asDocument() method and made other code improvements.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 4min)


Implement basic mod lints

This PR adds a new cli action ActionLint, run as drg_mod_integration lint $PROFILE, to perform some basic mod lints for the given $PROFILE. This PR also adds a mod lint button and a lint report GUI.

Currently implemented mod lints:

Lint mod conflicts.
Lint AssetRegistry.bin.
Lint incorrectly included shader files.
Lint outdated pak version.
Lint empty archive.
Lint archive containing only non-pak files.
Lint archive containing multiple paks.

Some basic manual testing can be done by creating a "test" profile which consists of two mods:

https://mod.io/g/drg/m/cave-leech-obi-wan-hello-there#1937463
https://mod.io/g/drg/m/spy-leech#2040409 (this has shader bytecode)

Pending Work

[x] Need to add some integration tests for the basic lints. We'd probably want to have some test mods for testing mod integration as well anyway.

cc #39.

It's not clear to me what test_mod_batches is supposed to me. I would opt for test_assets to contain anything test-related that's not actual code.
I'm also considering not including any archives (zip or pak) in the repo at all and instead build them from loose files when needed. This would make modification easier and would also provide more meaningful diffs. However, any tests are better than no tests so I'm find with how it is currently. Something to think about for future improvements.

I'm also considering not including any archives (zip or pak) in the repo at all and instead build them from loose files when needed. This would make modification easier and would also provide more meaningful diffs.

I agree with this, though it would require the integrations to have a build step and I'm not very sure how that would be nicely handled.


document that trailing slashed are supported.

no need to define /hello/?  just /hello

and /hello/ is equivalent to /hello

then add it to the docs, (see the title of this issue.)


Rust-gpu 0.6 was just released

Hi!
Awesome work with this rust-gpu integration for Bevy!
We from rust-gpu just released 0.6.0. I still have to write the release notes, but I was wondering if I could use this bevy rust-gpu gif as a featured title image?

Thanks, it's here: https://github.com/EmbarkStudios/rust-gpu/releases/tag/v0.6.0 🙂

Bevy Rust-GPU is now 0.6 compatible :partying_face:


Inconsistency when patch version is leaved out in VersionReq

If I have a requirement like 0.30, it would match 0.30.0. However if the requirement is 0.30-beta.1, it does not match 0.30.0-beta.1.
I just went through the SemVer documentation without finding much related info. Actually I doubt whether such a requirement is really allowed?
Playground
extern crate semver;

use semver::{Version, VersionReq};

fn main() {
    let req = VersionReq::parse("0.30").unwrap();
    let ver = Version::parse("0.30.0").unwrap();
    println!("{}", req.matches(&ver)); // true

    let req = VersionReq::parse("0.30-beta.1").unwrap();
    let ver = Version::parse("0.30.0-beta.1").unwrap();
    println!("{}", req.matches(&ver)); // false
}

if the requirement is 0.30-beta.1,

Yeah, I'm not sure this is a well-formed requirement. Hmmmm

@steveklabnik You meant 0.30-beta.1 is not well-formed but 0.30 is? I reckon to maintain consistency they should be both either legal or illegal.
But since it's not well-documented and actually requirements like 0.30 have already been used from time to time, what about applying similar rules to 0.30-beta.1 as well so that it can match 0.30.0-beta.1?

The semver spec doesn't discuss matchers at all, so there's more freedom here. We should investigate what matchers bundler and npm accept.

Version constraint 0.30-beta is
...invalid in npm:
const semver = require('semver')
semver.satisfies('^0.30-beta', '0.30.0-beta') // TypeError: Invalid Version: ^0.30-beta

...valid in composer: https://getcomposer.org/doc/articles/versions.md#stability-constraints
use Composer\Semver\Semver;
var_dump(Semver::satisfies('0.30.0-beta', '^0.30-beta')); // bool(true)

...valid in gem: http://guides.rubygems.org/patterns/#pessimistic-version-constraint
puts Gem::Dependency.new('', '~> 0.30-beta').match?('', '0.31.1'); // true

Actually Semver does specify this, in an indirect way:

If a version has a prerelease tag (for example, 1.2.3-alpha.3) then it will only be allowed to satisfy comparator sets if at least one comparator with the same [major, minor, patch] tuple also has a prerelease tag.

This seems to imply that the the specification must have a patch version number for a version with pre-release tag to be compatible. That seems to implies that either requirements like ^0.30-beta are invalid or ^0.30-beta should not match 0.30.0-beta.
Of course trying to interpret the specifications as literally as possible is not necessarily useful. But if we are to allow rules like ^0.30-beta then we need to decide:

Should ^0.30-beta match 0.30.0-beta2? Probably yes.
Should ^0.30-beta match 0.30.1-beta2? Questionable (quote above says pre-tags should not match if patch number differs). I'm going to say the only sensible answer, however, is yes.
Should ^0.30 >=0.30.0-beta match 0.30.1-beta2? I don't know. Intuitively it looks like it should, while the rule quoted above will imply it cannot; version numbers are not intuitive!

Personally I'd like to simplify the rules by:

Allowing prerelease tags without minor/patch version numbers (like 0-beta, 0.5-pr1)
Remove the quoted rule and instead require prerelease checking in every =, ^ and ~ number (so the pre_tag_is_compatible function can be removed and is_exact, matches_tilde and is_compatible all check pre_is_compatible (or pre_is_equal) at the start of the function)

Note that the above implies >=1.0 would now match 1.0-pre1. I'm not sure if we should fix this; if so we'd either need to add the quoted rule back in special cases or we'd need to break ordering (so !(1.0 <= 1.0-pre1) and !(1.0 >= 1.0-pre1)) or we'd need some weird ordering rules (IIRC Debian would consider 1.0-pre1 < 1.0 or something like that).
Then there's the question of how many project builds would get broken by changing the rules now. I suspect it wouldn't be too bad since prerelease tags aren't used very much and most version specifications are of the form x / x.y / x.y.z which semver interprets as ^x etc., in which case prerelease tags would not be interpreted differently aside from the weird cases mentioned above.
@steveklabnik I hope you are okay making some minor changes here? I'm quite happy to make a PR but we need to make some decisions first.

I am okay with making some changes, as long as they're going towards the spec and not away from it. :) In general, getting us to be compatible with npm's implementation is my goal. I actually wanted to make a comparison between major implementations, but hadn't had the time yet...
I'm super busy at the moment (just showed up at the work week) so I can't fully commit to a direction here, but it seems like we should change this; that is, in line with the principle above.

It seems like prerelease tags are only expected when a patch version is present, making 0.30-beta invalid.
Regarding the other issue, it's not very clear whether NPM considers 1.2.3-beta to come semantically before or after 1.2.3; prerelease tags are discussed right next to range selection but the two issues don't intersect. Does 1.2.3 match >= 1.2.3-beta for example?

@isaacs if you have a chance, any comment on ☝

/me is summoned
There's some confusion here about what spec governs semver ranges.  SemVer.org has detailed specifications for semver versions, but says nothing about ranges.  (In the 2.0 version of the spec, the word "match" was struck entirely, specifically because it is ambiguous and confusing to talk about "matching" without treating ranges and versions separately.  Versions don't match/satisfy one another; versions satisfy ranges, ranges match versions.)
The most popular existing implementation of semver ranges (by usage) is node-semver.  So I'll treat that as if it's a spec, and talk about how it handles ranges and specifically, ranges with prerelease tags.
In node-semver, 0.30-beta is just not a valid range designation:
> semver.validRange('0.30-beta')
null

You could do something like ^0.30.0-beta or ~0.30.0-beta.  In both cases, it would match any 0.30.0 version with a prerelease at or above beta (in an alphabetical sort).  But, it would not match 0.30.1-beta, because the prerelease tag is attached to the {0, 30, 0} tuple, not the {0, 30, 1} tuple.
There is no way with node-semver ranges to specify "any version at or above 0.30.0, which has a prerelease tag at or above -beta".  As others have pointed out, this is confusing, since 0.30.1-alpha may be "later" than 0.30.0, but is it ready?  Should it match?  Does it conform to the SemVer semantics of only containing non-breaking non-additive changes?
Prerelease tags are a separate universe that lives in a pre-committed state.  It's "allowed" by the SemVer specification to have a 1.2.3-beta version that breaks entirely from 1.2.2.  It's assumed to be a mistake, but mistakes are common and expected in prereleases (one might argue that's what betas are for, after all).  If you wish to opt into beta testing, you have to specify that in the range, but you aren't opted into beta-testing future versions without opting in again.  Because that would be weird.

Does 1.2.3 match >= 1.2.3-beta for example?

Yes, it does:
> semver.satisfies('1.2.3', '>=1.2.3-beta')
true

According to the SemVer spec, a prerelease tagged version is lower in the sort ordering than its non-prerelease-tagged counterpart.
$ semver 1.2.4 1.2.4-beta 1.2.2 1.2.5 1.2.3
1.2.2
1.2.3
1.2.4-beta
1.2.4
1.2.5

However, note that >= and <= will still omit prerelease tagged versions unless the named version in the range has a prerelease tag on it:
$ semver 1.2.4 1.2.4-beta 1.2.2 1.2.5 1.2.3 -r '>=1.2.3'
1.2.3
1.2.4
1.2.5

$ semver 1.2.4 1.2.4-beta 1.2.2 1.2.5 1.2.3 -r '>=1.2.4'
1.2.4
1.2.5

$ semver 1.2.4 1.2.4-beta 1.2.2 1.2.5 1.2.3 -r '>=1.2.4-alpha'
1.2.4-beta
1.2.4
1.2.5

$ semver 1.2.4 1.2.4-beta 1.2.2 1.2.5 1.2.3 -r '>=1.2.4-alpha <1.3 || 1.2'
1.2.2
1.2.3
1.2.4-beta
1.2.4
1.2.5

There's no law of the universe that says that this implementation of semver in Rust necessarily must match the implementation of semver in JavaScript, but if that is the goal, this is the answer.  And if y'all go a different way on this, it's probably worth mentioning in the docs or something, so users of npm and cargo don't get confused :)

This is fixed in 1.0.0 — 0.30-beta.1 is not considered a valid VersionReq.
This aligns with the grammar described in https://github.com/semver/semver/blob/efcff2c838c9945f79bfd21c1df0073271bcc29c/ranges.md.


[Bug]: Cannot add embedding back into collection using the same id after collection.delete() several times

What happened?
Issue:
Cannot add the embedding back to the collection for the same id, after deleting this id from the collection
Description:
I have loaded around >20K records into a collection hosted in a HTTP chroma server, each records has: [ids, metadatas, embeddings, documents]. The embeddings are computed from OpenAI's "text-embedding-ada-002" model.
After a group of record with same ids (e.g. 'error_id') in the collection got update (delete then add) for several times (observed 2 or 3 times). the embeddings could not be added into the collection using the same id anymore.

The way I did update is collection.delete(ids=['error_id', ...]), and then collection.add(ids=['error_id', ...], metadatas=[...], embeddings =[...], documents=[...])

when perform collection.add(), no error ever reported. The log in the server side shows the .add() is successful.

when perform collection.get(ids = ['error_id'], include = ['embeddings'])
The result returns like this
{'ids': ['error_id'], 'embeddings': [], }
The embeddings returned are always a empty list
But if I load the same embedding using a different id (e.g. error_id_2), the embeddings could be successfully added. And after collection.get(), I could see the embedding list with correct dimension

Here is my collection metadata:
collection.metadata
(20000,  {'hnsw:M': 64,   'hnsw:construction_ef': 100,   'hnsw:search_ef': 10,   'hnsw:space': 'ip'})
Does anyone encounter the same issue and know what's happenning?
(Note: the reason I did not use collection.update() but .delete() then .add() is that I observe the collection.update() will cause collection.query() error, not sure why is that either. But .delete() then .add() will not affect the .query() performance)
Versions
Chroma v0.3.26, Python 3.10.11 macOS 14.0
Relevant log output
No response

Could you please try on the latest version of chroma? We released a slew of fixes post v0.3 and this may be a solved issue.

Could you please try on the latest version of chroma? We released a slew of fixes post v0.3 and this may be a solved issue.

Thanks for the reply! By the way, in this case both the Chroma server and client need to be updated to v0.4+ right?

Yeah


Could you please add a license?

If you could please add a license file, that would be great. Thank you.

Good point, opened a PR on that.

(It's MIT licensed.)


fides deploy up doesn't work on Apple silicon

Description
I can't launch fides on my local machine on Apple silicon with fides deploy up. However, the command doesn't work.
fides deploy up

...
 ⠧ fides-pc The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested    0.0s
 ⠿ Container sample-app                                                                                Started 1.3s
 ⠿ Container fides                                                                                Started 16.6s
 ⠧ sample-app The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested  0.0s
 ⠦ fides The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested       0.0s

As we can spedify the platform through the DOCKER_DEFAULT_PLATFORM envnrionment variable, I set it for the fides command. However, it didn't work.
DOCKER_DEFAULT_PLATFORM="linux/amd64" fides deploy up

...
Error response from daemon: image with reference postgres:12 was found but does not match the specified platform: wanted linux/amd64, actual: linux/arm64/v8

Environment

Mac OS: 12.5.1
Chip: Apple M1 Max
Docker Desctop:  4.17.0
Python: 3.10.11

Assumptions
The platform of docker images pulled by fides deploy up doesn't work on Apple sillicon.
Acceptance Criteria
N/A
Mockups
N/A
Implementation Notes/Details
N/A

Hi @yu-iskw,
Thanks for raising this issue! I've just run fides deploy up on my own Apple Silicon MacBook Pro and can't reproduce the problem you're experiencing. My environment is not fully representative of your own but it's pretty close:

Fides Version: 2.13.0
OS: macOS 13.3.1 (a)
Python Version: 3.10.11
Docker Version: 23.0.5 (Docker Desktop 4.19.0)
Hardware: MacBookPro17,1 (Apple M1 chip, 16 GB RAM)

Could you please try to re-run fides deploy up without DOCKER_DEFAULT_PLATFORM set to linux/amd64 and share the full output here so that we can investigate further?
I've posted a successful run at the bottom of this comment if it helps.
// Dave
~ ❯ docker image ls                                                                                5s
REPOSITORY   TAG       IMAGE ID   CREATED   SIZE
~ ❯ fides deploy up
2023-05-18 12:02:20.835 | INFO     | fides.api.ops.tasks:_create_celery:47 - Creating Celery app...
2023-05-18 12:02:20.836 | INFO     | fides.api.ops.tasks:_create_celery:65 - Autodiscovering tasks...
> Loaded config from: .fides/fides.toml
WARNING: Your 'fides' CLI is installed outside of a virtual environment at: /Users/dave/.pyenv/versions/3.10.11
Docker may not have permission to access this path, so if you encounter issues with Docker mounts, try reinstalling 'ethyca-fides' using a virtual environment (see https://docs.python.org/3/library/venv.html).
If you did install using a virtual environment, check your PATH. You may have a global version of 'ethyca-fides' installed that is taking precedence!
Docker version is compatible, starting deploy...
 Initializing fides...

Ethyca exists to make privacy a default feature of any tech stack, and we need your consent to use some of your data to achieve this mission:

    - Usage statistics, including a unique identifier, for product improvement
    - Your email address and organization name, for our sales team (we will never share this data)

You can learn more, and manage your privacy settings any time by visiting:
    https://fid.es/privacy

Opt-in to anonymous usage analytics? [y/N]: n
Directory './.fides' already exists.
Configuration file already exists: ./.fides/fides.toml
To learn more about configuring fides, see:
	https://ethyca.github.io/fides/config/
----------

███████╗██╗██████╗ ███████╗███████╗
██╔════╝██║██╔══██╗██╔════╝██╔════╝
█████╗  ██║██║  ██║█████╗  ███████╗
██╔══╝  ██║██║  ██║██╔══╝  ╚════██║
██║     ██║██████╔╝███████╗███████║
╚═╝     ╚═╝╚═════╝ ╚══════╝╚══════╝

Sample Fides project successfully deployed and running in the background!
Next steps:

- View the documentation http://localhost:3000/landing

- Visit the Fides Admin UI running at http://localhost:8080
    (user=root_user, password=Testpassword1!)

- Sample 'Cookie House' Application running at http://localhost:3000

- Sample Privacy Center running at http://localhost:3001
<EMAIL_ADDRESS>
- Example Postgres Database running at localhost:6432
    (user=postgres, password=postgres, db=postgres_example)

- Example Mongo Database running at localhost:37017
    (user=mongo_test, password=mongo_pass, db=mongo_test)

- Visit docs.ethyca.com for documentation.

Run `fides deploy down` to stop the application.
~ ❯                                                                                3m 22s

Hi @yu-iskw, I'm going to close this issue as "can't reproduce" as I haven't heard back from you, but if you need any help getting this working I'd recommend our Fides Community Slack workspace.


[Gally]: master <- dev

Automatically created by Git-Ally

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(prisma): enable prisma generator support for ESM

Information

Type
Breaking change

Feature
No

Todos

[x] Tests
[x] Coverage
[ ] Example
[ ] Documentation

Hello @vangie
Thanks a lot for this PR. You've missed to commit the yarn.lock file ;)
Also, the repo follow a angular commit convention and use semantic release. Can you remove emoji from your commit message please (isn't supported by semantic release).
The commit message must be:
feat(prisma): enable prisma generator support for ESM

Hello @vangie Thanks a lot for this PR. You've missed to commit the yarn.lock file ;)
Also, the repo follow a angular commit convention and use semantic release. Can you remove emoji from your commit message please (isn't supported by semantic release).
The commit message must be:
feat(prisma): enable prisma generator support for ESM

OK, I have amended the git msg and add the missing yarn.lock file

@vangie @Romakita any update for this PR, it would be amazing to add it for the next update, I'm working on a project that I want to turn into full esm support but I can't because of schemas not generated in esm.
Thanks for the work !

I think publish a code that support commonjs / esm for this plugin is complicated. I started the v8 branch (ESM only). Maybe it's more appropriate to add this PR to the v8 roadmap.
The branch is almost ready. There are small issue related to GQL and prisma module.
Another solution is to duplicate the code inside the tsed/prisma module (one for cjs and one esm) and use exports field to use the appropriate code convention.
See you

@vangie I pushed some commit to unlock your dev ;)
Now you can generate the code for ESM and CJS.

I removed extensionless. I prefer to manage extension each time it's necessary in our code.
I removed the condition to not generate decorator when there is a recursive import, I don't now why you trying to fix that because, you have to generate decorators in any case !

See you

@vangie @Tomdrouv1 The PR seems to be ready ;) can you review the changes ?

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

v7.71.0
GitHub release

Your semantic-release bot :package::rocket:

@Romakita
I have updated TSED to 7.74.1 and regenerate prisma，The following error occurred
❯ pnpm prisma:generate

><EMAIL_ADDRESS>prisma:generate /Users/duwan/Workspaces/babelcloud/babel-agent
> bin/prisma-generate.sh -f

Running prisma generate...
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Error:
✔ Generated Prisma Client (v5.16.1) to ./node_modules/.pnpm/@prisma+client@5.16.1_prisma@5.16.1/node_modules/@prisma/client in 68ms

ENOENT: no such file or directory, lstat '/Users/duwan/Workspaces/babelcloud/babel-agent/node_modules/.pnpm/@tsed+prisma@7.74.1_@prisma+client@5.16.1_prisma@5.16.1__@tsed+core@7.74.1_@tsed+di@7.74.1_<EMAIL_ADDRESS>


update readme

to make clear how multiple parameters are passed to wiremock. took me a while and a dive into the code to figure it out

Hi @christian-draeger, many thanks for your interest in improving the documentation! Would you mind adding it to both examples of pom.xml in readme?
To be honest I never needed to specify both http and https while working with WireMock. Is this something you actually had to do? If not, would you mind replacing the second param with something more usual, e.g. --verbose?

hey,
yes in my case i needed --port=8089 --https-port=8090 --global-response-templating but --verbose would be ok for the readme as well. my intention is basically showing how to set multiple parameters.
i will update the readme

added --verbose to both examples of pom.xml in readme


Try codecov.io for collecting code coverage

Coverage remained the same at 100.0% when pulling 80b7b7a6892fbd1c2e0479c5b71bc14431360b30 on codecov into 5e7064e3f8895bd4e8c021a722de3a0ad560f523 on master.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5e7064e). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             master     #9   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      2
  Lines             ?     31
  Branches          ?      0
=======================================
  Hits              ?     31
  Misses            ?      0
  Partials          ?      0

Continue to review full report at Codecov.

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


Infinite Reflexes

Describe the bug
The "Reflex" power on the enderian seems to not trigger it's cooldown in server situations.
To Reproduce
Steps to reproduce the behavior:

Enter a server.
Get shot at by anything that can wield a bow.
Ignore the arrow entirely.

Expected behavior
The "Reflex" Power is supposed to go on a cooldown, not permanently defend you.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions
Windows 11
Java 8 Update 271
Minecraft 1.19
Fabric 0.14.12
Origins 1.19-1.6.2
Pehkui 3.4.1+1.14.4-1.19.2
Fabric API 0.58.0+1.19
OriginsTweaks 1.12.1

Thank you for reporting this bug!
Unfortunately, due to private reasons I can't work on this project for the time being, but I'm trying to do so as soon as possible!
I'm sorry for any issues with game balancing that may occur...


Periodically save measured data

Save the measured data periodically. This would enable the data to be saved if anything goes wrong and it could also clear some memory for longer measurements.

Done.


Add : index date search params

Fixes #285

@deepankarb made the request changes can you review it again?


Try bun:test

Followup to:

https://github.com/refined-github/github-url-detection/pull/129
https://github.com/refined-github/github-url-detection/pull/135

AVA:
❯ time npx ava

  12059 tests passed

________________________________________________________
Executed in    6.91 secs    fish           external
   usr time    7.27 secs   93.00 micros    7.27 secs
   sys time    0.91 secs  495.00 micros    0.91 secs

Bun:
 18681 pass
 0 fail
Ran 18681 tests across 1 files. [518.00ms]

Welp 😅

Additionally, AVA does not run at all on Node 20 and I'm done debugging Node’s stupid errors
(node:73995) ExperimentalWarning: Custom ESM Loaders is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
  Uncaught exception in test.ts

  TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for ./test.ts

  ✘ test.ts exited with a non-zero exit code: 1
  ─

  1 uncaught exception

I also tried to replace the build, but it's not enough at the moment. This is how far I got:
bun build index.ts --outfile distribution/index.bun.js

Issues:

I wasn't able to shake the collector
We still need Vite for the demo, which can never be replaced by Bun (because the entry point is index.html)


How could I inclue a pic?

Hello,
This is not exactly an issue but it could be new functionality. I would like to include a picture in a day, for example, 2n of May.
How could I know the coordinates of that day?
Thanks,
Ibon

Not sure if this is possible. Days are made with geom_tile and I don't know if it is possible to add images to them easily :(


chore(wmg): remove wmgv1

Reason for Change

#6092
removed unused/dead code, merged mixed code into wmgv2, removed wmgv1 tree

@seve the majority of changes are just moving files around - so that will keep the existing git history in tact and contributions will stay attributed to their respective contributors. the code that was removed was unused code - if you look at the total lines added/removed here it's not that much - the lines that were added were mostly due to mixed resources (i.e styles being pulled from older files that need to be removed) - I actually tried to avoid copying as much as possible and move and rename instead to keep the history intact.
if there's a cleaner way of doing it I'm happy to do it.

@seve the majority of changes are just moving files around - so that will keep the existing git history in tact and contributions will stay attributed to their respective contributors. the code that was removed was unused code - if you look at the total lines added/removed here it's not that much - the lines that were added were mostly due to mixed resources (i.e styles being pulled from older files that need to be removed) - I actually tried to avoid copying as much as possible and move and rename instead to keep the history intact.
if there's a cleaner way of doing it I'm happy to do it.

Ooh yeah really good point!
It seems like we can preserve git history by using git mv command!
------ CGPT says -------
When you move a file in a Git repository, you can preserve the file's history by using the git mv command. Git is designed to handle file renames and moves efficiently while maintaining the file's history.
Here's how you can move a file while preserving its history:

Use the git mv command to rename or move the file. For example:
git mv oldfile.txt newfile.txt

If you're moving the file to a different directory, you can specify the new directory in the command:
git mv oldfile.txt path/to/newfile.txt

Commit the changes:
git commit -m "Moved oldfile to newfile"

This will ensure that Git tracks the move as a rename/move operation, and the history of the file will be preserved.
If you've already moved the file without using git mv, Git will still try to detect renames and moves based on the content similarity between the files. However, it might not always correctly detect the move, especially if the changes between the files are substantial. In such cases, you can use the --find-renames option with git log to see the history of the moved file:
git log --follow path/to/newfile.txt

The --follow option makes Git track the history of the file even if it was moved or renamed.
In summary, using git mv is the best practice for preserving file history when moving or renaming files in Git. If you've already moved the file, Git's similarity-based rename detection can help, but using git mv is more reliable.

Thanks for this @tihuan! I find git is pretty good at tracking moves and changes and will use git mv where possible 🙏🏽


Find maximum number in an array

A program which finds maximum number in an array

hi @Zohaib-Sathio  can you please assign it to me under the label of Hacktoberfest accepted and Hacktoberfest 2022

Thank you!

Hi @Zohaib-Sathio !
I have created the PR by adding the desired program.
Please look into it. I will be waiting for any suggested changes from your side.
Thank you!

Thank you @ENVIRYO2112VIT for contributing, I have reviewed and merged your PR to the repo and labeled it also.


Failed installing

Maybe you can help..?

I cannot reproduce this problem in my environment. if coc.nvim is out of date, please update coc.nvim itself and try again.
If the problem persists, please report the issue to coc.nvim, as it may be a bug in coc.nvim.


Add instructions on how to integrate into web application

I have always really wanted to make a git-backed wiki engine with c# powered pages, with a nice intellisense ready editor. It strikes me that this is the project to help with that.
Are there instructions on how I could integrate this project into a web app somewhere? I've had a look but haven't found anything which expressly guides me on how to do so.

Which features are you thinking of? Local (dotnet-try) versus web-based (e.g. https://dotnet.microsoft.com/learn/dotnet/in-browser-tutorial/1) have a number of differences in capabilities.

Are you talking about server-side execution vs webassembly? If so server side.
I think server-side execution, the idea would be for it to be edited by trusted users. Are the codeexecutions run inside a container, or under some other kind of sandbox? I

Prior to our move to web assembly, server-side execution took place in transient containers because all users were anonymous. The infrastructure to manage these containers is not part of this repo. Web assembly offers improved scale, cost, and privacy, but limits you to netstandard2.0.

And also limits you to web requests issued from the browser sandbox, right? Server side would allow for more powerful (and of course more dangerous) scripts.

Right. The security boundary is the user's browser in the case of our web assembly implementation. In the server-based implementation, the security boundary is the machine with whatever limitations are placed on the account it runs under.

It'd be great to have the option of runner. I'm more interested in the
server side model, however.
On Thu, 12 Dec 2019, 21:11 Jon Sequeira<EMAIL_ADDRESS>wrote:

Right. The security boundary is the user's browser in the case of our web
assembly implementation. In the server-based implementation, the security
boundary is the machine with whatever limitations are placed on the account
it runs under.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/try/issues/675?email_source=notifications&email_token=AACDJ6QTG5CJSXSGWEQ6TP3QYKSHNA5CNFSM4JTANXN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGYBPBA#issuecomment-565188484,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACDJ6USFGZW5KOQZEULSWLQYKSHNANCNFSM4JTANXNQ
.


Fix crash when clicking on a link with the XCode editor is in File co…

Recreating the PR with just the fix for the crash.

thanks


EXCEPTION CAUGHT BY WIDGETS LIBRARY

I/flutter ( 9744): ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
I/flutter ( 9744): The following assertion was thrown building _ModalScopeStatus(active):
I/flutter ( 9744): type '() => void' is not a subtype of type '(dynamic) => dynamic' of 'f'

Without more information there's not much we can do with this bug report, I'm afraid.
Please don't hesitate to file a new bug if you can provide us with detailed information, such as the code that caused the error and a full log.

@lichentao that looks like your Tab widget is calling length on what it expects to be a list or string but is null.


Question?

Why not add a config where players can change simple values like the biome scale and hex size?

It already exists

Let me clarify as I did not explain myself very well. I meant specifically being able to edit those values through the mods like "mod menu" which allows you to edit configs of mods if there is an available config.

I also feel this mod would benefit from the accessibility of in-game config menu mods


baetyl-1698 add object ext func

Codecov Report

Merging #444 (22a55ac) into master (dcb569a) will decrease coverage by 0.62%.
The diff coverage is 1.15%.

@@            Coverage Diff             @@
##           master     #444      +/-   ##
==========================================
- Coverage   64.81%   64.19%   -0.63%
==========================================
  Files          91       91
  Lines        6713     6775      +62
==========================================
- Hits         4351     4349       -2
- Misses       1730     1793      +63
- Partials      632      633       +1

Impacted Files
Coverage Δ

service/object.go
50.58% <0.00%> (-30.55%)
:arrow_down:

plugin/awss3/awss3.go
7.87% <1.41%> (-1.06%)
:arrow_down:

common/string.go
80.00% <0.00%> (-20.00%)
:arrow_down:

Continue to review full report at Codecov.

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


[Bug] Remote logging blocks startup

🐛 Bug
If the configured remote logging endpoint is not accessible it prevents the node from starting up.
To reproduce

Break logging service
Restart node

Stack trace/error message
 [Logging] Failed to connect: connection timed out
 Failed to send structured log: sending on a full channel

pfn.log.gz
Expected Behavior
Node should continue to work if logging is unavailable.
System information
Please complete the following information:

release-1.3_c3692998

Note: This doesn't prevent the node from starting up.  The node is running, but this locks up the local logs so it looks like nothing is happening.
The fix here will continue to log at a local logger, at possible decreased retention of sent logs


You can stack duplicate construction ghosts within themselves

Expected:

You try to place multiple identical ghosts in the same place
Game tells you nah

Actual:

Stack of 10 billion unfinished walls

Closed by #1642


Where is the code???

Did you not get the joke

The code is deleted for security reasons. Actually there is so many insider's info in issue descriptions, I am afraid it is a big hole in security :(

Look harder

Of course I got the joke..

What joke? Security is seriously serious business.

Seriously?

Seriously. I use no code all the time for my secure applications and it works great.


[Multisig] User with the private key can view the transaction history

Users with the private key can view the transaction history

Option for user to choose if they want more than one private key in order to view the related data

@kanniec826 can you explain further on this story?


Provide ConfigFile type for consumers

I would like to type my config files but the default ConfigFile type expects properties that are not needed.
import {ConfigFile} from '@beemo/core';

const config: ConfigFile = {
  module: '@local',
  drivers: {
    prettier: true,
    typescript: {
      foo: 'hello',
    },
  },
};

export default config;

Added a BeemoConfig type.

Why is BeemoConfig not just Partial<ConfigFile>?

@domoritz Because it needs to be deeply partial, but a DeepPartial type was causing some issues with the drivers/scripts fields. I agree it's not ideal, but also not critical at the moment.


Hard to configure GW

When wanting to re-configure GW via BLE and app.srcful.io ->. It takes a long time before I can do anything, and I get no response at all when pressing the buttons. There's also no debug info for what is happening.

ye this is not the correct project for this issue


Read arguments from SublimeLinter

Add an option in cmd to read arguments from SublimeLinter. That way it is possible to set VHDL standard, for example.

Feel free to post an issue here: https://github.com/ringof/SublimeLinter-contrib-ghdl/issues


SWARM-1260 - Re-arrange classes for this DeploymentProcessor to fire.

Motivation
For some hidden, and silently-ignored reason, the DefaultApplicationDeploymentProcessor
didn't actually fire in actual usage.
Modifications
Moved other related classes from :main module's internal.* package to the
runtime.* package.  Additionally, while at it, remove left-over cruft and
rework the byte-code emitter to straight up emit, instead of copying and
adjusting a sometimes problematic Application implementation.
Result
Examples should now pass again.

[X] Have you followed the guidelines in our Contributing document?
[X] Have you created a JIRA and used it in the commit message?
[X] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[X] Have you built the project locally prior to submission with mvn clean install?

is it SWARM-1260?


[API] Fix docs sorting and add limit option

Ensure categories and docs are returned sorted by rank.
Eager load translations to save on DB queries
Add docs_limit option to limit the number of docs returned in the nested entities

Nice work although it now has merge conflcts