Upgrade to version 8 causes hanging of processes which dotnet monitor is supposed to be monitoring

Description
We recently upgraded our image from mcr.microsoft.com/dotnet/monitor:7 (which I think was specifically on mcr.microsoft.com/dotnet/monitor@sha256:0cda57851419ac60878166c29dd18f09915ca2047de60444847f91338db8a326) to mcr.microsoft.com/dotnet/monitor:8 (specifically mcr.microsoft.com/dotnet/monitor@sha256:9324ee5e07e7ce8428772aa6269438b3a6688649d1746f41190acb0a045ff857) in our production environment and some of the dotnet processes being run in the container which is supposed to be being monitored started emitting logs of the form:
The runtime has been configured to pause during startup and is awaiting a Diagnostics IPC ResumeStartup command from a Diagnostic Port.
DOTNET_DiagnosticPorts="/dotnet-diagnostics/port.sock"
DOTNET_DefaultDiagnosticPortSuspend=0

When the process emitted that log it then just hung in the SNl state, and we terminated it with an automatic cutoff for duration of time (see notes in configuration but these C# processes are supposed to be very short lived, which I suspect is where the issue stems from.)
At the same time there also seems to be a log message from the dotnet-monitor container saying:
{
  "Timestamp": "2024-05-02T08:39:56.8474094Z",
  "EventId": 99,
  "LogLevel": "Warning",
  "Category": "Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource",
  "Message": "Unable to fully initialize endpoint for process 792382. Some monitoring features may be unavailable.",
  "Exception": "System.AggregateException: One or more errors occurred. (Operations that change non-concurrent collections must have exclusive access. A concurrent update was performed on this collection and corrupted its state. The collection's state is no longer correct.)\n ---> System.InvalidOperationException: Operations that change non-concurrent collections must have exclusive access. A concurrent update was performed on this collection and corrupted its state. The collection's state is no longer correct.\n   at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)\n   at Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource.ResumeAndQueueEndpointInfo(ReversedDiagnosticsServer server, IpcEndpointInfo info, CancellationToken token)\n   --- End of inner exception stack trace ---\n   at Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource.ResumeAndQueueEndpointInfo(ReversedDiagnosticsServer server, IpcEndpointInfo info, CancellationToken token)\n   at Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource.<>c__DisplayClass19_1.<<ListenAsync>b__0>d.MoveNext()",
  "State": {
    "Message": "Unable to fully initialize endpoint for process 792382. Some monitoring features may be unavailable.",
    "processId": 792382,
    "{OriginalFormat}": "Unable to fully initialize endpoint for process {processId}. Some monitoring features may be unavailable."
  },
  "Scopes": []
}

I am afraid I have not yet managed a minimal reproduction as we saw this in production, not our staging environments where load is much lower. I wanted to raise this first in case you were able to make progress without it!
We have never seen this issue before in the version 7, so it came as quite the surprise when all of these processes started hanging 😄

Configuration
We run dotnet monitor in a kubernetes cluster (v1.25) alongside a single other container. That container has a main entry point which is a long lived process (length of the container), but that process also spins up lots of sub dotnet processes (being used as a customer merge driver in git).
We only saw this problem happen as part of those sub dotnet processes, which have been known to take seconds (or less) to execute, and it seems to be fairly random (i.e. a lot of those sub processes were fine but a minority hung on this bug)
We already have a lot of log messages coming out of dotnet monitor to the tune of:
{"Timestamp":"2024-05-02T08:39:54.2599063Z","EventId":52,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource","Message":"Unexpected timeout from process 792203. Process will no longer be monitored.","State":{"Message":"Unexpected timeout from process 792203. Process will no longer be monitored.","processId":"792203","{OriginalFormat}":"Unexpected timeout from process {processId}. Process will no longer be monitored."},"Scopes":[]}

{"Timestamp":"2024-05-02T08:39:54.2600976Z","EventId":44,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"Stopping collection rules.","State":{"Message":"Stopping collection rules.","{OriginalFormat}":"Stopping collection rules."},"Scopes":[{"Message":"TargetProcessId:792203 TargetRuntimeInstanceCookie:4d9379280ea940dd83d09bc58036e85f","TargetProcessId":"792203","TargetRuntimeInstanceCookie":"4d9379280ea940dd83d09bc58036e85f"}]}

{"Timestamp":"2024-05-02T08:39:54.2601133Z","EventId":45,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"All collection rules have stopped.","State":{"Message":"All collection rules have stopped.","{OriginalFormat}":"All collection rules have stopped."},"Scopes":[{"Message":"TargetProcessId:792203 TargetRuntimeInstanceCookie:4d9379280ea940dd83d09bc58036e85f","TargetProcessId":"792203","TargetRuntimeInstanceCookie":"4d9379280ea940dd83d09bc58036e85f"}]}

Suggesting we might already be pushing dotnet monitor to it's limit

Regression?
This previously worked with dotnet monitor version 7 (most recent)

Other information
The exception above seems to point to a concurrency issue, but I couldn't immediately figure it out hence why I am raising an issue not a PR
We would actually be perfectly happy for dotnet monitor to not monitor these short lived processes, so if we could do that it would be excellent 😅
I am by no means the expert on the code but at the very least the exception seems to be pointing to https://github.com/dotnet/dotnet-monitor/blob/ab0774688b140dedcbca8be761b6ce677301251f/src/Tools/dotnet-monitor/EndpointInfo/ServerEndpointInfoSource.cs#L223
My guess is that the _activeEndpointServiceScopes dictionary is being accessed concurrently (and so should be a concurrent dictionary). That dictionary doesn't seem to exist in the v7 version (introduced in https://github.com/dotnet/dotnet-monitor/pull/4964)

Thanks for reporting this! We'll try to take a look into this and investigate with the information that you've provided. However, I don't have a timeline for when we can give you definitive solution.

We would actually be perfectly happy for dotnet monitor to not monitor these short lived processes, so if we could do that it would be excellent 😅

You can accomplish this by clearing the DOTNET_DiagnosticPorts environment variable in your top-level .NET process (presumably the container entrypoint process) before launching the child processes e.g. Environment.SetEnvironmentVariable("DOTNET_DiagnosticPorts", null);. This will prevent the child processes from being observed by .NET Monitor in your current configuration but still allow the entrypoint process to be observed. This environment variable is only read by the runtime at startup, so clearing it anywhere in your managed code will not affect the observability of the process in which you clear it.

Thanks for speedy response @jander-msft! I will give that a go and see how we get on 😄 Let me know if I can do anything to help

In the disposal method it's using the _activeEndpointsSemaphore around a mutation of _activeEndpointServiceScopes, so I think it needs the same done around the call to .Add in this case?
            await _activeEndpointsSemaphore.WaitAsync(CancellationToken.None);
            try
            {
                serviceScopes = new List<AsyncServiceScope>(_activeEndpointServiceScopes.Values);
                _activeEndpointServiceScopes.Clear();
            }
            finally
            {
                _activeEndpointsSemaphore.Release();
            }

Yeah, I determined that to be the issue as well. I'll put up a PR shortly.

As a heads up, this should be fixed in the upcoming .NET Monitor 8.0 servicing release and .NET Monitor 9.0 Preview 4 release.

The fix is now available in the 8.0.2 release. Please check the release notes for any additional changes that may impact your usage of .NET Monitor: https://github.com/dotnet/dotnet-monitor/releases/tag/v8.0.2

Thanks!


Consider adding "Negative Predictive Value"

Following on from Issue #681.
There appears to be a "Negative Predictive Value" (=true negatives/(true negatives+false negatives)). I had a quick look, and I didn't notice scores already having a binary categorical metric that matches this.
Should this be added to scores? And if negative predictive value is added to scores, are there any other names by which the metric is known?

I have't seen this used in meteorology. Happy for it to be added. I'm not aware of any other names.


fix(db) postgres connector keepalive errors on load

Summary
Postgres strategy (new model) could result error like the below when running multiple subsequent Admin API calls rapidly (or parallel):
[error] 27206#0: *3351 lua coroutine: runtime error: /usr/local/share/lua/5.1/pgmoon/init.lua:294: bad request

I still struggle to see the difference before and after the patch, a lot of it seems to be re-factoring. What is the part that fixes it exactly, and where did this originate from? The PR description is very vague on details.

The biggest change is that when you don't have self.connection the self:query doesn't set one either, it just creates connection, uses it and sets keepalive, but it doesn't touch this self.connection in any way.

But I agree, if user ever calls :connect I think we might have a problem, with both cassandra and pg. That's why I would prefer that something in our system makes connection available per request and closes/keepalives it after. Something other that this strategy instance field, which may be shared between single worker on several requests.

Gotcha. The :connect() method was intended for users (likely, said users are us) who know they will need to make several queries at once. It is fine in the CLI or init contexts, but not at runtime indeed, since the DAO is shared between all requests, one of those queries could yield and another request could use the DAO, which by then has this connection object as an attribute...
Let's merge this for now, and consider what to do with :connect() later!


[KOGITO-1439] Cucumber tests: Set CLI or CR tests via test option

https://issues.redhat.com/browse/KOGITO-1439
removed CR / CLI differenciation.
By default, it will try to use the CLI to deploy. When executed, CLI command is creating a CR to deploy on Openshift.
Use make run-tests cr_deployment_only=true to tell the tests that we want only to test via CR and not CLI (because, for example, CLI is not available)
Also solve https://issues.redhat.com/browse/KOGITO-1435 (code removal)
Many thanks for submiting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[x] You've tested the new feature/bug fix in an actual OpenShift cluster

@MarianMacik @sutaakar can you have a final review ?


webssh depends on a vulnerable version of async

see https://github.com/billchurch/read-config-ng/issues/17
once fixed, rebuild the docker image

fixed upstream, the image was updated


Wrong repository helper function name

The helper os the mongoose repository has a function called: normalizeFiledNames and it must be: normalizeFieldNames

Fixed in #118


PHOENIX-6978 Merge to master after rebase

@stoty @virajjasani The CI builds for this PR are failing with some yetus related errors. Any idea how to resolve this?

When I faced this issue, I have opened another PR with the same changes, and that one worked.
No idea why this happens.


feat: attempt for a github action

~This action test with GOPATH on Linux amd64~ This does not work
Then it test with gomodules on linux / darwin / amd64 / arm

Coverage remained the same at 64.588% when pulling 9adc3de3c5305c86f40414e36da3f5119275519b on devops into fe1839e525c213cb5064395e73f3f69018e78162 on master.

I propose this github action.
First it runs test for go 1.13. and go 1.14 and coverage for go 1.14 in parallel.
If tests are success, it runs a build on amd64 Linux and macos in parralel.
All the steps are completing before travis :D
WDYT?

Why use github actions instead of travis ?
Also you only test build on linux/amd64 because github actions doesn't support other architecture.

We could add in the future a arm runner with hosted runner. Looks good to me https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners


ENH: convert event-based factors to continuous-time factors

Alphalens expects alpha factors to be more or less continuous in time: in other words, if I produced a factor value for AAPL today, then usually, there should be a factor value for AAPL tomorrow, and it should be close to today's value.
However, some alpha factors are event-based and are much "spikier": in other words, perhaps I produce a factor value for AAPL only several times a year (perhaps driven by earnings call or some other similar event).
Would it be appropriate to have an event_based_signal_to_continuous_signal included in Alphalens? I imagine that event based signals could be forward-filled: the last valid value would be propagated forward in time until the next valid value, possibly with some user-specified exponential decay to encode the fact that event based signals reflect information that loses value in time. Is this something the maintainers would be interested in having?

Actually Alphalens provides already an event based analysis. Have a look at the examples

Alphalens expects alpha factors to be more or less continuous in time: in other words, if I produced a factor value for AAPL today, then usually, there should be a factor value for AAPL tomorrow, and it should be close to today's value.

This limitation was fixed a long time ago


Add cask for official IRCCloud Desktop App

Changes to a cask
Adding a new cask

[x] Checked there aren’t open pull requests for the same cask.
[x] Checked there aren’t closed issues where that cask was already refused.  (https://github.com/caskroom/homebrew-cask/pull/22353 was not merged, this PR hopes to pick up this PR and fix what was missing)
[x] When naming the cask, followed the token reference.
[x] Commit message includes cask’s name.
[x] brew cask audit --download irccloud is error-free.
[x] brew cask style --fix irccloud left no offenses.
[x] brew cask install irccloud worked successfully.
[x] brew cask uninstall irccloud worked successfully.

Thank you for the contribution. It needed some fixes, so they were made in 53bcf42bfcdc23028ffbe69238007cbb0d46216b. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.

All good, thanks!


Can't read config file in monorepo

File structure:
/think
  package.json
  /node_modules
    /eslint
    /eslint-config-universe
  /mobile
    package.json
    .eslintrc
    /node_modules

Because of Yarn workspaces, the eslint and eslint-config-universe both get hoisted up to the root node_modules, but eslint seems to be looking for it only in the package's node_modules:
[Info  - 1:11:41 PM] ESLint library loaded from: /Users/gsquare567/Sites/think/node_modules/eslint/lib/api.js
[Info  - 1:32:56 PM] Cannot read config file: /Users/gsquare567/Sites/think/mobile/node_modules/eslint-config-universe/native.js Error: ENOENT: no such file or directory, open '/Users/gsquare567/Sites/think/mobile/node_modules/eslint-config-universe/native.js' Referenced from: /Users/gsquare567/Sites/think/mobile/.eslintrc

Fixed by changing auto to location:
    "eslint.workingDirectories": [
        {
            "mode": "location"
        }
    ],

This is for eslint 6.8 and vscode-eslint 2.1.5, btw.


Undo last deployment of clickhouse cluster

Sometimes if we give resource requirement which can't be completed by K8S then pods are in pending state.
Only solution is to vertically scale the nodes and complete the deployment .There's no option to undo the last deployment

try to 0.14.0 clickhouse-operator release,
for example
`
git clone git@github.com:Altinity/clickhouse-operator.git
cd clickhouse-operator
git checkout 0.14.0
git pull origin 0.14.0
OPERATOR_NAMESPACE=<your_installed_operator_namespace> bash -x ./deploy/operator/clickhouse-operator-install.sh
this release support preemptive task queue
so you can make changes in your kind: ClickhouseIntallation manifest with scaledown
and run kubectl apply -f <your_manifest>
and no wait pending state

@Slach  Thank you will try this

Yes, it takes almost 5-7 mins and then applies the new config

@Slach just for information,
Is there any option to check the progress of the cluster deployments? It's difficult to check from logs.

@apalmercari just use
kubectl describe chi -n <your_chi_namespace> <your_chi_name>
and see events


⚠ gorzdrav.org has degraded performance

In 95161a4, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 6198 ms

Resolved: gorzdrav.org performance has improved in 3eeced9.


Object curly spacing

This PR adds the object-curly-spacing rules according to specifications from eslint. The rule and test files have have been added and the README file has been updated to show that it is no longer in the TODO list.
Several other changes have been made in order to improve the developing experience.

No longer running all the tests to check if the rule in development works:
By default gulp test will run all the tests that it can find. We can now target a particular
test by using the single argument as explained in the README: gulp test --single rule-name.

Transpile files even if linting fails:
When running the tests we always run the build task which depends on the linting task.
Sometimes we may encounter linting errors that we are not willing to clean up yet and this
should not stop us from writing the rule. When this is the case we can add the flag --no-lint
so that the linting task is not triggered. For instance gulp test --single rule-name --no-lint.

I also added the rule to the project to test if we have inconsistencies in the project files. So far we are not adding spaces on imports but we do on object literals. In order to leave things working I have turned off the rule but we should consider using it in order to avoid future inconsistencies. I will open an issue for this.
Finally, the current state of the project is bad. Please test your master branch and let me know if you the valid-jsdoc test fails at should fail when using invalid JSDoc comments (matchDescription: "regex", requireReturn: false).

closes #58

We still need to merge PR #100 in order for the continuous integration to pass. In the mean time, once this is merged and my no-multi-spaces branch is approved then we should consider adding these tests as well:
https://github.com/eslint/eslint/blob/master/tests/lib/rules/object-curly-spacing.js
Hopefully none will fail.

Please, undo .gitignore, gulpfile.js and package.json.
There is a reason for not transpiling files when tests fail, and this is something I won't change. And there is also a reason for running all tests any time you want to test something.
Both "improvements" are design choices, and not errors.

Never said they were errors, they are just a way to speed up the development process for the rule we are focusing on. As the number of rules and tests grow more the time it takes to run over all the test will continue to grow. Those changes do not interfere with the current setup in any way. As the final step the developer needs to be responsible to run the final gulp test to make sure all the tests are running before pushing the changes so that the continous-integration won't fail.
Please note that the --no-lint flag is so that the traspilation won't fail due to lint errors (as opposed to tests failing) which can happen quite often (max-line, no-var-used, etc). During development I'm aware that some of these errors are introduced often but this shouldn't stop the tests from running, especially when I'm not ready to commit and create a PR.
The only reason I can think of we need to run all the tests when we want to test a single rule is if some of the test share some of the rules and to see how they interact with each other. Which is why when I was done writing my rule I ran the gulp test to make sure everything was in order.
It was because of the gulp test that I found out the one of your tests was broken. If I didn't write this flag I would have just given up and not written this PR and the other stuff I have written.
Don't get me wrong, I love the work you have done, it was because of it that it inspired me to stop waiting for the rules to be done and instead start writing them so that others may use them.
I ask you to please reconsider your views on those two optional flags I wrote. If nothing has changed your mind please let me know if I should I also revert the change to the tslint.config file. Thank you for your time.

Update: I have set the branch up to date with master and while testing I noticed that the tslint.config cannot have the rules of the project applied to it since this breaks the gulp test flow. Notice that now all the tests are passing and how these flags did not interfere.
Also, on the .gitignore, do you really want to commit js files on the src directory?

CI is failing because of the new "rulesDirectory" property in tslint.json.
About what you said, OK, I reconsider, and we can keep your changes.
About your last question: we should never have js files in the src directory, so I don't understand why we should have this restriction.

Yeah, I deleted my dist folder and i got the error that CI encountered, that's why I removed the changes from it. Any way we can apply the rules we make here to the project without interrupting the linter? I think that'll be for another issue.
Thank for you reconsidering. I have the next PR ready to go.
I only brought the last point since you had mentioned to revert the .gitignore. Either way, I'm glad you agreed that we should not have them. That is all. Thanks.

Thanks for contributing, have a good week :)


Solutions to the latest issues

This should solve:

https://github.com/TheAncientGoat/autoform-slingshot/issues/10
https://github.com/TheAncientGoat/autoform-slingshot/issues/11
https://github.com/TheAncientGoat/autoform-slingshot/issues/12

@TheAncientGoat we should bump the version after this gets in.

Did @kyooriouskoala confirm the fixes?

He did not, I just updated my version of the package to make it simple to
test. I guess we can wait for @kyooriouskoala
https://github.com/kyooriouskoala to confirm it.
2015-08-04 3:07 GMT+02:00 Ryan Swart<EMAIL_ADDRESS>
Did @kyooriouskoala https://github.com/kyooriouskoala confirm the fixes?
—
Reply to this email directly or view it on GitHub
https://github.com/TheAncientGoat/autoform-slingshot/pull/13#issuecomment-127445324
.

--
Cheers,
// Tim Brandin @timbrandin https://twitter.com/#!/timbrandin
http://timbrandin.com
http://studiointeract.com

Ok @kyooriouskoala, now I've found the solution to both the isolation issue and the deletions issue.


Add projects app

We a flipify user attempts to migrate from one service to another, we need an app incharge of migration details.

can you shed more light on this?


fix: check prom needs the opts

The check won't work when the server requires basic auth (which is given via the CURL_OPTS)

Hi @yoan-adfinis,
Thank you for this, we noted the same problem this morning, and I will be writing some tests to ensure that this issue won't be reintroduced once this fix is merged.

Change included and merged with #4


buildtools: update protoc and mold

These updates aren't very important but I would like to try out the new process as of #6195

waiting for all checks to pass
but Looks good to me

The CI run for the tagging is here: https://github.com/neondatabase/neon/actions/runs/7291140117
I used<PHONE_NUMBER> for the source tag (found it via checks tab -> "Build and Test" -> "neon-image" -> "Kaniko build Neon" ->  number next to BUILD_TAG ; also part of the URL of the "Build and Test" job). but that apparently gave an error:
Run NEXT_DIGEST=$(crane digest ${IMAGE}:${FROM_TAG} || true)
2023/12/21 17:10:06 HEAD request failed, falling back on GET: HEAD https://369495373322.dkr.ecr.eu-central-1.amazonaws.com/v2/build-tools/manifests/7289718682: unexpected status code 404 Not Found (HEAD responses have no body, use GET for details)
Error: GET https://369495373322.dkr.ecr.eu-central-1.amazonaws.com/v2/build-tools/manifests/7289718682: MANIFEST_UNKNOWN: Requested image not found

I used<PHONE_NUMBER> for the source tag (found it via checks tab -> "Build and Test" -> ["neon-image"]

It should be<PHONE_NUMBER> from https://github.com/neondatabase/neon/actions/runs/7289833292 (GITHUB_RUN_ID of the latest successful job in the PR)

that worked, it seems I forgot to press F5. This is a much smoother process now, thanks @abhigets !


ocis 1.0.0-beta7

Fix TUS upload errors

[x] missing headers in HEAD request https://github.com/cs3org/reva/pull/926

[x] change the default value of the Reva Transfer Token (default now 24hrs) https://github.com/owncloud/ocis-reva/pull/323

[x] make the default go client timeout configurable (default now 24hrs) https://github.com/cs3org/reva/pull/914/files

[x] release ocis-reva v0.9.0

[x] update ocis reva in ocis https://github.com/owncloud/ocis/pull/357

[x] release ocis

@HanaGemela We should do a upload/download testing
Clients:

Desktop Client
iOS Client
ocis Web Client

seems the release tag is already there, close ?

yes. Release is out.

Re- opening for QA

Split the qa ticket #365


Helpers for Unity Should have Unity updated to 5.0.1

Getting error if using the pre-release of the Unity DI Helpers because that Unity is only version 4 and still using Microsoft.Practices Namespace.

Updating to v5 is on my radar. Thanks for opening the issue. There are a few other fixes I’m working on before I publish the next preview.

@dansiegel, Thx a ton - for now i just mocked it locally to continue dev.
Looking forward to new previews.

This has been updated and will be in the next preview


Make image optional

Please make make the image optional. I tried passing an empty container but it still leaves a gap in the top.

To make the image optional or invisible, you must set it to null


Fix canvas zoom via mouse wheel on mac, it's too fast right now

Canvas zoom via alt+mouse wheel on the mac is really fast, I often end up in 16000% zoom from 10% if I'm not careful. This and the stutter make this shortcut really hard to use.

I just want to hop in here and say I experience the same thing and it's insanely annoying.
If there were some keyboard shortcuts (to increment/decrement zoom or jump to a fixed zoom) this would be a nice workaround, but it looks like those are not universally available, either.
After just keymashing, I was able to find that Command + +/- on the numberpad does increment/decrement the zoom, even though those hotkeys are not included in the menu (or the tooltips for the zoom magnifying glass icons):

Regardlees, zooming with the mouse is insanely touchy and very frustrating.

I love the project, thank you very much to the developers.
The only thing that really gets in the way is an unexpected zoom while copying elements. When I hold down CMD or CMD+C, any touch of the magic mouse on the mac causes the canvas to crazy zoom.
Is it possible to somehow disable the zoom for the CMDkey?
For example, pressing the ALT key already performs the same function. It would have been enough.

I don't know what it was like before this ticket was closed but zooming on Mac with a Magic Mouse is still impossibly fast. Without even dragging my finger it'll zoom all the way from min to max.

Please submit a new ticket if you feel if is still an issue.

For anyone else still hitting this issue landing here from Google, I found the workaround described here to make the zoom speed much more usable.


[FP]: Incorrect Liquibase Vulnerability detected for<EMAIL_ADDRESS>

Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:liquibase:liquibase:2.10.0:*:*:*:*:*:*:*
CVE
CVE-2022-0839
ODC Integration
No response
ODC Version
7.0.0
Description
The vulnerability being output here is for any liquibase version before 4.8.0.  However, the version of quarkus I am using (2.10.0.Final) is not using a liquibase version before 4.8.0.
From checking the quarkus bom here https://mvnrepository.com/artifact/io.quarkus/quarkus-bom/2.10.0.Final
It states it is using liquibase version 4.11.0 (https://mvnrepository.com/artifact/org.liquibase/liquibase-core/4.11.0).

Let me register a Quarkus 2.10.0.Final CPE qualifier in NVD and see if it can help

@sberyozkin won't help ... quarkus:quarkus CPEs are already present in the vulnerability datastreams (the source of CPEs that ODC consults to try and match libraries to CPEs), and version is irrelevant to how ODC links libraries to CPE (roughly spoken: by vendor and product, using text-matching weighted search algorithms on various strings found in a library).
Version only comes into play in judging whether the version depended upon is among the version-ranges documented as vulnerable in the datastream.
The version as extracted from the dependency gets appended to the base vendor/product identifier established from the ODC text-search results to form the cpe as listed in the report.
The FP report stems from the (known) inaccuracy of that matching algorithm, which makes ODC (incorrectly) link a quarkus library to support liquibase  (belonging to the quarkus CPE as it is part of the components of the core quarkus framework) to the CPE of the liquibase software itself (which the quarkus liquibase support library is not a part of).

@bhutchison Upgrading to 7.1.1 should resolve you FP

@bhutchison Upgrading to 7.1.1 should resolve you FP

Thank you, will test.

@aikebah Thanks very much for the explanation.
@bhutchison Thanks for opening this issue and confirming it has been resolved with 7.1.1

This was addressed with #4472 from @renegrob. However, the regex in <packageUrl<EMAIL_ADDRESS>(-> code) does not apply to quarkus-liquibase-deployment, note the -deployment.
@aikebah shall I create a PR to extend the regex in the existing FP or does this warrant a completely new entry?

@marcelstoer Extending the regex of the existing entry would be fine


Minor typo & Website Suggestion

In the homepage, the sample code is missing a comma:
var burst = new Burst({
    radius:   { 15: 50 }, // <--
    children: {
      fill: [ 'deeppink', 'cyan', 'orange' ],
    }
});

Also, the tutorials are excellent, but it would be nice if they could be broken down into smaller sub-sections, because currently each of them is a tad bit too long. Finally, while in-depth tutorials are absolutely helpful, an animejs style documentation could also be helpful for people who just want to glance over what code does what.
I'm definitely willing to help out with fixing those issues and writing docs. I just can't find it here. It might be a good idea to allow less-technical people to contribute to this awesome project?

Hi @donfour,
May be you should post your issue on this website repository: https://github.com/legomushroom/mojs-website/issues.
Best regards :wink:

Opps thanks!


Multiple connections at once

It'd be nice to allow multiple connections at once using tabs etc.

This feature is already planned for a future release


How can I configure the lua_shared_dict to the nginx-kong.conf

I want to use the lua_shared_dict in my plugin,but I can not add lua_shared_dict profile in the nginx-kong.conf~How can I do it?

https://github.com/Kong/kong/blob/master/kong/templates/nginx_kong.lua#L31 All these are the declared shared dictionaries kong has by default. You can add as many as you want in that file prior to starting up Kong.
Not sure if they have introduced a parameter in the conf yet to define custom shared dictionaries.

You can use Nginx directive injection feature to inject a shared dict into the Nginx conf file of Kong:
nginx_http_lua_shared_dict=my_dict_name 1m

Hello @hbagdi.
Is it possible to inject Nginx directives from a plugin ? Asking because of this.
I am developing a public plugin and I would like to not make the user edit their nginx directives.
I found an ugly workaround using environment variables : export KONG_NGINX_HTTP_LUA_SHARED_DICT="this_dict 20k", but that is still an extra step for the plugin users to do.
BTW, I love your work, guys !

I found an ugly workaround using environment variables : export KONG_NGINX_HTTP_LUA_SHARED_DICT="this_dict 20k", but that is still an extra step for the plugin users to do.

@Ilshidur As of today, this is the only way to add a shared dict. Agree that it requires an extra step but should be required only once while setting up configuration for Kong.
I'm going to close this as the original question is answered.
Please re-open if needed.

nginx_http_lua_shared_dict=my_dict_name 1m

Hi,
How'd one share more than one lua_shared_dict?

You can include a file with the include directive, which has a number of shared dicts.

You can set this env var KONG_NGINX_HTTP_LUA_SHARED_DICT: introspection 10m

Adding for reference; recently saw someone add multiple dicts like this;
nginx_http_lua_shared_dict=my_dict_name 1m; your_dict_name 1m;

@Tieske I am unable to configure kong with multiple shared dicts that way:
My docker-compose:
environment:
  KONG_NGINX_HTTP_LUA_SHARED_DICT: "discovery 1m; jwks 1m; introspection 1m"

The output I get is:
kong_1     | Error: could not prepare Kong prefix at /usr/local/kong: nginx configuration is invalid (exit code 1):
kong_1     | nginx: [emerg] unknown directive "jwks" in /usr/local/kong/nginx-kong.conf:36
kong_1     | nginx: configuration file /usr/local/kong/nginx.conf test failed

👍  @bforbis thx for the feedback, I updated my post above

@Tieske, to be extra clear, you need to add lua_shared_dict directive before each additional shared dict name. The way you have it right now, the generated directive would be:
lua_shared_dict my_dict_name 1m; your_dict_name 1m

This does not compile, since "your_dict_name" is not a known nginx directive.


god does not receive ProcessExits event when running as a server.

I have a simple test with the following config file "simple.god":
God.watch do |w|
  w.name = "simple"
  w.start = "ping google.com"
  w.keepalive
  w.interval = 1.seconds
end

If I run god in non-daemonized mode with god -c simple.god -D and then run ps aux | grep ping | awk '{print $2}' | xargs kill, I can see in the output that it detects the killed process and restarts it:
I [2016-05-25 19:41:42]  INFO: simple [trigger] process 3418 exited (ProcessExits)
I [2016-05-25 19:41:42]  INFO: simple move 'up' to 'start'
I [2016-05-25 19:41:42]  INFO: simple deregistered 'proc_exit' event for pid 3418
I [2016-05-25 19:41:42]  INFO: simple start: ping google.com
I [2016-05-25 19:41:42]  INFO: simple moved 'up' to 'start'
I [2016-05-25 19:41:42]  INFO: simple [trigger] process is running (ProcessRunning)

However, if I run god in daemonized mode and try the same command to kill all ping processes, god does not detect that the process has been killed:
I [2016-05-25 19:43:35]  INFO: simple move 'init' to 'start'
I [2016-05-25 19:43:35]  INFO: simple start: ping google.com
I [2016-05-25 19:43:35]  INFO: simple moved 'init' to 'start'
I [2016-05-25 19:43:35]  INFO: simple [trigger] process is running (ProcessRunning)
I [2016-05-25 19:43:35]  INFO: simple move 'start' to 'up'
I [2016-05-25 19:43:35]  INFO: simple registered 'proc_exit' event for pid 3473
I [2016-05-25 19:43:35]  INFO: simple moved 'start' to 'up'

<...Nothing more gets printed here...>

After killing all ping processes, god still thinks that "simple" is up.
I'm not sure what could be wrong since it works perfectly in non-daemonized mode.
Setup info:
god version: 0.13.7
OS: OS X 10.11.1

I discovered this work-around from someone at work: You have to put this block inside the main watch block:
  w.start_if do |start|
    start.condition(:process_running) do |c|
      c.running = false
    end
  end

So the final working config is:
God.watch do |w|
  w.name = "simple"
  w.start = "ping google.com"
  w.keepalive
  w.interval = 1.seconds

  w.start_if do |start|
    start.condition(:process_running) do |c|
      c.running = false
    end
  end
end

No idea why you need that when w.keepalive is already set, but it makes it work as expected.


Entities going to Thing not running state

Hello,
I have a deployment of Saas Thingworkx and  the github things go to "not running" state without any understanding of how or when this happens (we talked by email on my hp account).
Thing [Here goes GIT thing] is not running
This happens will all gitthings I have.
This happens executing Status service on the git thing.
I'm waiting for the logs, just opened case.

Thanks for reporting this @jlagares.
We’d need to have the entries around the time when you try to enable a Git thing from ApplicationLog (accessible via composer) and ErrorLog.log (which indeed you need to retrieve via a support ticket as it’s not exposed in composer).
I am quite curious to see why the Git things are not running, as I have not observed that before.

Thanks, ticket opened.
In the meantime I'm re creating all gitthings again, removed all repo content manually (as I could not via service) and checking again.
One question is, can 2 Git Things have the same repo folder ? As we have several and all point to the same folder but refer to different github branches, I'm thinking that this might confuse the thingworx git extension.

Two Git things can use the same File Repository, but mandatory they need to be found themselves in two different subfolders of that File Repository. The extension does not verify if there's already an existing local Git repository in the folder you specified, and yes, that can be a source of this issue (I think).

For transparency, in the error log we observed two interesting errors:

Unable to initialize thing [redacted], Cannot lock /ThingworxStorage/repository/GitRepository/[redacted]/.git/config. Ensure that no other process has an open file handle on the lock file /ThingworxStorage/repository/GitRepository/[redacted]/.git/config.lock, then you may delete the lock file and retry. This points into a file using that lock file - potentially two Git things created in the same folder can do this.
Unable to initialize thing [redacted], null. This error does not have much context and I requested an ErrorLog with stack trace activated.

And another question: did this behavior started happening sudden, after working fine in the past? Or is this the first attempt of using the GitBackup extension ? Besides the log files, can you remember anything that changed in your system before this error started appearing?

It happened without noticing working correctly before. This has also happened in some dockers that I have, so whenever I see it there I'll send you the error Log.
The environment is shared by many people so no clue everything that happened.
I'll be working with Ilaria in the following weeks so I can keep you updated.


SDK has to be implemented for newly added provisional clusters

SDK has to implemented for below mentioned clusters:

[ ] Bromodichloromethane Concentration Measurement Cluster
[ ] Bromoform Concentration Measurement Cluster
[ ] Bromate Concentration Measurement Cluster
[ ] Chloramines Concentration Measurement Cluster
[ ] Chlorine Concentration Measurement Cluster
[ ] Chlorodibromomethane Concentration Measurement Cluster
[ ] Chloroform Concentration Measurement Cluster
[ ] Copper Concentration Measurement Cluster
[ ] Dissolved Oxygen Concentration Measurement Cluster
[ ] Coli Concentration Measurement Cluster
[ ] Ethylene Concentration Measurement Cluster
[ ] Ethylene Oxide Concentration Measurement Cluster
[ ] Fluoride Concentration Measurement Cluster
[ ] Haloacetic Acids Concentration Measurement Cluster
[ ] Hydrogen Concentration Measurement Cluster
[ ] Hydrogen Sulfide Concentration Measurement Cluster
[ ] Manganese Concentration Measurement Cluster
[ ] Sodium Concentration Measurement Cluster
[ ] Nitric Oxide Concentration Measurement Cluster
[ ] Turbidity Concentration Measurement Cluster
[ ] Oxygen Concentration Measurement Cluster
[ ] Lead Concentration Measurement Cluster
[ ] Sulfur Dioxide Concentration Measurement Cluster
[ ] Sulfate Concentration Measurement Cluster
[ ] Total Coliform Bacteria Concentration Measurement Cluster
[ ] Total Trihalomethanes Concentration Measurement Cluster

When you say "SDK has to be implemented", what exactly do you mean @Survensa ?

That said, that looks like a list of the provisional concentration measurement clusters.  There are no plans to do any implementation work for those until there is a plan to have them not be provisional.


feat(azure): Add support for Azure PostgreSQL Server

Issue #572
Output example:
 Name                                          Quantity  Unit       Monthly Cost

 azurerm_postgresql_server.my_server
 ├─ Compute (MO_Gen5_16)                            730  hours         $1,379.41
 ├─ Storage                                           5  GB-months         $0.57
 └─ Additional backup storage                     2,000  GB-months       $200.00

 azurerm_postgresql_server.without_usage
 ├─ Compute (MO_Gen5_16)                                 730  hours              $1,379.41
 ├─ Storage                                                5  GB-months              $0.57
 └─ Additional backup storage                  Cost depends on usage: $0.10 per GB-months

@aliscott, this is ready to review!


Add Admin Tools to application panel #37

Created UIExtension object inside AdminTools.WebHome.

The entry inside the application panel:


User Might Not Have Container Write Access

Pretty error message.  Or maybe not show projects that the user can't actually use for deploy.
@grant

Filtering projects is much tougher as 1000s may be returned. Or 100s for enterprise users.
Also I don’t think it’s possible to “test” what a user/token can do (for reasons like security) so I’m not sure if this is doable.
It’s basically not possible to check “can I push to this gcr registry” without actually doing an operation like deleting a tag etc.

Yeah, so maybe we just have to catch the failure and handle it with a better error message.

Maybe once a project is selected we can check perms, and if they aren't sufficient we ask them to select a different project.

"Checking perms" is the difficult thing here. Docker Registry API doesn't really have a "test write access" option, we have to push an image to know that. (And we're pushing images with docker CLI which doesn't have the most parseable output.)
Also I don't think GCR can add such a feature as it’s primarily a Docker Registry v2 API implementation and nothing else.
I see two ways out of this:

Separate docker build  and docker push functionality. If "push" fails re-prompt for project.

Use something like https://github.com/google/go-containerregistry to push the image without docker CLI.

@ImJasonH added https://github.com/google/go-containerregistry/blob/31e00cede111067bae48bfc2cbfc522b0b36207f/pkg/v1/remote/check.go#L12-L49 exactly for this reason.


feat: add CockroachDB driver

I still need to write automated tests and setup CI, but I'm at the end of my day and wanted to go ahead and throw this out there.
I have tested/verified manually on my local computer (Mac) by building journey with the new driver and running my own migration scripts against local db nodes.
A lot of the code is taken from either twrobel3's CockroachDB driver for mattes/migrate or from the db-journey PostgreSQL driver.
Let me know what you think.

Hmm, looks like the crdb utility I'm using (cockroachdb/cockroach-go) isn't compatible with Go 1.7. Is this a blocker?

As of nexdrew/cockroachdb-driver#1, my driver is no longer compatible with current db-journey code because the support for locks is not great (see changes made here). Closing this.
If others are interested in supporting CockroachDB with db-journey, let me know and I can open PRs. In the meantime, I'm gonna try to support my own version of db-journey to see how things work out. Thanks!

Hi, sorry for the delay, was on holidays :)
I will check these changes this week and get back to you.
Thanks


Gradle 5.0-rc-4 exponential backoff makes IDE import very slow

Expected Behavior
Gradle 5.0-rc-4 should successfully sync in Android Studio 3.2.1.
Current Behavior
Gradle sync hangs at the following stage:
Build model 'org.jetbrains.plugins.gradle.model.BuildScriptClasspathModel' for root project 'my-android-project'

Context
This project is using dependency locking.
Steps to Reproduce (for bugs)

Open the attached project in Android Studio 3.2.1
Gradle sync
Cancel with the cross button and repeat if necessary

Sample project:
Gradle Hang.zip
Your Environment
Android Gradle Plugin 3.2.1
Android Studio 3.2.1
Build #AI-181.55<IP_ADDRESS>56338, built on October 9, 2018
JRE: 1.8.0_152-release-1136-b06 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.6
Kotlin 1.3.10
Build scan URL: https://scans.gradle.com/s/sxwbk763vyulg
Daemon thread dump:
gradle.threaddump.txt

Please provide a thread dump (using jstack) of the Gradle daemon when the hang occurs.

I can confirm that this is very slow with the 5.0 RCs. I don't think it's hanging but it is very slow (~10 minutes). It looks as if there is some (unexpected?) slow network access going on.
Works fine with 4.10.2.

@btilbrook-nextfaze can you confirm that this happens with every sync or just the first one?  The "Build model ..." message is a new message in 5.0, but what's happening under the covers is not.  Previously, this time would have been rolled up in the overall sync time and wouldn't be attributed to any particular action.

I can reproduce the issue with Studio 3.2. It's not hanging but loosing time on retrying jcenter with a backoff.

What is troubling though is that the build declares the google() repo first, then jcenter(), but it seems the sync process is trying to lookup things from jcenter() that are present in google().
Also see https://discuss.gradle.org/t/gradle-5-0-rc1-problem-with-artifact-resolution-in-intellij-import/29445 for an internal workaround.
FWIW, Studio 3.3 or 3.4 don't have the issue and the attached project syncs in a snap.

If it works with Studio 3.3 and 3.4 I wouldn't consider it a blocker for 5.0.
@eskatos @oehme WDYT?

So the root cause of the slowness is an internal exception triggering the HTTP retries:
Caused by: java.lang.AbstractMethodError
    at org.gradle.api.internal.artifacts.ivyservice.resolutionstrategy.DefaultCachePolicy.mustRefreshModule(DefaultCachePolicy.java:205)
    at org.gradle.api.internal.artifacts.ivyservice.resolutionstrategy.DefaultCachePolicy.mustRefreshModule(DefaultCachePolicy.java:192)

We are investigating the effect of no longer retrying when seeing that error. However a possible outcome might be we have to declared Android Studio 3.2.1 incompatible with Gradle 5.0.

And that error is caused by an added method on ModuleComponentIdentifier, which was already present in Gradle 4.10. So it really the combination of both causing the problem.

The error is caused by an incompatibility between Android Studio 3.2 and Gradle 5.0.
You have to upgrade to Android Studio 3.3 to work with Gradle 5.0.
The change we are doing for RC5 is #7813. Then the error is no longer hidden. Which means that the Sync in AS 3.2 will no longer "hang", but fail.
Thanks for reporting this @btilbrook-nextfaze!

Thanks for resolving it. I suspected this might ultimately be the outcome.

I had the same problem. Was Looking for some forum on this issue It take 10 minutes when i create a new activity or a fragment. Can someone please elaborate on what causes this issue.


When loop condition + invariant is verified, the whole loop is marked in the UI

The prover reports its verification result of "loop condition and invariant imply block postcondition" with the statement parameter set to the loop. Thus, in the UI, the whole loop is marked, which a) does not look pretty and b) covers other markers in the loop, e.g. invariant markers.

What should it cover? Would only the condition and the invariant be OK? (Yay, passing lists of related nodes requires yet another API change! Nothing to difficult though.).

I think 37c687b is the wrong way to go about this. Internally, the prover already supports passing multiple related nodes. The UI shouldn't really know anything about what the specific proof means to the user, it should be stupid and just display whatever the proof generation strategy thinks is important for this specific proof.
Also, instanceof. Argh!

I think it’s okay that the prover passes the whole loop, the UI can figure out what to do with it by itself. The invariants shouldn’t be marked anyways, because they are already marked when invariantValidAtEntryVerified is fired.

First of all, I think the invariants should also be marked. They, together with the invariants, have to imply the block postcondition.
The question is: Why should the UI even be able to figure it out? For all that it knows, the proof could have been conjured from thin air by a monkey with a typewriter. Maybe this monkey also wants to pass an invariant because he immediately sees that the invariant is too weak.
I think that simply passing a list of ASTNodes is the right way to go about this.

Well, don’t worry about instanceof; if that’s what bothers you, I’ll write a visitor which is only slightly more code …
But if you write

The UI shouldn't really know anything about what the specific proof means to the user, it should be stupid and just display whatever the proof generation strategy thinks is important for this specific proof.

, then we should do it the following way: IProverEventListener contains only one method, stuffVerified, with a list of nodes that it deems important for the current part of the proof. You will also have to supply the messages like "Verifying that loop condition and invariants imply the loop body’s postcondition" in the ProverResult.

On second thought, I’d rather name the method monkeyWithTypewriterVerifiedStuff in accordance with your previous example ;-)

Yes, you are right. That would probably be the cleanest approach. However, that would put natural language into the prover implementation. The compromise I chose was to let the UI know what was proven (e.g. that the conditional and the invariants imply the block precondition) but not how (e.g. the monkey might give you only an invariant because it immediately saw that something was foul about it or even give you the assertion where the whole thing breaks down).
By deciding to only color the condition, the UI already makes a statement about the "how": It tells you that the condition was analyzed to be "incorrect" whatever that means. In reality though, the problem may lie somewhere totally different and the prover may not even have looked at the condition while creating the proof.

Okay, that sounds reasonable, could you make the necessary changes to IProverEventListener in a new branch? I can then fix WorthwhileProveJob accordingly.


bug in burden.R

Hello,
i have the following problem running burden test between 2 counts files (case vs ctrls):
Rscript burden.R --casefile pzcounts.txt --casesize 56 --controlfile ctrlcounts.txt --controlsize 112 --outfile burden_11022021.out.txt
Error in if (case_count > args$casesize) { : argument is of length zero
Execution halted
R version is 4.0.2
PS I guess you should add R "argparse" library to requirement list.
Thank you for this tool!

Hi,
try installing "argparse" package (or "optparse" if your R version doesn't support it but then remember to replace 'library("argparse")' with 'library("optparse")' in burden.R file).
If this doesn't solve it then try to check the counts in your casefile: all the counts for each gene must be less then casesize.
Good luck!


Change Clear button to Back - existing sheet

On the first page of the existing monument submission pathway, change the Clear button to Back. When Back is clicked:

Returns to identify page
If user selects the existing sheet pathway again, any data they already uploaded or entered remains
If user selects the new sheet submission path, any previously-entered data in the existing sheet path is reset/removed/deleted
(Back button should be same yellow color as other existing back buttons)

This seems to be a duplicate of #130

This seems to be a duplicate of #130

I altered the title of #130 slightly to account for the difference between the two. It makes sense on the first page of the new sheet path to have all three buttons (back, clear, next), but for an existing sheet it only makes sense to have back and next because there is no keyed-in data to be cleared, and any uploaded file can be removed via #133.


Custom queries/mutations lack schema support

Environment information
System:
  OS: macOS 14.5
  CPU: (10) arm64 Apple M1 Max
  Memory: 254.86 MB / 32.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
  Yarn: 1.22.22 - /opt/homebrew/bin/yarn
  npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm
  pnpm: 9.5.0 - ~/Library/pnpm/pnpm
NPM Packages:
  @aws-amplify/auth-construct: 1.3.1
  @aws-amplify/backend: 1.4.0
  @aws-amplify/backend-auth: 1.2.0
  @aws-amplify/backend-cli: 1.2.9
  @aws-amplify/backend-data: 1.1.4
  @aws-amplify/backend-deployer: 1.1.4
  @aws-amplify/backend-function: 1.6.0
  @aws-amplify/backend-output-schemas: 1.2.0
  @aws-amplify/backend-output-storage: 1.1.2
  @aws-amplify/backend-secret: 1.1.3
  @aws-amplify/backend-storage: 1.2.1
  @aws-amplify/cli-core: 1.1.3
  @aws-amplify/client-config: 1.4.0
  @aws-amplify/deployed-backend-client: 1.4.1
  @aws-amplify/form-generator: 1.0.3
  @aws-amplify/model-generator: 1.0.8
  @aws-amplify/platform-core: 1.1.0
  @aws-amplify/plugin-types: 1.3.0
  @aws-amplify/sandbox: 1.2.2
  @aws-amplify/schema-generator: 1.2.4
  aws-amplify: 6.6.0
  aws-cdk: 2.158.0
  aws-cdk-lib: 2.158.0
  typescript: 5.3.3
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Describe the bug
a.mutation().arguments({
  id: a.id(),
  items: a.ref('Item').array()
})

When using custom queries/mutations like the above, the arguments are not valid to the typescript requirements. It seems that arguments are limited to primitives and lack support for things like arrays, references and custom types. This appears to be a blocker for us. Are there any work arounds?
Reproduction steps
a.mutation().arguments({
  id: a.id(),
  items: a.ref('Item').array()
})

Hey,👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂


Microsoft.Bot.Builder.Adapters.Facebook.FacebookMessage class is missing the Referral property for existing user scenario.

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
4.13.2 +
Describe the bug
Facebook describes two scenarios to the referral parameter being passed.

Uses the Postback root property which is catered for but scenario
uses the referral root property which can't be used.

See here both payload scenarios here
https://developers.facebook.com/docs/messenger-platform/discovery/m-me-links/#reading_parameter
To Reproduce
Use an m.me link with ref parameter for an existing page user scenario. Webhook sends this payload.
{
"sender":{
"id":""
},
"recipient":{
"id":"<PAGE_ID>"
},
"timestamp":1458692752478,
"referral": {
"ref": "ref_data_in_m_dot_me_param",
"source": "SHORTLINK",
"type": "OPEN_THREAD",
}
}
FacebookMessage class is missing the referral property in the root
Expected behavior
The Facebook message should have the Referral parameter set if available

@mrivera-ms - Can you help get this PR reviewed?

Hi @mrivera-ms, we reproduced the issue and after applying the fix in PR #5948 it was solved. Also, the PR looks good 👍

This has been fixed.


Publish a scala 2.11 version

I am using scala 2.11-RC1 in my project, and would like to try debox.
Please publish a 2.11 compatible version.
Thanks!

You already seem to support scala 2.11.
closing.


No "keep screen on" option

[Enter feedback here]
Docs say there is a "keep screen on" option.  This doesn't exist in the latest version (v0.65.0).

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: a20e555a-65ad-82e7-e1c0-f6577c1322b2
Version Independent ID: 29236a0e-82e8-92d7-a5fb-12a9a777bcc2
Content: PowerToys Awake utility for Windows
Content Source: hub/powertoys/awake.md
Product: dev-environment
Technology: powertoys
GitHub Login: @mattwojo
Microsoft Alias: mattwoj

To clarify, I am using the GUI, not the CLI.

Got a screenshot of the settings? :)

That's because the current selection ("Keep using power plan") is actually a passive state, therefore the setting for the screen is hidden. I agree it's confusing. Select a different mode and see what happens :)

That's because the current selection ("Keep using power plan") is actually a passive state, therefore the setting for the screen is hidden. I agree it's confusing. Select a different mode and see what happens :)

It's working fine, the documentation just confused me at first.

It says

This feature only works if Awake is running in one of the two Keep awake state.

now, does that suffice?

Sure, but I was thinking the screenshot should be updated and the section "Keep Alive" removed.


Proofreading of documentation

All documentation(wiki page), and readme's of all components should be proofread.

@slax0rr I can do that. I'll open a PR once I am done with it.

@codeahead14 it's all yours, make sure you catch the documentation in the feature/userDocs branch.

Hi @slax0rr, I have opened a PR updating the README.md. Please review and comment.

@codeahead14 there is no PR.

@slax0rr Please check now. An issue at my end.

Proofreading on https://github.com/SlaxWeb/Framework/tree/feature/userDocs/docs/source is still required.

Hi @slax0rr , Yes I am undergoing the documents.

@codeahead14 awesome, thanks for your help!


Create How It Works page

This page has two versions depending on what tab is selected at the top. All of the content is created in variables so that the appropriate content can be displayed.
I've made a sub-component in the page for BulletGrid (the white squares section) and the InstructionGrid (text and images on the top half).
I made a component QuestionList for the clickable drop-down questions since I could see that being used in other places on the site.

I've made all the requested changes except the questions drop-down. I think it makes sense to make another pull request for updating How It Works and the home page to use the same module for the questions drop-down, and style them consistently.


[SQL][V20200801] Adding new API version with named replica and maintenance

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

failover APIs are being added which look good. The inaccessibleDatabases APIs were added accidentally and are being removed. they are not live yet and no customers. So not a breaking change. Signing off from ARM side.

@ruowan can you please merge this?  Thank you.

/azp run automation - sdk

/azp run automation - sdk

/azp run


DevKit Payload UART wrapper (PLUART) should implement a queue for sensor lines, rather than a single buffer

Issue / request

PLUART maintains a single static _user_line buffer for thread-safe access of serial line data from sensors.
If the client app does not service data in this buffer with a call to readLine before another line comes from the sensor, the new line overwrites the buffer and data is lost.
Implement a thread-safe queue/buffer that can store multiple lines.
Alert client if data if queue overflowed and has been overwritten/lost.

Background / why
The PLUART namespace (defined here) adds some very convenient wrappers to the DevKit's Payload UART interface, which is the data interface for many of the serial connections the DevKit supports (UART, RS232, RS485, RS422, SDI-12).
There are (2) thread-safe methods exposed for users to access Rx data from their apps - PLUART::readLine and PLUART::readByte.
readLine can be used when the attached device is generating frames of serial data with reserved delimiting characters (a common example is ASCII text data with <CR> and/or <LF> being the frame delimiter). This is a very common pattern for legacy marine sensors so this is a very convenient wrapper to have.
The issue is that most of these sensors will have some multi-line data or command responses, the the potential for overwriting with the existing implementation results hairy-edge brittleness and a poor developer experience - the line buffer works most of the time. Works often enough to make it non-obvious what exactly is going wrong, but fails more than often enough to make it something a developer can just ignore. It's also susceptible to small timing changes in the app causing things to break, which can result in pernicious Heisenbugs.
related PR from legacy private repo for reference: https://github.com/wavespotter/bristlemouth/pull/465

As of the FreeRTOSConfig.h files I have read, it does seem like the protocol uses the CMSIS API for FreeRTOS.
So it could feasibly be solved by redefining the buffer in https://github.com/bristlemouth/bm_protocol/blob/3c10ebdedcb73a3b012b9545f5171ab0ba3a9ca8/src/lib/common/payload_uart.cpp to be a CMSIS message queue.
https://www.keil.com/pack/doc/CMSIS/RTOS/html/group__CMSIS__RTOS__Message.html
https://www.keil.com/pack/doc/CMSIS/RTOS2/html/group__CMSIS__RTOS__Message.html
The message queues are thread safe, but the messages in the queue are consume-on-read.


release(fix) : duplicate release for helm chart

this commit remote helm release workflow trigger on create which triggers duplicate event as push
fixes: #459

Hey @viveksyngh, thanks for taking this issue and solving it!
I recall we had some issues on releasing Helm Charts upon tagging, @mendrugory worked on that: let's wait for feedback from him!

Thanks @viveksyngh  for your contribution !!


Default chain ID should not be 1

Component
Forge
Describe the feature you would like
In #603, the chain ID was set to default to 1 if not specified (this may have already been the default behavior, though the rest still applies). Defaulting to mainnet's chain ID is not great for a few reason:

permits and other signatures generated during tests are valid and can be replayed on mainnet
When RPC support is added, frontend devs will change the network in metamask to the local forge node. Adding this network requires will require specifying a chain ID of 1, meaning any development transaction is now a valid mainnet transaction

We should default to 99 (like dapptools), 31337 (like hardhat), or really any arbitrary number not in use
Additional context
No response

cc @onbjerg

Yeah, it was already the default behavior. https://github.com/gakonst/foundry/pull/609


.depent not updating properly

project structure:

src/

main.c
sub_module1/

sub_module1.c
sub_module1.h

sub_module2/

sub_module2.c
sub_module2.h

problem:
Both main.c and sub_module1.c are dependent on sub_module2.h.
But on changing sub_module2.h and calling make compile only main.o gets recompiled.
Since there isn't necessarily an error this can cause impossible to debug problems or unwanted behavior of the compiled program.
expected behavior:
Both main.o and sub_module1.o should be updated.

Option 1: Ignore the "source" structure and put every *.o directly into the "build" directory without subdirectories.
or
Option 2: Maintain structure and insert full path to the *.o file

Option 1: Ignore the "source" structure and put every *.o directly into the "build" directory without subdirectories.
or
Option 2: Maintain structure and insert full path to the *.o file

I went with option 2


fix rowanj-gitx.rb

Closes #9196.

I have already pushed a commit for this manually 683134e39340ef31519b58c2328a3a2534cf927a .

Ah, thank you. I was really confused, for a moment: “I just fixed everything, why the heck am I still getting conflicts”?


fix(data-explorer): remove tabs bug

The result data in table is incorrect when any tab closed. Steps to reproduce:

Run three different queries to get three different result tabs
close one of them
check remaining tabs

I confirm the issue has been fixed. Please rebase to resolve conflict.


Update wrangler tag to point to wrangler:master

Updates

Update wrangler tag to point to wrangler:master

@chiukapoor Based on @MbolotSuse's comment, we can close this PR as norman master branch is already using tagged wrangler version with 1.28 changes.


2354 add a test script to run the quick system tests and publish results to s3

Make sure you have checked all steps below.
Issue

[x] My PR addresses the following issues and references them in the PR title. For example, "Issue 1234 - My Sleeper
PR"

Resolves https://github.com/gchq/sleeper/issues/2354

Tests

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

No tests required as this script runs the system tests

Documentation

[X] In case of new functionality, my PR adds documentation that describes how to use it, or I have linked to a
separate issue for that below.
[X] If I have added, removed, or updated any external dependencies used in the project, I have updated the
NOTICES file to reflect this.

I currently have this running as a cronjob and it appears to be working. It has also tested manually outside of the Docker containers on my dev VM.


chore: use colors from theme for notification's severity

Hey, I just made a Pull Request!
Colors of severity icons are based on theme.
Follow-up for https://github.com/backstage/backstage/pull/23371#discussion_r1524651872
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

not stale, it just needs 2nd review round.
Cc @Rugvip

not stale

not stale.
Cc @Rugvip


Put cookie bar on the top

hello @MariaSolovyeva
could you make top of "gitter-chat-embed" dynamically? based on the navbar bottom?

LGMT


Bug fix

Fixed _create_get_pricing_request method for products.
If the SKU contains a space, amazon returns "Client Error".

@saleweaver this is also affecting us, +1 for getting this merged!


Clipboard is not supported, due to requiring frame-spanning async

@philpax you resolved this one right?
Broke out this from an umbrella issue

Yep, all done in https://github.com/AmbientRun/Ambient/commit/7317bf0b4d21e239cbb00fe6f7727617cce1d531


./traccar.run: line 488: ./setup.sh: Permission denied

Hi Tananaev,
I tried to install traccar with following permission denied message. i have did 'chmod +x traccar.run' but still got same message, need your help
[root@server src]# ./traccar.run
Verifying archive integrity... All good.
Uncompressing traccar  100%
./traccar.run: line 488: ./setup.sh: Permission denied

Thanks in advance

You can extract it manually and run setup script. See https://github.com/tananaev/traccar-client-android/issues/101 for some more info.

Hi @tananaev I also got some experience on Permission denied
./traccar.run: line 488: ./setup.sh: Permission denied
can you help me to resolve it

What version are you using?

I believe you are running as a regular user which does not have the ability to create /opt/traccar.
Try running the script with elevated privilege - i.e., "$ sudo ./traccar.run --target /opt/traccar"


Change case of Speak With Animals to standardize

This was the odd spell out that used this case standard.

"Speak with Animals" is standard in Chicago, MLA, and Paizo titlecase.


Adds NSG Flow log via ARM info - fixes #79516

@kilasuit : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@kilasuit : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@kilasuit : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@GitaraniSharma-MSFT: I'm sorry - only the author of this article, @damendo, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off


[CSClosure] Remove last remaining uses of one-way constraints

Removes uses of one-way constraint from for-in conditions and
case patterns which are solved via conjunctions.

@swift-ci please test


test: make test paths more portable

Windows uses \ as the separator rather than /.  Adjust the tests for
this.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @harlanhaskins @jrose-apple

@swift-ci please smoke test

Haha, yes, that would be nice.  We just got a CI bot!  So, perhaps dreams to come true :-D


Documentation Revisions For 1.9.0+

The Konvoy 2.1.1 docs currently state to use the latest version of KIB: https://docs.d2iq.com/dkp/konvoy/2.1/image-builder/create-ami/
The latest version fails when using Kommander due to APIs being removed: https://kubernetes.io/blog/2021/08/04/kubernetes-1-22-release-announcement/#removal-of-several-deprecated-beta-apis
Docs should be updated accordingly to make note of incompatibilities, and if 1.9.0+ is intended to be used with Konvoy 2.1.1 there should be details telling you to use --kubernetes-version=1.22.8 as a parameter with the dkp cli.

We need to version KIB with specific versions of Konvoy and then document properly those version compatibilities. This is on our backlog.

Our new docs have mapped versions of dkp to kib https://docs.d2iq.com/dkp/2.4/konvoy-image-builder#id-(2.4)KonvoyImageBuilder-compatible-versionsCompatibleVersions
which match the kubernetes versions, kib versions, and dkp versions accordingly


Update repositories.txt

MCP3304 library which does not require the use of SPI/ serial.
Has three different options: either pulling the raw number 0-4095, pulling the voltage input, or pulling an averaged voltage with the option to select the amount of times it is averaged 0-1000, and adding in one's own delay between each averaged amount.

Tag has been created as the initial version matching the library.properties folder

@ArduinoBot


Add workflow example for CMIP6 ingestion from Thredds via STAC API backend

Add workflow example for CMIP6 ingestion from Thredds via STAC API backend.
Requires https://github.com/cedadev/stac-generator/pull/55

Hi @rhysrevans3, you are now an admin on this repo so you can accept the PR.


fix: use shellwords instead of shlex

The shlex splitting was ruining Windows paths. The shellwords is nicer to Windows.

Superseded by https://github.com/gptscript-ai/gptscript/pull/758


Get your Use Case Buddy started

Tutorials: https://developers.sap.com/tutorials/build-use-case-buddy.html
STEP 3
Import the templates for SAP Build Apps & Process Automation
After downloading and unzipped the template, it is forbidden to import content in SAP Build with Trial Booster
Importing is forbidden

For the file : use case buddy process..mtar in UseCaseBuddyTemplates_PleaseExtract.zip
there is a Correlation Id: 5295732a-b82b-4806-4a2b-ca44c37977ee

@FriederikeMa, can you please respond to the user's feedback?  Thank you.

Hi @AmauryVanEspen. The import could have failed due to your role setup in the BTP account you're using. A quick role assignment should fix it. Please use this guide and the mentioned roles https://help.sap.com/docs/build-apps/service-guide/configuring-user-roles.
Hope this helps! :)

I've tried reviewing role without success. Does it work in free tier ?

Yes it works in free tier.
Did you add all of the roles described in the guide?
Like these:

BuildApps
Registry
BuildAppsAdministrator
RegistryAdmin

Provided feedback for issue


New message view design not in threaded view

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.600
Where did you get the app from?
Google Play
Android version
13
Device model
No response
Steps to reproduce

Go to Unified Inbox

Click on a message which is not in a message thread.

Enjoy the restyled message view.

Go to Unified Inbox

Click on a message which is part of a message thread - you'll be taken to the thread view

Click on a message in the thread view

Enjoy the "old" message view instead of the restyled one.

Expected behavior
I would expect the new message view to be consistently seen in every message view.
Actual behavior
When I click on a message, which is not in a message thread, in the Unified Inbox, I see the new message view, with indication at the top which account the message comes from.
When I click on a message in the Unified Inbox which takes me to the thread view (i.e. the view listing all messages from the same thread) and then click on the message, I still see the old message view (without the indication of the account). The account is shown in the thread view (at the top, but with a simple, unstyled display), but not in the final message view.
Logs
No response

Hello @cketti .
We have thoroughly tested and replicated the bug scenario, and it has occurred for us on the following device and software configuration:
Phone Model: Samsung A6
Android Version: 10
K9 App Version: 6.702
App Source: F-Droid
Unified Inbox -> Click on a message which is not in a message thread -> Restyled message view :

Unified Inbox -> Click on a message which is part of a message thread - you'll be taken to the thread view -> Click on a message in the thread view -> "old" message view instead of the restyled one:


props cause render even if I didn't use props in render

Hello.
I read #347 so I know mobx cannot react by part of props, But I thought an observer component's render function is "react" at all the time props change(filtered by shallow equality check).
In other words, I thought render function won't be called in an observer component that doesn't use props in rendering.
mobx-react-devtools's observer tree shows "reactive props" if the component access props in render function, so I believe my guess.

But unlike what I think, render function called even if I didn't use props in there.
In this sample,  LoggableCounter's props won't use its props in render. but it re-render when I change its props by App's input box.
I guess observer component has to call render when its props change because the event has to call component's lifecycle. Is that right?
then, isn't there an awesome way to prevent re-render when the component function doesn't use props in render function? I know I can optimize this by split a component or make prop boxed-value. but I wonder if those are the best ways. For example, I think mobx-react can provide decorater like observer but somethings that makes problems are excluded from the decorated component's lifecycle.

awesome way to prevent re-render

Even better - if we would know that props wasn't used we could immediately return false from shouldComponentUpdate skipping shallow equality check.
The problem is that mobx tracks only render, but componentDidMount, componentDidUpdate, getDerivedStateFromProps can depend on props as well - they can affect rendered output.
So we would have to use different technique to detect props access in these methods.
Currently we are patching getter/setter, however I think that wouldn't work with getDerivedStateFromProps, because (correct me if I am wrong) it runs before the getter/setter is called.
But most importantly I think that the utilization is so limited it's not worth to bother ... it's effective only if this.props (whole object) is accessed conditionally or if some prop is passed accidentally... or am I missing something?

it's not worth to bother

Let's call the component MobxPureComponent that excludes the props-dependent lifecycle.
(This is one example of a solution to my issue. There will be many other solutions.)
If mobx-react provides a decorator that makes MobxPureComponent, I can optimize props-based render by using computed. I think it's worth to bother.
I know props  is immutable, so if I change partial of props the component cannot react selectively.
But other example is ready:
In my example, parent renders count and child renders Math.floor(count/2).
so child's render count should be roughly half of parent's render count when I optimized them well.
There's two counter example.
In react props example, parent has observable count variable and it is passed to child.
In store props example, store has props like component. It's observable.ref variable. It should be changed by calling setProps and setProps makes it immutable like props.
according to mobx-react-devtools's observer tree,
render function of child component in react props example depends on reactive props.
In store props example, the render function depends on the store's props variable.
In both examples, render function of the child component depends props(or props-like thing). And I tried optimizing them in the same way. But react props example cannot be optimized by computed-value.
React's passing props and making pure component is easy to read, and is easy to divide work. It would be very sad if I could not optimize the "props" provided and always had to write a store or boxed-value.
Thanks.

It was not the answer I wanted, but I was convinced of the direction that this project is pursuing. Thank you for your kind reply.


proc newGFileTmp*() is wrong in v0.8.5

See
https://discourse.gnome.org/t/g-file-new-tmp/5585

Should have been fixed, closing.


PostCSS 7 upgrade

Refs csstools/postcss-preset-env#58
Also added a package-lock file.

Thanks, @pascalduez !


Shovel Knight [PCSE00640]

App summary

App name: Shovel Knight
App serial: PCSE00640
App version: 1.00

Vita3K summary

Version: v0.1.8
Build number: 3216
Commit hash: https://github.com/vita3k/vita3k/commit/343d438e
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: njs
OS: Windows 11
CPU: I7 13700kf
GPU: AMD Rx 580 8G
RAM: 16 GB

Issues
No issues
Runs great
Screenshots

Log
Recommended labels

A?
B?
C?

please include screenshots and a log

Game plays without issues

Game plays without issues

When I tried to play, I had two issues:
One, the game ran too fast, and
Two, the black menu bar at the top of the screen was completely destroyed.

Had the same broken bar with opengl, but on vulkan the menu bar is normal.


Add misc script to find missing towncrier news files

The script finds missing towncrier files by scanning for merge commits that are not already in the CHANGE_LOG or not have the skip_release_notes label on github for the PR.

@sklam, could you list in the script the set of libraries it depends?

github.py
gitpython
docopt

Am I missing any other lib?

RE: https://github.com/numba/numba/pull/9101#issuecomment-1668421661
I have added the list to the script.

If you run the script on this branch, you will see:
> python maint/towncrier_checker.py  --token=insert_gh_token --beginning=0.58.0dev0 --repo=numba/numba
Removing 8982 as already in CHANGELOG
Removing 8932 as already in CHANGELOG
Removing 9004 as already in CHANGELOG
Removing 8929 as already in CHANGELOG
Removing 8964 as already in CHANGELOG
Removing 8958 as already in CHANGELOG
Removing 8895 as already in CHANGELOG
Removing 8976 as already in CHANGELOG
Removing 8896 as already in CHANGELOG
Removing 8998 as already in CHANGELOG
Removing 9005 as already in CHANGELOG
Removing 8978 as already in CHANGELOG
Removing 9006 as already in CHANGELOG
Removing 8996 as already in CHANGELOG
Removing 8902 as already in CHANGELOG
Removing 8909 as already in CHANGELOG
Removing 8947 as already in CHANGELOG
Removing 8965 as already in CHANGELOG
Removing 8907 as already in CHANGELOG
PRs that are missing towncrier notes and not skipped
7262 https://github.com/numba/numba/pull/7262
7543 https://github.com/numba/numba/pull/7543
8462 https://github.com/numba/numba/pull/8462
8885 https://github.com/numba/numba/pull/8885
8892 https://github.com/numba/numba/pull/8892
8906 https://github.com/numba/numba/pull/8906
8911 https://github.com/numba/numba/pull/8911
8916 https://github.com/numba/numba/pull/8916
8944 https://github.com/numba/numba/pull/8944
8974 https://github.com/numba/numba/pull/8974
8988 https://github.com/numba/numba/pull/8988
8995 https://github.com/numba/numba/pull/8995
9035 https://github.com/numba/numba/pull/9035

The Removing XXXX as already in CHANGELOG are showing PR merged that are already mentioned in the CHANGE_LOG, which indicates they are included in a previous release.
Everything else under PRs that are missing towncrier notes and not skipped are the PRs that is missing towncrier news fragment and they don't have the skip_release_notes label on GH.

Thanks, Siu! Already approved the PR.


Speedup rebuilding native helper changes

I was working on improving #5617, and while changing the pub native helper script, I noticed that rebuilding would rebuild native helpers for all ecosystems.
I think reordering things this way should make things a bit more efficient.

Change is 👍 to me, but did you verify it's actually faster? 😄 I've been surprised by Docker caching behavior a few times

Yeah, I did this while making changes to pub native helpers and after this when rebuilding you would no longer rebuild composer helpers, which are quite slow to rebuild, and others, making things faster!
Here, worst case scenario is changing composer helpers. No speedup there because it's the first in the list so changing any native helper file there triggers a rebuild of everything.
Best case scenario is changing terraform helpers. Since they come last in the list, changes in them will only cause rebuilding terraform native helpers but nothing else from other ecosystems.

This is really surprising behavior. Thanks for the speed up!


feat(cli): synchronize Tauri config and lib name with iOS Xcode project

the Xcode project now uses a fixed output library name, which means changes to the Cargo.toml lib name won't affect it (backwards compatible change, we're checking if this new format is being used or not by reading the project.pbxproj)
sync config identifier with the pbxproj
sync development team config with the pbxproj

the sync runs both on dev and on build

CI fix #10803


Supported SLS files

Hi,
I use the plugin via the cmd.run_all method.
I want to call SLS files via the state.sls method, but the output is not supported by SaltJsonReturnHandler.java. For the moment I have defined state.sls as *alwaysSuccessful, but I want to catch errors.
I would like to improve the plugin. Is it the best ways to write a new class SaltStateJsonReturnHandler.java (as SaltJsonReturnHandler.java) that parse state.sls json output ?
I did not succeed to have the same output with stale.sls than with cmd.run_all.
Rémy

The response from salt modules to the rundeck salt api comes as a boolean, either True or False or nested dict, like stdout, stderr, pid, response code. Either we can change the response output which salt api sends back to rundeck or write new code to handle the response on rundeck level.


[BEAM-10322] allow only single assignment to producing stages by pcol…

…lection map

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

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @pablom
CC: @robertwb

Run Python2_PVR_Flink PreCommit

can you share how to reproduce the issue, Heejong? @ihji

Could you clarify what the bug that you're trying to fix here is?

We're trying to find producer stages of a PCollection. The first stage
encountered is the producer (due to the topological order) Subsequent
stages encountered with subtransforms producing the PCollection are
consumers where a Data input transform reads in the PCollection.
I can go back to add the comment.
On Thu, Jul 2, 2020, 5:08 PM Robert Bradshaw<EMAIL_ADDRESS>wrote:

@robertwb commented on this pull request.
In sdks/python/apache_beam/runners/portability/fn_api_runner/execution.py
https://github.com/apache/beam/pull/12086#discussion_r449317183:

@@ -375,6 +375,8 @@ def get_all_side_inputs():
for o in transform.outputs.values():
if o in s.side_inputs():
continue

     if o in producing_stages_by_pcoll:

Why is it OK to ignore duplicates?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/12086#pullrequestreview-442079350,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJ5Z3HA54C75UNJTXSLX3TRZUOORANCNFSM4OHTZ6JQ
.

Here's a concrete example that can be fixed by this PR:
Stage A:
  (Input PCollection i - PTransform 1 - Output PCollection j)
Stage B:
  (Input PCollection j - PTransform 2 - Output PCollection k)
Stage C:
  (Input PCollection j for side input - PTransform 3)

We want to find Stage A for emitting side input for Stage C. However, some synthetic PTransforms are inserted during pipeline optimization phase:
Stage A:
  (Input PCollection i - PTransform 1 - Output PCollection j)
  (Input PCollection j - Synthetic Write - Data Sink)
Stage B:
  (Data source - Synthetic Read - Output PCollection j)
  (Input PCollection j - PTransform 2 - Output PCollection k)
Stage C:
  (Input PCollection j for side input - PTransform 3)

If we allow multiple assignments to producing_stages_by_pcoll, Stage B will emit side input for Stage C (topologically Stage B comes after Stage A). Since Stage B and Stage C have no dependencies, the pipeline will succeed when Stage B is executed first and fail when Stage C is executed before Stage B.

Folks just checking. I do not see an LGTM or an approval on this PR. Is everyone OK with it being merged?

My bad. Heejong and I discussed it via chat last week. I forgot to add the
LGTM when I merged.
On Tue, Jul 7, 2020, 9:36 AM Ahmet Altay<EMAIL_ADDRESS>wrote:

Folks just checking. I do not see an LGTM or an approval on this PR. Is
everyone OK with it being merged?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/12086#issuecomment-654982821, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJ5Z3ASYENCBI7LTG4RQMDR2NFI7ANCNFSM4OHTZ6JQ
.


ssh access to CAPO cluster nodes

[ ] setup (central) vault or use operations vault
[ ] setup bastion hosts
[ ] Modify CAPO bastions to take certificates instead of keys

Dupe of https://github.com/giantswarm/roadmap/issues/634


How to Remove the top swiping icon on table view of floating panel

see in this figure above the search bar there is one icon indicating dragging how to remove that.

Hi, please see the Use a custom grabber handle section in the repo readme.
All you have to do is to set to true the isHidden property of the surfaceView's grabberHandle:
For example:
fpc = FloatingPanelController()
//
// your setup here
//
fpc.surfaceView.grabberHandle.isHidden = true

Thank you very much


Failures on [ VM / Service ] Added getAllocationTraces and setTraceClassAllocation RPCs and identity hash support

There are new test failures on [ VM / Service ] Added getAllocationTraces and setTraceClassAllocation RPCs and identity hash support.
The tests
service_2/get_allocation_traces_test/dds RuntimeError (expected Pass)
service_2/get_allocation_traces_test/service RuntimeError (expected Pass)

are failing on configurations
app_jitk-linux-debug-x64
app_jitk-linux-release-x64
dartk-linux-debug-simarm64c
dartk-linux-release-simarm
dartk-linux-release-simarm64

cc @bkonyi @rmacnak-google

I can't find these failures anywhere on the bots from around the time this issue was filed. These tests should be skipped on app_jit and simarm configurations.
Can you link the failure logs @dcharkes?

@bkonyi https://dart-ci.firebaseapp.com/#showLatestFailures=false and search for 45017.

This was resolved in https://github.com/dart-lang/sdk/commit/7315480f5d8eba30ed455d83344daa1108627157.


Broken link https://appget.net/packages from front page

Thank you Keivan! Confirmed
New gallery looks slick :)


[Localization] Add a couple of missing imports

Import Path.h and FileSystem.h directly since they are the source
of llvm::sys::path::extension and llvm::system::fs::OpenFlags
respectively.
Resolves: rdar://77277253

@swift-ci please test


Not working on AndroidStudio 3.1 Canary 6

not working. the option is not showing

have the same problem.
didn't work for me


Upgrade engine to match types

Lowering types in stead of upgrading engine

Lowering types in stead of upgrading engine


Typo in the word "SharePoint"

Before creating a pull request, make sure that you have read the contribution file located at
https://github.com/pnp/powerShell/blob/dev/CONTRIBUTING.md
Type

[ ] Bug Fix
[ ] New Feature
[ ] Sample

Related Issues?
Fixes #X, partially fixes #Y, mentioned in #Z, etc.
What is in this Pull Request ?
Please describe the changes in the PR.
Guidance

You can delete this section when you are submitting the pull request.*
Please update this PR information accordingly. We use this as part of our release notes in monthly communications.
Please target your PR to Dev branch. If you do not target the Dev branch we will not accept this PR.

Closed because they are other typos I didn't fix, I will fix it and send a new pull request


I have a question about this version of stable-diffusion and vae

First of all, I want to thanks the author of this version of dreambooth, he let us easy to train our model
I would like to ask: I tried to use the CKPT model made in this version of dreambooth via colar  , but I found some of model have a problem: the eyes, noise...  of the model were obviously weird. I don’t know if I should add vae to correct it? A version would recommend?
thanks

The latest vae is already included in the base model, what you have to do is make sure your input images are high quality in the format png

The latest vae is already included in the base model, what you have to do is make sure your input images are high quality in the format png

Thanks for resolving my concerns for me


[BUG] SEA Visualforce Pages for Digital Experience

Describe the bug
Currently you are unable to include most of the Summit Events App Visualforce pages on a Digital Experience Site.
To Reproduce
Steps to reproduce the behavior:

Go to a Digital Experience Site
Try to add a Visualforce Page to an Experience Site page

Suggested Fix
Visualforce pages will not be available for Digital Experience unless the pages metadata includes the availableInTouch set to true:
<availableInTouch>true</availableInTouch>

Included in beta release <IP_ADDRESS>

Included in production release <IP_ADDRESS>


Left View PR

Sir @tarun26091999  Please have a look over this I have created a PR for this problem #1571 .

you have to mention the issue in PR, not PR in itself.

I didn't get your point can u plz explain?

#include
using namespace std;
#include
//creating a Binary Tree Node class
template   //makes sure that we can make a node of any data type we want
class BinaryTreeNode {
public :
T data;                      //data corresponding to the paticular node
BinaryTreeNode *left;     //stores the address of the left side of the BT
BinaryTreeNode *right;    //stores the address of the right side of the BT
  BinaryTreeNode(T data) {
      this -> data = data;
      left = NULL;
      right = NULL;
  }

};
//Take the Input Of the Binary Tree in the level Order Traversal
// Make sure if there is left or right node of any node then give it's data as -1;
BinaryTreeNode* takeInput() {
  int rootData;
  cin >> rootData;
  if(rootData == -1) {
      return NULL;
  }
  BinaryTreeNode<int> *root = new BinaryTreeNode<int>(rootData); //the root node
  queue<BinaryTreeNode<int>*> q;
  q.push(root);
  while(!q.empty()) {
      BinaryTreeNode<int> *currentNode = q.front();
    q.pop();
      int leftChild, rightChild;
      cin >> leftChild;           //giving the data for the leftChild .If the data provided is -1  don't make any node of it .
      if(leftChild != -1) {
          BinaryTreeNode<int>* leftNode = new BinaryTreeNode<int>(leftChild);
          currentNode -> left =leftNode;
          q.push(leftNode);
      }
      cin >> rightChild;
      if(rightChild != -1) {
          BinaryTreeNode<int>* rightNode = new BinaryTreeNode<int>(rightChild);
          currentNode -> right =rightNode;
          q.push(rightNode);
      }
  }
  return root;   //returning the root of the Binary Tree

}
//left view of a Binary Tree  Example:  1:2,3 ; 2:4,5; 3:6,7; 4:-1,8
//      1
//    2   3
//  4  5 6  7
//   8
//the left view will be : 1 2 4 8
// Understanding: When we carefully observe this ,all the elements that are occuring at the starting of every level is added up in
// the left view  of a BT
// So we try to taverse the tree in a level Order Traversal and storing the starting element of each level in the vector .
// At the end returning the vector ,that will contain the elements (left view elements).
vectorleftview(BinaryTreeNode*root)
{
vectorans;
if(root==NULL)      //checking for the base case if root==NULL return the empty vector
{
return ans;
}
 queue<BinaryTreeNode<int>*>q;

 q.push(root);
 while(!q.empty())
 {
     int n=q.size();          //gives the no of elements at a particular level stored in the queue at a particular time
     BinaryTreeNode<int>*help=q.front();
     q.pop();
     ans.push_back(help->data);   //storing the first encountered elemts in the particular level
     if(help->left!=NULL)
     {
         q.push(help->left);      //storing the left and the right nodes in the queue if exists
     }
     if(help->right!=NULL)
     {
         q.push(help->right);
     }
     n--;
     while(n--)        //working for the left over elements at the same level just excluding the first element
     {
         BinaryTreeNode<int>*help=q.front();
         q.pop();
         ans.push_back(help->data);
          //storing the left and the right nodes in the queue if exists
         if(help->left!=NULL)
         {
            q.push(help->left);
         }
        if(help->right!=NULL)
        {
           q.push(help->right);
        }
     }
 }
 return ans;

}
@tarun26091999  Sir this is my code

Closes issue:#505
@tarun26091999  Sir


Handle unexpected buildbox-casd termination in asyncio event loop

See original issue on GitLab
In GitLab by [Gitlab user @juergbi] on Oct 3, 2019, 18:14
buildbox-casd should normally terminate only after BuildStream sends SIGTERM in CASCache._terminate_casd_process(), which is never be invoked while the asyncio event loop is running. We should thus install an event loop handler to detect unexpected buildbox-casd termination as early as possible in the main process.
The handler should immediately stop the scheduler and job child processes and report the issue to the user, printing the last log lines of buildbox-casd and its exit code.

In GitLab by [Gitlab user @BenjaminSchubert] on Oct 4, 2019, 15:10
assigned to [Gitlab user @BenjaminSchubert]

In GitLab by [Gitlab user @BenjaminSchubert] on Oct 4, 2019, 15:11
mentioned in merge request !1620

In GitLab by [Gitlab user @marge-bot123] on Oct 8, 2019, 19:12
closed via merge request !1620

In GitLab by [Gitlab user @marge-bot123] on Oct 8, 2019, 19:12
mentioned in commit d390fd62f28db1cb812554d386f2b3560e5e6628