support for Koa or hapi

do you have any plan to support any servers rather than express soon ?

Hi @AhmadEl-Banna, thanks for your question.
There are no plans to support other servers than express so far. Can you further describe your requirements/use case?

Closing this for now, as there has been no more feedback on the issue.

@vjpr did using that wrapper work for you?

For me, koa has better design, with koa I can easily track all of my request and response.
Maybe we could make graphql-yoga support most servers like apollo-server.

Hey, @Urigo from The Guild here!
You might know us from projects such as graphql-code-generator, envelop or graphql-tools.
For a long time we thought that the Javascript ecosystem is still missing a lightweight cross-platform, but still highly customizable GraphQL Server.
In the past the awesome Prisma team took on that great challenge and now we are happy to announce that we are continuing them and just released GraphQL Yoga 2.0 - Build fast, extensible, and batteries-included (Subscriptions, Serverless, File uploads support) GraphQL APIs in Node.js 🚀
And regarding the issue here, Yoga is completely separated from the way you do HTTP, so you can easily use and expose anything to express but also use Yoga on many other environments and frameworks like Fastify, Koa, Hapi, Cloudflare Workers, Lambdas and many more.
We have been working a long time on version 2.0 and have been using it in our clients projects for a few months now and shared a couple of alpha cycles here.
Thank you all for your feedback and suggestions, you made this release possible!
Please try Yoga out again, give us feedback and help us spread the word on the new release!

Announcement and blog post
https://github.com/dotansimha/graphql-yoga/issues/704
https://www.graphql-yoga.com/


HOSTING-594 Add permissions for line-notify plugin

Add permissions for line-notify plugin

Description
Add permissions for maintainers to release https://github.com/jenkinsci/line-notify-plugin
Hosting request: https://issues.jenkins-ci.org/browse/HOSTING-594
Following users should have permission:
@wisdomcd    (Atifactory)
@wisdomcdh  (github)
Submitter checklist for changing permissions

Always

[x] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[x] Add link to resolved HOSTING issue in description above

For a new permissions file only

[x] Make sure the file is created in permissions/ directory
[x] artifactId (pom.xml) is used for name (permissions YAML file).
[x] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[x] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] All newly added users have logged in to Artifactory at least once

token looks like it should be stored as a http://javadoc.jenkins.io/hudson/util/Secret.html
See https://jenkins.io/doc/developer/security/secrets/ for why.

@daniel-beck
Thank you.
Let's add that feature in the next release.

Please address this issue and let me know when done.

@daniel-beck
This issue has been resolved.

@wisdomcdh Thanks! 👍

@daniel-beck Thank you for your help.
i fixed that

Still wrong, same line.

sorry
https://github.com/jenkinsci/line-notify-plugin/blob/master/pom.xml#L10

My previous feedback still applies.

Hello @wisdomcdh do you plan to address Daniel's comments? See his last one.
I will close this PR in a few days without action/answer here. Thanks for your understanding.

@batmat
I am really sorry
I have not worked for a long time because of my honeymoon.
I'll give you feedback soon.


Wrap HTML string in a

This ensures that all valid HTML fragments can be parsed by the DOMParser, including those with elements such as <tr> at the top level (e.g. if we are targeting a <tbody> with reef.component).
Fixes #192

This looks like a good PR. Doing some internal testing before I merge. Thanks for this!


Rebuild with a higher version of Tokio to fix CVE-2023-22466

Trivy scans my project and finds a CVE. When I look at it, the dependency comes in from reqwest which in turn uses hyper-tls that has the dependency. In hyper-tls, the Cargo.toml specifies version ^1 so I guess a simple update and rebuild would include a higher Tokio version that isn't affected by the CVE. I would contribute this as a PR but it seems to me (a Rust noob) that there is no coding involved.
packages/myproject/Cargo.lock (cargo)

Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 1, HIGH: 0, CRITICAL: 0)

┌─────────┬────────────────┬──────────┬───────────────────┬────────────────────────┬───────────────────────────────────────────────────────────┐
│ Library │ Vulnerability  │ Severity │ Installed Version │     Fixed Version      │                           Title                           │
├─────────┼────────────────┼──────────┼───────────────────┼────────────────────────┼───────────────────────────────────────────────────────────┤
│ tokio   │ CVE-2023-22466 │ MEDIUM   │ 1.22.0            │ 1.23.1, 1.20.3, 1.18.4 │ Tokio reject_remote_clients configuration may get dropped │
│         │                │          │                   │                        │ when creating a Windows named pipe...                     │
│         │                │          │                   │                        │ https://avd.aquasec.com/nvd/cve-2023-22466                │
└─────────┴────────────────┴──────────┴───────────────────┴────────────────────────┴───────────────────────────────────────────────────────────┘

You can just run cargo update and it'll resolve your problem.

You can just run cargo update and it'll resolve your problem.

Thanks, just tried it and it really updated the sub-dependency. Thanks for pointing that out and excuse my ignorance. I'm still new to Rust.


Potentially create BalanceNodeUtilization strategy

I've looked over the LowNodeUtilization strategy, and I'm not sure it fits my use case. I'm not sure if the right solution is to build a different strategy, but I wanted to spell it out to get your thoughts.
My understanding is LowNodeUtilization is trying to optimize for making the most use out of your cluster, there's no reason to run nodes if you aren't going to fill them up.
The issue I am trying to solve is that I know my cluster behaves badly when CPU and memory are near 100% (CPU because of some sort of contention, memory because if system OOM killer has to get involved it leaves things in a bad state). Because of that, I would like to optimize for preventing any nodes from running too hot, as opposed to making sure that all nodes are being used.
My thought was, instead of having thresholds and targets, to have some way of quantifying how "unbalanced" a cluster is, and have a toleration of that balance that is inevitable due to bin packing issues, and evict pods if they fall out of that range. (Something like how many standard deviations away from the mean a given node is, but probably with the language of binomial distributions since these are percentages.) As far as I can tell, this cannot be achieved with LowNodeUtilization, since I do not know a priori what levels my cluster is running at.
Please let me know if I'm way off base on this one, I've only just started playing with the descheduler. I was thinking of implementing something like the balancer I describe and came across this project, and if this seems like a good idea to you I'd love to try to implement this in the context of your app.

Hey @ravisantoshgudimetla; we spoke briefly about this at kubecon after the SIG-scheduler deep dive.
I wonder if a more holistic approach would be take each pod and run them through a copy of the scheduler, and see how "wrong" they are, then have some threshold after which an eviction would happen. For example, if a pod is currently on node X, but now node X has a much lower scheduling score than other nodes, evict the pod.
I'm afraid that any attempt to optimize for a specific thing (low/high node utilization, affinity, etc) has the risk of not taking the whole scheduling context into the picture, and could easily end up in pathological cases. For example, a node might be heavily utilized, but must be that way because of selectors/affinity, so continuing to evict from it would be useless.
I'm not sure if an approach like this would be possible, but if so, it could subsume the other strategies, and would get for free any improvements to the scheduler itself.

Hey @ravisantoshgudimetla, instead of descheduler you could try to optimise eviction policies to prevent OOM kills.
--system-reserved=memory=2Gi --eviction-soft=memory.available<5Gi --eviction-soft-grace-period=memory.available=5m
If you use the kubelet settings as above for example, it will trigger soft eviction and gracefully stop the the containers above the limit.
I'm not sure if it would help your case but you give it a try.

/kind feature

Sorry, I missed this. I think identifying the nodes that have better score for a given pod than the current node where the pod is running seems reasonable and is actually of the goals for descheduler. We're in the process of breaking k8s.io/scheduler dependencies and we think this strategy seems reasonable as @seanmalloy pointed out.

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale
/reopen

/remove-lifecycle rotten

/remove-lifecycle rotten
/reopen
Hey there! We hit a use-case where the nodeutilization plugin could not do much.
I did carefully read the comments and IMHO this BalanceNodeUtilization plugin idea is really cool to balance the pods across all nodes. It would be good load balancing practice for the cluster. FWIW, I think we should prioritize this plugin idea and discuss further about. cc @damemi @ingvagabund @seanmalloy
I'm not so sure about if nodeutilization and balanceutilization could mutually exclusive to run at same time. Please enlighten me here: Would be balanceutilization obsoletes the nodeutilization plugin? (Since nodes never go low/high utilization state since all will keep balanced by balanceutilization.)
As @lukemassa already mentioned:

Something like how many standard deviations away from the mean a given node is, but probably with the language of binomial distributions since these are percentages.

We can use standard deviation (with some margin of error (confidence interval)) to calculate drift/gap between lowest and highest pod counts accross Ready, Schedulable nodes.
Eventually we get something like:
apiVersion: "descheduler/v1alpha1"
kind: "DeschedulerPolicy"
strategies:
  "BalanceNodeUtilization":
     enabled: true
     params:
       maxAllowedStandardDeviationPercent: 5%

We are (w/ @eminaktas) volunteer to implement this plugin once we get agreement on this proposal!

See the Pods per Node metrics and our use-case below:

Most of the nodes are overutilized or appropriately utilized. The plugin doesn't get triggered because of:
lownodeutilization.go:118] "Criteria for a node under utilization" CPU=30 Mem=30 Pods=30
lownodeutilization.go:119] "Number of underutilized nodes" totalNumber=0
lownodeutilization.go:132] "Criteria for a node above target utilization" CPU=70 Mem=70 Pods=70
lownodeutilization.go:133] "Number of overutilized nodes" totalNumber=12
lownodeutilization.go:136] "No node is underutilized, nothing to do here, you might tune your thresholds further"

The idea is to keep all pod counts as balanced as possible per node! Eventually we expect ~45-50 pod counts per node. (as per the image above)
Waiting your thoughts!

I'm not sure I understand the difference between that and LowNodeUtilization. 30/70 are pretty wide thresholds for balancing utilization, so there will be variance in there. A closer threshold gap should trigger more evictions and ultimately lead to a more balanced state.
The other problem is that even if the descheduler calculates an optimal distribution, that doesn't mean those pods will get scheduled in that distribution. You would need a matching scheduler plugin to do that, and it would probably need to work in a batch scheduling format to consider all of the evicted pods at once.
But by default the scheduler does try to balance pods across nodes, prioritizing the lowest-utilized node. That's the idea behind LowNodeUtilization, bringing me back to my question that it's not clear to me how this differs. Maybe if you could provide an example it would help illustrate the idea?


Add method to easily override initial table records per page

Allows you to override the default records per page count (10) without having to override the entire getDefaultTableRecordsPerPageSelectOption method and all its other logic.
There may be a better name than "initial".

Maybe we should just move it to a property?

That would certainly be simpler, I only did it that way to mirror getTableRecordsPerPageSelectOptions().

Thanks :)


Pass cananocial name when updating records

The PowerDNS API spec requires a full canonical name when performing a REPLACE changeset,
however the power_dnsex wrapper is inconsistent with this spec in its update_record() method.
This fixes the inconsistency so that the record map behaves the same as the create_record()
method.
I wasn't able to figure out how to run the test suite, the setup seems developer-specific. I did check the update tests, and they are in fact using a full canonical name, so no adjustment may be necessary there.

This code has been moved to an internal repo, maybe we already fixed this. Anyway, I'll check if we fixed it, and update you.


Add "Movables Nodes" to the Scene

Those "Movable Nodes" can have n children (including Movable Nodes) and be moved.

Done in commit https://github.com/Sygmei/ObEngine/commit/35926495f3a4d437e5417466b8c99f4d13e16d65


Returned image uri produces security exception on Android

Description
The uri returned from Google Photos app can't be used due to security restrictions
There are two responses returned for the same file (note the URIs):
from Google Photos:
{"fileName": "20201104_185129.jpg", "fileSize": 4044295, "height": 2988, "isVertical": false, "originalRotation": 90, "path": "/storage/emulated/0/DCIM/Camera/20201104_185129.jpg", "timestamp": "2020-11-04T16:51:29Z", "type": "image/jpeg", "uri": "content://com.google.android.apps.photos.contentprovider/-1/1/content%3A%2F%2Fmedia%2Fexternal%2Fimages%2Fmedia%2F630/ORIGINAL/NONE/image%2Fjpeg/1388424768", "width": 5312}
from a third-party app:
{"fileName": "20201104_185129.jpg", "fileSize": 4044295, "height": 2988, "isVertical": false, "originalRotation": 90, "path": "/storage/emulated/0/DCIM/Camera/20201104_185129.jpg", "timestamp": "2020-11-04T16:51:29Z", "type": "image/jpeg", "uri": "content://media/external/images/media/630", "width": 5312}
How to repeat issue and example
(The same problem was mentioned in the issue #1380)
Steps:

Call ImagePicker.showImagePicker in your code
Select an image using Google Photos (!)
Try to access the selected image file by the returned URI

Result:
an error
Permission Denial: reading com.google.android.apps.photos.contentprovider.MediaContentProvider uri content://com.google.android.apps.photos.contentprovider/-1/1/content%3A%2F%2Fmedia%2Fexternal%2Fimages%2Fmedia%2F630/ORIGINAL/NONE/image%2Fjpeg/1388424768 from pid=18891, uid=10128 requires the provider be exported, or grantUriPermission()
Solution
I've not digging deep into it, just noted and wish to inform you so you'll be able to handle it somehow.
I'll try to use path value instead of uri value.
Additional Information

React Native version: 0.63.2
Platform: Android
Development Operating System: Windows
Dev tools: Android SDK version 29

Check the breaking changes and upgrade to version 3.0.0-vnext.4


[BUG] Receive 'Not Authorised' when using Custom JWT Authentication

Environment
We are running with the following setup:

Local FormIO Server
NodeJS API (Authenticates with IDS + Serves FormIO Token)
React Web App (Rendering FormIO Form using '@formio/react')

Hosting type

[ ] Form.io
[x] Local deployment

FormIO Version: 3.0.0-rc.10
@formio/react Version: 5.2.4-rc.1
formiojs version: 4.14.9
Frontend framework: React
Browser: Chrome
Browser version: 107

Steps to Reproduce

Login + Add FormIO JWT token (formioToken) to Local Storage
Load FormIO form
Make FormIO request
Receive 'Not Authorised' error message

Expected behavior
'formioToken' should remain in local storage and Web App should be allowed to make requests to FormIO.
Observed behavior
'formioToken' is removed from local storage once the Form is loaded and the Web App is now not authorised to make requests to FormIO.
Additional Information
Our Custom JWT auth worked with 'react-formio' v3 ('formiojs' v3). However when we moved to 'react-formio' v4 or '@formio/react' v4/5 (all using 'formiojs' v4) this bug appeared.
Our 'formioToken' is successfully placed into Local Storage, however when we load a form the 'formio.js' code errors out with 'Bad Token' here:

The token is then removed immediately from local storage and any subsequent FormIO requests are unauthorised.
I believe it is the same issue as the one this PR is trying to solve

Possible solved, but we just had the same problem and solved it by checking the setting of the apiurl in the Formio Setup. Because it was not set, the request for cecking the token goes to https://api.form.io/current. And at this endpoint the token validaten failed.
When we add sth like that:
Formio.setApiUrl(apiUrl);
where apiUrl contains the url of the correct formio Server, the error does not occur, and all things are working fine.

@buecki2018 can you show how you used it?

Not exactly, because i am not longer  involved in  project. But i remember that i simply do the Formio.setApiUrl(apiUrl); before using the Formio package.
And i think possible the error isn't still exist, because its one year ago?

@jasonsegal23 are you still reproducing this issue on the latest versions?

Thank you for your contribution. As this issue has been inactive for over 90 days, I will close it for now. If you wish to reopen the issue, please respond and we can resume the triage process.


Sound now plays on locked iOS device (fixes #526)

On my tests with an iPhone 6, using AudioCache, no sound started to play after device was locked.
Adding this one line fixed it:
        [[UIApplication sharedApplication] beginReceivingRemoteControlEvents];

Hope it can get merged! Thanks a lot for your great work!

@HugoHeneault do you know why it is so? PR LGTM but I'm not sure I understand why this is needed or at all related to your problem.

@luanpotter This methods seems to be required for showing controls on locked screen for iOS. It's not showing controls but seems to allow playing sound while device is locked. I don't know why, but I found many Stackoverflow threads writing about it...

Awesome, thanks! 👏


Compile Popup Msg ng-click w/ Controller As syntax

I am using Controller As syntax and am trying to get the popup to compile my html message using the settings below. Controller 'X' is known as dep in the html, and the alert function is defined in the controller as such.
vm.alert= function() {
    alert('hi');
 }

vm.mapMarkers.push({
   lat : 40.703289,
   lng : -74.014192,
   message : "
howdy
",
   compileMessage : true,
   getMessageScope : function() { return vm; },
   layer : 'vehicles'
})

It throws this error
Uncaught TypeError: c.$apply is not a function.
I am using packages:
"angular": "^1.4.7",
"angular-leaflet-directive": "^0.9.0",
"leaflet": "^0.7.7"
Any ideas?

Please, could you provide a jsfiddle showing this behaviour? You could use this jsfiddle as a starting point:
http://jsfiddle.net/maistho/9jymzymu/
I'm actually reworking all the code to make it compatible with Leaflet 1.0 and start the compatibility with Angular 2.0, but I can take a look at your problem if it's a bug generic enough.
I'm closing the issue, but will reopen if you provide the jsfiddle. Thanks

The example jsfiddle isn't showing any markers.

Here is the jsfiddle as requested, http://jsfiddle.net/bz5s7ybm/2/
Please reopen this issue and advise.
Thanks so much for your help,
Dan

Great, maybe @davidovich could help you, since he was the dev who coded this functionality.
I could take a look at it when I finish all the reestructuration of the code.

The example works though, and it is almost the same use case:
Please verify that you are using validated versions of leaflet and angular-leaftlet-directive.

@davidovich , seems the problem is related with using the controller with the "controller as" syntax introduced in angular 1.2. Old syntax is working perfectly as you say.

I updated the fiddle with the following dependencies.
I am using packages:
"angular": "^1.4.7",
"angular-leaflet-directive": "^0.9.0",
"leaflet": "^0.7.7"
Without controller as syntax (working)
http://jsfiddle.net/bz5s7ybm/21/
With controller as syntax
http://jsfiddle.net/bz5s7ybm/22/

I have not understood everything that is going on, but it works if you return the $scope in getMessageScope():
http://jsfiddle.net/bz5s7ybm/25/
I got my inspiration from:
http://toddmotto.com/digging-into-angulars-controller-as-syntax/

Great solution @davidovich, closing the issue as it's solved now.

good work! thx guys!!!!!!

What if the marker is being created in a factory service? The $scope passed into the service doesn't handle the same as in the controller example on jsfiddle.

Please, can you provide another jsfiddle with this new behaviour?

Here is an example using a factory service and Controller As syntax. Thx in advance for taking a look.
http://jsfiddle.net/bz5s7ybm/28/

Not sure if this is the correct way of doing things but why not just pass your scope to the service?
http://jsfiddle.net/2jm5L3yg/

No, that does not work. When clicking on the ngClick marker, alert dialog should show -- it does not in your updated fiddle.

@jessertaylor is right, this does work. there is no magic here, you need to pass the scope.
here is a small variant (only using scope in the make function)
http://jsfiddle.net/bz5s7ybm/33/
@tombatossals I think this is safe to close, @dkromp has evidently not investigated this thoroughly enough.

Excellent! Great work.

Thanks @jessertaylor @davidovich , you are great guys.


problem

What version of Wallet are you using?
Version: 0.7.2
What is happening?
https://fuellabs.github.io/swayswap/ and swap assets
It does not work properly
steps to reproduce
f
How it should behave?
f
What os are you seeing the problem on?
Windows Desktop
What browser?
Chrome
What is your browser version?
chrome last version

@taher636465 Thanks for reporting. On the following issues, please provide more information about the error to enable the team to understand better and be able to act on it.
Our network was unstable in the past weeks, causing transactions to be very slow and not finishing the execution. I will assume this was the issue you were seen. Please open a new issue in case you are seen this errors yet with more detailed information.


Use a custom README for the combined installer that explains how to inst...

...all.

@brson: no appropriate reviewer found, use r? to override

r? @steveklabnik
This replaces the README.md file inside the combined installer with one that explains how to install, not build from source.

@bors: r+ fc1d42a


Add a way to create a application credentials json file

Sometime it is easier to use authentication helpers to manage authentication as it means same code for different scenario (like running a process in your computer, on a CI or on production )
I added this option. In a way, it is not really linked to the core of this action, but as it is really really close, I feel it can be easier to have this option here.

I knew this PR would not be correct the first try as I wasn't 100% satisfied with it, but thank you to correct it by yourself by integrating it to the core action!
Note:  I added the if (idTokenAudience === '') {   because the API (hence the action) return a 400 bad request error without specifying the audience is mandatory.  It is a little bit frustrating because you may not be 100% sure of your workload identity setup and you tend to update this setup instead of the action configuration.   Perhaps adding a code in the catch(error)  like ' if token is idtoken and audience is not given then print "You may have forgotten to set audience" '  is a good compromise.


Info button on recordset page

The "?" button on the recordset page seems unnecessary to me and inconsistent in behavior.  It looks like a button, but it doesn't do anything if you push it, and it has information about the search box.  I would put the contents of the tooltip for this button on the magnifying glass (which has no tool tip) and eliminate this button.

@karlcz @robes @jrchudy @howdyjessie @RFSH @chiragsanghvi any objection?

Seems reasonable to me and should be simple to change.

No objection here.

No objection.


CI: K8sCustomCalls Basic test with byte-counter Loads byte-counter and gets consistent values

Test fail did not produce any artifacts nor normal test fail reports, so the title is gobbled up from the test logs. The error message is:
timed out waiting for pod bytecounter-compiler in namespace default to be ready: 4m0s timeout expired

This was the first test in the job, which may be significant for reproduction, so the whole log is copied below:
11:04:41  + cd /home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test
11:04:41  + HOME=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next ginkgo --focus=K8s -v --failFast=false -- -cilium.provision=false -cilium.timeout=170m -cilium.kubeconfig=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test/vagrant-kubeconfig -cilium.passCLIEnvironment=true -cilium.runQuarantined=false -cilium.image=quay.io/cilium/cilium-ci -cilium.tag=426bb86118a40ff9deeb036a7547d7286c3cf3df -cilium.operator-image=quay.io/cilium/operator -cilium.operator-tag=426bb86118a40ff9deeb036a7547d7286c3cf3df -cilium.hubble-relay-image=quay.io/cilium/hubble-relay-ci -cilium.hubble-relay-tag=426bb86118a40ff9deeb036a7547d7286c3cf3df -cilium.operator-suffix=-ci
11:05:23  Running Suite: Suite-k8s-1.16
11:05:23  =============================
11:05:23  Random Seed:<PHONE_NUMBER>
11:05:23  Will run 154 of 451 specs
11:05:23
11:05:23  S
11:05:23  ------------------------------
11:05:23  K8sCustomCalls Basic test with byte-counter
11:05:23    Loads byte-counter and gets consistent values
11:05:23    /home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:518
11:05:23  08:05:21 STEP: Running BeforeAll block for EntireTestsuite
11:05:23  08:05:21 STEP: Starting tests: command line parameters: {Reprovision:false HoldEnvironment:false PassCLIEnvironment:true SSHConfig: ShowCommands:false TestScope: SkipLogGathering:false CiliumImage:quay.io/cilium/cilium-ci CiliumTag:426bb86118a40ff9deeb036a7547d7286c3cf3df CiliumOperatorImage:quay.io/cilium/operator CiliumOperatorTag:426bb86118a40ff9deeb036a7547d7286c3cf3df CiliumOperatorSuffix:-ci HubbleRelayImage:quay.io/cilium/hubble-relay-ci HubbleRelayTag:426bb86118a40ff9deeb036a7547d7286c3cf3df ProvisionK8s:true Timeout:2h50m0s Kubeconfig:/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test/vagrant-kubeconfig KubectlPath:/tmp/kubectl RegistryCredentials: Benchmarks:false Multinode:true RunQuarantined:false Help:false} environment variables: [JENKINS_HOME=/var/jenkins_home ghprbSourceBranch=visibility-policy-fix-up<EMAIL_ADDRESS>VM_MEMORY=8192 MAIL=/var/mail/root KUBEPROXY=0 SSH_CLIENT=<IP_ADDRESS> 49670 22<EMAIL_ADDRESS>USER=root PROJ_PATH=src/github.com/cilium/cilium RUN_CHANGES_DISPLAY_URL=https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/1178/display/redirect?page=changes ghprbPullDescription=GitHub pull request #16258 of commit 426bb86118a40ff9deeb036a7547d7286c3cf3df, no merge conflicts. NETNEXT=1 ghprbActualCommit=426bb86118a40ff9deeb036a7547d7286c3cf3df SHLVL=1 CILIUM_TAG=426bb86118a40ff9deeb036a7547d7286c3cf3df NODE_LABELS=baremetal ginkgo nightly node-selected-gobbler vagrant HUDSON_URL=https://jenkins.cilium.io/ GIT_COMMIT=5a1178f7ab7288ec8993c6a33e9c9ef9f3ab670e OLDPWD=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next GINKGO_TIMEOUT=170m HOME=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next ghprbTriggerAuthorLoginMention=@jrajahalme BUILD_URL=https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/1178/ ghprbPullAuthorLoginMention=@jrajahalme HUDSON_COOKIE=2d84d0ae-0aa1-44a4-bfe5-1efe1ba06345 JENKINS_SERVER_COOKIE=durable-566a7e299b40ade7629ede0388948e1f ghprbGhRepository=cilium/cilium DOCKER_TAG=426bb86118a40ff9deeb036a7547d7286c3cf3df JobKernelVersion=net-next KERNEL=net-next CONTAINER_RUNTIME=docker WORKSPACE=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next ghprbPullLongDescription=Adjust and expand eBPF policy map keys and values to redirect for\r\nvisibility on the port of the visibility annotation while still\r\ndenying traffic on this port for identities for which the traffic is\r\ndenied.\r\n\r\nDatapath lookup order is, from highest to lowest precedence:\r\n1. L3/L4\r\n2. L4-only (wildcard L3)\r\n3. L3-only (wildcard L4)\r\n4. Allow-all\r\n\r\nThis means that the L4-only allow visibility key can only be added if\r\nthere is an allow-all key, and all L3-only deny keys are expanded to\r\nL3/L4 keys. If no L4-only key is added then also the L3-only allow\r\nkeys need to be expanded to L3/L4 keys for visibility redirection. In\r\naddition the existing L3/L4 and L4-only allow keys need to be\r\nredirected to the proxy port, if not already redirected.\r\n\r\nThe above can be accomplished by:\r\n\r\n1. Change existing L4-only ALLOW key on matching port that does not already\r\n   redirect to redirect.\r\n   - e.g., 0:80=allow,0 -> 0:80=allow,<proxyport>\r\n2. If allow-all key exists, add L4-only visibility redirect key if the L4-only\r\n   key does not already exist.\r\n   - e.g., 0:0=allow,0 -> add 0:80=allow,<proxyport> if 0:80 key does not exist\r\n     - this allows all traffic on port 80, but see step 5 below.\r\n3. Change all L3/L4 ALLOW keys on matching port that do not already redirect to\r\n   redirect.\r\n   - e.g, <ID1>:80=allow,0 -> <ID1>:80=allow,<proxyport>\r\n4. For each L3-only ALLOW key add the corresponding L3/L4 ALLOW redirect if no\r\n   L3/L4 key already exists and no L4-only key already exists and one is not added.\r\n   - e.g., <ID2>:0=allow,0 -> add <ID2>:80=allow,<proxyport> if <ID2>:80\r\n     and 0:80 do not exist and 0:80 was not added\r\n5. If a new L4-only key was added: For each L3-only DENY key add the\r\n   corresponding L3/L4 DENY key if no L3/L4 key already exists\r\n   - e.g., <ID3>:0=deny,0 -> add <ID3>:80=deny,0 if <ID3>:80 does not exist.\r\n\r\nWith the above we only change/expand existing allow keys to redirect, and\r\nexpand existing drop keys to also drop on the port of interest, if a new\r\nL4-only key allowing the port is added.\r\n\r\nAdjust the unit test to mimic the real behavior a bit better by\r\nregenerating endpoint policy after updating visibility policy. This is\r\nneeded due to the test using same port for HTTP and Kafka, and without\r\nregenerating visibility redirects no longer overwrite existing\r\nredirects.\r\n\r\nVisibility redirects need to be re-applied after applying incremental\r\npolicy map changes. This is due to incremental changes possibly adding\r\nkeys for new identities that need visibility redirections or\r\nadditional deny keys as defined above.\r\n\r\nTesting: New unit tests in policy package cover all the cases\r\ndescribed above.\r\n\r\nFixes: #9088\r\n\r\n```release-note\r\nPod L7 visibility annotations are now supported also when policy enforcement is enabled.\r\n```\r\n K8S_NODES=3 TESTDIR=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test LOGNAME=root NODE_NAME=node-selected-gobbler ghprbCredentialsId=ciliumbot _=/usr/bin/java HUBBLE_RELAY_IMAGE=quay.io/cilium/hubble-relay-ci STAGE_NAME=BDD-Test-PR GIT_BRANCH=origin/pr/16258/merge EXECUTOR_NUMBER=0 NO_CILIUM_ON_NODE=k8s3 ghprbTriggerAuthorLogin=jrajahalme TERM=xterm XDG_SESSION_ID=7 HOST_FIREWALL=0 CILIUM_OPERATOR_TAG=426bb86118a40ff9deeb036a7547d7286c3cf3df BUILD_DISPLAY_NAME=policy: Adjust existing policy for visibility annotations  https://github.com/cilium/cilium/pull/16258  #1178 ghprbPullAuthorLogin=jrajahalme HUDSON_HOME=/var/jenkins_home ghprbTriggerAuthor=Jarno Rajahalme JOB_BASE_NAME=Cilium-PR-K8s-1.16-net-next PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/go/bin:/root/go/bin sha1=origin/pr/16258/merge KUBECONFIG=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test/vagrant-kubeconfig FOCUS=K8s BUILD_ID=1178 XDG_RUNTIME_DIR=/run/user/0 BUILD_TAG=jenkins-Cilium-PR-K8s-1.16-net-next-1178 RUN_QUARANTINED=false CILIUM_IMAGE=quay.io/cilium/cilium-ci JENKINS_URL=https://jenkins.cilium.io/ LANG=en_US.UTF-8 ghprbCommentBody=test-me-please JOB_URL=https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/ ghprbPullTitle=policy: Adjust existing policy for visibility annotations GIT_URL=https://github.com/cilium/cilium ghprbPullLink=https://github.com/cilium/cilium/pull/16258 BUILD_NUMBER=1178 JENKINS_NODE_COOKIE=e5d0bff5-6a36-49f4-9e5c-5922ebcdd9c2 SHELL=/bin/bash GOPATH=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next RUN_DISPLAY_URL=https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/1178/display/redirect ghprbAuthorRepoGitUrl=https://github.com/jrajahalme/cilium.git FAILFAST=false HUDSON_SERVER_COOKIE=693c250bfb7e85bf ghprbTargetBranch=master JOB_DISPLAY_URL=https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/display/redirect K8S_VERSION=1.16 JOB_NAME=Cilium-PR-K8s-1.16-net-next PWD=/home/jenkins/workspace/Cilium-PR-K8s-1.16-net-next/src/github.com/cilium/cilium/test SSH_CONNECTION=<IP_ADDRESS> 49670 <IP_ADDRESS> 22 ghprbPullId=16258 CILIUM_OPERATOR_IMAGE=quay.io/cilium/operator HUBBLE_RELAY_TAG=426bb86118a40ff9deeb036a7547d7286c3cf3df JobK8sVersion=1.16 VM_CPUS=3 CILIUM_OPERATOR_SUFFIX=-ci]
11:05:23  08:05:22 STEP: Ensuring the namespace kube-system exists
11:05:23  08:05:22 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs")
11:05:25  08:05:24 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs") => <nil>
11:05:25  08:05:25 STEP: Preparing cluster
11:05:25  08:05:25 STEP: Labelling nodes
11:05:25  08:05:25 STEP: Cleaning up Cilium components
11:05:26  08:05:26 STEP: Running BeforeAll block for EntireTestsuite K8sCustomCalls
11:05:26  08:05:26 STEP: Ensuring the namespace kube-system exists
11:05:26  08:05:26 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs")
11:05:26  08:05:26 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs") => <nil>
11:05:26  08:05:26 STEP: Installing Cilium
11:05:28  08:05:27 STEP: Waiting for Cilium to become ready
11:06:54  08:06:40 STEP: Restarting unmanaged pods coredns-5495c8f48d-l8lwg in namespace kube-system
11:06:54  08:06:42 STEP: Validating if Kubernetes DNS is deployed
11:06:54  08:06:42 STEP: Checking if deployment is ready
11:06:54  08:06:42 STEP: Kubernetes DNS is not ready: only 0 of 1 replicas are available
11:06:54  08:06:42 STEP: Restarting Kubernetes DNS (-l k8s-app=kube-dns)
11:07:54  08:07:53 STEP: Waiting for Kubernetes DNS to become operational
11:07:54  08:07:53 STEP: Checking if deployment is ready
11:07:54  08:07:53 STEP: Checking if kube-dns service is plumbed correctly
11:07:54  08:07:53 STEP: Checking if pods have identity
11:07:54  08:07:53 STEP: Checking if DNS can resolve
11:07:54  08:07:54 STEP: Validating Cilium Installation
11:07:54  08:07:54 STEP: Performing Cilium controllers preflight check
11:07:54  08:07:54 STEP: Performing Cilium status preflight check
11:07:54  08:07:54 STEP: Performing Cilium health check
11:07:56  08:07:55 STEP: Performing Cilium service preflight check
11:07:56  08:07:55 STEP: Performing K8s service preflight check
11:07:57  08:07:56 STEP: Waiting for cilium-operator to be ready
11:07:57  08:07:56 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator")
11:07:57  08:07:56 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator") => <nil>
11:07:57  08:07:56 STEP: Making sure all endpoints are in ready state
11:07:59  08:07:58 STEP: Compiling custom byte-counter program
11:07:59  08:07:58 STEP: WaitForSinglePod(namespace="default", podname="bytecounter-compiler")
11:12:12  08:11:58 STEP: waitForSinglePod(namespace="default", podname="bytecounter-compiler", minRequired=1) => timed out waiting for pod bytecounter-compiler in namespace default to be ready: 4m0s timeout expired
11:12:12  08:12:08 STEP: cmd: kubectl describe pods -n default bytecounter-compiler
11:12:12  Exitcode: -1
11:12:12  Err: signal: killed
11:12:12  Stdout:
11:12:12
11:12:12  Stderr:
11:12:12
11:12:12
11:12:12  FAIL: bytecounter-compiler pod not ready after timeout
11:12:12  Unexpected error:
11:12:12      <*errors.errorString | 0xc000b00020>: {
11:12:12          s: "timed out waiting for pod bytecounter-compiler in namespace default to be ready: 4m0s timeout expired",
11:12:12      }
11:12:12      timed out waiting for pod bytecounter-compiler in namespace default to be ready: 4m0s timeout expired
11:12:12  occurred
11:12:12  === Test Finished at 2021-07-30T08:12:08Z====
11:12:12  08:12:08 STEP: Running JustAfterEach block for EntireTestsuite K8sCustomCalls
11:13:12  ===================== TEST FAILED =====================
11:13:12  08:13:08 STEP: Running AfterFailed block for EntireTestsuite K8sCustomCalls
11:14:12  cmd: kubectl get pods -o wide --all-namespaces
11:14:12  Exitcode: -1
11:14:12  Err: signal: killed
11:14:12  Stdout:
11:14:12
11:14:12  Stderr:
11:14:12
11:14:12
11:14:12  Fetching command output from pods []
11:14:12  ===================== Exiting AfterFailed =====================
11:14:12  08:14:08 STEP: Running AfterEach for block EntireTestsuite K8sCustomCalls Basic test with byte-counter
11:18:26  FAIL: terminating containers are not deleted after timeout
11:18:26  Expected
11:18:26      <*errors.errorString | 0xc000b00820>: {
14:04:29          s: Sending interrupt signal to process
14:04:39  cleaning up VMs started for k8s tests
14:04:39
14:04:39  ---------------------------------------------------------
14:04:39  Received interrupt.  Running AfterSuite...
14:04:39  ^C again to terminate immediately
14:04:39
14:04:39  Ginkgo ran 1 suite in 2h59m48.627810181s
14:04:39  Test Suite Passed

https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/1178/execution/node/129/log/
No artifacts were generated, no indication what failed on the job: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/1178/

Some related artifacts (missing the test-specific artifact as said above):
test_results_Cilium-PR-K8s-1.16-net-next_1178_BDD-Test-PR.zip
consoleText.txt


[Backport workspace]Patch/first pr (#194)

temp: add unit test

feat: add function test for workspace CRUD routes

feat: use saved objects client instead of internal repository

feat: update CHANGELOG

feat: exclude permission check wrapper

feat: add integration test

feat: add configuration

feat: enable workspace flag when run workspace related test

Description

Issues Resolved

Screenshot

Testing the changes

Check List

[ ] All tests pass

[ ] yarn test:jest
[ ] yarn test:jest_integration
[ ] yarn test:ftr

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] Update CHANGELOG.md
[x] Commits are signed per the DCO using --signoff

Codecov Report

Merging #196 (58f995b) into workspace (a2abcf2) will decrease coverage by 11.05%.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           workspace     #196       +/-   ##
==============================================
- Coverage      66.09%   55.05%   -11.05%
==============================================
  Files           3420     1191     -2229
  Lines          65752    24052    -41700
  Branches       10589     4028     -6561
==============================================
- Hits           43461    13242    -30219
+ Misses         19650    10155     -9495
+ Partials        2641      655     -1986

Flag
Coverage Δ

Linux_1
?

Linux_2
55.05% <ø> (ø)

Linux_3
?

Linux_4
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2589 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@SuZhou-Joe It looks some tests are failed

@SuZhou-Joe It looks some tests are failed

Indeed, it is due to:


refactor(multiple): ensure compatibility with TypeScript 4.3

See individual commits.

@jelbourn I added target: patch because nothing really affected components. Let me know if this should be target: minor though.


[google-cloud-cpp] fix feature name

Actually enable the experimental-storage-grpc feature.  We renamed the feature upstream, and failed to update the port.

The Windows builds seem to be stuck. I think this change is ready for review.

The Windows builds seem to be stuck. I think this change is ready for review.

Sorry about that, we had a bit of a double infrastructure SNAFU :).
Thanks for the fix!


Using Ecozy integration

Hi,
I have been trying to use the Ecozy integration to get the thermostat to work with iobroker, but have hit a bit of a wall:
Things i got to work:
thermostat_local_temperature,
thermostat_local_temperature_calibration,
thermostat_occupied_heating_setpoint,
thermostat_remote_sensing,
thermostat_control_sequence_of_operation,
thermostat_system_mode

Things which i did not get to work, and suspect won't work:
thermostat_unoccupied_heating_setpoint - accessing this this datapoint directly via the debug option in the adapter returns a "unsupAttribute" error message
thermostat_occupancy - can be read, but does not seem to be reported by the thermostat

Things i struggle with

runningMode (30) can be read from the thermostat, but does not change from "idle"
the Thermostat does not seem to change its valve position, The valve is constantly open, and only moves if set to pair / repair, this matches the fact that the running mode always returns idle.
...weekly_shedule - any time i access this the system crashes, i assume i do not have the correct message format.
i have been trying to formulate a message to be sent using the developer tab on the zigbee adapter, but so far have been unsuccessful, i always got the response

 {"err":"The argument object has incorrect properties"}

Right now, i am working off the assumption that the thermostat needs a schedule to start controlling the valve, but i have been unable to identify the message format / content needed to set a schedule, nor the correct properties to read a schedule off the thermostat.
(see comment on pull request on @sebastianheierhoff ,s fork - https://github.com/sebastianheierhoff/zigbee-shepherd-converters/commit/0bf5916c47f035e494d49568abddb902af4aef40)

Some of what you wrote might be correct, as the ecozy implementation is still far from perfect and hasn't been tested a lot. Unfortunately I don't have much time at the moment.
Did you check: http://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html? There is a part regarding message structure.
I will try to have a look at this tomorrow/Monday.

Thank you for the information. I will cross that with my notes and see if i can get somewhere.

For basic heating, you don't need a schedule. Sending the desired room temperature to the set topic as occupied_heating_setpoint is sufficient.

that's the thing.. the thermostat does not seem to close the valve, even if i set the target temp to 15 degrees with current temp at 22

What does system_mode say?

System mode is set to auto (1). I also tried heat (4)
The running_state never changes from 0 (idle), but that one is read only, as reported by the thermostat when trying to set it directly

That's really strange. Even without being paired to an active Zigbee2mqtt instance, my ecozy opens and closes the valve depending on the heating setpoint and the current room temperature.

Any updates?

I've been travelling, so no updates. I'll give it a go again this week and let you know.

I can confirm eCozy behaves rather unpredictable and wonky. I have more or less experience the same behavior as you although it seems to come good after a while.
Currently I'm implementing and testing a few changes:

pi_heating_demand and voltage conversion from here: https://github.com/ckpt-martin/Hubitat/blob/master/eCozy/eCozy-ZigBee-Thermostat-Driver.groovy
One of my two eCozy devices reports some time stuff upon pairing so I've added fz.generic_time and fz.generic_time_change to devices.js
Decrease the reporting intervals of temperature to hopefully increase the currently rather poor battery life. Why was it ever set to report every 5-30 seconds?

However the main problem I'm running into is that calling (cb) => device.report('hvacThermostat', 'pIHeatingDemand', 60, 600, 1, cb) results in a reporting configuration timeout BUT the device actually does seem to start reporting it and I haven't quite figured out why yet.
Last but not least I'm going to try and log pi_heating_demand now to see if my thermostats actually do anything.

I also get stuff like this in the debug console:
Received zigbee message of type 'attReport' with data '{"cid":"hvacThermostat","data":{"128":2529,"129":2736,"130":2600}}' of device 'Thermostat' (0x70b3d5de000008e2)

Any idea what that could be @Koenkk ?

@Zagitta these are report from the thermostats, I'm not sure what the data inside means, this has to be reverse engineered.

Decrease the reporting intervals of temperature to hopefully increase the currently rather poor battery life. Why was it ever set to report every 5-30 seconds?

My ecozy branch was integrated to enable more people to test the thermostat and continue developing the functionality. For testing purposes the regular reporting was helpful. I agree, that battery life is poor, though.

I bought a complete set with base yesterday.
I will sniff the complete procedure and provide the data.
Based on this data we should revise the converter area accordingly!

Unstar


Add Support for Conversations API

Support conversations API included from Mastodon 2.6.0 (tootsuite/mastodon#8832, https://docs.joinmastodon.org/methods/timelines/conversations/).

GET /api/v1/conversations
DELETE /api/v1/conversations/:id
POST /api/v1/conversations/:id/read

Codecov Report

Merging #126 into master will increase coverage by 0.01%.
The diff coverage is 81.81%.

@@            Coverage Diff            @@
##           master    #126      +/-   ##
=========================================
+ Coverage   80.09%   80.1%   +0.01%
=========================================
  Files          29      29
  Lines        1492    1503      +11
=========================================
+ Hits         1195    1204       +9
- Misses        204     205       +1
- Partials       93      94       +1

Impacted Files
Coverage Δ

status.go
85.62% <81.81%> (-0.29%)
:arrow_down:

Continue to review full report at Codecov.

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

LGTM, Thank you.


Solution for vmware disks needed

Find a solution for vmware disk creation needed, sucks in git

Try disk online resizing

move to submodule

-> submodule


[Bug]: Missing DrawerPortal, DrawerTrigger, DrawerClose in auto-import components

Reproduction
https://github.com/radix-vue/shadcn-vue/tree/dev/apps/www/src/lib/registry/default/ui/drawer
Describe the bug
Missing Drawer components: DrawerClose and DrawerTrigger as showing in demo
System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (6) x64 Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz
    Memory: 3.86 GB / 15.92 GB
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.21 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.14.3 - C:\Program Files\nodejs\pnpm.CMD
  npmPackages:
    nuxt: ^3.12.3 => 3.12.3
    radix-vue: latest => 1.9.0
    shadcn-nuxt: latest => 0.10.4

Contributes

[ ] I am willing to submit a PR to fix this issue
[ ] I am willing to submit a PR with failing tests

Here's what nuxt says about usage npm packages components (link).
Example of usage:
// ~/modules/create-component.ts
import { addComponent, defineNuxtModule } from 'nuxt/kit'

export default defineNuxtModule({
  setup() {
    addComponent({
      export: 'DrawerPortal',
      name: 'UiDrawerPortal',
      filePath: 'vaul-vue',
    })

    addComponent({
      export: 'DrawerClose',
      name: 'UiDrawerClose',
      filePath: 'vaul-vue',
    })

    addComponent({
      export: 'DrawerTrigger',
      name: 'UiDrawerTrigger',
      filePath: 'vaul-vue',
    })
  },
})

Some of the components were directly exported from the main package entry
https://github.com/radix-vue/shadcn-vue/blob/dev/apps/www/src/lib/registry/default/ui/drawer/index.ts#L1
because there was no need to create another component around those components

To solve missing auto-import components you need to use shadcn-nuxt module to take care of this issue

shadcn-nuxt

shadcn-nuxt is installed but, and components path is default, but I still don't understand how to fix it


Adding information regarding hackathons and other popular tech events.

Please explain your issue or the feature you are requesting properly.


Add missing util require in scripts.gui.functions

I guess i can add that i would remove "util" from "Lua.diagnostics.globals" in settings.json for vscode.
Jarg has it in his template, which may be where you got it from.
Just my opinion.


Added sprinkle theme

Designed a new theme to attract user base in your website
Issues #14

Looks Nice. Great Work!


AVRO-3789: [java] fix map comparison in GenericData

What is the purpose of the change
Fix map comparison in GenericData (AVRO-3789).
Verifying this change
See the new tests. These all failed before I changed the implementation.
Documentation
n/a

@RyanSkraba Any update on the forthcoming 1.11.3 release? It is now almost 2 months later and this bug makes 1.11.2 hard to use.


Support transform functions with AVG aggregation function

Support queries like:
SELECT AVG(SUB(col1, col2) FROM foo
SELECT AVG(SUB(DIV(col1, col2), DIV(col3, col4))) FROM foo
They were failing in AvgAggregationFunction as TransformBlockValSet() did not implement getValueType() method
Also added operand checks for transform functions for acceptable data types
Testing:
Added TransformQueriesTest to test both inner-segment and inter-segment, inter-server queries with custom data

cc @mayankshriv

Addressed review comments

Codecov Report

Merging #4550 into master will increase coverage by 0.01%.
The diff coverage is 73.62%.

@@             Coverage Diff              @@
##             master    #4550      +/-   ##
============================================
+ Coverage      64.4%   64.41%   +0.01%
  Complexity       20       20
============================================
  Files          1064     1064
  Lines         55307    55375      +68
  Branches       8061     8065       +4
============================================
+ Hits          35620    35672      +52
- Misses        17053    17076      +23
+ Partials       2634     2627       -7

Impacted Files
Coverage Δ
Complexity Δ

...core/operator/docvalsets/TransformBlockValSet.java
18.75% <100%> (+1.72%)
0 <0> (ø)
:arrow_down:

...orm/function/SingleParamMathTransformFunction.java
76.78% <50%> (-11.68%)
0 <0> (ø)

.../transform/function/AdditionTransformFunction.java
81.48% <73.33%> (-13.98%)
0 <0> (ø)

...form/function/MultiplicationTransformFunction.java
81.48% <73.33%> (-13.98%)
0 <0> (ø)

...ansform/function/SubtractionTransformFunction.java
79.26% <76.92%> (-14.68%)
0 <0> (ø)

.../transform/function/DivisionTransformFunction.java
79.26% <76.92%> (-14.68%)
0 <0> (ø)

...e/impl/dictionary/LongOnHeapMutableDictionary.java
78.26% <0%> (-10.87%)
0% <0%> (ø)

... and 27 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 66d31d6...2ac1ab8. Read the comment docs.

Closing this one after discussing with @Jackie-Jiang. The new PR here is fewer changes -- https://github.com/apache/incubator-pinot/pull/4557


Login and manual url screens are not working on netifly deploy

May be it is a netifly issue or something but links like Login and SSAdmin are not working. Fix these

Will fix it!

Now it is working on but on different domain .


Change the return values of Rows.scan and Rows.scanat methods

Codecov Report

Merging #36 (b029087) into master (4c40f04) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##           master      #36   +/-   ##
=======================================
  Coverage   81.97%   81.97%
=======================================
  Files          12       12
  Lines        2164     2164
=======================================
  Hits         1774     1774
  Misses        390      390

Flag
Coverage Δ

unittests
81.97% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

lib/rows.lua
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


ARCGIS for MN

Looks good and works fine, wondering why we're using the JSON instead of the CSV via fetch.getArcGISCSVURL? @chunder insights?

I don't prefer one to the other, I just want it to work if something gets updated, and I'm not sure which is more stable.

I don’t have any reason to prefer one way over another. This code checks to be sure it’s getting freshly updated data, which will at least shout at us if it gets stale.


Fix array encoding for PostgresJAsyncContext

Array encoding respect empty values or values with double quotes for PostgresJAsyncContext
Fixes #2418
Problem
See #2418
Solution
Put double quotes around any element value. Replace " with \" in the value.
Checklist

[ ] Unit test all changes
[ ] Update README.md if applicable
[ ] Add [WIP] to the pull request title if it's work in progress
[ ] Squash commits that aren't meaningful changes
[ ] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

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

Thanks @aleksandr-vin for your contribution. Could you please add a test for this case and we'll get it merged.

Thanks @aleksandr-vin for your contribution. Could you please add a test for this case and we'll get it merged.

@deusaquilus I tried to run tests locally but didn't make it in my spare time.
After
docker-compose -f docker-compose-m1.yml  down && docker-compose -f docker-compose-m1.yml run --rm --service-ports setup

the tests are not compiling:
docker-compose -f docker-compose-m1.yml run --rm sbt sbt test:compile

Plus attempts to check them via CI have very long cycle.
Giving up to figure out how to fix the tests. If you can fix them easily, I'd appreciate that.

@aleksandr-vin Lets figure out how to get tests compiling for you locally.
What error are getting?
Also, I’m going to think about having a dev-specific CI pipeline e.g something that only compiles to one Scala target, maybe only to one database and/or project.

JAsync support has been dropped


ERROR: Could not build wheels for thinc, which is required to install pyproject.toml-based projects

Description
After cloning the repo I created the python and after that when I tried to install the libraries using pip install -r requirements.txt and pip install . I got this below error:
error: command '/usr/bin/gcc' failed with exit code 1
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for thinc
Failed to build thinc
ERROR: Could not build wheels for thinc, which is required to install pyproject.toml-based projects
[end of output]

Environment
OS: Ubuntu 23.04
Python: 3.12.2

Issue is resolved, The correct way to install the dependencies is:
pip install harmony


ASV_eval: embedding_model.ckpt loading fails

The config file
https://github.com/egaznep/VoicePAT/blob/a20f0532307d4ab7176f2272755a614f51b34519/evaluation/privacy/asv/asv_train/hparams/ecapa/hyperparams.yaml#L49C1-L53C51
intends to specify a filename.
On the other hand, the code from speechbrain interprets it as path, relative to pwd.
        for name in self.loadables:
if not self.is_loadable(name):
continue
save_filename = name + PARAMFILE_EXT
if name in self.paths:
source, filename = self.split_path(self.paths[name])
elif default_source is not None:
filename = save_filename
source = default_source
else:
raise ValueError(
f"Path not specified for '{name}', "
"and no default_source given!"
)
Hence the file could not be found.


AuthFlow: AuthFlow is an Identity & Access Management (IAM) system secured by the Flow Blockchain

AuthFlow: AuthFlow is an Identity & Access Management (IAM) system secured by the Flow Blockchain
Grant category
Please select one or more of:

[x] Open source maintenance
[x] Developer tools / services
[ ] Educational material

Description
AuthFlow is an on-chain Identity & Access Management system and a replacement for services like Amazon’s AWS IAM or Microsoft’s Azure Active Directory, secured by the Flow Blockchain. Working in partnership with Emerald City DAO, EmeraldID will be updated to be the sole public Identity Provider for AuthFlow.
Problem statement
Current blockchain-based authentication methods typically only allow a developer to confirm who a user is and has to utilize other Web2 authentication methods and services (ex. Auth0, Okta) to do anything beyond smart contract interactions. As we move into a Web3 world there are still many use cases that require secure access to Web2 technologies. Such as accessing simple things like role-based access control to an app’s functions or a simple backend.
How it Works Today
As a developer creating an application, you want to provide secure access to your app. You allow users to log in using their Web3 Wallets, in the case of the Flow blockchain this is a multi-step process that provides you with a user identifier (Flow address) proving ownership of their on-chain account. This process is done through the FCL account proof process which provides functionality to prove a user is in control of a Flow address. All other aspects of authentication, authorization and session management are up to the application.
This current Web3 solution puts a heavy burden on the DApp developer(s) requiring them to write an extensive backend system to manage user access and authorized access to functionality.
Proposed solution
AuthFlow is an on-chain Identity & Access Management system, essentially a replacement for services like Amazon’s AWS IAM, Microsoft’s Azure Active Directory, and Auth0. Utilizing the Flow Blockchain, AuthFlow will return control of user identification and authentication to the app developer and end-users by merging Web3 with known authentication methods like JWT and OAuth 2.0.
Each app will create its own AuthSystem with an Identity Provider that can be managed by multiple AuthSystemAdmins. To ensure the integrity of the Authentication System, once the contract is deployed, all keys will be removed from the account. This prevents any future modification of the contracts that change the way the system authenticates users.
AuthFlow is THE security solution for developers and end-users operating across Web2 and Web3 spaces. The functionality can be defined as an Identity Provider and Password Manager merged into one. Your wallet interacts with Web2 as a password manager across all websites and also serves as your identity provider on Web2 and Web3.
Identity Providers

AuthFlow Server (open source server you host privately)
Emerald ID (like sign in with Facebook, peripherally everywhere)

Configurable to be transparent to users about who the identity provider is (Emerald ID)

Business Citadel (Like Emerald ID, Business Citadel is a cloud-hosted Identity Provider (and so much more) but focused on the business sector and providing secure employee access to the Web2 world. We will share more information about Business Citadel soon!)

Server/Client SDKs

Server SDKs

Go (Golang)
NodeJS

Client SDKs

Swift
JS/NodeJS

Impact
Let’s face it, getting authentication right is complicated and one screw-up can lead to costly data leaks. The AuthFlow SDKs allow you to secure both your front and backend resources with easy-to-use methods that will verify which roles/permissions the user has, as well as evaluate any access policies to ensure users only have access to authorized resources.
The server SDKs not only allow you to protect server-side resources but also allow you to stand up your own Identity Provider server that supports JWT, oAuth2.0, and SAML2.0 authentication methods.
Currently, The security measures that are present in Web2 authentication offered by identity providers like Auth0, Amazon’s AWS IAM, or Microsoft’s Azure Active Directory are superior to those on Web3. Not only does AuthFlow protect its user from vulnerabilities in the Web3 space, but it will also tighten user security across Web2 sites.
AuthFlow is THE security solution for developers and end-users operating across Web2 and Web3 spaces.
Milestones and funding

Milestone
Deliverables
Timeline
Risks
USD proposal

1 - Contract Completion
Smart Contract containing auth-system, auth-system admin, identity provider and identity provider admin resources. Along with needed functions for Dapps to interact with the contract.
2 months
- Completion within timeline.
“TBD”

2 - Go (Golang) Server SDK
Go Server SDK with support for oAuth2
3 months
- Completion within timeline.  - Emerald Shield contract audits may require rewrites to the SDK specifications which would extended the overall project timeline.
“TBD”

3 - JS Client SDK
JS Client SDK with support for server and client-only modes
3 months
- Completion within timeline.  - Audits of server and client SDK’s may require rewrites to the SDK specifications which would extended the overall project timeline.
“TBD”

4 - AuthFlow Manager & EmeraldID upgrades.
Hosted management UI for AuthSystem Admins to manage their roles/permissions and policies without building their own UI.
3 months
- Team currently does not have a front-end developer to complete the front-end portion of this milestone, and intends to allocate a portion of funding to secure a front-end developer for the project.  - Upgrading EmeraldID to be an AuthFlow identity provider could require rewrites to the EmeraldID contract.
“TBD”

5 - Adoption & Feedback Changes
Feedback period to drive adoption and iron out issues/changes from developer feedback.
6 months
- Any issues, vulnerabilities discovered, or changes made from feedback could result in rewrites of all codebases
“TBD”

6 - Swift Client SDK
Swift Client SDK with support for server and client-only modes
3 months
- Completion within timeline.  - The FCL-Swift SDK has not been completed yet and specifically does not support account proofs yet, however the FCL-Swift SDK team received a grant to complete the SDK with current timeline estimation showing completion prior to work required on the Swift SDK..
“TBD”

7 - NodeJS Server SDK
NodeJS Server SDK with support for oAuth2
2 months
- Completion within timeline.
“TBD”

8 - SAML2.0 Support
Adding SAML2.0 support to the Go and NodeJS Server SDKs and AuthFlow Manager
3 months
- Completion within timeline.
“TBD”

9 - Ongoing Maintenance
Ongoing Maintenance and support for the SDKs
1 year
- Completion within timeline.
“TBD”

Team

Name
Role
Bio
Contact

Brian Pistone
Executive Team (Founder / Full-Stack Developer / Lead Engineer / Chief IT Guru)
With 2+ decades in IT/software development Brian has been successfully running an IT Managed Services Company since 2017.  His life long mission of helping businesses grow through the better use of technology has lead to him becoming proficient in PHP, NodeJS/JS, Swift, Go, and now Cadence.
<EMAIL_ADDRESS>

Ashton Mercer
Executive Team (Chief Development Guru)
Ashton has spent the past four years studying marketing and entrepreneurial management at Boise State University, his knowledge and expertise on startup's and new venture creation is crucial to the developmental success of AuthFlow.
<EMAIL_ADDRESS>

Jordan Roeske
Executive Team (Chief Legal Guru)
Jordan is a licensed Attorney operating in multiple states, who enjoys and excels at legal research. Jordan provides the AuthFlow team with necessary legal guidance as AuthFlow expands into unseen territories.
<EMAIL_ADDRESS>

Andrew Van Dyke
Executive Team (Chief Financial Guru)
Andrew is a financial advisor and strategist with expansive knowledge of financial markets and regulations. Andrew offers financial/accounting expertise and oversee's AuthFlows finances.
<EMAIL_ADDRESS>

Jacob Tucker
Cadence Developer / Emerald ID Manager
Jacob (aka God) was founder of the first DAO on the Flow Blockchain (Emerald City DAO) and needs no introduction in this space.
<EMAIL_ADDRESS>

thanks for the submission @BoiseITGuru. could you also add the USD proposal to each milestone for our review? thanks!

Few questions:

How do you solve privacy concerns of end-users?
How do you solve privacy concerns of dapps? Not all dapps want to expose their user-base on a public blockchain.
How do you comply with regulations such as GDPR?

thanks for the submission @BoiseITGuru. could you also add the USD proposal to each milestone for our review? thanks!

@alxflw Certainly!, when we originally copied the issue template it still had the option for leaving them TBD to allow your team to proposal amounts. I have a meeting with the rest of the team tomorrow afternoon, we will discuss this and will get back to you ASAP.

Few questions:

How do you solve privacy concerns of end-users?
How do you solve privacy concerns of dapps? Not all dapps want to expose their user-base on a public blockchain.
How do you comply with regulations such as GDPR?

@chandanworkacct
1 & 2. We are using String/Password-Based Asymmetric Key Derivation to encrypt data at the Identity Provider level, depending on what type of data is used a portion of the strings or "passwords" used to created the keys is generated using either the data itself and/or unique salts from both the dapp and Identity Provider. For example your reference in question 2 to dapps not wanting to expose their user-base to the public, any specific identifiers to the dapp or end user would be stored as an encrypted string on-chain, in the case of logging in the end user this encryption and decryption or as I like to think of it "data translation" is handled by the Identity Provider and our sdks during the account-proof verification process.

Since all on-chain user data used/generated by AuthFlow is encrypted and with the exception of previously mentioned encrypted identifiers data is stored in a resource in the end users account, almost all of the regulatory requirements would still fall to the dapp itself. However, our SDKs will have a function for the dapp to notify the Identity Provider they have received and completed a "right to be forgotten" request thus removing all identifiers from the Identity Provider to ensure compliance. We are also exploring options for using and monitoring for Flow Events through a removal request to punish, remove, or take some other actions against a dapp not complying with requests for removal.

Hi @BoiseITGuru!
Thanks for your previous responses the additional details - have 2 follow up questions for you:

Have you been able to frame out the USD amounts for each of the proposed milestones?
We'd love to better understand what an MVP would look like for this solution.  Given this size of this project, it would be helpful to understand how we can iterate upon landing an MVP.

Hi @BoiseITGuru - just wanted to follow up again on the two questions above so that we can push the review of this proposal forward, thanks!

Hi @BoiseITGuru - I'm going to close this issue out for now, but please feel free to re-open if/when you're ready to dive back in.  Thanks!


Efficiency fix

This PR significantly improved efficiency of the SMC sampler - SMC now scales linearly with number of particles used.

[Current coverage][cc-pull] is 61.90%

Merging [#4][cc-pull] into [master][cc-base-branch] will increase coverage by +0.26%

@@             master         #4   diff @@
==========================================
  Files            17         17
  Lines           490        504    +14
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            302        312    +10
- Misses          188        192     +4
  Partials          0          0

Powered by Codecov. Last updated by [d194039...d093704][cc-compare]
[cc-base-branch]: https://codecov.io/gh/yebai/Turing.jl/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/yebai/Turing.jl/compare/d19403998bd06ec17ba437f83ca1ec265493bd76...d093704a0ac712003355d979eb23facdddfafbfd
[cc-pull]: https://codecov.io/gh/yebai/Turing.jl/pull/4?src=pr

Can you add some comments in the definition of ParticleContainer to explain what conditional and n_consume are for?

These fields are reserved for implementing rejuvenation steps (e.g. SMC2) - I've added some comments. These code will become more readable when the rejuvenation step is implemented.


update documentation - AWS AMI search

Hello there,
I just updated the documentation about searching the AMI on AWS specifying to select the "Public images" repository (not the "Owned by me") and updated the images accordingly!

should be avoid by easy installation feature in scrapoxy 4.0.0
Thanks for your contribution!


Shadow activity to handle activity results

Closes #8
Added ShadowActivity, that handles onActivityResult after purchase process is finished. This activity is constrained to portrait orientation only to decrease chances of activity recreation and thus disconnecting from original cashier instance.
Added ShadowActivityTest

@nbarishok Great PR. Thanks for PR #29 in addition. I think you have a great argument with the app combat dependency here.


Feature/1.0 fix header mobile

Objective
What: Header element are centered and responsive for all size of screen
Type

[x] Bug Fix
[ ] New Feature
[ ] Performance Tweaks
[x] Style Tweaks
[ ] Code Refactoring
[ ] Documentation
[ ] Tests

Tested

Documented

[x] Have you documented in changed file using comments
[ ] Have you added instructions to the README if needed?

Task linked: CU-2y2j6xt Make the header responsive between laptop & mobile screensize


Eradicate the 'unique "key" prop' warnings

For the guides and Components/APIs, we would continuously get:
Warning: Each child in an array or iterator should have a unique "key" prop.
when rendering them.

This add key attributes to our DOM elements that did not have them in order
to remove this warning. It uses a random string generator to create unique keys.

Should we establish the key a different or better way?

I went full hammer on this and put key attributes on everything. May have
been overkill, but the warnings are gone.

Should I be more selective on what we put the key attribute on?

Also fixed a:
Warning: Unknown DOM property frameborder. Did you mean frameBorder?
issue as well.
Test Plan:

No more warnings

Guides still render the same
APIs still render the same (when applied with fix from
https://github.com/facebook/react-native/pull/8746)

By analyzing the blame information on this pull request, we identified @caabernathy and @janicduplessis to be potential reviewers.

I think adding a random key is not a good idea since no-key behaves the same as random-key. If you add random keys everywhere you will make rerendering slower because now it can't reuse things with the existing heuristics. The only place we should need a key is when we are putting stuff in an array - if you're just returning some jsx then you shouldn't need a key. See https://facebook.github.io/react/docs/reconciliation.html for more on this. I think it would be ok to either 1/ abandon this and live with the warning or 2/ figure out some sane key to put on the places where we do have a number of siblings.

more discussion of keys here: https://github.com/facebook/react/issues/1342

I hate the warning. It looks a bit clowny to have that on our own server :)
So, instead of the general hammer, we can try to be selective, like you suggest.

So random keys are always frowned upon it seems like. That may be an issue with the way we currently have the GettingStarted page toggler and stuff because even if we use static keys, we get duplicate key warnings as well.
Random keys solve that problem, but if they are bad, then they are bad. So gotta think about a better way.

Could you use a counter to generate the keys deterministically? Without looking closely, I'd expect these components not to render stateful DOM elements (they're not <input> components for example) so the key prop isn't actually important.
The idea is that the counter is just a variable defined at the top of render() and keys within the render method are just counter++. This way, two render() passes without any state changes will deterministically produce the same output, keeping render() idempotent.

Also most of those places with randomKey() in the diff don't need keys at all. We should define keys just where they're needed so they don't mislead people reading the code later.

Also most of those places with randomKey() in the diff don't need keys at all. We should define keys just where they're needed so they don't mislead people reading the code later.

Yeah, I have a local commit that reduces the number of keys only to those that don't produce the warnings.

@ide Could consider a counter of some sort, yes. Thanks for the idea. I still fear that the toggler we have for Getting Started might cause problems with a constant key. I will have to see.

I think we are on to something with the sequential key counter, @ide! Thanks! :D

@ide I am noticing that as I test every doc in our docs, when I think I have gotten rid of the warning, I click on another one that gives the warning because it has an element not found in another document (say blockquote or something).
Is there a reason NOT to just put a key on all DOM elements to future proof this problem? Instead of selectively putting a key on all the elements that we use now that are causing the warning?

Is there a reason NOT to just put a key on all DOM elements to future proof this problem? Instead of selectively putting a key on all the elements that we use now that are causing the warning?

That would probably work though I think it would be better to have spurious warnings than spurious keys.

I agree it would be better to have spurious warnings than spurious keys. The "right way" to handle this is to assign keys only when appropriate, and to never use random keys. So if someone someday goes and does this the right way, if we add random keys everywhere they'll just have to figure out which ones to undo. If we leave the warnings, then the warnings will tell this someone where keys are needed. The warnings only are relevant if you look at the console, right?

Ok. Well this can serve as a model to get started with in the future. I think you should have the sequentialKey module where you fix one or two places where warnings arise. Then you can have small subsequent pull requests to fix others that come up after that.


Reenable typescript compilation in 2.0

@paulbatum - I think we should backlog this. We never GA'd TypeScript on v1. We need to think though how we want to do this properly, if we offer it.

For anybody curious, our recommended approach is to do your typescript compilation locally and deploy the resulting JavaScript. There are some complexities that need to be addressed if we are going to provide built-in compilation support and we're not sure yet if its worth the investment (many users are already happy doing the compilation locally).


dashboard does not allow anyone but creating user

The dashboard will not function with anyone but the user who created the cluster despite adding users to map_users with groups   = ["system:masters"].
system:masters is supposed to be automatically bound to the cluster-admin role which the dashboard requires.
https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles
It may be that that is not true and system:masters is being only bound to the bootstrappers role

May need to add a https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs/resources/cluster_role_binding between "system:masters" and "cluster-admin".

double checking, this issue appears to have resolved itself. yay?


GCode Streamer  app for CNC Plotter

In this version of GCode Streamer created many modifications such as:

Files format sorted for downloading (.gcode)
Image of the drawing showing in the window
Bugs fixed

Changes by AlexPC2 accepted and confirmed.


After running the program once, gradle and curl cannot connect to certain https websites

Operating system / операционная система
Windows 10 21H2
Running as service / Запуск программы как сервис
I run it as a regular program / Запускаю программу обычным образом
Describe the bug / Опишите ошибку программы
After running 1_russia_blacklist_dnsredir.cmd once, certain programs cannot read certain websites. As of now, I found only three websites that curl has trouble connecting to (hangs with no output): blackspigot.com, repo.spongepowered.org and files.minecraftforge.net. Opening them in any browser works fine. I also noticed that it reads fine without https://. I tried many things to make it work again, including flushing the dns cache and trying to connect with goodbyedpi running, nothing worked.
Additional information / Дополнительная информация
I'm pretty sure this is a GoodbyeDPI problem, because I didn't install any software except this.

If the program is not running, it's not effective. The websites mentioned are not reachable due to the block in Russia.
https://community.cloudflare.com/t/russia-blocks-tls-v1-2-requests-to-cloudflare-edges/636460

I'm pretty sure these websites worked fine before running the program. repo.spongepowered.org and files.minecraftforge.net are Maven repositories, I had been using them for a long time now.

All these domains are Cloudflare-fronted.

I know.

This doesn't make any sense: it worked before, now these websites only open in browsers which don't have any bypassing extensions installed, and running GoodbyeDPI any-country doesn't work either.

fixed it, ran Disable-TlsCipherSuite -Name TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 in an admin powershell


Unable to overwrite module setting in 3.2

Expected behavior:
When I overwrite module to "amd" in my config, gulp-typescript should output amd modules. This works in 3.1.7, but is broken in 3.2.
Actual behavior:
gulp-typescript emits the default commonjs modules, which is not even in my tsconfig.json.
Your gulpfile:
var gulp = require("gulp");
var typescript = require("gulp-typescript");

var project = typescript.createProject("tsconfig.json", {module: "amd"});

gulp.task("default", function ()
{
    return gulp.src("src/*.ts")
               .pipe(project())
               .pipe(gulp.dest("dist"));
});

tsconfig.json
{
  "compilerOptions": {
    "module": "es6",
    "target": "es5",
    "sourceMap": false
  },
  "exclude": [
    "node_modules"
  ]
}

I created a minimal repro project here: https://github.com/gnomesley/gulp-typescript-overwrite

I think that this is fixed with ffd9e689df4572a00aab993552075535455742e3. Can you install gulp-typescript from GitHub and check whether this fixes your problems?

Seems to be working now. Thanks!

The fix is included in the new release, 3.2.1.


sorry, i have another question

in the second part we want to compute the capacitance?

exactly :)


Add support for right shift by amount larger than argument width

Solution to #69
Replacement for #85
Right shifting UInt by amount greater than or equal to width gives value 0 with width of 1, once zero-width wires are supported #65, it should probably return zero-width wire instead.
I decided to implement this change as a new pass because I couldn't see where else it would fit in. I'm not sure I like the pass name "Legalization", but I couldn't think of anything better and I can see there possibly being other similar transformations that could be added to the pass. I left the actual process of turning a standard right shift (ie. amount < width of argument) in the Verilog Emitter because this really is a Verilog backend specific change. In a C++ emitter, bit extraction would map to a shift and mask.
The test is added to the "integration" tests list. Ultimately the tests should be refactored, but this is a nice Chisel-generated self-testing circuit to check that this feature is supported.
The changes to the Width trait have some overlap with Width in WorkingIR, and I think refactoring of the InferWidths pass will clean up the overlap.

Before merging, need to check that this fixes https://github.com/ucb-bar/uncore/commit/417565332484b2094e1518449b3cb2d80eafb0bf


[Slack] Get slack conversations/threads from support channel into a spreadsheet file

User Story

As a [user role below]:
Carbon for IBM.com team member

I need to:
have all of the historical slack conversations in #carbon-for-ibm-dotcom in a spreadsheet file

so that I can:
begin to analyze the slack questions asked by adopters

Additional information

There should be APIs that can be used to extract this data
Had conversations about setting up a chatbot for being able to field questions in the channel, taasbot as a reference (follow-on work from this issue)
Would ideally also like to continually monitor the slack channel to always listen and learn constantly what adopters are asking (follow-on work from this issue)

Acceptance criteria

[ ] Provide a data dump of historical slack conversations in #carbon-for-ibm-dotcom
[ ] Ideally the way we extract data is something that we can leverage again in the future

Discovered that this feature has been disabled by admins, so the only approach at this point may be to tap into APIs, which appears to require setting up a Slack app.
@janchild also mentioned that there might be a way to capture conversations through a Slack custom workflow.

Looking more into API scopes that are allowed in our IBM slack, and doesn't appear that there will be a way to programmatically fetch conversation history either using the APIs.
The API that would be needed to fetch the conversation history is:
https://api.slack.com/methods/conversations.history
Two of the scopes necessary for this API to work are im:history and mpim:history, which are listed as the prohibited scopes for any app that can be installed on a workspace:
https://w3.ibm.com/w3publisher/slack-at-ibm/apps-integrations/app-governance-policy/old-app-integration-list

Unfortunately, I'll have to close this issue, couldn't find a way of getting this via API or export.


WAS9?

Hi,
first, thanks for modules! :)
And now to my problem.. I am trying to install WAS9, but I am getting following error:
failed: [was-poc-02] (item=com.ibm.websphere.ND.v90) => {"changed": false, "item": "com.ibm.websphere.ND.v90", "msg": "Failed installing package 'com.ibm.websphere.ND.v90'", "stderr": "CRIMA1270E ERROR: The IBM WebSphere Application Server Network Deployment  package requires the IBM SDK, Java Technology Edition, Version 8 package. Install IBM SDK, Java Technology Edition, Version 8 together with IBM WebSphere Application Server Network Deployment .\n\nExplanation: To function correctly, these packages must be installed together.\n\nUser Action: Add the specified package to your installation. If the package is not available, you might need to add repositories.\n", "stderr_lines": ["CRIMA1270E ERROR: The IBM WebSphere Application Server Network Deployment  package requires the IBM SDK, Java Technology Edition, Version 8 package. Install IBM SDK, Java Technology Edition, Version 8 together with IBM WebSphere Application Server Network Deployment .", "", "Explanation: To function correctly, these packages must be installed together.", "", "User Action: Add the specified package to your installation. If the package is not available, you might need to add repositories."], "stdout": "", "stdout_lines": []}

I saw issue #2, but nobody answered there.. so maybe here? :)

Ok.. so we can actually install it when id is like id: 'com.ibm.websphere.ND.v90, com.ibm.java.jdk.v8'. We wrote also some patch with my colleague.. under testing now.. so PR incoming! :)

Hi @ronnicek Thank you for reporting. I'm looking forward to your PR :)


Make compatible with latest version of infisical paths

Hi there, wondering if you could add the extra parameter that is available now in the infisical sdk for the folder paths:
ie secret = client.get_secret("API_KEY", environment="dev", path="/")
Thanks

I added options for both env and path. For example:
- name: Print secret specifying an environment and path
  debug: msg="{{ lookup('scareyo.infisical.infisical', 'TEST_FOLDER_VALUE', env='staging', path='/folder') }}"

Awesome thanks for that, any chance to publish to ansible-galaxy?

I'm having trouble accessing my ansible galaxy namespace. Seems some others are also facing the same issue since the new ansible galaxy service was released (https://forum.ansible.com/t/namespace-changed-and-collection-upload-not-working/1314/21).
Once that's resolved I'll push the release.

Could you update galaxy.yml version number as well? Trying to install directly instead

I updated the version in git. I have access to my namespace now, but another Galaxy NG issue prevents me from uploading the collection:
https://access.redhat.com/solutions/7033171


[ADD] Split website_sale_search_custom into 2 modules

the custom search module contains 2 functionalities: clearing the search on category change, and
searching product tags. each functionality was split into a separate module (website_sale_search_tags
and website_sale_search_clear)
we only needed to clear the search bar for one of our clients, so we split the module.
feel free to merge this if you want.

@jbchouinard Thanks! You fix old issue I thought about.
Before merging this, I want to modify website_sale_search_custom and add there two modules to dependencies for backward compatibility.
Also, I need to update description of the new modules.

@yelizariev ok, I didnt touch the original module to avoid breaking anything, making it an empty module that depends on the other two seems like a reasonable solution.

@jbchouinard we are about to finish mentioned updates, so you don't need to worry about it. Thank you for the work you have already done.

We have merged the updates here: https://github.com/it-projects-llc/website-addons/pull/140


Whitelist words & relays

A list of words. Only events with these words are accepted.

Add a list of relays that are whitelisted to accept any incoming events from these relays


check all pluggables is initialized

Maybe fix https://github.com/rekabhq/background_locator/issues/264
Sometimes it seems that locationUpdated is called before initCallback is called and initCallback is not called.
In my environment, with this fix, initCallback is now called.
Thanks.

Changed to Draft due to still having issues with edge cases.


Update community-tooling.md

just wanted to add, we support cockroachdb as well. Including usually the cockroachdb specific features.

This change is

Thanks, @wzrdtales!
@vy-ton, PTAL.

@wzrdtales
Thanks for adding this! Looks good to me.
Before we merge this, could you also make the same changes to the following files:

v20.2/community-tooling.md
v21.2/community-tooling.md

@wzrdtales Additionally, CockroachDB is not listed among the supported databases at https://db-migrate.readthedocs.io/en/latest/. Could you add CockroachDB to that page, or, at the very least, add a note under PostgreSQL support?

@wzrdtales Additionally, CockroachDB is not listed among the supported databases at https://db-migrate.readthedocs.io/en/latest/. Could you add CockroachDB to that page, or, at the very least, add a note under PostgreSQL support?

sure, done

replaced previous commit 20.2 didn't had the section yet and it landed in the wrong one

replaced previous commit 20.2 didn't had the section yet and it landed in the wrong one

Thanks for doing that as well. Cheers!


scipy.interpolate.interp1d with kind=“previous” doesn't extrapolate as expected

import numpy as np
from scipy.interpolate import interp1d

a = np.arange(10)
b = a + 100

iterp = interp1d(a, b, kind="previous", bounds_error=False)
print(iterp([-1,-2,5,8,12,25]))
# [nan nan  105.  108. nan nan]

First two nan values makes sense, but last two don't since a previous value is available.
Now if I use extrapolate:
iterp = interp1d(a, b, kind="previous", fill_value="extrapolate")
print(iterp([-1,-2,5,8,12,25]))
# [100. 100. 105. 108. 109. 109.]

The last two 109. make sense but the first two 100. don't since there is no previous value.
I believe the result should be the intuitive [nan  nan  105.  108.  109.  109.]
Issue reported on stackoverflow too, if anyone wants to add comments there...
https://stackoverflow.com/questions/53753562/scipy-interpolate-interp1d-with-kind-previous-doesnt-extrapolate-as-expected
Scipy/Numpy/Python version information:

1.1.0 1.15.0 sys.version_info(major=3, minor=6, micro=5, releaselevel='final', serial=0)

Sorry if I 'm wrong but to what I understand interpolation can only be done for a point in [0,9] which is the range of a.Rest is extrapolation beyond this range.

I 'm interested in fixing this bug .I would definitely try to remove this bug if I can understand what you want.To what I understand previous is  your nearest neighbor extrapolation/interpolation in which nearest neighbor is checked(therefore beyond your [0,9] is 12 or 25 which first of all cannot be interpolated so result goes to nan which is your fillvalue and talking about extrapolate it is giving you the value of nearest neighbor of -1,-2 which correspond to a=0 and is b =100) .If I 'm wrong please tell what your desired output is so that I can add a code which would act accordingly.I think it's  badly termed.

I just think if you use "previous" for interpolation, it should use "previous" for extrapolation too, not "nearest". Now here there is no previous value to extrapolate so instead of silently defaulting back to "nearest" it should either extrapolate to nan or -inf (or raise an exception).

That is why I wrote badly named.

Thanks:)

I confirmed this issue still exists in the latest v1.5.2

I've been trying to fix this problem for the past week, I think I can fix it.
But I am not sure if I should fix it as has been suggested now...
Current implementation just fill requested points outside of the data range with fill_value whichever kind is used.
And, if fill_value is "extrapolate", it just fill requested points outside of the data range with first and last value of y whichever kind is used.
This strategy looks straightforward for me.
I think if I change the fill_value behaviors based on which kind is used, that might make some users be confused and break backward compatibilities.
So, I think we should update docstring or add notes to explain this strategy and workarounds for it.
(For example, there is a workaround for the first issue:
axis = -1
iterp = interp1d(a, b, kind="previous", axis=axis,
                 bounds_error=False, fill_value=(np.nan, b.max(axis=axis)))
print(iterp([-1,-2,5,8,12,25]))
# [ nan  nan 105. 108. 109. 109.]
```)

Does someone have any comments for this?

Apologies for this slipping under the radar @AtsushiSakai . I think your workaround is great!
Maybe the right thing to do is to actually implement your workaround as the strategy for kind="previous" and fill_value="extrapolate" and change the internal state of the extrapolation switch in the constructor.
A likely similar issue exists for kind="previous".


#Feature #Fix

Feature:

Adding the capability to initialize the PAIR containers from  the JSON model definition files included
Adding a database auto-upgrade mechanism with storage of the plugin version number for the future

Fix:

Add better support of the array typed object properties

C'est beau


First, probably naive, attempt to handle the error.

I didn't raise a ServiceNotValid exception because if I do the stack trace gets printed, which didn't seem very user-friendly... Happy to get feedback.
Critical Changes
Changes
Fixes #752
Issues Closed

This is ready for a second look, @davisagli. I must confess that I don't understand the syntax in the tests very well yet, so I wouldn't be surprised if my test isn't right. Please feel free to suggest changes. Thanks!

Saw the errors. Will try to fix.


Add a middleware system

this addition will like require refactoring routing out of Core and into a router class

ROuter class has been created

Completed with PR #122


Java VM Android class loading error log4j-core

After updating Gradle to 3.0.1
Error:Execution failed for task ':app:javaPreCompileDebug'. > Annotation processors must be
explicitly declared now.  The following dependencies on the compile classpath are found to
contain annotation processor.  Please add them to the annotationProcessor configuration.
- log4j-core-2.2.jar (org.apache.logging.log4j:log4j-core:2.2)   Alternatively, set
android.defaultConfig.javaCompileOptions.annotationProcessorOptions.includeCompileClasspath
= true to continue with previous behavior.  Note that this option is deprecated and will be
removed in the future.   See https://developer.android.com/r/tools/annotation-processor-error-
message.html for more details.

adding log4j-core-2.2.jar (org.apache.logging.log4j:log4j-core:2.2 as dependency or setting
android.defaultConfig.javaCompileOptions.annotationProcessorOptions.includeCompileClasspath = true
gives another error:
Rejecting re-init on previously-failed class
java.lang.Class<org.apache.logging.log4j.core.lookup.JmxRuntimeInputArgumentsLookup>:
java.lang.NoClassDefFoundError:

To Do: try implementing solution from:
https://github.com/dialogflow/dialogflow-android-client/issues/34#issuecomment-311106345

https://github.com/api-ai/apiai-android-client has transitive dependency on https://github.com/api-ai/apiai-java-client
Which adds log4j to your app.
log4j was not really designed to work on Android VM, so the best way to solve your issue is to use different implementation.
...


Task - Pools Portal - Add page to view all applicants in (their) Pools

Description
Remember, this is a page built in Backpack.
It should be a table that lists all applicants in the user's pools. (Note: we only have one pool to start with, so any Pool Managers must necessarily own that pool.)
TODO: find out exactly which fields we want to display here. For now, email and username are fine.
Preliminary list that is on google form:

First Name

Last Name

Contact Information (open field, guide says email and phone)

City (open field)

Province (open field)

Language of Preference

Working Ability

Work Locations (checkboxes)

Comments (for location)

Work Availability (shift work, work weekends, work scheduled overtime, work overtime on a short notice)

Education and Certifications

Computer Programming Languages

Employment History

Asset Qualifications (yes, no and explain for each)

Salary range and/or Group and Level Expected (radio buttons per $10,000 tranche)
-Group and Level (open text)

Can start with placeholder if needed to get started while we wait for final fields.


Merge release-4.6.2-m4 branch back to 4.6.x

Purpose
Note $subject

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: DimalChandrasiri:x: wso2-jenkins-botYou have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: DimalChandrasiri:x: wso2-jenkins-botYou have signed the CLA already but the status is still pending? Let us recheck it.


Fixed most of the issues and also adds much more fun!

So this PR implements #7, #4, #5, #1, #2.
Fixes pluralization issues, and add fun! Now messages might looks like this:

This is a pretty cool update. A couple thoughts, though:

Randomizing takes some of the fun out of it. I like that the amounts are entirely based on the amount of open PRs.

The random messages is a great idea, though some are a little silly. eg. "Sweat away those pounds." is fine, but "With :heart: from :moon:" is a little strange. I'm not sure I like that random people can be singled out either, because it takes away from the solidarity of the whole thing.

Multiple exercises sorta complicates things, or turns it into too much of a workout. What's default behavior and what's configurable?

Randomizing is only done to distribute amount PR`s to exercises. This does not add or remove anything.

Agree. Just wanted more messages to start off. This needs some :heart: from our poets /cc @zachdunn

This is the default behavior. Everything is configurable. Number of exercises, types of exercises, ratios, and so on.

:+1: for pushups, i want that unbalanced no-leg-day thing everyone seems to be doin!

Merging this, since its been here for a while, and it has been running for a while too

@robinpowered/product-team Merge PLS, this adds double pushups for us

Not to speak for too many, but I know that most of the people that do the pushups together in the office simply do a 1-to-1 on the number of open pull requests (25 pushups for 25 PRs, regardless of PR age). Is there any way we can make the non-linear pushup calculation (and old count) an option?