How should I assign a value to the "targets" when I draw the heatmap of yolov8-pose?

I don't think "targets=None" is right. in the "base_cam.py",
if targets is None:
    target_categories = np.argmax(outputs.cpu().data.numpy(), axis=-2)
    targets = [ClassifierOutputTarget(
        category) for category in target_categories]

obviously, "pose" output should not use "ClassifierOutputTarget"

Can you assist me in determining target_layers for yolov7 ?


Incompatibility with create mod

unrelated to #528
this happens on client, when changed is loaded together with create mod it gives error:
java.lang.IllegalStateException: Uploader not created, a dependency for another mod may be missing.
versions:
Forge: 40.2.10
Create: 0.5.1.c
Flywheel (bundled with create): 0.6.9-101
Changed: 0.12
full crash report attached
crash-2023-09-21_15.08.00-client.txt

Already fixed in https://github.com/LtxProgrammer/Changed-Minecraft-Mod/commit/5230e54a1dab83e0320c19b17cb8d85e00a63b45


refactor: log more descriptive info from initContainer

Right now the example workers' initContainer that checks for
head Pod to be running logs the message waiting for myservice.
There is no myservice per se. The actual thing it's waiting for
is the K8s Service for the head group.
This change updates the log message to be more descriptive and
removes the string myservice from various places to not be misleading.
Checks

[x] I've made sure the tests are passing.
Testing Strategy

[x] Unit tests
[ ] Manual tests
[ ] This PR is not tested :(

Sorry for taking long on this change. Let me help review it

Thanks, it's pretty small. Just the same change in many different files. Lmk if you have any questions.

This looks good to me. Apologies for the nearly three month delay in review. I'll merge after re-running the failed test.
In the future, I propose having the operator auto-configure an initContainer which will health-check the Ray head pod's GCS server: https://github.com/ray-project/kuberay/issues/476


Request to add eraser icon

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Hi Team,
Please add an eraser icon to the @mui/icons-material library soon.
Examples 🌈
https://fontawesome.com/icons/eraser?f=classic&s=regular
Motivation 🔦
No response

Hello, I can work on this


[BUG] Open search results in the same tab

Deployment details:

App version: 2.2.0
Platform: amd64
Docker image tag: latest

Bug description:
The option "Open search results in the same tab" does not work

Steps to reproduce:

Go to settings>Search>Open search results in the same tab = true
search something and press enter and a new tab opens up...

I found the client/src/utility/redirectUrl.js the lines that open the new tab document.location.replace(parsedUrl) which looks fine to me, so I guess the the sameTab variable is not set properly ? If I find time I will try to dig further
cheers, great project !

whoops duplicated, #270


trying to use the latest version of the plugin in 4.27.2 but it won't compile

I specifically need the android log fixes which aren't available in version 0.5 which is the last one that supported 4.27.2
trying to use the latest versions from 5.1 downported to 4.27 results in a lot of compiler errors...

Thank you for raising this! We'll check it with 4.27 and see what can be done in order to fix those errors

UnrealBuildTool: Error  : Unhandled exception: Source file ProjectName\Plugins\SentrySDK\Source\ThirdParty\Win64\Breakpad\bin\sentry.dll' does not exist
Seems like there is nothing in that ThirdParty folder when going to download the sentry-unreal source as zip file


YETUS-882. command line patch files do not work in docker mode

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://builds.apache.org/job/yetus-github-multibranch/job/PR-56/1/console in case of problems.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
82
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
0
There were no new shellcheck issues.

+1
shelldocs
0
There were no new shelldocs issues.

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

+1
asflicense
10
The patch does not generate ASF License warnings.

118

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-56/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/56

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 1c3bc910de47 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
precommit/src/main/shell/personality/yetus.sh

git revision
master / 0478292

Max. process+thread count
51 (vs. ulimit of 2000)

modules
C: precommit U: precommit

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-56/1/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.6.0

Powered by
Apache Yetus 0.11.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.


Adjust for new standard library path

Previously, symbols from the standard library were referenced using the devices/ prefix in sky130. This behavior was changed in a recent PDK version to match the default behavior of xschem. Standard symbols are now referenced without the devices/ prefix.
For example, devices/ipin.sym becomes ipin.sym.
An example that shows the issue is this schematic: https://xschem-viewer.com/?file=https%3A%2F%2Fgithub.com%2Fefabless%2Fsky130_pa_ip__instramp%2Fblob%2Fmain%2Fxschem%2Fsky130_pa_ip__instramp.sch
Btw. I really love xschem-viewer, a great tool and so useful!

Thanks for reporting! Looks like the current version of that file is broken (syntax error on line 94), so I'll test with https://github.com/efabless/sky130_pa_ip__instramp/blob/313bbc11df304a461684ebe26ffdfaa2c11273e1/xschem/sky130_pa_ip__instramp.sch

Fixed: https://xschem-viewer.com/?file=https%3A%2F%2Fgithub.com%2Fefabless%2Fsky130_pa_ip__instramp%2Fblob%2F313bbc11df304a461684ebe26ffdfaa2c11273e1%2Fxschem%2Fsky130_pa_ip__instramp.sch

Thanks a lot @urish!
Fixed the syntax error in the schematic (it seems xschem is much more lax) and can confirm it works again  🎉


Remove accidental dependency

This is a holding package that was likely accidentally added. It's a bit of a no-op but good to remove so folks don't copy/paste it into their workflow.

Thanks for this, must've slipped through! 🙏


Start teku with empty public keys is not allowed

Context
Teku validator binary is started with the following binary config
    exec /opt/teku/bin/teku \
        --network=prater \
        --data-base-path=/opt/teku/data \
        --eth1-endpoint=$HTTP_WEB3PROVIDER \
        --validators-external-signer-url=$HTTP_WEB3SIGNER \
        --validators-external-signer-public-keys=$PUBLIC_KEYS_COMMA_SEPARATED \
        --p2p-port=9000 \
        --rest-api-cors-origins="*" \
        --rest-api-interface=<IP_ADDRESS> \
        --rest-api-port=$BEACON_API_PORT \
        --rest-api-host-allowlist="*" \
        --rest-api-enabled=true \
        --rest-api-docs-enabled=true \
        --log-destination=CONSOLE \
        --validators-graffiti=\"$GRAFFITI\" \
        $EXTRA_OPTS

Been the flag --validators-external-signer-public-keys where the public keys must be specified in format comma-separated
Issue
The flag --validators-external-signer-public-keys does not allow to start with an empty string, a situation that may happen if the remote signer returns empty public keys loaded. Until Teku supports loading an empty string, the binary must be started with or without the validator flags depending on there are or no validators loaded onto the remote signer.
Upstream issue https://github.com/ConsenSys/teku/issues/5130

closed by https://github.com/ConsenSys/teku/pull/5145


chore: Add "I haven't reached out to support already" to issue template

We'd like to avoid duplicate support cases and have seen several of these recently - this PR adds an extra checkbox to confirm the issue opener hasn't already reached out to support via another channel.

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Img / "Relative src URLs can break" warning should not happen for src="cid: ..."

hey there!
if I'm using inline images I got this warning.
Thanks!
Cya crazyx13th

If you want to support a broader set of clients, you shouldn't be using inline images. However, the warning is indeed a limitation in your case. I proposed to make warnings optional based on a configurable client support ruleset https://github.com/revivek/oy/issues/73. I am not sure when I will have enough time to work on it.


[master] redesign configuration Interface

[ ] Split runtime config and schema config
[ ] Create schema config from ServiceDocument
[ ] Validation should contain position information
[ ] Merge should only happen for schema config
[ ] CLI should take schema and runtime config separately
[ ] Drop Json and YML options for creating Schema configurations.

To split configurations we can consider the following refactor on Config

// After (v2)
pub enum Config {
    SchemaConfig(SchemaConfig),
    RuntimeConfig(RuntimeConfig),
}

// Merge only Schema
pub struct SchemaConfig {
    pub schema: RootSchema,
    pub types: BTreeMap<String, Type>,
    pub unions: BTreeMap<String, Union>,
    pub enums: BTreeMap<String, Enum>,
}

pub struct RuntimeConfig {
    pub server: Server,
    pub upstream: Upstream,
    pub telemetry: Telemetry,
    pub links: Vec<Link>,
}

Phase 1

[ ] Merge on Config should ignore server, upstream and telemetry (Alphabetical order).
[ ] server, upstream and telemetry should be read from root configuration.
[ ] Merge directives (Make all directives repeatable).
[ ] Merge links into root configuration.

pr https://github.com/tailcallhq/tailcall/pull/3190 for phase 1
For phase 2 the multiple directives are already done by https://github.com/tailcallhq/tailcall/pull/3124

Make Config sub-type of ServiceDocument

What does it mean?

pr https://github.com/tailcallhq/tailcall/pull/3201 to drop support of json/yaml configs


Change colors?

Is there a way to change the colours of highlighting? My current colors are not that pleasing.

I did this:
cd zsh-syntax-highlighting && find . -type f -exec sed -i 's/green/blue/g' {} \;
Obviously change "blue" to your desired color. You can use hex  colors too:
find . -type f -exec sed -i 's/green/"#FF6329"/g' {} \;

See the documentation about ZSH_HIGHLIGHT_STYLES, and your terminal emulator's color palette.

there are some config about ZSH_HIGHLIGHT_STYLES  inzsh-syntax-highlighting/highlighters/main/main-highlighter.zsh.  you can set it in ~/.zshrc  to change color.
such as change ZSH_HIGHLIGHT_STYLES[arg0]
ZSH_HIGHLIGHT_STYLES[arg0]='fg=yello'

I did this: cd zsh-syntax-highlighting && find . -type f -exec sed -i 's/\<green\>/blue/g' {} \;  Obviously change "blue" to your desired color. You can use hex colors too: find . -type f -exec sed -i 's/\<green\>/"#FF6329"/g' {} \;

Yeah, that's right.  Again, see the documentation for details.


Mutations popup

Puts the mutation information in a pop-up. Also makes mutation points visible with a hack - root cause is zero inheritors.
https://github.com/user-attachments/assets/b254d18a-bc9f-4995-a822-5f6763a4d4de

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

8 of 10 (80.0%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.4%) to 82.282%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tsbrowse/pages/mutations.py
7
9
77.78%

Files with Coverage Reduction
New Missed Lines
%

tsbrowse/plot_helpers.py
2
53.49%

Totals

Change from base Build<PHONE_NUMBER>2:
-0.4%

Covered Lines:
678

Relevant Lines:
824

💛  - Coveralls

Super! That looks like it works a lot better than second panel?

Wow, this is so neat! 😍

The colour scheme for mutations was white for mutations with low numbers of inheritors - I've change it to one that goes green to blue.


.Net Identity Single Sign-out

Hi, i've been working on an implementation of IdentityServer4 (Major difference being that i'm using Razor) with .NET Core Identity, i have a webapp/client authing user via the implicit flow.
My IS4 implementation is based off of the IdentityServer4AspNetIdentity template
Currently when i logout via the client, i am redirected to IS4, where the appropriate logout stuff happens, then i am redirected back to the client, properly logged out (this works fine).
However, if i go directly to the IS4 instance and hit logout and then navigate to the Client/webapp, i am still logged in, this is obviously incorrect.
I Have scoured the internet for the past two days, have found information on Federated sign-out, FrontChannelLogoutUri and BackChannelLogoutUri, iframes, and all sorts of other things, i have tried all of them, and yet this issue remains. So, i turn here, can you please help me understand what i'm missing in my code?
This is the client logout page:
https://github.com/ldtteam/ChatChain/blob/feature/seperate-accounts-from-webapp/WebApp/Pages/Account/Logout.cshtml.cs
This is the IS4 logout page:
https://github.com/ldtteam/ChatChain/blob/feature/seperate-accounts-from-webapp/IdentityServer/Pages/Account/Logout.cshtml.cs
Obviously the code changed tonnes of times while i was testing all the different possible solutions, this code is my original attempt, as the code only got more and more unreadable as i attempted further solutions.
I can answer any questions you may have, and provide any code you may need.
I apologise if i missed something extremely obvious, i did my best to read all the documentation and information on this topic.

YOu need to render the iframe on the logged out view.

Thank you so much for that help.
I had done that several times, however i tried it again just now, and i realised that the iframe variable only gets set if you have logged in through the client (oidc), if you don't the iframe is null!

One quick question, if i have two clients authenticated (both going through the proper OIDC stuff) does two iframes get rendered? because i would assume not, given that the variable is a single url. not multiple. So, if not, which client would be logged out the first to go through OIDC, or the second? And is there a simple way to make sure both get logged out?
Thanks!

No and yes :)
The one iframe will then contain the two iframes.

Oh, That's interesting and cool. Thanks for your help!


A problem occurred evaluating project ':app'. > /home/daniel/atak-forwarder/app/build/blank-mapping.txt (No existe el archivo o el directorio) no mapping file exists, obfuscating just the plugin to work with the development core

Why?

Closing this since the current goal is a signed plugin and we are close to that goal.

Closing this since the current goal is a signed plugin and we are close to that goal.


SSL passthrough

Hi,
I'm trying to setup secure docker registry inside a kubernetes cluster with self-signed certificates, and im trying to test it on minikube
my end goal is to be able to do a docker push  kube-registry.com/hello-world
this is my setup, the registry:
apiVersion: v1
kind: ReplicationController
metadata:
  name: kube-registry
  namespace: kube-system
  labels:
    k8s-app: kube-registry
    version: v0
# A minikube issue prevents the following from working
#    kubernetes.io/cluster-service: "true"
spec:
  replicas: 1
  selector:
    k8s-app: kube-registry
    version: v0
  template:
    metadata:
      labels:
        k8s-app: kube-registry
        version: v0
# A minikube issue prevents the following from working
#        kubernetes.io/cluster-service: "true"
    spec:
      containers:
      - name: registry
        image: registry:2
        resources:
          limits:
            cpu: 100m
            memory: 100Mi
        env:
        - name: REGISTRY_HTTP_ADDR
          value: :5000
        - name: REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY
          value: /var/lib/registry
        - name: REGISTRY_HTTP_TLS_CERTIFICATE
          value: /cert/ca.crt
        - name: REGISTRY_HTTP_TLS_KEY
          value: /key/domain.key
        - name: REGISTRY_LOG_LEVEL
          value: debug
        volumeMounts:
        - name: image-store
          mountPath: /var/lib/registry
        - name: registry-cert
          mountPath: /cert/
          readOnly: true
        - name: registry-key
          mountPath: /key/
          readOnly: true
        ports:
        - containerPort: 5000
          name: registry
          protocol: TCP
      volumes:
      - name: image-store
        persistentVolumeClaim:
          claimName: kube-registry-volume
      - name: registry-cert
        secret:
          secretName: registry-cert
      - name: registry-key
        secret:
          secretName: registry-key

and the service:
apiVersion: v1
kind: Service
metadata:
  name: kube-registry
  namespace: kube-system
  labels:
    k8s-app: kube-registry
    kubernetes.io/name: "KubeRegistry"
spec:
  selector:
    k8s-app: kube-registry
  ports:
  - name: registry
    port: 5000
    nodePort: 31000
    protocol: TCP
  type: NodePort

i also generated the self-signed certificates, and created the relative volumes and config-maps and i edited my /etc/hosts
with this setup i am able to do docker push  kube-registry.com:31000/hello-world
the last step is to remove that port, and i started playing around with ingress and the solution with ssl passthrough seemed the right way to go so i did this:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: kube-registry-ingress
  namespace: kube-system
  annotations:
    ingress.kubernetes.io/ssl-passthrough: "true"
spec:
  rules:
  - host: kube-registry.com
    http:
      paths:
      - backend:
          serviceName: kube-registry
          servicePort: 5000
  tls:
  - hosts:
    - kube-registry.com

from my understanding ssl passthrough should not decrypt traffic on the ingress and just pass along the traffic to the service and back but docker push  kube-registry.com/hello-world gives me this error:

Error response from daemon: Get https://kube-registry.com/v2/: x509: certificate is valid for ingress.local, not kube-registry.com

this is curl output with port (not going through ingress):
* Rebuilt URL to: https://kube-registry.com:31000/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to kube-registry.com (<IP_ADDRESS>) port 31000 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=GB; ST=Test State or Province; L=Test Locality; O=Local Secure Registry for Kubernetes; CN=kube-registry.com<EMAIL_ADDRESS>*  start date: Dec 28 23:19:10 2017 GMT
*  expire date: Sep 19 23:19:10 2018 GMT
*  issuer: C=GB; ST=Test State or Province; L=Test Locality; O=Local Secure Registry for Kubernetes; CN=kube-registry.com<EMAIL_ADDRESS>*  SSL certificate verify result: self signed certificate (18), continuing anyway.
> GET / HTTP/1.1
> Host: kube-registry.com:31000
> User-Agent: curl/7.52.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Cache-Control: no-cache
< Date: Fri, 29 Dec 2017 00:31:18 GMT
< Content-Length: 0
< Content-Type: text/plain; charset=utf-8
<
* Curl_http_done: called premature == 0
* Connection #0 to host kube-registry.com left intact

and without port (using ingress):
* Rebuilt URL to: https://kube-registry.com/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to kube-registry.com (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: O=Acme Co; CN=Kubernetes Ingress Controller Fake Certificate
*  start date: Dec 28 22:51:53 2017 GMT
*  expire date: Dec 28 22:51:53 2018 GMT
*  issuer: O=Acme Co; CN=Kubernetes Ingress Controller Fake Certificate
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
> GET / HTTP/1.1
> Host: kube-registry.com
> User-Agent: curl/7.52.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx/1.13.5
< Date: Fri, 29 Dec 2017 00:32:22 GMT
< Content-Type: text/plain; charset=utf-8
< Content-Length: 0
< Connection: keep-alive
< Cache-Control: no-cache
< Strict-Transport-Security: max-age=15724800; includeSubDomains;
<
* Curl_http_done: called premature == 0
* Connection #0 to host kube-registry.com left intact

i don't understand why in the second case i get ingress's own certificate instead of the one from the registry. am i doing something wrong?
i also have a repository that sets up everything by using the script reg-tool.sh
ps: i know there is an addon that provides an unsecured registry and that for minikube it might not make much sense what i'm trying to do, i'm just using this little project to understand different components of kubernetes.

@deathcoder, have you managed to solve the issue in the end?

@deathcoder Do you find any solution?


feat(bearer-auth): added custom response message options

The author should do the following, if applicable

[x] Add tests
[x] Run tests
[x] bun run format:fix && bun run lint:fix to format the code
[x] Add TSDoc/JSDoc to document the code

@yusukebe here is the alternative PR: https://github.com/honojs/hono/pull/3381

@marceloverdijk
Thanks! Looks good to me. I'll merge this into the next later. Appreciate your contribution!


Add migration SQL_DUMP.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

I'd apply same priciple as in comments for https://github.com/yiisoft/log-target-db/pull/43


backport of 2287

This patch fixes an issue where if hosts have different service lists,
it will prevent restarting changes on services that run later on.
For example, hostA in the mons and rgws group would initiate a config
change and restart of services on all mons and rgws hosts, even though
a separate hostB (which is only in the rgws group) has not had its
configuration changed yet. Additionally, when the second host has its
coniguration changed as part of the ceph-rgw role, it will not initiate
a restart since its inventory name != the first hosts.
To fix this we should run the restart once (using run_once: True)
as long as the host has called the handler. This will ensure that even
if only 1 host has called the handler it will initiate a restart on all
hosts that have called the handler.
Additionally, we add a var that is set when the handler runs, this will
ensure that only hosts that have called the handler get restarted.
Includes minor fix to remove unrequired "inventory_hostname in
play_hosts" when: clause. This is no longer required since the handlers
were changed. The host calling the handler will be in play_hosts
already.
(cherry picked from commit 59a4335)

bkp of #2287

The CI has been already triggered. We just modified the commit message to include the Fixes: keyword so there is no need to wait for a new run of the CI.
The few failures here are unrelated.


[CT-1203] [Bug] mutiple references in a model causes duplicate entries in graph.node.depends_on

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
For a model that contains two relation references (is that the right term? trying not to say "references" to conflate that with the ref function), the corresponding entry in the manifest.json / graph will have the same node in the depends_on list multiple times:
Model with same source
-- in models/star.sql
select
  {{ dbt_utils.star(source('fake_source', 'orders')) }}
from {{ source('fake_source', 'orders') }}

Corresponding JSON
"nodes": {
        "model.davebt.star": {
            "raw_sql": "select\n  {{ dbt_utils.star(source('fake_source', 'orders')) }}\nfrom {{ source('fake_source', 'orders') }}",
            "compiled": true,
            "resource_type": "model",
            "depends_on": {
                "macros": [
                    "macro.dbt_utils.star"
                ],
                "nodes": [
                    "source.davebt.fake_source.orders",
                    "source.davebt.fake_source.orders"
                ]
            },
...

Model with same {{ ref() }}
-- in models/downstream.sql
-- depends on {{ ref('star') }}

select * from {{ ref('star') }}

Corresponding JSON
...
        "model.davebt.downstream": {
            "raw_sql": "-- depends on {{ ref('star') }}\n\n\nselect * from {{ ref('star') }}",
            "compiled": true,
            "resource_type": "model",
            "depends_on": {
                "macros": [],
                "nodes": [
                    "model.davebt.star",
                    "model.davebt.star"
                ]
            },
...

Expected Behavior
This may in fact be expected! This came up in the dbt_project_evaluator project -- multiple sources joined together is a violation of the recommended best practices (stage those sources!) and the same source called twice with the star macro as above caused an unintentional error.
The fix on the package side is really straightforward, but got us wondering what the intended behavior here is!
Steps To Reproduce

configure a source
reference it twice in any model file
reference model from step 2 in new model file multiple times
check manifest.json entries for these nodes

Relevant log output
No response
Environment
- OS: mac
- Python: 3.8.4
- dbt: 1.2.1

Which database adapter are you using with dbt?
postgres, redshift, snowflake, bigquery, spark
Additional Context
No response

@dave-connors-3 Thanks for opening this, and sorry it's taken me forever to respond!
This one is totally in our power to change. So really, the question is: What is the expected behavior? What ought it be?
Here's a halfway position that makes sense to me, but I wouldn't be surprised if someone else found it more confusing:

The refs node property is where dbt "captures" calls to ref() at parse time. (Same for sources/source() +  metrics/metric().) If those are called multiple times within one model, I'd expect those calls to appear multiple times, and in the same sequence in which they're called.
The depends_on node property is the result of some resolution & processing within dbt. It should be a clean, go-to place to quickly see which resources a given model depends on, and so it should be deduplicated — maybe even sorted (alphabetically), but that would just be a bonus.

The deduplication would be consistent with three other things already in the dbt-core codebase:

The DependsOn class already has an add_node property that checks to see if a node is already present before adding. But it looks like, in several places, we use depends_on.nodes.append instead of depends_on.nodes.add_node!
The depends_on.macros, which (after some quick manual testing to verify) appears to be the set of distinct macros called, even if a given macro is called multiple times
same_depends_on for exposures, which already deduplicates depends_on.nodes by wrapping it in set()

example
-- models/model_a.sql
select 1 as id

-- models/model_b.sql
select 1 as id

-- models/model_c.sql
select * from {{ ref('model_a') }}
union all
select * from {{ ref('model_b') }}
union all
select * from {{ ref('model_a') }}

current
    "model.testy.model_c": {
      ...
      "raw_code": "select * from {{ ref('model_a') }}\nunion all\nselect * from {{ ref('model_b') }}\nunion all\nselect * from {{ ref('model_a') }}",
      "language": "sql",
      "refs": [
        [
          "model_a"
        ],
        [
          "model_b"
        ],
        [
          "model_a"
        ]
      ],
      "sources": [],
      "metrics": [],
      "depends_on": {
        "macros": [],
        "nodes": [
          "model.testy.model_a",
          "model.testy.model_b",
          "model.testy.model_a"
        ]
      },
      "compiled_path": null
    },

proposed
    "model.testy.model_c": {
      ...
      "raw_code": "select * from {{ ref('model_a') }}\nunion all\nselect * from {{ ref('model_b') }}\nunion all\nselect * from {{ ref('model_a') }}",
      "language": "sql",
      "refs": [
        [
          "model_a"
        ],
        [
          "model_b"
        ],
        [
          "model_a"
        ]
      ],
      "sources": [],
      "metrics": [],
      "depends_on": {
        "macros": [],
        "nodes": [
          "model.testy.model_b",
          "model.testy.model_a"
        ]
      },
      "compiled_path": null
    },

Resolved by https://github.com/dbt-labs/dbt-core/pull/7455


Overlayed Histograms share same color using Bokeh backend

Overlaying two histograms using the Bokeh backend makes them share a color. This is not the case using the matplotlib-backend.
import numpy as np
import holoviews as hv
hv.notebook_extension("bokeh")

hvset = hv.Dataset({
    "Noise": np.random.normal(size=(1000,)),
    "More Noise": np.random.normal(loc=5, size=(1000,))
}, vdims=["Noise", "More Noise"])

hv.Overlay([
    hv.operation.histogram(hvset, dimension="Noise", adjoin=False, bin_range=(-5, 5), num_bins=40),
    hv.operation.histogram(hvset, dimension="More Noise", adjoin=False, bin_range=(0, 10), num_bins=40)
])

Definitely a bug in the bokeh backend - whether it is just the style definitions or something else in the code. Thanks for reporting this!

Yes, this is just down to the default style definition. We should just make it match matplotlib, here's the current setting:
options.Histogram = Options('style', fill_color="#036564", line_color="#033649")

It should probably be this instead
options.Histogram = Options('style', line_color='black', fill_color=Cycle())

I would be happy to see this style change committed straight to master - in my view, this is just fixing a bug.

Now fixed, it required updating the bokeh tests.


Support openjdknext build

make JDK_VERSION and JDK_IMPL optional parameters
if JDK_VERSION=next, then set JDK_VERSION to empty string in
Jenkinsfilebase
Remove the check of JDK_VERSION in test job template. The value is
handled in Jenkinsfilebase

Closes: #1018
Signed-off-by: lanxia<EMAIL_ADDRESS>

Tested with JDK_VERSION =next:
https://ci.adoptopenjdk.net/view/work in progress/job/Grinder_Sandbox/356/
Tested with JDK_VERSION ="":
https://ci.adoptopenjdk.net/view/work in progress/job/Grinder_Sandbox/357/
Tested with JDK_VERSION ="Next":
https://ci.adoptopenjdk.net/view/work in progress/job/Grinder_Sandbox/358/
Tested with old parameter JAVA_VESION=SE110:
https://ci.adoptopenjdk.net/view/work in progress/job/Grinder_Sandbox/355/

Just for the record, this PR also fixes the issue where JDK_VERSION and JDK_IMPL are required when AUTO_DETECT is enabled in JDK8
https://ci.adoptopenjdk.net/view/work in progress/job/Grinder_Sandbox/361/


feat(cli): use of preset account if cloud info missing

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 37.78%. Comparing base (006f11c) to head (59a3e83).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #278      +/-   ##
==========================================
+ Coverage   37.76%   37.78%   +0.01%
==========================================
  Files          84       84
  Lines        7470     7472       +2
==========================================
+ Hits         2821     2823       +2
  Misses       4649     4649

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


Revert "Deleted travis yml file"

Reverts products-devops-fall-21/products#128

Codecov Report

Merging #133 (7530aed) into main (b301db5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #133   +/-   ##
=======================================
  Coverage   95.41%   95.41%
=======================================
  Files           5        5
  Lines         436      436
=======================================
  Hits          416      416
  Misses         20       20

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 b301db5...7530aed. Read the comment docs.


Fix Mend exclude field in sec config

Description
Changes proposed in this pull request:

Fix configuration of exclude folders list for Mend scans

Related issue(s)

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


fix(reflect): failure to load assembly from "npm pack"

When the package.json file is the result of extracting a tarball
obtained from npm pack, it may have been processed by npmjs.com
during publishing, which can cause the bundleDependencies property to
appear with the value false. The null-coalescing (??) operator does
not rescue this properly and this results in a TypeError.
This is fixed by using || chaining instead of a null-coalescing, which
rescues from all falsey values in this case.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


[TritonGEN]: Replace GenISA intrinsics for named barriers with supported IGC intrinsics

The following GenISA intrinsics need to be replaced with OpenCL or long term supported IGC intrinsics:
"GenISA_threadgroupnamedbarriers_signal": ["Named Barriers Init",
    [("void",                          ""),
    [("int",                           "thread group named barrier ID"),
     ("int",                           "thread group count")],
    "Convergent"]],

"GenISA_threadgroupnamedbarriers_wait": ["Named Barriers barrier",
    [("void",                          ""),
    [("int",                           "thread group named barrier ID")],
    "Convergent"]],

Named barriers were removed from TritonGEN, closing this issue.


[PE-D][Tester A] DG does not mention that index is from the printed list

How to recreate:

Find names that doesn't exist
run command

Labels: severity.Low type.DocumentationBug
original: 9fc70c892/ped#5

Completed. PR #162


[FLINK-19037] Forward ioExecutor from ClusterEntrypoint to Dispatcher

What is the purpose of the change
Before this change, the dispatcher was using the executor of the RPC service for executing IO or heavy tasks.
Now, we forward the ioExecutor of the ClusterEntrypoint to the Dispatcher.

Thanks for the review. Will merge the change.


Improve agent related collections

Is your feature request related to a problem? Please describe.
Agent related collections are currently returned from a basic keyword search against all collections. See if there are ways of getting better results back.
Additional context
This might require additional API endpoints.

Things to consider here:

Whatever query is made here needs to be reproducible in the main search page
Searching only for agents directly linked to collections will (at least now) overly limit the search results
Doing a keyword search for a name might return non-relevant results (for example if a result has both names in a hit, but not necessarily together). At the same time, using a phrase search for the name will return fewer results since names are sometimes in inverted order in collection/object descriptions.


Disable coverageThreshold from cli

Do you want to request a feature or report a bug?
feature
What is the current behavior?
Nothing exists as far as I can tell
What is the expected behavior?
To disable coverageThreshold:
jest --coverageThreshold # and not passing anything

Kind of like disabling the collectCoverageFrom
jest --collectCoverageFrom # and not passing a glob

Wanting to do this so when we run jest --watch it wont come up with errors saying it can't find the coverage for the files that are meant to have a coverage threshold.
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
Jest: v21.1.0
node v6.10.3
yarn v1.0.2

I was able to get around this by creating a jest watch config file that uses the base jest config and just omits collectCoverageFrom, coveragePathIgnorePatterns, coverageThreshold

But think might still be handy to be able to configure at least the global threshold via a --coverageThreshold flag

In other projects, I've seen a --no- prefix negate any/all flags. I followed suit in gitlike-cli, as an example.

I don't think this is super common. You can pass --config '{"coverageThreshold": {}}' or something like that, I think?
If not, you can create a custom watch plugin that allows you to disable it

@SimenB  you are so cute.

jest --coverageThreshold '{}' does the trick


[Bug Report] [el-table] displays old images when table data has been updated.

Element UI version
2.4.5
OS/Browsers version
Windows 10 / Chrome
Vue version
2.5.16
Reproduction Link
https://jsfiddle.net/BkunS/nbmhuj9s/
Steps to reproduce
Click Update Button to update data in table, images could take several seconds to load. Before new image is loaded, the table is displaying new data with old images.
What is Expected?
The table should NOT continue to display old image while table data being updated and new image is still being download. The image slot should go blank when there's an update in url.
What is actually happening?
The image stays the same and will be swapped after new image finished downloading. This will cause table displaying new table text data with old images data during the loading period of new images.

@BkunS specify key for image https://jsfiddle.net/nbmhuj9s/1/

@ziyoung Thank you so much!!


Created Wind Waker HD FPS Slowdown Fix Pack!

Hi, Could I please get a little more detail as what this does exactly. How does it reduce frame loss and will it be needed in further Cemu updates

I believe it disables network connectivity stuff from last I remember.

Thanks for getting back to me. I'd like to request if I may that little descriptions for FPS and other non resolution related graphics packs gets included. Having a higher FPS is always nice but it's impotent to know how it's being done encase in works by disabling a feature you want or something.


Could not launch ubuntu distro. Now I cannot install any distro. error: 0x80070002

Environment
Windows build number:
Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19018.0 Microsoft Windows NT 10.0.19018.0

Your Distribution version:
Cannot run the specified commands because of the issue. But it was Ubuntu 18.04

Steps to reproduce
Trying to start the distro led only to an error mesage:

ubuntu
The system cannot find the file specified.

In trying to debug, I first tried to uninstall and reinstall the distro. So I uninstalled it by right clicking the tile and selecting "uninstall". Next I verified that it is uninstalled:

wslconfig.exe /l
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Microsoft Store

However, when trying to install a distro I run into one of two errors. For the one just named "Ubuntu" in the Windows store I get an error popup:

Transcription:
"Something unexpected happened! Reporting this problem will help us understand it better. You can wait a bit and try again or restart your device. That may help.
Code: 0x80073D05"
For the one named "Ubuntu 18.04" in the Windows store it apparently installs correctly, but when trying to launch fails with the following message:
"Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070002
Error: 0x80070002 The system cannot find the file specified.
Press any key to continue..."
Logs, gathered as specified under https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md can be found in the following file:
logs.zip
Expected behavior
Start the distro
Actual behavior
Encountering "Error: 0x80070002", the distro fails to launch.

Thank-you for submitting logs. Ref #5107 #4959.

Please see #5107

Thank you for your replies.
If I understand this correctly, issue #5107 links the problem to VPN installations under windows and indeed I have two VPNs installed. So this can indeed be what's causing my issue.
As recommended there, I disabled and re-enabled the WSL feature in windows and this seems to have fixed the problem. For now.
Still would be nice to know what I can do to avoid running into this in the future...

/dupe #5107


"Jumping" KeyboardAvoidingView content on iOS in case of Passwords autosuggest button is present at the top of the keyboard

Description:
"Jumping" KeyboardAvoidingView content on iOS in case of appearing of Passwords autosuggest button at the top of the keyboard.

React Native version:
System:
OS: macOS Mojave 10.14.5
CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Memory: 363.24 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.15.3 - ~/.nvm/versions/node/v10.15.3/bin/node
Yarn: 1.17.3 - ~/.yarn/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v10.15.3/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 23, 28, 29
Build Tools: 28.0.3, 29.0.0, 29.0.1, 29.0.2
System Images: android-28 | Android TV Intel x86 Atom, android-28 | China version of Wear OS Intel x86 Atom, android-28 | Wear OS Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.5 AI-191.8<IP_ADDRESS>00203
Xcode: 11.2.1/11B500 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
npmGlobalPackages:
create-react-native-app: 2.0.2
react-native: 0.61.5

Steps To Reproduce:

Run code on iOS device with enabled password autosuggest function.
KeyboardAvoidingView must have behavior='padding' and must be aligned to the bottom of the screen
Screen must contain 2+ TextInput fields one of which must have textContentType='password' or/and secureTextEntry={true}
Change focus by tapping from one field to another.

Expected Results:
KeyboardAvoidingView content don't move while changing focus on the TextInput fields.
Snack:
https://snack.expo.io/@sergeyyuhimovich/keyboardavoidingview-bug

I've been having this problem as well but on iOS. I managed to get around it by setting secureTextEntry prop to true only when the password input is focused. I did the same with the textContentType, setting it to 'password' when the secureTextEntry prop is true, otherwise set it to 'none'. It doesn't seem like the best solution but it does work. Hope this helps

keyboardWillShow triggers twice when secureTextEntry is true.

@stale I swear

Any updates on this?

keyboardWillShow still triggers twice when secureTextEntry is true.

I'm running into the same issue when switching between inputs which both have textContentType set to something other than none, e.g. telephoneNumber and emailAddress.

I'm running into the same issue when switching between inputs which both have textContentType set to something other than none, e.g. telephoneNumber and emailAddress.

any solution to this?

Why was this closed?

If this is still a problem please create a new issue against the latest stable version of RN

Absolutely still an issue, happens with vertically centered form, inside <KeyboardAvoidingView> with a password field.

Problem still persist after 4 years, interesting.

I ended up using Animated.View with variable marginTop based on the keyboard state and screen height. Not the most elegant but works if the content that needs moving is relatively small.

The issue is still happening

Anyone know how to fix this? Happening for me with all the content inside the KeyboardAvoidingView when typing the non secureTextEntry TextInput in. It does not happen when that prop is true. Expo SDK 51.


helmfile deps cannot create a lock file for an OCI repo

IMO it is related to https://github.com/roboll/helmfile/issues/2075 but have different way to discover.
reproduce
helmfile:
repositories:
  - name: huma
    url: ghcr.io/huma-engineering/helm-charts
    oci: true

releases:
  - name: compose-operator
    namespace: compose-operator
    # chart: ../charts/compose-operator
    chart: huma/compose-operator
    version: 0.39.0

Run helmfile deps
$ helmfile deps
Pulling ghcr.io/huma-engineering/helm-charts/compose-operator:0.39.0
Exporting ghcr.io/huma-engineering/helm-charts/compose-operator:0.39.0
Pulled: ghcr.io/huma-engineering/helm-charts/compose-operator:0.39.0
Digest: sha256:59632103db46727136a1cd08388cced3ee802e596f1d119a2b2bd6318b93fa06

Exporting ghcr.io/huma-engineering/helm-charts/compose-operator:0.39.0
Pulled: ghcr.io/huma-engineering/helm-charts/compose-operator:0.39.0
Digest: sha256:59632103db46727136a1cd08388cced3ee802e596f1d119a2b2bd6318b93fa06

Updating dependency /tmp/helmfile4265576871/compose-operator/compose-operator/compose-operator/0.39.0/compose-operator
There are no repositories defined in your helmfile.yaml.
This means helmfile cannot update your dependencies or create a lock file.
See https://github.com/roboll/helmfile/issues/878 for more information

I'd like to relate this to #2074, looks like the same problem


Order changes when toggle visible

Hi bertrandg,
I have two  with order 0 and 1, and I the 0 is toggle-able with a button. When I set 0 invisible and back, the order of them changed to 2 and 1. Is this my issue or a bug?
This happened after I update from 0.2.2 to 1.0.0-beta.5.
Thanks!

I tried what you say (with 1.0.0-beta.5) and it works, order is keeped:
https://stackblitz.com/edit/angular-k2op76?file=app%2Fhello.component.ts

Oh I just got what you mean, you are not using [order]!
Yes that's normal to react like this, now you have to set a [order] property if you want to keep order while toggling <split-area> presence using *ngIf of [visible] (Before 1.0.0 using [visible] keep order by default).

Alright, thanks very much. This is a fantastic ng plugin  btw.


Can i use it with MvvmCross?

Is it possible?

Any plans to give sidebar navigation Unified API support fro 64 bits? Soon only 64 bits apps con Apple Store.

Unified API support has been added.

Really? Well, cannot add the component to Unified project, it is not available.

Sorry I should have specified. There is a Unified version in the
repository. I'm told the component with Unified support should should be
approved and released in January.
Jack
On Fri, Jan 9, 2015 at 8:21 PM alexrainman<EMAIL_ADDRESS>wrote:

Really? Well, cannot add the component to Unified project, it is not
available.
—
Reply to this email directly or view it on GitHub
https://github.com/jdehlin/Xamarin-Sidebar/issues/14#issuecomment-69434144
.


Formatting everything 7

Last one! In this one I turn on the formatter check in CI, too.

Merged although some of this is preposterous ;P Let's see how I deal with this in dev :)


switching between channels can scroll up by itself

Would be nice if channels would stay scrolled all the way down, unless I scroll them up myself

Or at the very least stay in place so that if I've scrolled up a ton to read something and then need to check a DM, I don't have to scroll all the way up again.


how to fire an event when slider value change and call a function

i do't understand how i can fire the an function when a slider value change

You need to register a function on the onChange option using the rzSliderOptions attribute.
Example: http://jsfiddle.net/uz9eLpar/ .

this example is wonderful but my range slider is double and after doing this i can't able to fire an function.. is you have any example of double range slider for fire an function when release the click on button

Like this: http://jsfiddle.net/muwetwLc/ ?

yes thanks sir i try this...

$scope.minRangeSlider = {
minValue: 0,
maxValue: 10000,
options: {
floor: 0,
ceil: 10000,
step: 1,
onEnd: $scope.searchByPrice(0)
}
};

is this code right ?? function is not fire

Nope it is wrong.
The problem is with the way you set the onEnd function. Now, onEnd is not set to a function but to the result of searchByPrice.
So you can do:
$scope.minRangeSlider = {
        minValue: 0,
        maxValue: 10000,
        options: {
            floor: 0,
            ceil: 10000,
            step: 1,
            onEnd: $scope.searchByPrice
        }
};

If the way above, you need your searchByPrice to be declared before this code.
But if you really need to pass 0 to your searchByPrice, then do:
$scope.minRangeSlider = {
        minValue: 0,
        maxValue: 10000,
        options: {
            floor: 0,
            ceil: 10000,
            step: 1,
            onEnd: function() {
                 $scope.searchByPrice(0);
            }
        }
};

With the code above, you can declare searchByPrice wherever you want.

thanks sir .. it solve my problem and working correctly....

sir you have any date range picker for getting the two dates and perform a operation???

Please use https://gitter.im/rzajac/angularjs-slider to chat ;)


Issue 1010 upgrading

Fixing ZAP upgrade command so the correct files are selected

Codecov Report

Merging #1011 (33db595) into master (4f2a3d6) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1011      +/-   ##
==========================================
- Coverage   67.07%   67.06%   -0.01%
==========================================
  Files         157      157
  Lines       17185    17187       +2
  Branches     3752     3753       +1
==========================================
  Hits        11527    11527
- Misses       5658     5660       +2

Impacted Files
Coverage Δ

src-electron/main-process/startup.js
43.17% <0.00%> (-0.22%)
:arrow_down:


Add User Authentication to Your Application (SAP HANA Cloud)

Tutorials: https://developers.sap.com/tutorials/hana-cloud-cap-add-authentication.html
Error in Section 6
[cds] - connect to db > hana {}
[ERROR] Unable to get xsuaa credentials. Please make sure your app is bound to a single xsuaa service inst
Log-File
0 info it worked if it ends with ok
1 verbose cli [ '/opt/nodejs/node-v10.23.1-linux-x64/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 warn lifecycle The node binary used for scripts is /extbin/bin/node but npm is using /opt/nodejs/node-v10.23.1-linux-x64/bin/node itself. Use the --scripts-prepend-node-path option to include the path for the node binary npm was executed with.
8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /opt/nodejs/node-v10.23.1-linux-x64/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/user/projects/MyHANAApp/node_modules/.bin:/home/user/.node_modules_global/bin:/extbin/bin:/extbin/npm/docker/bin:/extbin/npm/globals/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/curl/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/user/projects/MyHANAApp
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'NODE_ENV=production cds run' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
14 verbose stack Error<EMAIL_ADDRESS>start: NODE_ENV=production cds run
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter. (/opt/nodejs/node-v10.23.1-linux-x64/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
14 verbose stack     at EventEmitter.emit (events.js:198:13)
14 verbose stack     at ChildProcess. (/opt/nodejs/node-v10.23.1-linux-x64/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
14 verbose stack     at ChildProcess.emit (events.js:198:13)
14 verbose stack     at maybeClose (internal/child_process.js:982:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /home/user/projects/MyHANAApp
17 verbose Linux 5.4.0-5-cloud-amd64
18 verbose argv "/opt/nodejs/node-v10.23.1-linux-x64/bin/node" "/usr/local/bin/npm" "start"
19 verbose node v10.23.1
20 verbose npm  v6.14.10
21 error code ELIFECYCLE
22 error errno 1
23 error<EMAIL_ADDRESS>start: NODE_ENV=production cds run
23 error Exit status 1
24 error Failed at the<EMAIL_ADDRESS>start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]
What can i do?
Regards Thomas

What exactly is this from.  Is this the log from npm start in the root of the project?  I think the key of this is actually on the 2nd line:
[ERROR] Unable to get xsuaa credentials. Please make sure your app is bound to a single xsuaa service inst
This would seem to indicate a problem with your default-env.json in the root of the project and it not having the xsuaa section properly. Can you maybe share a screenshot of the default-env.json in the root of the project without revealing the technical details of the credentials section?  We just need to see if you have the content structured correctly in there.  Perhaps when you cut and pasted the service-key details into the credentials section something went slightly wrong.

Hi Thomas,
It is the log File from npm start.  I attatched to default-env.json as a zip File.
default-env.zip

I took the liberty of removing the attachment once I had a look at it since it does have credentials in it. I know its just trial, but still better safe than sorry.
Your default-env.json looks right to me. I compared it to the one in my project and it's structure at least is fine. I notice that you have the destinations at the top of the file though.  So is this copy of the default-env.json from the /app folder or the one from the root folder? With mutliple copies for the different part of the application it's easy to update the wrong one.  You need the xsuaa section in both versions of the file. Double check that this is the content in both locations.
The other thing that might be at issue here is knock on effect from the typo you find earlier: https://github.com/SAPDocuments/Issues/issues/232
When you delta with my mistake earlier did you leave the service name lower case?  If so you want to make sure you match the service name in the default-env.json. The more I think about it, this is likely the root cause.  If you created your sevice as myHANAApp-xsuaa-service, then match that same name in the default-env.json.  I had a typo in one part of the tutorial earlier where I had accidentally used lower case myHANAApp-xsuaa-service in one of the code snippets. I've since corrected the tutorial and made it all consistently MyHANAApp-xsuaa-service. But if you have your service instance as myHANAApp-xsuaa-service from my earlier mistake you will have to adjust that in the reference in the default-env.json files as well.  You can always do a cf services from the terminal to see what your instance is named.  It is case sensitive.  Sorry about that issue.

Sorry Thomas. I had move the default-env.json from root folder to the /app Folder.
I create a new default-env.json in the root Folder and change it the origin version.
Npm start work fine. Thank for your help. Have a nice day.
Von: Thomas Jung @.>
Gesendet: Mittwoch, 17. März 2021 21:20
An: SAPDocuments/Issues @.>
Cc: Th0masMa @.>; Author @.>
Betreff: Re: [SAPDocuments/Issues] Add User Authentication to Your Application (SAP HANA Cloud) (#240)
I took the liberty of removing the attachment once I had a look at it since it does have credentials in it. I know its just trial, but still better safe than sorry.
Your default-env.json looks right to me. I compared it to the one in my project and it's structure at least is fine. I notice that you have the destinations at the top of the file though. So is this copy of the default-env.json from the /app folder or the one from the root folder? With mutliple copies for the different part of the application it's easy to update the wrong one. You need the xsuaa section in both versions of the file. Double check that this is the content in both locations.
The other thing that might be at issue here is knock on effect from the typo you find earlier: #232 https://github.com/SAPDocuments/Issues/issues/232
When you delta with my mistake earlier did you leave the service name lower case? If so you want to make sure you match the service name in the default-env.json. The more I think about it, this is likely the root cause. If you created your sevice as myHANAApp-xsuaa-service, then match that same name in the default-env.json. I had a typo in one part of the tutorial earlier where I had accidentally used lower case myHANAApp-xsuaa-service in one of the code snippets. I've since corrected the tutorial and made it all consistently MyHANAApp-xsuaa-service. But if you have your service instance as myHANAApp-xsuaa-service from my earlier mistake you will have to adjust that in the reference in the default-env.json files as well. You can always do a cf services from the terminal to see what your instance is named. It is case sensitive. Sorry about that issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/SAPDocuments/Issues/issues/240#issuecomment-801415863 , or unsubscribe https://github.com/notifications/unsubscribe-auth/APIMH5HYNUC4V4B4MDPWCJ3TEEFF5ANCNFSM4ZLFBA7Q .  https://github.com/notifications/beacon/APIMH5DPP46AZXJAS4ZCCR3TEEFF5A5CNFSM4ZLFBA72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF7CKFNY.gif

Very good!


Support indexing Python

Let's figure out the right way to index python projects. Right now, most python projects are deployed using setup.py files. This is rough because it means we need to parse python code to be able to extract dependencies. Some projects have requirements.txt but that only lists dependencies, not the core module itself.
Pipfile looks really promising as it provides a way to manage dependencies in a declarative way but it's unclear what scale this mechanism is used: https://github.com/pypa/pipfile

In talking with a few folks about this, it sounds like there might be a way to get this information from artifactories pretty easily. Pypi repositories contain a .egg-info directory. This directory contains PKG-INFO which contains the module name and requires.txt which enumerates the concrete dependencies of the project. This should be easy enough to index for a v1. We will still need to figure out how to index source repositories but this is a good start.

In some further discussions, it sounds like we should be working with the Wheel spec where possible: https://www.python.org/dev/peps/pep-0427/
This is a gzipped artifact that can easily be unpacked using unzip and will provide similar information. In this case, I think it's fine to only support wheel compatible dependencies.

 Everything else should translate fine.


Please enable GitHub Discussions

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[x] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[ ] zsh
[ ] fish

Problem / Steps to reproduce
Firstly. I just stumbled across your repository. A great piece of software I wished I had learned about years ago :-)
So much so that I imagine a myriad ways in which I would like to use it. Many topics come to mind, but I don't believe they belong in the issues area of the repository, hence my suggestion to open a discussions now available on private and public repositories.
The discussions I would immediately be tempted to initiate are, unsorted:

Borrow functionality from rsync such as --exclude, --exclude-from, --include,  --include-from, or --files-from to easily handle noisy directories such as node_modules, vendor, or tmp/swap directories, backup files, etc.
Borrow functionality from find to include file attributes (i.e. time, permissions, ownership)
Include caching possibly with a dedicated daemon and make-like algorithms
Offer as a shell extension (KornShell, Bash) managed through set fzf on/off such that vim ** becomes automagically vim $(fzf **)
Include capabilities from attr to match tags in addition to file names
Have metrics on how performance scales (e.g. +60mn for 7mio files)
Set the functional boundaries of fzf? (aka UNIX philosophy for binaries)
Standardisation... with the possible end-goal of being POSIX-compliant

Thanks for the suggestion. Done.
FYI, some of the items you mentioned were already discussed on the issue tracker. Here are a few pointers.

https://github.com/junegunn/fzf#respecting-gitignore
#2330
#763
#578

Simply put, fzf is more like grep not find so it doesn't want find-like tool's capabilities (Unix philosophy).
Regarding the performance, I think fzf is fast enough that its performance is no longer an issue for most common use cases. If someone is running into a performance problem, they should ask if fzf is the right tool for the job. For example, for searching the file contents, ripgrep is a much better fit. You still can use fzf to add interactivity to it.
RG() {
  RG_PREFIX="rg --column --line-number --no-heading --color=always --smart-case "
  INITIAL_QUERY="$1"
  local selected=$(
    FZF_DEFAULT_COMMAND="$RG_PREFIX '$INITIAL_QUERY' || true" \
      fzf --bind "change:reload:$RG_PREFIX {q} || true" \
          --ansi --disabled --query "$INITIAL_QUERY" \
          --delimiter : \
          --preview 'bat --style=full --color=always --highlight-line {2} {1}' \
          --preview-window '~3:+{2}+3/2'
  )
  [ -n "$selected" ] && $EDITOR "$selected"
}


fix: add missing assets directory

The type of this PR is: Bugfix

This PR resolves failing build on Android
Description
The test build on Android has been failing due to missing the bundleReleaseJsAndAssets. This is a step that have separated from the main build because it's the one that consumes the most resources.
The build has been failing because at some point we removed the step of creating the assets folder.

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Fix test build failing - mounir

Dev changes

This PR contains the following changes:

Android user-facing changes (Fix test build failing - mounir)

  Generated by :no_entry_sign: dangerJS against 514c681f793e5b96f4db7f77589f9a74b37ff937

#squashongreen


[CosmosDB] Bulk Upsert not creating resourceBody Id for you

Package Name: @azure/cosmos
Package Version: 3.9.5
Operating system: Windows 10
[ ] nodejs

version:  Node 10 & 8

[ ] typescript

version: 3.3.3

Describe the bug
When running a bulk "Upsert" operation, "id" is not created for you.
To Reproduce
Steps to reproduce the behavior:

 const creates = objects.map(item => ({     operationType: "Upsert",     resourceBody: item,   }));
await this._cosmos.database(this._database).container(this._container).items.bulk(creates);
You will receive a 400 error followed by multiple 424 errors depending on how many items you are upserting (see screenshot).

Expected behavior
When running an "Upsert" operation, "id" should be created for you.
Screenshots

Additional context
Not sure if this is where the issue is or not but I thought it might help: /sdk/cosmosdb/cosmos/src/utils/batch.ts

@C-reddd this definitely looks like an oversight in bulk, I’ll work on it

Awesome! Thanks @zfoster!
Another quick question/thought. Are bulk operations suppose to retry if they receive a 429 response? If not, that would be a nice addition as well!
Thanks,
Connor

Im not sure if retries on 429s are working yet for bulk, I don’t believe they are but we should be able to hook into the existing retries logic down the road.
I see though that you’re getting 424 errors, those are the result of your first request failing. Bulk is opting out of subsequent requests once one fails, since it’s not atomic.  I can add an option to the bulk request options to change that too (though it wouldn’t help here if those are also all upserts without ids in the body)

Yeah I understand the 424 errors. After I submitted the ticket last night I went ahead and changed my code to add "id" to the Upsert resourceBody and items were correctly being added. However, you still do run into issue where some of the objects are created (201) and some objects are rejected with a 429 (due to rate limiting).

For now I’d recommend enabling autoscale on the container, that will fix the 429s. I can’t give an ETA now on retries but it’s definitely in the pipeline along with transactional batch

Sounds good! I appreciate the help!


Plugin request: flutter-tools.nvim

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find a similar feature request

🏷 Feature Type
New Addon
🔖 Feature description
Currently flutter projects are considered like any other dart project by the LSP. Which could be a very unfulfilling experience, especially if you come from vscode.
flutter-tools.nvim enhances the experience of working with Flutter projects in Neovim by adding these features: (Images of these features are available on the plugin's README)

Run flutter app with hot reloading
Start emulators or connected devices
Visualise colours from LSP
Visualise logs
Widget guides
Outline window
Closing Tags
Statusline decorations
Good experience with debugging

✔ Solution
To add flutter-tool.nvim as a official plugin of the flake.
In my opinion, this plugin should be enabled by default, since it doesn't affect working with Dart or any other type of project besides Flutter. And you'll basically always want it when using working on Flutter projects.
❓ Alternatives
No response
📝 Additional Context
Warnings to consider(especially the first one): https://github.com/akinsho/flutter-tools.nvim#warning
My config:
require('flutter-tools').setup {
  lsp = {
    color = { -- show the derived colours for dart variables
      enabled = true, -- whether or not to highlight color variables at all, only supported on flutter >= 2.10
      background = false, -- highlight the background
      foreground = false, -- highlight the foreground
      virtual_text = true, -- show the highlight using virtual text
      virtual_text_str = "■", -- the virtual text character to highlight
    },
    on_attach = on_attach,
    flags = lsp_flags,
    capabilities = capabilities,
  },
}

Displaying colors never worked for me. Maybe you'll have better luck with it.

on_attach = on_attach,
flags = lsp_flags,
capabilities = capabilities,

what are those, and how are they obtained - is it using some local variables from your config?

on_attach = on_attach,
flags = lsp_flags,
capabilities = capabilities,

what are those, and how are they obtained - is it using some local variables from your config?

These variables are for  nvim-lspconfig.
When you add a language to  nvim-lspconfig you usually pass these (to each langauge).
An example of adding python in lspconfig in this flake: https://github.com/NotAShelf/neovim-flake/blob/81eff0fd61b45239e9d829b407682bf9f4164928/modules/lsp/config.nix#L254
So I guess on_attach will equal to default_on_attach in the lsp configuration of this flake.

Sample module available over at the flutter-tools.nvim branch

Sample module implementation available over at the flutter-tools.nvim branch

Thanks! this seems to be working fine except the fact that I can't get the colors to show.
But as I've mentioned in the issue, I can't get them to show in my own config, so that's probably expected.


Pass prefix to children in validator name

This passes the full nested path down through the model structure.  For the following code:
// /server/main.js
import { Meteor } from 'meteor/meteor';
import { Class } from 'meteor/jagi:astronomy';

const Child = Class.create({
  name: 'Child',
  fields: {
    name: {
      type: String,
      validators: [{type: 'equal', param: 'John'}],
    },
    friends: {
      type: [String],
      default: () => [],
    },
    obj: {
      type: Object,
      default: () => {},
      validators: [{type: 'has', param: 'foo'}],
    },
  },
});

const Parent = Class.create({
  name: 'Parent',
  fields: {
    name: {
      type: String,
    },
    child: {
      type: Child,
      optional: true,
    },
    children: {
      type: [Child],
      default: () => [],
    },
  },
});

Meteor.startup(() => {
  let a = new Parent({
    name: 'Bob',
    child: {
      name: 'Steve',
      friends: ['Garry', 3, 'Norbert', 5],
      obj: {},
    },
    children: [{
      name: 'Eric',
      friends: ['Hugo', [3]],
      obj: {
        foo1: 'bar'
      },
    }],
  });
  try {
    a.validate({ stopOnFirstError: false })
  } catch (e) {
    console.log(e);
  }
});

You get the following error with full paths for the invalid fields:
{ [Error: "child.name" should be equal John [validation-error]]
 error: 'validation-error',
 reason: '"child.name" should be equal John',
 details:
  [ { className: 'Child',
      type: 'equal',
      name: 'child.name',
      nestedName: 'name',
      value: 'Steve',
      param: 'John',
      message: '"child.name" should be equal John' },
    { className: 'Child',
      type: 'string',
      name: 'child.friends.1',
      nestedName: undefined,
      value: 3,
      param: undefined,
      message: '"child.friends.1" has to be a string' },
    { className: 'Child',
      type: 'has',
      name: 'child.obj',
      nestedName: 'obj',
      value: {},
      param: 'foo',
      message: 'The "child.obj" field does not have the "foo" property' },
    { className: 'Child',
      type: 'equal',
      name: 'children.0.name',
      nestedName: 'name',
      value: 'Eric',
      param: 'John',
      message: '"children.0.name" should be equal John' },
    { className: 'Child',
      type: 'string',
      name: 'children.0.friends.1',
      nestedName: undefined,
      value: [Object],
      param: undefined,
      message: '"children.0.friends.1" has to be a string' },
    { className: 'Child',
      type: 'has',
      name: 'children.0.obj',
      nestedName: 'obj',
      value: [Object],
      param: 'foo',
      message: 'The "children.0.obj" field does not have the "foo" property' } ],
 message: '"child.name" should be equal John [validation-error]',
 errorType: 'Meteor.Error' }

What's the point of such change? How did it look before and how does it look right now? What's the benefit?

Hmm, I was having an issue where on nested objects I wasn't getting a full nested path to the field not validating, but I don't seem to be able to replicate it right now.  I'll do some more testing and see if I can figure out what was going on.

I've designed it to have information about path and single field name and it should work properly. If it does not than I may consider merging this PR but I have to be sure that it's required. So some reproduction repository would be helpful.

I've not been able to recreate the issue, You can close for now, and if it
becomes an issue again for me, then I can re-open/create a new issue if I
can create a reproduction for htis.
On Tue, Aug 16, 2016 at 1:13 PM, jagi<EMAIL_ADDRESS>wrote:

I've designed it to have information about path and single field name and
it should work properly. If it does not than I may consider merging this PR
but I have to be sure that it's required. So some reproduction repository
would be helpful.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jagi/meteor-astronomy/pull/475#issuecomment-240084077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFBvrYD-xZoxDP9t_rZZGoutZ1D0GwPWks5qgaltgaJpZM4JhBlW
.

Ok cool

It seems that issue is still here, I've reproduced it here : https://github.com/frco9/astroBug

I don't see any bug in the current code. The message is "bar.title" is required and it's correct. It's the full path. It passes full path in the name property and partial field name (the last segment of path) as the nestedName. That's it. There is no need for more information. If it's not working for you than it may mean that you're using some older version of Astronomy. What version are you using?

Oh I just noticed that problem is for not single nested fields but for doubly nested fields. Ok I will take a look at it.

Ok in deed this PR fixes this bug. In the future please describe your problem in more details :)

Thanks ! I will ;) !
Le mar. 15 nov. 2016 à 21:37, jagi<EMAIL_ADDRESS>a écrit :

Merged #475 https://github.com/jagi/meteor-astronomy/pull/475.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jagi/meteor-astronomy/pull/475#event-860035066, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AADtr7rajVx1s1vJwXcmz7FryTj0R6tsks5q-hfsgaJpZM4JhBlW
.

--
Jérémie Foucault


Increase the issue per page limit to 100

Increase the issue per page limit to 100, since we have more than 25 issues for voting in the TEC Hatch Config proposals.
Resolves #36.

Thanks for the update. Merged!


Add history field to image inspect

This fixes #860
Only add history to image inspect since the rest field mentioned in this issue are buildah specific. There is no sense to add it here.
Signed-off-by: Qi Wang<EMAIL_ADDRESS>

LGTM

LGTM, assuming happy tests.

bot, retest this please
/lgtm

LGTM
/approve

bot, retest this please

bot, retest this please

bot, retest this please


Ability to rearrange the pinned folders

It'd be nice to be able to re-arrange the pinned folders and customize them

Duplicate of #2011.


R.chain transucer, closes #1033

h/t to @kevinbeaty for his help pushing this over the finish line

Could you fix the lint errors?

hmmm. passes locally

((:bell:))

:deciduous_tree:


Add icon upload for applications

Everything is in the title.

I see two manners to handle this issue.  The first one is to make the following javascript functions: ` `` findAppIcon that returns the app icon stored beforehand in src/img folder and findAppAvatar that customizes the icon (for example the background color). Then I add in  _app-directive.html file this code

The last one is to make a directive in javascript that contains a function uploadIcon  and use it (the same technique used to upload the application ZIP file)

You do not need to find the icon (findIcon).
The icon location is already contained in the JSon (the one that describes an application) if it exists. Look for APP_ICON in our JSon serializer. When there is no icon, a random avatar is picked up by the web administration.
What you need to do is to update the _app-directive.html file and plug a library to:

Select an image on the disk when we click on a specific link.
Crop this image.
Invoke the "Upload" REST API provided by the DM.

CropperJS seems really cool. MIT license, Bower integration... They have a demo site too. Take inspiration from it.
You should have modifications to do in the _app-directive.html file and in its controller. Plus one in utils.service.rClient.js to invoke the Roboconf's REST API. And you would have to add CropperJS (or any other library you might use) in the dependencies section of the bower.json file.


Tree fails to render or appear in DOM

Describe the bug
Starting off with this library (this is great by the way, thank you for creating and maintaining this library), so attempting to start pretty basic and then adapt it to my specific needs. I have a component that should hold the tree:
import {
  UncontrolledTreeEnvironment,
  StaticTreeDataProvider,
  Tree,
} from "react-complex-tree";

const CategoryTree = () => {
  const readTemplate = (template: any, data: any = { items: {} }): any => {
    for (const [key, value] of Object.entries(template)) {
      // eslint-disable-next-line no-param-reassign
      data.items[key] = {
        index: key,
        canMove: true,
        isFolder: value !== null,
        children:
          value !== null ? Object.keys(value as Record<string, unknown>) : [],
        // : undefined,
        data: key,
        canRename: true,
      };

      if (value !== null) {
        readTemplate(value, data);
      }
    }
    return data;
  };

  const categoryItems = {
    root: {
      container: {
        item0: null,
        item1: null,
        item2: null,
        item3: {
          inner0: null,
          inner1: null,
          inner2: null,
          inner3: null,
        },
        item4: null,
        item5: null,
      },
    },
  };

  const items = readTemplate(categoryItems);
  console.log(items);

  return (
    <UncontrolledTreeEnvironment
      dataProvider={
        new StaticTreeDataProvider(items, (item, data) => ({
          ...item,
          data,
        }))
      }
      getItemTitle={(item) => item.data}
      viewState={{
        "tree-1": {
          expandedItems: [],
        },
      }}
    >
      <Tree treeId="tree-1" rootItem="root" treeLabel="Test" />
    </UncontrolledTreeEnvironment>
  );
};

export default CategoryTree;

This is basically ripped straight from the docs/example code in the source files, so I would expect it would work.
The issue I'm running into is that the Tree component does not render (I have another parent component that includes <CategoryTree /> as one of its children). There's no error in the console and no flags in my IDE, but it doesn't show up in my browser and I also can't find it in the DOM at all.
Expected behavior
I would expect to see something similar to here: https://rct.lukasbach.com/docs/guides/static-data-provider
Additional context
Currently running in a dev environment using:

Vite version 5.2.0
React version 18.2.66
React complex tree version 2.4.5

Running in Chrome version 127.0.6533.89 on Mac OS Venture (13.0)
I'm happy to provide any other information that may help in figuring this out.

With some slight code changes, I now have a version of it working - still not sure why this original code would not render anything though...

Hot did you solve it?


Install Docusaurus-Terminology and Migrate Website to Use Yarn

This PR installs the Docusaurus-Terminology libraries and migrates the /website dir to use Yarn rather than NPM

The working branch for this PR has the following implemented to support development of the yarn based build on cloudflare:

a minimal install of the Docusaurus-Terminology parser and term frameworks
removed the package-lock file (and replaced it with yarn-lock)
a test term defined in the file /docs/terms/test_term.mdx
a substitution for the term in the /docs/intro.md file

The changes LGTM


S3 support

Hi,
Please confirm whether s3 support is there for iasql.

Hey @AshnaSabu123 I was able to squeeze very basic S3 support into 0.0.5. It doesn't do much beyond letting you create, delete, and list buckets (no permissions, files, etc), but it's a foundation to build on.
What feature(s) of S3 do you use and would like to have access to? We can probably get that done first while filling it out.

Closing this out as s3 bucket support was added and no other features were requested. We will fill in other S3 functionality over time following our internal roadmap.


Car stream works but...

Car Stream works on my rooted fon but other apps like webviewauto.apk , odb2mini.apk and tinycam.apk is not diplayed in my car. HELP PLEASE!!!
Only AA mirror and carstream 2.0 is running and displayed in my car.
On my Fon runs GPS 12.6.85 and AA 3.5.583023
Car stream and AA mirror runs but other apps are not. Reason unknown.. help please

You can not run webview auto, AA browser, obd2 and tiny cam, Because the developers of these apps should include the UnLock feature by Slashmax into their apps.
you can use AA mirror because there is an Unlock apk by Slashmax himself.
and kirankumar integrtaed the unlock feature by Slashmax into carStream.

Can someone help me with the link to download carstream 1.8.3. Will car stream work on an unrooted phone that has google service update blocked?

You can use CarStream 2.0
But it wont work,
It will show server error on the phone screen even if you are using GPS 12.2.21 or earlier, Google has completely blocked it.
Only rooting will help.

I have a snapdragon samsung and I don't think there is root available for it. I want to find out if the earlier version of carstream like 1.8.3 will work on unrooted phone if I block play service from updating

A big NO. Carstream 1.8.3 will not work.

Hi pls confirm how to download carstream 2 version.also the process to run video through it.
Thanks

You can download Carstream 2.0 from the homepage of this site. If download option not visible click on assets. Then you can see release apk.
You need a Rooted phone. Step by step instruction is on previous issues check all

USing GPS 12.6.85 and AA 3.2.58 for long time on op3t. Since yesterday AA refuses to load unless i update some google apps including AA.i havent updated to the latest oos as that auto updates gps. anyone else experiencing this? any suggestions or combintions of software versions still working? thx..


Fix error message spamming when selecting PressableButtons in Editor …

…(#943)

Also fixes multi-object modification of "Is Interactable" convenience alias for StatefulInteractable.enabled.

(cherry picked from commit 3351ba1acb3a039bec9ac4c15de67fb2bbbb29f8)

/azp run

/azp run

/azp run


feat: Add new EKS module maintainer: dpiddockcmp

Hi Anton,
Can you add a new maintainer for the EKS module? Github username: @dpiddockcmp
They have been a huge help to the quality of the module and supporting users also. It would be great to have them onboard.
Thanks!

With great pleasure!

Done! Welcome @dpiddockcmp !

Hi 👋


chore: add missing options in commandline docs

bc5839e3 commit add --add-host flag, but forget to add it to the docs. Just use pouch gen-doc to fix it!

Ⅰ. Describe what this PR did
Just use pouch gen-doc to update docs.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Yes.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

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


Simplify generate parser tool

It's an internal build tool, so we can remove unused features.
Remove argparse dependency, remove unused Python generation.

Pull Request Test Coverage Report for Build 1022

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.603%

Totals

Change from base Build 1019:
0%

Covered Lines:
8623

Relevant Lines:
10309

💛  - Coveralls


Strange Memory Leak-like Behavior Using Shenandoah GC & AlwaysPreTouch

Question
Question
Are there any know bugs when using Shenandoah GC and the AlwaysPreTouch flag on eclipse-temurin:17?
Earlier this week I was working on improving the performance on my server and noticed what seemed to be a very slow memory leak. So I gathered and analyzed 2 different heap dumps across a timeframe. Both were identical and within 25MB of difference in heap size. Off-heap usage was also within that same negligible range of difference. The strange part that I noticed was the server slowly using/adding upwards of 1.2GB+ of RAM over a 10 hour period. Same behavior occurs over longer periods as well at a semi-linear rate. And I'm assuming given enough time it would run into an OOM situation.
After discovering that, I was experimenting with my GC flags and I eventually came to the conclusion that -XX:+AlwaysPreTouch was the reason for this slow climb in RAM usage when combined with Shenandoah GC specifically. Once I removed that flag the RAM completely stabilized and had no slow increases in RAM over time. And this is rather strange considering that nobody is on the server and it is basically idle during both heap dumps.
Additionally there are no other things contributing to RAM usage. It is only M-C in this environment.
Hopefully that's a decent overview of the context to the question here. If you have questions I will do my best to answer them. And I will post links to the heap dumps in question below.
Context
Context of all this is on a dedicated Java M-C server using Shenandoah GC.
Java version:
Java Version: 17.0.7, Eclipse Adoptium
Java VM Version: OpenJDK 64-Bit Server VM (mixed mode, sharing), Eclipse Adoptium
Your operating system and platform:
I'm on a dedicated host with the following configuration.
Docker container on Linux (Ubuntu 22) using image eclipse-temurin:17-jdk
Operating System: Linux (amd64) version 5.15.0-69-generic
You can see in this screenshot that the RAM usage is slowly increasing (6AM to 10AM+) despite the heap dumps showing the heap size staying the same.
https://cdn.discordapp.com/attachments/1097554927460552835/1110241709243236442/image.png
Right picture is baseline heap dump. And left is 4 hours after baseline dump.
https://cdn.discordapp.com/attachments/1110251836037939221/1110394013854482503/image.png

Might be a genuine issue with Shenandoah and Pretouch (aggressively loading in memory so it can meet the pause guarantees.

I've passed this on to one of the original Shenandoah authors

I did test AlwaysPreTouch with G1GC and didn't notice the same behavior as explained above. I understand G1GC and Shenandoah are very different but I don't personally know enough about either of them to know why there would be a major difference with AlwaysPreTouch.
And earlier I did see a bug that the Shenandoah dev team closed around 3 years ago that sounds similar to what is happening. But again do not know enough myself to know whether or not it's related to this behavior.
https://bugs.openjdk.org/browse/JDK-8245757
Also I will mention this is a dupe of #804 that got closed. I just didn't want this to get buried because of MC seeing as it doesn't seem to be related to MC as far as I can tell.
But with all that said I should be able to answer any questions about the environment or test different setups if needed.

We (AWS Corretto team) will investigate, but today is a holiday in US

@kdnilsen Hey Kelvin, nice to hear from you!  LMK if you want this transferred to JBS.

Hi there! On first read, I am puzzled how AlwaysPreTouch could contribute to the apparent leak, given that it "only" writes to memory at page granularity and lets the underlying OS memory manager to map the pages early. When you say "RAM", what does that mean exactly? Is this process RSS, Java heap "used", or something else?
To investigate further, it would be good to have the following:

JVM command line. You can drop MC-related application options, as it would mostly be interesting what JVM options the run is done with.
GC logs during the "leaky" couple of hours, to see whether GC makes weird choices there. Enable with -Xlog:gc.
NMT logging to see if there is a memory leak in native structures somewhere. Enable with -XX:NativeMemoryTracking=summary, and then do the regular dumps with jcmd <pid> VM.native_memory.

Additionally I was using the -XX:ShenandoahGuaranteedGCInterval=20000 flag during all of this behavior. And with AlwaysPreTouch disabled the web panel would report the same RAM usage over time. And with it enabled you get the slow increase in RAM usage according to the web panel. Which is very strange considering I did all this testing while the server was "idle" aka nobody joining during the periods of testing.

Hypothesis: so every 20 seconds a GC would happen, regardless what happened in the system, idle or not. AlwaysPreTouch would commit the entire region on first allocation, whether application (normal) or GC (evacuation) allocs. If -Xmx != -Xms, it might so happen than on every GC we take another region and commit it. Which will look like RSS growing until it hits Xmx.
Question: Is Xmx == Xms in that config? If not, would the "leak" still happen with -Xms${C}g -Xmx${C}g -XX:+AlwaysPreTouch, for a reasonable $C?

I believe it was Xmx=6192M & Xms=512. Although with the same flags on the JVM for G1GC, I didn't see the 'leaky' behavior using AlwaysPreTouch. Only with Shenandoah for some reason.

From my understanding the line graph that shows RAM usage over time would be how much RAM the docker container is using. And the 2 pie graphs would be JVM heap dumps I believe. I will try and get another person to clarify that first statement.

This is the dev's response to that.

It’s process rss, as reported specifically with docker stats

GC logs during the "leaky" couple of hours, to see whether GC makes weird choices there. Enable with -Xlog:gc.

NMT logging to see if there is a memory leak in native structures somewhere. Enable with -XX:NativeMemoryTracking=summary, and then do the regular dumps with jcmd  VM.native_memory.

Is there a particular log from above that you would like to see in particular? I could work on getting those generated today if so.

So I was able to get the basic GC Logs with the -Xlog:gc flag. And unfortunately I can't run jcmd in my environment. Also cannot drop Minecraft given the setup of the server via the host I'm using.
Also I did test out having Xmx=Xms with Pretouch and as expected it went ahead and allocated all available memory. And after an hour there was no increase in RAM usage in the docker container. Now I don't know if the leaky behavior is still occurring though since I don't know enough about GC to interpret the logs I generated. But anyways the log for this is below.
ShenAlwaysPreTouchGCLog-Xmx=Xms.txt
With Pretouch enabled and the Xms=512 set to that, the container used 300 more MB of RAM after an hour.
ShenAlwaysPreTouchGCLog-Xms=512.txt
And below is No Pretouch with Xmx=Xms at 6192M
ShenNoPreTouchGCLog-Xmx=Xms.txt
And then No Pretouch with Xms=512 below
ShenNoPreTouchGCLog-Xms=512.txt
Anything else that I might be able to test for you @shipilev? I think your hypothesis could be correct here but again I didn't look at the logs generated and I don't know enough about GC either, so I don't know for certain if that's the case.

I wonder why you run with 20s GC interval? Is it to keep the heap sizes low?

Umm well I was previously dealing with 155MB allocation per second with just one person online with 6GB allocated. Which is absurd for Minecraft in that context lol. Basically I kept running into OOM crashes due to this until I figured out that memory pressure was the problem.  You should be able to see below 3 minute allocation profilers before and after I found a fix for the issue of high memory pressure. So I should in theory be able to raise that guaranteed GC interval by quite a bit since I decreased memory pressure by 10x lol
You should be able to change the label to Bytes Per Second on these. Also looking back at these, the number for Memory (Process) is the total amount currently allocated instead of the actual max allocation.
Before Fix (1 Player): https://spark.lucko.me/6d1hJ8GpAp
After Fix (1 Player): https://spark.lucko.me/OE3dFezvPI

It looks that a better option here would be dropping -XX:+AlwaysPreTouch and then try with -XX:ShenandoahGCHeuristics=compact to battle fragmentation-induced heap growth better.

Yeah I'll just drop PreTouch for now. And currently I'm using experimental mode (=iu) with the flags below. I'll have to try out compact mode and see how that works out in different setups. Along with changing the guaranteed GC interval to something higher.
-XX:MaxGCPauseMillis=100 -XX:+ExplicitGCInvokesConcurrent -XX:+ParallelRefProcEnabled -XX:ShenandoahUncommitDelay=17000 -XX:ShenandoahGuaranteedGCInterval=20000 -XX:+UseShenandoahGC -XX:+DisableExplicitGC -XX:+UseNUMA -XX:-DontCompileHugeMethods -XX:+PerfDisableSharedMem -XX:+UseFastUnorderedTimeStamps -XX:-UseBiasedLocking -XX:ShenandoahGCMode=iu
Also I noticed compact mode isn't mentioned on the docs for openjdk Shenandoah here:
https://access.redhat.com/documentation/en-us/openjdk/17/html/using_shenandoah_garbage_collector_with_openjdk_17/different-modes-to-run-shenandoah-gc
But anyways thanks for all the analysis on this scenario @shipilev! Glad it's not necessarily a memory leak and more so that PreTouch wasn't being used in the right context.
I'll close this issue/question after the comments stop from either of us or by the end of the day otherwise.


make DevicePreview and GetMaterialApp.router  can work together on locale changes

ATTENTION: DO NOT USE THIS FIELD TO ASK SUPPORT QUESTIONS. USE THE PLATFORM CHANNELS FOR THIS. THIS SPACE IS DEDICATED ONLY FOR FEATURE REQUESTS
Is your feature request related to a problem? Please describe.
I use GetMaterialApp.router  in my project and use DevicePreview to test layout issues. However one thing is quite annoying that locale changes don't trigger the UI change.
Describe the solution you'd like
locale changes in device preview will trigger locale change in GetMaterialApp.router.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

any updates

Apparently this worked for me:
// ...
  runApp(
    DevicePreview(
      availableLocales: const [
        Locale('en', 'US'),
        Locale('pt', 'BR'),
        // ...
      ],
      enabled: !kReleaseMode,
      builder: (context) => GetMaterialApp(
        builder: (BuildContext ctx, Widget? widget) {
          // ...
          DevicePreview.appBuilder(ctx, widget),
          // ...
        },
        translations: value_sets.AppLabels(),
        locale: () {
          if(!kReleaseMode) {
            Get.locale = DevicePreview.locale(context);
            return DevicePreview.locale(context);
          }
          return Get.deviceLocale;
        }(),
        fallbackLocale: const Locale('pt', 'BR'),
        // ...
      ),
    ),
  );
// ...


Update index.md

Fixes #30281

Internal previews

📄 File
🔗 Preview link

aspnetcore/fundamentals/logging/index.md
Logging in .NET Core and ASP.NET Core

@cijothomas what about moving it to the very bottom of the file under it's own H2? Doesn't the comment still apply?
If not, happy to remove the note.

I'd suggest removing it now.
(once we decide to show how to do the logging even before DI/host is ready, then we need to show LoggerFactory.Create to create a alternate pipeline. When we add that, this Note can be brought back.)

Moved to #30288