Define experience for notation sign command

Things to consider

Should we use a default key or need the user to explicitly specify the key
Does signing automatically push signature to repo? Which repo?
How does one filter out private signatures from being automatically pushed to public repos?
Make params like --trust more intuitive.

Related to #78 #88

Spec  needs to be finalized to start on this.

Per some feedback, I'd like to see something implemented such as a --dry-run switch on notation sign which returns back information about what is going to be signed.  This way someone can make sure they are going to be signing the right artifact.

Per some feedback, I'd like to see something implemented such as a --dry-run switch on notation sign which returns back information about what is going to be signed. This way someone can make sure they are going to be signing the right artifact.

@dtzar  - Extending the above, @gokarnm  pointed out that we should have a similar debug capability for all CLI commands, that can be used for "diagnostic logging" to find problems and validate workflows. Do you think that is a separate user story, or should it be a requirement for all CLI command we implement.

Here is a summary. I suggest changing the list in the issue to task-list, and check the one which is resolved.

Should we use a default key or need the user to explicitly specify the key

User can specify the key or use the default key without specifying any key

Does signing automatically push signature to repo? Which repo?

After successful signing, sigature by default is pushed to the same repo as container image

How does one filter out private signatures from being automatically pushed to public repos?

User can disable the auto-push using --push false, and generate signatures to specify path using --output flag, @shizhMSFT please comment

Make params like --trust more intuitive.

@gokarnm could you elaborate this one?

--trust may have been a parameter supported in early alpha releases, I'm not able to find a reference to it. The overall reason this issue was created was to track documenting the CLI experience (spec) for Sign (and Verify) command so that we can gather feedback from the community and finalize the CLI experience that can be then implemented.

--trust may have been a parameter supported in early alpha releases, I'm not able to find a reference to it. The overall reason this issue was created was to track documenting the CLI experience (spec) for Sign (and Verify) command so that we can gather feedback from the community and finalize the CLI experience that can be then implemented.

I will start to update the sign command in notation_cli.md (like verifying existing options, adding examples) and then issue a PR for a review. This PR can also be used to align rc.1 sign behavior. What do you think? If we agree with this initiative, we can later do the same thing for other commands.

Yes, that sounds great. We want to go through each command that we want to stabilize in RC1 and define/review the experience.

@gokarnm @SteveLasker @dtzar Any thoughts on the following proposal, if you all agree, I can issue a PR to update the sign CLI document to fix the following issues and add more examples as well.

Since TSA based timestamping will not be available in rc.1, I propose to remove the following option from notation sign command:
-e, --expiry duration         expire duration
-t, --timestamp string        timestamp the signed signature via the remote TSA

Currently after a successful sign, the signature is pushed to the remote registry by default, but the signature is also stored as a file in directory $HOME/cache/notation. Do we have a valid use case to store the signature locally? If not, I suggest to remove signature cache from rc.1, and removing notation cache command which is used to manage the local signatures

The same question on option --push-reference different remote to store signature. If there is no valid use case to push a signature to a different remote for storage, I suggest removing this option as well. We can use ORAS CLI/API to copy container images and signatures from one registry to another registry, which is more secure.

as discussed in the meeting on 9/19

"-e" option should stay for RC-1. "-t" option can be removed for the RC-1
Lets remove "notation cache".. , if "cache" is removed, there is no need for "notation push/pull" commands?
The notation push and pull were created to push and pull signatures from and to cache. Additionally, there are no near term use cases for "Cache" in RC-1, so we can remove it as well.

Agree with Samir's three bullets.  expiry wouldn't really change as it is just a user-defined timestamp.
As far as --push-reference I'd also agree to remove.
With cache - we should remove the notation cache command for RC.1.  That said - my guess is that when we enable local signing post RC.1, we would want/use the actual signature local so we could use that code.  I'd check with the developers on their thoughts there.  If we would use that code, then I'd leave notation code there which leaves the signature itself on local storage.

Closed since PR #341 merged


I will upload a file specifically for 1.16.3


Implement Connect buttons on the User Resource card

[x] Connect button for User Resources and Services supporting it.

Pushing - [ ] Additional actions for User Resources to it's own issue. Will require some more thought.


Fix: clear orientation listener on close

What

This PR cleans android orientation listener on camera session close.
If this is not done, the events are still fired and they accumulate until you kill the app.
Changes

Added a clearListeners functions in the OrientationManager which is then called when CameraSession.close() is called.
Tested on

Samsung Galaxy tab active4 pro. Android 14.
Related issues

Thanks for handling the requested changes


Duplicate lemma about product uniformity

Lemmas
https://github.com/leanprover/mathlib/blob/e74ff76ccac882018e9c1fd70772fd7c88ae06f5/analysis/topology/uniform_space.lean#L1482-L1485
and
https://github.com/leanprover/mathlib/blob/e74ff76ccac882018e9c1fd70772fd7c88ae06f5/analysis/topology/uniform_space.lean#L1535-L1539
have the same statement, although one proof is shorter than the other.
Obviously I can open a PR deleting one of them if you want, but maybe you want to use the opportunity to make some extra checks and reorganization.

closed with e67f2adfd22efafc7e0bfe9190583a3716bde495


Backport: Sync releases table with tags on push and for mirrors (#2459)

Sync releases table with tags on push and for mirrors

Code style fixes

Fix api to return only releases

Optimize release creation and update
Minimize posibility of race conditions

Fix release lower tag name updating

handle tag reference update by addionally comparing commit id

backport from #2459

LGTM

Make LG-TM work

@lafriks Tested and it does exactly the same as on master ;-)

@lafriks Can you do a force push to retsart drone build?

I will after other PR is merged as I will need to resolve conflicts then

Trusted LGTM


Geolocation Fails

Electron version: 1.3.3
Operating system: Windows 10

Hi,
I have issue with resolving of geocoordinates
navigator.geolocation.getCurrentPosition returns with following error
PositionError {code: 2, message: "Network location provider at 'https://www.googleapis.com/' : Returned error code 403."}

electron-prebuilt is just the npm module. Issues with electron should be opened at electron/electron.

@m0n01i7h see https://github.com/electron/electron/pull/7276


Account for age in estimates

Is your feature request related to a situation you're trying to understand with microCOVID? Please describe.
A child going to school.
Describe the solution you'd like
The estimate should possibly be 4x lower than it is, given my very limited data.
Relevant Research or Citations
I did a fairly conservative analysis of the risk of an average child contracting COVID at school in my province, and found that if the site's estimate was anywhere near right, cases would be exploding in schools. In fact, they're slowly decreasing. The analysis follows.
Note that I'm using demographic COVID rate data from this tweet, but since rates are small enough, the only thing that really matters is that R0 is apparently less than one.
Because I'm aiming to show that microCOVID is providing an overestimate, I'm going to input a set of assumptions that will tend to make it estimate low. They are, in rough descending order of how generous I think they are:

Children can only contract COVID from school.
Everyone is silent.
Students 6+ feet apart (most classrooms here are closer)
Everyone properly wearing thick, snug cloth masks.
20 people in 5 meters (most classes here are larger).
20 hours of indoor class time a week (my daughter's is closer to 25)
The teacher doesn't exist.
Ventilation isn't exceptionally good.
Nobody vaccinated (kids can't be here, yet).
189/100k cases from the last week reported, 9.1% of tests come back positive, no increase from last week to this week (I'm not sure this matters much, since I'll compare the result to this number). This gives reported prevalence 0.19%, adjusted prevalence 0.47%; I assume that's for the last 10 days.

microCOVID's estimate is a 1.4% chance of contracting COVID, with a confidence interval of (0.47%, 4.2%).
Not every child faces that risk. A recent estimate touted about a 6% homeschooling rate, which means that 94% of students are exposed to at least this level of risk. Let's round it down to 90%, to account for students in smaller classrooms, or hypothetical schools with exceptional ventilation.
This gives the average Albertan child in that age range a 1.3% chance of catching COVID every seven days, with a confidence interval of (0.42%, 3.8%). This is with assumptions that are extremely generous in lowering the probability.
microCOVID's "adjusted prevalence," if I readjust it to be for 7 days instead of 10, is 0.33%. But cases are trending slowly down in Alberta, including in that age range, which means that the actual prevalence must be higher than the actual chance of contracting the disease.
Conclusion
If we give microCOVID information about children attending school, being careful to make assumptions that lower the risk of contracting the illness (including the assumption that children can't contract COVID anywhere else), the lower bound of microCOVID's confidence interval is around 20% too high, and microCOVID's best estimate is around 3.9 times too high.
I haven't done this analysis for other areas, but those assumptions (except possibly for ventilation) should be pretty conservative for most schools, so it shouldn't be too hard to check. I hope this was a helpful analysis without any issues that render it useless.

The way I've managed this is to add a "vaccine" on the internal activity page that says <10 and has a .5 multiplier because I think I'd seen a few places that young kids seemed to be about 50% as likely to contract Covid in the same situation. It feels like the risk seems similar to what we are seeing in terms of the actual prevalence. Another way to do it if your school district is posting district-level case information for students is to make that a custom location which lets you use the prevalence in schools vs. the prevalence in the larger community.


Fix jitpack.yml

Modified jitpack.yml to use Jitpack's built in jdk property.
Also removed the ENVIRONMENT environment variable because it was specific to Apoli.

Closed because the relevant change was already made


NDRS-706: Provide JSON versions of Contract and ContractPackage

REF: https://casperlabs.atlassian.net/browse/NDRS-706
Added Contract and ContractPackage struct to a new contracts.rs module inside the json compatibility module.

Closing PR. Moved to: https://github.com/CasperLabs/casper-node/pull/772

Closing PR. Moved to: https://github.com/CasperLabs/casper-node/pull/772


Issue with kubelet

This is a...

[ ] Feature Request
[x ] Bug Report

Problem:
While Running any Container on my Machine I see errors as below
pod_workers.go:182] Error syncing pod 978265f7-b
helpers.go:468] PercpuUsage had 0 cpus, but the
remote_runtime.go:115] StopPodSandbox "94f7ad2e4
kuberuntime_manager.go:780] Failed to stop sandb
kuberuntime_manager.go:580] killPodWithSyncResul
pod_workers.go:182] Error syncing pod 978265f7-b
When I checked kubelet via systemctl status command see errors as
Oct 27 21:50:54 kuber-poc-app2 kubelet[30324]: E1027 21:50:54.520513   30324 helpers.go:468] PercpuUsage had 0 cpus, but the actual number is 2; ignoring extra CPUs
Oct 27 21:51:08 kuber-poc-app2 kubelet[30324]: E1027 21:51:08.510483   30324 remote_runtime.go:115] StopPodSandbox "023d1954c4b29da2ac77b8e8c14284f4b6219f8e7b6f849318fff13a7d3b7738" from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
Oct 27 21:51:08 kuber-poc-app2 kubelet[30324]: E1027 21:51:08.510591   30324 kuberuntime_manager.go:780] Failed to stop sandbox {"docker" "023d1954c4b29da2ac77b8e8c14284f4b6219f8e7b6f849318fff13a7d3b7738"}
Oct 27 21:51:08 kuber-poc-app2 kubelet[30324]: E1027 21:51:08.510633   30324 kubelet_pods.go:1036] Failed killing the pod "nginx-deployment-569477d6d8-92gsl": failed to "KillPodSandbox" for "4310e420-bb5f-11e7-aadb-00505601302d" with KillPodSandboxError: "rpc error: code = DeadlineExceeded desc = context deadline exceeded"
Oct 27 21:51:08 kuber-poc-app2 kubelet[30324]: E1027 21:51:08.510720   30324 remote_runtime.go:115] StopPodSandbox "d24d82cacc5e36b429aebc1853c808db944bb893d5a2eb00b6d7c3af581c0246" from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
Proposed Solution:
Not Sure
Page to Update:
http://kubernetes.io/...

Type          Status
Initialized   True
Ready         False
PodScheduled  True
Volumes:
default-token-dznl8:
Type:       Secret (a volume populated by a Secret)
SecretName: default-token-dznl8
Optional:   false
QoS Class:      BestEffort
Node-Selectors:
Tolerations:    node.alpha.kubernetes.io/notReady:NoExecute for 300s
node.alpha.kubernetes.io/unreachable:NoExecute for 300s
Events:
FirstSeen     LastSeen        Count   From                    SubObjectPath   Type            Reason                  Message

12m           12m             1       default-scheduler                       Normal          Scheduled               Successfully assigned nginx-deployment-569477d6d8-zrk8d to kuber-poc-app3
12m           12m             1       kubelet, kuber-poc-app3                 Normal          SuccessfulMountVolume   MountVolume.SetUp succeeded for volume "default-token-dznl8"
8m            8m              1       kubelet, kuber-poc-app3                 Warning         FailedCreatePodSandBox  Failed create pod sandbox.
8m            2m              4       kubelet, kuber-poc-app3                 Warning         FailedSync              Error syncing pod
8m            1m              4       kubelet, kuber-poc-app3                 Normal          SandboxChanged          Pod sandbox changed, it will be killed and re-created.

[root@kuber-poc-app2 ~]# kubeadm version
kubeadm version: &version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.1", GitCommit:"f38e43b221d08850172a9a4ea785a86a3ffa3b3a", GitTreeState:"clean", BuildDate:"2017-10-11T23:16:41Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
[root@kuber-poc-app2 ~]#
[root@kuber-poc-app1 nginx_kube]# kubectl version
Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.0", GitCommit:"d3ada0119e776222f11ec7945e6d860061339aad", GitTreeState:"clean", BuildDate:"2017-06-29T23:15:59Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.2", GitCommit:"bdaeafa71f6c7c04636251031f93464384d54963", GitTreeState:"clean", BuildDate:"2017-10-24T19:38:10Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
[root@kuber-poc-app1 nginx_kube]# cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)
[root@kuber-poc-app1 nginx_kube]#

Oct 28 00:48:32 kuber-poc-app3 kubelet: W1028 00:48:32.362598   10444 docker_sandbox.go:343] failed to read pod IP from plugin/docker: NetworkPlugin cni failed on the status hook for pod "nginx-deployment-569477d6d8-n7pls_default": Unexpected command output Device "eth0" does not exist.
Also see this into /var/log/messages

kubelet: weave-cni: error removing interface "eth0": Link not found

It worked when both kubelet and docker forced to use same cgroup Issue #54910


Support float  arguments to  to_timestamp function

Is your feature request related to a problem or challenge?
In https://github.com/apache/arrow-datafusion/pull/7844 we are (about to) change to_timestamp to be aligned with postgres by taking seconds instead of milliseconds.
To fully align with postgres, we should also add support double (Float64) arguments as well
The postgres documentation for to_timestamp is here
Describe the solution you'd like
I would like the to_timestamp function to also support  Float64 point arguments:
For example, (not the 1.1 at the end of the timestamp)
willy=# select to_timestamp(1.1);
       to_timestamp
--------------------------
 1970-01-01 08:00:01.1+08

Describe alternatives you've considered
No response
Additional context
Note the string / two argument version of to_timestamp is covered by https://github.com/apache/arrow-datafusion/issues/5398

Thanks @spaydar  -- note that we haven't merged https://github.com/apache/arrow-datafusion/pull/7844 yet, so you probably would need to start from that branch if you want to work on this prior to @comphead merges

Is this still up for grab?

I'm still working on this; it's been a bit more involved than I expected. Is this blocking other issues?

No blocking issues as of now, rather this is one of the missing pieces for timestamp


Fix/remove basenames modal

What changed? Why?

removed basenames modal from web and docs

Notes to reviewers
How has it been tested?
locally

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


Error when creating a new calendar: Exception: You do not have access to the calendar

Feb 9, 2024, 12:43:47 PM	Info	Updating all sync triggers
Feb 9, 2024, 12:43:54 PM	Error	Exception: You do not have access to the calendar.
    at create(Code:673:18)
    at updateSyncTriggers(Code:1931:95)
    at createCalendar(Code:1474:76)
    at onSubmitCalendarForm(Code:1174:92)

Also when trying to update it. But I do have access to the Google Calendar instance 🤔


CSharp intellisense occasionally fails with an exception

I couldn't get a consistent repro but it happens occasionally when I try to type DateTime.Now in line 5.

I don't get the expected CSharp intellisense and the following exception is thrown
Failed to synchronize document '/Users/ajbaaska/Github/temp/RazorVSCodeTest/Pages/Index.cshtml__virtual.cs': "System.ArgumentException: An item with the same key has already been added. Key: /Users/ajbaaska/Github/temp/RazorVSCodeTest/Pages/Index.cshtml__virtual.cs
  at System.Collections.Generic.Dictionary`2[TKey,TValue].TryInsert (TKey key, TValue value, System.Collections.Generic.InsertionBehavior behavior) [0x000ad] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Collections.Generic.Dictionary`2[TKey,TValue].Add (TKey key, TValue value) [0x00000] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at OmniSharp.Roslyn.BufferManager.TryAddTransientDocument (System.String fileName, System.String fileContent) [0x00101] in <87f0b9e659494985a2da11f6102d4a4b>:0
  at OmniSharp.Roslyn.BufferManager+<UpdateBufferAsync>d__7.MoveNext () [0x0028c] in <87f0b9e659494985a2da11f6102d4a4b>:0
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at OmniSharp.Roslyn.CSharp.Services.Buffer.UpdateBufferService+<Handle>d__2.MoveNext () [0x00072] in <7e8bc09baf3d4b52839d77f569cbdb5f>:0
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () [0x00000] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at OmniSharp.Endpoint.EndpointHandler`2+<HandleSingleRequest>d__18[TRequest,TResponse].MoveNext () [0x000e4] in <3c50833d933444f18e15117ec743f98f>:0
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () [0x00000] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at OmniSharp.Endpoint.EndpointHandler`2+<Process>d__16[TRequest,TResponse].MoveNext () [0x0024b] in <3c50833d933444f18e15117ec743f98f>:0
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () [0x00000] in <0f9df4881040473f9da7cf6c2e2cb8c3>:0
  at OmniSharp.Stdio.Host+<HandleRequest>d__13.MoveNext () [0x000e7] in <33e072d1bf1148378944302c3cd641c2>:0 "

VS Code version: 1.28.2
Omnisharp version: 1.17.0-beta7
OS: MacOS Mojave
Project template: dotnet new razor
dotnet SDK version: 2.2.100-preview2-009404

This is probably what was mentioned in known issues as Leaving Razor files open for a significant period of time results in loss of Razor C# tooling on macOS. I tested how long it takes for this exception to appear and it usually happens after 3 minutes of the document being open.

I hit something similar to this on Windows:
Failed to synchronize document '/c:/Users/daroth/Desktop/WebApp3/WebApp4/Pages/About.cshtml__virtual.cs': "System.ArgumentException: An item with the same key has already been added.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at OmniSharp.Roslyn.BufferManager.TryAddTransientDocument(String fileName, String fileContent)
   at OmniSharp.Roslyn.BufferManager.<UpdateBufferAsync>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Roslyn.CSharp.Services.Buffer.UpdateBufferService.<Handle>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Endpoint.EndpointHandler`2.<HandleSingleRequest>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Endpoint.EndpointHandler`2.<Process>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Stdio.Host.<HandleRequest>d__13.MoveNext()"

https://github.com/OmniSharp/omnisharp-roslyn/commit/de5f66f7533623fbd72005ad52375fb0707a36a2


[WIP] Add batch_events HTTP API endpoint

This adds the /apps/[app_id]/batch_events endpoint.
WIP: because this add some validation I would first like to be reviewed or nudged in doing it another way if that's better/more acceptable. (no tests yet too)
I am using a "custom" JsonResponse to stay as close a possible to the Pusher API response and only add an extra field in the response with the validation errors.
Pusher responds with something like the response below. As far as I can tell they only report the first error and does not send any remaining valid events, so I matched that here.
{
    "body": "Missing required parameter: channel\n",
    "status": 400,
}

I also want to add this validation to the TriggerEventController if the way of doing this validation is correct or we land on a good validation method.

@stayallive Can you rebase?

@rennokki, there is still a question open for the direction of this PR.

WIP: because this add some validation I would first like to be reviewed or nudged in doing it another way if that's better/more acceptable. (no tests yet too)

Also this was almost 2 years ago so it might take me a bit to find the time to work on this, are you taking over some/all maintenance for this project?

I started maintaining the project since this morning, so I am just looking after some of the PRs that went stale. The project will likely go further with more major releases since there are a lot of breaking changes and code formatting to be done.
The only thing I can say is that the idea is good, as long as it complies with this specification: https://pusher.com/docs/channels/library_auth_reference/rest-api#post-batch-events-trigger-multiple-events-
Regarding the tests & validation, we'll figure it out. :)

I might revisit this for 2.x once it's stable (if not already implemented).

Can you create an issue with this current PR's body so we can mark it as enhancement and taking care of it later?

No problem, done: #529.


Page not found: cannot find local project src code.

in Getting Started of Tutorial section, at Handling Http requests, in the text 'You can run this application locally by grabbing the source code from here.' the link is not broken.it need update.

This is essentially a dup issue asking about documentation.


Fixed grammar

Not sure why you closed this.
e.g. is a Latin acronym for Exempli Gratia, which means "for example".
In the document it says "for eg" which doesn't make sense, but could be fixed in one of 2 ways:

replace "for eg" with"e.g."
replace eg with example, giving "for example".

I opted for the second one.


[BUG] scorecard-action

2023/12/14 18:21:00 error sending scorecard results to webapp: http response 400, status: 400 Bad Request, error: {"code":400,"message":"workflow verification failed: imposter commit: 03e7845b7bfcd5e7fb63d1ae8c61b0e791134fab does not belong to github/codeql-action/upload-sarif, see https://github.com/ossf/scorecard-action#workflow-restrictions for details."}

Closed by https://github.com/konstruktoid/ansible-role-hardening/pull/451


feat: adds VVP Flow to architecture section

Description

Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[ ] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[ ] Copyright and license header are present on all affected files

LGTM, please rebase as I just merged two new PRs. You shouldn't get any conflicts.
NOTE: There seems to be an issue when using the http version of the remote, so please use the ssh version. If it's already setup you can change the url:
git remote set-url upstream git@github.com:eclipse-tractusx/managed-identity-wallet.git

or set it up
git remote add upstream git@github.com:eclipse-tractusx/managed-identity-wallet.git

afterwards you can run:
# make sure you're on your PR branch
git fetch upstream

# make sure you're at the tip by visually inspecting the output of git log:
git log --oneline --graph -5

# all is good, then run:
git rebase upstream/develop
git push -f


login: Support basic auth login via API creds

Required for all PRs:

[ ] README.md updated (if needed)
[ ] Passes gofmt and golint

cc @raazcrzy

@raazcrzy I looked at the accounts api docs and made a curl request like this which gave me a 200 OK
curl -u <my-api-creds> https://accapi.appbase.io
but when I tried to replicate that in code I couldn't fetch the user email and got the error user not logged in despite getting a 200 code
Is the API endpoint that I am using for login correct?

@palash25, requests with basic auth attached should work just fine. Are you sure, you are passing the basic auth on subsequent requests and not trying to use accapi-session to authenticate the requests?


[dca] Introduce the Cluster Tagger

What does this PR do?
The Cluster Tagger is just a fancy name for a collection of components we already have, now available also in the Cluster Agent. Here's what's included in this PR:

It enables the workloadmeta to run in the DCA. A few supporting changes were made: workloadmeta.GetGlobalStore no longer creates a store by itself, and workloadmeta.CreateGlobalStore takes up that responsibility. It takes a catalog of collectors to run, instead of defaulting to all available collectors. We also have two catalogs available: workloadmeta.NodeAgentCatalog and workloadmeta.ClusterAgentCatalog.
It introduces a new workloadmeta collector, kubeapiserver, responsible for fetching data about pods and storing them as our well known workloadmeta.KubernetesPod already in use everywhere. The most effective way we found to do this was to use a Reflector, which is a funny name for a component that lists then watches a resource.
Enables our good old tagger in the DCA, with zero changes 😄
Changes the remote tagger to be able to point to a different endpoint. This is needed so the Cluster Checks Workers can point the remote tagger to the DCA. Enabling the tagger server in the DCA is added in #13844. This touches basically all agent binaries unfortunately, and is basically what teams other than Container Integrations need to review. I'm hoping that the components work will reduce the need for this types of changes in the future, since other components will just get an initialized instance automagically injected in, instead of having to know anything about remote.Options.

Since these are all reusable components, data flows with very little effort. The kubeapiserver collector uses known types, so as soon as the tagger is enabled, it can start collecting pod tags immediately. Since we're using our standard tagger, it can be very easily exposed via gRPC in the DCA with the same server code we use in the node agents as well. Since that's a known interface, cluster check runners can just point the remote taggers there, and all of a sudden we have pod tags replicated to all components, ready to be used with a simple tagger.Tag.
Motivation
Beyond general availability of pod tags in the Cluster Agent and Cluster Workers, the Cluster Tagger is meant to initially power two specific use cases (not part of this PR): tagging of events generated by the kubernetes_apiserver check, and metrics generated by the kubernetes_state_core check. Those two are among of the most requested features in container-land.
Additional Notes
Note for reviewers: this PR also includes the two commits from #13844, where we enabled the remote tagger in the cluster check workers. I'll rebase this PR on that once it's merged.
A few other implementations were considered for this feature. They're detailed below, together with the reasons for not choosing them over the one put forward in this PR.
Using a Pod Informer
The most obvious way to consume pod information from the API server is to use an informer. It watches all changes to the pod objects, storing the full objects into its own internal storage, and allowing event handlers to be attached to changes in those objects.
Its main advantage is that it's a popular way of doing things, requires very little setup, and Just Works(tm). The main problem is memory usage. Below is a benchmark showing memory usage of the DCA running in a cluster with ~2.5k pods:

Compared to the implementation proposed in this PR, it uses about ~100MB more, just from the data living inside the informer alone. Even if we were to assume that this increase is acceptable, it does not show the cost of the full solution. Being able to have tags extracted from the informer would also entail either of the two following paths:

Implement a workloadmeta collector to store the data coming from the informer events, so we can reuse pkg/tagger/local.Tagger with no changes. This would cause a further ~150MB increase for this particular cluster due to the duplicated data, and is prohibitive in bigger clusters.

Implement a completely new tagger collector that is able to consume k8s.io/api/core/v1.Pod objects. While this does not incur a large memory penalty beyond the tags themselves, is a good bit of code to write and maintain, especially since it's supposed to be an exact duplicate of the existing collector in the tagger.

Using a Pod Lister
Since the biggest issue with using a pod informer is either the duplication or excessive data being held in memory, a natural solution is to use a pod lister, periodically calling the API Server for a list of all pods, and storing them in workloadmeta. Its only advantage is being relatively simple ("just" a method call in a loop), but in the end this was only briefly considered and discarded due to the following reasons:

We'd need to diff the current pods in workloadmeta vs. the list coming from the API server. While that's somewhat trivial, it is a loss compared to using an informer, where we only need to handle events.
While less data would be kept in memory (the full pod data only for the duration of the workloadmeta pull, and the extracted data afterwards), it would require much more data to travel over the network since we'd get the full working set on every pull, which can easily be several megabytes.
Any pods that started and finished between pulls (aka short-lived pods) would be completely invisible to workloadmeta, and therefore would have no tags associated to them.

These issues could be fixed by careful use of resourceVersion parameters and watches, and that's the thought process that led us to use the Reflector that does exactly that. There are some relevant docs that state as much.
Getting tags or pods directly from node agents
This was our first idea on how to implement this. We had planned to benchmark pull from agents vs. push to DCA, but several disadvantages made us discard the whole idea on principle. I can't think of a clear advantage to this approach, and the list of downsides is large.

In a big cluster, that's a lot of network traffic going all over the place. Pushing to the DCA means being able to support thousands of requests, and pulling from the node agents is probably more efficient but means exposing them to the cluster, which is not something we currently do and has security implications.
There are a lot more potential points of failure. An agent might fail to push its data, or the DCA might not be able to reach the agent for any amount of time, for all kinds of random reasons.
Similar to the pod lister solution, this one has the potential to miss short-lived pods. It's possible to store updates and consolidate them into batches instead of consuming lists directly, but that's a feature that does not exist in workloadmeta nor the tagger. Those batches also need to be pruned in failure scenarios (DCA failing to pull, or unreachable from the agent) to prevent runaway memory usage.
Dealing with several DCA replicas requires a lot more thinking. Does each agent push to all DCAs? Just the leader? How does the leader replicate data to the replica? Or does it even have to?

Possible Drawbacks / Trade-offs

Since the cluster tagger needs to collect information from all pods in the cluster, big clusters will of course consume a lot of memory. In a cluster with ~15k pods, we saw an increase of about 500MB in memory consumption. This is also heavily dependent on labels and annotations on top of those pods, since that's data that we have to collect for the complete set of tags to work, and they may be relatively large string blobs. Due to this, the cluster tagger sits behind a feature flag that's disabled by default for now.

In clusters with a lot of pod churn, there is also a small but noticeable increase in CPU usage as well. During testing, we noticed that this increase is higher with the workloadmeta+reflector solution we're going with compared to using an informer, which suggests possible optimizations to be made in workloadmeta. Given that the increase was small, we're not considering it a blocker for this PR. The graph below shows CPU usage and has the same DCA instances as the one I showed earlier in this PR:

Each DCA replica will have its own full copy of workloadmeta and tagger data, regardless of leadership status. This results in some waste, but does simplify implementation by a lot, since we don't have to fill or purge data when leadership status changes. It also simplifies clients, since they don't have to be redirected to the leader, or restarting the remote tagger when leadership status changes. Load-balancing is not terribly important due the usual small number of cluster check runner replicas, but is taken care of by the Kubernetes Service in front of the DCA replicas anyway.

To save memory, we do not store any data about containers. We also have a single use case for container-level tags in a cluster context in KSM, but those metrics are also available from the kubelet check coming from the node agents, so we find this to be an acceptable omission. This is very easy to change should we ever need it in the future.

Describe how to test/QA your changes
The DCA binary currently does not have a tagger-list or workload-list command, which is due to be implemented soon, so it's hard to QA this directly. But since it propagates tags (which are the bits we actually care about in the context of this PR) to the cluster check runners, running agent tagger-list on them is a good way to ensure that tags for all pods in the cluster are present. Just remember to set cluster_agent.collect_kubernetes_tags to true in the cluster agent first!
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

Rebased on top of main to fix conflicts.


[Package Issue]: Fortinet.FortiClientVPN very outdated

Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Other
Brief description of your issue
Winget has FortiClient VPN version <IP_ADDRESS>0 (August 2019). The latest version at the time of writing is 7.0.2 (October 2021).
Steps to reproduce
Doesn't apply
Actual behavior
Doesn't apply
Expected behavior
Doesn't apply
Environment
Doesn't apply

Screenshots and Logs
No response

@itsTyrion Can you provide the download links to the new version’s installer?

https://links.fortinet.com/forticlient/win/vpnagent

https://links.fortinet.com/forticlient/win/vpnagent

Looks like they moved to an interactive only installer; I can't seem to figure out the TOS acceptance switch

Looks like they moved to an interactive only installer; I can't seem to figure out the TOS acceptance switch

Not quite, they moved to "online installer downloads offline installer and executes that".
%LocalAppData%\Temp\FortiClientVPN.exe is the full path of what's downloaded.
If you run THAT with .\FortiClientVPN.exe /quiet /norestart, you can do a non-interactive install

It is impossible to get the URL of the offline installer from the online installer because it fetches the files from encrypted API. 😕

Whhhyyyy


Dart -> Engine roll failing on dart2wasm compilation failures

Starting in https://github.com/flutter/engine/pull/53168
In https://dart.googlesource.com/sdk.git/+log/53c41325c29f..411ddd5acfab there are a few dart2wasm commits from @osa1 and @mkustermann
Unfortunately the logs don't have much info: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8746163314286567409/+/u/compile_bundle_dart2wasm-skwasm-ui/stdout
FYI @eyebrowsoffire

It turns out the issue is this: https://dart-review.googlesource.com/c/sdk/+/369020
In development, the web engine is a package (package:ui) and we run the unit tests against that package. Disallowing the wasm:import and wasm:export pragmas in user code therefore breaks all our engine unit tests. We probably need to have package:ui be allowlisted to use these. Or maybe introduce a flag we can use that allows user code to use these pragmas.

A revert ( https://dart-review.googlesource.com/c/sdk/+/369500 ) has been submitted.

The revert unblocked the roller. Closing.


Deployment is getting stuck

Jobs log :
Deploying packages to http://dev00:7120/crx/de/../..
Deploying /opt/app/workload/jenkins/ecms/data/jobs/testDeploy/workspace/aem-upperfunnel-apps-1.0.32-SNAPSHOT.zip to http://dev00:7120/crx/packmgr/index.jsp#/etc/packages/Upperfunnel/aem-upperfunnel-apps-1.0.32-SNAPSHOT.zip
After this it just gets stuck and there is nothing in Jenkins log as well.
I checked the connection from job configuration and it is successfull!!
I am using plugin version 1.5.3
AEM is 6.1 SP1

Hi @poojasharma6 ,

was the plugin working for you before installing 1.5.3, or did you recently upgrade?
what version of Jenkins are you using, and what are the installed versions of Credentials, SSH Credentials, and Bouncycastle API Plugins ?
What is the size of aem-upperfunnel-apps-1.0.32-SNAPSHOT.zip ?
Are you connecting to your AEM instance through a reverse proxy like Apache, an F5, or an ELB?

What is the result of running this curl command? (Please redact any credentials or Authorization headers before pasting the output)
curl -u <user>:<pass> -v -Fcmd=delete -Fjcr:primaryType=adamcin:NoSuchType http://dev00:7120/crx/packmgr/service/exec.json/adamcin/no-such-package-1.0.0.zip
I expect to see something similar to the following:
$ curl -u admin:admin -v -Fcmd=delete -Fjcr:primaryType=adamcin:NoSuchType http://localhost:4502/crx/packmgr/service/exec.json/adamcin/no-such-package-1.0.0.zip
*   Trying ::1...
* connect to ::1 port 4502 failed: Connection refused
*   Trying <IP_ADDRESS>...
* Connected to localhost (<IP_ADDRESS>) port 4502 (#0)
* Server auth using Basic with user 'admin'
> POST /crx/packmgr/service/exec.json/adamcin/no-such-package-1.0.0.zip HTTP/1.1
> Host: localhost:4502
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.49.1
> Accept: */*
> Content-Length: 266
> Expect: 100-continue
> Content-Type: multipart/form-data; boundary=------------------------facded5317e05af0
>
< HTTP/1.1 100 Continue
< HTTP/1.1 200 OK
< Date: Tue, 18 Oct 2016 23:28:51 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 36
< Server: Jetty(9.2.9.v20150224)
< X-Powered-By: Jetty(9.2.9.v20150224)
<
* Connection #0 to host localhost left intact
{"success":false,"msg":"no package"}

This is what i got:
[enabler@dev00 workload]$ curl -u user:pass -Fcmd=delete -Fjcr:primaryType=adamcin:NoSuchType http://dev00:7120/crx/packmgr/service/exec.json/adamcin/no-such-package-1.0.0.zip
{"success":false,"msg":"no package"}

@poojasharma6 that's the expected response, but I need the answers to the other questions and I also need you to run that curl command with "-v" to see the verbose output.

Apologies, I didn't see your response properly. Sorry for that.
Here it is:

This is the first time I am using this plugin so 1.5.3 is the only version i have used
Jenkins: 2.19.1
Credentials: 2.1.6
SSH Credentials: 2.4
Bouncycastle API: 2.16.0
Package Size: 690.4 KB
reverse proxy like Apache, an F5, or an ELB? No
Curl -v output -

`$ curl -u admin:pass -v -Fcmd=delete -Fjcr:primaryType=adamcin:NoSuchType http://zlt07765.vci.att.com:7120/crx/packmgr/service/exec.json/adamcin/no-such-package-1.0.0.zip

About to connect() to zlt07765.vci.att.com port 7120 (#0)
Trying <IP_ADDRESS>... connected
Connected to zlt07765.vci.att.com (<IP_ADDRESS>) port 7120 (#0)
Server auth using Basic with user 'admin'

POST /crx/packmgr/service/exec.json/adamcin/no-such-package-1.0.0.zip HTTP/1.1
Authorization: Basic YWRtaW46Q21zRGV2I0FyY2g=
User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.18 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
Host: zlt07765.vci.att.com:7120
Accept: /
Content-Length: 266
Expect: 100-continue
Content-Type: multipart/form-data; boundary=----------------------------aeab810ba693

< HTTP/1.1 100 Continue
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: application/json;charset=utf-8
< Content-Length: 36
< Date: Fri, 21 Oct 2016 15:00:12 GMT
<

Connection #0 to host zlt07765.vci.att.com left intact
Closing connection #0
{"success":false,"msg":"no package"}`

Since this is working fine for publish instance, i tried to dig out the reason for why it is failing for author
if I give just the base URL in the plugin.
If I give baseURL followed by /crx/de/../.. , plugin test connection returns successfull - but still deployment hangs.
I found out that we are using CSP login (somewhat like ldap integration) for both author and publish but it is used somewhat differently for author.
However, if i do installation through maven or curl on command line - passing admin credentials, it works perfectly fine. It fails  when using the plugin :(

Non-standard authentication schemes can definitely cause issues. Can you provide more detail:

Is it SSO based, like SAML, or is Oak configured to pass credentials to a backend CSP connection?
are you able to login as admin through CRX de lite?

It sounds like the SSO auth handler hijacks the /crx/de request, and may also be hijacking the post to /crx/j_security_check.
Can you try issuing the following curl command and paste the verbose output?
curl -v -dj_username=<user> -dj_password=<pass> -dj_validate=true -d_charset_=utf-8 http://zlt07765.vci.att.com:7120/crx/j_security_check

Here is the output:
'$ curl -v -dj_username=admin -dj_password=pass -dj_validate=true -d_charset_=utf-8 http://zlt07765.vci.att.com:7120/crx/j_security_check

About to connect() to zlt07765.vci.att.com port 7120 (#0)
Trying <IP_ADDRESS>... connected
Connected to zlt07765.vci.att.com (<IP_ADDRESS>) port 7120 (#0)

POST /crx/j_security_check HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.18 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
Host: zlt07765.vci.att.com:7120
Accept: /
Content-Length: 71
Content-Type: application/x-www-form-urlencoded

< HTTP/1.1 302 Moved Temporarily
< Server: Apache-Coyote/1.1
< Location: https://www.e-access.att.com/empsvcs/hrpinmgt/pagLogin/?retURL=http%3A%2F%2Fzlt07765.vci.att.com%3A7120%2Fcrx%2Fj_security_check&sysName=AuthForCQ
< Content-Length: 0
< Date: Mon, 24 Oct 2016 17:56:05 GMT
<

Connection #0 to host zlt07765.vci.att.com left intact
Closing connection #0
'

Here is the output:
'$ curl -v -dj_username=admin -dj_password=pass -dj_validate=true -d_charset_=utf-8 http://zlt07765.vci.att.com:7120/crx/j_security_check

About to connect() to zlt07765.vci.att.com port 7120 (#0)
Trying <IP_ADDRESS>... connected
Connected to zlt07765.vci.att.com (<IP_ADDRESS>) port 7120 (#0)

POST /crx/j_security_check HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.18 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
Host: zlt07765.vci.att.com:7120
Accept: /
Content-Length: 71
Content-Type: application/x-www-form-urlencoded

< HTTP/1.1 302 Moved Temporarily
< Server: Apache-Coyote/1.1
< Location: https://www.e-access.att.com/empsvcs/hrpinmgt/pagLogin/?retURL=http%3A%2F%2Fzlt07765.vci.att.com%3A7120%2Fcrx%2Fj_security_check&sysName=AuthForCQ
< Content-Length: 0
< Date: Mon, 24 Oct 2016 17:56:05 GMT
<

Connection #0 to host zlt07765.vci.att.com left intact
Closing connection #0
'

Here is the output:
'$ curl -v -dj_username=admin -dj_password=pass -dj_validate=true -d_charset_=utf-8 http://zlt07765.vci.att.com:7120/crx/j_security_check

About to connect() to zlt07765.vci.att.com port 7120 (#0)
Trying <IP_ADDRESS>... connected
Connected to zlt07765.vci.att.com (<IP_ADDRESS>) port 7120 (#0)

POST /crx/j_security_check HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.18 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
Host: zlt07765.vci.att.com:7120
Accept: /
Content-Length: 71
Content-Type: application/x-www-form-urlencoded

< HTTP/1.1 302 Moved Temporarily
< Server: Apache-Coyote/1.1
< Location: https://www.e-access.att.com/empsvcs/hrpinmgt/pagLogin/?retURL=http%3A%2F%2Fzlt07765.vci.att.com%3A7120%2Fcrx%2Fj_security_check&sysName=AuthForCQ
< Content-Length: 0
< Date: Mon, 24 Oct 2016 17:56:05 GMT
<

Connection #0 to host zlt07765.vci.att.com left intact
Closing connection #0
'

@poojasharma6 I've uploaded version 1.5.4 that should be available this evening with the ability to enable Preemptive Auth for Base Url patterns. Please upgrade and then navigate to Manage Jenkins -> Configure System -> section "CRX Content Package Deployer - HTTP Client", and enter "http" for the "Preempt Login for Base URLs". Then try your build again. You should see following message in the execution log:
[ALERT] Preemptive basic auth enabled for URL http://zlt07765.vci.att.com:7120

@poojasharma6 Please upgrade to version 1.6 for this feature. It now works using regular expressions and has been tested on a master-slave jenkins installation.

Hi @adamcin ,
I upgraded to 1.6 and as suggested by you, used Preemptive basic auth for HTTP but still deployment is getting stuck
I did not get any alert in job console logs like you indicated. That is when i went back and looked at the jenkins configuration for plugin and they are not there.
I try adding the configuration again and save but it vanishes.

@poojasharma6 I see my mistake. Version 1.6.2 is on its way.

Let me know when its available please

@poojasharma6 It's available. Please upgrade and let me know how it goes.

Deployment to author is still getting stuck :(

@poojasharma6 please paste the full execution log and your global plugin config. Thanks.

Here is the execution log:
Started by user anonymous [EnvInject] - Loading node environment variables. Building in workspace /opt/app/workload/jenkins/ecms/data/jobs/testDeploy/workspace [workspace] $ /bin/bash -e /tmp/env-testDeploy5327540386606299364.sh [environment-script] Adding variable 'pubServerPort' with value '7210' [environment-script] Adding variable 'pubServerName' with value 'dev00' [environment-script] Adding variable 'authServerPort' with value '7120' [environment-script] Adding variable 'authServerName' with value 'dev00' Deploying packages to http://zlt07765.vci.att.com:7120 [ALERT] Preemptive basic auth enabled for URL http://dev00:7120/
After this it get stuck and nothing happens
Attached is the global plugin config (change to .xml)
org.jenkinsci.plugins.graniteclient.GraniteAHCFactory.txt

@poojasharma6 what is the difference between dev00 and zlt07765.vci.att.com ?

They are same , no difference. I changed that in the output to hide the
real servername. But it seems I missed it somewhere :)
On Tue, Nov 1, 2016 at 6:20 PM, Mark Adamcin<EMAIL_ADDRESS>wrote:

@poojasharma6 https://github.com/poojasharma6 what is the difference
between dev00 and zlt07765.vci.att.com ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/adamcin/crx-content-package-deployer/issues/4#issuecomment-257716639,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVLJ5yXyCFgSn5CyFTV2YREbCxHyoV0uks5q57tHgaJpZM4KY0W1
.


Refactor puppet modules to be more modular

This branch implements 2 major things:

The puppet piece of making it easy to install different submodules of Zulip on different servers.
Adding variables for the postgres and Linux versions to make the puppet configuration support non-Trusty platforms without hackery.  This should help a lot as it's a key step required for #79, #42, #43, and #41.

I've tested that it runs happily on an Ubuntu Vivid test machine (except for the fact that there's no pgtune) and our CI will hopefully confirm that it also still works on Ubuntu trusty.
Before merging I'll also want to confirm that this branch has no effect on a happily configured Ubuntu trusty machine.

Automated message from Dropbox CLA bot
@timabbott, it looks like you've already signed the Dropbox CLA. Thanks!

I successfully tested this on trusty, so this is ready for review.

I fixed a small bug in this and then merged it.  @Galexrt FYI.

@timabbott Good to hear! My pull request for docker is coming in the next hours.


DOC: blaze to pandas. Closes #1249.

Not married to the language. Low-hanging fruit. First thing I wanted to do that was non-obvious / not readily documented.

Closing to cleanup old PRs. Feel free to submit a new PR.


ValueError: Invalid config.json: [Errno 2] No such file or directory: 'config.json'

When i run pycryptobot i see this error ValueError: Invalid config.json: [Errno 2] No such file or directory: 'config.json' in windows 7

you missing the file "config.json" in the directory  /pycryptobot. You have to create it and put your coinbase or binance's api keys + others parameters

Thx this error is now finished


[Web PubSub] Update API for WPS Extensions library

cc: @tg-msft

API changes have been detected in Microsoft.Azure.WebJobs.Extensions.WebPubSub. You can review API changes here

API changes have been detected in Microsoft.Azure.WebJobs.Extensions.WebPubSub. You can review API changes here


Handle tenant failures

This was an issue that was caught on a live debugging session

I'm just used to writing <=, but i essentially meant it as === 0.

@aaomidi what I meant was we should be checking the length of the array instead of the uri -
tenantDetails.length instead of tenantDetailsUri.length

Where am I using tenantDetailsUri.length?

@aaomidi In this link I pasted above (line 273) -
displayName: tenantDetailsUri.length && tenantDetails[0].displayName

Ooooh sorry, I was looking at my changed code.


⚠ Bofrost.de has degraded performance

In 5d141fe, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 915 ms

Resolved: Bofrost.de performance has improved in dda6dc9 after 37 minutes.


feat(frontend): add balance to icrc-ledger.api

Motivation
We aim to support tokens without an index canister. This means that we want to support tokens without transactions, but we still want to fetch balances. These balances can be queried directly from the ledger.
Changes

Add balance to icrc-ledger.api
Comment and add todo for missing test to existing functions

Relates to https://github.com/dfinity/oisy-wallet/issues/2883


Scope not getting assigned properly

Hi,
I am requesting group_join scope during authorization process and my request is successful. When I inspected the response headers, am seeing two different values for Http Get & Http Post requests. Also the Apps section in settings (http://www.meetup.com/account/oauth_apps/) shows only the basic actions. Due to this, a group join request fails with insufficient scope error.
Http Get
{
X-RateLimit-Remaining: 29
Connection: keep-alive
Server: cloudflare-nginx
X-RateLimit-Reset: 10
Transfer-Encoding: chunked
X-OAuth-Scopes: basic
Date: Tue, 17 May 2016 10:12:05 GMT
Vary: Accept-Encoding, User-Agent, Accept-Language
X-Accepted-OAuth-Scopes: group_join, basic
X-Meetup-server: api10
X-Total-Count: 50
X-RateLimit-Limit: 30
}
Http Post
{
X-RateLimit-Remaining: 29
Connection: keep-alive
Server: cloudflare-nginx
X-RateLimit-Reset: 10
Transfer-Encoding: chunked
X-OAuth-Scopes: group_join
Date: Tue, 17 May 2016 10:14:57 GMT
Vary: Accept-Encoding, User-Agent, Accept-Language
X-Accepted-OAuth-Scopes: basic
X-Meetup-server: api6
X-RateLimit-Limit: 30
}
Not able to understand what is wrong with my request/code and why group join scope is not getting assigned. I have also tried revoke access and authorize.
Thanks
Kumaran

were you able to solve this? I'm having the same issue


Query Take and Includes causes related collection to be empty

I have the following statement below, for privacy reasons i cannot list the specifics.
dbcontext
.AsNoTracking()
.Where(query)
.OrderByDescending(d => d.Created)
.Take(8).
.Include(c =>xxxxxxxxxxx)
.ToList()

The results are always more than 8 in varying amounts and some of the referenced included collections are blank, if i remove the take all works well.
Has anyone encountered a bug with a specific: query, include and take where the results with the take were missing the related collection but without it weren't.
Further technical details
Entity Framework: 6.1.3
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10
IDE: Visual Studio 2017

@devteamexpress For EF6 issues, please use https://github.com/aspnet/EntityFramework6
Also, for any issue filed there we will need more information on how to reproduce what you are seeing. A complete code listing or project is ideal, but if that's not possible, then at least the shape of the entity types and something that resembles more accurately the query being used.


[DOC] Debian for 3rd-party repositories

What do you want to do?

[X] Request a change to existing documentation

Tell us about your request.
The Debian installation instructions tell users to install the repository keyring into /usr/share/keyrings, but according to Debian instructions for 3rd-party repositories, this directory should only be used if there is also a package provided that manages the keyring at this location going forward. If that is NOT the case, the keyring should be stored in /etc/apt/keyrings instead. Please either fix the documentation or provide a package for managing the keyring.
What other resources are available?
See https://wiki.debian.org/DebianRepository/UseThirdParty
Relevant paragraph:

If future updates to the certificate will be managed by an apt/dpkg package as recommended below, then it SHOULD be downloaded into /usr/share/keyrings using the same filename that will be provided by the package. If it will be managed locally , it SHOULD be downloaded into /etc/apt/keyrings instead.

Thanks, @dhs-rec! Would you like to raise the PR for the update?
@peterzhuamazon for visibility.

Thanks, @dhs-rec! Would you like to raise the PR for the update?
That depends on what the preferred fix is. If it's just the documentation update, then yes, I can do that. However, from a user's perspective, having a package to manage the keyring file after the initial setup would be way more comfortable.

@peterzhuamazon - What do you suggest?

Hi @dhs-rec ,
In the same doc it says: https://wiki.debian.org/DebianRepository/UseThirdParty
In releases older than Debian 12 and Ubuntu 22.04, /etc/apt/keyrings does not exist by default. It SHOULD be created with permissions 0755 if it is needed and does not already exist.

Ultimately it is a path for locating a key file.
I look at how Temurin handle this and it uses: /etc/apt/trusted.gpg.d/ which is also not recommended.
https://adoptium.net/installation/linux/
The certificate MUST NOT be placed in /etc/apt/trusted.gpg.d or loaded by apt-key add.

Sury.org was one of the suggestions I received in this issue and they also use /usr/share/keyrings.
https://github.com/opensearch-project/opensearch-build/issues/3371#issuecomment-1497830461
I think if needed we can definitely add a step for mkdir for /etc/apt/keyrings and switch to there but to me it feels like uses can change that at any given time. Is there any more documentations or example you can referring for me to take a look?
Thanks.

The PostgreSQL folks do it right: https://wiki.postgresql.org/wiki/Apt. They also provide a package for managing the keyring file.

I think we could change the location of the key to /usr/share/opensearch-commons if needed.
Or just add a mkdir for /etc/apt/keyrings.
Tho again, maybe I missed it, what is the harm for adding a key to /usr/share/keyrings?
Trying to check if there is a hard requirement for us to make that switch. Thanks.

I think we could change the location of the key to /usr/share/opensearch-commons if needed. Or just add a mkdir for /etc/apt/keyrings.
Tho again, maybe I missed it, what is the harm for adding a key to /usr/share/keyrings?

@peterzhuamazon, there is no harm, things will work regardless of where the key is stored. But if the key is added to /usr/share/keyrings, users expect (by reading the linked Debian wiki page), that there is a package provided which manages that key going forward. And that is not the case here.

Trying to check if there is a hard requirement for us to make that switch. Thanks.

Only if you want to follow Debian's standards for 3rd-party repositories...


other: add TypeScript tracker generation script

SUMMARY
This is an ad hoc script for regenerating the content of issue #10004. I'm committing it to the repo so that anyone can run it, and so that i don't need to keep ignoring it from my future PRs. This will be deleted once everything is migrated over to TypeScript.
This does not affect any application code, so this is still in JS (writing/running one-off scripts in TS is still somewhat tricky to get right, so i figured this was easiest)
TEST PLAN
N/A
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

to: @ktmud @graceguo-supercat @john-bodley

Codecov Report

Merging #10074 into master will decrease coverage by 0.64%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #10074      +/-   ##
==========================================
- Coverage   70.49%   69.84%   -0.65%
==========================================
  Files         585      184     -401
  Lines       31073    18191   -12882
  Branches     3185        0    -3185
==========================================
- Hits        21905    12706    -9199
+ Misses       9058     5485    -3573
+ Partials      110        0     -110

Flag
Coverage Δ

#cypress
?

#javascript
?

#python
69.84% <ø> (-0.23%)
:arrow_down:

Impacted Files
Coverage Δ

superset/views/database/mixins.py
59.64% <0.00%> (-21.06%)
:arrow_down:

superset/utils/cache.py
48.00% <0.00%> (-20.00%)
:arrow_down:

superset/db_engine_specs/mysql.py
78.26% <0.00%> (-13.05%)
:arrow_down:

superset/views/database/validators.py
78.94% <0.00%> (-5.27%)
:arrow_down:

superset/views/database/api.py
84.09% <0.00%> (-3.41%)
:arrow_down:

superset/db_engine_specs/postgres.py
97.29% <0.00%> (-2.71%)
:arrow_down:

superset/views/database/views.py
87.17% <0.00%> (-2.57%)
:arrow_down:

superset/models/core.py
83.96% <0.00%> (-2.34%)
:arrow_down:

superset/jinja_context.py
80.00% <0.00%> (-0.96%)
:arrow_down:

superset/security/manager.py
88.69% <0.00%> (-0.35%)
:arrow_down:

... and 407 more

Continue to review full report at Codecov.

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


Issue with k8s.io/docs/tasks/network/validate-dual-stack/

This is a Bug Report

Problem:
Validate that the node has an IPv4 and IPv6 interface detected (replace node name with a valid node from the cluster. In this example the node name is k8s-linuxpool1-34450317-0):

kubectl get nodes k8s-linuxpool1-34450317-0 -o go-template --template='{{range .status.addresses}}{{printf "%s: %s \n" .type .address}}{{end}}'
Hostname: k8s-linuxpool1-34450317-0
InternalIP: <IP_ADDRESS>
InternalIP: 2001:1234:5678:9abc::5

The node won't get Ipv6 address unless a CCM updates the node, please refer this ticket,
https://github.com/kubernetes/kubernetes/issues/88784#issuecomment-596303566
Proposed Solution:
Please update this part with more details about when node gets dual stack addresses
Page to Update:
https://kubernetes.io/...

v1.17.3

/sig network
/priority backlog


It could be very useful
Thanks again

It is indirectly possible if you use the OAuth2 ClientCredentialsGrant. In this case you can receive a valid token by accessing the token-endpoint directly with basic authentication. If the lifetime of the tokens are your problem you are able to configure the token lifetime per client and per realm.
If you want to try it with the ClientCredentialsGrant you need to enable ServiceAccount at the clients configuration. After that a new tab should appear called "Service Account" where you can add realm-roles. The client acts as user and client if service account is enabled. Afterwards you can increase the lifetime of the token to 1 day or something similiar. Just be sure to be cautios on productive environments with long living tokens.
Does this help?

Thanks @Captain-P-Goldfish but the only method that I have to communicate with SCIM endpoints is via basic authentication. Your suggestion pass throw a token release, or am I missing something?

You are using curl right? So you still have the possibility to authenticate with Bearer tokens by setting the authorization-header manually:
curl -H "Authorization: Bearer ${TOKEN}" http://localhost:8080/auth/realms/test/scim/v2/Groups

But there is unfortunately no way that I will start messing around with the login mechanisms of keycloak. At least I cannot see why the only possible authentication form should be basic.

I know :-) ... the endpoint will be consumed by legacy software and I don't have control over it :( ... I'm looking for a solution

In this case I am afraid I cannot help. Adding alternative login mechanisms would potentially hold some unwanted security risks that I might open into keycloak and I would like to avoid this.

Fell free to reopen if you got another idea or solution we could come up with but this is out of scope for this project I'm afraid

Thanks @Captain-P-Goldfish .
I tried also with your suggestion but I received an error with "unauthenticated".
I tried service account and a user but nothing.

works for me. Just tried:
curl -X POST -u my-scim-client:c6cfad8b-fb5e-416e-95d9-6180ddd2d273 -H "Content-Type: application/x-www-form-urlencoded" --data "client_id=my-scim-client&grant_type=client_credentials" http://localhost:8080/auth/realms/scim/protocol/openid-connect/token

and got
{"access_token":"eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICIwM1MzN1FoLXFKemk1U3M5MTdfcTZ1Y2NuR2FYMXJFQXJFN1FoYUpjc2dBIn0.eyJleHAiOjE2MjY4MzU3MDYsImlhdCI6MTYyNjc5OTcwNiwianRpIjoiZmYwNjBjMTYtMjZkMi00MGE1LWJhZGMtODUzNDQ3M2IxZjBiIiwiaXNzIjoiaHR0cDovL2xvY2FsaG9zdDo4MDgwL2F1dGgvcmVhbG1zL3NjaW0iLCJhdWQiOiJhY2NvdW50Iiwic3ViIjoiZDAyZDM3MWQtOTE2ZC00YTUxLWJiZWYtYzdhM2RmOWIzZTI2IiwidHlwIjoiQmVhcmVyIiwiYXpwIjoibXktc2NpbS1jbGllbnQiLCJhY3IiOiIxIiwicmVhbG1fYWNjZXNzIjp7InJvbGVzIjpbIm9mZmxpbmVfYWNjZXNzIiwiZGVmYXVsdC1yb2xlcy1zY2ltIiwidW1hX2F1dGhvcml6YXRpb24iXX0sInJlc291cmNlX2FjY2VzcyI6eyJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6InByb2ZpbGUgZW1haWwiLCJlbWFpbF92ZXJpZmllZCI6ZmFsc2UsImNsaWVudElkIjoibXktc2NpbS1jbGllbnQiLCJjbGllbnRIb3N0IjoiMTI3LjAuMC4xIiwicHJlZmVycmVkX3VzZXJuYW1lIjoic2VydmljZS1hY2NvdW50LW15LXNjaW0tY2xpZW50IiwiY2xpZW50QWRkcmVzcyI6IjEyNy4wLjAuMSJ9.CaXmUO0M2H4gTKqy_V7z0PkwYXoGqBRT4uF3d_kNvFGp4p2pSAbcNbrAETavf8hEFLrvvzjUe1iLpmCE74uttznQYo1J2OQydoK3QIqC_xxYL9kaNewWb1qHcFcitHs5V2EtnZDvdQM7y8tekgGIDLRQjQOJAP6R-ovB3k48WNPTIRWf2sWaF90RAhaqjAsLMb-HESWOC7YkEfPHm3yxVL9YoMVEktIFM_4DRqZJwGp7CFxvAwID69NvtWdFJk7PwIcgV3tEgC8NUDijWY8PmPLwdPIoRnwtR36lQX8vWkqMT72LSyrE2PN7FAROsOeoJf6jxQOkkPvmjaYA5stlAA","expires_in":36000,"refresh_expires_in":0,"token_type":"Bearer","not-before-policy":0,"scope":"profile email"}

store token in variable
BEARER=eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICIwM1MzN1FoLXFKemk1U3M5MTdfcTZ1Y2NuR2FYMXJFQXJFN1FoYUpjc2dBIn0.eyJleHAiOjE2MjY4MzU3MDYsImlhdCI6MTYyNjc5OTcwNiwianRpIjoiZmYwNjBjMTYtMjZkMi00MGE1LWJhZGMtODUzNDQ3M2IxZjBiIiwiaXNzIjoiaHR0cDovL2xvY2FsaG9zdDo4MDgwL2F1dGgvcmVhbG1zL3NjaW0iLCJhdWQiOiJhY2NvdW50Iiwic3ViIjoiZDAyZDM3MWQtOTE2ZC00YTUxLWJiZWYtYzdhM2RmOWIzZTI2IiwidHlwIjoiQmVhcmVyIiwiYXpwIjoibXktc2NpbS1jbGllbnQiLCJhY3IiOiIxIiwicmVhbG1fYWNjZXNzIjp7InJvbGVzIjpbIm9mZmxpbmVfYWNjZXNzIiwiZGVmYXVsdC1yb2xlcy1zY2ltIiwidW1hX2F1dGhvcml6YXRpb24iXX0sInJlc291cmNlX2FjY2VzcyI6eyJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6InByb2ZpbGUgZW1haWwiLCJlbWFpbF92ZXJpZmllZCI6ZmFsc2UsImNsaWVudElkIjoibXktc2NpbS1jbGllbnQiLCJjbGllbnRIb3N0IjoiMTI3LjAuMC4xIiwicHJlZmVycmVkX3VzZXJuYW1lIjoic2VydmljZS1hY2NvdW50LW15LXNjaW0tY2xpZW50IiwiY2xpZW50QWRkcmVzcyI6IjEyNy4wLjAuMSJ9.CaXmUO0M2H4gTKqy_V7z0PkwYXoGqBRT4uF3d_kNvFGp4p2pSAbcNbrAETavf8hEFLrvvzjUe1iLpmCE74uttznQYo1J2OQydoK3QIqC_xxYL9kaNewWb1qHcFcitHs5V2EtnZDvdQM7y8tekgGIDLRQjQOJAP6R-ovB3k48WNPTIRWf2sWaF90RAhaqjAsLMb-HESWOC7YkEfPHm3yxVL9YoMVEktIFM_4DRqZJwGp7CFxvAwID69NvtWdFJk7PwIcgV3tEgC8NUDijWY8PmPLwdPIoRnwtR36lQX8vWkqMT72LSyrE2PN7FAROsOeoJf6jxQOkkPvmjaYA5stlAA

then
curl -H "Authorization: Bearer ${BEARER}" http://localhost:8080/auth/realms/scim/scim/v2/Users

and eventually received
{"schemas":["urn:ietf:params:scim:api:messages:2.0:ListResponse"],"totalResults":1,"itemsPerPage":1,"startIndex":1,"Resources":[{"schemas":["urn:ietf:params:scim:schemas:core:2.0:User"],"id":"586cded0-8bb6-4020-b262-bf0ebfa49cf2","userName":"my-test-user","active":true,"meta":{"resourceType":"User","created":"2021-07-20T16:50:38.717Z","lastModified":"2021-07-20T16:50:38.717Z","location":"http://localhost:8080/auth/realms/scim/scim/v2/Users/586cded0-8bb6-4020-b262-bf0ebfa49cf2"}}]}

Works perfectly fine for me

Ok, I understood 😅... I caught my error 😁
Thanks for the patience

glad it works :-)


optimization readme

What this PR does:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Codecov Report

Merging #335 (2c99f6c) into develop (04933a9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #335   +/-   ##
========================================
  Coverage    36.78%   36.78%
========================================
  Files           54       54
  Lines         3262     3262
========================================
  Hits          1200     1200
  Misses        1938     1938
  Partials       124      124

Continue to review full report at Codecov.

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


Added preloader

Description

Fixes #801
https://github.com/SurajPratap10/Imagine_AI/assets/103810119/4cde4518-c954-4d97-b75a-7cfb947f31bc

Screenshots

BEFORE
AFTER

Checklist

[ ] Tests have been added or updated to cover the changes
[ ] Documentation has been updated to reflect the changes
[x] Code follows the established coding style guidelines
[x] All tests are passing

It breaks the app


Add persistence to gafaelfawr redis at T&S sites

Also, these PVs are created with the reclaim policy "Delete" (which means the volume is automatically deleted when the PVC is deleted).
In some cases, it might be appropriate to change the reclaim policy to "Retain".
kubectl patch pv <your-pv-name> -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}'


Convert 'xml:lang' attribute to use namespace when performing Codelist checks

This is a fix to the bug identified by @andylolz in https://github.com/IATI/pyIATI/pull/45#issuecomment-342554472 - Codelist validation would raise a key error for any dataset with an xml:lang attribute.
This is a specific fix to the xml:lang problem. It does not address the issues that the current code does not support custom namespaces (though this is a larger problem).

Nice – this looks good to me (when I comment out the fix, the new test fails – so looks like that is doing its job!)


Snapshot download is inefficient

Currently the bedrock snapshot download runs the download and extraction in separate stages which is very slow and inefficient especially on platforms like EC2. It would be nice if this was reworked to simply pipe the download from wget through | tar -C /geth -xvf - so the download and extraction is in one shot, then you don't have to waste time reading and extracting the 400GB you just downloaded...

Hi, our fork has fixed this issue and use an official snapshot.
Check out https://github.com/Chomtana/simple-optimism-node/tree/main/scripts
Pull request https://github.com/smartcontracts/simple-optimism-node/pull/97


High CPU load

Tested on iPad Pro 13 inch - CPU usage is about 30-45% in idle. And a lot more in the old iPads
Sound of AUv3 in 90% cases is late and goes crazy (I used code for auv3 from brokenV3) If I add two or more plugins, then CPU load 100%  and sound is hang

Hi Wiksnet.  Yea, its in a broken branch for a reason. :).  What is your testing method.  What host?  How do the numbers in AUv3 compare with the standalone app? Lets use this issue for further communication, but since this is on-going develop, I'll close this as an open issue.

Hello Aure,
I use Garageband and Cubasis 2. iPad 12.9inch, ios: 12.1.3 (16D40). Output: built-in iPad speakers.

First I compiled app (no difference if I run debug+garageband or just compile app and run garageband)
Open GarageBand or Cubasis (better garageband, in cubasis for some reason in 50% of cases it worked fine)
Remove all instruments and add just one Synth One auv3

result... sound is fine, but CPU in the XCode or Cubasis metric control is about 32-45% that seems to be alarming, because the simple use of SynthKit with 1 oscillator usually shows 1% CPU, other auv3 plugins also shows for me 1-5% cpu

Add second auv3:Synth One instrument

the sound starts to distort very much and the processor shows 75-100% load
it seems as if two synthesizers use one buffer for sound and edit it - but I'm newbie for programming with audio and can't be sure.  one thing I am sure for sure. that this should not be so, because adding 4-5 synthesizers just puts down the whole system and GarageBand or Cubasis is hang.

ps...
I tried to record a video today, but for the most cases it worked all day for me :) Only 3-4 times I noticed it. Yesterday it not worked at all in 90% cases. Anyway I'll try to catch it and show you.
Also I went the other way and created an empty new project with added AudioKit framework. Auv3 is running and by pressing a note I just reproduce sound of 1 oscillator using this code:
` //osc
let oscillator = AKOscillator()    //Create the sound generator
                                    //master out
                                    AudioKit.output = oscillator    //Tell AudioKit what to output

                                    do {
                                        try AudioKit.start()    ///Start up AudioKit
                                    } catch {
                                        print(error)
                                    }

                                    oscillator.amplitude = 0.5
                                    oscillator.frequency = random(in: 220...880)    //Set oscillator parameters
                                    oscillator.start()    //Start the oscillator`

It sound good in garageband/cubasis and cpu:0-1%, but when I'm adding a second auv3, then sound  then the sound is very distorted.
Here is private video - https://youtu.be/SDG_x2yAM9E
and also issue with cpu load (this one from "broken" branch*, but for the master cpu load is actually same)
https://studio.youtube.com/video/8OMlE80o9DM/edit

Finally catch it - https://www.youtube.com/watch?v=vdrDd3WEmVo

Yikes, we definitely got some issues don't we?  I'll see what I can do.  I think I see what is wrong with your experiment, I'll make a commit there directly.

Thanks. Sure. I rather ran into two problems. 1st is a broken/hang sound like on the last video (used code from "broken" branch, nothing has been changed). And the second is that the sound from plugin1 comes out from a  second pluging too. Even if I did not press the note on second. - The same issue actually I saw in the "experimentation" branch.


Remove deprecated files that were used to generate documentation

Issue
Just some housekeeping with files that were used to generate documentation.
Solution
Delete them.
Impact
None.
Usage Changes
None.
Considerations
None?
Testing
None.

👋


Named @RestForm and error mapping of the violations

The @RestForm annotation is accepting a value which is the name of the parameter.
So it is valid to name the the parameter:
@POST
public void procced(@RestForm("u") @NotBlank String userName) {
    // do something with the form parameters
}

But in this case the the validation is executed (hasError() returns true) but the error is placed on the "userName" key. I would have expected to have them on "u".
Is that expected?
The returned violations here do not seems to contains this information:
https://github.com/quarkiverse/quarkus-renarde/blob/7533edcef039b0721b76d52f27f91d047854f2f1/runtime/src/main/java/io/quarkiverse/renarde/util/MyValidationInterceptor.java#L34-L35
So the mapping to the lastNode key seems difficult to change:
https://github.com/quarkiverse/quarkus-renarde/blob/7533edcef039b0721b76d52f27f91d047854f2f1/runtime/src/main/java/io/quarkiverse/renarde/util/Validation.java#L101-L110

Ah yes, good point. We need to add logic to find the original form name. If you're up for making a PR, I can help you.

I just implemented the unit test in a10cd252467d08d276eadc1f8f05eafb91216692, but I would need some pointer on "logic to find the original form name" because right now I have no clue how it is supposed to be done.

Unfortunately, we don't have any logic in Quarkus REST to reverse-map parameters back to their HTTP form name (or query, or header, or cookie).
It should be doable for simple cases, though, in MyValidationInterceptor, because when you get a validation error on method parameters, the constraint violation's property path is {<method name>, <parameter name>} so you can ignore the first element, only keep the last member (as we do now) and then iterate the method parameters to find the parameter with the right name using ctx.getMethod().getParameters().
Once you get the right parameter, you can load its annotations and if you see a @RestForm or a @FormParam annotation with a non-null value, you can use that for the error key.
This won't work for bean params, though, but we can add support for them later, let's not over-engineer this for now.

This won't work for bean params, though, but we can add support for them later, let's not over-engineer this for now.

This is an other potential issue, but right now if you use FormData class approach (which every field annotated with @RestForm as suggested in this section), according to my tests there is no validation.

Are you sure? Did you add @Valid to the endpoint parameter?

Thank you for the pointer, I was not aware of the @Valid annotation.
So for the second example of the page https://docs.quarkiverse.io/quarkus-renarde/dev/advanced.html#_the_endpoint (with the FormData). This applies the validations:
@Consumes(MediaType.MULTIPART_FORM_DATA)
@POST
public void complete(@RestQuery String confirmationCode,
        @Valid FormData form) {
    // do something with the form parameters
}

public static class FormData {
        @RestForm @NotBlank @Length(max = Util.VARCHAR_SIZE) String userName;
        @RestForm @NotBlank @Length(min = 8, max = Util.VARCHAR_SIZE) String password;
        @RestForm @NotBlank @Length(max = Util.VARCHAR_SIZE) String password2;
        @RestForm @NotBlank @Length(max = Util.VARCHAR_SIZE) String firstName;
        @RestForm @NotBlank @Length(max = Util.VARCHAR_SIZE) String lastName;
}

With the same limitation as the one discussed in this issue:
public static class FormData {
        @RestForm("foo") @NotBlank @Length(max = Util.VARCHAR_SIZE) String userName;
        //...
}

The validation works, but is set on errors map with the key "userName" and not "foo".

OK, so same problem, I suspected.


issue #144 - spread remaining props on parent div

Rebased

Rebased.

@cklab can you rebase with latest master?

@ad1992 rebased

Rebased once more.

@cklab can you rebase with latest master and make the review fixes?

Apologies, I haven't used this library for almost a year now. I don't have the luxury to continually rebase and resolve conflicts for trivial reasons.


Logbook front page of wavelog shows distances in km when settings set to miles

This is for reporting bugs with the code, if this issue is regarding setting up on your local server please use the discussions area
Describe the bug
I have set up my preferences to show distanes in miles.

I see distances in kilometers from the front page of wavelog on the logbook below the map.

Version Information

Wavelog:          1.8.8 (I did just update to 1.9, issue is still present)

Steps to Reproduce

Set distance preferences in wavelog to miles, and have distances set as a column in your logbook
go to wavelog front page where map and recent qsos are
see that the distances are in kilometers on the logbook

Expected Behavior
I expect the distances to be in miles if that is what I have selected in preferences.

You should update your instance. This has been implemented in version 1.9:
https://github.com/wavelog/wavelog/pull/1331

@phl0 I did just update. I am on 1.9, issue persists.

I tried switching distance preferences, then switching back. did not help. still in km. Also tried turning off the distance column on the logbook, then turning it back on. no luck. still shows km. I am definitely on 1.9

This was fix right after 1.9 release: https://github.com/wavelog/wavelog/pull/1331
Either switch to dev branch, or wait for the new release.


People Picker should have ability just to display inactive users name (ideally the value fetched from 'Author/Title')

Enhancement.
People Picker should have the ability to assign the person (IPersonaProps) directly. This is useful just to display the inactive users when you have people picker in Edit form.. Just like how SharePoint lists users in Person column even the users' accounts are no longer valid.
Currently I am forced to show blank when you Edit the form this is very confusing to the end users.
We can fetch username from user field though the user is inactive.. for ex: (_api/web/lists('listid here')/items(1)?$select=ID,Author%2FTitle&expand=Author). This 'Title' would be displayed in OOB people picker box though the user is not active. Similarly we should also be able to assign the value to the PnP's people picker control.
Otherwise again we need to depend on NormalPeoplePicker to achieve this behavior.
This is somewhat related to the below issue
#https://github.com/SharePoint/sp-dev-docs/issues/5970
We all know SharePoint does not resolve the inactive users.. its SharePoint behavior.. nothing we can do there..
The issue can be resolved if we can provide the ability to display the username in the picker's textbox.
Here is my thought for fix.
Change the defaultSelectedUsers property from string or IPersonaProps
Ideally inactive users email would be null in OOB SharePoint... When email is null/empty just display the given 'initials' and 'text'.. if email has value just continue the current functionality. Basically apply filter to 'selectedPersons' and play around.
Of course.. need to update the document...on how to bind inactive users?

Can this be triaged quickly? This is a basic requirement and without this the control cannot be used for Edit forms. It's pretty much limited to for New Forms. Also, appears many people are looking for this implementation. Appreciate your response soonest.

@sankarkumar23 - Understand that this is an open source effort and everyone here volunteers their time to create these resources. You're also asking right in the middle of a time of year when many people are taking time off to spend the holidays with their families. The team here will take a look at this when they can. If your request seems as if it will benefit the larger community, they may implement it. Reminder: open source means you can contribute the fix/change, too.

I made the fix and created a pull request. Please review and accept if fix makes sense.
Currently the defaultSelectedUsers is accepting email or login name in string [].. I just extended it to accept the user title along with an append '|inactive'. So if string endswith '|inactive' it will be exclude it from the people search but still binds it to the control.
for example, assume if you you have an defaultPerson object with two properties email and title (user name of the inactive user) it can be assigned as shown below.
defaultSelectedUsers={this.props.defaultPerson.map(e => e.email || ${e.title}|inactive)}

I made the fix and created a pull request. Please review and accept if fix makes sense.
Currently the defaultSelectedUsers is accepting email or login name in string [].. I just extended it to accept the user title along with an append '|inactive'. So if string endswith '|inactive' it will be exclude it from the people search but still binds it to the control.
for example, assume if you you have an defaultPerson object with two properties email and title (user name of the inactive user) it can be assigned as shown below. The email should be empty for inactive users.
defaultSelectedUsers={this.props.defaultPerson.map(e => e.email || ${e.title}|inactive)}

Thank you @sankarkumar23  for reporting this one and creating a PR.

Thank you @sankarkumar23 for reporting this one and creating a PR.

@AJIXuMuK - Could you please push #773 also to 2.4.0

@AJIXuMuK - I have enhanced the fix as previous fix forces to verify the user is active or inactive before hand. With this new code if user is not found, ideally inactive user, the appended title will be shown. Appreciate your review. Also please see if this change can be pushed with 2.4.0
Still got a punch because of https://github.com/pnp/pnpjs/issues/778. EMail is not available (in expand) for userfield with multi-select. Either you get email from sp.web.getUserById(id#) or just settle with Title field. If usefield is not multi-select there is no need to call sp.web.getUserById since "expand" itself provides both Title and EMail.
<EMAIL_ADDRESS>//email can be active or inactive user's.
or
defaultSelectedUsers={["/usertitle"]} // this also works and just binds the title.

@AJIXuMuK - I have enhanced the fix as previous fix forces to verify the user is active or inactive before hand. With this new code if user is not found, ideally inactive user, the appended title will be shown. Appreciate your review. Also please see if this change can be pushed with 2.4.0
Still got a punch because of https://github.com/pnp/pnpjs/issues/778. EMail is not available (in expand) for userfield with multi-select. Either you get email from sp.web.getUserById(id#) or just settle with Title field. If usefield is not multi-select there is no need to call sp.web.getUserById since "expand" itself provides both Title and EMail.
<EMAIL_ADDRESS>//email can be active or inactive user's.
or
defaultSelectedUsers={["/usertitle"]} // this also works and just binds the title.

Hi @sankarkumar23,
I've merged your latest update.

Hi @sankarkumar23,
I've merged your latest update.

Thank you @AJIXuMuK.

Thank you @AJIXuMuK.


Need openedx.yaml files

Both for this repo, and for the repos that it creates.

Openedx yaml for this repo: https://github.com/edx/edx-cookiecutters/blob/master/openedx.yaml
openedx yaml for repos it creates: https://github.com/edx/edx-cookiecutters/blob/master/python-template/{{cookiecutter.placeholder_repo_name}}/openedx.yaml


How we can add bookmarks in pdf

Hi,
I want to use this awesome library unable to find a method for adding bookmark.
Can you please help me?
Thanks
Shubham

There is no possibility of editing documents.

oh....no.....


RCON stops working after server restart

Bug Report
System Information

Windows 10
AMP <IP_ADDRESS>
Bleeding

I confirm:

[x] that I have searched for an existing bug report for this issue.
[x] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.

Symptoms
The new Avorion template uses SourceRCON for console input as STDIO does not work on Windows. When the server is started for the first time after the instance is started, console input works fine in AMP. However, if the server is restarted, or stopped and started, then console input stops working. The instance needs to be restarted to get it working again.
Reproduction

Create a new Avorion instance, start the server, then restart it.

This issue also seems to affect BattlEye RCON on Arma Reforger (on a Linux this time).

I believe this was addressed in Nightly, but I've tried that and Bleeding and still have the issue on 7d2d generic.

This does indeed appear to be fixed for Avorion on Windows with Nightly.

This is still an issue in the generic 7d2d.

Just a testing update.  But this issue is still happening with the generic module for 7d2d on Ubuntu/Linux on the most recent AMP.

AMP v20220917.1, built 17/09/2022 03:00
Ubuntu Server 18.04

Testing procedure:

Create a new instance of 7d2d using the generic module.
Start the 7d2d game server - no issues
Shutdown and restart the game server - RCON hangs and AMP does not recognize the game server has started.
Shutdown the game server (using abort button).  Stop and restart the AMP instance.
Start the 7d2d game server - again no issues.

RCON is still hanging unless the AMP instance is restarted.

This also still seems to be an issue for BattlEyeRCON

Fixed in 2408.

No, it's not fixed, at least for BattlEyeRCON on Arma generic.
On Windows AMP now never connects to RCON, despite the RCON server listening. And on Linux the whole instance just crashes during startup with a RCON socket error. So things have actually regressed.
Maybe issues shouldn't be closed until testing has actually shown them to be resolved?

It was tested, but the bug referenced SourceRCON, not BERCON.

Originally, yes, but then the issue was found to be wider and I and Ice included comments to that effect and I updated the title. Anyhow, hope you can find the issue

Reopening due to issue still persisting, and adding to 2.4 LTS milestone for proper check and reproduction.

Mentioned in issue 779 - tracking there.


Fix hotkeys matching

Hi,
Thank you for such a great library! I'm using it in my project and am happy with the functionality. It has everything I need.
Unfortunately, I've faced a bug in the hotkeys matching algorithm: it doesn't check that the controls aren't pressed when they're not needed. Let me give you an example to explain the situation better.
Suppose I want to do some action on the ctrl+m hotkey. The action will be executed even on ctrl+shift+m or ctrl+alt+m. It doesn't seem correct, because I may want to set another action on the ctrl+shift+m hotkey. The most common case is when the user wants to add hotkeys for scrolling: ctrl+tab is next and ctrl+shift+tab is prev.
In this PR, I've fixed this bug by checking if the modifier key is not pressed when it doesn't need to be pressed.

@all-contributors please add @TheBestTvarynka for code

Thank you 😊


Month range is not compatible

The range for the month is not compatible with the original cron.
crontab man page says:

month	     1-12 (or names, see below)
http://www.unix.com/man-page/linux/5/crontab/

So node-cron should follow the original range.

An option to use unix cron format would be nice, particularly if the cron string is generated. Otherwise, I now have to parse my cron string, adjust the month, and rebuild my string to feed it into node-cron.

Could we just add an option to trigger the unix cron mode? This library is the only one that use 0-11  for months, all others use 1-12. So it is not cool because it's too special.

@dule I have to do exactly the same, could you please share with me some sample code?

He is a workaround for the problem:
npm install cron-converter --save

var Cron = require('cron-converter');

var cronInstance = new Cron({
  outputMonthNames: true
});

var pattern = '* * * 9 *';
pattern = cronInstance.fromString(pattern).toString();
console.log(pattern); // * * * SEP *

We changed month number to month name, then it's working fine with this library.


Preflight Checklist

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
[X] I am not looking for support or already pursued the available support channels without success.

Version
1.4.0
Installation Type
Official Docker Compose
Service Name
Doc(DongTai-Doc)
Describe the details of the bug and the steps to reproduce it
1.点击进入项目
2.点击漏洞报告下载，处理1天，进度仍一直提示下载中

Additional Information
No response
Logs
无

It is the bug of v1.4.0, we will fix the bug in next version


Add option to change language manually

My phone is set to English, and as a result the app is in English as well. I would appreciate an option to change the language of the app to German without changing the language of the operating system.
App version: 1.0.4
OS version: Android 9

Thanks for the suggestion, @davidhusz . We are already tracking a similar proposal in corona-warn-app/cwa-wishlist#22 and will therefore close this issue here.


Fix "Find component IDs" anchor reference

Not sure why the backticks at the end there are seen as a modification. I just used the github editor to tweak this file.

@eogas : Thanks for your contribution! The author, @gregvanl, has been notified to review your proposed change.

Thanks!
#sign-off


Is this gem abandoned?

First of all, I don't want to sound harsh; the amount of work put here and what it provides is amazing!
There's a big number of unaddressed issues, PRs that are not merged nor commented and (apparently) tests are failing since long. So I would just like to know better if this gem has a future or not.

Hi @dgmora, you're not sounding harsh and your concern is justified. It is true that I have been neglecting this particular repository for some time. I had to focus on other responsibilities, and wasn't able to find time for this one.
In particular, I have spent quite some time on the sibling repository, https://github.com/elastic/elasticsearch-ruby, which provides a low-level Ruby client and a couple of widely used extensions, and which also serves as a basis for the Rails integrations in this repository. I have been able to clear up most of the pull requests and issues there, notably when it comes to compatibility with various Elasticsearch versions, and plan to switch focus to the Rails integrations in this repository in the coming weeks and months (notably, again, revisiting compatibility with Elasticsearch versions).
So no, this gem is definitely not abandoned. It is just that I have kept focus on the other set of libraries.
P.S.
What's not very evident from the outside perspective, perhaps, is that even small pull requests come with some overhead, sometimes a considerable overhead: I have to understand the intention there, find other related issues or patches, review the changes and sometimes ask for changes, verify (and sometimes add) the tests locally, clean up and annotate the commit messages, merge into appropriate branches. I guess I could make my life easier if I would just click the "Merge" button, but I don't want to risk the chance that the codebase falls totally apart...

Thanks for the clarification! For the elasticsearch versioning and PRs overhead, I guess it'd be helpful if you could test against multiple versions. I used docker (install docker, docker run elasticsearch; or per version docker run elasticsearch:5.1.2) to have elasticsearch running easily for the tests.

Thanks for the understanding!
Testing against multiple version of Elasticsearch is not really a problem -- notice I haven't even included it in my list of problems :)
I use the Test::Cluster extension for that, which is also used at Travis with the SERVER=start environment variable for the elasticsearch-ruby group of gems. The only thing needed to be done is to download & extract the appropriate versions.
I'll close this issue if it's OK -- since I've managed to clear up most of the pending issues in the elasticsearch-ruby repository, I'll switch focus to this repository next.