Add go.mod and go.sum

Thank you for introducing a great go-wasm example.
I faced a problem building the project in go1.12 environment, since the latest release of github.com/anthonynsimon/bild is as of year 2016 that does not include imgio.JPEGEncoder which is required for shimmer.
I had the go.mod file to use the latest commit of master (as of<PHONE_NUMBER>2716) so that shimmer can be built with the required function. And the specified commit can be replaced if newer version of github.com/anthonynsimon/bild is released.
Including go.sum and go.mod is recommended. https://github.com/golang/go/wiki/Modules#should-i-commit-my-gosum-file-as-well-as-my-gomod-file

Also, please change the commit message to be "[Added]: go.mod and go.sum". Thanks

@agnivade You're right. Thanks for pointing out. I'll fix it.

@agnivade Please check on commit ab196da.


[preview] move to elastic brand

Mass update preview changes for https://github.com/elastic/logstash/issues/2832

LGTM

fixed by https://github.com/logstash-plugins/logstash-output-statsd/commit/06e3941b184dc23311c131a316a4956f85c1dcc9


Pin OpenShift GitOps operator to version 1.9

This PR:

Pins the version of the OpenShift GitOps Operator to version 1.9.  This is being used in lieu of "latest", which does not align to the ZTP solution: https://docs.openshift.com/container-platform/4.14/scalability_and_performance/ztp_far_edge/ztp-preparing-the-hub-cluster.html

Expected that this will remain true for OpenShift 4.13 and 4.14.  This may be adjusted in the future with subsequent PRs as the ZTP solution tests new versions of GitOps (ArgoCD).

@novacain1 Should we update the ZTP plugin from 4.12?

believe the ztp-site-generate plugin is in the catalog repo.  going to merge this.

/cherry-pick cars2


Fix belt motor stopping when a ball is at the trigger sensor

When a ball is fed through the robot it makes its way through the system and once it hits the trigger sensor the belt motor and trigger motor both stop even though the belt motor should still continue.

Fixed after realizing the sensor wasn't plugged into the roborio


[Question] potential  vulnerability issues on csi driver

Hello,
I have used a security script that on my test aks cluster verifies NSA Hardening for k8s, we have the following issues:
[control: Allow privilege escalation] failed
Description: Attackers may gain access to a container and uplift its privilege to enable excessive capabilities.
Failed:
Namespace kube-csi
Deployment - aad-pod-identity-mic
DaemonSet - aad-pod-identity-nmi
Remediation: If your application does not need it, make sure the allowPrivilegeEscalation field of the securityContext is set to false.

[control: Allowed hostPath] failed
Description: Mounting host directory to the container can be abused to get access to sensitive data and gain persistence on the host machine.
Failed:
Namespace kube-csi
DaemonSet - aad-pod-identity-nmi
DaemonSet - csi-csi-secrets-store-provider-azure
Remediation: Refrain from using host path mount.

[control: Automatic mapping of service account] failed
Description: Potential attacker may gain access to a POD and steal its service account token. Therefore, it is recommended to disable automatic mapping of the service account tokens in service account configuration and enable it only for PODs that need to use them.
Failed:
Namespace kube-csi
ServiceAccount - aad-pod-identity-mic
ServiceAccount - aad-pod-identity-nmi
ServiceAccount - csi-secrets-store-provider-azure
ServiceAccount - secrets-store-csi-driver

Remediation: Disable automatic mounting of service account tokens to PODs either at the service account level or at the individual POD level, by specifying the automountServiceAccountToken: false. Note that POD level takes precedence.

[control: Immutable container filesystem] failed
Description: Mutable container filesystem can be abused to inject malicious code or data into containers. Use immutable (read-only) filesystem to limit potential attacks.
Failed:
Namespace kube-csi
Deployment - aad-pod-identity-mic
DaemonSet - secrets-store-csi-driver

Remediation: Set the filesystem of the container to read-only when possible (POD securityContext, readOnlyRootFilesystem: true). If containers application needs to write into the filesystem, it is recommended to mount secondary filesystems for specific directories where application require write access.

[control: Ingress and Egress blocked] failed
Description: Disable Ingress and Egress traffic on all pods wherever possible. It is recommended to define restrictive network policy on all new PODs, and then enable sources/destinations that this POD must communicate with.
Failed:
Namespace kube-csi
Deployment - aad-pod-identity-mic
DaemonSet - csi-csi-secrets-store-provider-azure
DaemonSet - secrets-store-csi-driver
Remediation: Define a network policy that restricts ingress and egress connections.

[control: Linux hardening] failed
Description: Containers may be given more privileges than they actually need. This can increase the potential impact of a container compromise.
Failed:
Namespace kube-csi
Deployment - aad-pod-identity-mic
DaemonSet - secrets-store-csi-driver
Remediation: You can use AppArmor, Seccomp, SELinux and Linux Capabilities mechanisms to restrict containers abilities to utilize unwanted privileges.

[control: Privileged container] failed
Description: Potential attackers may gain access to privileged containers and inherit access to the host resources. Therefore, it is not recommended to deploy privileged containers unless it is absolutely necessary. This control identifies all the privileged Pods.
Failed:
Namespace kube-csi
DaemonSet - secrets-store-csi-driver
Remediation: Remove privileged capabilities by setting the securityContext.privileged to false. If you must deploy a Pod as privileged, add other restriction to it, such as network policy, Seccomp etc and still remove all unnecessary capabilities. Use the exception mechanism to remove unnecessary notifocations.

[control: hostNetwork access] failed
Description: Potential attackers may gain access to a POD and inherit access to the entire host network. For example, in AWS case, they will have access to the entire VPC. This control identifies all the PODs with host network access enabled.
Failed:
Namespace kube-csi
DaemonSet - aad-pod-identity-nmi
DaemonSet - csi-csi-secrets-store-provider-azure
Remediation: Only connect PODs to host network when it is necessary. If not, set the hostNetwork field of the pod spec to false, or completely remove it (false is the default). Whitelist only those PODs that must have access to host network by design.

NSA FRAMEWORK

My question is if I were implemented it is it will effect Azure AKS management and may effect the cluster usage ?

Hello 👋🏻
By default we only set the required RBAC permissions and security context for the the driver and provider pods. Changing the default will cause the driver and provider to fail when trying to perform the volume mount operation.

So I cant apply those changes if I get you right because it will cause failure on the driver?

So I cant apply those changes if I get you right because it will cause failure on the driver?

That's right!

10x


400 error

I get a 400 error in this build https://app.circleci.com/pipelines/github/brainhubeu/issue-overseer/88/workflows/f3d168d6-981d-47ef-aea4-92505d68c386/jobs/187 though locally it works with the same token. No report is uploaded. However, the exit code is 0.

Based on more recent builds, this has been fixed for you.


WIP: work item children

fixes https://github.com/fabric8io/fabric8-planner/issues/980

Codecov Report

Merging #876 into master will decrease coverage by -0.66%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #876      +/-   ##
==========================================
- Coverage   70.53%   69.87%   -0.66%
==========================================
  Files          78       82       +4
  Lines        5470     5616     +146
==========================================
+ Hits         3858     3924      +66
- Misses       1255     1335      +80
  Partials      357      357

Impacted Files
Coverage Δ

work-item-children.go
0% <0%> (ø)

main.go
0% <0%> (ø)
:white_check_mark:

workitem/undoable_wi_repo.go
17.18% <0%> (-0.56%)
:x:

workitem/workitem_repository.go
65.96% <0%> (-6.06%)
:x:

comments.go
79.26% <0%> (-5.02%)
:x:

space.go
80.35% <0%> (-0.6%)
:x:

render.go
100% <0%> (ø)
:white_check_mark:

userspace.go
0% <0%> (ø)

rendering/markup_render.go
87.5% <0%> (ø)

... and 1 more

Continue to review full report at Codecov.

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

[test]

@kwk Do we know anything about how to identify the 'hierarchy' type based on the dynamic space template etc?

@aslakknutsen no we don't know that yet.

@kwk I changed code to use list-children in the design. Also moved code to workitems.go
I am not sure where Goa is adding that Workitem suffix.
Let me if any this looks good now. Thanks for the review!

[test]

[test]

[test]

@baijum Could you create a follow up Issue to redo the this to use some form of link type when we get there?

@baijum Could you create a follow up Issue to redo the this to use some form of link type when we get there?

Can you please give more details about this?

@baijum The space template defines the forward and reverse names and any link per say. Children can't really be based on that someone chose to call their link parent-of. We most likely need some form of link category or similar to state what this 'random link type defined by the space template' is suppose to represent


lammpsdatareader: Mass exceeds tolerance of match

With spce.data from here, I get the following error:
$ csg_dump --top spce.data
an error occurred:
Mass exceeds tolerance of match

(found in https://github.com/votca/csg-tutorials/pull/24)
The fun part is that spce.data only has one mass in it.

Ok

Well I found the problem I assumed for some reason that all files coming from lammps would be purely atomistic for some reason no course graining. Thus when using the mass to match with an atom type it was rightly throwing an error. I will change this so that it able to distinguish between an element and a course grained molecule based on the mass.


[Addition]: EDA IoT 3 hotspots in Pt Augusta South Australia

Hotspot b58 Addresses
1127sgwYppjMsmeTLHGAX9HqzgeqVhktc2qem16WHWX51ULthw9u
11HvZ4devRjWWFMU6PTnt3AcFh4yv45DwPB7hq2F6L5PzaimD1t
112dAbNDTiv3fQU3BVUb9pn3i6NkM6GXMheEc66mxDNQMMkfiCR2
Discord Handle
jaytheblader
Reason(s)
They only witness each other.
also verified by a mapping excursion to Pt Augusta and found nothing in that area exists, (checked with 3 working mappers.)

ya. these need to be added to the denylist as it's reaping massive amount of HNT. I just randomly pulled up a transaction by the related wallet. It's traced to other cheating cluster in China.

Transaction trace to various clusters

This issue can be closed as completed. ✅
Is a duplicate of https://github.com/helium/denylist/issues/7396 and all of the hotspots were added to PR https://github.com/helium/denylist/pull/7605


My Thai Star angular client updated to Angular CLI 1.6.0.

Lint refactoring: unused imports, variables, etc. removed.
Angular CLI updated to 1.6.0.
NGSW support included to build My Thai Star as PWA.
Some tests fixes.

We've tested this PR yesterday using Jenkins in our Production Line instance and results totally acceptable.


Fix tooltip position

Problem
When use this plugin on sub-window, tooltip will shown with wrong contents(too big image) on wrong position.

screenshot

Solution
import poi/views/components/etc/overlay instead direct @blueprintjs/core
(same as poi-plugin-ezexped/ui/fleet-picker/fleet-button)

screenshot

Note
TP value tooltip is not well tested (changes on a863467). Because transport operation is closed currently.

LGTM


 I'm not sure if I've done something wrong.

because /servers and /me isnt set up if u want to get it done code it urself

yes that's right, it hasn't been implemented, but you can try follow this https://github.com/charfweh/discord-bot-dashboard, its a forked and updated version of this very repository, hope it helps.


Update spec URL and document status in solid-oidc

In /index.bs and /primer/index.bs
Update spec URLs... eg /specification/solid-oidc to /solid-oidc
For Status of this Document, revise from https://github.com/solid/specification/blob/e14c6385533b975d83cc9250aedd242965cbdad9/protocol.html#L207 (Editor's Draft) or nearly identical: https://github.com/solid/specification/blob/cd8fbb1d8298e7064b444418e7c737f42fe4ef3e/wac.html#L278 (Draft).

Resolved via #14 and #15


Preceeding zeros are not handled properly

Expected behaviour
When a user enters preceding zeros, they should be removed
Actual behaviour
Preceding zeros are not removed and passed on to the downstream system
Steps to reproduce the behaviour -

Open an eQ survey
Enter preeceding zeros<PHONE_NUMBER>000000000000001) as test data in various fields.
Submit Survey
Verify the image file and other files generated for down stream system.

Technical information
Browser
IE11
Operating System
Windows 7
Screenshot

Output_DataFile.txt

Has this been verified to be fixed by #341 ? @weapdiv-david

No, we're still sending strings downstream at present.  Will need to verify with the SDX team that we can change the format to send integers, then update our downstream tests accordingly

Confirmed this is fixed by #368 on pre-prod. Closing.


Add notempty struct tag

Currently there is no easy way of knowing if a environment variable is set with an empty value except for checking the value yourself.
In certain workflows like for example when using docker-compose with variable substituion this can be a problem.
In this case a missing system variable is replaced by an empty string. The resulting container sees a set but empty variable. Therefore the required keyword does not result in an error and is useless.
notempty uses required and errors on a empty variable with message "empty value"

Sorry, I don't really understand the use case here. required looks at whether an envvar is set; it does not look at whether the value is the "zero" value.
To be honest, this feels like a bug in docker-compose. An unset environment variable and an environment variable set to the empty string are intentionally different constructs.

Ok maybe my use case too specific but it was just an example. The behavior of docker-compose is actually not a bug but probably not taking full adavatage of docker-compose features. Unfortunately I currently have no easy way of solving this.
Nontheless I still think checking for zero value in genaral is a valid use case. There could be multible different reasons why an variable is set empty by accident. A few I can think of right now are for example a misbehaving setup scripts or you forgotten value in a .env files, possibly even a misconfigured system.
While values which are converted into a different type might error straigt away string values will be empty. On fields you know that can not be empty like for example a database connection string you still have to check. This can be cumbersome for large structs and might negate the gains from using this lib in the first place.
Sure an empty value might be noticed immediatly because for example a connection failed, but the error might not be obvious or it does fail much later or not at all depending on what the value is used for.

All of the examples you described are upstream bugs (misbehaving setup scripts, forgotten values in .env, misconfigured system). I don't think it's the responsibility of a library to handle those misconfigurations.
This library isn't a replacement for configuration validation - you still need to do that. For example, you still need to make sure the value given for a database string actually looks like a database string.
If you really wanted this functionality, you could implement a custom type and decoder:
type AlwaysString string

func (a AlwaysString) EnvDecode(val string) error {
  if val == "" {
    return fmt.Errorf("...")
  }
  *a = val
  return nil
}

But I don't think this makes sense as a general-purpose functionality in the library.

Well ok but what is required then for? This also a kind of validation which you only need when you have a so called upstream bug. Why even error out when type conversion does not work. I mean its an upstream bug just make sure you provide the correct value. Why do you need default values? You could just check the value yourself.
What I'm getting at here is that I think checking for an empty environment variable is well whithin the scope of a library like this. (Btw similar libs support this feature). It's not like fully fletched regex-validatation or doing fancy log4j-style bloat.
You can even see how little had to be changed for this feature so it can't be out of scope that much.
I really like the style and simplicity (like prefixes and you only use one struct tag) of this library and would hate to not use it.
And to be honest writing notempty is why cleaner than having to check multiple values within your main (or where ever you want to check). I just gave some quick examples but there are many cases where empty values aren't that easy to spot.

required is for when a value must be specified in the environment. There's a fundamental difference between:
FOO=

and
unset FOO

In the first, FOO is set. It's set to an empty value, but it's set. Thus, it would pass a required validation. In the second, FOO is unset. That variable is undefined. Thus, it would fail a required validation.

What I'm getting at here is that I think checking for an empty environment variable is well whithin scope of a library like this. (Btw similar libs support this feature).

I disagree. Feel free to use those other libs.

I really like the style and simplicity (like prefixes and you only use one struct tag) of this library and would hate to not use it.

This library is small and simple because I reject changes like these.

Even Bash (and most programs I know of) treats empty and unset variables mostly the same. There is not that much difference. It's by far not out of scope.

Even Bash [...] treats empty and unset variables mostly the same.

This is factually incorrect 1, 2, 3.

Yes of course thats why I said mostly. I have yet to actually differenciate between empty and unset in bash. In your provided links even the easies way of checking for unset is checking if the variable is zero length aka empty

As I probably cannot convince you otherwise I would like to know why you think validating if a variable is set with required is in scope of this libray or if you think required was a mistake.


SET GRID and string variable

Reported by Ansley B Manke on 7 Oct 2002 16:04 UTC
yes? use coads_climatology
yes? set grid sst
yes? let a =  "hello"
yes? list a
!Segmentation fault
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/463

Comment by<EMAIL_ADDRESS>on 16 Oct 2002 19:41 UTC
Bug fixed 10/16/02:
turns out that in complete_missing_limits.F, when the axis number for the
abstract axis was being checked, it was only doing so for the x_axis.  moved
check inside the dimension loop to check for the abstract axis in each
dimension.


Remove cuda-cupti and cuda-nvcc run dependencies for pixi

This PR removes the aforementioned dependencies from the pixi section of pyproject.toml. Given that https://github.com/conda-forge/jaxlib-feedstock/pull/241 has been merged, they are not needed anymore

📚 Documentation preview 📚: https://jaxsim--138.org.readthedocs.build//138/

Let's proceed without updating the pixi.lock file. We currently have two of them, but ideally I'd like to maintain only one.

I can open a separate PR for that

This was removing cuda-cupti too soon, see https://github.com/conda-forge/jaxlib-feedstock/pull/241#issuecomment-2102674767 and https://github.com/conda-forge/cuda-cupti-feedstock/issues/14 .


feat: jwt handlers to decode and encode formData for auth0 action

WIP - As it requires tests and some typescript finessing
Who is this for?
Anyone who wants to ensure that formData (or any data) can be sent to an auth0 action securely.
This forms part of https://github.com/wellcomecollection/wellcomecollection.org/issues/7896
What is it doing for them?
It provides verify and generate jwt utils to decode incoming token from an auth0 action and add form data and securely send back to an auth0 action.
But why would we send back to an action? We will need to send back the registration form name, surname and acceptance of terms and conditions data to an action so we can call sierra in that action and create/update a patron record as part of the patron self registration.
note: the auth0 action script is in progress on Identity API
These handlers should be used in account/registration within the updateUser function (  <form onSubmit={handleSubmit(updateUser)} noValidate>)

@davidpmccormick has helpful folded these handlers into his work on ithub.com/wellcomecollection/wellcomecollection.org/pull/7905 so I'm going to close this one.


No MacOs version

I was trying to install it on a mac, but no Mac Os version ?

We are working on this issue.

Mac OS Version released.


tf.image.crop_and_resize

Anyone know how the
tf.image.crop_and_resize(images, boxes, batch_inds,
[pooled_height, pooled_width],
method='bilinear',
name='Crop')
work? i cannot find the " tf.image.crop_and_resize" in  tensorflow/python/ops/gen_image_ops.py.
Thank you

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

N/A

It is written in C++ ... see e.g.
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/ops/image_ops.cc

Can i have the "Exact command to reproduce" too?
Tensorflow is new to me. I am trying to understand what happen in the function tf.image.crop_and_resize(images, boxes, batch_inds,
[pooled_height, pooled_width],
method='bilinear',
name='Crop')"  .
If use
return tf.image.crop_and_resize(images, boxes, batch_inds,
[pooled_height, pooled_width],
method='bilinear',
name='Crop')"  .
How the input of this function is used in the function and what it with return?

have the C++ code explains how the tf.image.crop_and_resize work?
I am not sure the .Input() in given link can explain the function.


[com.google.fonts/check/smart_dropout] FAILs when all checks run, PASSes when only this check runs

Check fails on this font in the CI and when I run Fontbakery locally, but passes when I run just that one check using -c smart_dropout.
I investigated the font and the code think it should pass in any case, so I'm very much at a loss of ideas what could cause this behaviour. It seems to be some sort of interference with other checks running.

Confirmed, I'm taking a look.


[HoloToolkit] Objects moves with head movement

Overview
When attach a HandDraggable or TwoHandsManipulatable script to an object it moves with the headset position not only with controllers.
Expected Behavior
Objects can be manipulated with the controllers as expected.
Actual Behavior
Objects moves/rotate when you move the head too.
Steps to reproduce

Create a gameObject with a box collider
Add HandDraggable or TwoHandsManipulatable script
Run the scene, pull and hold the trigger while pointing to the object and move the headset

Unity Editor Version
2017.4.20f2
Mixed Reality Toolkit Release Version
HoloToolkit-Unity-2<IP_ADDRESS>-Refresh

Please re-open if issue repros with MRTK v2 as we are no longer actively updating HTK.
Thanks!
Yoyo


Enhancement: Create wrapper for DuckDB to read remote parquet files

Using the DuckDB crate for Rust, create a wrapper that can read parquet files stored in an S3 bucket.

we already have S3 FDW can read parquet file on S3, is this you're looking for?


[Windows] Set the uplink port with "no-flood"

Set the uplink port with configuration "no-flood", so that the ARP "normal"
flow will not forward the packets to the uplink interface.
"no-flood" config is supported only in OpenFlow10, so using the ovs command
to set it.
Fixes #865

/test-all

/test-all

/test-windows-conformance
/test-windows-networkpolicy

/test-all

/test-e2e
/test-windows-conformance
/test-windows-networkpolicy

/test-windows-conformance

/test-windows-conformance

/test-windows-conformance


Implement Queen Attack

There is no common set of tests for this exercise, so implementation is
a bit....free form. I think there are two interesting things to look at,
what tests to use, and how to use them.
Which Tests
I first surveyed all of the languages that implement this exercise and
looked at what they tested. In order of prevalence, the five most common
test types cover:

Can 2 queens attack each other?
Can 2 pieces occupy the same
space?
Comparing string representations of the
chessboard
Does a chessboard start with the queens in their default
positions?
Errors are raised if an invalid position is
used

Then there are some uncommon edge-case tests. Can there be more than one
chessboard? Can the board be empty? Algebraic chess notation? Etc.
Of the top five, I found that only numbers 1 and 5 really cover the
exercise as stated -- if I place two pieces on the board, can they attack
each other?
So, those are the tests that I've implemented here.
Implementing the other tests requires the introduction of a Chessboard
object. And also a way to identify pieces (which team they belong to,
how they are represented as strings, etc.)  That can be interesting to
do, but I find it beyond the scope of this exercise as written.
At best, I think these tests should be suggested as Extra Credit.
What Order
I was very particular in my test order. Some languages, for example,
start with the board representation tests. This requires students to
write a lot of code in order to get just one test to pass.
I have found that the faster I can get the first test to pass, the
better. So my first test requires nothing more than a can_attack
function that returns false. The tests then build on that, adding
complexity. Then, once can_attack is fully implemented, I add the
curveball test of invalid chess positions, which will get students
thinking about bad inputs and Rust's error handling.

If you're interested in the tests implemented by other languages, I've summarized it here: https://gist.github.com/IanWhitney/dd34f8a16c730f3cd77c

@petertseng, it sounds like some of the survey I did for this problem overlaps well with your recent work (as outlined in today's newsletter). So if I can contribute to a canonical version of the Queen Attack tests, let me know. Happy to help.

Many thanks for conducting the survey @IanWhitney !!
Since I will be traveling, remind me if I haven't gotten back to this PR in 72 hours from now. Of course anyone else is free to beat me to the punch on this!
In the meantime, my remarks on the cross-track consistency work:
A great first step will be to open a PR in https://github.com/exercism/x-common adding queen-attack.json with what you think are the tests that are in fact relevant to the exercise, as you described in your commit message/PR description. It will be good if your PR references https://github.com/exercism/todo/issues/133. In that PR will probably discuss with @kytrinyx and any interested track maintainers to get agreement on the set of tests.
After that is merged, then the next thing is to get tracks in line with it, adding or removing tests.
We have a tool https://github.com/exercism/blazon for filing issues across all tracks with a given problem, we can help draft an issue text if you like.
Of course you are free to file PRs actually making the changes for some (or even all?!) tracks if you desire, but it's totally fine to load-balance across multiple contributors.
All of the above are absolutely open for you to take charge of currently, since I should probably only focus on one problem at a time and my current efforts are focused on a different problem. So it's yours if you want it!

FYI @petertseng I merged the PR in x-common: https://github.com/exercism/x-common/issues/211

Yeah, I guess either can_attack or Queen::new has to deal with the possibility of an invalid queen.
What would you say to having that be in Queen::new instead? So Queen::new could return a Option<Queen> or maybe a Result<Queen, Something> (I think a error type of () isn't all that useful and one might as well use Option in that case, but if there is some sensible errror type we coud consider it).
I realize that yes, you'd still have to unwrap() the result of that Queen::new in the tests, so it's not like it's saving us any unwrapping. But it seems useful to me to raise errors as close to the site of the error as possible.
Another reason for that would be that then it's obvious what queen caused the problem. If I have queenA.can_attack(queenB) which is an Error, how do I know what queen caused the problem? I could have a known-good Queen to call against both queens and see which one errors, but that seems cumbersome. Seems easier for clients of the code if we can know at construction time that we will either get a valid Queen, or an error right then.
(By the way the commit message of 2a74be0b50f803e0e7ac4514c44e7d1f16a0eb0f implies that Queen::new is returning the Result like I suggest, but in fact it is can_attack that has the Result)
This is just what I think but I could be convinced otherwise, totally open to hearing what @IanWhitney or @EduardoBautista (or anyone else!) have to say about that.

Doing it on Queen::new does seem more in line with the common test suite
But if I do it that way, then every test would have lines like:
  let white_queen = Queen::new((2,4)).unwrap();

Is there a way in Rust to have students avoid using a Result value until they reach the test that introduces error handling? Because that's what I think would be best in terms of learning curve. I'd love students' initial implementations to be simple,
pub fn new(position: (i8,i8)) -> Queen {
  Queen {position: position}
}

Because the simple implementation gets tests passing faster, which I always think is a good thing.
And then when the student hits the error handling test they have to figure out how to modify their simple implementation to handle this extra complexity.

Oh, and my example is returning an empty-tuple error because I didn't see a good reason for it to return anything more complex. Students could return any error type they like. It just has to properly handle is_err().

But if I do it that way, then every test would have lines like:

let white_queen = Queen::new((2,4)).unwrap();

Hmm, is that better or worse than there being lines of the form:
assert!(white_queen.can_attack(black_queen).unwrap());

One of the two has to have that unwrap if we are to have error handling at all.

Is there a way in Rust to have students avoid using a Result value until they reach the test that introduces error handling? Because that's what I think would be best in terms of learning curve. I'd love students' initial implementations to be simple,

This is a good thought.
We'd have to figure out how to get this accepted by the type checker if Queen::new should start out returning just a Queen but later should change to returning a Result<Queen, _>. It seems to imply that the earlier tests expecting a Queen would have to be deleted. Or at least not compiled, using some sort of conditional compilation thing? You could explore the conditional compilation route if you think it will be better. If it works out we may like to think about how other problems in this track can make use of it (separately from this PR of course).
Alternatively, is there a way that the test could provide the implementation of some_queen.unwrap() (which would presumably just be the identity function)? That way Queen::new((2,4)).unwrap() will work both when Queen::new is expected to return a Queen and when it's expected to return a Result<Queen, _>
If it turns out the above suggestions are working too hard against the type system, maybe it's a sign that in Rust, the type system means you have to check errors earlier than you might have to in other languages. Although I realize that statement is more about when you would check errors when you're using a library that provides a fixed interface. The question we're dealing with here is "when should we add error handling when iteratively developing, and when we add error handling, how are our tests affected?"

Oh, and my example is returning an empty-tuple error because I didn't see a good reason for it to return anything more complex. Students could return any error type they like.

Ah I see! I missed the fact that it just needs to be an error of some kind instead of being forced to be ().  Great!

Thinking about it more, I may be trying to implement Null Object Pattern in Rust. And you're right, that may be an idea that is incompatible with how Rust wants me to work. The pattern exists for OO languages which can return nulls, and Rust can't do that.
Maybe the best approach is to have Queen::new return a Result. And then I'll re-order the tests a bit to make initial progress easier.

Ok. I think we're pretty good. Or at least I hope so, since I won't have nearly as much free time to hack on this stuff after today.

I think this is pretty good as well! Given that Queen::new is returning the Result now rather than can_attack I think it definitely made sense to reorder the tests in the fashion given.
If it turns out that students are not figuring out that the return value should be of a Result type we can point it out to them via a comment in the test file or something. May want to periodically examine submissions to queen-attack to see whether anyone has such trouble.
Given I'm happy with this and nobody else had objections over the weekend let's get this merged. Thanks again for the work.


Compatibility for rails 3.2

Rails to serialize model names to symbols instead of strings. Fixed in more recent versions of Rails.

@beatjoerg I'm terribly sorry, I can see from git blame that I've already added the to_s conversion as part of 64111a2b... Thanks for the patch and sorry for my oversight when doing that commit.


Push Notifications

Hi,
I love the app, but I was wondering if you could add push notifications?

Hello,
I managed to add push notifications, I’ll get a blog post up tomorrow for it

Hi
Any news about push notification?

Has anyone figured out how to add push notifications using firebase functions?


Fix two window function bugs

@yhuai @guowei2 This PR fix two issues
1 HiveQl line number 796, it should be withDistinct, otherwise leads to test failure
2 Fix the case of sql in my added unit tests:
select area, sum(product), sum(sum(product)) over (partition by area) from windowData group by month, area

This sql want to aggregate product for (month, area) and (area)
select area, sum(product), sum(product) / sum(sum(product)) over (partition by area) from windowData group by month, area

this sql want to aggregate product for (month, area) and want to know the ratio over the product of all area.

I have merged it.

@yhuai , i have not fixed all the issues, this PR has test failure

What test failures? Tests you added and we already have or tests you have not added? There is no failure in the current pr. If you have any case that has not been added in your mind, please comment on the pr. Thanks!

btw, after I merged your pr, I made some changes on the analysis part.

YES, i have noticed that you have fixed it. it is in analyzer changes leads to window.q failure


Implementing .STRUCT / .ENDSTRUCT

Hello Jeroen,
I try to use mos_api.inc from agon-mos however it failed to process.  Some errors are minor issues, however I realized ez80asm do not understand structures.
Are you planning to add this construct?

Hi Radek,
The mos_api.inc is has been written by Dean for use in the ZDS assembler, which has a somewhat different syntax.
I'm not currently planning to include structures in ez80asm


Ratify(latest:v1.0.0-rc.5) installed with helm even with --set cosignEnabled=true fails to load cosign plugin

What happened in your environment?
Ratify installed helm using helm install ratify ratify/ratify --atomic
--namespace gatekeeper-system
--set cosign.enabled=true   --set-file cosign.key=cosign.pub --set-file dockerConfig=docker.json
Installed fine
helm install ratify ratify/ratify --atomic \
    --namespace gatekeeper-system \
 --set cosign.enabled=true   --set-file cosign.key=cosign.pub --set-file dockerConfig=docker.json
NAME: ratify
LAST DEPLOYED: Tue Jul  4 15:40:25 2023
NAMESPACE: gatekeeper-system
STATUS: deployed
REVISION: 1

When trying to deploy a pod and Gatekeeper trying to do admission control using Ratify external data provider the Ratify fails validation failing to load cosign plugin
time="2023-07-04T05:41:36Z" level=info msg="Resolve of the image completed successfully the digest is sha256:d2b2f2980e9ccc570e5726b56b54580f23a018b7b7314c9eaff7e5e479c78657"
{
  "isSuccess": false,
  "verifierReports": [
    {
      "isSuccess": false,
      "name": "cosign",
      "message": "an error thrown by the verifier: failed to find plugin \"cosign\" in paths [/.ratify/plugins]",
      "artifactType": "application/vnd.dev.cosign.artifact.sig.v1+json"
    }
  ]
}

The logs of Ratify does say that it loaded the verifier though
time="2023-07-04T05:30:24Z" level=info msg="Address was empty, setting to default path: /.ratify/plugins"
time="2023-07-04T05:30:24Z" level=info msg="verifier 'cosign' added to verifier map"

What did you expect to happen?
The Ratify should load the plugin fine and verify the signature of the container image tried to be deployed
What version of Kubernetes are you running?
1.25.6
What version of Ratify are you running?
v1.0.0-rc.5
Anything else you would like to add?
No response
Are you willing to submit PRs to contribute to this bug fix?

[X] Yes, I am willing to implement it.

We updated the build step to optionally build the plugin, see PR 860.
The immdiate fix , we need to update our publish workflow to build ratify image with the plugin.  We also need to think about if we need to provide a flag in helm chart for user to specify which image in install.

thanks for reporting this issue, this also reveals a gap in our test coverage. Please see PR fix: publish ratify image with plugin by susanshi · Pull Request #916 · deislabs/ratify (github.com) for the fix.  As a workaround, if you build a local image with the flags enabled, you should be unblocked.

This has been resolved RC6 release, please let us know if you are unblocked. thanks!

@suganyas Could you verify whether this issue is fixed in RC6 release? Thanks.

closing for now as previous release fixed this. Please open again if you still see issues.


send OI param for historical data API

PHP SDK is dead and no one is maintaining it anymore

PHP SDK is dead and no one is maintaining it anymore

@ranjanrak can you take a look at this?

@ranjanrak can you take a look at this?

@vividvilla  Ahh, didn't receive any alert for this tag. Saw this now. Have fixed this issue(missing oi field in historical data response) and raised an PR here. Please review this.

@VarunAgw
This is already fixed through this PR.


Error when running tests

Run tests
Ensure a test fails
Fix failed test
Run tests

Following message is displayed

Maybe this is related. My unittests also stopped working.
System:
Version: 1.31.1 (system setup)
Commit: 1b8e8302e405050205e69b59abb3559592bb9e60
Date: 2019-02-12T02:20:54.427Z
Electron: 3.1.2
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763
Discovery of unit tests finds no tests. When Ctrl+Shift+P -> Python: Run All Unit Tests, I see in the Python Test Log's output:
  File "c:\Users\micro\code\somefile.py", line 1, in <module>
    import pandas as pd
  File "C:\Users\micro\Anaconda3\envs\py36\lib\site-packages\pandas\__init__.py", line 19, in <module>
    "Missing required dependencies {0}".format(missing_dependencies))
ImportError: Missing required dependencies ['numpy']

So in a module I'm importing into the unit test that imports pandas, pandas is unable to find numpy. I can import pandas in a Terminal inside VS Code without error.
I have a conda environment based on python 3.6.8, tried removing and reinstalling numpy and pandas, but to no avail.

Closing as stale.

Closing as stale.


tokenColorCustomizations strange mixing behavior

tokenColorCustomizations has a strange behavior with colors "mixing" each others, see screen capture bellow:

What is interfering and how can I prevent it?
My settings

Take a look at warnings.

Ok I managed to find the right synthax, but it was hard (the warnings weren't very precise):
"textMateRules": [
        {"scope": "entity.name.tag", "settings": {"foreground": "#8cc3ff"}},
        {"scope": "entity.other.attribute-name", "settings": {"foreground": "#ffc68c"}},
        {"scope": "punctuation.definition.tag", "settings": {"foreground": "#8cc3ff"}},
      ]

Thanks again for your help!


Added Robossembler project grant proposal

Hi, Robossembler team!
Thank you for participating in our grant program, your project is really cool!
About your proposal: we have updated the repository and template to the final version, and I would like to ask you to modify the proposal and bring it to the current template. There are partially changed the fields you already have + added a section about the schedule and budget. You don't need to describe everything strictly, just figure out your plans and write them there. Of the budget is similar. Also, could you please remove all comments that start with the ‘>’ from the document?
I know that you get the grant before we prepared this repository, but still, I would like to have your finalized example for future projects.
Many thanks.


docs: fix references loading with key name

The docs are wrong.

Well, yes, the docs were dated, but your change is not really fixing them (read the whole sentence now, load is calling load?)

Perfect, thanks!


Orphaned ItemView tab on reload

I am developing a plugin that creates an ItemView in the sidebar.  When I use hot-reload to disable/enable my plugin it always leaves an orphaned ItemView tab behind and creates a 2nd new one instead.  If I manually disable and re-enable the plugin in the settings this does not happen.
Any ideas what could be causing this and how I might trouble-shoot this?

If you have a link to the source I can take a look, but I don't know of anything that would do this off the top of my head.  Are you using the ensureSideLeaf() API?

Hm.  You have some code to remove the old leaf, but that shouldn't be necessary; recent versions of Obsidian put up a temporary view proxy that it'll refresh with the real view once 1) the plugin is loaded, and 2) the leaf is revealed.
However, it's possible that there's been a change in how that gets done, in such a way that Hot Reload isn't triggering the mechanism any more.  (Though that seems unlikely.)  What version of Obsidian are you on, precisely?
The only other thing I can think of is that using an async onload method can result in some weirdness if you save a change at the same time a previous hot reload is occurring, but it's unlikely you'd trigger such a thing consistently, I don't think.

I agree it should not be necessary, but right now this is just a workaround!
I was also wondering if it has anything to do with the new 'Deferred Views' feature.  I am on the latest version (1.7.7 update and installer).
It is consistent. If I manually disable / enable the plugin after a code change it refreshes fine.  If I use hot-reload I always get a 2nd orphaned View tab.

I made the following changes and now it works correctly... Not really sure I can explain why 🤔
    async reload(plugin) {
        const plugins = this.app.plugins;  // <-- added this. as using app is deprecated.

        // Don't reload disabled plugins
        if (!plugins.enabledPlugins.has(plugin)) return;

        await plugins.disablePluginAndSave(plugin);  // <-- changed to the ...AndSave() version
        console.debug("disabled", plugin);


upstream cereal improvements

TODO: Provide cereal author with a minimal project to reproduce per archive registration limitations.  The current registration mechanism is applied to all visible archive types (any type #included at the stop the registration is attempted).

This change won't be added, as discussed in this thread: https://github.com/USCiLab/cereal/issues/406


access events in function

Hello, I know this is a bit noob question but please do answer...
based on your documentation,
<AppStateListener         onActive={handleActive}         onBackground={handleBackground}         onInactive={handleInactive}       />
I'd like to access those 2 events (onActive, onBackground) from any function like componentWillMount or any custom function.

Closing.  If there are still questions here, please open a new issue with additional details.


Fix typo + fix tests + update dev dependencies.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
-

👍

👍


Added useDepthPicking flag from 3d-tiles

Cherry-picked 312fecca4f67805dd482b6370733d5a6d102561c and 66a9da108f8b48a64f0f538eeac7bbb8fc1ba198 into master, allowing you to set a useDepthPicking flag in Scene.

Update CHANGES.md.
Remind me what the use case - pick mouse over picking for point clouds was slow?

Yes it seems like that was the reason.

OK, update CHANGES.md and we'll merge.

Updated.


Correctly Calculate Icon & Label in PieSlice

The way I currently calculate the correct position for the icon and its label is horrible and needs to be fixed.

I think I got this to work now. :)

Fixed by #23


Obj-C Cannot create an instance of calendar

Hi I'm Yiğit.
I'm trying to open a WWCalenderTimeSelector in obj-c project. Like this :
`+ (void) createCalendar:(ExtViewController<WWCalendarTimeSelectorProtocol>*) delegate{
    static WWCalendarTimeSelector *obj = nil;
    if(obj == nil){
        obj = [WWCalendarTimeSelector instantiate];
    }
    obj.delegate = delegate;
    obj.optionLayoutWidthRatio = 0.5;
    [obj.optionStyles showTime:NO];
    obj.optionButtonTitleDone = @"OK";
    obj.optionStyleBlurEffect = UIBlurEffectStyleExtraLight;

    [[SlideNavigationController sharedInstance] presentViewController:obj animated:NO completion:nil];
}`

But when i call this method,your'open static func instantiate() -> WWCalendarTimeSelector' method throws an exception in this('return UIStoryboard(name: "WWCalendarTimeSelector", bundle: bundle).instantiateInitialViewController() as! WWCalendarTimeSelector' ) line.
Error output :

2016-10-05 18:33:34.546 prj[657:533235] Unknown class _TtC38WWCalendarTimeSelectorStoryboardBundle22WWCalendarTimeSelector in Interface Builder file.
Could not cast value of type 'UIViewController' (0x3bb4f40c) to 'WWCalendarTimeSelector.WWCalendarTimeSelector' (0xa4c93c).

Any solution ? :/
Best regards..

I just move WWCalendarTimeSelector.storyboard from Resources group to main folder . It fixed my problem.


Rename, and other things like that

Maybe possibility to rename without refresh the page?

A page refresh is a pretty simple way to rename your nickname, otherwise it would cause identity confusion. An announcement like "relogging as feliwyn2" before a refresh would probably be sufficient in a conversation.

Yeah, but the history?

@feliwyn there's no history in Hack.Chat nothing you say is saved on a server !!


Upgrade soci-snapshotter to v0.4.0

Upgrading to v0.4.0 required wrapping the local oci.Store used to store SOCI artifacts in a store.SociStore type exposed by SOCI because soci.WriteSociIndex expects a store.Store type. For some context, store.Store is an interface that extends oci.Store to allow for garbage collection of SOCI artifacts.
Related Issue
Please reference the issue that this pull request addresses. This can be a new issue or an existing one.
Proposed Changes
Please describe the changes proposed in this pull request. This could include bug fixes, feature enhancements, code refactoring, documentation updates, or any other modifications to the codebase.
Reviewers
Please tag the person or team responsible for reviewing this pull request, using the @ symbol followed by their username.

/do-e2e-tests


v9 Migration Doc

This change is

Review status: 0 of 1 files reviewed at latest revision, 4 unresolved discussions, some commit checks broke.

docs/basics/upgrading-react-on-rails.md, line 9 at r1 (raw file):

* If you have `react_component` returning hashes, then switch to `react_component_hash` instead

## Upgrading to version 9

from v8?

docs/basics/upgrading-react-on-rails.md, line 20 at r1 (raw file):
I don't follow this one.
webpacker just makes it so you don't have to do your own webpack configuration

This enables your webpack bundles to bypass the Rails asset pipeline and it's extra minification

that's moving beyond v7 of RoR

docs/basics/upgrading-react-on-rails.md, line 23 at r1 (raw file):

#### From version 8
See [our changelog for instructions](https://github.com/shakacode/react_on_rails/blob/master/CHANGELOG.md#90-from-8x-upgrade-instructions)

let's include this here

docs/basics/upgrading-react-on-rails.md, line 32 at r1 (raw file):

*   `Gemfile`: bump `react_on_rails` and add `webpacker`
*   layout views: anything bundled by webpack will need to be requested by a `javascript_pack_tag` or `stylesheet_pack_tag`
*   `config/initializers/assets.rb`: Delete it. You don't need it anymore.

maybe revert back to default for assets.rb? I'm not sure about deleting it.

Comments from Reviewable

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, 4 unresolved discussions, some commit checks broke.

Comments from Reviewable

Review status: all files reviewed at latest revision, 4 unresolved discussions, some commit checks broke.

docs/basics/upgrading-react-on-rails.md, line 20 at r1 (raw file):
Webpacker does make it so that you don't have to do your own webpack configuration, but clients with legacy projects are likely to want to maintain control of their webpack configuration. Therefore, the only other reason a client would want to integrate webpacker is to bypass the double minification.

that's moving beyond v7 of RoR
Anything involving webpacker is moving beyond RoR v7. What's your point?

docs/basics/upgrading-react-on-rails.md, line 23 at r1 (raw file):
Previously, justin808 (Justin Gordon) wrote…
let's include this here

Will do.

docs/basics/upgrading-react-on-rails.md, line 32 at r1 (raw file):
Previously, justin808 (Justin Gordon) wrote…
maybe revert back to default for assets.rb? I'm not sure about deleting it.

Well, if we're going to tell people to revert it, then we'll have to identify exactly what changes RoR made to it. Shall we assume the client installed RoR v7?

Comments from Reviewable

Review status: 0 of 3 files reviewed at latest revision, 7 unresolved discussions.

docs/basics/upgrading-react-on-rails.md, line 20 at r1 (raw file):
Previously, Judahmeek (Judah Meek) wrote…
Webpacker does make it so that you don't have to do your own webpack configuration, but clients with legacy projects are likely to want to maintain control of their webpack configuration. Therefore, the only other reason a client would want to integrate webpacker is to bypass the double minification.

that's moving beyond v7 of RoR
Anything involving webpacker is moving beyond RoR v7. What's your point?

This makes no sense at all to me.
Webpacker provides 2 things:

View helpers that support bypassing the asset pipeline to enable things like avoiding double minification and proper source maps. This is 100% a best practice.
A default Webpack config so that you only need to do minimal modifications and customizations. However, if you're doing server rendering, you may not want to give up control. Since Webpacker's default webpack config is changing often, we can give you definitive advice on this one. In general, if you're happy with doing your own Webpack configuration, then stick to that. Most bigger projects will prefer having more control.

docs/basics/upgrading-react-on-rails.md, line 11 at r2 (raw file):

## Upgrading to version 9

### With no interest of integrating webpacker

Need a few sentences of pros and cons of either way.

docs/basics/upgrading-react-on-rails.md, line 16 at r2 (raw file):

In /config/initializers/react_on_rails.rb, rename:

config.npm_build_test_command ==> config.build_test_command
config.npm_build_production_command ==> config.build_production_command

Also create config.node_modules_location and set it to "client"

* In `/config/initializers/react_on_rails.rb`:
    *  Rename `config.npm_build_test_command` ==> `config.build_test_command`
    *  Rename `config.npm_build_production_command` ==> `config.build_production_command`
    *  Add `config.node_modules_location = "client"`

docs/basics/upgrading-react-on-rails.md, line 23 at r2 (raw file):

Reason for doing this: This enables your webpack bundles to bypass the Rails asset pipeline and it's extra minification, enabling you to use source-maps in production, while still maintaining total control over everything in the client directory

#### From version 8

Most people are upgrading from 7 or earlier to 9 or later, so this is a bit confusing.

Comments from Reviewable

Reviewed 3 of 3 files at r2.
Review status: all files reviewed at latest revision, 7 unresolved discussions.

Comments from Reviewable

suggestions provided

Review status: all files reviewed at latest revision, 6 unresolved discussions.

docs/basics/upgrading-react-on-rails.md, line 32 at r1 (raw file):
Previously, Judahmeek (Judah Meek) wrote…
Well, if we're going to tell people to revert it, then we'll have to identify exactly what changes RoR made to it. Shall we assume the client installed RoR v7?

No idea on this one.

Comments from Reviewable

Review status: all files reviewed at latest revision, 6 unresolved discussions.

docs/basics/upgrading-react-on-rails.md, line 20 at r1 (raw file):
Previously, justin808 (Justin Gordon) wrote…
This makes no sense at all to me.
Webpacker provides 2 things:

View helpers that support bypassing the asset pipeline to enable things like avoiding double minification and proper source maps. This is 100% a best practice.
A default Webpack config so that you only need to do minimal modifications and customizations. However, if you're doing server rendering, you may not want to give up control. Since Webpacker's default webpack config is changing often, we can give you definitive advice on this one. In general, if you're happy with doing your own Webpack configuration, then stick to that. Most bigger projects will prefer having more control.

Stolen

docs/basics/upgrading-react-on-rails.md, line 11 at r2 (raw file):
Previously, justin808 (Justin Gordon) wrote…
Need a few sentences of pros and cons of either way.

Used your own comments with minor modifications

docs/basics/upgrading-react-on-rails.md, line 16 at r2 (raw file):
Previously, justin808 (Justin Gordon) wrote…

In /config/initializers/react_on_rails.rb, rename:

config.npm_build_test_command ==> config.build_test_command
config.npm_build_production_command ==> config.build_production_command

Also create config.node_modules_location and set it to "client"

* In `/config/initializers/react_on_rails.rb`:
    *  Rename `config.npm_build_test_command` ==> `config.build_test_command`
    *  Rename `config.npm_build_production_command` ==> `config.build_production_command`
    *  Add `config.node_modules_location = "client"`

Done

docs/basics/upgrading-react-on-rails.md, line 23 at r2 (raw file):
Previously, justin808 (Justin Gordon) wrote…
Most people are upgrading from 7 or earlier to 9 or later, so this is a bit confusing.

I moved this section to the end

Comments from Reviewable

@judahmeek Any final questions for me? Ready to merge?

Reviewed 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 6 unresolved discussions.

Comments from Reviewable

@justin808 Yes, ready to merge.


Allow colors to be assigned (by color name) on the command line

The built-in color assignment mechanism breaks down after the first 15 logs, and may make some choices that a human would consider to be poor. The tool should define at least a dozen colors and allow the user to specify them on the command line.
The tool should also allow the user to select a specific color (from the 255 standard ANSI colors) even if that color has no defined name.

The built-in color assignment mechanism breaks down after the first 15 logs,

Imo, A color assignment mechanism is not feasible to use with > 10 logs, since it becomes hard to keep track. So, this problem can be discarded

and may make some choices that a human would consider to be poor. The tool should
define at least a dozen colors and allow the user to specify them on the command line.

Imo, allowing users to choose colors is not required; letting users choose colors would just make the tool fancy. Instead we could use a better set of colors by removing the 'poor' choices.


use our" is_dag" flag for JOBSUBJOBSUBSECTION choice

I think this resolves the issue VIto has been seeing with --maxConcurrent vs JOBSUBJOBSUBSECTION.

Submitted some test jobs using this code
bin/jobsub_submit -G icarus --memory 200MB --disk 500MB -N 5 --maxConcurrent 10 file:///usr/bin/sleep 300

jobID<EMAIL_ADDRESS>checking it I get
$ condor_q 1878521 -dag -af Environment | grep -o " JOBSUBJOBSECTION=. "
 JOBSUBJOBSECTION=0
 JOBSUBJOBSECTION=1
 JOBSUBJOBSECTION=2
 JOBSUBJOBSECTION=3
 JOBSUBJOBSECTION=4

JOBSUBJOBSECTION counter is working as expected.


Publish moon_flutter to pub.dev

Publish moon_flutter to pub.dev and attain as high pub score as possible (documentation, best practices, test coverage etc).

Partially done. We are for now present on pub.dev as unlisted package.

Any updates on this?

Hopefully late Q1 or early Q2 2024.

Folks are starting to talk about moon on twitter. Hoping to see this on pub soon.

There are multiple reasons why it has not yet left unlisted status on pub. The obvious one is that some core components like Card, Slider, Stepper etc are still missing. There's also some juggling with internal priorities and acceptance criteria. But the bigger issue as we are getting close to 1.0.0 release and looking back at the whole journey holistically is that we are not 100% happy with the end result quite yet.
What we have currently is not majorly improving on what Flutters Material is doing. Yes we are exposing more parameters like animation duration and curves, yes the theming isn't a nuclear option of wrapping the app with some sort of MoonApp, yes composing ThemeExtensions is flexible and overridable (if clunky with the nested copyWith calls) and yes we have incorporated, expanded, fixed and been inspired by a lot of community solutions. But we are still currently swapping one restrictive way of doing things (Material) with another maybe less restrictive way.
The way you build, theme and compose widgets in Flutter is imho fundamentally flawed and just does not play well with things like consuming composite design tokens (this is almost a non-issue with web technologies and React Native StyleSheet approach). I have expounded more on this topic in this now closed Flutter PR comments: https://github.com/flutter/flutter/pull/142151#issuecomment-2010282434 (probably need to expand to see all the conversation). We have also strayed pretty far from the ideal of creating a headless UI approach in Flutter we initially set out to do.
For the past month or two we have been rolling ideas how to keep the opinionated Moon specifics (like theming) separated from the core of the component library. So that we can get back to have the core be as headless as possible, fulfill internal criteria and yet still allow the possibility for the community to build their own theming solution around it if so desired. Regardless which solution we decide upon, 1.0.0 will be breaking change in one way or the other. Though hopefully not too breaking and with proper deprecation approach.

Saw this on twitter and I'm super excited for this 🔥

We have released v1.0.0 but the package will remain unlisted until v2 as currently v1 has way too many solutions centered around our corporate internal customer needs. V2 should be something that is more flexible, composable and themable.


WIFI-838: Dynamic discovery of HSPs/IDPs

Dynamically discover RADSEC endpoint based on NAPTR DNS records.
Signed-off-by: Arif Alam<EMAIL_ADDRESS>

Merged b9e54ac2, thanks


Cannot configure the Robotiq gripper: IO Exception

Ros2 humble ubuntu 22.04.
the port connection /tmp/ttyUR
[ERROR] [1732020153.874565794] [RobotiqGripperHardwareInterface]: Cannot configure the Robotiq gripper: IO Exception (2): No such file or directory, file /src/planning_control-1119/serial-ros2/src/impl/unix.cc, line 152.

Do you have both the "Robotiq Grippers" and "rs483" URCaps installed?
They conflict with each other (see https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/blob/main/ur_robot_driver/doc/setup_tool_communication.rst) and you would need to disable the "Robotiq Grippers" URCap.


Add a workflow to build the Docker image

We won't see the result until we merge, so self-merging and checking if it fixes the issue (we haven't pushed a docker image in 20 days).

It worked \o/


update for Laravel 5.1 compatibility

guess you need another branch. at least temporarily - to support both versions L5 and L5.1

Can we do this to support both at once? E.g.
php

use Illuminate\Support\Collection;

...

protected function getExistingSlugs($slug)
	{
		$config = $this->getSluggableConfig();
		$save_to         = $config['save_to'];
		$include_trashed = $config['include_trashed'];

		$instance = new static;

		$query = $instance->where( $save_to, 'LIKE', $slug.'%' );

		// include trashed models if required
		if ( $include_trashed && $this->usesSoftDeleting() )
		{
			$query = $query->withTrashed();
		}

		// get a list of all matching slugs
		$list = $query->lists($save_to, $this->getKeyName());

		return $list instanceof Collection ? $list->all() : $list;
	}

I prefer @Keoghan's approach.  Did you PR that?

Hi - yes, sorry, I should have done separately, but it's included in the Issue 141 PR.

Solved by #148


Can't use with Expo

Tried to install module and peerDeps with expo install ...

I confirm, expo SDK 39 same issue...

You need to downgrade the react-native-redash.
yarn add react-native-redash will install 15.11.1 at this moment, and it seems like it will break expo-progress.
I downgraded below and it works with Expo SDK 39.
    "react-native-redash": "^14.1.1",

Also react-native-gesture-handler was updated when I run the module install command and expo-cli was warning about it so I reverted to what it was ("~1.7.0",)
Maybe we should modify the dependencies. (I'm not really familiar with making packages so I don't know how I could make a pull-req)

@foloinfo Your solution works for me! Thank you!

@foloinfo  Your solution works for me! Thank you!

The above solution appears to work for Expo SDK 40 also, thanks!

The above solution appears to work for Expo SDK 40 also, thanks!

Not working on SDK 41 with:
    "react-native-gesture-handler": "~1.10.2",
    "react-native-redash": "^14.1.1",

Working on Expo SDK 41 with the following packages:
"react-native-gesture-handler": "~1.10.2",
"react-native-redash": "~14.2.4"

Also working on Expo SDK 42 with the following packages:
"react-native-gesture-handler": "~1.10.2",
"react-native-redash": "~14.2.4"
...but gives warnings:
interpolate() was renamed to interpolateNode() in Reanimated 2. Please use interpolateNode() instead
interpolate() was renamed to interpolateNode() in Reanimated 2. Please use interpolateNode() instead


Add --format option when publishing layer archives

First pass at #90 (still needs docs updates and additional tests)

Tests added for the gzip archive generation, but the deployment tests are currently failing (apparently on the shutil.unpack_archive step).

First step in resolving that should be to add round trip tests for each archive format as noted in the TODO comment for https://github.com/lmstudio-ai/venvstacks/pull/94/files#diff-f7a0668aa31dcd0f42d10a363e7df152b718bac6a30aefe1c2108b34c59b280d


Feature/ssh keys

Description
I think we're ready to go for this one, at least in order to present it and get feedback. Consensus seems to be that clearing the success message isn't a big problem; everything else mentioned has been addressed.
Type of Change

Non breaking change ('update', 'change')

Also I broke something ARB-1344


add an option to JUnitReporter to write the output to a single xml file

With this Pull Request, you can initialize the JUnitReporter to write its output to a single xml file instead of one xml file per test suite. This can be useful to simplify or speed up CI parsing.
eg:
require "minitest/reporters"
Minitest::Reporters.use! Minitest::Reporters::JUnitReporter.new('reports/path', single_file: true)

In the process I also changed the position empty = true argument to a keyword argument.

What do you think would be an appropriate name for the option flag?
Is it ok to use keyword arguments? Or should I rewrite it to use a ruby 1.9 style options hash?

Well, we are supposed to work with at least ruby 1.9, but keyword arguments are ruby 2.0 feature.
Also I'd prefer to be backward compatible, JUnitReporter.new( 'filename', false) still should work.

You're right, it's better to keep Ruby 1.9 compatibility.
I've adapted my code.

Any change to get final version in near future?

@os97673 I've sorted the tests by class.

Thank you for the contribution.  I've merged the PR but perhaps you would add some documentation to the class about the new option (so others would know about it ;)


Feature Request: Add a range method to Array

A simple generator that creates a numerical array: http://docs.python.org/library/functions.html#range
Array.range(3); // [0, 1, 2]
Array.range(1, 11); // [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
Array.range(0, 30, 5); // [0, 5, 10, 15, 20, 25]
...

I don't think that can be lazy evaluated in JS?

Check Number#upto and Number#downto for this... giving me ideas for the docs now though....

I am just quick by writing issues ;)

No worries :)

No worries :)


A0-3946: Fix password saving function not working properly

Issue 1: Password saving feature was not consistent. ✅
Issue 2: If checkbox "Extend the period without password by 15 minutes" was not checked, it locks account and on next sign in asks for password, even if saved password was still in the memory and it didn't expire yet. ✅
Tested in Chrome and FF.
P.S. I edited some code but were not able to test them yet, since nightly wallet was not responding. I will test it again in the morning.

Nightly is down since yesterdays evening :(( I were not able to test new code yet...

Sure, sounds good
On Fri, Feb 9, 2024 at 1:42 PM Wojciech Basiura @.***>
wrote:

@.**** commented on this pull request.
In packages/extension-base/src/background/handlers/Extension.ts
https://github.com/Cardinal-Cryptography/aleph-zero-signer/pull/143#discussion_r1484207352
:

 } else {

 pair.lock();

 await this.refreshAccountPasswordCache(pair, { clearCache: true });

okay, it was my idea, sorry, but I think there is too much going on in
refreshAccountPasswordCache 😅
How about a this.clearCache(pair) method and no clearCache param from
refreshAccountPasswordCache? I just find it confusing that we refresh
account twice
—
Reply to this email directly, view it on GitHub
https://github.com/Cardinal-Cryptography/aleph-zero-signer/pull/143#pullrequestreview-1872190570,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAWREIE3WXDUJH5VKP3WQZTYSYDQ3AVCNFSM6AAAAABCVHJNDGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQNZSGE4TANJXGA
.
You are receiving this because you authored the thread.Message ID:
@.***
.com>


going GREEN

hey first nice code
my problem is as soon as I switch on from my Home assistant the led is normal an after 3 sec. it turn green (also disconecting from the pc) somtimes I can turn it on and of but after a smale time it is Green again
LG Simon

Can you give me more information? Which sketch? What's you configuration?


Using "Int64" for SQLite type "INTEGER" instead of "Int"

Hi,
From your code, you directly convert 64 bits integer to Swift "Int". It will cause unexpected result on 32-bits device. Could you map the SQLite type "INTEGER" to Swift "Int64"?
Thanks a lot.
            } else if let result = result as? Int {
                sqlite3_result_int64(context, Int64(result))

                case SQLITE_INTEGER:
                    return Int(sqlite3_value_int64(value))

        } else if let value = value as? Int {
            try(sqlite3_bind_int64(handle, Int32(idx), Int64(value)))

            case SQLITE_INTEGER:
                return Int(sqlite3_column_int64(self.handle, Int32(idx)))

Have you actually encountering a problem here? I think this is basically a non-issue, and changing it would negatively impact the interface. If you're worried about overflow (on an auto-incrementing key, for example), you could use a TEXT column (or UUIDs).
If you have suggestions for supporting Int64 while letting the average user continue to use Int, please let me know.

Hi, I am using an integer to store unix timestamp (comes from server). It is my fault to use Int at beginning. But once I want to switch to Int64, I have no chance to store it properly.
I can use TEXT, but I don't think it is good idea. The sqlite type INTEGER can be at most 64bits on either 32bits device or 64bits device. So I think it should be nice to let caller has chance to pass or get a 64 bits integer even on 32bits device.
I have forked this repo and define an alias using macro to replace almost all Int:
#if SQLITE_USING_INT64_AS_INTEGER
public typealias SQLiteInt = Int64
#else
public typealias SQLiteInt = Int
#endif

Without "SQLITE_USING_INT64_AS_INTEGER", the common user do not need change anything.
With it, you are right, it indeed badly impact the interface, you must explicitly convert Int literal to Int64. But it is Swift language feature/bug.
Here is the change on my repo (all unit tests with/without the macro are passed), could you please take a look:
https://github.com/lestathc/SQLite.swift/commit/eb8c398be063a8a8be95e4a4964e53340dfe3ff5
Thanks.

Could you please try the int64 branch I just pushed? It's off the Swift 1.2 branch for now, but I'll try to get a Swift 1.1-compatible branch up soon.

thank you so much for fixing this! saved my day! :)

Please let me know how this affects your interfaces (and how noisy your code becomes). If you're using the type-safe interface, hopefully it's limited to the times you use Expression<Int64>.

Closed by https://github.com/stephencelis/SQLite.swift/commit/5380d5b502bd76ea99fe0ec54785f6bacd1cb8c1

Thanks for fixing.
For some reason, I can not install xcode6.3, so I do not try this. But I think it woks like my forked solution with the compile flag.
Thanks a lot.

Oh, seems you have merged it with main branch, checked and changed my code. Work perfectly, thank you so much.

@lestathc Hope it's a clean solution for you!


Fixed #30687 -- Fixed using of OuterRef() expressions in distance lookups.

https://code.djangoproject.com/ticket/30687

rebased onto latest master

buildbot, test on oracle.

@brownan Thanks for this patch :+1: I pushed minor edits.
@charettes Thanks for the review :+1:

@charettes I did try leaving out the tuple condition and returning a list unconditionally, but some tests failed. Turns out at least one place elsewhere in the code expects a tuple type and not a list (I forget where). I didn't try returning a tuple unconditionally, but from the CI tests it seems that doesn't hurt anything.
Thanks for the comments, I'll keep them in mind for my next patch.


#12 semaphoreci badge

Coverage remained the same at 89.806% when pulling 719eb0c7f46b8152f099222ffdbab713976a069c on readme-semaphoreci into 4470ee0b8bfdc22500ef3517ef71de01ab5b8a94 on master.


How to infer the aspect and aspect-sentiment for some custom sentence?

For eg given the sentence, "the acting was good but direction was poor", I want to infer the (aspect, aspects-sentiment) pairs such as (acting,good), (direction,poor). How can I do that?
Kind regards

Stanfold CoreNlp have a toolkit can do this


[chores] Allow passing a string or uuid to the membership helpers

Allow passing an UUID or str to the membership helpers, which will
be interpreted as organization primary key.
This is useful in those cases in which building the organization
instance requires generating an extra DB query: passing
obj.organization_id instead of obj.organization will result
in less queries being executed.

Coverage increased (+0.01%) to 97.951% when pulling 85dfe0c1dc7c61926cb1e3b0888ecadeb22b4398 on allow-pass-pk-to-membership-helpers into 6a8581482600c814bca1058d50b39e5ae79357ad on master.


Notion. Don't know if its bug yiiActiveForm after submit

Hi, everyone! I found strange reaction while working with yiiActiveForm.js and validating data.
When we are working with validationOnSubmit normal behavior is to press submit -> yii (js) is using method methods.submitForm which checks if data validated and inserting input[type=hidden][name=submit] when we forcing submit from button. Aftewards, yii forcing second submit on form.
The bug is occured when on tag button exisiting option [name=submit]. Probably clear JS cannot find input or something and second submit cannot be called from yii. For userthis bug looks like to need to click 2 times on button. What do you think about this reaction. Does yii need to control this situation?

How to reproduce it?

You need to create ActiveForm with validationOnSubmit and render Html::submitButton with htmlOption
name=submit
After validation will be created input with same name and bug should happen

same issue! i have the following code, and have to click submit button twice to submit the form.
<?php $form = ActiveForm::begin() ?>
<?= $form->field($model, 'username')?>
<input type="submit" name="submit" />
<?php ActiveForm::end()?>

Btw, sorry that i didnt say that bugfix to that situation is to remove [name=submit] from your Submit button or input. But it still the strange bug

https://github.com/yiisoft/yii2/issues/8756

@kLkA this link explain the problem that cause behavior.

@kLkA see this https://api.jquery.com/submit/

Forms and their child elements should not use input names or ids that conflict with properties of a form, such as submit, length, or method. Name conflicts can cause confusing failures.


Java change feed processor library

Is there any plan for adding Java library for change feed processor library ? Or is there some kind of tutorial which shows the same using Java or REST APIs in some other language ?

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

ID: e1a5194d-0869-94e6-227f-4fba0c798b22
Version Independent ID: 47f771ee-5237-7fb5-dbc6-fcebafdec142
Content: Working with the change feed processor library in Azure Cosmos DB
Content Source: articles/cosmos-db/change-feed-processor.md
Service: cosmos-db
GitHub Login: @rafats
Microsoft Alias: rafats

@anujku The best next steps for this is to create an entry in the Cosmos DB User Voice, and please reach out to the product group directly: askcosmosdb at Microsoft.com and request Java SDK specific change feed processor examples/content. By doing so, you will get more traction with your request. By adding a User Voice entry, others can upvote and comment with regard to the desired functionality.
We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


pre-requisite dependency(node or yarn) version check added in dev.sh file

fixed #168

First check

[x]  Node is installed or not
[x]  Compatible node version is installed or not

Second check

[x]  Yarn is installed or not
[x]  Compatible yarn version is installed or not

If these two checks will pass then only ./dev.sh will run successfully
@jayantbh sir take a look

REQUIRED_DOCKER_VERSION=22.3.1
How did you land on this version being required?
Not saying it's wrong, but I thought we need v24 at least. Unless you're sure that it works with v22 perfectly, you might want to change that to v24.

REQUIRED_DOCKER_VERSION=22.3.1

How did you land on this version being required? Not saying it's wrong, but I thought we need v24 at least. Unless you're sure that it works with v22 perfectly, you might want to change that to v24.

Sorry sir, I want it to 27.3.1 and this is because I have read docker docs it is the latest docker version and I also use this version locally

The earliest version that supports the docker watch and sync commands will be sufficient.

I have an idea that'll make the version check experience better.
Right now, let's say all your versions are wrong...
Then you run dev.sh, and it breaks saying the node version is wrong.
You fix that, then it says yarn version is wrong, and so on.
What if we check all breaking versions without killing the script, and then list breaking versions of everything at the end right before killing the script?

@jayantbh Sir, I have changed the docker version 24.0.0 because it is docker watch was added
and can you tell me why my pre-commit checks are failing

I have an idea that'll make the version check experience better.
Right now, let's say all your versions are wrong...
Then you run dev.sh, and it breaks saying the node version is wrong. You fix that, then it says yarn version is wrong, and so on.
What if we check all breaking versions without killing the script, and then list breaking versions of everything at the end right before killing the script?

on it sir

@jayantbh how my pr has 23 commits. I have not added this much

You would need to rebase your branch onto main. This might have happened due to merging main into your branch.

@jayantbh Sir i have rebased it but it is still giving this pre-commit check error

Is it even possible to fix this error


fix: could not find a declaration file for module 'ansis'

Types of changes

This PR contains a:

[x] bugfix
[ ] new feature
[ ] code refactor
[ ] test update
[ ] typo fix
[ ] docs change
[ ] breaking change

Motivation / Use-Case

Fixes this TypeScript error:

Breaking Changes
None
Additional Info

Checklist

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

hang on! @webdiscus what's this file? https://github.com/webdiscus/ansis/blob/master/pkg/package.json why is there two package.json files?

hang on! @webdiscus what's this file? https://github.com/webdiscus/ansis/blob/master/pkg/package.json why is there two package.json files?

Hello @will-stone,
can you please add the types.d.ts to the pkg/package.json too.
We have 2 package.json files:

./package.json - the file for local development and contribution.
The source code is written as ESM, therefore for local development is required the "type": "module" here.
The main file is defined as source file: "main": "./src/index.js" for tests.
./pkg/package.json - the clean & small file for NPM package, containing different fields.
The NPM package contains "compiled" universal (ESM/CJS) code, therefore is required different file with other "main": "./index.js" and the type of  the package is not module.

can you please change the "version": "2.0.2", field in both package.json and pkg/package.json files

Done and done 👍

@will-stone  the v2.0.2 is deployed.
Thank you!

Oh awesome! thanks for the quick turnaround 🥳


refactor: Move keystate into StreamDeck class

This let's us expand the StreamDeck class to multiple streamdecks in the future.

LGTM, good to merge :+1:


add more specific log message to readClusterIDsForOrgID

Description
I was trying to find the amsclient is not able to retrieve cluster list. Using fallback method, which wasn't to be found in logs, so I assumed it was using the AMS API correctly, but I didn't notice that that part is only ran if amsClient is initialized, which isn't the case on QA I suppose.
Testing steps
n/a
Checklist

[x] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

LGTM of course. The amsclient package prints a message if it is not initialised, but only at the very beginning of the start up of the service


Can see the service starting up in the cli but cant access it through browser

i am using below config and could see the service listening at <IP_ADDRESS>:3000
docker run -p 3000:3000 quay.io/gambol99/keycloak-proxy:latest --listen=<IP_ADDRESS>:3000  --discovery-url=https:///auth/realms/ --client-id=xyz --resources="uri=/*" --enable-logging=true --verbose=true --upstream-url=http://localhost:8080
When i open a browser an go to http://<IP_ADDRESS>:3000, i never gets redirected to anywhere and i see server not found. even though my keycloak-proxy service is up and running. I may be not understanding how this keycloak-proxy.
Please help me where i  am going wrong.

hi @abhishekraghav ... this is docker networking issue, your listening on --listen <IP_ADDRESS>:3000 and the ports aren't being forwarded ... you can --listen :3000

Hey Thanks a lot. Now i am actually get to see some action.
This is my configuration i am passing
docker run -p 3000:3000 quay.io/gambol99/keycloak-proxy:latest --listen=:3000 --discovery-url=https:///auth/realms/DCI --client-id=safety --client-secret=977fc4ed-e2b0-485b-a398-be017b25e926 --resources="uri=/*|methods=GET" --enable-logging=true --verbose=true --upstream-url=http://localhost:8080/
I am being redirected to keycloak once i try accessing  http://localhost:3000 and once i enter the users credentials, i am seeing a call being made to /oauth/callback and then i am locked in infinite loop.
This is my log looks like:

Now I am successfully being redirected to keycloak after i am

hi @abhishekraghav .. the issue is caused by the proxy not listening on https. By default for security reasons the cookie is set secure only, so your browser is wisely refusing to send the access token.
Normally it will warn you of the configuration error here but because you've not specified a --redirection-url  it doesn't know what the incoming protocol will be. This option is purposely left configurable as in our setup's we terminate TLS on the upstream proxy. But yes it should be documented better!!.
In regard to fixing it for testing you can just override the setting via --secure-cookie=false or simply set the proxy to use TLS with --tls-cert and --tls-private-key

hi @abhishekraghav  ... did that solve the issue? ... can i close the issue

Hey @gambol99 thanks a lot. Now i am not seeing the infinite loop issue. I think i am almost there.
There is one thing though,  i am not able to set the routings properly. I am trying to move away from keycloak-proxy and instead using your solution as it is more rich in features.
Here's my keycloak proxy config looks like:
{
"target-url":"http://:8080",
"bind-address":"<IP_ADDRESS>",
"http-port":"8080",
"applications":[
{
"base-path":"/",
"error-page":"/error.html",
"proxy-address-forwarding":true,
"adapter-config":{
"realm":"sample",
"auth-server-url":"https:///auth",
"ssl-required":"external",
"resource":"my-resourse-name",
"public-client":true
},
"constraints":[
{
"pattern":"/protected/",
"authenticate":"true"
},
{
"pattern":"/ui/",
"permit":"true"
}
]
}
],
"header-names":{
"keycloak-email":"mail"
}
}
I just wanted to know, what should be corresponding config file for go-KCproxy looks like.
i tried this, i couldn't get it correct,
docker run -p 3000:3000 quay.io/gambol99/keycloak-proxy:latest --listen=:3000 --discovery-url=https:///auth/realms/sample --client-id=my-resourse-name --client-secret=977fc4-2b0-485b-a398-be017b25e926 --secure-cookie=false --redirection-url=http://localhost:3000  --resources="uri=/protected/*" --enable-logging=true  --verbose=true --upstream-url=http://:8080
Am i missing anything here.
Thanks again.

Hi @gambol99  any other information you need from my setup..??

hi @abhishekraghav .. what is the error your getting? as i'm not seeing anything unusual
[jest@starfury keycloak-proxy]$ docker run -ti --rm quay.io/gambol99/keycloak-proxy:latest --version
keycloak-proxy version v2.1.0-rc2 (git+sha: ffe2fc4, built: 17-07-2017)
...
docker run --net=host quay.io/gambol99/keycloak-proxy:latest --listen=:3000 --discovery-url=<url> --client-id=broker --client-secret= --redirection-url=http://<IP_ADDRESS>:3000 --resources="uri=/protected*" --enable-logging=true --verbose=true --upstream-url=http://<IP_ADDRESS>:8080 --secure-cookie=false

[jest@starfury]$ curl -k http://<IP_ADDRESS>:3000/test
dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
[jest@starfury]$ curl -k http://<IP_ADDRESS>:3000/test

[jest@starfury]$ curl -k http://<IP_ADDRESS>:3000/protected
Temporary Redirect.
[jest@starfury]$ curl -k http://<IP_ADDRESS>:3000/protected/test
Temporary Redirect.
[jest@starfury]$ curl -k http://<IP_ADDRESS>:3000/public/something
dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused

Hey thanks.
Yes, its actually working. I have few doubts
is it possible to have redirects like this,
if i hit KeycloakProxyURL, i should be redirected to my UI compoment automatically. Currently i have to append /ui/ at the end of my keycloak proxy url (like this: localhost:3000/ui/) to redirect to my web component.
i did configure my upstream url as like this:
--upstream-url=http://:/ui/
Still it redirects me to '/'.
There are other calls also which are made from ui. e.g. /protected which is working fine expected.
Thanks.

hi @abhishekraghav ... there isn't an option for a default redirect i'm afraid. At present, the proxy will keep the incoming url via state, perform the oauth flow and redirect back to the previous requested url, so if you come in via / it will redirect post auth. Since it's only /protected* which is authentication can you not place a redirect in the app? ... Also, note any uri added upstream-url would be ignored, the proxy only care's about the upstream host.

Thanks for the explanation. Now i understood.
One more question regarding injecting headers:
In keycloak proxy there is way to inject header like this and also you can override the header name in it e.g.
"header-names":{
"keycloak-email":"mail"
}
In you version of keycloak proxy , what should be the corresponding way to achieve this.
If i have to instruct KC proxy to inject user's email into the headers, what  should be the syntax..?
Is it possible to override the header name..?
I found that there is something like this:
--headers value                     custom headers to the upstream request, key=value
I am little confused on what should be the key and what should be the value..?
PS: In keycloak i have created the mappers for adding user's email in access token and ID token.

Also, I am little confused on how CORS can be enabled on KC proxy, i see way to add CORS header (Access-Control-Allow-Origin) header by passing this in the command line
--cors-origins=[https://]
But some how i am not seeing this header coming in the response from proxy in browser.
Am i doing something wrong..?
I see lot of other options to configure CORS related stuff e.g. --cors-methods, --cors-headers, --cors-exposed-headers,  --cors-max-age etc. Do i also need to pass these as well.
Also , how can i verify whether CORS header is added or not..?
Thanks.

Hey @gambol99  i could successfully inject the header in the response. I get it finally by passing adding claims like this:
"add-claims": [
"email"
]
On my application, i could retrieve the same with this key , "X-Auth-Email". 👍
Now the Only thing i am stuck now is the CORS Configuration.  Not really sure, how can i get that configured in my current setup.
Pasting the configuration i tried:
{
	"discovery-url": "https://keycloak-example-url/auth/realms/SAMPLE",
	"client-id": "sample",
	"client-secret": "sample-secret",
	"listen": ":3000",
	"enable-refresh-token": true,
	"redirection-url": "http://localhost:3000/",
	"upstream-url": "http://my-app-url/appContext/",
	"secure-cookie": false,
	"enable-logging": true,
	"verbose": true,
	"resources": [
		{
			"uri": "/protected/*"
		}
	],
	"cors-origins": ["*"],
	"cors-headers": ["Access-Control-Allow-Origin","Access-Control-Allow-Headers"],
	"cors-methods": [],
	"cors-credentials": true,
	"cors-max-age": "1h",
	"cors-methods": [
		"GET",
		"POST",
		"HEAD",
		"OPTIONS"
	],
	"add-claims": [
		"email"
	]
}

Everything works fine as per above config, only the CORS part i am not getting it right. Please see if thats the right configuration. I should be seeing the CORS headers in the response headers in the reponse, but i couldn't see any such header in the browser.
I really appreciate your help.
Thanks a lot.

Hey @gambol99  you can close this. I guess i should open a new issue/question for that as it is completely different from the original title of this issue/question.
Thanks.


Disable flaky failoverJournalFencingTest

Codecov Report

Merging #13341 (10b6fb5) into master (9c1c15f) will decrease coverage by 20.35%.
The diff coverage is n/a.

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

LGTM

alluxio-bot, merge this please.


How to boost a Keras model using AdaBoost classifier?

Hi all,
I'm gonna to use Adaboost classifier(sklearn.ensemble.AdaBoostClassifier) for bosting bottom keras model,and i know neural networks are not compatible with the sklearn Adaboost.
Can anyone guide me how to do this?
model = Sequential()
model.add(Dense(10, activation='relu', input_shape=(input_dim,)))
model.add(Dense(10, activation='relu'))
model.add(Dense(10, activation='relu'))
model.add(Dense(1, activation='relu'))

FYI- for those coming in through search, the stack overflow answer is here: https://stackoverflow.com/a/52246180/345660

i am facing the same problem if you figure out this problem please share your work with me how I can solve this issue.

See my stack overflow link above: https://stackoverflow.com/a/52246180/345660

@masoudnick Please check with the above comment and let us know if it is still an issue .Thanks!

Closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Reduce buffer size

Hi,
why is the buffer_size set to 10MB ? Can that be increased and is there any implication with the same
def all_reduce_and_rescale_tensors(tensors, rescale_denom, buffer_size=10485760):
"""All-reduce and rescale tensors in chunks of the specified size.

You can increase it. It will cause more memory usage for the buffer, but may be slightly faster. We've reworked this a bit in a forthcoming fairseq update, and set the buffer size to the number of model params automatically (i.e., there's only a single all-reduce call per update).

thanks for the info @myleott


Update how-to-install-the-management-and-reporting-databases-on-separ…

…ate-computers-from-the-management-and-reporting-services51.md
Added markdown for Notes.
Removed characters that created formatting errors.
Removed dead URL.

#sign-off

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.


Promote modules out of core?

Punting this to 0.6. Too much of a pain right now

What do you want to keep in core? You think bare minimum like index/series/frame/panel?

I don't see a need for the core subpackage. I'm going to punt this to 0.7 early next year, will not happen for 0.6


[DONT_MERGE][monitoring][broker][metadata_store] add metrics for BatchMetadataStore

Motivation
add metrics for batch_metadata_store.
This PR should being merged after https://github.com/apache/pulsar/pull/17041 in case of conflicts.
Documentation
Check the box below or label this PR directly.
Need to update docs?

[x] doc-required
(Your PR needs to update docs and you will update later)

[ ] doc-not-needed
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

TIP: You can covert PR status to draft, if it's not ready for review. :)

TIP: You can covert PR status to draft, if it's not ready for review. :)

Thanks~

TIP: You can covert PR status to draft, if it's not ready for review. :)

Thanks~

See this.

@codelipenghui @asafm PTAL

@asafm I've updated the PR and only keeps pulsar_batch_metadata_store_executor_queue_size, pulsar_batch_metadata_store_queue_wait_time.
and add pulsar_batch_metadata_store_batch_execute_time pulsar_batch_metadata_store_perbatch_ops

@codelipenghui PTAL

/pulsarbot run-failure-checks

Codecov Report

Merging #17072 (0d79b3f) into master (0866c3a) will increase coverage by 31.46%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master   #17072       +/-   ##
=============================================
+ Coverage     38.97%   70.43%   +31.46%
+ Complexity     8311      436     -7875
=============================================
  Files           683       26      -657
  Lines         67325     2246    -65079
  Branches       7217      245     -6972
=============================================
- Hits          26239     1582    -24657
+ Misses        38079      492    -37587
+ Partials       3007      172     -2835

Flag
Coverage Δ

unittests
70.43% <ø> (+31.46%)
:arrow_up:

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

Impacted Files
Coverage Δ

...java/org/apache/pulsar/proxy/stats/TopicStats.java
58.82% <0.00%> (-41.18%)
:arrow_down:

...a/org/apache/pulsar/proxy/server/ProxyService.java
80.00% <0.00%> (-0.94%)
:arrow_down:

...n/java/org/apache/pulsar/broker/PulsarService.java

.../pulsar/broker/service/AbstractBaseDispatcher.java

...sar/broker/service/persistent/PersistentTopic.java

...ransaction/buffer/impl/InMemTransactionBuffer.java

...ransaction/buffer/impl/TopicTransactionBuffer.java

...nsaction/buffer/impl/TransactionBufferDisable.java

.../metadata/v2/TransactionBufferSnapshotIndexes.java

.../org/apache/pulsar/broker/lookup/RedirectData.java

... and 649 more

/pulsarbot run-failure-checks

@codelipenghui all the required checks are passed

@tjiuming did you have a plan to add some information about the new metrics?

@tjiuming did you have a plan to add some information about the new metrics?

there are already a PR for the doc, I'll update it soon


use same yValues, no line show in chart

When I use LineChart and put the same y-value on it from begin to end,there is no line showed in the chart.It should be a line,how to solve this problem?Thanks

Hi, I believe it's the same case as in #143 and #169. Try to use custom viewport.

Thanks！I have tried the method you suggested, but it seemed nothing changed.I will appreciate if you fix the problem.

Oh, I use the method you told after setting the data, it works! Thank you so much!


Map Popup with HTML Bootstrap 5 Components wont Interact

Hello,
[Environment] Azure maps SDK V2 & 3 (currently using latest preview 10)
I'm embedding some HTML content into the map popups using Bootstrap 5 components. I'm finding that some of the components such as range sliders and input fields won't allow me to interact with them.
Sample popup shown below, the buttons and date picker are working so not all component types are affected. If I load the same html into a normal web page then all components are OK, something affects them when placed inside the popup.

I found a question raised on this in 2020 but it seems the topic had not been resolved. Ive had to forceully set the input field to focus before it would work (later found this in one of your code samples too). This is not ideal but at least something I can work around.
Once I started testing some other component types such as a range slider and select dropdown, I found that setting the dom element to focus does not resolve the issue for all component types, so far only an input field is resolved using this trick.
After hours of scratching head, I've managed to find the source of conflict which resides somewhere within the mapcontrol JavaScript file.

In the screenshot below you can see under mousedown, the item div.popup-container.bottom.maplibregl is causing this conflict.

Once I deleted this event listener, I was able to interact with all the html components without an issue.

I dont know how I'm going to workaround this becuase this event listener is coming from a file in your SDK. This is a big issue for my project, please help :)

After studying the sdk's code,  it looks to be that you've set the popup container (some parent element) to have the mousedown listener calling preventDefault of which any child elements (including my own HTML Content inside the popup) was also inhereting this and stopping some component types from working properly.

I eventually figured out that explicitly adding  onmousedown="event.stopPropagation()";  to each of the html components that were affeted when loading them into the popup would stop this inheretance from the popup container down the tree across all the child elements.
Having applied this workaround, the elements seem to interact properly now (still some testing to do) but looking much better now. It does feel a bit hacky having to do this, would be interested to know why the popup's parent element needs a preventDefault in the first place and whether it's somethng that would be better removed? considering that touch events are not affected in this way.

I suspect that those events are have to do with the dragging feature of the popup. They should be adding/removing those events as needed based on if the dragging option is turned on or not. I'll provide that feedback to the Azure Maps team.

Thank you for bringing this to our attention. After careful consideration, the team has decided not to fix this particular issue due to conflicts with meeting accessibility requirements. In the meantime, we recommend using the workaround that you have discovered. If you have any further questions or concerns, please don't hesitate to reach out. We value your feedback and strive to provide the best possible user experience for all our customers.