DCD Backend: Respect recently added assets in project service

at the moment, the project service gathers many assets in AddAssetsToProject, but somebody (this guy!) forgot to add for instance Topsides, and Explorations.
This should ideally be covered by tests, and sample/test data.

OK we alreadu have this covered by tests that I think @petterwildhagen wrote ages ago.
and explorations and topsides and wellprojects (which i'm working on right now) are already in the data, and in the tests.
BUT explorations are not added in the AddAssetsToProject method, and yet the tests are not failing.
Indeed, when I comment out the call to AddAssetsToProject, it's still not failing, and I double checked with a manually with an assertion against 0 - the count of for instance explorations is not zero.
so this makes me think that we don't actually need to call AddAssetsToProject in the get methods of the project service.
thoughts, @petterwildhagen @eiriksanderfjeld @eric ?
what I also don't understand is the call to Include in the get methods - we include cases, but we don't seem to need to include other stuff. entity is still a very opaque black box for me... when I comment out the call to Include, in the test, we have cases in the response returned by the service... is that one unnecessary, too? perhaps because we removed all the virtual IDs that would have caused lazy loading?

@petterwildhagen I tested again, more carefully - removing the AddAssetsToProject call on each project in the GetAll method of the project service does not fail the tests, BUT the json result in the swagger interface is barren (missing all assets).
there is something between the objects in the code and the response given out by the API, apparently O_o

we now have a POC for querying our API and checking the response. let's see if we can catch the weird behaviour with these tests.


Cannot deploy CRDs to Kubernetes 1.11

Describe the bug:
When deploying CRDs to Kubernetes 1.11, they fail to apply with validation errors: https://prow.build-infra.jetstack.net/view/gcs/jetstack-logs/pr-logs/pull/jetstack_cert-manager/2199/pull-cert-manager-e2e-v1-11/1182598410243411968
The relevant error: must only have "properties", "required" or "description" at the root if the status subresource is enabled
This is because we specify type: object at the root of our OpenAPI schema: https://github.com/jetstack/cert-manager/blob/4ec682db20d2f030c5bbaac67c4f2f5301a7b081/deploy/manifests/00-crds.yaml#L1366
You can see in Kubernetes 1.11, this field is in fact not allowed: https://github.com/kubernetes/kubernetes/blob/9016740a6ffe91bb29824f80c34087b993903bd6/staging/src/k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/validation/validation.go#L303-L306
We added it is a requirement to make our OpenAPI schema structural - discussing on #sig-api-machinery, it may be possible to relax the requirement to have this field in order for a schema to be structural, however it will require a bugfix/patch which will take some time to propogate through to cloud providers/managed service providers.
Expected behaviour:
We should either explicitly declare 1.11 as unsupported, or otherwise remove this field so that users can deploy to kubernetes 1.11.
For what it's worth, 1.11 is now EOL, and EKS for example is upgrading all 1.11 users to 1.12 in November: https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html
ref #2064
Steps to reproduce the bug:
Attempt to apply the deploy/manifests/00-crds.yaml file against a Kubernetes 1.11 cluster.
Environment details::

Kubernetes version (e.g. v1.10.2): v1.11
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): N/A
cert-manager version (e.g. v0.4.0): v0.11.0, v0.10.x
Install method (e.g. helm or static manifests): N/A

/kind bug
/area deploy

Not good, but the temporary workaround is to add this argument --validate=false.

This argument won't actually help in specifically Kubernetes 1.11's case - because it refuses to accept our CRD manifest as it sets the type: object field on our CRDs schema (as highlighted in the first post).
It's a real PITA, and after discussion with #sig-api-machinery I think it may be one that we can't work around without removing this field altogether, which will mean our CRD schemas are no longer 'structural' (which is a requirement for CRDv1).
Whilst we could remove this field and it will work for 1.11, I'm not sure if it's really worthwhile (and it means we're reverting progress forward). That said, I'm not too comfortable with the way we've discovered this, and the 'surprise' drop of support...

I also this:
must only have "properties", "required" or "description" at the root if the status subresource is enabled
And i comment this:
`
#subresources:
status: {}
`
That is OK.

I have the same error.

This bit me as well.
It might be an unfortunate situation, but as far as I can see, cert-manager 0.11 not compatible with Kubernetes 1.11.
Would it make sense to update this documentation? https://docs.cert-manager.io/en/release-0.11/getting-started/install/kubernetes.html

Hi, just saying that dropping support for Kubernetes 1.11 means that you also drop support for OpenShift v3.11 which is as for now used by many enterprises. Consider to revert this breaking change for the switchover period when enterprises will start using OpenShift which is Kubernetes 1.14 based.

@yehaifeng Did you checked impact of commenting subresources: status: {}?
This breaking change was introduced by "Move status to a CRD Subresource (#2097, @JoshVanL)"
@JoshVanL can you evaluate the impact of this modification?

@grzechukol thanks for the explanation there - I'd not seen your message until just now!
This is unfortunate as it means we can't make use of 'structural schemas', which is what allows things like kubectl explain to work, as well as various other new CRD related features.
What is OpenShift's deprecation policy for versions, and how are they maintaining Kubernetes 1.11? Presumably they are back-porting fixes all the way back there... 😬
Disabling the status subresource will allow the components to deploy, but the controller itself will no longer work so you should not do this. Instead, removing this field from all CRDs (i.e. type: object at the root of the schema): https://github.com/jetstack/cert-manager/blob/e6bf2c0ace6cf2e674149147a292a22108722af1/deploy/manifests/00-crds.yaml#L42
As well as setting preserveUnknownFields: true (it is currently explicitly false) should make it possible to run on OpenShift 3.x. We could potentially look at removing these lines from the -openshift variants of our manifests automatically in order to maintain support for 3.x until it is deprecated.

Hm, it seems that 3.11 will be deprecated in June 2022 (for 'full support'). This seems like a really long time for us to hinder the UX of users on 4.x and beyond... If we also want to continue to support 3.x, we'll probably need to ship multiple different OpenShift variants because of this issue 🤦♂  https://access.redhat.com/support/policy/updates/openshift

Works...
If you want a no brainer, just grab:
#!/bin/bash

# https://github.com/jetstack/cert-manager/issues/2200#L42
# ./install-crd.sh | oc create --validate=false -f -

curl -sL https://github.com/jetstack/cert-manager/releases/download/v0.12.0/cert-manager-openshift.yaml | \
  sed -e 's/preserveUnknownFields: true/preserveUnknownFields: false/g' | \
  sed -e 's/type: object//g'

@munnerz
Since crds are inside the helm chart, its possible to add some conditions inside the crds? Like a hybrid chart for kubernetes and openshift?

I think @jkroepke made a wonderfull suggestion here. I also need to stick with OKD 3.11 for the next 1,5 years.

It might only affect some German users but I'd like to throw this one in: I just tried to install cert manager to Open Telekom Cloud which is also stuck on K8S 1.11. I already asked when they consider to upgrade but until then I will also need to apply a workaround to make this run.

We recently came across this same issue in one of our projects. I think one solution is to use Cpabalities in helm charts to drop the unknown fields.
Here is an example: https://github.com/kubevault/installer/blob/master/charts/csi-vault/templates/appbinding-crd.yaml#L33-L35

@munnerz
Openshift 3.11 receives some patches last weeks, e.g.: https://github.com/openshift/origin/pull/24540 + the patch is released for all enterprise users.
Maybe you can drop all the workarounds created in 0.14 (#2609) for the old openshift 3.11 and just support one CRD.

Sadly that still is not possible - the full list of fields we have to 'transform' to create the 3.11 compatible CRDs can be found here: https://github.com/jetstack/cert-manager/blob/f3df90305c03c82c0ccf113d87cd6025de7eca3e/hack/filter-crd/main.go#L174-L186
Notably, we have to remove the new API version (v1alpha3) altogether, as well as a few other additional OpenAPI schema options (such as x-kubernetes-preserve-unknown-fields) to avoid users having to use --validate=false on all their kubectl calls (which is often not possible with GitOps tools).
I think we are stuck with supporting two variants of the CRDs for the foreseeable future - the earliest we could remove it is once Kubernetes v1.14 is no longer a supported platform 😞


Fixed snap

Snap was initially building qpdf 10.3.6 which was conflicting with current master of libcupsfilters which requires qpdf>=11.0
Qpdf initially used autotools for build, which was changed to cmake in version 11.2.0

There is an error missing file qpdf.hh that is coming

Now the error has been fixed

Thank you very much @metabiswadeep !


Add support for seeded rng

This is needed eg. for cryptographic applications. Fully backwards-compatible.

Hmm, I ran tests with SpecRunner.html. I'll fix these errrors.

Coverage increased (+0.006%) to 94.241% when pulling ec13f39cdd5103f824747fd6ce23af4f697af22f on malyvsen:master into 4e99b15b7951338f164728377c906caae5a78202 on peterolson:master.

Coverage increased (+0.006%) to 94.241% when pulling ec13f39cdd5103f824747fd6ce23af4f697af22f on malyvsen:master into 4e99b15b7951338f164728377c906caae5a78202 on peterolson:master.


Fixed the error while setting tim drectory for excised tim file.

As tim_directory is now a property of TimingConfiguration class with the setter function set_tim_directory, it was giving an error while setting the tim directory for excised tim file using self.tim_directory = ''. I have now changed it to self.set_tim_directory = '' to fix that.

@lanky441 I introduced this bug in #63 by misunderstanding how setter functions work and failing to adequately test my code. I essentially wrote this:
class TimingConfiguration:
    @property
    def tim_directory(self):
        # get the tim directory
    @tim_directory.setter
    def set_tim_directory(self):
        # set the tim directory

thinking that the name of the set_tim_directory() function didn't matter, since the name of the Property was already set by the tim_directory() function. But in fact, the name of the setter does matter, and should have been tim_directory() for it to work in the usual way, where there is only one property tim_directory with both a getter and a setter, which is what I intended.
What the above code actually does is create two properties, one called tim_directory with only a getter function, and a second one called set_tim_directory with the exact same getter function, but an additional setter function. That's why getting the value with tc.tim_directory works fine, but to set it you have to do tc.set_tim_directory = ''. This is a byproduct of the way that property decorators work, where each one creates a new Property object that replaces the last one.

The correct way to fix this is at the source, by changing the name of the setter to tim_directory() instead of set_tim_directory(). There's a couple of similar changes that I should make, too. I'll make a separate PR to do that, and close this one.


Add 1.3.9 perf test with https_logs load

Description
Add 1.3.9 perf test with https_logs load
Issues Resolved
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #3408 (fc95193) into main (c38175c) will decrease coverage by 0.29%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #3408      +/-   ##
==========================================
- Coverage   91.74%   91.46%   -0.29%
==========================================
  Files         172      172
  Lines        4991     4991
==========================================
- Hits         4579     4565      -14
- Misses        412      426      +14

see 2 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Update Dart Lang Icon

Replace the icon of the Dart language, which was an old version.

Please approve this PR. I need this.

@Almighty-Alpaca Please check and approve this PR.

This looks good to me, but changing the logo in the repository is only half the battle, it needs to be changed on the discord developer portal as well
This task can only be done by alpaca himself as he is the owner of the application containing all of the resources that the plugin uses

This looks good to me, but changing the logo in the repository is only half the battle, it needs to be changed on the discord developer portal as well This task can only be done by alpaca himself as he is the owner of the application containing all of the resources that the plugin uses

You're right. I want the person in charge of this project to merge this PR, and modify the icon on the Discord Developer Portal.


Feature request: Configure userns_mode

As a user with an elastic ci stack with docker user namespace enabled (the default for EnableDockerUserNamespaceRemap), I would like to disable, or otherwise configure, the user namespace for a particular build step running with this plugin by configuring the userns_mode docker compose parameter.
https://docs.docker.com/compose/compose-file/#userns_mode
https://docs.docker.com/engine/security/userns-remap/

I'm not sure if you could reconfigure the elastic CI stack’s EnableDockerUserNamespaceRemap from this plugin? Perhaps @lox might know better how these two interact?

As I understand EnableDockerUserNamespaceRemap would configure the "server" default, but setting userns_mode would override for any particular run.

That's correct @s01ipsist, I do recall someone mentioning they didn't have much luck trying to disable it on a per-run basis 🤔

I can understand if you didn't want to add a feature that may or may not work as documented. Would you consider an alternative approach where an --extra-args or similar allowed direct pass through of arguments. It's an "extra for experts" feature and somewhat future-proofs the plugin in that it allows users to adopt new features before the plugin explicitly supports them. Just floating ideas.

I think it makes sense to add a userns_mode option, I just wanted to check that it'd work in an elastic stack setup.
Just for context/understanding, why not change it in your docker-compose configuration file?

@toolmantim - great question.  🤦♂ I completely lost sight of how the plugin functions to call, and optionally overwrite, the docker-compose config. The --extra-args concept is nonsense with that exposed, as is any real need to expose this userns_mode configuration. Perhaps the readme could restate similar at the end of the arguments listing, perhaps I just missed the wood for the trees.

😁 No worries!


Ctrl-Shift-N is not a good shortcut for a blank sheet on chrome

Not so much of an issue when installed as a PWA since the Chrome shortcut no longer applies in that case. However, it might make sense for Ctrl-Shift-N to open a new window when in installed standalone mode

This solution  works with edge to open a new window in standalone mode. Verified that it works on Chrome and Edge using the following command:
window.open('/', '_blank', `width=${window.innerWidth}, height=${window.innerHeight}`)


cc-wrapper: add support for hardbackedgecfi hardening flag on x86_64 & aarch64

Description of changes
(This sits on top of  #318256 ~(go review that!)~, because it takes advantage of a refactoring done there - the only "interesting" commit in this PR is the last one)
Some background: https://discourse.nixos.org/t/future-design-of-hardening-flags/38826
This experimentally implements the hardening flag hardbackedgecfi (hardware-based backward edge Control Flow Integrity) in different ways on the x86_64 and aarch64 linux platforms. The flag is only enabled on the pkgsExtraHardening package set here.
Here's where I need some help - I don't have access to hardware that implements either of these features. So while I can do a large rebuild and ensure it doesn't break anything on older systems (for which the features are effectively a no-op), I'm unable to find out how many packages these flags break when the features are actually active.
On x86_64 this enables CET "shadow stack" features implemented in (a seemingly random selection of) new Intel processors and AMD Zen3+. It requires a 6.6+ kernel. Helpfully those VPS providers that do have processors supporting this don't necessarily expose the feature to guests, so I'm probably appealing to people with bare metal here to be able to test this properly.
On aarch64 this uses "pac-ret" - pointer authentication of return addresses on the stack. This uses instructions added in ARM 8.3. Unfortunately most (all?) dev board SoCs don't implement anything further than 8.2, and the most widely used processor for cloud ARM instances, the Ampere Altra series, is also ARM 8.2. I do hear that the latest AWS Gravitons implement ARM 9.0, so that's a possibility (I have no personal AWS account though). So far I've managed to test packages (built on native ARM 8.2 hardware) on qemu's TCG aarch64 implementation - which luckily does implement the pointer authentication instructions. Although it's obviously extremely slow and it took me a weekend to (re-)build a small selection of packages with good test suites on some fairly beefy x86_64 hardware. And there are some spurious test failures caused by running the tests on qemu in the first place which doesn't help..
What am I trying to discover? Whether there's significant overlap in the sets of packages broken by these two features. If there isn't, they probably shouldn't be covered by the same hardening flag and I should rethink this.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

How exactly do I turn this on? I've compiled something like .#pkgsExtraHardening.gqrx but only see x86_Thread_features: in /proc/self/status. I see user_shstk in /proc/cpuinfo (I'm on zen4) and am running:
Linux monomyth 6.8.11-xanmod1 #1-NixOS SMP PREEMPT_DYNAMIC Tue Jan  1 00:00:00 UTC 1980 x86_64 GNU/Linux

https://sourceware.org/git/?p=glibc.git;a=commit;h=55d63e731253de82e96ed4ddca2e294076cd0bc5 looks relevant, as it disabled shadow stack by default.

Good find, my guess is that they needed to do that because certain unnamed distributions started blindly enabling the flag in their builds before it was possible to test for breakage.
I guess we could make pkgsExtraHardening revert that change.

I've actually tried that environment variable and still don't see it...

OK, I actually do see it now but not how I originally thought.
GLIBC_TUNABLES=glibc.cpu.hwcaps=SHSTK strace ./result/bin/gqrx 2>&1 | grep prctl
arch_prctl(ARCH_SET_FS, 0x7f849aa68740) = 0
arch_prctl(ARCH_SHSTK_ENABLE, 0x1)      = 0
arch_prctl(ARCH_SHSTK_STATUS, 0x7fffc5c5d400) = 0
arch_prctl(ARCH_SET_FS, 0x7f0cf80e2f40) = 0

strace ./result/bin/gqrx 2>&1 | grep prctl
arch_prctl(ARCH_SET_FS, 0x7fa38e6a8740) = 0
arch_prctl(ARCH_SET_FS, 0x7fe76625bf40) = 0

Update: success!
GLIBC_TUNABLES=glibc.cpu.hwcaps=SHSTK:glibc.cpu.x86_shstk=on ./result/bin/gqrx
x86_Thread_features:    shstk
x86_Thread_features_locked:

From what I understand, there are a few considerations here:

the ENDBR opcodes inserted by the compiler to mark valid branch targets on x64 are NOPs on old CPUs, so it should be safe to compile this on CPUs that don't support it
maybe we should use -fcf-protection=full: https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index-fcf-protection
those tunables need to be enabled by default somehow

* the ENDBR opcodes inserted by the compiler to mark valid branch targets on x64 are NOPs on old CPUs, so it should be safe to compile this on CPUs that don't support it
* maybe we should use `-fcf-protection=full`: https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index-fcf-protection though the backedge CFI flag would then mean more than pac-ret

TODO. I'm currently only looking at stack-protecting features as they appear to have fewer caveats. I expect we'll end up covering forward-edge CFI with a different flag.

* those tunables need to be enabled by default somehow

On it.

I'll spend about an hour bootstrapping everything again with those enabled :-)

Hopefully this doesn't cause a rebuild for non-x86.
It builds for me.

Alright, now we're cooking. PCRE hates this.
./test-driver: line 109:  3769 Segmentation fault      (core dumped) "$@" > $log_file 2>&1
FAIL: pcre_jit_test
FAIL: RunTest
PASS: RunGrepTest
=================================
   PCRE 8.45: ./test-suite.log
=================================

# TOTAL: 3
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: pcre_jit_test
===================

Running JIT regression tests
  target CPU of SLJIT compiler: x86 64bit (little endian + unaligned)
  in  8 bit mode with UTF-8  enabled and ucp enabled:
............................................................
............................................................
............................................................
............................................................
............................................................
............................................................
............................................................
............................................................
............................................................
.......................FAIL pcre_jit_test (exit status: 139)

FAIL: RunTest
=============

PCRE C library tests using test data from ./testdata
PCRE version 8.45 2021-06-15

---- Testing 8-bit library ----

Test 1: Main functionality (Compatible with Perl >= 5.10)
  OK
  OK with study
  OK with JIT study
Test 2: API, errors, internals, and non-Perl stuff (not UTF-8)
  OK
  OK with study
Segmentation fault (core dumped)

** Test 2 requires a lot of stack. If it has crashed with a
** segmentation fault, it may be that you do not have enough
** stack available by default. Please see the 'pcrestack' man
** page for a discussion of PCRE's stack usage.

 Do these packages behave themselves if you hardeningDisable = [ "hardbackedgecfi" ]; ?

I'll give Python a shot, that looks like it may have been the issue for LLVM. PCRE behaved when I changed that.

So, it was actually LLVM that caused the problem. What would cause a process to not report shstk in its thread features? I can build armagetronad.dedicated and have it work, but armagetronad the desktop app doesn't support shadow stacks.
... Wait, as I was writing this, I answered my own question. My system isn't compiled with CFI, so it's graphics drivers!

I forget about things like that being mostly a server user.

Excellent thankyou. So far it's looking like there isn't much correspondence between broken packages for shadow stacks and for pac-ret, so this might need a rethink.


Building container image fails on the code compilation stage

Hi there,
I can't build the container image, because it fails on the compilation:
error: could not compile `packed_simd` (lib) due to 106 previous errors
warning: build failed, waiting for other jobs to finish...
Error: building at STEP "RUN cargo build --release": while running runtime: exit status 101

Could you advise on how to fix this?
full_log.txt

Hey! Thanks for opening an issue! The container image has been outdated for some time now, but I've gone ahead and updated it to be compatible with the latest changes over in #101. For now, feel free to try it out with that branch instead!


do not turn on serde (from hex) when the serde feature is not on

cc @KolbyML
missed from #34

That is a thing very cool :D


Bug Tapo H100 Smart Hub > 12 Devices

Last version of integracion
Device:
H100
por TP-Link
Firmware: 1.3.9 Build 230522 Rel.103415
Hardware: 1.0
HS Versions:
Core 2023.12.1
Supervisor 2023.11.6
Operating System11.2
The problem began to happen the moment I exceeded 12 devices paired with the tapo hub, from that moment every time I reload the integration devices randomly appear and disappear, always missing some, especially motion sensors or door sensors
log:
home-assistant_tapo_2023-12-13T18-53-04.108Z.log
Currently the sensor of a window is the one that does not appear, I understand that it is the binary_sensor error
My theory is that when all the devices that depend on the coordinator are listed, exceeding a certain amount will cause the hub to time out and stop responding as expected. If this is the case, perhaps making a slower acquisition of the subdevices may work.

Similar problem here: in my case the HUB stops responding on the lan but is accessible from the Tapo App

@alexskynet Of course, from the tapo app everything works and appears correctly, it seems to be a rejection towards the integration

Issue is still ongoing.  I have now reverted to purchasing additional hubs to work around this limitation but it would be good if it could be resolved


Smart indentation doesn't respect indentation space settings to two spaces

switch (10) {/**/
}

Set indentation settings to two spaces. Then add a new line after the marker.
Expected: Cursor is placed two spaces into the next line.
Actual: Cursor is placed four spaces into the next line.

@DanielRosenwasser I'm having trouble reproducing this in vscode. You should show me this when you're available.

Looks like it's fixed now?

Vscode doesn't seem to be calling into tsserver for this so may be a change on their side.


Attribute has already been defined error

I don't know what happened but today when I rebuilt my project I got an error with the attrs.xml of the library.

I wouldn't completely trust AIDE to work correctly. But that usually happens if a library is referenced twice.

Yeah you're right. I actually removed the library from my project and re-added it but AIDE failed(bug) to remove the reference to the original library. thanks


The component has no name, add 'name' property on the Vue component

 The component has no name, add 'name' property on the Vue component

My component has a parameter for the name property...

Hello @KnaanBraz trying to cover our bases  here. do you still meet tis issue with the current version ?


Interface Omitted from Generated SDL

I'm trying to use the Interface derivative macro to define a common interface many types can implement, but the generated SDL does not include any interfaces.
Interface:
#[derive(Interface)]
#[graphql(field(
    name = "id",
    type = "ID"
))]
/// An object that can be identified by its identifier (ID).
pub enum Identifiable {
    User(User),
    Media(Media)
}

Query:
pub struct Query;

#[Object]
impl Query {
    async fn media(&self, id: ID) -> Option<Media> {
        None
    }

    async fn user(&self, id: ID) -> Option<User> {
        None
    }
}

User:
use uuid::Uuid;
use async_graphql::{ID, Object};

#[derive(Queryable)]
pub struct User {
    // Note: Stored as a UUID but returned to the user as an ID.
    pub id: Uuid,
    pub username: String,
    pub email: String,
    pub nickname: Option<String>,
    pub biography: Option<String>
}

#[Object]
impl User {
    /// The ID of the user.
    pub async fn id(&self) -> ID {
        self.id.into()
    }
}

Media:
#[derive(Queryable)]
pub struct Media {
    // Note: Stored as a UUID but returned to the user as an ID.
    pub id: Uuid,
    pub description: Option<String>
}

#[Object]
impl Media {
    /// The ID of the media.
    pub async fn id(&self) -> ID {
        self.id.into()
    }
}

SDL:
type Query {
        media(id: ID!): Media
        user(id: ID!): User
}
type Media {
        """
        The ID of the media.
        """
        id: ID!
}
type User {
        """
        The ID of the user.
        """
        id: ID!
}
schema {
        query: Query
}

I'm confused why there's no interface Identifiable {...} in the SDL (or if this is intentional). It would be useful in type-safe environments where common fields can be shared and passed around (like how GitHub makes extensive use of interfaces in its API).

If your Schema does not directly reference this Interface, then it will not exist in the registry.
You can register it manually with SchemaBuilder::register_type.

That solved my problem - thanks!


Add missing C# file content for new project

Fixes #12017
The bug was caused because not all language checkers had a csharp entry, and since the language checker is global it doesn't make sense to display a language that can't be selected for one checker.
Ideally, we would introduce a lint failure to make this mistake impossible (and catch other places where we made the mistake). That is out of scope for this PR.

Wait, but why does a chooser with a missing option down below affects the chooser that has C# and prevents it from showing it? Isn't this a bug on its own?

Verified that the fix works in site prerview.

I would say that having C# for the first part of the guide is better then not having it, even if it doesn't continue for the rest of the guide.


egg dropping problem in python

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Description
Added code for egg dropping puzzle in python.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Fixes #6256

@bhav09 kindly review :)


virt-launcher lifecycle cleanup

Virt-Launcher Lifecycle Management
In general for Kubevirt, I think we need to strive to make whatever component creates a resource be in charge of that resource's lifecycle.
For virt-launcher, the component that creates that resource is virt-controller. For a VM in virt-controller, the flow is...

start virt-launcher pod for the VM
assign the VM to the node the virt-launcher pod started on
watch for VM to be finalized
ensure virt-launcher pod terminates for a finalized VM.

That last step of "ensuring virt-launcher pod terminates" is what this patch addresses. Previously we depended on the virt-launcher's timeout to clean up orphaned virt-launches. While I think the timeout has a role in our design, I believe the normal mode of operation is that virt-controller should ensure cleanup of the virt-launcher pods it creates.
Virt-Launcher Timeout
Virt-launcher has a timeout duration it will wait trying to detect the VM process before exiting. This timeout should be seen as a failsafe mechanism that gives us a guarantee that a virt-launcher pod will not remain active indefinitely without a corresponding VM process.
However, I don't think that it is wise for the virt-launcher timeout to be associated with the normal mode of operation. This timeout needs to be very generous and only exist as a safety mechanism.  The 60 second timeout we previously had is not enough time to guarantee the VM has launched. There are too many variables involved.
For example, during virt-controller failover, the time between when virt-launcher starts and when the VM get's it's node assignment could exceed 60 seconds. This would cause the VM to fail to start after virt-controller recovers because the virt-launcher pod for the corresponding VM expired.
The virt-launcher timeout being hit means something outside of the normal mode of operation has occurred. To account for this change in perspective, the timeout has been increased to 5 minutes.

retest this please

In general for Kubevirt, I think we need to strive to make whatever component creates a resource be in charge of that resource's lifecycle.

Yes and no. I want to look into that when we implement #413. Having the timeout and virt-controller as safeguards is definitely fine. In the context of #413 I want to  discuss if parts of the responsibility might go to virt-handler and virt-launcher, to properly implement host-side restart policies.

#413 I want to discuss if parts of the responsibility might go to virt-handler and virt-launcher, to properly implement host-side restart policies.

yes, I agree. That will require coordination between virt-handler and virt-launcher. I'll give this some thought as well.


Add instructions for installation on Solus

What is the purpose of this change? What does it change?

Was the change discussed in an issue or in the forum before?

Checklist

[ ] I have read the Contribution Guidelines
[x] I have added tests for all changes in this PR
[x] I have added documentation for the changes (in the manual)
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (template here)
[ ] I have run gofmt on the code in all commits
[ ] All commit messages are formatted in the same style as the other commits in the repo
[x] I'm done, this Pull Request is ready for review

Codecov Report

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

@@            Coverage Diff             @@
##           master    #1695      +/-   ##
==========================================
- Coverage   52.43%   47.08%   -5.35%
==========================================
  Files         143      143
  Lines       11415    11415
==========================================
- Hits         5985     5375     -610
- Misses       4507     5176     +669
+ Partials      923      864      -59

Impacted Files
Coverage Δ

internal/backend/azure/azure.go
0% <0%> (-82.15%)
:arrow_down:

internal/backend/swift/swift.go
0% <0%> (-78.45%)
:arrow_down:

internal/backend/b2/b2.go
0% <0%> (-77.73%)
:arrow_down:

internal/backend/gs/gs.go
0% <0%> (-73.61%)
:arrow_down:

internal/backend/swift/config.go
36.95% <0%> (-54.35%)
:arrow_down:

internal/checker/checker.go
65.65% <0%> (-3.98%)
:arrow_down:

internal/backend/test/tests.go
60.21% <0%> (-0.66%)
:arrow_down:

internal/archiver/archiver.go
64.04% <0%> (-0.22%)
:arrow_down:

Continue to review full report at Codecov.

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


NoApiKeys

| Support request? | [ yes]
I already opened same ticket but closed it since i thinked i solved it. Turns out not. This has been also troubleshooted with google and they claim same that no APY key is in use. I installed according to installation document. Not docker. Everything works but not google maps. I have entered API-keys in app/config/parameters.yml
cocorico_geo.google_place_api_key: AIzaSyBomj_-***
cocorico_geo.google_place_server_api_key: AIzaSyBomj_-***
cocorico_geo.ipinfodb_api_key: AIzaSyBomj_-***
perhaps google maps has different variable name in conf? if so please tell
This is full error what i get in web browser console
util.js:229 Google Maps JavaScript API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messages#no-api-keys
js?libraries=places&language=en:78 You must use an API key to authenticate each request to Google Maps Platform APIs. For additional information, please refer to http://g.co/dev/maps-no-account For more information on authentication and Google Maps JavaScript API services please see: https://developers.google.com/maps/documentation/javascript/get-api-key

Hello there.
For 'cocorico_geo.google_place_api_key' and 'cocorico_geo.google_place_server_api_key' you can use the same API key.
In order to generate your own API key, do not forget to follow:

To get an API key:
Go to the Google Cloud Platform Console.
Click the project drop-down and select or create the project for which you want to add an API key.
Click the menu button  and select APIs & Services > Credentials.
On the Credentials page, click Create credentials > API key.
The API key created dialog displays your newly created API key.
Click Close.
The new API key is listed on the Credentials page under API keys.

And after that, you should run the composer again (the only way that worked with me)
composer install && php bin/console assets:install --symlink web --env=dev && php bin/console assetic:dump --env=dev && php bin/console doctrine:cache:clear-metadata && rm -rf ./var/cache && rm -rf ./var/logs && php bin/console cocorico:currency:update


ArchWSL emacs gui

Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.
If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.
Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues.  Please direct all Windows crashes and security issues to<EMAIL_ADDRESS> Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".\
See our contributing instructions for assistance.
Please fill out the below information:

Your Windows build number:  (Type ver at a Windows Command Prompt) Microsoft Windows [版本 10.0.19041.264]

What you're doing and what's happening:  (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.) i want to use emacs gui version in ArchWSL , I check the # 4106
so i write export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):0 in .bashrc
and VcXrsv

i run emacs the emacs gui window in a flash and get this
(emacs:1192): Gtk-WARNING **: 10:32:01.105: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../gtk/gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Adwaita/24x24/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Bail out! Gtk:ERROR:../gtk/gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Adwaita/24x24/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Fatal error 6: Aborted
Backtrace:
emacs[0x50fbcf]
emacs[0x4f5175]
emacs[0x50dfcf]
emacs[0x50e20e]
emacs[0x50e2f9]
/usr/lib/libpthread.so.0(+0x14960)[0x7f27d30f0960]
/usr/lib/libc.so.6(gsignal+0x145)[0x7f27d2e382e5]
/usr/lib/libc.so.6(abort+0x127)[0x7f27d2e21853]
/usr/lib/libglib-2.0.so.0(+0x1c062)[0x7f27d42d7062]
/usr/lib/libglib-2.0.so.0(g_assertion_message_error+0xb8)[0x7f27d4304178]
/usr/lib/libgtk-3.so.0(+0x2c6169)[0x7f27d4b6b169]
/usr/lib/libgtk-3.so.0(+0x2c65c2)[0x7f27d4b6b5c2]
/usr/lib/libgtk-3.so.0(+0x2c66d9)[0x7f27d4b6b6d9]
/usr/lib/libgtk-3.so.0(+0x2c6990)[0x7f27d4b6b990]
/usr/lib/libgtk-3.so.0(+0x2af341)[0x7f27d4b54341]
/usr/lib/libgtk-3.so.0(+0x34b773)[0x7f27d4bf0773]
/usr/lib/libgtk-3.so.0(+0x3514b1)[0x7f27d4bf64b1]
/usr/lib/libgtk-3.so.0(+0x2aace3)[0x7f27d4b4fce3]
/usr/lib/libgtk-3.so.0(+0x1ef183)[0x7f27d4a94183]
/usr/lib/libgtk-3.so.0(+0x1ee16e)[0x7f27d4a9316e]
/usr/lib/libgtk-3.so.0(gtk_widget_get_preferred_height_and_baseline_for_width+0xa5)[0x7f27d4a93275]
/usr/lib/libgtk-3.so.0(+0x3a4adc)[0x7f27d4c49adc]
/usr/lib/libgtk-3.so.0(+0x34b773)[0x7f27d4bf0773]
/usr/lib/libgtk-3.so.0(+0x3514b1)[0x7f27d4bf64b1]
/usr/lib/libgtk-3.so.0(+0x39e6a3)[0x7f27d4c436a3]
/usr/lib/libgtk-3.so.0(+0x1ef183)[0x7f27d4a94183]
/usr/lib/libgtk-3.so.0(+0x1ee16e)[0x7f27d4a9316e]
/usr/lib/libgtk-3.so.0(gtk_widget_get_preferred_height_and_baseline_for_width+0xa5)[0x7f27d4a93275]
/usr/lib/libgtk-3.so.0(+0x34b773)[0x7f27d4bf0773]
/usr/lib/libgtk-3.so.0(+0x3514b1)[0x7f27d4bf64b1]
/usr/lib/libgtk-3.so.0(+0x3952f3)[0x7f27d4c3a2f3]
/usr/lib/libgtk-3.so.0(+0x1ef183)[0x7f27d4a94183]
/usr/lib/libgtk-3.so.0(+0x1ee16e)[0x7f27d4a9316e]
/usr/lib/libgtk-3.so.0(gtk_widget_get_preferred_height_and_baseline_for_width+0xa5)[0x7f27d4a93275]
/usr/lib/libgtk-3.so.0(+0x1ef183)[0x7f27d4a94183]
/usr/lib/libgtk-3.so.0(+0x1ee16e)[0x7f27d4a9316e]
/usr/lib/libgtk-3.so.0(gtk_widget_get_preferred_height+0x81)[0x7f27d4a934b1]
/usr/lib/libgtk-3.so.0(+0x1eec3e)[0x7f27d4a93c3e]
/usr/lib/libgtk-3.so.0(+0x1ee16e)[0x7f27d4a9316e]
/usr/lib/libgtk-3.so.0(gtk_widget_get_preferred_height_and_baseline_for_width+0xa5)[0x7f27d4a93275]
/usr/lib/libgtk-3.so.0(+0x8716c)[0x7f27d492c16c]
...
Aborted

And I already try  sudo pacman -S pixbuf2 it still this way

What's wrong / what should be happening instead:

Strace of the failing command, if applicable:  (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).

For WSL launch issues, please collect detailed logs.

microsoft/WSL#4106

#4106

Probably not in this case; emacs-gtk wouldn't have made it to the first warning, nvm the hard error. That native "Native gl" checkbox in VcXsrv is backwards; that might be a place to start (but probably isn't it).
Works here on Focal. You'll get better eyeballs forums related to the products involved (mostly Arch forum I suppose). That error "Unrecognized image file format" is not WSL actionable. Probably something (image related) not installed/configured in your userspace but won't speculate wut.

I don't why but i reboot
emacs  and startxfce4 can show graphic interface


notification when message fails to send

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @tneot01 in #android-requests.

Should be pretty easy. Only show the notification is the app is active and the currently active chat is not the one that had the send failure

We have this in place already, it was just broken on Android 12


date should use the chrono crate and not time

We are mixing time and chrono in the project. So, we should only use chrono to facilitate the maintenance.
$ rg "^time =" src/uu/date/Cargo.toml
21:time = { workspace=true }

I would like to pick this up.

sure, please give a try ;)


Fix indentation for poise init example

Description of change
First line in the generated src/lib.rs file for poise project was wrongly indented. Fixing the indentation in indoc! fixes it.

Github displays it kind of strangely, but it is just an unindent of 8 spaces for all but the first line.

The changes here reduced the indentation by 1 tab, but the first line in indoc uses spaces. Aren't all lines supposed to have the same indentation character?


Qcad <IP_ADDRESS>

Motivation for this change

update to <IP_ADDRESS>
fix problem with loading shared library for sqlite of the qcad drawing library

Regarding the shared library: I don't fully understand the problem here. Suggestions welcome.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS

[x] Tested execution of all binary files (usually in ./result/bin/)

I know this is only an update, but the derivation is not supposed to take qt5 as argument: https://nixos.org/manual/nixpkgs/stable/#qt-default-nix-co-1

I know this is only an update, but the derivation is not supposed to take qt5 as argument: https://nixos.org/manual/nixpkgs/stable/#qt-default-nix-co-1

thanks for this hint, I made a separate PR for that: https://github.com/NixOS/nixpkgs/pull/98327


Performance test suit

Its time to start adding some checks to the operations (without taking into account latencies with external storages) since caching should be as transparent as posible for the users.

It is probably worth it to use pytest-benchmark plugin. Maybe by just benchmarking the CMDS in the test_cache.py would be enough

Not worth the effort, will reopen in case functionality that could add a big impact in performance is added


Add icons to the Navlinks in the Navbar

Hello,
Can I contribute by adding attractive icons to the NavLinks present on the navbar section.

Please assign me this issue under ggsoc'24.
Thank you

I am participating in GSSOC'24. I am interested in resolving this issue. Could you please assign this issue to me under GSSOC'24 with appropriate level labels?


property ~~ [] SQL Syntax is Broken

When you try run a query that gets models based on the elements in an array and the array is empty, like this:
MyModel.query(on: request).filter(\.id ~~ [])

Instead of generating a WHERE (false) statement, it creates
WHERE (`mymodels`.`id` false)

This has been fixed and a test added in #114


EasyGCP stack published to registry

What problem are you facing?
Need to configure all GCP environment resources required to deploy application stacks like sample-stack-wordpress including: provider, secret, cluster class, network, subnets, managed service access, resource classes, etc.
How could Crossplane help solve your problem?

Provide an EasyGCP kind that will generate all necessary resources
Support easy customization of the Stack by forking / copying the repo

Related Issues

#1096 Design for Easy Stack Resources

Publishing works but Upbound registry doesn't support anonymous registry yet and *StackInstall objects do not support private registries. So, this is effectively blocked by https://github.com/crossplaneio/crossplane/issues/505


how to duplicate the results in paper?

Hi, I follow the suggested code and pre-trained model. But I cannot get the results listed in paper.
I change the batch size from 1024 to 256 and lower the lr_scale from 100 to 25. Is there any suggestion on how to change other hyper-parameters?
Thank you!

Please use the default hyperparameters listed in our paper. Especially the lr_scale should be set to 100, which promotes stable trainining and good performance. Thanks


"read-more-button" for long texts in search results

Example: http://localhost:8000/cm_search/search_result/?page=1&query=hamburg

done


Possible visual shift on feed tab bar when pinned feeds load + did not correctly remove what's-hot as default in prod

Describe the bug

The Feeds ✨button (added by #2033) could be rendered before the pinned feeds are loaded, which would cause a visual shift in the case that the user does in fact have custom feeds. I'm not sure if this would show up in prod, where the pinned feeds tend to load before the tab bar is rendered (at least for me), but I've been seeing it on the simulator which is much slower.
I removed what's-hot from being auto-pinned in a file that was no longer being used; need to remove it in the right place

To Reproduce
Steps to reproduce the behavior:
This bug isn't in prod. It was just added and is on the main branch.

Open the app on an account that has a pinned feed after quitting the app
Look at the feeds tab bar and notice that the Feeds ✨button sometimes flashes before the pinned feeds are loaded

Expected behavior
Given the prevalence of that flow (it will happen for every user who has custom feeds every time they open the app after quitting), I think it's better to wait until the preferences have loaded to display the Feeds ✨ button so there isn't a visual shift in the case that the user does have pinned feeds.
Screenshots
I will add a screen recording in a minute
Details

Platform: iOS simulator
Platform version: iPhone 15 running iOS 17
App version: main branch

@pfrazee putting up a PR for this. I don't know if it will be a problem in prod, but might as well fix it. I also noticed that in #2033 I removed what's-hot from DEFAULT_FEEDS for prod in src/lib/constants.ts, but as of 18 days ago that was no longer being used - I should've removed it from DEFAULT_PROD_FEEDS in src/state/queries/preferences. Updated the issue and will include that in the PR. Sorry to not have done this right the first time. Thanks.


initial add of dockerization of tests

Doesn't quite work (installs, but the bootstrap_apollo.sh doesn't quite work) as it doesn't understand docker or sudo from the initial context.
Something  like this should work
docker run bf1ad0638c63 /app/bootstrap_apollo.sh
But we get
docker run bf1ad0638c63 /app/bootstrap_apollo.sh
/app/bootstrap_apollo.sh: line 6: docker: command not found
[BOOTSTRAP] Waiting while Apollo starts up...

Got this working somewhere else.


PYIC-6658: udpate Orchestrator stub JAR to match real orch JAR

Proposed changes
What changed

removes persistent_session_id from stub as real orch JAR does not have this
adds jti to orch stub JAR
adds drivingPermit and returnCode claims and re-names socialSecurityNumber -> socialSecurityRecord

Why did it change
We had a P1 incident recently caused by our the JAR provided by the orchestrator stub differing from the JAR received in production. This PR ensures that there are no discrepancies between a JAR from the orch stub and one from the real orch.
Issue tracking

PYI-6658

Best as I can tell this is correct, although perhaps not complete (see comment). Hoping @billrdunn or @isaac-GDS can have a more thorough review tomorrow


fix: set keys of heading shortcuts correctly

[x] I read the contributing guide
[x] I agree to follow the code of conduct

Summary
The keys of the heading shortcuts are not set correctly.
How did you test this change?
Automated tests.

Thanks for your contribution.


Alternative event loop ?

Hello,
Is uWebSockets tied to libuv's event loop, or could it be made so that the event loop be chosen by the user of the library ? For instance to use Qt's, boost::asio's, or the C++ Networking TS's io_service ?
Thanks

The idea is to depend directly on (a very small portion of) libuv (uv_poll_t, uv_async_t, uv_timer_t) so that the library can be used both in stand alone C++ or as an addon in node.js. However I also wanted to have it run ontop of mTCP and other crazy tech so I started this little side project µUV which is a reimplementation of the uv_poll_t, uv_async_t and uv_timer_t directly ontop of Linux epoll. So with this you can actually remove libuv as a dependency and instead link to µUV.
µUV is a lot more lightweight and also faster than libuv but I did not see any interest in it so I stopped maintaining it. It is located in uUV.cpp and uUV.h and is currently not updated but you should be able to implement a similar "backend" ontop of anything. Basically you need to implement those three features of libuv in a substitute library.

Okay, good to know. Thanks.

There are now experimental ASIO support as well as raw epoll. New backends can be added very nicely now. Will be in next version :+1:

nice! this will be interesting to benchmark.

IKR? But it is not fully complete, just got it working enough to be sure it will be possible. If you look in Asio.h you get the idea


Added CLI for M365 version for script "Fetch User Profile Properties From Site Collection And Export To CSV"

Added CLI for M365 version for script on issue #279

@Adam-it I've implemented a fix for this issue. Could you please check if it works on your end?

Hi @Adam-it @MathijsVerbeeck is there any changes left to make? Im looking to merge and get the sample live 😃

@pkbullock It's up to @Adam-it to review. For me, it's ready to merge 😁

Oh sorry both for keeping you waiting.. i totally forgot/missed I was going to have another look at this 😱🙁 🙏
I will assign myself to it and have a quick check after Nikodem goes to sleep 🙂.
Will keep you posted on this one

@Adam-it - no worries, family first, when you have a moment.
Thanks @MathijsVerbeeck for confirming :-)

@MathijsVerbeeck for a great sample, thank you!! 👏😊 This should be live shortly 😊
@Adam-it appreciate the review :-)


Custom component conflicts with HomeAssistant's modbus integration.

First and foremost, thank you for this custom component, it's very useful and the install is a breeze (only need to enable ModBus capabilities on the heatpump), great work.
However I did find this issue when I tried to enable Modbus integration with Home Assistant:

Version of the custom_component

VERSION = "0.0.1"
Configuration

NA

Describe the bug
Using this custom component with Home Assistant's modbus integration enables results in the custom component not being able to load, since both use pymodbus library but version 3.1.3 for Home Assistant and version 2.5.3 for this custom component.
Forcing this custom component to use pymodbus 3.1.3 fails, since it seems to be using some calls and/or dependencies that are no longer supported in this version.
Debug log

Logger: homeassistant.setup
Source: setup.py:213
First occurred: 1:53:52 PM (1 occurrences)
Last logged: 1:53:52 PM

Setup failed for custom integration idm_heatpump: Unable to import component: No module named 'pymodbus.client.asynchronous'

Thanks for reporting the issue. Seems it only affected new installations so I didn't notice it.
Everything should be fixed in the new v0.2.0 release. It should now also be easier to install this custom integration via HACS. Take a look at the new README.


Spelling Mistake :)

Simple spelling mistsake I found in inspect element settings.
Check out the image attached with this thread.
Thanks,

Hi, that's actually not a spelling mistake. The debugger is DevTools. The debuggee is the thing that you're debugging... the viewport in other words.


META-16566 feat: add interface for new schema CRUD access

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[x] Links to related issues: META-16566 (LI internal)
[ ] Tests for the changes have been added/updated (if applicable)
[x] Docs related to the changes have been added/updated New Schema Migration (LI Internal)

Oh I just remembered something @yangyangv2. We should avoid using internal ticket IDs (in commit message) in this project since it is open source.


NavList impossible to dynamically open with defaultOpen

Description
I can't open a NavList programmatically. It only stays open if you set aria-current="page".
I have a nested NavList which contains NavList.SubNav. All is well, it works great.
The list looks something like this:

Home
About

Things
General

General 1
General 2

Contact

When I'm on /about/things the "About" and then "Things" is opened:

But suppose I don't want it to be controlled by the URL. But some other reason. For example, I might want to expand ALL items fully all the time.
An application of this would be if you have a tree of pages, and a search/filter and when something is searched for, I remove all that don't match but to make it clear, I want all nodes fully opened. I.e. to not depend on click state, but controlled dynamically from the outside.
Steps to reproduce

Clone https://github.com/peterbe/primer-navlist-repro
npm install
npm run dev
View on http://localhost:3000
Click around.  Nothing hidden/collapsed.
Actual result
Nothing happens.
Version
35.32.0
Browser
No response

Hi!
Thanks for the repro, really appreciate it! It's in our inbox for prioritisation now, you'd hear from soon :)
Tiny optional repro tip, no big deal: Love getting a repro, I would love it even more if the repro uses the storybook setup in primer/react because then we can use the pull request tooling we have in the repo 😇

Thanks for filing! This sounds like a feature request as I don't believe it's functionality we had scoped in to the NavList originally. That said, I think it would be great for us to discuss at Primer Patterns (cc @tallys) to explore whether this is a use case we want to support.

sounds like a feature request as I don't believe it's functionality we had scoped

yeah maybe. It's unclear. If anything, it's a bug in intuition :)
You'd expect a prop called defaultOpen mean that it's open by default. But I can see how it can also be interpreted as "open, yes, unless there's an override reason not to".

My intention, by the way, is to build a search filter above the left-hand sidebar on docs.github.com that filters the big navlist. If you type something into it, it would hide all the leafs that don't match-by-title, and hide all the parents that have 0 leafs in them. But it's not yet scoped work. Just a prototype.

@peterbe - we'll send you an invite to the next Primer patterns working session to talk through your specific use case.

We chatted about this in Primer Design Pattern meeting.
The origins of this issue was that; it's a bug (in React primer).
But more importantly, it's worth considering if it's accessible at all, even if it was possible (...with React Primer).
As a reminder, the prototype that stirred this looks like this:

It rewrites the tree of links in the sidebar to only show leaves that match the search input and/or nodes in the tree that contain a leaf that matches.
This would/could/should reduce the number of items shown so that they eyes can easily scan and find the best title to click on.
The problem is that after the filtering has been applied you now have to click to expand the NavList tree to see the good matches. It would be easier if, typing "contain", automatically makes the sidebar look like this:

But it's not possible.
However...
We pondered if it's even a good idea. How can it be accessible by default? Is it obvious with a live region that the listing has refreshed and is now showing matches?
Another option is that of the Microsoft Learn site. For example: https://learn.microsoft.com/en-us/azure/data-explorer/
They too have long list of options in their side bar. And they place a search input widget above the tree ("Filter by title"). But what they do is that they do an autocomplete-like widget to find within the tree. That could be an option for us (GitHub Docs) too.
With that in mind; it's not obvious that React Primer has a bug here. Yes, it became impossible to implement the prototype the intended way, but perhaps the prototype idea was wrong in the first place.
@mperrotti @siddharthkp Do you want to close this or leave it open?

The origins of this issue was that; it's a bug (in React primer).

I'd argue that this isn't actually a bug. defaultOpen follows a common React pattern where props that start with default or initial (e.g.: defaultValue) are just intended to initialize state.
That being said, I think we should close this issue. If we find an accessible way to have a controlled NavList component, then we can revisit this.

Sounds good @mperrotti, we can always reopen if anything


from future import print_function

Should fix #1   Be ready for Python 3

Wow, @cclauss contributes to everything 👋  2.3 repos 😁


Invalid deleteMany invocation in relational schema

Bug description
Following error when calling deleteMany on (empty) box table with relations.
When invoking deleteMany on any other table, no error occurs.
    Invalid `prisma.box.deleteMany()` invocation
    Invalid response data: the query result was required, but an empty Object((Weak)) was returned instead.
      at PrismaClientFetcher.request (node_modules/@prisma/client/runtime/index.js:1:47490)

How to reproduce
import { PrismaClient } from "@prisma/client";

const prisma = new PrismaClient();

await prisma.box.deleteMany({});

Prisma information
datasource db {
  provider = "postgresql"
  url      = env("POSTGRES_URL")
}

generator client {
  provider = "prisma-client-js"
}

model Calibration {
  id           Int      @id @default(autoincrement())
  box          Box
}

model Box {
  id                Int                @id @default(autoincrement())
  connectionHistory ConnectionHistory?
  calibrations      Calibration[]
}

model ConnectionHistory {
  id      Int                @id @default(autoincrement())
  box     Box
}

Environment & setup

OS: Mac OS
Database: PostgreSQL
Prisma version: 2.0.0-preview024 and 2.0.0-preview025
Node.js version: v13.1.0

Sure, this is what is inside the README.md:
CREATE TABLE "public"."Calibration" (
    "box" integer  NOT NULL ,
    "id" SERIAL,
    PRIMARY KEY ("id")
)

CREATE TABLE "public"."Box" (
    "connectionHistory" integer   ,
    "id" SERIAL,
    PRIMARY KEY ("id")
)

CREATE TABLE "public"."ConnectionHistory" (
    "id" SERIAL,
    PRIMARY KEY ("id")
)

CREATE UNIQUE INDEX "Box_connectionHistory" ON "public"."Box"("connectionHistory")

ALTER TABLE "public"."Calibration" ADD FOREIGN KEY ("box")REFERENCES "public"."Box"("id") ON DELETE CASCADE  ON UPDATE CASCADE

ALTER TABLE "public"."Box" ADD FOREIGN KEY ("connectionHistory")REFERENCES "public"."ConnectionHistory"("id") ON DELETE SET NULL  ON UPDATE CASCADE

Ah, you created the database with prisma2 migrate? We'll take that into consideration.

Yes, you're right created the database with prisma2 migrate, does this make a change?

No, it is just additional information that is good to have as context when looking into bugs 👍

I can reproduce this with preview025 but I can't reproduce this with 2.0.0-alpha.993
Can you try with the alpha version? Use npm install @prisma/cli@alpha @prisma/client@alpha to install the alpha version and run npx prisma2 generate

I tested it:
Can't reproduce it with 2.0.0-alpha.997.

Yay, thanks!


modal.action loading

Feature request 🚀

[ ] I will create Pull Request
[x] It's just a suggestion

Expected

Component or something else

<Button has loading attribute, might be useful for Modal.Action? not sure if this is out of scope
Examples
<Modal.action loading={loading}/>

Programme (Optional)
Others (Optional)

No, currently, Action does not inherit all Button component props.


Quantity of items in distribution is not always visible

Summary
I noticed that the Items in this distribution section has a bug in which the quantity of the item isn't always visible. As a consequence, it isn't clear how many are available for line items and can lead to confusion. We've heard in some cases distribution causing some confusion, and this might be one cause.

Ideally, we'll be able to keep the quantity visible for every additional item added.
How to reproduce

Login as a diaperbank user.
Goto http://diaper.test/diaper_bank/distributions/new
Set the storage location & click "+ Add another item"
You should see that the new line doesn't have the quantity

Things to Consider
Let's make sure that any other page that uses this form is also fixed.
Criteria for Completion

This should be a bulleted list of items that, if satisfied, would result in an acceptably complete Pull Request. Be as specific as you need to be. For example:

[ ] When a user clicks "+ Add another item", the quantity of the item is always visible

Looking at this!

Hello @valeriecodes are you still working on this?

No, I've unassigned myself


Incompatible with Electron v10.x.y+ when dealing with .asar

when Electron dealing with directory with .asar, will directly access options.withFileType.
See: https://github.com/electron/electron/blob/4594af595eab12e76034d0d0e94539ef390024bb/lib/common/asar.js#L597
and in graceful-fs v4.2.7 and above, will set options to null in some circumstances.
For example: https://github.com/isaacs/node-graceful-fs/blob/9ec3413c8eb1c073c42262bf5a2a8cdf556f68a7/graceful-fs.js#L113
when options sets to null, options.withFileTypes in Electron will cause error.
I suppose it is a bug.

currently I use yarn and set:
"resolutions": {
    "graceful-fs": "4.2.6"
 }

in package.json to lock graceful-fs in v4.2.6

I have a similar issue. The options = null should be replaced with options = undefined because null cannot be replaced with default parameters.
Because of that, I am having trouble running my electron application. I see errors with this module.


click event not firing in v10

After updating to JSDOM v10 div.click()  no longer fires the onClick listener attached to that node.
Event listener was attached node using following syntax:
node['onclick'] = function () {/*not related*/}

same code works in browsers
You can reproduce this in InfernoJS repository:
https://github.com/infernojs/inferno/tree/dev

update to JSDOM v10
npm run test:server  => click related tests fail
JSDOM 9.12 all works.

Did you check the new https://github.com/tmpvar/jsdom#executing-scripts ?

Closing since that is probably it, but happy to reopen if we missed something.


Add functionality for modifying lock files, e.g., adding a new dependency without generating the whole file from scratch.

the current behavior is good, it enables us to detect dependency resolution changes (the lockfile diff would be bigger than one single dependency update)


add convenience function to report which etree OWSLib is using (#276)

Thanks!  I am forwarding this to the pyGDP devs.


changing tabBadge number automatically with EventEmitter is not working

Ionic version:  (check one with "x")
[ ] 1.x
[x ] 2.x
I'm submitting a ...  (check one with "x")
[ x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

when the event emitter is fired, the subscribe recibes that value. and the new value is storing in the local variable, but the view shows the previous one until some other event happens, like a doRefresh, doInfinite, or touching the tab-bar, etc...
Expected behavior:

Immediately change that badge number
Steps to reproduce:

Related code:
export class TabsPage {
  public newNotifications;
  HomePageTab = HomePage;
  SearchPageTab = SearchPage;
  SendPageTab = SendPage;
  SubscriptionsPageTab = SubscriptionsPage;
  ProfilePageTab = ProfilePage;

  constructor(
    public sharedVariables: SharedVariables
  ) {

    this.sharedVariables.numberOfNotifications
      .subscribe(newNotifications => {
        console.log("new notification" + newNotifications);
        this.newNotifications = newNotifications;
      });
  }

}

this is the code on TabsPage component.
In the template I have  tabBadge="{{ newNotifications }}" and the weird part is that the log is showing perfectly, that means that the local variable is actually storing the new value, but as I mentioned above the badge don't update until other thing happens in the app.
I think this could have something to do with NgZone, but I also think that this must not be the correct behavior for this.
Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
insert the output from ionic info here

Hello! Thanks for opening an issue with us! As this seems like more of a support question of how to implement custom functionality, i will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!


Tag releases in repo

Would be great if you started to tag releases.
https://github.com/NekR/offline-plugin/releases
https://git-scm.com/book/en/v2/Git-Basics-Tagging

hey @andykenward, I have nothing against it actually, I just don't see yet why it's needed/makes sense. There is a https://github.com/NekR/offline-plugin/blob/master/CHANGELOG.md actually which has all the data.

@NekR But if you actually want to look at the code for each release via the CHANGELOG.md you can't. You have to search through the commit titles to find them and hope the one released on NPM is that one.
I honestly don't see why you wouldn't add a simple tag v.4.5.3 to the commit that is that version published to NPM.
I use git-flow workflow for this reason.
If you look at react releases and tags history. Don't you think that makes people's life easier?
Also allows people to use Github drop-down menu to quickly access tags

I'm going to be honest about this -- I don't use it because I'm too lazy. But I'll try to reconsider it.
@andykenward have absence of tags/releases made things harder for you? What exactly you were looking for?

Try npm version. It handles version number commit and tag for you.
npm version patch && git push && git push --tags && npm publish is a nice Workflow and not that much work.

 Using commitizen and cz-conventional-changelog

@sokra that's interesting, I didn't know about npm version. Thanks 👍

@TheLarkInn semantic-release seems too complicated (in comparison to npm version for example). But I'll check that too, thanks! :-)

Just to not forget: It may make sense to use this for GitHub Releases: https://github.com/zeit/release

Okay, I made my first release with npm version patch && git push && git push --tags && npm publish: https://github.com/NekR/offline-plugin/releases/tag/v4.5.4
I'll be trying other ways too though.

I started doing releases. I do them as @sokra suggested, seems fine enough to me. Thank you!
@andykenward thank you too for reporting this, I think we can close this now :-)


SWARM-1442: Include licenses deliverables.

NOT READY FOR MERGE YET!
This PR outlines additional configuration needed to generate licenses deliverables using wildfly-swarm-fraction-plugin (currently unreleased 61-SNAPSHOT).
To try it out run:

mvn clean package -DskipTests -Pgenerate-licenses
mvn clean package -DskipTests -Pgenerate-licenses -f pom-redhat.xml

The generated zip can be found at target/wfswarm-rest-http-8-SNAPSHOT-license.zip.
Note that the licenses-transform.xsl file will need some more tweaks as it looks like there are some artifacts which don't have license specified etc.

@kenfinnigan The PR was merged with a SNAPSHOT dependency - wildfly-swarm-fraction-plugin. I'm preparing another PR to sync with https://github.com/wildfly-swarm/wildfly-swarm/pull/638. So I can update the version once 61 is released.


Fix lit analyzer errors

Changes
The two culprits were no-unknown-attribute and no-incompatible-type-binding.

no-unknown-attribute errored because we marked attributes as @ignore so they wouldn't be documented but apparently Lit Analyzer doesn't like that because it also then thinks they don't exist.
no-incompatible-type-binding errored because we're passing values Lit Analyzer thinks are strings into what is effectively an enum type. Having to add comment types in these cases feels pretty bad so not sure if anyone has any thoughts on disabling this rule.

I would be pro turning off no-incompatible-type-binding because it's also the reason we are now forced to use boolean-attribute="true" instead of the more succinct boolean-attribute


Support query script by lock script hash

Sometime we want query the script by lock script hash.
The typical example is query sudt owner's script. Now we can query the script in ckb-cli and explorer:

ckb-cli wallet get-live-cells --lock-hash <lock-hash>
explorer https://pudge.explorer.nervos.org/address/0x787e97af6860c58fcecd12653714330c003f5b960e09f027295a49e3c41d609f

But if user want query the script in sdk code,  it's not easy to do it.
So, can ckb-indexer provider a way to query the script by lock script hash?

I think you can use this sudt type script to query the first transaction to find the issuer's lock script, and then use the issuer's lock script to get the live cell:
echo '{
    "id": 2,
    "jsonrpc": "2.0",
    "method": "get_transactions",
    "params": [
        {
            "script": {
                "code_hash": "0xc5e5dcf215925f7ef4dfaf5f4b4f105bc321c02776d6e7d52a1db3fcd9d011a4",
                "hash_type": "type",
                "args": "0x6fe3733cd9df22d05b8a70f7b505d0fb67fb58fb88693217135ff5079713e902"
            },
            "script_type": "type"
        },
        "asc",
        "0x1"
    ]
}' \
| curl -H 'content-type: application/json' -d @- \
https://testnet.ckb.dev/indexer

{
  "jsonrpc": "2.0",
  "result": {
    "last_cursor": "0xa0c5e5dcf215925f7ef4dfaf5f4b4f105bc321c02776d6e7d52a1db3fcd9d011a4016fe3733cd9df22d05b8a70f7b505d0fb67fb58fb88693217135ff5079713e902000000000009069c000000010000000001",
    "objects": [
      {
        "block_number": "0x9069c",
        "io_index": "0x0",
        "io_type": "output",
        "tx_hash": "0xef0cd57d61d86dfe0147f7dc786710bb797ba23769318a2884a2cffa5346d992",
        "tx_index": "0x1"
      }
    ]
  },
  "id": 2
}


Issue with hdf backend when running nested sampling.

When attempting to run a fit using nested sampling either on my laptop or under the specific setup I use on CC the following error occurs:
Traceback (most recent call last):
  File "/home/pjs902/.local/bin/GCfitter", line 307, in <module>
    fit_func(**vars(args))
  File "/home/pjs902/.local/lib/python3.9/site-packages/fitter/core/main.py", line 906, in nested_fit
    backend.update_intial_batch(results)
  File "/home/pjs902/.local/lib/python3.9/site-packages/fitter/core/main.py", line 288, in update_intial_batch
    grp[key][-n_grow:] = val
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "/cvmfs/soft.computecanada.ca/easybuild/software/2020/avx2/MPI/intel2020/openmpi4/hdf5-mpi/1.12.1/lib/python3.9/site-packages/h5py-3.5.0-py3.9-linux-x86_64.egg/h5py/_hl/dataset.py", line 942, in __setitem__
    mspace = h5s.create_simple(selection.expand_shape(mshape))
  File "/cvmfs/soft.computecanada.ca/easybuild/software/2020/avx2/MPI/intel2020/openmpi4/hdf5-mpi/1.12.1/lib/python3.9/site-packages/h5py-3.5.0-py3.9-linux-x86_64.egg/h5py/_hl/selections.py", line 264, in expand_shape
    raise TypeError("Can't broadcast %s -> %s" % (source_shape, self.array_shape))  # array shape
TypeError: Can't broadcast (13,) -> (13, 17)

This happens regardless of if I remove any left over backend files from previous runs. I'm running on commit f14291300c02eb206acc9b4fb5871ecb1844532d from the develop branch.

fitter_NGC0104.log
slurm-65700139.log

Just to update the progress here, I've narrowed this down to an issue with my data file when I include the pulsar data. Adding the extra proper motion data doesn't break anything but adding the pulsar data, even with the pulsar likelihood disabled breaks it.

Ok, just to confirm what we speculated earlier, I didn't actually have the pulsar likelihood disabled like I thought I did. Just tested it with it properly disabled and it works fine. Haven't looked into it at all but now it seems more likely that a bunch of (or all of) the initial samples are failing, making the array of samples empty and causing the size mismatch when it tries to save to the backend.

To once again document the progress over the past week, I'm now pretty sure this has nothing to do with anything going on inside the pulsar likelihoods themselves. I've tested with each of the pulsar likelihoods disabled and the issue still occurs. I've also had a look at dynesty and they specifically handle the case where all of the initial samples are returned as -inf and they give a specific error message for that case which we haven't yet reached. Additionally, I've tested forcing the pulsar likelihoods to just return 1 instead of whatever value they actually calculate. So, based on these tests I'm pretty sure the pulsar likelihoods themselves are not to blame.
I have however found some very very strange behaviour by dumping the results dictionary at the time of the crash:
{'bound_iter': 0,
 'bound_orig': 0,
 'delta_logz': 1e+300,
 'eff': 0.9900990099009901,
 'h': -9.900990099009874e+297,
 'loglstar': -1e+300,
 'logvol': -0.009950330853168092,
 'logwt': -1e+300,
 'logz': -1e+300,
 'logzvar': -9.851812725908975e+295,
 'ncall': 1,
 'ustar': array([0.57146696, 0.75116869, 0.94833975, 0.35921788, 0.63676913,
       0.32263736, 0.50516653, 0.85124256, 0.31663921, 0.32336887,
       0.78167389, 0.38656441, 0.24449442, 0.63153795, 0.45676492,
       0.69988187, 0.50224247]),
 'vstar': array([12.71493837,  3.75833175, 14.2509264 ,  1.7960894 ,  2.22869194,
        0.36452747,  7.577498  ,  2.70248513,  0.06074136,  0.80101634,
        3.47601734, 38.65644097,  3.46696655]),
 'worst': 0,
 'worst_orig': 0}

In particular:
results['vstar'].shape = (13,)
results['vstar'] = array([12.71493837,  3.75833175, 14.2509264 ,  1.7960894 ,  2.22869194,
        0.36452747,  7.577498  ,  2.70248513,  0.06074136,  0.80101634,
        3.47601734, 38.65644097,  3.46696655])
results['ustar'].shape = (17,)
results['ustar'] = array([0.57146696, 0.75116869, 0.94833975, 0.35921788, 0.63676913,
       0.32263736, 0.50516653, 0.85124256, 0.31663921, 0.32336887,
       0.78167389, 0.38656441, 0.24449442, 0.63153795, 0.45676492,
       0.69988187, 0.50224247])

The ustar and vstar arrays are different sizes. I'm entirely unsure what could be causing GCfit to infer 4 additional parameters when a pulsar likelihood is enabled. We do pass around a few extra things like the cluster's position and proper motion but I'm not sure how or even if they could affect the number of parameters that GCfit gives to dynesty.

Final resolution here: I was using ViTables to modify the datafiles and it was apparently appending some extra metadata in the form of HDF attrs. This meant that when the length of the variable initials was read from the observations there were 4 extra elements stuck on the end.


Style fixes

As per the suggestion on #40 I've run the code through clang-format. I've also added the style guidelines to CONTRIBUTING.md.
The style used is pretty much Google style. I ran clang-format with -style={BasedOnStyle: Google, BraceBreakingStyle: BS_Stroustrup} -r -i {3DSMax,Arnold,Maya,Python,Softimage}/**/*.{cpp,h} (and recursive wildcards turned on in bash).
Fixes #40

Does the project still compile?  If you say yes, I will merge it.

Sorry I should have mentioned this in the description. I have only tested that the Maya plugin compiles because it's the only one that I can get compiled on master.

thx!


[BUG] AKS EE install does not fail when Azure Arc does not have required permissions

Describe the bug
When setting up AKS EE with Azure Arc with a SP that does not have permissions to READ the resource group Azure Arc is set to be provisioned at the install succeeds and Azure Arc is initialized in the cluster, however Azure Arc pods will start to fail with certificate and volume mount issues.
When uninstall Azure Arc from the cluster and reinstalling it with Azure CLI command (using the same SP as above):
az connectedk8s connect --name aks-edge-stack-test --resource-group ***

We'll end up getting an error for not enough permissions to read resource group:
az connectedk8s connect -n aks-edge-stack-test -l eastus2 -g *** --subscription ***
This operation might take a while...

The outbound network connectivity check has failed for the endpoint - https://eastus2.obo.arc.azure.com:8084/
This will affect the "cluster-connect" feature. If you are planning to use "cluster-connect" functionality , please ensure outbound connectivity to the above endpoint.

The required pre-checks for onboarding have succeeded.
Http response error occured while making ARM request: (AuthorizationFailed) The client '***' with object id '***' does not have authorization to perform action 'Microsoft.Kubernetes/connectedClusters/read' over scope '/subscriptions/***/resourcegroups/***/providers/Microsoft.Kubernetes/connectedClusters/aks-edge-stack-test' or the scope is invalid. If access was recently granted, please refresh your credentials.
Code: AuthorizationFailed
Message: The client '***' with object id '***' does not have authorization to perform action 'Microsoft.Kubernetes/connectedClusters/read' over scope '/subscriptions/***/resourcegroups/***/providers/Microsoft.Kubernetes/connectedClusters/aks-edge-stack-test' or the scope is invalid. If access was recently granted, please refresh your credentials.
Summary: Failed to check if connected cluster resource already exists.

Because of this error the Azure CLI command never installs Azure Arc in the cluster, because they would fail to start as we saw with the AKS EE installation.
To Reproduce
Steps to reproduce the behavior:

Set up AKS EE with Azure Arc with a SP that does not have permissions to READ the resource group Azure Arc
See Azure Arc pods fail to start

Expected behavior
AKS EE should check that Azure Arc has the required permissions to proceed on the provided SP like the Azure CLI command and fail the installation process if not enough permissions are found.
Environment (please complete the following information):

AKS Edge Essentials Version 1.26.6-<IP_ADDRESS>
Kubernetes version 1.26.6-<IP_ADDRESS>
Windows Host OS (please complete the following information):

Edition: Windows Server 2019 Standard
Version: 10.0.17763 Build 17763
Virtual Machine: Virtual machine in a local datacenter

We have created a bug (25840088) to track this internally. I will post any updates here


Fix wrong message for failure of MODBUS write and clean others

An error message "Read [...] impossible" for writing errors was confusing.
The messages used a mix of "Register" and "register". Use always "register".
Replace "Holding" and "Input" by lowercase variants (see Growatt documentation).

Description
See commit message above.
How Has This Been Tested?

[x] Not applicable (only string modifications)

Inverter type

[ ] Simulated inverter
[ ] Inverter type e.g. Growatt 1500 TL-X

Stick type

[x] Shine X
[x] Shine S
[ ] Lolin32
[ ] Nodemcu32

Write errors can be caused by different reasons – not connected, but also protected registers which don't accept certain values or which may only be written under certain conditions (for example soft power off). That's too complicated for a short error message, so don't try to give a (possibly wrong) reason.
Read and write errors can also be caused by too fast operations. Maybe instead of "Read [...] impossible - not connected?" it would be better to simply say "Read [...] failed".


fix: apply a quick fix to fix the broken staked relayer page

Can you please add the same quick fix to the vault page?

Yes, done.


fix: not remove old VrfParamsChanges to validate old dag block correctly

Purpose
Keep old VrfParamsChanges to validate old dag block correctly

I do not like this solution, we should try to save as little as possible. I will approve it for now, but this should be just temporary and we should figure out how to deal with old dags

I do not like this solution, we should try to save as little as possible. I will approve it for now, but this should be just temporary and we should figure out how to deal with old dags

@kstdl and @MatusKysel can we save only the info needed to recompute these values should we need them for when a very old dag block is generated?

I do not like this solution, we should try to save as little as possible. I will approve it for now, but this should be just temporary and we should figure out how to deal with old dags

@kstdl and @MatusKysel can we save only the info needed to recompute these values should we need them for when a very old dag block is generated?

We should merge this so we can confirm that this is the problem and let's try to figure out how to deal with old DAGs, bacause this will be issue for rewards also. With this current approach we need to save a lot of data


Option for download stock_prices.csv

Is there a plan to have a system to easily download the stock price for all indices?

I can find how using yfinance lib.
# Define the ticker list
import pandas as pd
tickers_list = ['GOOG', 'AAPL', 'FB', 'BABA', 'AMZN', 'GE', 'AMD', 'WMT', 'BAC', 'GM', 'T', 'UAA', 'SHLD', 'XOM', 'RRC', 'BBY', 'MA', 'PFE', 'JPM', 'SBUX']

# Fetch the data
import yfinance as yf
data = yf.download(tickers_list,'2000-1-1')['Adj Close']

# Print first 5 rows of the data
print(data.head())

# Save file
data.to_csv('stock.csv')

Closing because it seems like you've solved the problem. Please reopen if not!


Change the border color of the selected element

 Issue by yasassri
Monday Oct 16, 2017 at 12:25 GMT
Originally opened as https://github.com/ballerina-lang/composer/issues/3763

Can we change the color of the border of a code segment? If e have a large code block e.g: a while loop. It is difficult to recognize the boundary of the loop. Can we change the color when the element is selected?

 Comment by maheeka
Wednesday Nov 15, 2017 at 18:08 GMT

We do have a boundary for the while loop in design view. Are you referring to having another level of highlighting?

Composer is discontinued hence closing the issue.


Addition of DHL_Products class

This class contains all dhl products and their attributes, such as compatible services, min and max sizes and weights, as well as localized namings.
I used the official infographics and charts of the DHL dev website to assemble this list.
PS: This is my first ever PR on Github, tell me if i'm doing something wrong :)

Hello,
first thanks for contributing. Your Pull-Request looks fine so far, please use an extra branch next time, so when you adding more changes to your master branch these changes don't appear here. Now if you add stuff to your master branch these will also come in here.
Now to your Pull-Request: I don't get for what you want to use this? Do you have an example or such stuff I'm unsure if I should merge this because may it confuses more than it helps?
Maybe more details would help me to understand what you want to do with it^^

Hi,
okay yes I understand about the branching.
Well we use your api for business customers running online shops. They use a UI for creating shipments within the admin office of their store.
To know which services, and min-max weights and sizes are applicable to the various DHL products, this list is needed and so i assembled it from the tables given by DHL.
It is not a very innovative or brilliant addition to your already very nice SDK, it's just a time saver really.
For example my shipment creation UI has a html <select> for the desired DHL package type, and upon selection displays checkboxes for all available services such as Go Green, Day of delivery, and so on, as well as providing the internal validation systems with information to quickly validate user input for package sizes and weight.

The Idea is not bad, I will merge it but change it a little plus I can use this for validation =)
I will merge it with my changes on weekend then

Done =) I used Objects for every Product-Info instead of using so long arrays. You can access them now like this:
// Get Max-Height for "NATIONAL_PACKAGE"
DHL_ProductInfo::getInfo(DHL_ShipmentDetails::PRODUCT_TYPE_NATIONAL_PACKAGE)->getMaxHeight();


Chat app like signalir?

is it possible with that?

very very good

@praeclarum  has created this nice example: https://github.com/praeclarum/OouiChat


Replace Ember.assign usage with Object.assign

Follow up to #299.

The embroider safe test failing seems like a timing issue rather than an issue with this PR. maybe retriggering will make it pass


Bug when updating time/date on an event page

When changing the time from 16:30 to 16:15 (on a published event page for the autumn conference), the new time (and date) disappears when changing to Norwegian, and the updated Norwegian time/date changes when changing back to English. But if we publish the English page and then change to Norwegian and publish that it works as expected.

Seems like you don't have to change anything in the time - just switching between the different languages seems to reset the date and time fields to blank...

@fernandolucchesi @padms @millianapia
Should be fixed now, can't really feature flag it but everything looks to work again

@meols Should be fixed on the dev dataset now https://studio-global-development-equinor-web-sites-dev.c2.radix.equinor.com/desk

Thanks @SvSven - looks great!


Added Drag'n'Drop ability in remarkise

I love remark.js and like that it is possible to just open a markdown file from another server via remarkise. However, at work I am not allowed to upload my presentation files to servers. That is the reason why I added the support for drag and drop.
It uses the FileReader API, and the drop-area is not shown if the browser does not support this feature.

Nice, thanks!


Word wrapping changes location

https://github.com/yuku/textcomplete/tree/main/packages/textcomplete-textarea is using https://www.npmjs.com/package/textarea-caret which said in the readme that it copies text after the caret too to consider word wrap complication and that's why I tried this.
But I think the issue here is rather about that math.max not detecting that a new line has started because of word wrap.
I suppose if the y coordinate of selection start is higher than y coordinate of space/newline, then we have to assume word has wrapped and probably set x coordinate to extreme left.

Good spot!

But I think the issue here is rather about that math.max not detecting that a new line has started because of word wrap.

This isn't the case. Automatic word-wrapping is purely a visual artifact and doesn't introduce a "\n" in the value.

Yes, and that's why it doesn't "detect" it when looking for \n


feature/checkstyle-integration

add required checkstyle configs
updated poms as per checkstyle configs
fixed checkstyle violations

Closes #602

Hi @williewheeler
I have fixed merge conflicts and fixed checkstyle violations that came due to those changes.
Please review and merge this PR.
Thanks

@0001vrn Merged -- thank you very much for this submission.


Firebase for Flutter CodeLab User Interface Code May Need Updating

Problem
On using the user interface code provided for the Firebase for Flutter CodeLab, I encountered the following compilation error:
Initializing hot reload...
Syncing files to device Android SDK built for x86...

Compiler message:
lib/main.dart:46:50: Error: The argument type 'List<DocumentSnapshot>' can't be assigned to the parameter type 'List<Map<dynamic, dynamic>>'.
 - 'List' is from 'dart:core'.
 - 'DocumentSnapshot' is from 'package:cloud_firestore/cloud_firestore.dart' ('../../../../Dev/flutter/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-0.13.4/lib/cloud_firestore.dart').
 - 'Map' is from 'dart:core'.
        return _buildList(context, snapshot.data.documents);

Platform
Deploying to an Android emulator executing on a Mac.
Steps to Reproduce

Replaced the created flutter app's main.dart code with that provided on https://codelabs.developers.google.com/codelabs/flutter-firebase/#4, as directed.
Upon hot reload occurring, a recompilation was triggered, and the above compilation error was seen.

Potential Workaround/Resolution

Found could get past the issue by using the type DocumentSnapshot rather than Map in themain.dart file:

import 'package:cloud_firestore/cloud_firestore.dart';
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

final dummySnapshot = [
  {"name": "Filip", "votes": 15},
  {"name": "Abraham", "votes": 14},
  {"name": "Richard", "votes": 11},
  {"name": "Ike", "votes": 10},
  {"name": "Justin", "votes": 1},
];

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Baby Names',
      home: MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  @override
  _MyHomePageState createState() {
    return _MyHomePageState();
  }
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text('Baby Name Votes')),
      body: _buildBody(context),
    );
  }

  Widget _buildBody(BuildContext context) {
    return StreamBuilder<QuerySnapshot>(
      stream: Firestore.instance.collection('baby').snapshots(),
      builder: (context, snapshot) {
        if (!snapshot.hasData) return LinearProgressIndicator();

        return _buildList(context, snapshot.data.documents);
      },
    );
  }

  Widget _buildList(BuildContext context, List<DocumentSnapshot> snapshot) {
    return ListView(
      padding: const EdgeInsets.only(top: 20.0),
      children: snapshot.map((data) => _buildListItem(context, data)).toList(),
    );
  }

  Widget _buildListItem(BuildContext context, DocumentSnapshot data) {
    //final record = Record.fromMap(data);
    final record = Record.fromSnapshot(data);

    return Padding(
      key: ValueKey(record.name),
      padding: const EdgeInsets.symmetric(horizontal: 16.0, vertical: 8.0),
      child: Container(
        decoration: BoxDecoration(
          border: Border.all(color: Colors.grey),
          borderRadius: BorderRadius.circular(5.0),
        ),
        child: ListTile(
          title: Text(record.name),
          trailing: Text(record.votes.toString()),
          onTap: () => print(record),
        ),
      ),
    );
  }
}

class Record {
  final String name;
  final int votes;
  final DocumentReference reference;

  Record.fromMap(Map<String, dynamic> map, {this.reference})
      : assert(map['name'] != null),
        assert(map['votes'] != null),
        name = map['name'],
        votes = map['votes'];

  Record.fromSnapshot(DocumentSnapshot snapshot)
      : this.fromMap(snapshot.data, reference: snapshot.reference);

  @override
  String toString() => "Record<$name:$votes>";
}

Closing this issue as getting to https://codelabs.developers.google.com/codelabs/flutter-firebase/#8, it becomes clear making these changes is part of the plan! 👍


BUG: rekor search

I intermittently get errors when trying to verify attestation. I suspect it's a rekor problem?
calculated root:
[132 232 216 48 108 59 50 197 236 185 146 185 227 68 190 133 21 213 122 121 1 147 162 124 107 174 49 111 31 250 222 55]
 does not match expected root:
[23 93 206 14 188 138 123 76 20 90 197 85 245 154 233 32 233 26 65 69 91 221 43 184 6 252 85 24 60 92 168 117]: verifying inclusion proofverification failed: could not find a matching signature entry
exit status 2while verifying the same provenance

calculated root:
[128 119 111 49 254 53 189 249 195 141 0 27 246 84 213 157 191 22 221 250 116 235 9 254 122 25 214 232 229 215 253 244]
 does not match expected root:
[236 214 7 183 14 217 72 75 194 121 46 12 227 70 223 102 211 40 95 189 150 32 202 72 173 127 241 7 182 167 110 244]: verifying inclusion proofverification failed: could not find a matching signature entry
exit status 2

/cc @asraa

Hmmmm this error is coming from verifying the inclusion proof for the log entry.
I had seen it once before running go test but am having trouble reproducing it. Do you have an entry that can occassionally trigger it? Or is it any entry. (Currently running go test to see if any of those trigger)
I took a quick look over our entry log verification and didn't see anything, but I'm not sure what could be happening

It happened a couple times with https://github.com/slsa-framework/example-package/releases/tag/v10.0.9

This entry seems to not be available in the rekor log at all https://github.com/slsa-framework/example-package/actions/runs/2279044938
verification failed: could not find a matching signature entry

=== CONT  Test_runVerify/versioned_tag_no_match_empty_tag_workflow_dispatch
    main_test.go:304:   (*errors.errorString)(
        - 	e"could not find a matching signature entry",
        + 	e"invalid semantic version",
          )
calculated root:
[30 131 14 243 243 54 125 231 215 158 208 211 131 4 60 95 139 108 199 236 237 180 145 72 133 89 113 77 115 86 90 5]
 does not match expected root:
[99 162 240 228 26 97 158 145 186 26 222 48 211 156 144 224 234 189 58 38 5 216 205 201 15 153 138 78 227 229 235 215]: verifying inclusion proof=== CONT  Test_runVerify/valid_main_branch_set
    main_test.go:304:   any(
        - 	e"could not find a matching signature entry",
          )
--- FAIL: Test_runVerify (0.00s)

@asraa @laurentsimon
Is this still an issue? Can we close?

I think good to close. But let's wait for @asraa to ack and close.


examples: cert-manager podmonitoring manifest

Add an example for the basic cert-manager podmonitoring manifest to scrape the cert-manager metrics

@pintohutch : ^^

Hi @ajayk
Thanks for the contribution!
Let's flesh out the README a bit more -- the other examples here link to documentation in which we try to guide the user through the whole process of integrating an application with Managed Service with Prometheus. The podmonitoring config is only one part of the puzzle. Can you include:

a link to cert-manager itself (https://cert-manager.io/)
a sample yaml snippet or instructions on how to configure cert-manager to export prometheus-format metrics. I haven't worked with cert-manager, but I found the following through a quick search:

https://cert-manager.io/docs/usage/prometheus-metrics/ , which says you want to set certain configs in the Helm chart or apply a patch to the container
the helm chart itself (https://github.com/cert-manager/cert-manager/blob/7c175c5d80fba53915ae6c98c5c0e7cde8f27615/deploy/charts/cert-manager/templates/deployment.yaml#L117) seems to suggest that the named port http-metrics (9402) is always exposed no matter what. Setting additional configs only matter for interoperability with prometheus-operator, not GMP with managed collection

guidance on how to verify (2) is working -- for example, our Airflow instructions document how to run kubectl port-forward ... and access the port to check that metrics are available at that endpoint.
podmonitoring -- you have this, great!
guidance on how to verify that metrics are correctly ingested into GMP (again, refer to our published docs that ask the user to navigate to Metrics Explorer and run a given query.