feat: [M3-6145,  M3-6191, M3-6233] - Add User Data to Linode Clone and Backup flow

Description 📝
Adds User Data section to the Linode clone flow
Preview 📷

Remove this section or include a screenshot or screen recording of the change
How to test 🧪
Navigate to create Linode page

Enable MSW to validate this change
Click on "Backup/Clone", then select Linode (with an image that supports cloud-init).
Validate the "User Data" accordion and confirm that the warning message is rendered.
Now select Linode (with an image that doesn't support cloud-init).
Validate the "User Data" accordion and confirm that the warning message should not be rendered.
Click on Linode create (clone and backup flow) and validate the response.

How do I run relevant unit or e2e tests?

yarn test
yarn cy:run

On an unrelated note, it would be nice if develop was merged into feature/metadata so Vite can be used and tested as this project is developed.

M3-6233 should also be included in the PR title, right?

Great feedback, @bnussman-akamai I agree with UX thing, will circle back with UX on that. @hkhalil-akamai Added the ticket M3-6233 to the PR.


step-ca: 0.23.0 -> 0.23.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/smallstep/certificates/releases.
meta.description for step-ca is: A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH
meta.homepage for step-ca is: https://smallstep.com/certificates/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.23.1 with grep in /nix/store/qywi4ds0ng7rmy4h68yp6z6rj1k9b21v-step-ca-0.23.1
found 0.23.1 in filename of file in /nix/store/qywi4ds0ng7rmy4h68yp6z6rj1k9b21v-step-ca-0.23.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
step-ca

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qywi4ds0ng7rmy4h68yp6z6rj1k9b21v-step-ca-0.23.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A step-ca https://github.com/r-ryantm/nixpkgs/archive/3469fcfe483f52f36ce143139db5f93ff2a0e407.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qywi4ds0ng7rmy4h68yp6z6rj1k9b21v-step-ca-0.23.1
ls -la /nix/store/qywi4ds0ng7rmy4h68yp6z6rj1k9b21v-step-ca-0.23.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

step-ca

Maintainer pings
cc @CMCDragonkai @mohe2015 @techknowlogick for testing.

Result of nixpkgs-review pr 211596 run on aarch64-darwin 1

1 package built:

step-ca

@ofborg test step-ca

I think this blew up in Hydra? https://hydra.nixos.org/build/206729862

yep, it's broken on linux, I guess it works on darwin because of __darwinAllowLocalNetworking = true?


After using redis as pubsub, the message will not be deleted after being processed by the subscriber

After dapr uses redis as pubsub, after the message is processed by the subscriber, the message will be processed by the ACK mechanism, but the processed message is not deleted. This lacks the function of deleting the message that has been consumed. Currently, it only supports setting maxlen to ensure the total length of the Stream, but doing so will waste space. It is recommended to increase the parameters to control the consumed messages will be automatically deleted after a certain period of time
https://github.com/dapr/components-contrib/blob/3c28fee80f1cbf7c37df2854836cc3bc8660f9e3/pubsub/redis/redis.go#L246-L267

After the message is processed, the ACK mechanism will be used to prevent repeated consumption, but it does not delete the processed message. I hope to add a function that the message will be deleted after a certain period of time after consumption, or provide a message to be deleted after a certain period of time. Option to delete immediately after consumer consumes

When multiple services subscribe to the same topic, it can be difficult to determine an appropriate time to delete messages. In particular, it is difficult to determine whether messages should be deleted when one of these services is down. What do you think?
Redis pubsub has a maxLenApprox metadata defined maximum number of items inside a stream, does this meet your needs? You can refer to here: https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-redis-pubsub/#spec-metadata-fields

When multiple services subscribe to the same topic, it can be difficult to determine an appropriate time to delete messages. In particular, it is difficult to determine whether messages should be deleted when one of these services is down. What do you think?
Redis pubsub has a maxLenApprox metadata defined maximum number of items inside a stream, does this meet your needs? You can refer to here: https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-redis-pubsub/#spec-metadata-fields

When multiple services subscribe to the same topic, if some services are not started, redis does not know that there are still services that are not executed, and after the message is acked, when the previously unstarted service is restarted, the message that has been acked is still acked. Will it be redelivered?

Services with deferent consumerID (defaults to appid if not set) are independent when consuming messages. So if multiple services have different appid, messages will be redelivered.

@zhenlei520 You can refer to here for more details: https://docs.dapr.io/developing-applications/building-blocks/pubsub/pubsub-overview/#consumer-groups-and-competing-consumers-pattern

Yes, what you said makes sense, but if you specify maxLenApprox, when the accumulation exceeds the number, it will also be deleted without delivery.
I checked the introduction of Streams in the redis documentation, and I think this is caused by the problem of redis. If redis can provide a function of binding a consumer group to a message, it will be fine. Bind the consumer group to the message when the system starts. When all consumer groups in the message are acked, it is the best way to stay for a certain period of time before being deleted.


Enhancement request - partial edges for low cost production boards and prototyping?

For rapid prototyping and as a customer choice for a lower cost production board I would like to have an option to select the program to cut the base for partial edges just along the full running length so a minimal amount of bending just into the tip and tail transition area where the bezier meets the arc.  Worth it or a PITA? cheers Rich

@Mike I think I have another keen coder, he might lean on your for some C tutorship but he's keen and a very passionate mountaineer and skier and I suspect he's better at coding than he lets on! He likes the idea of lightweight edges ie. short edges less steel. I'll get him in touch ok mate. cheers

Hi @mikemag I've started playing with this. I'm keen and have a fair bit of programming experience but have no experience with git and little with C++ so this will be a learning process. I figure this shouldn't be too bad an issue to start on.
As I see it what needs doing is:

Add parameters to loadBoard function (in MonkeyCam.cpp) to describe the length/position of the partial edge. I'm thinking along the lines of two parameters, one for the distance from the nose to the start of the metal edge and a second for the distance from tail.

Modify the generateBaseCutout function in shapes.cpp to limit the region where the base shape is offset inwards to the length where we want the metal edge to be. To do this I guess I'll have to clip the overall board shape and the current base shape (offset in by 2mm) using some simple rectangles, then recombine them. I can work this out by following what you've already done to generate the core shape where it meets at the nose and tail spacers as this is relatively similar.

Does that approach sound reasonable? Do you have any better ideas for how to define the edge length and position?
Cheers, Reg

Hey @RegMeasures awesome to have you involved mate, I'm sure Mike will give you excellent guidance when necessary inbetween the other parts of his very busy life.
For the partial edges, from a constructors point of view what I am keen on is to have no additional bending of edges if possible, so just letting the edge fall in to the sidecut without then at each end having to go in the other direction into the tip and tail at all, otherwise we start having to bend edges again, and I hate bending edges. So I would think keep the length just within the actual finished sidecut radius....
@mikemag has done this in MonkeyCAM ver 3 too?
Managed to cut some stuff badly today but was a good start, just getting a feel for what I don't know and a huge learning curve ahead!!!!!

@RegMeasures, glad you're excited to help!!! Some quick answers to your questions:
Your suggestion for how to form a new base with partial edges is reasonable. In the past (v3) I put in the effort to ensure that I cut the end of each edge section perpendicular to the edge at that point, but it's overkill. We're using round cutters, so we have to clean that part of the base up with a knife anyway. So clipping with a simple square should suffice.
To decide where to end the edge, measure from the end of the effective, not from the end of the nose/tail. No one knows how long the arcs of their noses and tails are :) What you'll want to do is say "extend the edge 4cm past the effective edge". You may want to adjust that based on the nose or tail geometry, so a different setting for nose and tail would be good. By doing this people will end up with consistency between different board shapes: when you stand up all your boards after a year the edges will end a similar distance from the "hips". It's most likely that you'll pick a default length, and most people will never have to change it.
Make sure to make a boolean option for "use partial edges" vs "full wrap".
@splitn2 suggests that he wants to end his edges right at the end of the effective edge. So make sure that 0 is a valid value for the new parameters. That said, it's probably a bad idea to end right there. You want to go past the hips a bit, otherwise you'll have the rough, vulnerable edge end right at the leading end of the effective edge, which is engaged with the snow surface in a carve. @splitn2, going a few cm past the ends of the EE will be minimal edge bending effort, don't worry!! :)

Oh, and @RegMeasures, be sure to see the sections on https://github.com/mikemag/MonkeyCAM/wiki on modifying MonkeyCAM if you haven't already. There's a good overview of the overall architecture and how shapes are formed.

@mikemag @RegMeasures thats great guys !!!!!!

@RegMeasures I have some paulownia .....how is your coding going? I'll start ripping timber this weekend and building up core blocks, we can try this short edge on your skis once you have your ski design in MonkeyCAM. the cnc is ready and I'll have the timber and other materials too. cheers, Rich

Nice work @splitn2. I've got the partial edges working - need to send it back to @mikemag to merge it in. I would have done this earlier but I got bogged down trying to fix a bug with the line endings in the G-Code output files which I think is related to compiling on windows. I can't seem to work out why it is doing it though...

cool @RegMeasures I look forward to seeing this. As soon as we have a new release and then with your ski design you have your first set of MonkeyCAM output files, I suggest we do a trial cut and see how the files behave.

@RegMeasures last night I did a test run of my machine , just "cutting air", of a rifle stock design which is another collaboration project I'm working on, and the results were pleasing, the CNC seems to be very responsive and powerful. We were using a basic CAM out of Solidworks which is only good for evaluation but it helped prove the point I'm making the right progress. I have a load of cutting tools coming from china and my vacuum dust extraction system is almost dialed. So progress in the workshop is good. Keep up your good work mate this is exciting!

Fixed by @RegMeasures with ac3eede63d7607c7ab938683b04c7f5142bf3113.

Included in v4.0.4, https://github.com/mikemag/MonkeyCAM/releases/tag/4.0.4


Can I use kinect vertically for body tracking?

Hi, I use Kinect vertically.
Body tracking is relatively unstable compared to when used in the horizontal direction.
Do I need to replace variables to use vertically?
Describe the bug

Body Tracking unusable.
To Reproduce

Tested in Simple_3D_Viewer sample : WFOV 2x2 binned Mode
Expected behavior

Logs

Screenshots

Desktop (please complete the following information):

OS with Version: Win 10
SDK Version:  Azure Kinect Body Tracking SDK 0.9

Additional context

Thanks for reporting this issue. The vertical mounting is not supported in the previous version of SDK, To address this issue, we will add an option for the customer to specify the mounting direction of the sensor when creating the tracker.

To address this issue, we will add an option for the customer to specify the mounting direction of the sensor when creating the tracker.

It would be really great! Brilliant idea.

The new release 0.9.2 is published! The problem is resolved. You can download this now at: msi,  nuget or apt-get on Linux.


add option to run workflow manually

Why do we need this?

Why do we need this?

Because the latest versions of containers wasn't pushed last time. So, it is easier to run workflow by pressing button, instead of changing code to trigger workflow.


Improve typos configuration

Description
Make typos config more strict preventing future ignore of actual typos. Put everything in its place.
You could check hidden files by removing . from the command line.
https://github.com/static-web-server/static-web-server/blob/9afff97acd15320bbd8b7c426d42a3fd369992c3/Makefile#L301

Done 🍏

Glad to contribute.


Expanding functionality of the gun adapter

Added possibility to get response body as stream and in chunks.
Also added possibility for reusing opened connection.

👋 @alex-strizhakov  how's going? :)

hi @teamon !
Main options are here. What i have to do to make it merged?
I can add tests for proxy option, by adding tinyproxy image, if it is needed. How it is done in mint
SNI option can be removed after this issue will be fixed.
Options for support gun 1.3 and master can be removed after release gun 2.

Please take a look at the pending review comments :)

I thought they all were resolved :)

Let's do it then! 🚀

👍


128 bit

What do we think of natively supporting u128 / i128 by applying https://github.com/protocolbuffers/protobuf/blob/20a30c675a4fa51736dd183ff9ecf16ef8300325/src/google/protobuf/stubs/int128.h
u128 quite a common datatype nowadays => ipv6, uuid, sol/eth/bitc, etc...

also - well aware it's not standard to require "external types" outside the core protobuf language
however, we have the elegance of cargo for additional features :)
...would propose an opt-in feature flag

Could this be provided by an external crate?

Anything can be provided by an external crate. And complicate the software chain of protobuf generation.
Rather, I think the narrative should follow:
Why do people use the Prost crate?
It decodes protobuf onto Rust primitives - rather than ffi <> gprc api
What's the benefit of Prost over alternative implementations?
Centralize definitions into protobufs, rather than decoding from a library model into native rust model then encoding back to library model
Why include this feature?
u128 happens to be a rust primitive - which falls inline w/ the boundary & advantage of this library
accordingly, though that may be a valid answer for alternative, random data types, I don't think it applies herein

Yeah that seems fair, I guess since rust supports it as a primitive we could add support. I would be open to accepting a PR for this.

Hi, I'd like to make this real. We highly need this. But I'm not sure how to achieve it. It'd be nice if someone can give me some guidance on this feature.

hi @thaodt you can come on discord and we can chat in the #prost channel (the tokio.rs discord). I believe this change will just require implementing Message for these types similar to what we do for u64 etc https://docs.rs/prost/latest/prost/trait.Message.html#impl-Message-for-u64

Closing this - until hardware supports u128,
individuals should opt for string type <> u128.
Proprietary protocols can implement custom bytes
approach as linked above.


Use h2 in view

I clearly think it's better and common to use an h2 rather than an h1. For w3c validator and also often, h1 is not "our products" or "best products", it's commonly a sentence optimized for SEO or other.

@maximebiloe Can you review it ? Or close ?

@matthieumota @maximebiloe is no longer part of the Core team.
Since the h1 is in a section, there is no need to change this one. More your remove the inheritance if the include contains an h2.


Optional params?

Is there support for optional params similar to express (Without regex).
route.get('/profile/:id?', function * (next) {...});

Yes, koa-router uses path-to-regexp.

The answer in this issue leaves a little to be desired. While it's good to know that koa-router supports this, an example would also be nice since this is not listed in the README.

And the answer is:
route.get('/profile/:id*', function * (next) {...});

And the answer is:
route.get('/profile/:id*', function * (next) {...});

shouldn't it be :id? (with question mark)

It is actually :id*
path-to-regex Says:

Parameters can be suffixed with an asterisk (*) to denote a zero or more parameter matches. The prefix is used for each match.

@GabrielNicolasAvellaneda
To make a parameter optional, then it's :id?, to make it match the beginning of a certain string then it's :id*.
URL you visit: mydomain.com/example/123/hello
example/:id?/hello -> The field id will in this case be 123. The ID field can be omitted, the ? makes it optional.
example/:id*/hello -> The field id will in this case be 123/hello. * matches everything after, regardless of content.
Sorry to bump an old post, just wanted to clarify a small incorrect interpretation of the documentation.


Android missing signature

Under Android replace:
firebase::admob::Initialize(*app, kAdMobAppID);
with
firebase::admob::Initialize(GetJniEnv(), GetActivity(), kAdMobAppID);
and you get crash, as there is no such method on Android side.

Hi,
The C++ library always requires you to pass in the Firebase App. When you initialize Firebase App on Android, you pass in the JNI environment and activity.
See the AdMob sample app for an example:
https://github.com/firebase/quickstart-cpp/blob/master/admob/testapp/src/common_main.cc#L126

I try to use Firebase on Amazon devices without Google Play Services. So I can't init Firebase, as I always get annoying dialog "Update Google Play Services". But, according to docs - there is no need for Firebase to use AdMob.
And AdMob has special constructor for such cases - see admob.h
Looks like you forgot to implement jni-bridge on c++ side to java side. c++ has function, but does not route to java call. It's easy to fix.

Sorry about that. I do see the Initialize() method you described.
It does seem that there is a bug that still looks for the class com.google.android.gms.tasks.Task when you initialize AdMob in that way. Thank you for reporting it, I'll take a look and see what's needed to fix it.


Readme and Documentation update

Readme and Doc update
Description

We add more details and update the Readme and Documentation.
Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ x ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ x ] I have updated the documentation accordingly.
[ x ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ x ] All new and existing tests passed.

@ismaelfaro I tried creating a pull request to your fork. Let me know if you don't see it.


Fix window.open with wrong name

When calling window.open the newly created window would have the name of the last option in the features argument as the title. I think it's supposed to be pointed to frameName.

Thanks for fixing this :shipit:

Np!


Web3 Authentication example is insecure

Hi,
I believe that the solution provided in this example is extremely insecure. Anybody can inject their own "metamask" object into the browser and thus authenticate as someone else.
I know you guys work hard and I appreciate your effort to in making this amazing framework.
However, if anyone had built an application based on this example it would be a disaster as the crypto community is extremely tech-savvy and can spot such vulnerabilities very quickly.
Cheers.

@mlewandowskim thanks for raising the concern. The example wasn't ours to begin with and hasn't seen updates for a while, so we decided to remove it instead.


remove testling badge

hasn't run since September 25th

fixed by https://github.com/dominictarr/crypto-browserify/commit/52b4aff1903a9d64c9a095024635229616de99d6


[Bug Report] tabs switching route is destroyed when [Vue warn]: Error updated hook: (found in ) vue.esm.js 65d7:1447 Cannot read property'offsetWidth'of undefined ()... )

Element UI version
0.1.0
OS/Browsers version
chrome 53
Vue version
2.2.6
Reproduction Link
https://jsfiddle.net/无路由不好提供demo
Steps to reproduce
子页面使用el-tabs后，切换到其他子页面，在执行destory时出现如题JS error。

没有JS Error
What is actually happening?
出现描述中的error

You can use vue-router in JSFiddle. Please update your repro link.

May be I wrong，I use keep-alive and  I destroy when activated
http://jsfiddle.net/xgrjzsup/1846/

Is there any reason you destroyed the instance in its activated hook?

@Leopoldthecoder no, thank you

I met this problem recently, I guess you should do a similar operation with me.Used in the el-tab this component v-if, in fact, should use v-show。
Or you made other related dom operations。


Bump Chart, Sort streams by, Sort series by

When you change "Sort streams by" or "Sort series by" option nothing happens.
In which chart does the bug happen?

Bump chart

RAWGraphs Version
Beta 2.0 (app version 24/03/21)
Web browser and version
Chrome 89.0.4389.90
Operating System
MacOS Big Sur 11.2.3
Project file
Foreign Residents in Milan.rawgraphs.zip
Additional context

Yes that's true! this option doesn't make sense in this chart - it is an option of the area chart. Will remove it in the new version


sanchez version 1.0.20 incorrectly reports version number as sanchez-1.0.19

Describe the bug
sanchez version 1.0.20 incorrectly reports version number as sanchez-1.0.19
To Reproduce
Install sanchez from https://github.com/nullpainter/sanchez/releases/tag/v1.0.20 (I used the Linux version).
sanchez/Sanchez --version - to get the version number, which is reported as 1.0.19
Expected behaviour
1.0.20 is reported, not 1.0.19
Real behaviour
The correct version number is reported!
Screenshots
Above should be clear enough/
Environment:
Linux web 5.10.0-15-amd64 #1 SMP Debian 5.10.120-1 (2022-06-09) x86_64
Additional information
I looked at the source code and I suspect the issue comes from Sanchez.csproj:
<PropertyGroup>
    <Version>1.0.19</Version>
    <FileVersion>1.0.19</FileVersion>
</PropertyGroup>

However I've not got an environment set up to build from the source code.
Minor isssue by far, but confused me when I thought I'd installed the new version, did a version check to see old version, so re-installed it, did version check to see the old version. I then stopped myself before I did an endless do...while version <> "1.0.19" loop...

Thanks Mike; I remembered to fix this in version 1.0.21 (coming shortly)


Opnsense openvpn added

This is a specialized parser and scenario for OpenVPN running on OPNsense. This is a work in progress as the most elegant solution would be to create a generic parser and scenario for OpenVPN regardless of platform. As described in the parser readme this depends on a few modifications to the syslog parser.

I did the PR with the wrong github account. D'oh!.


maxTime and minTime for TimeInput would be really nice

maxTime and minTime props for TimeInput would be really nice. They should be working similar as maxDate and minDate.

I agree with you @MRauca.
maxTime, minTime props are really needed for me and this library 😢

I agree with you @MRauca.
maxTime, minTime props are really needed for me and this library 😢


attempt at extensionless filename support

This is an attempt at addressing #85

Considering the difficulty in using mimetypes to do a reasonable job of guessing the filename extension, I'm going to close this PR in favor of the simple solution adapted in #85.


Build failure due to gix-config after cargo-update

Describe the bug
After running cargo update on the cargo-generate library (or in project that depends on cargo-generate without a .lock file) the build fails due to changes in the gix-config crate.
Build error:
error[E0425]: cannot find value `env_var` in crate `gix_path`
  --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/gix-config-0.20.1/src/file/init/comfort.rs:31:54
   |
31 |                     .storage_location(&mut gix_path::env_var)
   |                                                      ^^^^^^^ not found in `gix_path`

....

To Reproduce
Steps to reproduce the behavior:

git fetch'd cargo-generate main (tested on 1eea043ebcc9d3e30a1a0c391afff89ca38a1b67)
cargo update
cargo check

Expected behavior
build to succeed
Desktop (please complete the following information):

OS: Linux
Version: 6.2.11-arch1-1
Build tools: clang
Shell: zsh
rustc --version: rustc 1.66.1 (90743e729 2023-01-10)

Additional context
Seems to be fixed by bumping the gix-config dep:
diff --git a/Cargo.toml b/Cargo.toml
index 4611262..b7091b3 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -27,7 +27,7 @@ home = "~0.5"
 sanitize-filename = "~0.4"
 rhai = "~1.13"
 path-absolutize = "~3.0"
-gix-config = "0.20"
+gix-config = "0.21"
 paste = "~1.0"
 names = { version = "~0.14", default-features = false }
 log = "~0.4"

I get this same error after updating Rust with rustup update when I get up to the step of running cargo install cargo-generate when following these setup instructions to learn Rust and Wasm https://rustwasm.github.io/docs/book/game-of-life/setup.html
I'm using toolchain stable-2023-03-28-x86_64-apple-darwin on macOS with rustc 1.68.2 (9eb3afe9e 2023-03-27)

Closing because gix-config bumped to 0.22 and fixed the issues upstream: https://github.com/Byron/gitoxide/commit/94564df0b5edcb41f1088c6db04add851c66b2af


Anomaly locator tweaks

About the PR

This tweaks the anomaly locator to increase its detection range (from 10 to 20) and decreases its power cell draw rate (from 5 to 1). This is  to make locating anomalies using this device easier, with its increased range, and sets a battery life which seems more reasonable for hunting anomalies (3 mins with a small power cell, 6 with a medium, 9 with a large). The beep intervals for this device have also been adjusted to account for the change in detection range.
Media

[X ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

tweak: The detection range of the anomaly locator has been doubled, and its battery life increased by a factor of five

if this is audio spam come and crucify me later


KeyError: b'0101' issue in Python 3.5

Hi
I am encountering below mentioned error after applying the fix for Issue #21.
nat_type, external_ip, external_port = stun.get_ip_info(stun_host=(stun_details[0]), stun_port=int(stun_details[1]))
File "C:\Users\User\AppData\Local\Programs\Python\Python35\lib\site-packages\stun_init_.py", line 253, in get_ip_info
stun_host=stun_host, stun_port=stun_port)
File "C:\Users\User\AppData\Local\Programs\Python\Python35\lib\site-packages\stun_init_.py", line 191, in get_nat_type
ret = stun_test(s, stun_host, port, source_ip, source_port)
File "C:\Users\User\AppData\Local\Programs\Python\Python35\lib\site-packages\stun_init_.py", line 136, in stun_test
bind_resp_msg = dictValToMsgType[msgtype] == "BindResponseMsg"
KeyError: b'0101'

Since the pull requests fixing this project for Python 3 have been open for a long time, I decided to make my own version of this project. It may be useful to you: https://github.com/arantonitis/pynat

Fixed bug:
bind_resp_msg = dictValToMsgType[msgtype.decode()] == "BindResponseMsg"


Add support for mouse back/forward buttons

When pressing the back button on my mouse, nothing happens. I would expect it to go back to the previous page. And similarly for the forward button.

This is a mouse with extra function buttons, yeah?

The mouse has 8 buttons in total (including the one on the mouse wheel).

Ok, I'll look into this

#852 Implements this for Windows users. I tested it on Ubuntu 16.04 running Unity and it did not work but nothing crashed and burned so this shouldn't change anything for non-Windows users.


Strat does not identify the 'trend'.

I'm submitting a ...
[x ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Action taken (what you did)
starting my strategy I noticed that in the .check phase the variable 'trend' always returns 'in no trend'.
so strat ignore all the settings if 'trend.up' and 'trend.down'. the only one that works is 'in no trend'

Expected result (what you hoped would happen)

Actual result (unexpected outcome)

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)
this is part of code where var trend is configured:

if(MACDsaysSELL && StochRSIsaysSELL) {
// new trend detected
if(this.trend.direction !== 'high')
this.trend = {
duration: 0,
persisted: false,
direction: 'high',
adviced: false
};
	this.trend.duration++;

	log.debug('In high since', this.trend.duration, 'candle(s)');

	if(this.trend.duration >= this.settings.thresholds.persistence )
		this.trend.persisted = true;

	if(this.trend.persisted && !this.trend.adviced) {
		this.trend.adviced = true;
		this.advice('short');
	} else
		this.advice('short');

}
//buy when stochRSI in high and MACD in low
else if(MACDsaysBUY && StochRSIsaysBUY && BBsayBUY) {

	// new trend detected
	if(this.trend.direction !== 'low')
		this.trend = {
			duration: 0,
			persisted: false,
			direction: 'low',
			adviced: false
		};

	this.trend.duration++;

	log.debug('In low since', this.trend.duration, 'candle(s)');

	if(this.trend.duration >= this.settings.thresholds.persistence)
		this.trend.persisted = true;

	if(this.trend.persisted && !this.trend.adviced) {
		this.trend.adviced = true;
		this.advice('long');
	} else
		this.advice();

} else {
	// trends must be on consecutive candles
	this.trend.duration = 0;
	log.debug('In no trend');

	this.advice('long');
}

Hey! Unfortunately this is not the place to get strategy support. This is the perfect place for it: https://forum.gekko.wizb.it/forum-12.html


Numbers refactor

Move the numbers piece of state from local to the run method into the Ctx struct with the other rendering state.

I signed it!

Thanks for taking a look @raphlinus. I appreciate not wanting to merge a breaking change in to master, but I don't see how my proposed changes are breaking.  The only public functions in this module are run and push_html and I didn't change the signature of either function.  So I'm curious what you see as a breaking change.


Black screen on mobile android, cant run even basic 3d sence

Tested versions
Godot 4.2.1 and I dont see solution on other version as well
System information
window 10, godot4.2.1 vulakan mobile
Issue description
Black screen forever when open 3d sence with mobile android. Hope it work normal
Android info:
Oppo CPH2239
Android 11, api 30
Chipset: mt6765
Build:CPH229_11_C_32
Realease: 11
OpenGL:3.0.2
CPU:arm64-v8a
VersionTemplate 4.2.1.stable
Export setting:
name="Android"
platform="Android"
runnable=true
dedicated_server=false
custom_features=""
export_filter="all_resources"
include_filter=""
exclude_filter=""
export_path="../../Godot Export/Test.apk"
encryption_include_filters=""
encryption_exclude_filters=""
encrypt_pck=false
encrypt_directory=false
[preset.0.options]
custom_template/debug=""
custom_template/release=""
gradle_build/use_gradle_build=true
gradle_build/export_format=0
gradle_build/min_sdk="24"
gradle_build/target_sdk="30"
architectures/armeabi-v7a=false
architectures/arm64-v8a=true
architectures/x86=false
architectures/x86_64=false
version/code=1
version/name=""
package/unique_name="com.example.$genname"
package/name=""
package/signed=true
package/app_category=2
package/retain_data_on_uninstall=false
package/exclude_from_recents=false
package/show_in_android_tv=false
package/show_in_app_library=true
package/show_as_launcher_app=false
launcher_icons/main_192x192=""
launcher_icons/adaptive_foreground_432x432=""
launcher_icons/adaptive_background_432x432=""
graphics/opengl_debug=true
xr_features/xr_mode=0
screen/immersive_mode=true
screen/support_small=true
screen/support_normal=true
screen/support_large=true
screen/support_xlarge=true
user_data_backup/allow=true
command_line/extra_args=""
apk_expansion/enable=false
apk_expansion/SALT=""
apk_expansion/public_key=""
permissions/custom_permissions=PackedStringArray()
permissions/access_checkin_properties=false
permissions/access_coarse_location=false
permissions/access_fine_location=false
permissions/access_location_extra_commands=false
permissions/access_mock_location=false
Steps to reproduce
1, create project have only one 3d sence and camera and sky
2, setting export
3, run Remote debug
4, Mobile open app, show godot logo then black screen forever(I mean still run app but never show 3d sence).

Minimal reproduction project (MRP)
no

@huwpascoe No. I run on window already, camera can see green static.

Try aiming the camera down, you're probably given a different view so it might miss it on a smaller screen

@AThousandShips I dont think so sir.  Behave respectfully or I'll refer this to the code of conduct team

@AThousandShips are you serious? I don't mean to disrespect you, maybe you just thought that yourself. OK, what ever you are.
I try render full way but still the same.

@BachDown If you wrongly assumed someone's gender (something I would simply advise never to do), and get corrected, the respectful response is "Apologies, this wasn't intentional" and not reacting with a laughing emoji.

OK, what ever you are.

@BachDovn This is not a way to answer. This is even worse. Not every contributor is by default a man, please read the code of conduct.

@BachDovn And please, remove that laughing react here: https://github.com/godotengine/godot/issues/90512#issuecomment-2049391666
If you don't, it will be reported to the code of conduct team.

@AThousandShips so you're not a man, you're female or lgbt. Ok, I'm sorry for not knowing your gender . But I think this gender misunderstanding is understandable

@AThousandShips So, what is your gender?

My pronouns are on my profile clear as day, there's no honest intent here, or this would have been resolved with a reasonable apology

@AThousandShips Ok, I just call you is you....is that ok.
You right, I am sorry to you...and I hope every one here is nice. And help me solve android proplem.Thanks

Apology accepted

interesting convo. anyways, ive been experiencing something similar.
the high end vulkan renderer works perfectly fine.
unsure about mobile but as it uses vulkan too it should be alright too.
but when using compatibility, it glitches out a lot and produces this:
Flash warning
https://github.com/godotengine/godot/assets/102416174/e2d42a3c-97cd-4560-b934-99f4f014f63f
as compat is the default, godot is unusable on my phone. using remote deploy for my game and forcing vulkan, it works as expected.
using a Samsung S20 FE.


issue for build-arm on device

Build with make dev-arm and running on linux+arm device is correct.
Build with make build-arm was crash when loading  index.js
log:
[User]  (2.542, +1)      ChartConstructor: Chart 33 created     (in chart_wrap.cpp line #666)
[User]  (2.543, +1)      NativeCompSetStyle: Chart 33 setStyle type 0   (in chart_wrap.cpp line #5)
[User]  (2.543, +0)      NativeCompSetDivLine: Chart 33 setDivLineCount 0 12    (in chart_wrap.cpp line #158)
[User]  (2.543, +0)      NativeCompSetPointNum: Chart 33 setPointNum 12         (in chart_wrap.cpp line #170)
[User]  (2.543, +0)      NativeCompSetLeftAxisOption: Chart 33 setLeftAxisOption        (in chart_wrap.cpp line #210)
[User]  (2.543, +0)      NativeCompSetLeftAxisData: Chart 33 setLeftAxisData    (in chart_wrap.cpp line #399)
[User]  (2.543, +0)      NativeCompSetBottomAxisOption: Chart 33 setBottomAxisOption    (in chart_wrap.cpp line #294)
Segmentation fault (core dumped)

No more information was available to analyze the crash.
And the next step in dev-arm  will run:
NativeCompSetStyle: View 34 setStyle type 0    (in view_wrap.cpp line #5)

I'm having the same problem, how can I fix it

@kisvegabor I'm having the same problem, how can I fix it

@HuangJC-cn Do you fix this？

We're seeing the same issue on both some x86 hosts (but not all) and arm hosts.

It would be helpful to have a complete stack trace to find where this is happening

Debug(-g) works, Release not.

There's a new build system in the master branch. Please open a new issue if it is not working on a Linux system.


Start a draft for an Ament Python guide.

This is very much a work in progress and is littered with implicit
TODOs in addition to lacking much organization.
I started by trying to jot down as many major questions or known
limitations of ament_python packages as I could think of.
I'm going to keep iterating on this as a draft but if anyone else would
like to throw on extra info I invite anyone on the team to toss a few
commits on the branch.
@sloretz do you have suggestions for exemplary ament_cmake packages containing python extensions? I have always used rclpy but I'm not sure if it has become "special" either due to the pybind11 work or by being the rcl binding for the language rather than an application package which builds python extensions.

do you have suggestions for exemplary ament_cmake packages containing python extensions?

rclpy and rosbag2_py are the only two I can think of that create CPython extensions. IIUC they both use CMake instead of setuptools Extension because it's too difficult to list out include directories and link libraries without find_package(...).
I wouldn't consider rclpy or rosbag2_py special - any package that wants to pybind11 would be wise to copy their ways.
I'm not really sure what makes the ament_python build type special other than it causes colcon (colcon-ros?) to create a shell script that appends the install directory to AMENT_PREFIX_PATH.

I like this pr a lot! I think documentation on ament_python is really lacking. Please let me know if I can help you somehow, @nuclearsandwich! Generally I would suggest to keep this brief for now so that there is at least something which is better than the current state. This would also streamline the review process. Then we could add additional points in follow-up prs, as needed.


Create security.md

feat: Add security.md file to outline the project's security policy

name: Pull_request_TEMPLATE.yml
about: use this template for creation of pull requests
title: '[FIX/Feat] '
labels: ''
assignees: ''

name: Pull Request Template
Description

Fixes # (issue)

Screenshots (if applicable)

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

Checklist

[ ] I have read the contributing document.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have added necessary tests to ensure my changes are effective.
[ ] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

Additional Information

And also add your security email and supported version

issue no??

screenshot of output


Make it embedded-HAL independent

Thanks for this well designed BMP-180 driver!
I am wondering what could be done to make it independent of the embedded HAL (used here for delay and i2c), so that one could use it eg on a raspberry pi,  in my case with rppal.

One possibility would be to use a half based lib like https://docs.rs/rpi_embedded/latest/rpi_embedded/

nevermind, it just works with rppal when using the hal feature


Add types for channel dynamic dispatch

Add internal DynamicChannel trait implemented by Channel that allows
polling for internal state in a lock safe manner and does not require
knowing the channel size.
Existing usage of Sender and Receiver is preserved and does not use
dynamic dispatch.
Add DynamicSender and DynamicReceiver types that references the
channel using the DynamicChannel trait and does not require the const
generic channel size parameter.

Having the ability not know the channel size is very convenient when you don't want to change all of your channel using code when tuning the size. With this change, existing usage can be kept, and those willing to pay the price for dynamic dispatch may do so.

Having the ability not know the channel size is very convenient when you don't want to change all of your channel using code when tuning the size. With this change, existing usage can be kept, and those willing to pay the price for dynamic dispatch may do so.

Doesn’t a simple type alias also achieve the same goal ie a type alias requires a change in just one place…?

@huntc If you control the entire code base, yes. But if you expose an API in in one crate, and want consumers of your API to not consider the queue size, I believe this is a much nicer way. Using Channel in in Drogue Actor, the library can now expose an Address handle for the actor that doesn't need to have the channel size as a type parameter. Then I can use this address handle in another library that doesn't need to care about the queue size etc.

For the 'try' synchronous operations of the channel, I was able to work around this by adding a 'wrapper trait'. However, for async and GAT, the trait would need to have an associated type, which in turn requires specifying the associated types whenever using the trait, so that approach does not work.
Having the functionality in the Channel impl itself is the better way IMHO.

Some performance numbers
Static on master
Size:
Finished release [optimized] target(s) in 28.68s

text    data     bss     dec     hex filename
13208     104    1444   14756    39a4 channel_sender_receiver
Stack:
(HOST) INFO  reading 254.49 KiB of RAM for stack usage estimation
(HOST) INFO  program has used at least 0.21/254.49 KiB (0.1%) of stack space
Static on branch (should be the same as on master)
Size:
Finished release [optimized] target(s) in 29.89s

text    data     bss     dec     hex filename
13208     104    1444   14756    39a4 channel_sender_receiver
Stack:
(HOST) INFO  reading 254.49 KiB of RAM for stack usage estimation
(HOST) INFO  program has used at least 0.21/254.49 KiB (0.1%) of stack space
Dynamic on branch
Size:
Compiling embassy-nrf-examples v0.1.0 (/home/lulf/dev/embassy/examples/nrf)
Finished release [optimized] target(s) in 0.30s
text    data     bss     dec     hex filename
13244     104    1468   14816    39e0 channel_sender_receiver_dyn
Stack:
(HOST) INFO  reading 254.46 KiB of RAM for stack usage estimation
(HOST) INFO  program has used at least 0.22/254.46 KiB (0.1%) of stack space

let's do this :rocket:
bors r+

bors r+


⚠ Bofrost.at has degraded performance

In 21b1a9d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1656 ms

Resolved: Bofrost.at performance has improved in 2ae1429 after 13 minutes.


Error running app. If this keeps happening, please contact support.

Thank you so much. Will check it out again today. We are doing a POC for a public sector client. The use case is exactly what your app does. Let the end users draw meaningful insights into the raw data (csv and json) that we publish on the client website.
Do you have any guidelines/ suggestions on how to quickly do a POC with customized UI (customer logo etc).?
Thanks and Regards,
Priyaroop Singh

From: Pablo Marin @.>
Sent: Tuesday, May 16, 2023 10:38:53 AM
To: pablomarin/GPT-Azure-Search-Engine @.>
Cc: Priyaroop Singh @.>; Author @.>
Subject: Re: [pablomarin/GPT-Azure-Search-Engine] Error running app. If this keeps happening, please contact support. (Issue #29)
[EXTERNAL]: This email originated from outside OnActuate. Be Cautious when opening attachments & links.
Yes, we are aware, just a lot of demand for the free version of streamlit cloud.
We just moved it to Azure Web App and should handle the load
—
Reply to this email directly, view it on GitHubhttps://github.com/pablomarin/GPT-Azure-Search-Engine/issues/29#issuecomment-1550098018, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEHA5IL65PAENAIBI2J4H6LXGO3S3ANCNFSM6AAAAAAYDBMX5A.
You are receiving this because you authored the thread.Message ID: @.***>
This email and its attachments are intended exclusively for the named addressees and may contain information that is confidential, commercially sensitive and/or privileged. If you are not the addressee, please be advised that you have received this email in error and you must not read, use. Disseminate, forward, print, copy and/or disclose the contents of this e-mail. If you receive this e-mail in error, please advise us immediately and permanently delete the e-mail. Every reasonable precaution has been taken to ensure that any attachment to this e-mail has been swept for viruses, however, it is the sole responsibility of the recipient(s) to ensure that the email and attachments are virus free. OnActuate Consulting Inc, nor any of its subsidiaries, associates or holding companies, cannot and do not accept liability for any damage sustained as a result of software viruses, malware or other malignant code and would advise that you carry out your own virus checks before opening any email or attachment to this email. OnActuate Consulting Inc maintains a policy of email monitoring including spot checks and audits to detect unauthorised use of its email system. Any email may therefore be intercepted and/or subject to review.

I keep getting this error –
⚠ Too many failed retries. Try Again - RateLimitError: Requests to the Creates a completion for the chat message Operation under Azure OpenAI API version 2023-03-15-preview have exceeded call rate limit of your current OpenAI S0 pricing tier. Please retry after 6 seconds. Please contact Azure support service if you would like to further increase the default rate limit..
Thanks and Regards,
[photograph]
Priyaroop Singh
Technical Architect | Onactuate
m: + 1<PHONE_NUMBER>
e: @.***
777, Hornby Street,
Vancouver, Canada
www.onactuate.comhttp://www.onactuate.com/
[facebook icon]https://www.facebook.com/profile.php?id=100015262663408 [twitter icon] https://twitter.com/smultronstalet  [youtube icon] https://www.youtube.com/user/CodeTwoChannel  [linkedin icon] https://www.linkedin.com/in/priyaroop-singh-1860363/  [google plus icon] https://plus.google.com/+PriyaroopSingh  [instagram icon] https://www.instagram.com/priyaroopsingh/
From: Priyaroop Singh @.>
Date: Tuesday, May 16, 2023 at 10:42 AM
To: pablomarin/GPT-Azure-Search-Engine @.>, pablomarin/GPT-Azure-Search-Engine @.>
Cc: Author @.>
Subject: Re: [pablomarin/GPT-Azure-Search-Engine] Error running app. If this keeps happening, please contact support. (Issue #29)
Thank you so much. Will check it out again today. We are doing a POC for a public sector client. The use case is exactly what your app does. Let the end users draw meaningful insights into the raw data (csv and json) that we publish on the client website.
Do you have any guidelines/ suggestions on how to quickly do a POC with customized UI (customer logo etc).?
Thanks and Regards,
Priyaroop Singh

From: Pablo Marin @.>
Sent: Tuesday, May 16, 2023 10:38:53 AM
To: pablomarin/GPT-Azure-Search-Engine @.>
Cc: Priyaroop Singh @.>; Author @.>
Subject: Re: [pablomarin/GPT-Azure-Search-Engine] Error running app. If this keeps happening, please contact support. (Issue #29)
[EXTERNAL]: This email originated from outside OnActuate. Be Cautious when opening attachments & links.
Yes, we are aware, just a lot of demand for the free version of streamlit cloud.
We just moved it to Azure Web App and should handle the load
—
Reply to this email directly, view it on GitHubhttps://github.com/pablomarin/GPT-Azure-Search-Engine/issues/29#issuecomment-1550098018, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEHA5IL65PAENAIBI2J4H6LXGO3S3ANCNFSM6AAAAAAYDBMX5A.
You are receiving this because you authored the thread.Message ID: @.***>
This email and its attachments are intended exclusively for the named addressees and may contain information that is confidential, commercially sensitive and/or privileged. If you are not the addressee, please be advised that you have received this email in error and you must not read, use. Disseminate, forward, print, copy and/or disclose the contents of this e-mail. If you receive this e-mail in error, please advise us immediately and permanently delete the e-mail. Every reasonable precaution has been taken to ensure that any attachment to this e-mail has been swept for viruses, however, it is the sole responsibility of the recipient(s) to ensure that the email and attachments are virus free. OnActuate Consulting Inc, nor any of its subsidiaries, associates or holding companies, cannot and do not accept liability for any damage sustained as a result of software viruses, malware or other malignant code and would advise that you carry out your own virus checks before opening any email or attachment to this email. OnActuate Consulting Inc maintains a policy of email monitoring including spot checks and audits to detect unauthorised use of its email system. Any email may therefore be intercepted and/or subject to review.

Yes, unfortunately AzureOpenAI  preview GPT-4 is being very limited right now :/

Thank you so much. Will check it out again today. We are doing a POC for a public sector client. The use case is exactly what your app does. Let the end users draw meaningful insights into the raw data (csv and json) that we publish on the client website. Do you have any guidelines/ suggestions on how to quickly do a POC with customized UI (customer logo etc).? Thanks and Regards, Priyaroop Singh
…

Yes, just for the repo, and use your own files and data, then edit app/pages/3 and use your own document

Apps are now migrated to Azure Web App. This error doesn't happen anymore


remove manifest file before deploy

@hootan-nik I also ran into issues on 0.0.5. This task solved it for me:
before 'deploy:assets:update_asset_mtimes', 'deploy:assets:cleanup_manifests'

namespace :deploy do
  namespace :assets do
    task :cleanup_manifests, roles: :web, except: {no_release: true} do
      run "rm #{shared_path}/assets/manifest-*.json"
    end
  end
end


[mesecons] Microcontroller(FPGA) has same craft recipe than LUAController

Actually Microcontroller (aka FPGA) has same craft recipe than LUAController:

The Microcontroller should have the following craft recipe:

Just change this and get good https://github.com/MinetestForFun/server-minetestforfun/blob/master/mods/mesecons/mesecons_microcontroller/init.lua#L145

I gave my approval for the merge of the PR, thank you @sys4-fr


Address issues in auto-generated CDDL specification

Description
This addresses issue https://github.com/IntersectMBO/cardano-ledger/issues/4462

Moves some core type CDDL definitions to cardano-ledger-core
Defines Shelley CDDL types through Huddle
Adds huddle-based testing in Shelley
Moves the Shelley CDDL to being auto-generated via the Huddle def
Updates Conway to use some definitions from Shelley where they were unchanged
Updates the gen-cddl.sh script to check Shelley definitions

One unexpected change: the huddle definition for protocol_param_updates has a size limit on the max block header size. This is consistent with the Haskell serialisers and data structure.
In addition, we add a couple of extra commits solving two issues:

#4522 - we reintroduce the long explanations of various types which were subsequently not included in the generated CDDL.
#4535 - we add a root element as the first element in the generated CDDL

Note that this PR now incorporates the contents of #4552
Checklist

[x] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages.
New section is never added with the code changes. (See RELEASING.md)
[ ] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[x] The version bounds in .cabal files for all affected packages are updated.
If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[x] Self-reviewed the diff

In addition to documentation comments, is it possible to regroup definitions please. For example, currently the conway certificates definitions are all over the place. It seems they are sorted alphabetically, which isn’t useful.

Rebased on master, to remove the master-merge commit


Create sample that shows how to integrate with Azure Active Directory ( AAD )

It is known that Azure Active Directory endpoints do not allow Cross Origin Resourece Sharing (CORS).
Others have documented it is a PITA to integrate with Azure Active https://github.com/manfredsteyer/angular-oauth2-oidc/issues/135
Others got frustrated about Azure AD not respecting OIDC, so they switched to using their own library directly https://github.com/manfredsteyer/angular-oauth2-oidc/issues/126

We will write something down regarding ADFS and Azure AD. For the time beeing, you might find the following snippet from a real-world project useful.
All those things can also be configured within an config-object passed to .configure(...).
this.oauthService.redirectUri = environment.oauthRedirectUri;
this.oauthService.clientId = 'client-id';
this.oauthService.responseType = 'code token id_token';
this.oauthService.scope = 'openid allatclaims';
this.oauthService.logoutUrl = 'https://adfs-test.de/adfs/oauth2/logout';
this.oauthService.issuer = 'https://adfs-test.de/adfs';

/* This needs to be set manually b/c ADFS and Azure AD do not support CORS */
this.oauthService.resource = 'urn:example:example';
this.oauthService.userinfoEndpoint = 'https://adfs-test.de/adfs/userinfo';
this.oauthService.loginUrl = 'https://adfs-test.de/adfs/oauth2/authorize/';
this.oauthService.tokenEndpoint = 'https://adfs-test.de/adfs/oauth2/token/';

this.oauthService.events.pipe(filter(e => e.type === 'token_received')).subscribe(_ =>
{
   // do this and that ...
});

this.oauthService.tokenValidationHandler = new NullValidationHandler();

Another thing to consider is that you have to configure two apps/resources in your Azure AD: The client (Angular app) and the Backend.

Hi manfredsteyer,
Thank you for the library. I used to create an Ionic App and worked very well.
Now I am trying to do the same with Azure AD, using the v1 or v2. Doing some research, I notice that Azure doesn't allow call and get the discovery document because they don't have the CORS enabled (like @mores comment before).
Do you have success to write an example using AAD? I am struggling to understand the different URLs that Azure provides in the configuration and how to use them using your last sample code posted here.
In my app, I am getting a valid token and sending to the API, and there I am validating using the .Net Core JWT authentication.
services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme).AddJwtBearer(options =>
   {
      options.Authority = "https://dev-262704.oktapreview.com/oauth2/default";
      options.Audience = "api://default";
   });

I think that this is needed:
this.oauthService.strictDiscoveryDocumentValidation = false;
other wise you get
discovery_document_validation_error

When I tried the scope per your comment, azure is reporting:
The scope openid allatclaims is not valid
so I am using
this.oauthService.scope = 'openid';

"oauth2AllowImplicitFlow": true, should be in the Manifest of the registered app inside of Azure Active Directory admin center

Here is my extremely simple Login button for Azure: https://github.com/mores/angular-examples/tree/master/oidc-azure
I update src/app/app.component.ts with my guid tenant - and my client id
After hitting the login button, the url that shows in my browser is in the form of https://demo:4200/#access_token=eyJ0eXAiOiJ<  snip  >Vio68Xw &token_type=Bearer&expires_in=14399&scope=email+openid+profile&id_token=eyJ0eXAiOiJ<  snip  >IrXM4i1J8Q&state=Pxz<  snip  >a08&session_state=5e798974-<  snip  >-cdf9dcb4c3a0
I have gotten back valid tokens from Azure.
Console shows:
error loading jwks angular-oauth2-oidc.js:521
has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Any help is appreciated.

If you get a CORS error, is there also a failed request in the network tab of your dev tools? What host is it trying to reach?
If you could also add this gist's code way up early in your code, then you'd also get some additional logging you could share, so we can know what bit of logic in the library is causing the CORS request.

I do not see any errors in the network tab.
There are two OAuthErrorEvent
type: "jwks_load_error"
statusText: "Unknown Error"
type: "discovery_document_load_error"
statusText: "Unknown Error"
It is having issues with this url: https://login.microsoftonline.com/ < enter guid here>/discovery/v2.0/keys

I now understand what @manfredsteyer was trying to say in his comment above....
any and all communication is proxied  through adfs-test.de.
adfs-test.de is a private server needed to facilitate the communication from angular to azure.

Other people are having issues validating token too: https://github.com/Microsoft/azure-spring-boot/issues/476

Currently, I made it work with Azure B2C with the following setup:
import { Injectable } from '@angular/core';
import { OAuthService } from 'angular-oauth2-oidc';
import { MyValidationHandler } from './validation.handler';

@Injectable({
  providedIn: 'root'
})
export class AuthService {

  constructor(private oauthService: OAuthService, private validationHandler: MyValidationHandler) {
  }

  getIdentityClaims() {
    return this.oauthService.getIdentityClaims();
  }
  logout() {
    this.oauthService.logOut();
  }
  login() {
    this.oauthService.initImplicitFlow();
  }

  setup() {
    this.oauthService.configure({
      responseType: 'token id_token',
      logoutUrl: 'http://localhost:8080/',
      issuer: 'https://<name>.b2clogin.com/<name>.onmicrosoft.com/v2.0/',
      strictDiscoveryDocumentValidation: false,
      tokenEndpoint: 'https://<name>.b2clogin.com/<name>.onmicrosoft.com/oauth2/v2.0/token?p=signinsignup',
      loginUrl: 'https://devcvp.b2clogin.com/devcvp.onmicrosoft.com/oauth2/v2.0/authorize?p=b2c_1_signinsignup',
      redirectUri: 'http://localhost:8080/login/oauth2/code/dsa-azure-b2c',
      clientId: '<client-id>',
      dummyClientSecret: '<secret>',
      scope: 'openid offline_access ....',
      skipIssuerCheck: true,
      oidc: true,
    });
    this.validationHandler.setKeyUri('https://<name>.b2clogin.com/<name>.onmicrosoft.com/discovery/v2.0/keys?p=signinsignup');
    this.oauthService.tokenValidationHandler = this.validationHandler;
    this.oauthService.setStorage(sessionStorage);

    this.oauthService.tryLogin({});
  }
}

I also had to use the PR #527 from @ismcagdas. Otherwise the flow fails.
Furthermore, to validate the tokens, I adapted the JwkValidationHandler to first fetch the keys from a configured URL, though nothing complicated.
Hope this helps.

I think I found out what "special processing" means:
https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/609#issuecomment-405683736
( Azure is adding a ‘nonce’ to the header - The JWS is signed with a SHA2 of the nonce, the ‘nonce’ is replaced before the JWS is serialized. )
It sounds like there is a need for a AzureValidationHandler to validate the access token.

I think I have a good working example now: https://github.com/mores/angular-examples/tree/master/oidc-azure
This ONLY utilizes an idToken, which will validate from a subclass of JwksValidationHandler.

They seem to have enabled CORS for their jwks endpoint now. Best to switch over or get caught out like we did with a cached copy of the old keys.

I am totally new in OIDC and need to use OIDC with Azure active directory.  Does any one have a working example where no Identity server is required. I tried Mores's example but it also need a 'PRIVATE_PROXY_SERVER'.

Where did you get the issuer url in the portal?

Where did you get the issuer url in the portal?

If you open 'https://login.microsoftonline.com/common/v2.0/.well-known/openid-configuration' (the standard OIDC discovery endpoint) you get all the JSON data for their configuration. Replace 'common' with your Azure tenant ID for more specific values.

I think I have a good working example now: https://github.com/mores/angular-examples/tree/master/oidc-azure
This ONLY utilizes an idToken, which will validate from a subclass of JwksValidationHandler.

Hello @mores
I followed your example. I did not understand this part (app.component.ts) :
this.oauthService.loadDiscoveryDocument( 'https://' + PRIVATE_PROXY_SERVER + '/angular2azure/openid-configuration?tenant=' + TENANT_GUID ).then( doc => {......
So, I change it for:
this.oauthService.loadDiscoveryDocument('https://login.microsoftonline.com/thisismydirectoryname.onmicrosoft.com/v2.0/.well-known/openid-configuration').then( doc => {....
And It started to work, so now everything is fine.. I'm going to adapt this to my actual project..
Thanks a lot!

I wrote a blog post about how to use the component with Azure AD B2C:
https://about-azure.com/2019/09/26/using-azure-ad-b2c-with-angular-8/
The post includes a live demo and the source code. Hope that helps you.

Does anyone have experience with the userinfo endpoint?
The following code leads to a 401 - "Access token validation failure. Invalid audience."
oauthService.loadUserProfile().then(u => console.log(u));

@gerbermichi This is my solution:
this.oauthService.loadDiscoveryDocumentAndLogin().then(() => {       this.oauthService.loadUserProfile().then(profile => {         this.userProfile = profile;       }); });

Does anyone implement in Azure AD (not Azure B2C) with PCKE successfully? Thanks.

Does anyone implement in Azure AD (not Azure B2C) with PCKE successfully? Thanks.


DropCursorBridge is not exported

Hey there! tried open a small PR for this but don't have write access.
As the title says, the DropCursor bridge is there and all but is not exported on src/index.tsx. Super small fix

Oh my bad, I will push a fix
Btw, you could fork this repo and open a pr between your fork and this repo

Released!

Oh my bad, I will push a fix Btw, you could fork this repo and open a pr between your fork and this repo

Oh didn't know this was a thing, great


Modify deadline date

change functionality of deadlinedate such that date earlier than today wont be accepted
update austenjs PPP

Codecov Report

Merging #279 (dd62bce) into master (9e30d0f) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #279      +/-   ##
============================================
+ Coverage     66.43%   66.47%   +0.03%
  Complexity      535      535
============================================
  Files            99       99
  Lines          1874     1879       +5
  Branches        193      194       +1
============================================
+ Hits           1245     1249       +4
  Misses          566      566
- Partials         63       64       +1

Impacted Files
Coverage Δ
Complexity Δ

.../java/seedu/address/model/person/DeadlineDate.java
95.23% <100.00%> (+0.50%)
11.00 <0.00> (+1.00)

.../java/seedu/address/model/util/SampleDataUtil.java
28.00% <100.00%> (+9.81%)
2.00 <0.00> (ø)

...ess/model/person/DeadlineDateInRangePredicate.java
70.83% <0.00%> (-4.17%)
11.00% <0.00%> (-1.00%)

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 9e30d0f...dd62bce. Read the comment docs.


Extract Work Item Repository From Service

It would make sense to extract storage & query of work items into a separate module serving as a repository. See http://martinfowler.com/eaaCatalog/repository.html

How is this different from https://github.com/almighty/almighty-core/issues/28 ?

It has a more descriptive title? No, it's the same thing.


The ops modules should always return results

Currently we return Type::Void when an operation isn't allowed. It's a bit janky, but can give us some bad type-errors. We could guess what type we should return and return that, which would give better type-errors. Now we kinda get a series of faults from 1 error.

Isn't this solved by #254 ?


[AMORO-1765]: Add metric collection API

Why are the changes needed?
resolve #1765
Brief change log
Add metric interface
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (not documented)

Perhaps a tool should be provided to convert iceberg metric into com.codahale.metrics.Metric?

@huyuanfeng2018 The utility class for converting Iceberg metrics to com.codahale.metrics.Metric will be defined together with IcebergReporter, as they both require dependencies on iceberg-core and iceberg-api. However, ams-api itself does not need to depend on these two modules. WDYT.

Perhaps a tool should be provided to convert iceberg metric into com.codahale.metrics.Metric?

@huyuanfeng2018 The utility class for converting Iceberg metrics to com.codahale.metrics.Metric will be defined together with IcebergReporter, as they both require dependencies on iceberg-core and iceberg-api. However, ams-api itself does not need to depend on these two modules. WDYT.

ok

Perhaps a tool should be provided to convert iceberg metric into com.codahale.metrics.Metric?

@huyuanfeng2018 The utility class for converting Iceberg metrics to com.codahale.metrics.Metric will be defined together with IcebergReporter, as they both require dependencies on iceberg-core and iceberg-api. However, ams-api itself does not need to depend on these two modules. WDYT.

1

LGTM.

It feels a bit confusing, some are called reporters and some are called Emitters


Basic impl for #147

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/105/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/107/


High memory consumption

Description
Cmpiling application with couple of reducers (~20) and action creators (~200) takes 2 GB RAM and requires passing --max-old-space-size to node when invoking tsc. Before fixing #164 it was much worse but it is still unuseable.
Steps to Reproduce
Steps to reproduce the behavior:

Download and unpack https://drive.google.com/file/d/1FUzk5NeRfxUvwd4eXCxIFcb7Scmvh9D4/view?usp=sharing
run npm i
run node --max-old-space-size=8192 ./node_modules/.bin/tsc --diagnostics
See the result

Expected behavior
Compilation of such project should be a piece of cake ;-)
Suggested solution(s)
Improve types or identify bug in TypeScript.
Project Dependencies

Typesafe-Actions Version: 4.4.1
TypeScript Version: 3.5.2
tsconfig.json: included in the tgz

Environment (optional)

OS: Debian Linux Buster
Node Version: 12.4.0
Package Manager and Version: npm 6.9.0

I can confirm that as well. Cold start of tsc still takes too much of the resources and time.

Probably related to this, I noticed when I changed all my reducers from standard switch case to createReducer, compiler typechecking and autocomplete slowed down noticably to the point where it's painful to use

@mmalicki that was actually also my case

Thanks for the reproduction case 👍. I have confirmed an issue and will be working on that.

I can confirm the issue. Thanks so much for looking into it!

PR is ready, now it's infinitely scalable. will release a new version tomorrow.
@zdila You can test it now using the following in your project to confirm:
npm i piotrwitek/typesafe-actions##168

@piotrwitek thanks, but with npm i piotrwitek/typesafe-actions##168 there is no more dist in node_modules/typesafe-actions.

@zdila you can build the project locally and copy the dist folder or wait for me to release under the next branch in a few hours

Published on npm as @next

Shouldn't that be released as v4.5.0 since it's a major performance issue?

There is a breaking change in the API and I'm respecting semver.
But I might consider it if that is something critical to the majority of the users.

After upgrading to @next release, project hangs on tsc again with memory leak at the end (19x createAsyncAction, 1x createStandardAction).
4.4.2 is working fine.
What can I do to provide you more details?

In my case typesafe-actions@next works now fine on my project. Thanks Piotr.

@hsz take a look at great reproduction example from @zdila above and try to isolate the issue in your project the same way. Only this way we can confirm the issue is on our end and not within your application setup.


can this project handle million of  one time task?

I got 30 million  users, every one has one task specified on at specific day, note not  the same date,  for example,
user1, got a task , run at 2021-10-3 23:19:00
user2, got a task , run at 2021-11-3 13:19:00
...

30 million tasks,  which means we have no way to load all tasks into memory, does this project support this case please ?

Hi, friend @vidyli
I've dealt with a requirement similar to yours, kind of like sending birthday wishes to a user~
I handled this requirement by delicate like this.
Design two execution tasks that
Task A: keep processing the user's tasks to aggregate them in time on a BTree on disk or in a database.
Task B: keep getting the machine time, fetching the corresponding data from the BTree or the database, and executing the user's tasks.
I don't know if this is for you, but if you have any questions you can contact me  :) .


Use explicit IndexMap::swap_remove in Sabre

Summary
indexmap are moving to deprecate the remove function to push people to be explicit about whether they want swap_remove or shift_remove in IndexMap 2.2.0.  Sabre doesn't care about the order provided it's deterministic and reproducible, so we just use the more efficient swap.

Details and comments
Needed for #11663.

I did actually originally write the patch on that branch, but then I thought that there's a chance that a screw-up in this patch could affect the output of Sabre, so I wanted the full justification to appear in its own place in the commit history.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
20 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.02%) to 89.531%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
2
92.44%

crates/qasm2/src/parse.rs
18
96.69%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
59541

Relevant Lines:
66503

💛  - Coveralls


CSS Files collide with bootstrap and creative team css

there should be a way to scope the calendar styles with the components itself, there is no way a single component breaks the entire page styling lol.
Also How can I set a week view? I literally tried everything without good results :)

I've tried to implement this way:
`

I've tried to implement this way:
<style scoped>     @import '~vuetify/dist/vuetify.min.css';     @import '~material-design-icons-iconfont/dist/material-design-icons.css';     @import '~dayspan-vuetify/dist/lib/dayspan-vuetify.min.css'; </style>

I've tried to implement this way inside the component:
<style scoped>     @import '~vuetify/dist/vuetify.min.css';     @import '~material-design-icons-iconfont/dist/material-design-icons.css';     @import '~dayspan-vuetify/dist/lib/dayspan-vuetify.min.css'; </style>


fix(zipAll): complete when the source is empty

This fixes the situation where the zipAll() operator doesn't send complete notification when the source Observable is empty:
Observable
  .empty()
  .zipAll()
  .subscribe(null, null, () => console.log('complete 1'));

This doesn't print anything. Demo: https://jsbin.com/fucijuz/2/edit?js,console
Description:
This problem occurs only when using zipAll() and not zip(). The zip() operator internally wraps zipAll() with ArrayObservable. So the following works fine:
Observable
  .zip(Observable.empty())
  .subscribe(null, null, () => console.log('complete 2'));

This is internally called as:
Observable
  .from([Observable.empty()])
  .zipAll()
  .subscribe(null, null, () => console.log('complete 3'));

which is all right.
Related issue (if exists):
#2426

Coverage increased (+0.001%) to 97.689% when pulling 712feceb78ed018c30f71012ec3a6a7f1a0f4162 on martinsik:zip-send-complete-on-empty into 69d051bc56cb337148db30515029363c1e78b90d on ReactiveX:master.


Update the CCAL releases please!

Are the releases supposed to mirror each version? If you pip install ccal currently, you get version 7.2.

Got it. Done.


Combination of old and new route definition syntax in same app breaks ziggy.

Ziggy version
v1.5.0
Laravel version
v9.0
Description
We are working on a large scale application that has recently upgraded to Laravel 8.0. The application makes use of both the old (string) and new (array) syntax in different parts in the app for defining routes.
new
Route::get('/example', [ExampleController::class, 'exampleMethod']);
and
old
Route::get('/example', 'ExampleController@exampleMethod');
However Ziggy doesn't seem to support using both the old and the new syntax at the same time. Only allowing the old syntax where a route is defined via a string. The following error is thrown while generating the route file for the new syntax:

[2023-04-14 09:54:03] local.ERROR: ReflectionFunction::__construct(): Argument #1 ($function) must be of type Closure|string, array given (View: /var/www/dossierdata/resources/views/index.blade.php) (View: /var/www/dossierdata/resources/views/index.blade.php) {"userId":2,"exception":"[object] (Illuminate\\View\\ViewException(code: 0): ReflectionFunction::__construct(): Argument #1 ($function) must be of type Closure|string, array given (View: /var/www/dossierdata/resources/views/index.blade.php) (View: /var/www/dossierdata/resources/views/index.blade.php) at /var/www/dossierdata/vendor/laravel/framework/src/Illuminate/Routing/RouteSignatureParameters.php:27)
[stacktrace]

To try and workaround this issue I thought I might define a filter array under config/ziggy.php to only allow generation for route definitions using the old syntax. But after looking at the Ziggy source code it seems that ziggy is still retrieving and processing routes that are excluded under config/ziggy.php.
Any help is much appreciated.
Ziggy call and context
I installed Ziggy as described in the documentation. I'm using Ziggy by adding the @routes directive to our head tag in index.blade.php. The error is thrown after I add the @routes directive and try to visit the website.

Ziggy configuration
A Ziggy object hasn't been generated yet because the error is being thrown during the build process.

Route definition
Route::get('/example', [ExampleController::class, 'exampleMethod']);

Can you share the full stack trace and a more complete example route definition? E.g. if you're importing the controller class or adding any middleware to the route. It doesn't look like that error is coming from your routes file.

This doesn't look related to Ziggy. Feel free to comment again if you can share more information or reproduce this in a fresh app.


c2/cuda/groth16_*: refactor tail msm prep.

tolerate more variations in circuits;
shorten variable names;

Merged by 4051de496b6b26fbeb7f8fc813a6d9f52c44e528.


what about MICA MICB typing

Dear OptiType,
May I ask does Optitype support MICA, MICB typing? It work pretty well on genotyping HLA genes, but will it also work on MICA and MICB? Thanks in advance.
Yours,
Ying

The following system can do this：http://hla.duxactcl.com/


fix(v2): to fix the canary release GH workflow

Motivation
WIP, trying to fix the broken GH action introduced in https://github.com/facebook/docusaurus/pull/3827

Note:
It seems a npm auth token with role "automation" (allow to publish without 2FA auth)  can't run npm access ls-packages (Lerna tries to run it by default)


Implementation: Support for Bearer token auth between Service Catalog and brokers

Bearer token auth support code implementation based on the ideas from two proposals:

Proposal for opaque bearer token auth https://github.com/kubernetes-incubator/service-catalog/pull/1044
Proposal for additional auth support https://github.com/kubernetes-incubator/service-catalog/pull/1037

Note that there are some differences in the implementation compared to the proposals mentioned above.
I went without extra abstraction of AuthInterface for now, just extended existing AuthConfig type. While it's not as flexible as AuthInterface approach, it is much easier to reason about, and does not have to provide an abstraction for other auth techniques, such as x509 mentioned in https://github.com/kubernetes-incubator/service-catalog/pull/1037#discussion_r127596077.

/cc @liggitt @rifung @ash2k @bmelville @pmorie

/cc @arschles

/retest

I'm wondering, is there no controller_test.go with tests for the bulk of the code you've modified?

@bmelville I'm happy to add one if the code itself looks good.
I don't see a separate test for (existing) basic auth either, though.

I'd like to reserve the chance to add the second LGTM here

@pmorie finished making changes to switch to the union type, please review.

Then how about a type field? It just feels clunky to bake the type into the
name since for any new method we have to add effectively code to the
controller to simply add a strong that encodes the type of token.
On Tue, Aug 1, 2017, 18:06 Paul Morie<EMAIL_ADDRESS>wrote:

@pmorie commented on this pull request.
In pkg/apis/servicecatalog/v1alpha1/types.go
https://github.com/kubernetes-incubator/service-catalog/pull/1053#discussion_r130651507
:

type BrokerAuthInfo struct {

// BasicAuthSecret is a reference to a Secret containing auth information the
// catalog should use to authenticate to this Broker using basic auth.
BasicAuthSecret *v1.ObjectReference json:"basicAuthSecret,omitempty"

// Basic provides configuration for basic authentication
Basic *BasicAuthConfig json:"basic,omitempty"
// Bearer provides configuration for bearer token authentication
Bearer *BearerTokenAuthConfig json:"bearer,omitempty"

Seems like entirely opaque auth header is not usable with k8s service
account tokens. I'm not against fully opaque controller over the auth
header value, but i think we should also have something that works
correctly with k8s service account tokens.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/service-catalog/pull/1053#discussion_r130651507,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKwedKFfC-TEkFt7Nx8ILf6txSxGzcmGks5sT00DgaJpZM4OdkmI
.

Then how about a type field? It just feels clunky to bake the type into the name since for any new method we have to add effectively code to the controller to simply add a strong that encodes the type of token.

basic and bearer auth schemes account for the majority of the static credentials you are going to encounter. I think it is worth integration with those in a first-class way. If you run into other use cases, a fully generic Authorization header option could be added later, but I'm skeptical that will be necessary (most others I'm aware of have a dynamic component, like negotiate, etc)

Bearer is not static though? It's only static because something else
exchanges the refresh token for a bearer token?
On Tue, Aug 1, 2017, 18:49 Jordan Liggitt<EMAIL_ADDRESS>wrote:

Then how about a type field? It just feels clunky to bake the type into
the name since for any new method we have to add effectively code to the
controller to simply add a strong that encodes the type of token.
basic and bearer auth schemes account for the majority of the static
credentials you are going to encounter. I think it is worth integration
with those in a first-class way. If you run into other use cases, a fully
generic Authorization header option could be added later, but I'm skeptical
that will be necessary (most others I'm aware of have a dynamic component,
like negotiate, etc)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/service-catalog/pull/1053#issuecomment-319429311,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKwedAys3FgLuP3ku39h1UCmuOmEyFRYks5sT1cIgaJpZM4OdkmI
.

Bearer is not static though? It's only static because something else exchanges the refresh token for a bearer token?

By static, I mean not tied to a particular request, as opposed to a Authorization: Negotiate authorization that requires sending the same request multiple times, changing what is sent in response to a WWW-Authenticate challenge from the server

@nilebox you can eliminate the OSB bump in this PR now.

@pmorie I think this PR is ready to be merged now.


ERROR: Failed building wheel for gym: wheel.vendored.packaging._tokenizer.ParserSyntaxError: Expected end or semicolon (after version specifier)

While installing gym==0.21.0, this error is seen.
Its seems to be broken since 2-3 weeks.
14:12:26        Traceback (most recent call last):
14:12:26          File "/usr/local/lib/python3.8/site-packages/wheel/vendored/packaging/requirements.py", line 35, in init
14:12:26            parsed = parse_requirement(requirement_string)
14:12:26          File "/usr/local/lib/python3.8/site-packages/wheel/vendored/packaging/_parser.py", line 64, in parse_requirement
14:12:26            return _parse_requirement(Tokenizer(source, rules=DEFAULT_RULES))
14:12:26          File "/usr/local/lib/python3.8/site-packages/wheel/vendored/packaging/_parser.py", line 82, in _parse_requirement
14:12:26            url, specifier, marker = _parse_requirement_details(tokenizer)
14:12:26          File "/usr/local/lib/python3.8/site-packages/wheel/vendored/packaging/_parser.py", line 126, in _parse_requirement_details
14:12:26            marker = _parse_requirement_marker(
14:12:26          File "/usr/local/lib/python3.8/site-packages/wheel/vendored/packaging/_parser.py", line 147, in _parse_requirement_marker
14:12:26            tokenizer.raise_syntax_error(
14:12:26          File "/usr/local/lib/python3.8/site-packages/wheel/vendored/packaging/_tokenizer.py", line 163, in raise_syntax_error
14:12:26            raise ParserSyntaxError(
14:12:26        wheel.vendored.packaging._tokenizer.ParserSyntaxError: Expected end or semicolon (after version specifier)
14:12:26            opencv-python>=3.
14:12:26                         ~~~^
14:12:26
14:12:26        The above exception was the direct cause of the following exception:
14:12:26
14:12:26        Traceback (most recent call last):
14:12:26          File "", line 2, in
14:12:26          File "", line 34, in
14:12:26          File "/tmp/pip-wheel-34ur4kuy/gym_f74ca167b0dc4f1da53d4decc6d2d4f6/setup.py", line 39, in
14:12:26            setup(
14:12:26          File "/usr/local/lib/python3.8/site-packages/setuptools/init.py", line 153, in setup
14:12:26            return distutils.core.setup(**attrs)
14:12:26          File "/usr/local/lib/python3.8/distutils/core.py", line 148, in setup
14:12:26            dist.run_commands()
14:12:26          File "/usr/local/lib/python3.8/distutils/dist.py", line 966, in run_commands
14:12:26            self.run_command(cmd)
14:12:26          File "/usr/local/lib/python3.8/distutils/dist.py", line 985, in run_command
14:12:26            cmd_obj.run()
14:12:26          File "/usr/local/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 395, in run
14:12:26            self.egg2dist(self.egginfo_dir, distinfo_dir)
14:12:26          File "/usr/local/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 534, in egg2dist
14:12:26            pkg_info = pkginfo_to_metadata(egginfo_path, pkginfo_path)
14:12:26          File "/usr/local/lib/python3.8/site-packages/wheel/metadata.py", line 160, in pkginfo_to_metadata
14:12:26            for key, value in generate_requirements({extra: reqs}):
14:12:26          File "/usr/local/lib/python3.8/site-packages/wheel/metadata.py", line 138, in generate_requirements
14:12:26            for new_req in convert_requirements(depends):
14:12:26          File "/usr/local/lib/python3.8/site-packages/wheel/metadata.py", line 103, in convert_requirements
14:12:26            parsed_requirement = Requirement(req)
14:12:26          File "/usr/local/lib/python3.8/site-packages/wheel/vendored/packaging/requirements.py", line 37, in init
14:12:26            raise InvalidRequirement(str(e)) from e
14:12:26        wheel.vendored.packaging.requirements.InvalidRequirement: Expected end or semicolon (after version specifier)
14:12:26            opencv-python>=3.
14:12:26                         ~~~^
14:12:26        [end of output]
14:12:26
14:12:26    note: This error originates from a subprocess, and is likely not a problem with pip.
14:12:26    ERROR: Failed building wheel for gym
14:12:26    Running setup.py clean for gym
building_wheel_gym_error.log

Yes, this looks identical to the issue mentioned here.
I could try to see if I could fix gym myself on my own fork.

Went down a small rabbit hole and found something surprising. There is a breaking issue with gym>=0.22 (see here), which sb3 depends on. Hence sb3 has a strict dependency to only support gym==0.21, which seems to have all kinds of fun issues.
Hence, upgrading gym is not an option.
However, setting setuptools==66 should resolve the issue. I observed something similar on colab and I managed to fix it by installing pip install setuptools==66 before running pip install -r requirements.txt (see here for more information).
It works on colab now but I will see if it passes the unit tests. Could you try to install the correct version of setuptools before trying to install the remainder of the deps?

I made a gist here for you to try. At least it works there.

All CI jobs were successful (see here). It also works fine on google colab (see here).
Are you sure you ran pip install setuptools==66 before installing any dependencies? Did you create a virtual environment?
Lastly, it might be that upgrading pip resolves the issue. In the colab, I'm using a very new version of pip. Try upgrading to latest:
pip install --upgrade pip

@andreped : setuptools were added in requirement.txt. It was installed alng with other python modules.
And, Iam using python:3.8 container image, And we havent created any virtual env.
Let me try to upgrade the pip.

Working Solution:
pip3 install --no-cache-dir --no-deps -r requirements.txt --timeout 60 --> Here, setuptools==66 was used. pip upgrade was not done.
Non-Working Solution:
pip3 wheel --no-cache-dir --no-deps --wheel-dir /wheels -r requirements.txt --timeout 60
Why we use wheels?
Machine learning based container images are very huge.
So, we use the python image to install wheels and then only wheels are copied to final image. This reduces the final image size.
Ex:
FROM python:3.8 as builder
RUN mkdir -p /ws/
WORKDIR "/ws/"
COPY src/requirements.txt requirements.txt
RUN pip3 install --upgrade pip
&& pip3 install --no-cache-dir --no-deps setuptools==66 --timeout 60
&& *pip3 wheel --no-cache-dir --no-deps --wheel-dir /wheels -r requirements.txt --timeout 60 *
&& rm -rf /ws
WORKDIR "/"
FROM python:3.8-slim as runner
RUN mkdir -p /ws/
WORKDIR "/ws/"
COPY --from=builder /wheels /wheels
#RUN pip install --upgrade pip
RUN pip install --no-cache-dir --no-deps /wheels/ *
&& rm -rf /wheels
&& rm -rf /ws

Ok, it seems like --no-deps is the key here.
We use docker as well when we run the CI tests. It is still strange to me why it didn't work for you while it seems to work most other places.
As you use docker, it might be that you are missing some key dependency that resolves this.

But, in our case, Error is seen in this step:
pip3 wheel --no-cache-dir --no-deps --wheel-dir /wheels -r requirements.txt --timeout 60

Aaah, I see. But is it only through the Dockerfile-install that it fails or does it work outside docker?

Just tried running this line on my windows laptop:
pip3 wheel --no-cache-dir --no-deps --wheel-dir /wheels -r requirements.txt --timeout 60

Works fine. However, in my case most of the wheels were already.
Perhaps it is easier if I build a sapai-gym myself and use that one instead. Then you do not need to compiled your own wheels during installation. I'm testing this now here.

I have now built precompiled wheel for sapai-gym (see here).
All CIs seem to work (see here.
Hence, if you try cloning/pull latest commit, I believe it might work.

Within docker, we use 2 OS.

Ubuntu --> Installation is okay
Python3.8 images based on debian. --> Issue is seen here.
I might have to understand, the package difference between these base OS and python modules.

Just tried to setup super-ml-pets on a personal windows laptop and I ran into the same issue still. Preinstalling setuptools==66 resolves the issue.
Thus, precompiling wheel for sapai-gym is not sufficient. We will need to precompile wheel for gym. I could make an attempt.

I have now precompiled wheels for sapai-gym and gym, so maybe you will be more lucky this time around. Try to pull latest and try again.

pip3 wheel --no-cache-dir --no-deps --wheel-dir /wheels -r requirements.txt --timeout 60

I also tried running this command locally and it works fine. From the verbose it is also clear that it downloads the precompiled wheels (and does not build gym).

I always tried to install setuptool==66 and gym==0.21.0. With this error persists.
With latest gym version, issue doesnt occur.

What do you mean by latest gym version? Newer than 0.21? Those are not compatible with simple-basline3 (sb3).
I have precompiled the 0.21 wheel now and released it in my own fork. I believe that should work, as building during install is no longer required. Was it that you tried?

Yes, gym==0.26.2 installation works.
Off course, We also can't migrate to latest gym - 0.26.2.

What should be tried here? How to do this or any links to follow?
I believe that should work, as building during install is no longer required. Was it that you tried?

I have precompiled the 0.21 wheel now and released it in my own fork. I believe that should work, as building during install is no longer required. Was it that you tried?

^again. I should have fixed this in my own release of gym, which my own sapai-gym depends on (see here).
In order to properly get that fix, you will likely need to do --no-cache-dir to ensure that you get the updated wheel of sapai-gym, as I only updated the wheel itself and did not make a new release.
So please, try setting up the docker image again, if thats what you are trying to do.
If all this does not work, I will need a reproducible bash script demonstrating what you are trying to do, including the Dockerfile.

Great! What do you mean with "release your change"?
It is already part of super-ml-pets, as the the gym wheel above is part of the sapai-gym dependency here (which has been recently updated).
Does everything work now for you?

I misunderstood, the correction will be published to https://pypi.org/project/gym/#history.
Now, all issues are sorted out. Thanks for your support.


Incorrect constraints on HINT instructions

This is regarding the table in 2.9. HINT Instructions
Note that there is a similar table in section 7.4. HINT Instructions, which does not have these errors.
An excerpt from the current table for reference:

Instruction
Constraints
Code Points
Purpose

ADD
rd=x0,rs1=x0
2^10-32

ADD
rd=x0,rs1=x0,rs2=x2-x5
28

ADD
rd=x0,rs1=x0,rs2=x2-x5
4
(rs2=x2) NTL.P1 (rs2=x3) NTL.PALL (rs3=x4) NTL.S1  (rs2=x5)

FENCE
rd=rs1=x0,fm=0,pred!=W,succ!=0
15

The issues:

Row 1 should have rs1!=x0
Row 2 should have rs2!=x2-x5
Row 3 has one 'rs3' in the purpose column instead of rs2 (this made me chuckle)
Row 3 is missing the NTL.ALL text
Row 4 should have succ=0

@wmat these look like asciidoc transliteration errors; can you fix them?


Set same env variables as sensor process and s/_sensor_service/sensor_service

Fixes https://github.com/StackStorm/st2/issues/2694 and https://github.com/StackStorm/st2/issues/2693
Need feedback on https://github.com/StackStorm/st2docs/issues/156

Docs: https://github.com/StackStorm/st2docs/pull/157

Let's please get this addressed - https://github.com/StackStorm/st2/pull/2695#discussion_r63854788
Besides that, LGTM, :+1:

As mentioned in #2699 (yes, that PR I opened because I missed this one), it would also be good to add some (integration / end to end) tests which test datastore operations to st2tests or similar.
The unit tests which we have right now only test implementation details - they test correct environment variables are set. What we really are interested in and should be testing is "do datastore related methods" work. For that, we need end to end tests.

Minor comment wrt to PR title and description - imo, it's better if the PR title includes a more high-level description of what is being fixed / changed. This makes it easier for anyone checking the PR to understand what is going on and what is being changed.
Right now it includes implementation detail ("setting same environment variables"and  by itself this doesn't tell much). Imo, a better title would be something along the lines of "Fix datastore access in the Python runner actions" or something along those lines since that what we are doing - we are fixing datastore access for Python runner actions (and "setting same environment variables" is just an implementation detail of the fix which can be included in the description).

As per slack discussion, here is an integration test for datastore access in action - https://github.com/StackStorm/st2tests/pull/47

Thanks for moving the code and adding a test :+1:


Feat: add crypto exchange rate

There are commented tests because of the bug with Superface operations not returning fail error code.

Description

Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I haven't repeated the code. (DRY)
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

LGTM, could anyone else do a review?


Add custom validation rules where possible

An issue was reported where a user provided bucket name exceeded due to prefix/rand-string being appended. If we know the length of these, we should try to add custom validation rules where possible to prevent errors at apply time.
│ Error: googleapi: Error 400: Use of this bucket name is restricted: 'bkt-cdw-demo-data-ingestion-lanreo-bucket_simple_example-7b683ee9'
, invalid
│
│   with module.secured_data_warehouse.module.data_ingestion.module.data_ingestion_bucket.google_storage_bucket.bucket,
│   on .terraform/modules/secured_data_warehouse.data_ingestion.data_ingestion_bucket/modules/simple_bucket/[main.tf](http://main.tf/) line 17,
 in resource "google_storage_bucket" "bucket":
│   17: resource "google_storage_bucket" "bucket" {

In some cases it looks like we have two vars used in construction of the name which would not work with custom validation rules https://github.com/GoogleCloudPlatform/terraform-google-secured-data-warehouse/blob/987aaf34ae899edde82b7854530519ea9231e519/modules/data-ingestion/main.tf#L27

Thanks @bharathkkb ! I will take a look.