kubectl submission of config.yml secret fails:

The instructions in the README.md say to submit the clair-kubernetes.yml file first, but this seems it would fail as it's trying to mount a secret that is submitted second.  If it fails, it should restart and try to find the newly submitted secret.  However, either way it still fails with config.yaml not found:
`knepper@MacBook-Pro-2:~/clair/contrib/k8s> kubectl --server="<IP_ADDRESS>:8080" create -f clair-kubernetes.yaml
You have exposed your service on an external port on all nodes in your
cluster.  If you want to expose this service to the external internet, you may
need to set up firewall rules for the service port(s) (tcp:30060,tcp:30061) to serve traffic.
See http://releases.k8s.io/release-1.1/docs/user-guide/services-firewalls.md for more details.
service "clairsvc" created
replicationcontroller "clair" created
replicationcontroller "clair-postgres" created
error validating "clair-kubernetes.yaml": error validating data: field nodePort: is required; if you choose to ignore these errors, turn validation off with --validate=false
jknepper@MacBook-Pro-2:~/clair/contrib/k8s> kubectl --server="<IP_ADDRESS>:8080" describe svc
Name:			clairsvc
Namespace:		default
Labels:			app=clair
Selector:		app=clair
Type:			NodePort
IP:			<IP_ADDRESS>
Port:			clair-port0	6060/TCP
NodePort:		clair-port0	30060/TCP
Endpoints:
Port:			clair-port1	6061/TCP
NodePort:		clair-port1	30061/TCP
Endpoints:
Session Affinity:	None
No events.
Name:			dashboard-api-service
Namespace:		default
Labels:			romulus/lb=vulcan,romulus/route=public
Selector:		app=dashboard-api
Type:			NodePort
IP:			<IP_ADDRESS>
Port:				9003/TCP
NodePort:			30001/TCP
Endpoints:		<IP_ADDRESS>:9292
Session Affinity:	None
No events.
Name:			kubernetes
Namespace:		default
Labels:			component=apiserver,provider=kubernetes
Selector:
Type:			ClusterIP
IP:			<IP_ADDRESS>
Port:				443/TCP
Endpoints:		<IP_ADDRESS>:6443
Session Affinity:	None
No events.
`
Nonetheless, my problem is the submission of the secret fails with the following output:
jknepper@MacBook-Pro-2:~/clair/contrib/k8s> kubectl --server="<IP_ADDRESS>:8080" create -f config.yaml --v=3 F0321 09:31:44.340694   84663 helpers.go:96] error validating "config.yaml": error validating data: Object 'apiVersion' is missing in '{"clair":{"api":{"cafile":null,"certfile":null,"healthport":6061,"keyfile":null,"paginationKey":null,"port":6060,"servername":null,"timeout":"900s"},"database":{"cacheSize":16384,"source":"postgres://postgres:password@postgres:5432/postgres?sslmode=disable"},"notifier":{"attempts":3,"http":{"cafile":null,"certfile":null,"endpoint":null,"keyfile":null,"servername":null},"renotifyInterval":"2h"},"updater":{"interval":"2h"}}}'; if you choose to ignore these errors, turn validation off with --validate=false
My kubernetes version is:
v1.0.3
Pod creation failing:
jknepper@MacBook-Pro-2:~/k8s> kubectl --server="<IP_ADDRESS>:8080" describe pods clair-u1p5r Name:				clair-u1p5r Namespace:			default Image(s):			quay.io/coreos/clair Node:				<IP_ADDRESS>/<IP_ADDRESS> Start Time:			Mon, 21 Mar 2016 09:13:47 -0700 Labels:				app=clair Status:				Running Reason:				 Message:			 IP:				<IP_ADDRESS> Replication Controllers:	clair (1/1 replicas created) Containers:   clair:     Container ID:		docker://aa09617c867d0d7b1f9a0ad1b42d8d7ca513fce9824da7bceae0202a59331c10     Image:			quay.io/coreos/clair     Image ID:			docker://7158ef42f9d805c0498a2231c4fc5d6740f5bd359bf4e3540eda3ade3d985a49     State:			Running       Started:			Mon, 21 Mar 2016 09:47:11 -0700     Last Termination State:	Terminated       Exit Code:		1       Started:			Mon, 21 Mar 2016 09:47:01 -0700       Finished:			Mon, 21 Mar 2016 09:47:01 -0700     Ready:			False     Restart Count:		11     Environment Variables: Conditions:   Type		Status   Ready 	False  Volumes:   secret-volume:     Type:	Secret (a secret that should populate this volume)     SecretName:	clairsecret   default-token-i7ba3:     Type:	Secret (a secret that should populate this volume)     SecretName:	default-token-i7ba3 Events:   FirstSeen	LastSeen	Count	From			SubobjectPath				Reason		Message   ─────────	────────	─────	────			─────────────				──────		───────   33m		33m		1	{scheduler }							scheduled	Successfully assigned clair-u1p5r to <IP_ADDRESS>   33m		33m		1	{kubelet <IP_ADDRESS>}	implicitly required container POD	pulled		Pod container image "gcr.io/google_containers/pause:0.8.0" already present on machine   33m		33m		1	{kubelet <IP_ADDRESS>}	implicitly required container POD	created		Created with docker id 2518104c9595   33m		33m		1	{kubelet <IP_ADDRESS>}	implicitly required container POD	started		Started with docker id 2518104c9595   33m		33m		1	{kubelet <IP_ADDRESS>}	spec.containers{clair}			created		Created with docker id 9118b37ec74f   33m		33m		1	{kubelet <IP_ADDRESS>}	spec.containers{clair}			started		Started with docker id 9118b37ec74f   33m		33m		1	{kubelet <IP_ADDRESS>}	spec.containers{clair}			created		Created with docker id 6abc111e5983   33m		33m		1	{kubelet <IP_ADDRESS>}	spec.containers{clair}			started		Started with docker id 6abc111e5983
The error returned from the submitted pods are related to not being able to find the config.yaml:
jknepper@MacBook-Pro-2:~/k8s> kubectl --server="<IP_ADDRESS>:8080" logs clair-u1p5r 2016-03-21 16:47:41.652439 C | main: failed to load configuration: open /config/config.yaml: no such file or directory
I also attempted removing references to the secret, the config arguments to the clair container as well as the mount point to get the ""defaults"" specified in the config.yml file as stated when you don't use the secret, and it still failed with the same error but different path '/etc/config/config.yaml' not found.

Hi,
The issue here is that you try to create a k8s secret using config.yaml which contain the Clair configuration and not a proper k8s secret object. Actually, you're using k8s 1.0 and the README makes the assumption that k8s 1.2 is used.

You should create a yaml file containing a k8s secret object and use it instead.
We have to modify the README to make that assumption clear and wait until the single-node k8s installation procedure actually installs 1.2 and not 1.1 as it currently does. This should be out this week and next week. We could also create a secret file too but we would have to base64 encode Clair's config, which is not really readable/discoverable - while the point of these instructions are to make it so.

Waiting on https://github.com/coreos/coreos-kubernetes/pull/355 and subsequent doc update on https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant-single.html

@knepperjm  this issues has been closed because kubernetes v1.2 is now available via coreos-kubernetes. You can find the docs for vagrant here: https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant-single.html


Incompatible Type Error Union Types

Why is this union type an error?
type Data = number[] | {}[] | Array<{}[]> | Array<number[]>

When I go to check my code it gives the following
build/js/helpers.js:2
  2: type Data = number[] | {}[] | Array<{}[]> | Array<number[]>
                 ^^^^^^ number. This type is incompatible with
  2: type Data = number[] | {}[] | Array<{}[]> | Array<number[]>
                            ^^ object type

build/js/helpers.js:2
  2: type Data = number[] | {}[] | Array<{}[]> | Array<number[]>
                 ^^^^^^ number. This type is incompatible with
  2: type Data = number[] | {}[] | Array<{}[]> | Array<number[]>
                                         ^^^^ array type

build/js/helpers.js:2
  2: type Data = number[] | {}[] | Array<{}[]> | Array<number[]>
                 ^^^^^^ number. This type is incompatible with
  2: type Data = number[] | {}[] | Array<{}[]> | Array<number[]>
                                                       ^^^^^^^^ array type

build/js/helpers.js:2
  2: type Data = number[] | {}[] | Array<{}[]> | Array<number[]>
                            ^^ object type. This type is incompatible with
  2: type Data = number[] | {}[] | Array<{}[]> | Array<number[]>
                 ^^^^^^ number

build/js/helpers.js:2
  2: type Data = number[] | {}[] | Array<{}[]> | Array<number[]>
                                         ^^^^ array type. This type is incompatible with
  2: type Data = number[] | {}[] | Array<{}[]> | Array<number[]>
                 ^^^^^^ number

can you reproduce it in flow try?

I've updated the example with my code causing problems. Check out this flow
And here's a fiddle of how it is meant to work

I tried to rewrite your types in a DRY way. I think it works now.
Also Array.isArray(arr) is nicer than arr.constructor === 'Array'.

That did it. Thanks for the help. One question though, is it better to use an object literal or an Object wrapper? I read somewhere that since Object is a superclass of many javascript types, it could reference pretty much anything. I don't know if that's the case or not though.


Create CONTRIBUTING.md

Solves https://github.com/contactlab/contactlab-ui-components/issues/58

hi @BotamicIO thanks for the collaboration, but please make a fork/PR from the develop branch, I will add this information asap in the contributing file


Exception generating new chunk

https://gist.githubusercontent.com/Rongmario/7e23be9265468972fa78ca3fab665cb9/raw/5f0e6ce9e9a205856e109a0b9130ff5f5670bd25/gistfile1.txt

I had the same error.. fixed after removing Thaumcraft.

Hey guys, can you tell me if this is reproducable and how?


developper getting started page on istio/istio

there are a number of documents in each repo and elsewhere but we are missing a unified
"getting started" for development entry point in istio/istio
I will add first some pointers to the existing documents and we can unify as we go
cc @xiaolanz

done (at least initial page)


docs: remove $ from readme for easier copy and paste

docs: remove $ from readme for easier copy and paste
What does this PR do?
Using the copy and paste button on GitHub results in including $.
We should remove the $ from the README (on our podman desktop site, we
instead just ignore the $ at the beginning when copying and pasting).
Screenshot / video of UI

N/A
What issues does this PR fix or reference?

N/A
How to test this PR?

N/A
Signed-off-by: Charlie Drage<EMAIL_ADDRESS>

issue: please remove the svelte upgrade from that PR

Good catch, messed up my rebase!
Updated


Switch from mini-player to desktop player and then searching results in scaling issue

Checklist:

[x] I have checked that there are no issues with similar or the same content
YOU SHOULD CHECK CLOSED ISSUES ASWELL

[x] I have checked the FAQ (https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/wiki/FAQ) and the answer I am looking for is not there

[x] I have double checked and can reproduce the issue

OS:
Windows 7 Enterprise
GPMDP Version:
4.5.0
Issue Descriptions:
Switching from the mini player to the desktop player (not full screened) and then immediately searching for a song results in everything being displayed very small as if zoomed out very far. This does not happen every time and is not so often as to be a big problem but I have had it occur a couple of times a week with daily use of the app. Switching back to the mini player and then back to the desktop player corrects the display.
This has happened on both my primary and secondary monitor.

Steps to Reproduce:
With app in mini-player mode, click the button to expand to desktop mode and search for a song/artist/album.

I reported this issue last year here: https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/issues/2647,  but it was closed because apparantly I was the only one having it. I still experience the issue on two independent computers. One at work and the other at home. I have dual monitor setup in both workstations with one monitor rotated 90 degrees.
The issue is random and occurs sometimes only when I switch from the miniplayer to window.
@IrksomeZeus, Do you perharps have dual monitor setup with one monitor rotated 90 degrees. Thats the only common denominator in both my setups and I wonder if that is the cause.

I am running the app on my desktop with two monitors attached but neither are rotated. One is connected via DVI and the other is using a display port. It does not seem to matter which monitor the app is on.
The issue seems to happen most often when I have the mini-player open with the audio paused and I lock my computer for the night - it does not go to sleep, only locked. When I return in the morning and expand the player then enter a search, the described issue occurs.

I've been having some weird scaling issues as well. The app will also lose track of it's last know position on the screen.
setup:
High dpi screen at to 2000x3000 resolution with 200% scaling (so my old man eyes can actually see it.) This is the laptop's primary display.
I have 2 1080p monitors attached via a specialized Dock connected via display port these are set to 100% scaling
GPMDP will occasionally open mostly offscreen fairly frequently, but not 100% of the time. It will be scaled at 200%, even though what little of it that is on screen is on one of the 1080p monitors. I can normally crab the edge and move it to get the title bar back on the screen, but this does not always work. Removing the laptop from the dock or just starting the system w/o the dock connected will normally pull/start it fully on the primary screen.


PyTorch 1.12 with device "mps" for apple m1

Hi,
PyTorch 1.12 is finally optimized for apple silicon M1 processor but it requires torch.device("mps") configuration.
I was not able to set it and got this error when trying to set device to "mps" :
RuntimeError: Expected one of cpu, cuda, xpu, mkldnn, opengl, opencl, ideep, hip, ve, ort, mlc, xla, lazy, vulkan, meta, hpu device type at start of device string: mps
Could you please provide such parameter settings?
Thanks.

My bad, this is a pytorch-lightning issue.


Window mode for Integrated Terminal

I would be nice if we could use the Integrated Terminal in a window mode, like the DevTools allow in most browsers.

/duplicate https://github.com/Microsoft/vscode/issues/34442


reference circuit to check matplotlib changes

There are many changes happening on the matplotlib drawer and we need better confidence in the changes (given that there are no automated tests). I think we just need one reference circuit with all gates (standard library, a unitary, a state prep, QFT, opaque, reset, measure). This can go in tools. And then every PR has to show how that image will look like after the changes.
This could be used to test other things too but matplotlib is of immediate importance.

@ajavadia I thought I might try to take on creating the reference circuit you've described. It would help a lot in testing mpl drawer, especially in testing global changes, like layer widths and box widths.
I started by creating an import list, taking essentially everything from circuit.library and qiskit.extensions. I thought before I proceed further it would be good to get an approval on which of these gates are required and if there are others. I assume doing some controlled versions would be good and also doing some to_gate() gates. Here's the import list.
from qiskit.circuit.library.standard_gates import *
from qiskit.circuit.barrier import Barrier
from qiskit.circuit.measure import Measure
from qiskit.circuit.reset import Reset

from qiskit.circuit.library.blueprintcircuit import BlueprintCircuit
from qiskit.circuit.library.generalized_gates import (
    Diagonal,
    MCMT,
    MCMTVChain,
    Permutation,
    GMS
)
from qiskit.circuit.library.boolean_logic import (
    AND,
    OR,
    XOR,
    InnerProduct,
)
from qiskit.circuit.library.basis_change import QFT
from qiskit.circuit.library.arithmetic import (
    FunctionalPauliRotations,
    LinearPauliRotations,
    PiecewiseLinearPauliRotations,
    PolynomialPauliRotations,
    IntegerComparator,
    WeightedAdder,
)
from qiskit.circuit.library.n_local import (
    NLocal,
    TwoLocal,
    RealAmplitudes,
    EfficientSU2,
    ExcitationPreserving,
)
from qiskit.circuit.library.data_preparation import (
    PauliFeatureMap,
    ZFeatureMap,
    ZZFeatureMap
)
from qiskit.circuit.library.quantum_volume import QuantumVolume
from qiskit.circuit.library.fourier_checking import FourierChecking
from qiskit.circuit.library.graph_state import GraphState
from qiskit.circuit.library.hidden_linear_function import HiddenLinearFunction
from qiskit.circuit.library.iqp import IQP

from qiskit.circuit.quantumcircuit import QuantumCircuit
from qiskit.circuit.classicalregister import ClassicalRegister, Clbit
from qiskit.circuit.quantumregister import QuantumRegister, Qubit
from qiskit.circuit.gate import Gate
# pylint: disable=cyclic-import
from qiskit.circuit.controlledgate import ControlledGate
from qiskit.circuit.instruction import Instruction
from qiskit.circuit.instructionset import InstructionSet
from qiskit.circuit.barrier import Barrier
from qiskit.circuit.measure import Measure
from qiskit.circuit.reset import Reset
from qiskit.circuit.parameter import Parameter
from qiskit.circuit.parametervector import ParameterVector
from qiskit.circuit.parameterexpression import ParameterExpression

from qiskit.extensions.quantum_initializer.diagonal import DiagonalGate
from qiskit.extensions.quantum_initializer.initializer import Initialize
from qiskit.extensions.quantum_initializer.isometry import Isometry
from qiskit.extensions.quantum_initializer.mcg_up_to_diagonal import MCGupDiag
from qiskit.extensions.quantum_initializer.squ import SingleQubitUnitary
from qiskit.extensions.quantum_initializer.uc import UCGate
from qiskit.extensions.quantum_initializer.uc_pauli_rot import UCPauliRotGate
from qiskit.extensions.quantum_initializer.ucrz import UCRZGate
from qiskit.extensions.quantum_initializer.ucry import UCRYGate
from qiskit.extensions.quantum_initializer.ucrx import UCRXGate
from qiskit.extensions.simulator.snapshot import Snapshot

from qiskit.extensions.hamiltonian_gate import HamiltonianGate
from qiskit.extensions.unitary import UnitaryGate

import numpy as np
import matplotlib as mp

Thanks. I agree with you. I think we need all the standard gates. But not everything from the other parts of the library maybe 1 or 2 just to see how their parameters get rendered. We should also use isometry. The end result should not be so cluttered that it is hard to see anything so you might have to play around with it a bit.

On Jun 9, 2020, at 5:52 PM, Edwin Navarro<EMAIL_ADDRESS>wrote:
@ajavadia I thought I might try to take on creating the reference circuit you've described. It would help a lot in testing mpl drawer, especially in testing global changes, like layer widths and box widths.
I started by creating an import list, taking essentially everything from circuit.library and qiskit.extensions. I thought before I proceed further it would be good to get an approval on which of these gates are required and if there are others. I assume doing some controlled versions would be good and also doing some to_gate() gates. Here's the import list.
from qiskit.circuit.library.standard_gates import *
from qiskit.circuit.barrier import Barrier
from qiskit.circuit.measure import Measure
from qiskit.circuit.reset import Reset
from qiskit.circuit.library.blueprintcircuit import BlueprintCircuit
from qiskit.circuit.library.generalized_gates import (
Diagonal,
MCMT,
MCMTVChain,
Permutation,
GMS
)
from qiskit.circuit.library.boolean_logic import (
AND,
OR,
XOR,
InnerProduct,
)
from qiskit.circuit.library.basis_change import QFT
from qiskit.circuit.library.arithmetic import (
FunctionalPauliRotations,
LinearPauliRotations,
PiecewiseLinearPauliRotations,
PolynomialPauliRotations,
IntegerComparator,
WeightedAdder,
)
from qiskit.circuit.library.n_local import (
NLocal,
TwoLocal,
RealAmplitudes,
EfficientSU2,
ExcitationPreserving,
)
from qiskit.circuit.library.data_preparation import (
PauliFeatureMap,
ZFeatureMap,
ZZFeatureMap
)
from qiskit.circuit.library.quantum_volume import QuantumVolume
from qiskit.circuit.library.fourier_checking import FourierChecking
from qiskit.circuit.library.graph_state import GraphState
from qiskit.circuit.library.hidden_linear_function import HiddenLinearFunction
from qiskit.circuit.library.iqp import IQP
from qiskit.circuit.quantumcircuit import QuantumCircuit
from qiskit.circuit.classicalregister import ClassicalRegister, Clbit
from qiskit.circuit.quantumregister import QuantumRegister, Qubit
from qiskit.circuit.gate import Gate
pylint: disable=cyclic-import
from qiskit.circuit.controlledgate import ControlledGate
from qiskit.circuit.instruction import Instruction
from qiskit.circuit.instructionset import InstructionSet
from qiskit.circuit.barrier import Barrier
from qiskit.circuit.measure import Measure
from qiskit.circuit.reset import Reset
from qiskit.circuit.parameter import Parameter
from qiskit.circuit.parametervector import ParameterVector
from qiskit.circuit.parameterexpression import ParameterExpression
from qiskit.extensions.quantum_initializer.diagonal import DiagonalGate
from qiskit.extensions.quantum_initializer.initializer import Initialize
from qiskit.extensions.quantum_initializer.isometry import Isometry
from qiskit.extensions.quantum_initializer.mcg_up_to_diagonal import MCGupDiag
from qiskit.extensions.quantum_initializer.squ import SingleQubitUnitary
from qiskit.extensions.quantum_initializer.uc import UCGate
from qiskit.extensions.quantum_initializer.uc_pauli_rot import UCPauliRotGate
from qiskit.extensions.quantum_initializer.ucrz import UCRZGate
from qiskit.extensions.quantum_initializer.ucry import UCRYGate
from qiskit.extensions.quantum_initializer.ucrx import UCRXGate
from qiskit.extensions.simulator.snapshot import Snapshot
from qiskit.extensions.hamiltonian_gate import HamiltonianGate
from qiskit.extensions.unitary import UnitaryGate
import numpy as np
import matplotlib as mp
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

If we follow the #4544 approach, I think would be better to do one test per each.

But that creates a 100 images to manually check? Also some issues might arise in bigger circuits not trivial ones like how different boxes are spaced next to each other. I don’t have a good answer and we probably have to refine over time.

On Jun 9, 2020, at 8:16 PM, Luciano Bello<EMAIL_ADDRESS>wrote:
If we follow the #4544 approach, I think would be better to do one test per each.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Error when running script

when i try to run script i get this error.

I have the same

Use debug flag while compiling, run the exe using command prompt, so that
you get the proper error
Note the error and send it here, in most of the case there is some missing
dependencies on your system which leads to this error,
If you get any error like "ModuleNotFound", then try installing it and
create a fresh payload
On Tue, 10 May, 2022, 11:59 pm Fluorex, @.***> wrote:

I have the same
—
Reply to this email directly, view it on GitHub
https://github.com/PushpenderIndia/technowlogger/issues/29#issuecomment-1122730822,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANORYISXXQJ7DMXRHDV5HPLVJKTJHANCNFSM4TZC4TLA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Disable changing of the cursor shape when open with carbon-util-confirm

Hi,
There is this thing that is bothering me with the changing of the cursor shape. When I enter the prompt for carbon-util-confirm the cursor change to an underline and remane like that for all the shell session. I would be really nice having an option in the setting for disabling this behaviour.
https://user-images.githubusercontent.com/96259932/206923297-62acc267-547c-4cac-bff6-d93794d1799f.mov

Fair enough, I can imagine one wanting to see the regular cursor in such windows, I may actually remove that part all together since I don't think it provides much value 👍

#108 resolves this, I also defaulted Normal in this popup to use the same highlight group as the border and cursor line since by default it looked a bit confusing in menus with only 2 entries.
Cheers for the report 👍


Extracted file writing to separate method

Coverage decreased (-0.04%) to 68.182% when pulling dde56ffac5c3e89c8e674f85bcc29dab0fd2c3c1 on tomdcsmith:extract_output_file_writing_2 into ff6a2d880ddba041807f188b7bc81e6fb8a77f37 on EBIvariation:master.

Coverage decreased (-0.05%) to 70.366% when pulling 4f1d98e8c12f3d0a741a45ef0de69baef1144ab1 on tomdcsmith:extract_output_file_writing_2 into a9014223aa731e5bda832d9e1f24bc3f6ee102a5 on EBIvariation:master.


Update credentials for the MySQL and Postgres integrations without restart

Our database credentials (user/pass) are created and change regularly through automation.
However, the Datadog agent (with MySQL and Postgres integrations) only loads these configs on start, so the agent process must be killed and then a new process started.
This results in needing to kill and restart the process regularly. In our case, this means the entire k8s container(running datadog-agent).
What options are there to reload these credentials without a complete stop/start?

It'd be nice to be able to use a .pgpass file or even PGPASSWORD environment variable. That way we could keep the credentials in sync ourselves without the client loading them in on startup.
It seems we're required to specify a password (if the host isn't localhost) otherwise an empty string will be used.
https://github.com/DataDog/integrations-core/blob/27aa7aafb4e418831602096f6ebbb40227bcee22/postgres/datadog_checks/postgres/postgres.py#L309-L322

This is more of a feature request, if you still require this feature, feel free to reach out to support.


Watch a directory recursively

Hey folks 👋
Is it possible to watch the directory recursively? So when I do watch("/home/roma/"), I receive events from:

/home/roma/* files per se
/home/roma/docs and any other existing subdirectory of the path
/home/roma/justaddeddir/* - any new directory created after we have started watching the root dir

I assume that this is a common case for inotify usage and would be great to have in pynotify.
Thank you in advance!

Hello 👋
First off, thank you for showing interest in this project!
My initial motivation for creating this project was to make it easier to create an encrypted mirror of a few directories, so recursive usage was in mind.
During the design of PyNotify, though, I decided against including recursive capabilities. This was mostly because it should be relatively easy to implement on the consumer side, but also because it breaks the current level of abstraction. The library is currently an one layer above inotify (sending to handlers), whereas recursiveness implies another layer above (handling events).
I'm not against implementing recursiveness, I'm just providing the reasoning behind it not being implemented already. Perhaps an extra module to implement common tasks like this could create the separation of concerns desired?


get_property: early return when property not found

When property is not found, the testing framework was returning Status::Ok with empty array.
Proxy-wasm-sdk library is reading that as correct return value and returning Ok(Some(Bytes)). The correct branch should be Status::NotFound => Ok(None), when the property is not found. So, fixing the return value from the testing framework.
Here https://github.com/proxy-wasm/proxy-wasm-rust-sdk/blob/v0.2.1/src/hostcalls.rs#L396-L422
pub fn get_property(path: Vec<&str>) -> Result<Option<Bytes>, Status> {
    let serialized_path = utils::serialize_property_path(path);
    let mut return_data: *mut u8 = null_mut();
    let mut return_size: usize = 0;
    unsafe {
        match proxy_get_property(
            serialized_path.as_ptr(),
            serialized_path.len(),
            &mut return_data,
            &mut return_size,
        ) {
            Status::Ok => {
                if !return_data.is_null() {
                    Ok(Some(Vec::from_raw_parts(
                        return_data,
                        return_size,
                        return_size,
                    )))
                } else {
                    Ok(None)
                }
            }
            Status::NotFound => Ok(None),
            status => panic!("unexpected status: {}", status as u32),
        }
    }
}

👍 Nice. Sort of unrelated, but I'm thinking the SDK is wrong in not differentiating between a nil value to an existing property and a non existent prop... I was thinking of raising that with them, as the fn sig is Err = Status, it could return that information rather than discarding of it.


add logging to file feature

The commit has made the following changes

the way csv files is read
bumped version to 1.2

This commit also includes added feature

things are logged to keep-mega-alive.log file
unsuccessful logins are handled properly and logged

My pleasure!
Made changes as suggested, except one.
Also, I have changed the interpreter from sh to bash. I  was having problem with command substitution.


ROX-14689: Operator install tools with go

Description
Currently in operator/ we are downloading tools directly from github. This has some downsides e.g. we are rate limited, dependabot could not update version. In this PR I introduced the same way of installing tools as we use in main directory.
Testing Performed
CI

Current dependencies on/for this PR:

master

PR #4648

PR #4658

PR #4649   👈

This comment was auto-generated by Graphite.

Maybe I just don't know how to use this graphite thing, but this PR seems
to contain much more than what the description says. Please ping me when
it's in a more reviewable state, happy to take a look.

/retest

I think you'll also need to do something about the make -C operator kuttl command in qa-e2e setup...

/retest

Following tests failed. Retest:

RoutesTest: Verify that routes are detected correctly
AdmissionControllerTest: Verify Admission Controller Enforcement on Updates (nginx w/ inline scan)
AdmissionControllerTest: Verify Admission Controller Enforcement on Updates (nginx w/ inline scan)

Following tests failed. Retest:

RoutesTest: Verify that routes are detected correctly

This is unrelated flake tracked elsewhere.

AdmissionControllerTest: Verify Admission Controller Enforcement on Updates (nginx w/ inline scan)
AdmissionControllerTest: Verify Admission Controller Enforcement on Updates (nginx w/ inline scan)

I think these are also unrelated, I'll take a look at these as I'm currently working on improving this test.


Read URLs from a configuration file

📑 I have found these related issues/pull requests
There is a request for an API (Issue #118) but apart from that did not find anything related to a file.
🏷 Feature Request Type
API / automation options, Other
🔖 Feature description
When creating a monitor for a few URLs, the UI is easy. But when that has to be done for a lot it becomes a bit of a problem. I want to import a host of URLs that I want to monitor
✔ Solution
Import or allow reading of a file (csv) with a list of URLs - 1 on each line, with it's configuration mentioned on the same line in a fixed format.
e.g:
URL1, monitor type, name, heartbeat, etc.
URL2, monitor type, name, heartbeat, etc.

Alternatively, use the UI to set the monitoring details and only import the list of URLs that follow that configuration.
❓ Alternatives
No response
📝 Additional Context
No response

This is a duplicate of:

https://github.com/louislam/uptime-kuma/issues/1354
https://github.com/louislam/uptime-kuma/issues/1190

And related to:

https://github.com/louislam/uptime-kuma/issues/956
https://github.com/louislam/uptime-kuma/issues/1323

=> closing as a duplicate


bools are incomparable

The compiler rejects this program:
let x = true;
let y = (false == x);

with this error:
[Type error] [3.16] bool and bool are incomparable. Cannot create a join for construct ==.
let y = (false == x);
               ^

Facepalm

joinOf (in subtyping.scala) needs to have a case for when the types are equal.
@sgpthomas want to take a look at this?


RenameKeyword: add convert_title_case flag to prevent Title Case conversion

we have a use case where we only want RenameKeywords to support keyword deprecation, i.e. to translate old to new keywords via replace_pattern. The automatic title case conversion is not desired as we have not adopted this style in our keyword library. hence suggesting a new flag

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (fc4ab6e) 96.91% compared to head (e71a8d3) 96.91%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #613   +/-   ##
=======================================
  Coverage   96.91%   96.91%
=======================================
  Files          50       50
  Lines        4955     4959    +4
=======================================
+ Hits         4802     4806    +4
  Misses        153      153

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Thanks for the PR! I remember it from our conversation on Slack and it was on my todo list (which I'm currently going over with multiple updates for Robocop & Robotidy) but it certainly helps to receive PR :)


CalendarList getItems() function should return an array instead CalendarListEntry

Hi all,
I'm using Google Calendar Service and extracting all my calendars with getItems() function.
from apiclient-services/src/Google/Service/Calendar/CalendarList.php
 /**
   * @return Google_Service_Calendar_CalendarListEntry
   */
  public function getItems()
  {
    return $this->items;
  }

This function in fact returns an array of CalendarListEntry not a single CalendarListEntry, so it should be
 /**
   * @return Google_Service_Calendar_CalendarListEntry[]
   */

Result of getItems :
array (size=5)
  0 =>
    object(Google_Service_Calendar_CalendarListEntry)[2364]
      protected 'collection_key' => string 'defaultReminders' (length=16)
      public 'accessRole' => string 'reader' (length=6)
      public 'backgroundColor' => string '#b3dc6c' (length=7)
      public 'colorId' => string '10' (length=2)
      .....
  1 =>
    object(Google_Service_Calendar_CalendarListEntry)[2365]
      protected 'collection_key' => string 'defaultReminders' (length=16)
      public 'accessRole' => string 'owner' (length=5)
      public 'backgroundColor' => string '#a47ae2' (length=7)
      public 'colorId' => string '24' (length=2)
    ....
  2 =>
    object(Google_Service_Calendar_CalendarListEntry)[2366]
      protected 'collection_key' => string 'defaultReminders' (length=16)
      public 'accessRole' => string 'owner' (length=5)
      public 'backgroundColor' => string '#fad165' (length=7)
      public 'colorId' => string '12' (length=2)
     ....

Thanks

Duplicate of https://github.com/google/google-api-php-client/issues/443

Thanks for the heads up! This library is autogenerated so we can't make the fix right there in the services code.

ok, so a little question. How people is solving this problem? because i'm fixing vendor classes in my own project but if someone clone it and make a vendor install, there gonna be a lot of errors using that Classes

@elenitaex5, are you just fixing it to get type hinting working in your IDE/editor?


User Story: Login with social media

As a user, I can login with social media, so that I can access the site.
Acceptance Criteria:

User can login via social media
User is logged in after submitting information

Tasks:

[x] Develop login form
[x] Process login request

Delivered in 64241b2


x/pkgsite: in some cases pkg.go.dev does not show the latest version as the latest

What is the URL of the page with the issue?
https://pkg.go.dev/github.com/perillo/go-portable
What is the problem?
Due to an oversight, I tagged version v0.3.0 of github.com/perillo/go-portable without first merging from the develop branch.  The result is that now there are two versions (v0.2.0 and v0.3.0) with the same commit and date.
After merging from develop, I released v0.4.0 but pkg.go.dev still thinks that v0.3.0 is the latest release.  It can be verified at
<EMAIL_ADDRESS> where the version is marked as not at latest.

Looks like this is fixed.


Misc Issues with 0.14.7

Sheard creepers need a name: http://i.imgur.com/uSmQfYZ.png
Single Machines TE's are not named. Thus shows this when using Holoinventory http://imgur.com/dEg6iZp
Broken Craft/Minetweaker integration? http://pastebin.com/pgBiWTaB
Script: http://pastebin.com/QwzBe9x4
Using CraftTweaker: 3.0.20
I'm not sure if you have control over this or not but Tinkers smelting of concentrated hellfire only uses one dust per ingot instead of the 8x dust in the cauldron. Just thought I'd bring that up.

CraftTweaker integration in newer versions requires MTLib to work. I'll add a localized name for sheared creepers, but it looks like HoloInventory doesn't grab the ".name" portion of the localization string for modded blocks. I'll have to see if just generically defining that as "Mechanical Machine" fixes it.
As for the concentrated hellfire, it seems to be something tied to the Ore Dictionary name, I'll probably revert it to "powderedHellfire" instead of "dustHellfire" for the time being.

I will tell dries about the HoloInventory stuff and see what he thinks.
Thanks for the quick reply! I'll keep an eye out for more issues.


upload files with cotntent_type zip and filename without zip give a .zip

The parameter content-type as application/zip and a filename without .zip seems not handled
File pushed with a different name without extension
Use of content_disposition do not give the filename as dl and a mix of target filename with .zip extension.
The usage on a s3 bucket give the correct filename
Scenario
echo test > testfile.txt
zip testfile.test testfile.txt
aws s3 cp --endpoint-url=http://localhost:9444 testfile.test s3://mybucket/123456789 --content-type "application/zip" --content-disposition 'attachment; filename = "testfile.test"'

Now download the file 123456789 from s3 ninja url
http://localhost:9444/ui/mybucket/123456789
Observed output
The downloaded file is 123456789.zip
Expected output
The file expected to be testfile.test or at least 123456789

Hello @hugocarnide 👋 Many thanks for reporting this. Please excuse the late reaction.
Actually, the /ui/ URL is just a User Interface for convenience. It exhibits non-standard behaviour such as the one you witnessed in this case. I agree that the behaviour may be surprising, and that we should consider changing it. However, please note that you should not rely on a certain behaviour of the UI for development, and rather use AWS-S3-like access to your data.

I have created PR #220 for this. During development, I was wondering whether the reported behaviour is browser-specific – I failed to reproduce the condition as described. Still, the PR should solve it for all browsers.


use downcase instead of snake case for attributes

per our discussion in #601
This gets all the specs passing.
There are currently 83 different attributes that use snake case: https://gist.github.com/titusfortner/032d80553aa1ff10061de7eb0fe2919b
The only one this gives special consideration for is :http_equiv. Are we ok with the rest being downcased?

rebased and updated with corrections

nevermind, have more work to do.
Also, Generator is failing on SVG :(

Any easy fixes with the failing SVG generation?

So, there is a bug in current SVG spec. IDL grammar is not valid for ShadowAnimation interface. I've sent an email to SVG W3C mailing list about this problem. but until it's fixed we'll have to edit spec:
sed -i.bak "s/Constructor<\/i> (/Constructor<\/i>(/" support/svg.html

After that, you should be able to generate elements from spec.

All requested changes have been made; before merging it, though...
These are the arguments that are now set to get ignored
%w(cells elements hash rows span text size selected? clear style width height tHead tFoot)
We are using attributes both for custom locators and for custom methods on the applicable elements. I think some of these should be allowed as locators, but not as methods, not entirely removed from html_elements.rb.
This PR is better code than what we have now, so I'll push forward on it, assuming you don't see any issues with it on your next look. But I still wanted to get your opinion on changing it again. :)

FTR, here is an email I've sent to SVG working group to address the problem with IDL interface: https://lists.w3.org/Archives/Public/www-svg/2017Aug/0005.html.

merged


Add timelock to output purpose

For staking (and also vesting) we need to be able to make outputs unspendable for a given period of time. This similar to bitcoin timelocks, but it's not implemented at the script level.

Added some comments.
In addition to that, I think it would be nice to see this mechanism used for block reward maturity too. Just let consensus rules enforce that the reward outputs have the appropriate time lock on them. It seems like a nice design to have the same mechanism deal with all these time-locky things. However this would deviate from Bitcoin somewhat so may not be exactly what the devs expect.

It's part of the plan. All in good time. We'll have to asses all options once PoS works.

I have merged master to this branch. Everything vent smoothly and I only needed to fix tests after that, but please take a look anyway.


[8.x] Add timestamps to model save options

This PR adds disable timestamps option to model save function.
A sample code before this change:
// updating model without touching updated_at
$user->name = 'new name';
$user->timestamps = false;
$user->save();
$user->timestamps = true;

Same code after this change:
$user->name = 'new name';
$user->save(['timestamps' => false]);

Or using update:
$user->update(['name ' => 'new name'], ['timestamps' => false]);

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

FYI this was once attempted in Laravel years ago but it ended up being removed because it didn't cover every edge case:  https://github.com/laravel/framework/pull/12617 (https://github.com/laravel/framework/pull/12403#issuecomment-190753867)
If you don't wish to update timestamps on model relationships, the (currently undocumented) Model::withoutTouching() method may be what you want: https://github.com/laravel/framework/pull/23469
From your code sample above updating a single model, userland can accomplish this by adding a method to the Model class.
namespace App\Models;

use Illuminate\Database\Eloquent\Model as BaseModel;

class Model extends BaseModel
{
    public function keepingTimestamps(callable $callback)
    {
        try {
            $timestamps = $this->timestamps;
            $this->timestamps = false;

            return tap($this, $callback);
        } finally {
            $this->timestamps = $timestamps;
        }
    }
}

App model classes will extend App\Models\Model instead of Illuminate\Database\Eloquent\Model. Or if only one model needs this behavior, define this method in that class.
optional($request->user()->latestMessage)->keepingTimestamps(
    fn ($message) => $message->update(['read_at' => now()])
);

See #43441


Cannot use "OR" function

See my relationship criteria below.
(status__c IN ('Active', 'Active - pending end') AND avtrrt__start_date__c != THIS_WEEK) OR (status__c IN ('Active', 'Active - pending end') AND avtrrt__end_date__c = LAST_WEEK)
Error: Relationship Criteria '(status__c IN ('Active', 'Active - pending end') AND avtrrt__start_date__c != THIS_WEEK) OR (status__c IN ('Active', 'Active - pending end') AND avtrrt__end_date__c = LAST_WEEK)' is not valid, see SOQL documentation http://www.salesforce.com/us/developer/docs/soql_sosl/Content/sforce_api_calls_soql_select_conditionexpression.htm, error is 'unexpected token: OR'

@girlyITgeek I tested your criteria, adapted to my own org, inside the Developer Console and it ran OK.
select id from case where (status IN ('New', 'Closed') AND CreatedDate != THIS_WEEK) OR (status IN ('New', 'Closed') AND CreatedDate = LAST_WEEK)
Could you write something similar that will run OK in your Developer Console, or another SOQL tool, and paste it back here with screenshots of your rollup? I don't know what could be wrong but maybe we'll figure it out by seeing the whole picture.
Thanks.

I think you might need to wrap the whole thing in another set of parentheses.

Thank you wes1278!!! That worked.

No problem @girlyITgeek! Glad it works. @aheber, SOQL is a little smarter when it's not being injected from a string like we're doing with this tool.  :)


move to the right

How i can move items to the right?
my desire app is like this:
http://i.stack.imgur.com/yAMSN.gif
thanks

hope to solve ur problem
https://thinkandroid.wordpress.com/2010/01/14/how-to-position-views-properly-in-layouts/


[ionic v4] ion-back-button defaultHref is not interpreted as relative route

Bug Report
Ionic Info
Run ionic info from a terminal/cmd prompt and paste the output below.

Ionic:
   ionic (Ionic CLI)          : 4.1.1 (/usr/local/lib/node_modules/ionic)
   Ionic Framework            : @ionic/angular 4.0.0-beta.7
   @angular-devkit/core       : 0.7.5
   @angular-devkit/schematics : 0.7.5
   @angular/cli               : 6.1.5
   @ionic/ng-toolkit          : 1.0.7
   @ionic/schematics-angular  : 1.0.5

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : none
   Cordova Plugins       : no whitelisted plugins (0 plugins total)

System:

   Android SDK Tools : 26.1.1 (/Users/jurgen-visser/Library/Android/sdk)
   ios-deploy        : 1.9.2
   NodeJS            : v8.11.3 (/usr/local/bin/node)
   npm               : 5.6.0
   OS                : macOS High Sierra
   Xcode             : Xcode 9.4.1 Build version 9F2000

Describe the Bug
When I set defaultHref to a relative path e.g. defaultHref="../page" the router doesn't seem to resolve it as a relative path from the route that I'm currently in. I've found similar strange behaviour with hrefs and routerLinks in other components.
Steps to Reproduce
Steps to reproduce the behavior:

create a ion-toolbar with ion-back-button that has defaultHref set
<ion-back-button defaultHref="../page"></ion-back-button>
click it
See error: Cannot match any routes. URL Segment: '../page'

Expected Behavior
I expect the router to try and determine the path relative to the current route. This is an absolutely essential feature, because my current route may have id's in it that I don't want to have to explicitly print in the defaultHref or other href fields.

that was fast!


Add worker-threads-pool to external pools benchmarks

The behaviour of that pool seems weird to me, so please test it.
Signed-off-by: Jérôme Benoit<EMAIL_ADDRESS>
PR Checklist

[x] Please add a description of your changes.
[ ] We need your changes to come with unit tests in order to keep this project in quality and easy to maintain.
[ ] If your changes contain any new feature please be sure to document it.
[ ] Please add a link to the open issue or task that this pull request will resolve.
[ ] Add a note to the changelog to indicate the change.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If yes please indicate it and migration info into the CHANGELOG.md file.

Approved from my side, awaiting approval from @pioardi
The you can merge it :+1:


TwitchAPI not working with mono?

The error I get: All API calls require Client-Id or OAuth token. Set Client-Id by using SetClientId("client_id_here")
But I only get that if I use it with mono on my linux server (running openSUSE). It works totally fine when I'm testing it on my windows machine. I am setting the client id and access token.

I actually run a couple of twitch bots with the library on mono. They run on the AWS Linux AMI image. So, I'm certain it works fine on mono, at least on that distro. What you can try doing (and assuming that you are in fact setting the client id), is setting:
TwitchAPI.Settings.Validators.SkipClientIdValidation = true;

Also, perhaps way out in left field, but are you loading your credentials via a textfile or something and perhaps that doesn't exist on your production linux instance?

Btw I'm trying to get clip info with
TwitchLib.Models.API.v5.Clips.Clip clip = await TwitchAPI.Clips.GetClip(slug);
I tried setting the value you mentioned to true and it's a different error from the exception now. Again it still completely works on my windows machine, the error on the linux machine is:
The requested feature is not implemented.   at System.Net.WebRequest.CreateHttp (System.String requestUriString) [0x00000] in <filename unknown>:0   at TwitchLib.Internal.Requests+<generalRequest>d__12.MoveNext () [0x00000] in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0   at System.Runtime.CompilerServices.TaskAwaiter1[TResult].GetResult () [0x00000] in :0
at TwitchLib.Internal.Requests+d__51[TwitchLib.Models.API.v5.Clips.Clip].MoveNext () [0x00000] in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0   at System.Runtime.CompilerServices.TaskAwaiter1[TResult].GetResult () [0x00000] in :0
at TwitchLib.Internal.TwitchAPI.v5+d__15.MoveNext () [0x00000] in :0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in :0
at System.Runtime.CompilerServices.TaskAwaiter1[TResult].GetResult () [0x00000] in <filename unknown>:0   at TwitchLib.TwitchAPI+Clips+<GetClip>d__0.MoveNext () [0x00000] in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0   at System.Runtime.CompilerServices.TaskAwaiter1[TResult].GetResult () [0x00000] in :0
at TwitchBot.TwitchChat+d__9.MoveNext () [0x00000] in :0
`

So that seemed to be a bug with an older version of mono. Updating to the latest version fixed the issue, I thought I was on the latest but there was some issue with my repositorys being outdated with openSUSE. Issue is resolved now though. Thanks

I was just going to say, the only time I've seen that error is with older versions of mono. Glad you got it figured out, hopefully. Cheers :)

Going to close this, if you're still hitting issues, feel free to reopen it.

TwitchAPI.Settings.Validators.SkipClientIdValidation = true;
This worked for me as i had similar issue - it did not let me set UserId and OAuthToken - exeptions were thrown and those properties in settings were still empty.
I have all packets up to date.

What exceptions were you getting with that setting disabled?

I got same (unhandled) exception as baffler - All API calls require Client-Id or OAuth token. Set Client-Id by using SetClientId("client_id_here")
Couple handled exceptions earlier, but the fields stays null. With this setting it works like charm and settings fields are filled correctly.


The violation error message doesn't perfectly match the rule class name

Feature Request

Q
A

New Feature
yes

RFC
yes

BC Break
no

Summary

The violation error message doesn't perfectly match the rule class name
Example:
'should not depend on classes outside in namespace' vs NotHaveDependencyOutsideNamespace(...)
I think it would be better to print:
'not have dependency outside namespace'

Fixed by #211
Thanks!


With v1beta1 node names has changed to ip-x-x-x-x.ec2.internal instead of karpenter.sh/xxx

Description
Observed Behavior:
Karpenter spins new nodes with names like ip-x-x-x-x.ec2.internal
Expected Behavior:
Names like karpenter.sh/provisioner/<name> or karpenter.sh/nodepool/<nodepool-name>
Reproduction Steps (Please include YAML):
install karpenter v32+ and use v1beta1
Versions:

Chart Version: "v0.32.1"
Kubernetes Version (kubectl version):

Client Version: v1.28.3
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.2-eks-f8587cb

I checked source code here: karpenter/pkg/providers/instance/instance.go
func getTags(ctx context.Context, nodeClass *v1beta1.EC2NodeClass, nodeClaim *corev1beta1.NodeClaim) map[string]string {
	var overridableTags, staticTags map[string]string
	if nodeClaim.IsMachine {
		overridableTags = map[string]string{
			"Name": fmt.Sprintf("%s/%s", v1alpha5.ProvisionerNameLabelKey, nodeClaim.Labels[v1alpha5.ProvisionerNameLabelKey]),
		}
		staticTags = map[string]string{
			fmt.Sprintf("kubernetes.io/cluster/%s", options.FromContext(ctx).ClusterName): "owned",
			v1alpha5.ProvisionerNameLabelKey:                                              nodeClaim.Labels[v1alpha5.ProvisionerNameLabelKey],
			v1alpha5.MachineManagedByAnnotationKey:                                        options.FromContext(ctx).ClusterName,
		}
	} else {
		staticTags = map[string]string{
			fmt.Sprintf("kubernetes.io/cluster/%s", options.FromContext(ctx).ClusterName): "owned",
			corev1beta1.NodePoolLabelKey:       nodeClaim.Labels[corev1beta1.NodePoolLabelKey],
			corev1beta1.ManagedByAnnotationKey: options.FromContext(ctx).ClusterName,
			v1beta1.LabelNodeClass:             nodeClass.Name,
		}
	}
	return lo.Assign(overridableTags, settings.FromContext(ctx).Tags, nodeClass.Spec.Tags, staticTags)
}

And looks like there is no Name tag override for v1beta1.
I also tried to set Name in EC2NodeClass like this:
  tags:
    Name: karpenter.sh/nodepool/%nodepool-name%

  tags:
    Name: karpenter.sh/nodepool/$nodepool-name

  tags:
    Name: karpenter.sh/nodepool/${nodepool-name}

  tags:
    Name: karpenter.sh/nodepool/<nodepool-name>

But no luck. How can I set names for new instance to be karpenter.sh/nodepool/<nodepool-name> ?

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

what about to do it like this:
func getTags(ctx context.Context, nodeClass *v1beta1.EC2NodeClass, nodeClaim *corev1beta1.NodeClaim) map[string]string {
	var overridableTags, staticTags map[string]string
	if nodeClaim.IsMachine {
		overridableTags = map[string]string{
			"Name": fmt.Sprintf("%s/%s", v1alpha5.ProvisionerNameLabelKey, nodeClaim.Labels[v1alpha5.ProvisionerNameLabelKey]),
		}
		staticTags = map[string]string{
			fmt.Sprintf("kubernetes.io/cluster/%s", options.FromContext(ctx).ClusterName): "owned",
			v1alpha5.ProvisionerNameLabelKey:                                              nodeClaim.Labels[v1alpha5.ProvisionerNameLabelKey],
			v1alpha5.MachineManagedByAnnotationKey:                                        options.FromContext(ctx).ClusterName,
		}
	} else {
		overridableTags = map[string]string{
			"Name": fmt.Sprintf("%s/%s", corev1beta1.NodePoolLabelKey, nodeClaim.Labels[corev1beta1.NodePoolLabelKey]),
		}
		staticTags = map[string]string{
			fmt.Sprintf("kubernetes.io/cluster/%s", options.FromContext(ctx).ClusterName): "owned",
			corev1beta1.NodePoolLabelKey:       nodeClaim.Labels[corev1beta1.NodePoolLabelKey],
			corev1beta1.ManagedByAnnotationKey: options.FromContext(ctx).ClusterName,
			v1beta1.LabelNodeClass:             nodeClass.Name,
		}
	}
	return lo.Assign(overridableTags, settings.FromContext(ctx).Tags, nodeClass.Spec.Tags, staticTags)
}

@wiseelf This is documented as changed behavior as part of the v1beta1 migration.
Just curious: What's the reason that you want the old naming? From what we understand from users, having the node name be the Name tag on the instance would be helpful to a lot of users. You can still look up the karpenter.sh/nodepool through the tags, which you should be able to see Karpenter-managed nodes.

@jonathan-innis that is visually better when we need to do something in aws console. I can easily identify exact nodes I need just by seeing their name.
previously I had them like this:
karpenter.sh/provisioner-name/nodes-group-1
karpenter.sh/provisioner-name/nodes-group-2
karpenter.sh/provisioner-name/nodes-group-3

Right now they all the same, and I need to specify the tag exactly to filter them.
I can do that through the tags the only how can I pass nodepool name in the tag?
apiVersion: karpenter.k8s.aws/v1beta1
kind: EC2NodeClass
metadata:
  name: tedt
spec:
  amiFamily: Bottlerocket
  tags:
     Name: karpenter.sh/nodepool/%nodepool-name%

Right now they all the same, and I need to specify the tag exactly to filter them

I'm not quite getting that. How are they all the same? Shouldn't their names differ by their node name? Or are you saying that they all look similar so it's hard to differentiate between which nodes are owned by one nodepool or another?
karpenter.sh/nodepool name is automatically tagged on the instances. You shouldn't need to do anything additional to get that tag onto the instance.

I'm not quite getting that. How are they all the same? Shouldn't their names differ by their node name? Or are you saying that they all look similar so it's hard to differentiate between which nodes are owned by one nodepool or another?

They all look similar ip-x-x-x-x.ec2.internal, so to filter only selecter nodepool I need to add filter like this

Also it is hard to identify instances that are managed by karpenter from a regular instances, because they all have the same name.

karpenter.sh/nodepool name is automatically tagged on the instances. You shouldn't need to do anything additional to get that tag onto the instance.

Yes, instances have that tag, but I want it to be a name of the instance. To achieve that I need to set tag Name to karpenter.sh/nodepool/$nodepool-name
How can I do that?

You can overwrite the Name tag in the EC2NodeClass, but Karpenter doesn't have support for dynamic tag names (related issue: #4228). Without dynamic tags names you wouldn't be able to set the Name to the node pool name but you would be able to set it to any other static string (e.g. you could set it to the EC2NodeClass name or just "karpenter node"). IIUC you're main concern is being able to easily differentiate Karpenter nodes at a glance so would this fit your use case?

@snorlaX-sleeps It's the note under AWSNodeTemplate -> EC2NodeClass in the v1beta1 migration guide. Maybe the wording could be more clear, it doesn't specifically call out its the Name tag.


S3 static file serving/Django-pipeline & Compressing with Yugilfy

S3 static file serving integration with Django-pipeline & Compressing with Yugilfy for Prod env's

Coverage decreased (-1.22%) to 48.24% when pulling 77d710bde9700a40ea5eb6c0342b1e731fdd873a on kave:master into dbda218533b8bd0cf4496d8001968bbd8559f5aa on excellaco:master.

This is great!


Update JFXTreeTableColumn.java

Added setPercentageWidth

Hello,
your code is forcing pref width binding regardless whether the percentage width is set or not.
Sorry can't accept this PR, it could be implemented better.
Regards,


Internet Explorer 3.02

Website not working on my windows NT

me too please fix

fix

please

AH


N04: Gas optimization possible in ReentrancyGuard.sol

Description
Use Zeppelin's ReentrancyGuard contract to get better gas optimization. Copy and pasted due to version incompatibility
Other changes
n/a
Tested
everything should continue working as expected

Fixes https://github.com/celo-org/celo-labs/issues/616

Backwards compatibility
yes

This makes a huge storage change so I must close this. RIP


fix QnA access levels, fix #2800, fix style

Fixes #2800
Description
Turn JoinOperator into an enum and make it public, fix QnAMaker exports
Specific Changes

Make ActiveLearningUtils public from qnamaker-utils/
Make QnAResponseContext and JoinOperator public from qnamaker-interfaces/
Change JoinOperator to enum, rename file from JoinOperator.ts to joinOperator.ts
Cleanup exports for QnAMaker (make exports more explicit)

Pull Request Test Coverage Report for Build 169744

19 of 19 (100.0%)  changed or added relevant lines in 4 files are covered.
9 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.06%) to 83.341%

Files with Coverage Reduction
New Missed Lines
%

libraries/botframework-streaming/src/webSocket/webSocketTransport.ts
2
81.55%

libraries/botframework-streaming/src/webSocket/webSocketServer.ts
7
66.67%

Totals

Change from base Build 169723:
-0.06%

Covered Lines:
15588

Relevant Lines:
17786

💛  - Coveralls


distributed mxnet is too slow when parameter size are increased

As input are sparse feature, the total parameters are 1.3G , the speed of distributed trainning are too slow.So mxnet can't support large parameters?

https://github.com/dmlc/mxnet/issues/5498 sparse tensor is in development

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!


Added first news item, and news page

Dropped the Hello World news item, and replaced it with a news item about the participant poll.
However, I am unsure that things are optimal.  In particular, I am confused by the relationships between latest-news, posts, and blog.  It works, but it ain't warm and fuzzy.

Thanks @denis-yuen.  I'll merge.


Updated the development environment setup guide

Q
A

content fix?
yes

New article?
no

Related issues?
n/a

What's in this Pull Request?
Fixed typos and updated the development environment setup guide

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/spfx/set-up-your-development-environment.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thx Waldek.


Inline ignore for files

Our use-case is a large lerna mono-repo with a number of packages each generating nested index files. Although ctix already provides .ctixignore, it would be extremely handy if we could indicate at the top of a file to ignore exporting it in the generated index:
/* ctix ignore */
There may be a use-case for being able to embed this at the export level (if you have files with multiple exports and some should be in the index and others shouldn't), but I think a simple one-off directive at the top of a file is probably "good enough". Curious what the feasibility of a feature like this is, and if the use-case seems broad enough to support it.

@hallister, That's good idea. However, I'm working on another project right now, os I can't update right now. If you issue a PR, I can review it. Thank you for your feedback!

@hallister Hi,
I was working on ctix 2.x. The 2.x version now allows you to set include, exclude directly without using the .ctiignore file, or use the include, exclude in the tsconfig.json file. I was also made improvements to allow you to exclude files or export statements with comments you've suggested.
Please see the documentation I was put together on inline exclude. Barring any special bugs, I will be releasing version 2.x next week. Thank you for your feedback in making ctix better.

That feature was added in version 2.0


Extract :buildProfile subproject from :core

Green build: https://builds.gradle.org/viewLog.html?buildId=17499169&buildTypeId=Gradle_Check_Stage_ReadyforMerge_Trigger


[Good Issue First] Unable to add new organization using script "addOrg3.sh"

I am using fabric-samples -> test-network to establish the hyperledger fabric network.
The following error comes up when trying to add a new organization to the existing running hyperledger fabric network.
Bringing up Org3 peer
ERROR: .FileNotFoundError: [Errno 2] No such file or directory: './docker/docker-compose-org3.yaml'
ERROR !!!! Unable to start Org3 network

Environment:
Windows 11 OS
WSL2 - Ubuntu
Fabric Samples - Latest version: 2.2.4

@parhampr thanks for raising, this issue should now be fixed


Upcoming

Forgot to add a description. This PR is to touch on and improve the PlayerAnnounce hook a bit

closing off for now.
if this is still needed, id suggest creating a new branch from the upcoming branch and making fresh changes on top of that.
once done PR in with full detail to outline the issue, so i can test and confirm your code.


Compliant with Government of Canada “Standard on Web Accessibility” (i.e. WCAG 2.0)

https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=23601

Duplicate


VAE example is no longer valid

I followed this example and it now requires a call() method in keras.Model.
Not working:
https://keras.io/examples/generative/vae/
Working:
https://www.tensorflow.org/guide/keras/custom_layers_and_models
After calling fit ...
NotImplementedError: in user code:
anaconda3/lib/python3.8/site-packages/keras/engine/training.py:1330 test_function  *
return step_function(self, iterator)
anaconda3/lib/python3.8/site-packages/keras/engine/training.py:1320 step_function  **
outputs = model.distribute_strategy.run(run_step, args=(data,))
anaconda3/lib/python3.8/site-packages/tensorflow/python/distribute/distribute_lib.py:1286 run
return self._extended.call_for_each_replica(fn, args=args, kwargs=kwargs)
anaconda3/lib/python3.8/site-packages/tensorflow/python/distribute/distribute_lib.py:2849 call_for_each_replica
return self._call_for_each_replica(fn, args, kwargs)
anaconda3/lib/python3.8/site-packages/tensorflow/python/distribute/distribute_lib.py:3632 _call_for_each_replica
return fn(*args, **kwargs)
anaconda3/lib/python3.8/site-packages/keras/engine/training.py:1313 run_step  **
outputs = model.test_step(data)
anaconda3/lib/python3.8/site-packages/keras/engine/training.py:1267 test_step
y_pred = self(x, training=False)
lib/python3.8/site-packages/keras/engine/base_layer.py:1037 call
outputs = call_fn(inputs, *args, **kwargs)
anaconda3/lib/python3.8/site-packages/keras/engine/training.py:446 call  **
raise NotImplementedError('When subclassing the Model class, you should '
NotImplementedError: When subclassing the `Model` class, you should implement a `call` method.

I was able to successfully execute the tutorial as is from the colab gist given on the top.
Also there is TF implementation for convolutional variational  autoencoder you may find useful.


FTX Exchange implementation

Hi,
Is anyone looking at implementing the rapidly growing ftx exchange ?
https://ftx.com/futures
FTX seems to have quite a lot of unique contract names, to start with I am thinking of supporting their quarterly and semiannual futures as a starting point.
Unlike other exchanges you can only get the poll by the expiry such as https://ftx.com/api/futures/BTC-0327 for the semiannual contract or https://ftx.com/api/futures/BTC-1227 for the quarterly. As such I am wondering if we could use the existing convention of BTC.USD.THIS_QUARTER and BTC.USD.NEXT_QUARTER and have a helper that generates the last Friday of the current quarter and last Friday of next quarter based on the current date i.e from 14/10/2019 the helper would create 27-12-2019 as the last Friday of current quarter and 37-03-2020 for the last Friday of next quarter, which can then be used in the rest request to get the futures trade data via GET https://ftx.com/api/markets/BTC-1227/trades?limit=100 as something like GET https://ftx.com/api/markets/BTC-USD-QUARTER/trades?limit=100 is not supported on ftx's API.

This can be closed as an implementation exists now


[ATLAS-3923]: fix NullPointException in HBaseBasedAuditRepository.listEventsV2

fix NullPointException in HBaseBasedAuditRepository.listEventsV2

Apache JARA: https://issues.apache.org/jira/browse/ATLAS-3923

Thanks  @zyyBjtu for PR, It looked good. I have merged it.


Adventure Map Interactive Blocks not working

Players are unable to activate the use effect of certain blocks in the adventure map that you would be able to expect them to; While the players can use Stair sitting, Half Slab sitting, PCs, Healers, Enchanting Tables, and Enderchests, players are unable to interact with seemingly everything else. Including blocks such as normal chests I believe players used to be able to interact with before. The immediate issue is that this makes crafting in the adventure map impossible for 3x3 crafting. (also Anvils do not work despite Enchanting Tables functioning properly)
(comedically making crafting a pay2play feature in the tier 3 store rank in the adventure realm layer specifically)
A similar error to this occurs when trying to interact with every use block.

Still an issue!  Needs to be migrated to Internal tracker!

Forwarded to the Internal tracker! Will update here when fixed!

Fixed, thanks for the report! Closing


feat: update postcss version to 8, and migrate plugin to fit that version

feat: update postcss version to 8, and migrate plugin to fit that version

没人维护了吗


Allow for Building on Linux with Dark Haxx™

What I've done is simply translating the batch commands to their sh equivalents, a tedious task that I'd never get my hands on manually, thx Copilot!
This is a very primitive attempt of building The Archive on Linux(and possibly other Unix-like OSes, provided .NET SDK, and coreutils-or-equivalent are installed). As changes to Windows batchfiles are included, this "patch" needs to be tested on Windows to see whether the formatting messes with VS.
As such, the process is no longer automated by VS, dependency resolution(a la dotnet restore) has to be done manually with each submodule before building, the following procedure is concluded:

run dotnet restore --force /property:Configuration=R_xx(with R_xx your desired modloader) for TheArchive_Core, TheArchive_IL2CPP, and TheArchive_MONO. No need for BuildHelper it seems, as it helps itself out. Pretty helpful BuildHelper!
then run dotnet build --configuration R_xx under the root. Again with R_xx your desired modloader.
Profit??
I have tested the produced binary and it seems to be running well on my machine, I hope anybody out there could help with this PR, XOXO <3

Just tried it out on my Linux system, can confirm it builds correctly! Thanks for making it work, I attempted it before and it was a real headache.


Rename members to match naming styles

tag @dotnet/project-system

There are many more instances in the solution and also in the same file. Either we change everything or just leave them. Fixing them partially is going to result in more naming styles

I went through and changed all the m_ ones.


Add proposed Sepolia Capella epoch

Proposed based on the conversation in https://github.com/ethereum/pm/issues/711
Epoch 56832 / Slot 1818624 is both a sync committee and historical roots boundary. ETA: 2/28/2023, 4:04:48 AM UTC

On protest, but given the boundary condition that we decided to go with the fork anyway, the epoch is :+1:

Looks good to me 👍

Looks good

At the time of updating, what should I do as I'm running a few Sepolia test net nodes. download the new Sepolia image?

Yes, from a node runner perspective - all you need to do is update to the latest release of the client you are using


operator aqua-operator-certified (2022.4.517)

/ok-to-test

/pipeline restart operator-hosted-pipeline

/test skip check_pruned_graph

/pipeline restart operator-hosted-pipeline


The editor delete "newline symbol"

well, a picture may be more obvious
before

after

Thanks for the report. A fix will be pushed soon.


focus_manager should check for debugPrintKeyboardEvents for logging key events

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Use case
In focus_manager.dart, key events are logged in _focusDebug checking if debugFocusChanges is true. This generates a lot of undesired output if I'm only interested in key events.
There is a debugPrintKeyboardEvents flag, but when set, there isn't output indicating whether the key event was handled. This output is generated when debugFocusChanges is true.
To confirm, run the following code and press any key:
Code sample
import 'package:flutter/material.dart';

void main() {
  debugFocusChanges = true;
  runApp(MaterialApp(
    home: Scaffold(body: SizedBox()),
  ));
}

Proposal
Check for debugPrintKeyboardEvents when logging key events instead of debugFocusChanges.

CC @Renzo-Olivares  @justinmc

@gspencergoog Do you have any opinions on this?


ajax.reload() do not respond when using ajax option

When you use the new ajax option (http://datatables.net/reference/option/ajax) the ajax.reload() function does not work appropriately.
First example (not working): http://jsfiddle.net/cru97z69/
But when you use the legacy sAjaxSource option (http://legacy.datatables.net/usage/server-side) the ajax.reload() function work normally.
Second example (working): http://jsfiddle.net/cp3hd8pv/1/
The same bug is reproducible with ajax.url().load() function.

Looking at debug information, the data is being loaded from the server, so the problem is when reload call the callback (?)

I think the problem is that when you use the ajax option of DataTables 1.10 it sends the server-side processing request with different (camelCase) parameters from the old style 1.9- legacy parameters. The result is that your server-side processing script is returning the draw counter as 1 always.
If you enable the legacy mode it works okay: http://jsfiddle.net/cru97z69/1/ .
See the docs for more information about the new and legacy modes.


⚠ Bofrost.fr has degraded performance

In 5ff139d, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1038 ms

Resolved: Bofrost.fr performance has improved in 1abd17d after 8 minutes.


🐛 Bug Report: microsoft authenticator not working

📜 Description
After upgrade from 1.25 to 1.29, microsoft authenticator not working.
👍 Expected behavior
SSO login works.
👎 Actual Behavior with Screenshots
SSO login not working, always ask said "Approval required".
👟 Reproduction steps
follow official guide. debug localy.
📃 Provide the context for the Bug.
auth:
  environment: development
  providers:
    microsoft:
      development:
        clientId: ******
        tenantId: ******
        clientSecret: ******
        additionalScopes:
          - Mail.Send
        signIn:
          resolvers:
            - resolver: emailMatchingUserEntityProfileEmail

🖥 Your Environment
OS:   Darwin 23.5.0 - darwin/arm64
node: v18.20.3
yarn: 3.8.1
cli:  0.26.11 (local)
backstage:  N/A

Dependencies:
  @backstage/app-defaults                                            0.0.0-use.local
  @backstage/backend-app-api                                         0.0.0-use.local
  @backstage/backend-common                                          0.0.0-use.local
  @backstage/backend-defaults                                        0.0.0-use.local
  @backstage/backend-dev-utils                                       0.0.0-use.local
  @backstage/backend-dynamic-feature-service                         0.0.0-use.local
  @backstage/backend-openapi-utils                                   0.0.0-use.local
  @backstage/backend-plugin-api                                      0.0.0-use.local
  @backstage/backend-tasks                                           0.0.0-use.local
  @backstage/backend-test-utils                                      0.0.0-use.local
  @backstage/catalog-client                                          0.0.0-use.local
  @backstage/catalog-model                                           0.0.0-use.local
  @backstage/cli-common                                              0.0.0-use.local
  @backstage/cli-node                                                0.0.0-use.local
  @backstage/cli                                                     0.0.0-use.local
  @backstage/codemods                                                0.0.0-use.local
  @backstage/config-loader                                           0.0.0-use.local
  @backstage/config                                                  0.0.0-use.local
  @backstage/core-app-api                                            0.0.0-use.local
  @backstage/core-compat-api                                         0.0.0-use.local
  @backstage/core-components                                         0.0.0-use.local, 0.13.10
  @backstage/core-plugin-api                                         0.0.0-use.local
  @backstage/create-app                                              0.0.0-use.local
  @backstage/dev-utils                                               0.0.0-use.local
  @backstage/e2e-test-utils                                          0.0.0-use.local
  @backstage/errors                                                  0.0.0-use.local
  @backstage/eslint-plugin                                           0.0.0-use.local
  @backstage/frontend-app-api                                        0.0.0-use.local
  @backstage/frontend-plugin-api                                     0.0.0-use.local
  @backstage/frontend-test-utils                                     0.0.0-use.local
  @backstage/integration-aws-node                                    0.0.0-use.local
  @backstage/integration-react                                       0.0.0-use.local
  @backstage/integration                                             0.0.0-use.local
  @backstage/plugin-api-docs-module-protoc-gen-doc                   0.0.0-use.local
  @backstage/plugin-api-docs                                         0.0.0-use.local
  @backstage/plugin-app-backend                                      0.0.0-use.local
  @backstage/plugin-app-node                                         0.0.0-use.local
  @backstage/plugin-app-visualizer                                   0.0.0-use.local
  @backstage/plugin-auth-backend-module-atlassian-provider           0.0.0-use.local
  @backstage/plugin-auth-backend-module-aws-alb-provider             0.0.0-use.local
  @backstage/plugin-auth-backend-module-azure-easyauth-provider      0.0.0-use.local
  @backstage/plugin-auth-backend-module-bitbucket-provider           0.0.0-use.local
  @backstage/plugin-auth-backend-module-cloudflare-access-provider   0.0.0-use.local
  @backstage/plugin-auth-backend-module-gcp-iap-provider             0.0.0-use.local
  @backstage/plugin-auth-backend-module-github-provider              0.0.0-use.local
  @backstage/plugin-auth-backend-module-gitlab-provider              0.0.0-use.local
  @backstage/plugin-auth-backend-module-google-provider              0.0.0-use.local
  @backstage/plugin-auth-backend-module-guest-provider               0.0.0-use.local
  @backstage/plugin-auth-backend-module-microsoft-provider           0.0.0-use.local
  @backstage/plugin-auth-backend-module-oauth2-provider              0.0.0-use.local
  @backstage/plugin-auth-backend-module-oauth2-proxy-provider        0.0.0-use.local
  @backstage/plugin-auth-backend-module-oidc-provider                0.0.0-use.local
  @backstage/plugin-auth-backend-module-okta-provider                0.0.0-use.local
  @backstage/plugin-auth-backend-module-onelogin-provider            0.0.0-use.local
  @backstage/plugin-auth-backend-module-pinniped-provider            0.0.0-use.local
  @backstage/plugin-auth-backend-module-vmware-cloud-provider        0.0.0-use.local
  @backstage/plugin-auth-backend                                     0.0.0-use.local
  @backstage/plugin-auth-node                                        0.0.0-use.local
  @backstage/plugin-auth-react                                       0.0.0-use.local
  @backstage/plugin-bitbucket-cloud-common                           0.0.0-use.local
  @backstage/plugin-catalog-backend-module-aws                       0.0.0-use.local
  @backstage/plugin-catalog-backend-module-azure                     0.0.0-use.local
  @backstage/plugin-catalog-backend-module-backstage-openapi         0.0.0-use.local
  @backstage/plugin-catalog-backend-module-bitbucket-cloud           0.0.0-use.local
  @backstage/plugin-catalog-backend-module-bitbucket-server          0.0.0-use.local
  @backstage/plugin-catalog-backend-module-gcp                       0.0.0-use.local
  @backstage/plugin-catalog-backend-module-gerrit                    0.0.0-use.local
  @backstage/plugin-catalog-backend-module-github-org                0.0.0-use.local
  @backstage/plugin-catalog-backend-module-github                    0.0.0-use.local
  @backstage/plugin-catalog-backend-module-gitlab-org                0.0.0-use.local
  @backstage/plugin-catalog-backend-module-gitlab                    0.0.0-use.local
  @backstage/plugin-catalog-backend-module-incremental-ingestion     0.0.0-use.local
  @backstage/plugin-catalog-backend-module-ldap                      0.0.0-use.local
  @backstage/plugin-catalog-backend-module-logs                      0.0.0-use.local
  @backstage/plugin-catalog-backend-module-msgraph                   0.0.0-use.local
  @backstage/plugin-catalog-backend-module-openapi                   0.0.0-use.local
  @backstage/plugin-catalog-backend-module-puppetdb                  0.0.0-use.local
  @backstage/plugin-catalog-backend-module-scaffolder-entity-model   0.0.0-use.local
  @backstage/plugin-catalog-backend-module-unprocessed               0.0.0-use.local
  @backstage/plugin-catalog-backend                                  0.0.0-use.local
  @backstage/plugin-catalog-common                                   0.0.0-use.local
  @backstage/plugin-catalog-graph                                    0.0.0-use.local
  @backstage/plugin-catalog-import                                   0.0.0-use.local
  @backstage/plugin-catalog-node                                     0.0.0-use.local
  @backstage/plugin-catalog-react                                    0.0.0-use.local
  @backstage/plugin-catalog-unprocessed-entities-common              0.0.0-use.local
  @backstage/plugin-catalog-unprocessed-entities                     0.0.0-use.local
  @backstage/plugin-catalog                                          0.0.0-use.local
  @backstage/plugin-config-schema                                    0.0.0-use.local
  @backstage/plugin-devtools-backend                                 0.0.0-use.local
  @backstage/plugin-devtools-common                                  0.0.0-use.local
  @backstage/plugin-devtools                                         0.0.0-use.local
  @backstage/plugin-events-backend-module-aws-sqs                    0.0.0-use.local
  @backstage/plugin-events-backend-module-azure                      0.0.0-use.local
  @backstage/plugin-events-backend-module-bitbucket-cloud            0.0.0-use.local
  @backstage/plugin-events-backend-module-gerrit                     0.0.0-use.local
  @backstage/plugin-events-backend-module-github                     0.0.0-use.local
  @backstage/plugin-events-backend-module-gitlab                     0.0.0-use.local
  @backstage/plugin-events-backend-test-utils                        0.0.0-use.local
  @backstage/plugin-events-backend                                   0.0.0-use.local
  @backstage/plugin-events-node                                      0.0.0-use.local
  @backstage/plugin-home-react                                       0.0.0-use.local
  @backstage/plugin-home                                             0.0.0-use.local
  @backstage/plugin-kubernetes-backend                               0.0.0-use.local
  @backstage/plugin-kubernetes-cluster                               0.0.0-use.local
  @backstage/plugin-kubernetes-common                                0.0.0-use.local
  @backstage/plugin-kubernetes-node                                  0.0.0-use.local
  @backstage/plugin-kubernetes-react                                 0.0.0-use.local
  @backstage/plugin-kubernetes                                       0.0.0-use.local
  @backstage/plugin-notifications-backend-module-email               0.0.0-use.local
  @backstage/plugin-notifications-backend                            0.0.0-use.local
  @backstage/plugin-notifications-common                             0.0.0-use.local
  @backstage/plugin-notifications-node                               0.0.0-use.local
  @backstage/plugin-notifications                                    0.0.0-use.local
  @backstage/plugin-org-react                                        0.0.0-use.local
  @backstage/plugin-org                                              0.0.0-use.local
  @backstage/plugin-permission-backend-module-allow-all-policy       0.0.0-use.local
  @backstage/plugin-permission-backend                               0.0.0-use.local
  @backstage/plugin-permission-common                                0.0.0-use.local
  @backstage/plugin-permission-node                                  0.0.0-use.local
  @backstage/plugin-permission-react                                 0.0.0-use.local
  @backstage/plugin-proxy-backend                                    0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-azure                  0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-bitbucket-cloud        0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-bitbucket-server       0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-bitbucket              0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-confluence-to-markdown 0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-cookiecutter           0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-gcp                    0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-gerrit                 0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-gitea                  0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-github                 0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-gitlab                 0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-notifications          0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-rails                  0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-sentry                 0.0.0-use.local
  @backstage/plugin-scaffolder-backend-module-yeoman                 0.0.0-use.local
  @backstage/plugin-scaffolder-backend                               0.0.0-use.local
  @backstage/plugin-scaffolder-common                                0.0.0-use.local
  @backstage/plugin-scaffolder-node-test-utils                       0.0.0-use.local
  @backstage/plugin-scaffolder-node                                  0.0.0-use.local
  @backstage/plugin-scaffolder-react                                 0.0.0-use.local
  @backstage/plugin-scaffolder                                       0.0.0-use.local
  @backstage/plugin-search-backend-module-catalog                    0.0.0-use.local
  @backstage/plugin-search-backend-module-elasticsearch              0.0.0-use.local
  @backstage/plugin-search-backend-module-explore                    0.0.0-use.local
  @backstage/plugin-search-backend-module-pg                         0.0.0-use.local
  @backstage/plugin-search-backend-module-stack-overflow-collator    0.0.0-use.local
  @backstage/plugin-search-backend-module-techdocs                   0.0.0-use.local
  @backstage/plugin-search-backend-node                              0.0.0-use.local
  @backstage/plugin-search-backend                                   0.0.0-use.local
  @backstage/plugin-search-common                                    0.0.0-use.local
  @backstage/plugin-search-react                                     0.0.0-use.local
  @backstage/plugin-search                                           0.0.0-use.local
  @backstage/plugin-signals-backend                                  0.0.0-use.local
  @backstage/plugin-signals-node                                     0.0.0-use.local
  @backstage/plugin-signals-react                                    0.0.0-use.local
  @backstage/plugin-signals                                          0.0.0-use.local
  @backstage/plugin-techdocs-addons-test-utils                       0.0.0-use.local
  @backstage/plugin-techdocs-backend                                 0.0.0-use.local
  @backstage/plugin-techdocs-module-addons-contrib                   0.0.0-use.local
  @backstage/plugin-techdocs-node                                    0.0.0-use.local
  @backstage/plugin-techdocs-react                                   0.0.0-use.local
  @backstage/plugin-techdocs                                         0.0.0-use.local
  @backstage/plugin-user-settings-backend                            0.0.0-use.local
  @backstage/plugin-user-settings-common                             0.0.0-use.local
  @backstage/plugin-user-settings                                    0.0.0-use.local
  @backstage/release-manifests                                       0.0.0-use.local
  @backstage/repo-tools                                              0.0.0-use.local
  @backstage/test-utils                                              0.0.0-use.local
  @backstage/theme                                                   0.0.0-use.local
  @backstage/types                                                   0.0.0-use.local
  @backstage/version-bridge                                          0.0.0-use.local

👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Hmm, could be that the required scopes have changed and they need to be approved over on the Microsoft end? I believe there might be an option to allow users to approve individual scopes as well if you are alright with that.

@Rugvip , I don't think so, because it's working with 1.25.  Nothing changes on Azure.
Follow this guide https://backstage.io/docs/auth/identity-resolver#sign-in-without-users-in-the-catalog, I created packages/backend/src/auth.ts, still not working. I believe something changes in 1.29

@crazy-canux alright. Could you provide a bit more information about when the error happens and if there are any clues in logs etc.?

No error in logs. The different is "Approval required" popup in 1.29.
Is there any changes about the "api permission" on azure?

No error in logs. The different is "Approval required" popup in 1.29.
Is there any changes about the "api permission" on azure?

Are you able to easily try the old 1.25 version? I'm curious if that screen still appears on the old version or not. It does look like something that's been changed in the Microsoft configuration on your end rather than anything to do with the auth provider in Backstage, although I could be wrong about that ofc.

I realize a change that's happened between 1.25 and 1.29 is that the additionalScopes config has been fixed. Earlier it used to never be included, but it is now fixed an will always be included. It's likely that the addition of the Mail.Send scope is what breaks things here, and it should most likely be safe for you to remove it. If you do want it to be included you'll need to configure it in the list of defaultScopes in the frontend MicrosoftAuth implementation instead, due to how the Microsoft auth provider still manages multiple different auth clients for different resources through the frontend.

That error suggests you need to provide admin consent to one or more permissions.  Can you check you've followed the section on Admin Consent at https://backstage.io/docs/auth/microsoft/provider/#configure-app-registration-on-azure .
If you're asking for additional scopes, you'll probably need to grant admin consent for those too.

Another question is do you really need the Mail.Send scope?  If not, I'd just remove that.  Mail.Send is included in the docs as an example at https://backstage.io/docs/auth/microsoft/provider/#configuration , but you probably don't want that unless you've built a custom plugin to send email.

@Rugvip , @afscrome  thanks for help. After remove "Mail.Send", it's working.
Like you mentioned, there is a bug, that's why the same configuration works with 1.25, but not working with 1.29.
One more thing. After remove "Mail.Send", I got error with "user don't have email" after setup "sign-in-without-users-in-catalog".  https://backstage.io/docs/auth/identity-resolver#sign-in-without-users-in-the-catalog.
Now, I use msgraph to import org data before login.

to me is a god idea include this description on the documentation.


[Hub Generated] Review request for Microsoft.ApiManagement to add version preview/2018-06-01-preview

If you are a MSFT employee you can view your work branch via this link.
Fix for https://github.com/Azure/azure-rest-api-specs/issues/6713
Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@MyronFanQiu fyi

Automation for azure-sdk-for-python

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

@solankisamir Thanks!

@openapi sdkautomation rebuild

@openapi sdkautomation rebuild

@openapibot sdkautomation rebuild

@openapibot sdkautomation rebuild

@openapibot sdkautomation rebuild


Dropdown in Breadcrumb

We can have an advanced breadcrumb, which will have a dropdown for navigating to a specific position in case of nested pages.
For example:
Home / Dashboard v / Profile
Here, 'Dashboard' leads to different pages and profile is one of them. So, if the user wants to directly navigate to some other page from Profile page, then, it can do so by clicking on the dropdown on Dashboard link and selecting the desired page; instead of first going back to Dashboard and then selecting the desired page.

This kinda works in v4; the only major problem is that the dropdown's height causes the text of the other non-dropdown crumbs to become vertically misaligned.

Won't be adding to the default v4, but sounds ripe for custom CSS or open source add-on.

[Just a thought] Won't it be nice, if developers don't have to reach out to add-ons if most modern things are included by default in the framework. Because, in enterprise production systems it takes a lot of process and debate before going out of the framework and opt for any add-on.

If we added every quasi-reasonable feature that was ever requested, the framework would become very complex, much harder to maintain, and would justifiably be considered bloated by [potential] users. Therefore, each potential addition must be carefully considered.

In fairness, and to aid any future re-evaluation of this feature request, there have been 2 prior issues related to such a feature: #559, #6115


support: Added noop way of visiting registration and invitation links.

Closes #13262
Now the staff member can visit the registration and invitation links without changing the status attribute of PreregistrationUser and EmailChangeStatus classes if the invitation url ends with the support parameter as True.
Works as previously intended if a staff member is not logged in and the support parameter is True.
For a user to change their email, the tests were present.
Added remaining tests.
Testing Plan:
tested with ./tools/test-all and '/activity/support'

@r0fls thanks for working on this!  @hackerkid can you do the first review?

Hello @hackerkid, I've made the appropriate changes.

@hackerkid thanks for the reviews. Modified the files and the git log. 👌

@hackerkid updated the pr.

hi @hackerkid updated.

This should be inviter not invitor

Made this change in another test case i noticed and added it as a separate commit.

@ryanreh99 Changes look great to me. One minor suggestion is that the last commit should have been merged with the first commit. Since making that change as a seperate commit does not add any useful information to the zulip commit history. @timabbott should be able to take care of that when he reviews the PR.
@timabbott This is ready for a review from your side.

@mateuszmandera can you give this the next review, since you've been working in our authentication code path recently?

Looks good to me, though I think one more test for the case of access with support=True by someone's who's not logged in would be useful.

The two test changes were actually fixes to existing tests; I merged those.  @ryanreh99 it'd be great if you can add the test @mateuszmandera suggested; I'll add a couple small comments as well.

@timabbott, I added the test case and made the necessary changes.

Posted 2 comments, looks good to me aside of those.

I made some UI changes to the /activity/support page, and then realized that this feature is broken.  I pushed some prototyping to it, but I don't have a good solution.
The problem is that of domains; /activity/support is meant to be able to administer an entire Zulip server, not just a single realm (that's the distinction between .is_staff and .is_realm_admin).  The problem is the check for request.user.is_staff uses cookies, and the cookie for is_staff is only available on the staff user's own realm.  Easily reproducible by using the "create realm" button in an incognito tab, creating the invite to inspect in that realm, and then using this feature.
There's a few days to attack this:

Having the form on templates/confirmation/confirm_preregistrationuser.html post to a realm.uri for the target realm (causes a CSRF error, I think for good reason).
Hacking things to allow visiting another realm's registration page on the is_staff user's domain (close to the current code I just pushed).  Broken because then it renders the page using the logo/description/etc. for the is_staff user, which more or less defeats the purpose of this.  Maybe fixable if we're willing to do a hack in the zulip_default_context logic to allow some sort of override realm to be set; I have a test implementation of that which I've pushed here.

@ryanreh99 probably it makes sense for you to take over writing tests to cover the new details in this new implementation.

Closing, as #14584 addressed the issue this was working on.