dbt run fails with "The specified schema name userid@domain either does not exist or you do not have permission to use it

Hello,
When I create a schema manually, add it to my profiles.yml, and then submit "dbt run", my model is built successfully. However, if the schema specified in my profiles.yml does not exist, the build fails with:
"The specified schema name 'userid@domain' either does not exist or you do not have permission to use it" "CREATE SCHEMA failed due to previous errors"
when active directory integrated authentication is used. This feels like a DB permissions issue but I am able to log into SSMS using active directory integrated and create schemas without issue. I am also not sure why my userid and domain are being concatenated for the schema name when my profiles.yml contains "schema: staging".
I'm running dbt=0.19.2. What additional information can I provide for troubleshooting?

@jhoolachan thanks for putting in the work to get this set up!
more info:

what MSFT SQL product are you using? SQL Server (on-prem or IaaS) or Azure SQL?
what does a redacted version of your profiles.yml look like? It kinda seems like you have your user and schema` fields switched.

Full disclosure: I've never personally gotten active directory integrated authentication to work, as my company uses Azure Active Directory, and it is a lot of work to set that up in a demo environment. If you or your company uses is Azure Active Directory, I definitely recommend the cli auth method.

@swanderz
I'm using Azure SQL and my profiles.yml is below:
azure-sql-demo:
target: dev
outputs:
dev:
type: sqlserver
driver: 'ODBC Driver 17 for SQL Server'
server: {server}
port: 1433
database: {dbt}
schema: staging
authentication: ActiveDirectoryIntegrated
encrypt: true
I also see the same issue when using service principal authentication. In that scenario, the compiled schema is : client_id@tenant_id
As noted, both methods work without issue as long as the schema already exists. I have not tried the CLI auth method but can give it a shot.

I also see the same issue when using service principal authentication. In that scenario, the compiled schema is : client_id@tenant_id

weird! it might be that 'userid@domain' or client_id@tenant_idaren't properly quoted?
I highly recommend the cli auth option, then get started after that.
p.s. if you're interested in getting started with dbt & Azure SQL, you might be interested in this guide that @chaerinlee1 made.

The guide is great; thanks for that!
I was able to successfully connect via the CLI auth but I'm still facing the same error. My updated profile.yml is below.
azure-sql-demo-cli:
  target: dev
  outputs:
    dev:
      type: sqlserver
      driver: 'ODBC Driver 17 for SQL Server'
      server: {server}
      port: 1433
      database: BGEHRPTDCLD-DB-01
      schema: new_schema
      authentication: CLI

The error is the same as when connecting via AAD Integrated:
"The specified schema name 'userid@domain' either does not exist or you do not have permission to use it" "CREATE SCHEMA failed due to previous errors"

The error is the same as when connecting via AAD Integrated:
"The specified schema name 'userid@domain' either does not exist or you do not have permission to use it" "CREATE SCHEMA failed due to previous errors"

is userid@domain' anywhere in your profiles.yml? I'm confused now.
when you call dbt debug does everything run ok?

Nope, neither my userid or company domain are present in the profiles.yml - but those are the credentials I use during authentication
dbt debug looks good

Running with dbt=0.19.2
dbt version: 0.19.2
python version: 3.7.9
python path: c:\users\****\anaconda3\envs\dbt\python.exe
os info: Windows-10-10.0.18362-SP0
Using profiles.yml file at C:\Users\****\.dbt\profiles.yml
Using dbt_project.yml file at B:\****\dbt_project.yml

Configuration:
  profiles.yml file [OK found and valid]
  dbt_project.yml file [OK found and valid]

Required dependencies:
 - git [OK found]

Connection:
  server: ****
  database: ****
  schema: new_schema
  port: 1433
  UID: None
  client_id: None
  authentication: CLI
  encrypt: False
  trust_cert: False
  Connection test: OK connection ok

are you using the Azure SQL database that isn't master?
can you log-into the database using SSMS using the "MFA + interactive auth" option (the one the opens a browser pop up to login w/ your creds)
are you 100% confident that userid@domain doesn't show up anywhere in your dbt project folder?

Yes, my permissions don't even allow me to see master
I cannot. Per our cloud team, the only login we can use in SSMS is AAD - Integrated
Yes. It is a very basic project  with only a handful of sources and models

Edit: I saw your note to move it to tsql-utils. Is that functionality available in GitHub or do you just mean re-post there?

yes, I think so, but let's have that discussion on the tsql-utls repo Issues page.
as for the main issue, now I'm rather stumped! if you DM me on the dbt Slack, I can give you test Azure SQL to play with (to see if the error persists).
Can you log into the db with SSMS, and execute CREATE SCHEMA new_schema without issue?
You might want to follow up with you cloud team's set up because in my view, using "Active Directory - Integrated" with Azure SQL must mean that your cloud team has:

an on-premise Active Directory deployment,
either Azure AD Connect or Active Directory Federation Services enabled
someone who is the AAD admin of the Azure SQL server has already granted your identity the right permissions on the Azure SQL db

@alieus @NandanHegde15 any ideas what might be going on here?

another thing that would help is if you could go to the logs/dbt.log file and scroll down to the bottom where you're getting the error and share that here (or DM it to me) as a Gist. I'd be interested to see what SQL statement was trying to execute when you got the error message that you did.

Ah! Running CREATE SCHEMA new_schema in SSMS fails with the same error. I forgot that I need to add use CREATE SCHEMA new_schema AUTHORIZATION {DB user} where {DB user} is the security group that my login has access through. The schemas I've been using were created a while back and the AUTHORIZATION piece slipped my mind.
Is schema creation handled by a particuar macro that I can modify to include the authorization clause?

We are having the same issue, but only when the AAD user is part of an AAD group, and is not the first user attempting this:
posted it on stackoverflow, can you confirm that you have the same setup @jhoolachan?

This happens because the user can not be created implicitly. If you configured your database like me, and provided permission to an Azure AD group (and not the user themselves), CREATE SCHEMA is not able to implicitly create the user.
It seems documented in the remarks section here.

updating scope bc #277 isn't working yet

I did some testing for the use case of @w0ut0 and figured it out:
If we have #277, then we can set the authorization of the schema to the group you're in. That seems to work. You need a few permissions to create the schema and tables/views, but basically with #277 we should get there.
I documented the permissions in https://github.com/dbt-labs/docs.getdbt.com/pull/3378


Fix flaky test

Dynamically select a free port for STS server to bind, to avoid binding a port that is already in use.
This deflakes TestStsFlow.
https://github.com/istio/istio/issues/19918

@JimmyCYJ: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
fa5b912f04fedea1db37d1b5d92016dd46a90b99
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
fa5b912f04fedea1db37d1b5d92016dd46a90b99
link
/test lint_istio

gencheck_istio
fa5b912f04fedea1db37d1b5d92016dd46a90b99
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

In response to a cherrypick label: new pull request created: #21454


Add codeowners file

Description
The github CODEOWNERS file allows repository owners to specify owners of a repository or particular directories within a repo. This flexible approach allows automatic notification/addition of reviewers to pull requests relevant for that team or individual that is responsible for the repository. Later, we could add restrictions so that reviewers listed would have to accept the change before it could be merged, but I am not suggesting that right now.
Advantages:

guarantee that one of the reviewers has the ability to merge, meaning that we won't have any time between a change being marked accepted and merged.
the author of the PR would not have to figure out whose approval they need to get a change merged.

Issue(s) addressed
Experiment to  implement suggestion in https://github.com/orgs/JCSDA-internal/discussions/144

Perhaps consider adding a deputy as well?

I can add you if you like, but at the moment this codeowners thing just makes sure I am added by default to every PR - very light touch. I don't really want to spam multiple people with emails when there is no need? I won't be required to accept the PR for it to be merged, so doesn't matter if I get hit by a bus! :) I agree though we would want something else if we require a review from a particular group. I am really only adding this as a demo - where I think it will be most useful is in ufo - we can say, add met office team as a codeowners for a bunch of met office checks just so they get automatically notified or add a global owner to make sure one person has a handle on merging the changes in at JCSDA. I see every PR come in on this repo anyway so I don't think this will make much difference... just playing around.

@twsearle Understood. All good as it is. 😄


Add logging to BotFrameworkHttpClient.PostActivityAsync()

Fixes #3823

@johnataylor, could you please review this? Your approval is required for merging. Thanks.


Fix flaky TestHotReloadUIConfigTempFile

Signed-off-by: albertteoh<EMAIL_ADDRESS>
Which problem is this PR solving?

Fixes #2711

Short description of the changes

Flush file writes to disk to ensure subsequent reloads will pickup changes.
Create a new temp dir just for temp files (purged upon completion) to ensure a clean test environment and avoid aforementioned watch error.
Simplify and provide reusable file change wait logic based on approach taken in cert_watcher_test.go, using log messages as a signal.

Testing

Integration tested locally with jaeger-query. Confirmed log message appearing due to missing UI config path.

{"level":"info","ts":1609828122.089528,"caller":"app/static_handler.go:170","msg":"UI config path not provided, config file will not be watched"}

Ran 100 consecutive tests without error:

go clean -testcache && go test  -test.count=100 ./cmd/query/app -test.run TestHotReloadUIConfigTempFile

Kafka integration tests were passing for me locally. Any idea why it's not passing in CI?

Kafka integration tests were passing for me locally. Any idea why it's not passing in CI?

I don't understand why codecov thinks the fs_watcher.go file is untested, as TestHotReloadUIConfigTempFile will be executing these lines (my Goland IDE says this file is 100% covered).
Happy to add some simple tests instead of watcher/empty_test.go if need be.

I don't understand why codecov thinks the fs_watcher.go file is untested, as TestHotReloadUIConfigTempFile will be executing these lines (my Goland IDE says this file is 100% covered).
Happy to add some simple tests instead of watcher/empty_test.go if need be.

I don't understand why codecov thinks the fs_watcher.go file is untested

Perhaps because you exercise it from another package? Go tests to not extend coverage to other packages unless explicitly requested.

I don't understand why codecov thinks the fs_watcher.go file is untested

Perhaps because you exercise it from another package? Go tests to not extend coverage to other packages unless explicitly requested.

Thanks, Albert!

Thanks, Albert!


[Hub Generated] Review request for Microsoft.Devices to add version 2019-03-12

If you are a MSFT employee you can view your work branch via this link.
Contribution checklist:

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

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/5478
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/5478/commits/0c60a919da00031c0b3a2ef8a4bbb775c07c85a7

Looks good for the most part, just need a quick approval from ARM for the deleted models

Thanks. This means we have to meet with ARM team right?

@jlian ARM will post their comments on this PR, don't think you need to meet them since it is a relatively small change

Ok thanks. We're not ready for this to be merged into master yet (I'm preempting a little with this PR). Just want to make sure that we can get a heads up before the merge? Or is there a "hold-off" label like docs we can use?

I have added the DoNotMerge label

startbuild

startbuild

@jlian We are ready to merge this one. Please let us know when we can.

We're still getting ready on our side. Sorry for the delay

@jlian gentle reminder, we will close the PR by EOW if there is no activity

startbuild

Gonna close this until we can figure it out form our end


Updated sidebar listing and settings

Updated sidebar to list folders alphabetically and split folders to be grouped by apps and everything else. This allows for pulling the deluge folder out of the alphabetical listing in a clean way.
The theme was also updated the collapse folders by default for a cleaner aesthetic.

Current dependencies on/for this PR:

main

PR #1   👈

This stack of pull requests is managed by Graphite.


Unreadable error message

When I make an error in my hypr.conf a red box appears on the top of the screen over my waybar, describing the error. However, on my 40 inch monitor the font of this error message is so small that I can't read it. There should be a kind of default minimal font for system wide messages on hyprland.

fixed in 7cde50a018eb6a1f6e06f81768e73ecd5f982c2e


Cannot open mailto links[bug]

Describe the bug
Tauri cannot open mailto links

Reproduction
-- tauri.conf.json
"allowlist": {
	"all": true,
	"shell": {
		"open": true
	}
},

-- javascript
<a<EMAIL_ADDRESS>test </a>

Expected behavior
It should open the default mail application
Platform and versions
Environment
  › OS: Manjaro 22.0.0 X64
  › Node.js: 16.16.0
  › npm: 8.19.2
  › pnpm: Not installed!
  › yarn: Not installed!
  › rustup: 1.25.1
  › rustc: 1.64.0
  › cargo: 1.64.0
  › Rust toolchain: stable-x86_64-unknown-linux-gnu

Packages
  › @tauri-apps/cli [NPM]: 1.1.1
  › @tauri-apps/api [NPM]: Not installed!
  › tauri [RUST]: 1.1.1,
  › tauri-build [RUST]: 1.1.1,
  › tao [RUST]: 0.14.0,
  › wry [RUST]: 0.21.1,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../public
  › devPath: http://localhost:8082/
  › framework: Svelte

App directory structure
  ├─ node_modules
  ├─ src
  ├─ .svelte-kit
  ├─ src-tauri
  └─ static

Stack trace
No response
Additional context
No response

@lucasfernog Hi, I believe this bug is back in Tauri 2, as I get exactly the same page as in the above screenshot when I click a mailto: link (in version 2.0.6 of Tauri).

@yokljo do you have the shell plugin installed?

@FabianLars
I did add the shell plugin and have those permission:
  "permissions": [
    "core:default",
    "shell:allow-open",
    "shell:default"
  ]

And my mailto links won't open (nothing happens).

Any errors in the dev tools console? What about your tauri info output?
I'll try it out again once I'm back home but I don't see anything wrong in the plugin's code right now.

Using OP's example <a<EMAIL_ADDRESS>test </a>:

Windows: works
macOS: requires target="_blank"

The reason for that is that on Windows the os/webview handles those links already but on macOS it relies on the shell plugin which only reacts to a elements with the _blank target.
For me the current behavior is good enough, but feel free to open an issue here https://github.com/tauri-apps/plugins-workspace if you disagree.

Thanks, @FabianLars. With "_blank" it works as expected and this is good enough for me, too! 👍


Convert to use bnd-maven-plugin

We also add a resolve check to confirm the OSGi metadata can resolve.
I also tidied up some pom metadata which is used for OSGi metadata.
Two things to note:

This changes the Bundle-SymbolicName of the jar to the default which is the artifactId (which is also what assertj-core uses). It was org.assertj.guava. If we want to retain the original Bundle-SymbolicName, then we will need to set it in the Bnd configuration and the verify.bndrun file.
The verify check would fail since the jar imports org.assertj.core.internal which is not exported by assertj-core. So this is temporarily ignored by the -runsystempackages statement in the verify.bndrun file.

This changes the Bundle-SymbolicName of the jar to the default which is the artifactId (which is also what assertj-core uses). It was org.assertj.guava. If we want to retain the original Bundle-SymbolicName, then we will need to set it in the Bnd configuration and the verify.bndrun file.

Could this name change cause compatibility issues in the OSGi world? If not, I'd use the same pattern as assertj-core.

The verify check would fail since the jar imports org.assertj.core.internal which is not exported by assertj-core. So this is temporarily ignored by the -runsystempackages statement in the verify.bndrun file.

Perfect, we'll make sure to remove that once #70 is fixed.

Could the different symbolic name cause compatibility issues in the OSGi world?

Not really. At runtime, no one is likely to care about the BSN. It is more referenced during tool time if the tooling uses BSNs. So any downstream user may need to update such tool inputs when the update is released. But maven and gradle builds typically reference the jar via maven GAV (which is not changing).
When the assertj-core project switched to bnd-maven-plugin in 3.15, it also made the the BSN change (from org.assertj.core to assertj-core) and we had to adjust in the Bnd project. https://github.com/bndtools/bnd/commit/00a9d549a1ba4c3e2ef4720d9dd27b611ea7a8d6#diff-098e0861cd307b703acf27acb89560edf8bea267d2add2be2e758526215aabf0L3
But the real reason this change would not be a problem is #70 which means no one could use the current jar in OSGi at the moment. So the BSN change is quite safe :-)


Add interpreter for UniformDequantizeOp

Following the testing guidelines

closed via https://github.com/openxla/stablehlo/issues/2373


ALSA CTL fixes

Wow, many thanks. I knew that something was not right with ctl plugin when disconnecting BT device, but I've got no time to investigate it. And it has turned out that I've broke it :D It seems that one day I will have to add better test coverage for ctl.

Merged into master fa43ce2c89.


(Home Assistant Add-On) LED config is being ignored

Describe the issue you are experiencing
I'm using the current integration on Home Assistant.
Dunno why but suddenly the blue LED on my RPI-RF-MOD started to blink blue every second.
I read about messy internet connection, etc. but it seems to work just fine.
Describe the behavior you expected
Well, the LED settings shouldn't be ignored - at least it seems like so.
Steps to reproduce the issue
Don't know how to reproduce this... But I already disabled the "Info-LED" settings under "General settings" and disabled every check in the "Advanced settings", including the LED options there.
What is the version this bug report is based on?
<IP_ADDRESS>31014
Which base platform are you running?
rpi4 (RaspberryPi4)
Which HomeMatic/homematicIP radio module are you using?
RPI-RF-MOD
Anything in the logs that might be useful for us?
/etc/config # ls
InterfacesList.xml     addons                 firewall.conf          homematic.regadom.bak  measurement            rfd.conf               time.conf
NoAddonUpdateCheck     cloudmaticDisabled     firewallConfigured     hs485d                 neoDisabled            rpi4usb3CheckDisabled  timezone
NoBadBlocksCheck       crRFD                  firmware               hss_led_info.conf      netconfig              server.pem             tweaks
NoFSTRIM               crypttool.cfg          hideStickyUnreach      ids                    nut                    shadow                 userAckSecurityHint
NoPortForwardingCheck  disableLED             hm_addons.cfg          internetCheckDisabled  rc.d                   snmp                   userprofiles
ReGaHssVersion         disableOnboardLED      hmip_address.conf      localtime              rega.conf              syslog
TZ                     eshlight               homematic.regadom      log4j2.xml             rfd                    systemLanguage

Additional information
No response

I have the exact same problem, as described in the bug report, even on a fresh installation of HomeAssistant and Raspberrymatic CCU.

I'm pretty sure this has something to do with @jens-maus changes to hss_led in this merged commit:
https://github.com/jens-maus/RaspberryMatic/commit/ef8ebf3ed1c29e42808eedc0f9e801033e04abe3
Maybe a permission problem?
Oh and btw, I restored a backup of the add-on and disabled automatic updates for now. Everything's fine again now.


update license attribute

specifying the type and URL is deprecated:
https://docs.npmjs.com/files/package.json#license
http://npm1k.org/

Coverage remained the same at 100.0% when pulling e5b2670af205ca0fb6f589a396b89ab2845a91ac on pgilad:patch-1 into 55f90e3763af84c7eb599bd6403dbe14f63d5513 on wearefractal:master.


Added a learning Resource for web dev

https://www.w3schools.com/whatis/
This is w3 website that contains HTML,CSS,JAVASCRIPT and many more tech stacks used for web development.

@breakerh please have a look .

/assign

@ritikaaaa177 We already have w3schools.


Action Button in rows

Hello,
Can we have actions buttons in rows for datatable in vue without use of jquery or vanila js.
I need suggestions on how we can have buttons used though the components directly.
Thanks

See #6.


istioctl --set doesn't support escaping strings

Background: https://github.com/istio/istio/pull/17334

I can't for the life of me figure out the syntax for passing in values to the sidecarInjectorWebhook.injectedAnnotations parameter, to set the apparmor annotation slightly_smiling_faceMy issue is that the "key" part contains dot-notation so it attempts to split it up no matter how I try to encapsulate it
Using Helm I think the proper way is to encapsulate it in quotes and escape dots
istioctl manifest generate \
    --set cni.enabled=true \
    --set values.sidecarInjectorWebhook.injectedAnnotations."container\.apparmor\.security\.beta\.kubernetes\.io/istio-proxy"=runtime/default \
    --output ./generated

However this results in a mess in the actual manifest
injectedAnnotations:
  "container\": "map[apparmor\:map[security\:map[beta\:map[kubernetes\:map[io/istio-proxy:runtime/default]]]]]"
Doesn't matter if I try to escape the dots or not

Thanks!

adding complex stuff like this is really painful with helm --set and may not even be possible with istioctl.. I am not sure. What I would recommend is just to use a file. This will work:
ik manifest generate -f <(echo 'apiVersion: install.istio.io/v1alpha2
kind: IstioControlPlane
spec:
  values:
    sidecarInjectorWebhook:
      injectedAnnotations:
        container.apparmor.security.beta.kubernetes.io/istio-proxy: runtime/default')

I feel like this is one where we should just document the limitations of --set rather than sinking effort into improving it - we really want to discourage its use except for experimenting.

🖤this. This is key to moving away from installing/customizing Istio with helm. All our installs presently use an override.yaml to provision network load balancers.


Server crashing randomly after latest Updates

This Issue is interesting - the first half Hour all was fine, than, the Server crashes and restarting.
First after using the Guide, than, without anyone touched it.
Here is the Output:
http://hastebin.com/ikudoxabib.lua

Ok, I hope it works now again after I added a small check.
Sorry for the server crashes.

Thank you very much for your fast response!
Seems stable now - i hope i answer not to fast ;)


bug:

Describe the bug
When starting of dynamic informers for new CRDs is enabled, in an OpenShift cluster which has ~ 280 CRDs installed, the kubestellar controller manager shows many client-side throttling messages in the log.
I0205 02:01:39.499569       1 request.go:697] Waited for 17.144362886s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/kubeflow.org/v1alpha1
I0205 02:01:49.499937       1 request.go:697] Waited for 27.144577753s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/operator.tigera.io/v1
2024-02-05T02:01:53Z    INFO    Placement       Got object event        {"apiextensions.k8s.io/v1": "CustomResourceDefinition", "": "trustyaiservices.trustyai.opendatahub.io.trustyai.opendatahub.io"}
I0205 02:01:59.700193       1 request.go:697] Waited for 37.343447865s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/authorization.openshift.io/v1
I0205 02:02:09.899934       1 request.go:697] Waited for 47.543101288s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/observability.open-cluster-management.io/v1beta2
I0205 02:02:20.099804       1 request.go:697] Waited for 57.742738621s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/workload.codeflare.dev/v1beta1
I0205 02:02:30.100048       1 request.go:697] Waited for 8.794602429s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/packages.operators.coreos.com/v1
I0205 02:02:40.100055       1 request.go:697] Waited for 18.794475039s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/apiserver.openshift.io/v1
I0205 02:02:50.300102       1 request.go:697] Waited for 28.994482276s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/tekton.dev/v1
I0205 02:03:00.499286       1 request.go:697] Waited for 38.993577734s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/mcad.ibm.com/v1beta1
I0205 02:03:10.499820       1 request.go:697] Waited for 48.993988956s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/policy.open-cluster-management.io/v1
I0205 02:03:20.700052       1 request.go:697] Waited for 59.193708821s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/hive.openshift.io/v1
I0205 02:03:30.899001       1 request.go:697] Waited for 1m9.19315794s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/imageregistry.operator.openshift.io/v1
I0205 02:03:40.899537       1 request.go:697] Waited for 1m19.193581633s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/lighthouse.submariner.io/v2alpha1
I0205 02:03:50.899980       1 request.go:697] Waited for 1m28.994554135s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/certificates.k8s.io/v1
I0205 02:04:01.099382       1 request.go:697] Waited for 1m39.19373169s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/flowcontrol.apiserver.k8s.io/v1beta3
I0205 02:04:11.099508       1 request.go:697] Waited for 1m49.193740238s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/addon.open-cluster-management.io/v1alpha1
I0205 02:04:22.499022       1 request.go:697] Waited for 1.19403917s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/networking.k8s.io/v1
I0205 02:04:32.499979       1 request.go:697] Waited for 11.194659797s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/oauth.openshift.io/v1
2024-02-05T02:04:33Z    INFO    Placement       Got object event        {"apiextensions.k8s.io/v1": "CustomResourceDefinition", "": "predictors.serving.kserve.io"}
I0205 02:04:42.499920       1 request.go:697] Waited for 21.194715153s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/submariner.io/v1alpha1
I0205 02:04:52.698761       1 request.go:697] Waited for 31.193879603s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/events.k8s.io/v1
I0205 02:05:02.699252       1 request.go:697] Waited for 41.194219885s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/operators.coreos.com/v1alpha2
I0205 02:05:12.699427       1 request.go:697] Waited for 51.194329866s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/tekton.dev/v1
2024-02-05T02:05:17Z    INFO    Placement       Got object event        {"apiextensions.k8s.io/v1": "CustomResourceDefinition", "": "datasciencepipelinesapplications.datasciencepipelinesapplications.opendatahub.io"}
I0205 02:05:22.898830       1 request.go:697] Waited for 1m1.192828889s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/autoscaling/v1
I0205 02:05:32.898933       1 request.go:697] Waited for 1m11.192823041s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/crd.projectcalico.org/v1
2024-02-05T02:05:37Z    INFO    Placement       Got object event        {"apiextensions.k8s.io/v1": "CustomResourceDefinition", "": "trustyaiservices.trustyai.opendatahub.io.trustyai.opendatahub.io"}
I0205 02:05:42.899554       1 request.go:697] Waited for 1m21.19331421s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/operators.coreos.com/v1
I0205 02:05:53.099467       1 request.go:697] Waited for 1m31.194016075s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/autoscaling/v2
I0205 02:06:03.299339       1 request.go:697] Waited for 1m41.393774303s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/kubeflow.org/v1alpha1
I0205 02:06:13.499646       1 request.go:697] Waited for 1m51.594011096s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/multicluster.x-k8s.io/v1alpha1
I0205 02:06:23.699689       1 request.go:697] Waited for 2.395233485s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/proxy.open-cluster-management.io/v1beta1
I0205 02:06:33.898757       1 request.go:697] Waited for 12.594184958s due to client-side throttling, not priority and fairness, request: GET:https://kubernetes.default.svc/apis/edge.kubestellar.io/v1alpha1

Steps To Reproduce

Run the KS controller in a cluster with a large number of CRDs and observe the log

Expected Behavior
There should not be client-side throttling
Additional Context
It is most likely that client-side throttling is due to inefficiency of the code for detecting new api resources and starting the related informers. For each new CRD, the CRD handler invokes the dynamic client's ServerPreferredResources(), which lists all preferred API resources on the API server. At controller startup, this call happens for each CRD resource present on the cluster (which can be hundreds) and as a result that causes the client-side throttling.
https://github.com/kubestellar/kubestellar/blob/04fc0d219561582c2787f0b85fb29b6909282d70/pkg/placement/crd.go#L83
The code could be improved by just getting the new CRD from the CRD lister, finding the GVR for the resource and starting the informer for that GVR, rather than calling ServerPreferredResources for every new CRD.

@ezrasilvera it is related. It was not possible even to get to see this issue until https://github.com/kubestellar/kubestellar/pull/1707 is merged (because the controller crashes). After #1707 is merged, the controller does not crash but this issue happens. I preferred to deal with this with a second PR as it can be a bit more complex, and in a way it's an orthogonal issue.

(A) A CRD can define multiple versions. You probably want to work with just one.
(B) Discovery has an option for client-side caching, which would remove redundant calls to the apiserver(s).

@MikeSpreitzer B) can be quite useful and make it easier the fix. Do you have a reference for that option?

For discovery with client-side caching on disk, see https://github.com/kubestellar/kubestellar/blob/v0.14.2/cmd/kube-watchall/main.go#L55 for an example usage.

@waltforme it looks like things work ok on a OCP cluster with ~ 288 api resources, but @cwiklik has been testing on a cluster with 408 api resources and still gets thottling to the point that the controller won't register the CRDs and start. See attached log:
ks.log


SCP region restriction on AWS account is not allowing to validate SCP policies

Hi,
We have SCP policies setup on AWS account which allows us to deploy resource and restricted to specific region (say we are allowed to deploy resources only to ap-southeast-2 - Sydney region). I see in initialise/cmd.go check for simulate-principal-proxy is called at the time of validating SCP policies. Even though there are no restrictions on Sydney region around what AWS resource we create, when I run rosa init --region=ap-southeast-2 gives error saying Unable to validate SCP policies. Actions not allowed with tested credentials [ec2:* autoscaling:* elasticloadbalancing:* ..]
I see similar issue was resolved on ISI and UPI installer in the past https://bugzilla.redhat.com/show_bug.cgi?id=1757244
Could you please advice on this issue ?

Also, based on this article https://github.com/openshift/installer/issues/4048 it is advised not to simulate-policy restriction
https://github.com/openshift/installer/issues/4048

Also, based on this article https://github.com/openshift/installer/issues/4048 it is advised not to simulate-policy restriction
https://github.com/openshift/installer/issues/4048

/remove-lifecycle stale
This is impacting us in deploying ROSA. Our guardrails have restrictions on some resources specific to the account guardrails which will have no impact on deploying ROSA resources.

Does https://github.com/openshift/rosa/pull/328 fix your issue? It should be available as part of the v1.0.5 release. Otherwise, do you have the error output when you run the command?


autotest / rvm / autofeature=true / iconv;

loading autotest/cucumber_rails_rspec2
Autotest style autotest/cucumber_rails_rspec2 doesn't seem to exist. Aborting.

autotest will crash with AUTOFEATURE=true when iconv is not listed in your dependencies (Gemfile), cucumber depends on iconv for json.

Sorry, this looks like a minority issue. Unless you can provide a patch it isn't going to be fixed.


Catch docker exit code in Python to stop script

When you run multiple pipelines that depend on each other and one fails, the script keeps running and can start from the wrong output data as in the case of an evaluation pipeline following an indexing one

Fixed in #769


test.sh fails with bash complaining about 'continue' statement

When refactoring the code of test.sh some lines of code of the for loop were move into the testDynamicPackages function (see Injecting PR #25) causing the script to fail as explained  below.
Originally, in case one of the test artifact file  is missing we skip the test for the given distribution:release thanks to a continue statement in the for loop. Inadvertently this  continue statement has been moved into that function.
The logic need to be rework a bit so that it works with the function call.
Here are the logs depicted the issue;

  # Tests of the dynamic packages #
  ## Looking for debian-bullseye ##
  tmp created
  /workspace/tmp /workspace
  ### Copying the packages and the dockerfile for debian-bullseye ###
  cp: cannot stat '/workspace/containerd-v1.5.11_240322-1707/debian/bullseye/ppc64*/containerd.io_1.5.11*_ppc64*.deb': No such file or directory
  bundles-ce-debian-bullseye-ppc64le.tar.gz
  ls: cannot access 'containerd*ppc64*.*': No such file or directory
  ERROR: The docker-ce packages and/or the containerd packages and/or the Dockerfile is/are missing
  /home/prow/go/src/github.com/ppc64le-cloud/docker-ce-build/test.sh: line 86: continue: only meaningful in a `for', `while', or `until' loop
  ### # Building the test image: t_docker_debian_bullseye # ###

I have only traces of this issue for the build of containerd v1.6.6 using kubectl, and only for 2 (in first case) or 3 (in second case) of the 12 targets.
Looking at details of my data, this issue appears only when a distrib has not been built correctly (ubuntu-jammy and centos-9 due to building on a P8 , or a failed build due to web-access temporarily broken).
So, I have no data proving that this still appears.
I'll have to collecte more data when building again a new set of versions for Docker and Containerd. Or I have to rebuild 20.10.17 for collecting more traces.
I'll have to check that I save all useful traces.


Duplicately named and unsafe to upvalue moho functions

Some moho functions in different files have the same name. E.g.
CSlideManipulator:SetSpeed(speed)
and
CRotateManipulator:SetSpeed(self, degrees_per_second)
are both "SetSpeed" functions. In the above case you can maybe distinguish between them by the number of arguments, but there are quite a few more of them.
From the sim part of the moho functions the duplicates are:
{'CanAttackTarget', 'GetFactionIndex', 'IsOpponentAIRunning', 'AddAgentFalloffForce', 'GetBlueprint', 'SetResourceCap', 'Stop', 'base', 'GetSkirmishBase', 'IsMoving', 'SetHeadingPitch', 'GetCurrentTargetPos', 'SetEnabled', 'GetLauncher', 'GetVelocity', 'PlaySound', 'IsEnabled', 'RemoveBuildRestriction', 'GetMaxHealth', 'CreateProjectile', 'SetSpeed', 'Destroy', 'GetPersonality', 'AddBuildRestriction', 'GetWeaponCount', 'SetAcceleration', 'AddResourceManagerType', 'SetRegenRate', 'print', 'GetHealth', 'SetGoal', 'GetPosition', 'Enable'}
"base" and "GetBlueprint" appear quite a few times, both of which we don't want to touch anyway though.

Seemingly, upvaluing
local UnitWeaponMethods = _G.moho.weapon_methods
local UnitWeaponMethodsChangeMaxRadius = UnitWeaponMethods.ChangeMaxRadius
also leads to a weird error I can't explain. Hence I removed the lines
    "ChangeMaxRadius": "INFO: UnitWeapon:ChangeMaxRadius(value)",
    "ChangeMinRadius": "INFO: UnitWeapon:ChangeMinRadius(value)",

from the moho sim reference file for now

Removed "Enable" and "Disable" functions from the moho reference  in 962a562aa4b11569aa21c98037c5b362c7e134ea, as similarly named lua functions were upvalued incorrectly to those

Further removed the following potentially unsafe to upvalue moho references in commit dae4d4001ff4fc5271a0f646f94528bd5c51344a:
"Sim.<global>"
        "Damage": "INFO: Damage(instigator, origin, target, amount, damageType)",
        "GetBlueprint": "INFO: blueprint = GetBlueprint(entity)",
         "print": "INFO: Print a log message",

"Sim.AiSkirmishBase": {
        "print": "INFO: Print a log message",

"Sim.CAiAttackerImpl": {
        "Stop": "INFO: Stop the attacker",

"Sim.CPlatoon": {
        "Destroy": "INFO: CPlatoon:Destroy()",
        "Stop": "INFO: CPlatoon:Stop()",

"Sim.CollisionBeamEntity": {
        "IsEnabled": "INFO: bool = CollisionBeamEntity:IsEnabled()",

"Sim.Entity": {
        "GetBlueprint": "INFO: blueprint = Entity:GetBlueprint()",
        "Destroy": "INFO: Entity:Destroy()",
        "Kill": "INFO: Entity:Kill(instigator,type,excessDamageRatio)",
        "PlaySound": "INFO: Entity:PlaySound(eventname,cull)",

"Sim.UnitWeapon": {
        "GetBlueprint": "INFO: blueprint = UnitWeapon:GetBlueprint()",
        "PlaySound": "INFO: UnitWeapon:PlaySound(weapon,eventName)",

I don't know if all of them actually are unsafe, but as the editor doesn't understand the code and instead just upvalues all lua functions of the same name, having moho functions with a very generic name is almost certainly a bad idea.
See e.g. the problems that the "Disable" upvalue above caused by incorrectly upvaluing other lua functions called "disable" to the moho fct "disable" even though they had nothing much in common, besides the name.
Also, some of them were duplicately named and hence weren't upvalued with the current editor code anyway.

This upvalue:
self:GetWeaponByLabel('Suicide'):FireWeapon()

to
self:GetWeaponByLabel('Suicide')
UnitWeaponMethodsFireWeapon(self)

makes problems, which probably means that the upvalue is unsafe

Similarly to the above, the upvalue of SetCollision in SBOOhwalliStrategicBomb01_script.lua causes a desync and was hence removed from the moho reference in e5f89ba233a821335081240966505e9a8ccd3aa1


use HTTPS on ignition download

/test e2e-aws

please squash commits into a single one.
/ok-to-test

/hold

Created a fresh PR for same - https://github.com/openshift/hypershift/pull/453


Version 1.4.3 not untar properly

cordova config.xml
<plugin name="cordova-plugin-secure-key-store" spec="~1.4.0" />
When cordova prepare or add platform I always get
Discovered plugin "cordova-plugin-secure-key-store" in config.xml. Adding it to the project Fetching plugin<EMAIL_ADDRESS>via npm Error during untar for C:\Users\user\.cordova\lib\npm_cache\cordova-plugin-secure-key-store\1.4.3\package.tgz: Error: invalid tar file Error during untar for C:\Users\user\.cordova\lib\npm_cache\cordova-plugin-secure-key-store\1.4.3\package.tgz: Error: invalid tar file Error during untar for C:\Users\user\.cordova\lib\npm_cache\cordova-plugin-secure-key-store\1.4.3\package.tgz: Error: invalid tar file Failed to restore plugin "cordova-plugin-secure-key-store" from config.xml. You might need to try adding it again. Error: Failed to fetch plugin<EMAIL_ADDRESS>via registry. Probably this is either a connection problem, or plugin spec is incorrect.
When I tried with spec="1.4.2" this will work fine.
I also tried spec="1.4.3" and will have the same issue above.
Please check if 1.4.3 is properly working because my tgz cannot extract by cordova

@mikeccuk2005 Thanks for pointing this out. Seems issue was with the version number. Version number was not updated properly on all places. Fixed in v1.4.4. Try new release v1.4.4 and see if you still seeing this issue.
Thanks.


Add support for python3.9

Can Skfolio add support for python3.9?  Because some commonly used quantization packages  like qlib support only up to python3.9.

Related to this discussion
Also keeping in mind that python 3.9 will reach EOL next year so qlib will probably update its version soon.


About the license for this model

Thank you for sharing your great code. :smiley_cat:
What is the license for this model? I'd like to cite it to the repository I'm working on if possible, but I want to post the license correctly.

Converted ONNX + TFLite
https://github.com/PINTO0309/PINTO_model_zoo/tree/main/418_Diffusion-Low-Light

Thank you.

Thanks for your contribution, our model follows the MIT license.

Thank you!


Add files via upload

Applying Moorpark College to free student license IntelliJ program

@EvanBl I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host my.vcccd.edu.domains.lib.file not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


[IMPROVEMENT] Reject strict-local + RWX volume creation

Is your improvement request related to a feature? Please describe (👍 if you like this request)
When the server node is down, the RWX nfs server is unable to create on another node because of the strict-local volume.
Maybe we should reject strict-local + RWX.
Also strict-local is for distributed application only. Distributed application means it has replication capability, so they will only RWO.
Describe the solution you'd like

Describe alternatives you've considered

Additional context
https://suse.slack.com/archives/C02DR3N5T24/p1695171814534559

cc @ChanYiLin

PR: longhorn/longhorn-manager#3334

PR: https://github.com/longhorn/longhorn-manager/pull/3334

Hi @COLDTURNIP,
Move the status of Longhorn Sprint to Review to make the bot create Pre Ready-For-Testing Checklist and update the list.
Then you could move the status to Ready for Testing

Test Steps

Step 1. a Longhorn-ready cluster
Step 2. create a storage class (see attached example)

provisioner: driver.longhorn.io
parameters.dataLocality: strict-local
parameters.migratable: false

Step 3. create a workload, with a PVC that claim a ReadWriteMany volume of given above class
Step 4. verify the cluster

the pods of the workload must stick as pending because of PV
check the status of created PVC, it must be pending, and one of the event indicates that access mode rwx (migratable: false) is incompatible with data locality strict-local mode

The following example resources can be created/cleanup by kubectl apply -f example.yaml and kubectl delete -f example.yaml
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: longhorn-6735-strict-local-rwx
provisioner: driver.longhorn.io
parameters:
  dataEngine: v1
  numberOfReplicas: "1"
  dataLocality: strict-local
  migratable: "false"
  staleReplicaTimeout: "30"
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: 6735-strict-local-rwx
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 5Mi
  storageClassName: longhorn-6735-strict-local-rwx
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: 6735-strict-local-rwx-verify
  labels:
    app: 6735-strict-local-rwx-verify
spec:
  replicas: 1
  selector:
    matchLabels:
      app: 6735-strict-local-rwx-verify
  template:
    metadata:
      labels:
        app: 6735-strict-local-rwx-verify
    spec:
      containers:
        - name: 6735-strict-local-rwx-verify
          image: busybox
          command: ['sh', '-c', 'while true ; do now=$(date +%s) ; echo $now ; for vol in share1 share2 share3 ; do echo $now >>/mnt/data/${vol}/log || echo $now >/mnt/data/${vol}/log ; done ; ls -l $(find /mnt/data -name log) ; sleep 1 ; done']
          volumeMounts:
            - mountPath: /mnt/data/share1
              name: share1
      volumes:
        - name: share1
          persistentVolumeClaim:
            claimName: 6735-strict-local-rwx

Test Steps

Step 1. a Longhorn-ready cluster

Step 2. create a storage class (see attached example)

provisioner: driver.longhorn.io
parameters.dataLocality: strict-local
parameters.migratable: false

Step 3. create a workload, with a PVC that claim a ReadWriteMany volume of given above class

Step 4. verify the cluster

the pods of the workload must stick as pending because of PV
check the status of created PVC, it must be pending, and one of the event indicates that access mode rwx (migratable: false) is incompatible with data locality strict-local mode

The following example resources can be created/cleanup by kubectl apply -f example.yaml and kubectl delete -f example.yaml
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: longhorn-6735-strict-local-rwx
provisioner: driver.longhorn.io
parameters:
  dataEngine: v1
  numberOfReplicas: "1"
  dataLocality: strict-local
  migratable: "false"
  staleReplicaTimeout: "30"
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: 6735-strict-local-rwx
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 5Mi
  storageClassName: longhorn-6735-strict-local-rwx
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: 6735-strict-local-rwx-verify
  labels:
    app: 6735-strict-local-rwx-verify
spec:
  replicas: 1
  selector:
    matchLabels:
      app: 6735-strict-local-rwx-verify
  template:
    metadata:
      labels:
        app: 6735-strict-local-rwx-verify
    spec:
      containers:
        - name: 6735-strict-local-rwx-verify
          image: busybox
          command: ['sh', '-c', 'while true ; do now=$(date +%s) ; echo $now ; for vol in share1 share2 share3 ; do echo $now >>/mnt/data/${vol}/log || echo $now >/mnt/data/${vol}/log ; done ; ls -l $(find /mnt/data -name log) ; sleep 1 ; done']
          volumeMounts:
            - mountPath: /mnt/data/share1
              name: share1
      volumes:
        - name: share1
          persistentVolumeClaim:
            claimName: 6735-strict-local-rwx

@COLDTURNIP This seems like a simple case to automate with a robot test. I encourage you to give implementing the test a try.
cc @derekbit @longhorn/qa

Verified pass on longhorn master(https://github.com/longhorn/longhorn-manager/commit/6da14ea7d571c7e73b6eae663fc11154d346de1e)

following test steps,  can see creation of RWX + strict-local PVC jejected

  Warning  ProvisioningFailed    36s (x8 over 2m43s)   driver.longhorn.io_csi-provisioner-5847bdddf5-425wm_8a4fcc3e-7de1-4616-b9b4-9640c305a198  failed to provision volume with StorageClass "longhorn-6735-strict-local-rwx": rpc error: code = Internal desc = Bad response statusCode [500]. Status [500 Internal Server Error]. Body: [code=Internal Server Error, detail=, message=failed to create volume: unable to create volume pvc-865e5e1f-4c01-461b-b87f-e26cfcef2ea8: admission webhook "validator.longhorn.io" denied the request: access mode rwx (migratable: false) is incompatible with data locality strict-local mode] from [http://longhorn-backend:9500/v1/volumes]

Create RWX volume with data locality=strict-local from UI rejected as well.


Separate callbacks into own file

The Dash guide shows how to create a Dash app in a single file. However, the app file quickly grows to several hundred files for a moderately sized dashboard. The question of how to organize Dash apps, so that callbacks are in a separate file, has been raised several times in the Dash community forum without help. Please add a recipe for how to break down a Dash app into separate files, as can be seen in the Dash slapdash boilerplate. The Slapdash project is well-designed, but leaves a lot to be desired in terms of explaining why the files are structured in such a way and how to create a simple Dash project with that file structure.

Related issue in Slapdash project:
https://github.com/ned2/slapdash/issues/6
Related discussions in community forum:
https://community.plot.ly/t/dash-callback-in-a-separate-file/14122
https://community.plot.ly/t/callbacks-in-a-separate-file/15034

A better place for this issue would be in the dash-docs repo: https://github.com/plotly/dash-docs/issues/. In Dash Docs, we have a tutorial on this in https://dash.plot.ly/urls and I'd accept a PR to make that more discoverable


Module cache

Add cache module. Depends on #3832 config module.

@aurianer is this ready now?

As far as I concerned yes, but I'm not sure as some picycle tests failed due to socket timeout, what do you think ?

@aurianer the pycicle problems seem to be unrelated, however @msimberg might know better.

Thanks !


User/gustavoca/packing solution fix

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

Project coverage is 66.27%. Comparing base (d0929da) to head (47b8e29).
Report is 25 commits behind head on feature/sbom-targets-task.

Additional details and impacted files
@@                      Coverage Diff                      @@
##           feature/sbom-targets-task     #681      +/-   ##
=============================================================
- Coverage                      69.69%   66.27%   -3.43%
=============================================================
  Files                            277      277
  Lines                           8653     8649       -4
  Branches                        1009     1009
=============================================================
- Hits                            6031     5732     -299
- Misses                          2105     2408     +303
+ Partials                         517      509       -8

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


emitClient to specified player array

https://github.com/altmp/altv-issues/issues/948

Ready to merge


Fix 237 by including private function checks in package namespaces.

Fixes 237 by including private function checks in package namespaces.
Add a test for this.

@piccolbo Would be great if you could help test this patch.

Will do

Does not pass. Fails a little later, same way. Details to follow shortly.

This is the first failure I got
> ### ** Examples
>
> as.data.frame(
+   where(
+     input(mtcars),
+     cyl > 4))
Error in kv2rdd.list(if (ncol(k) == 0) f1(kv) else do.call(rbind, lapply(unname(split(kv,  :
  could not find function "keys.spark"
Calls: source ... computeFunc -> <Anonymous> -> FUN -> FUN -> kv2rdd.list
Execution halted
15/03/20 14:03:32 ERROR Executor: Exception in task 0.0 in stage 0.0 (TID 0)
org.apache.spark.SparkException: R computation failed with
 Error in kv2rdd.list(if (ncol(k) == 0) f1(kv) else do.call(rbind, lapply(unname(split(kv,  :
  could not find function "keys.spark"
Calls: source ... computeFunc -> <Anonymous> -> FUN -> FUN -> kv2rdd.list

So this is progress, because kv2rdd.list is private and is found but keys.spark is also private and is not found. I patched the code to fully qualify that name and it moves to a later point of failure:
Error in lazy_eval(x, c(data, list(.data = data))) :
  could not find function "as.lazy"
Calls: source ... f1 -> do.call -> <Anonymous> -> lazy.eval -> lazy_eval
Execution halted
15/03/20 13:56:23 ERROR Executor: Exception in task 0.0 in stage 0.0 (TID 0)
org.apache.spark.SparkException: R computation failed with
 Error in lazy_eval(x, c(data, list(.data = data))) :
  could not find function "as.lazy"
Calls: source ... f1 -> do.call -> <Anonymous> -> lazy.eval -> lazy_eval
Execution halted
	at edu.berkeley.cs.amplab.sparkr.BaseRRDD.compute(RRDD.scala:80)
	at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:262)
	at org.apache.spark.rdd.RDD.iterator(RDD.scala:229)
	at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:62)
	at org.apache.spark.scheduler.Task.run(Task.scala:54)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:177)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)

Now this is getting complicated. lazy_eval is in package lazyeval, imported by plyrmr (just like SparkR). as.lazy is an exported function in that package. So my initial idea about this being an issue with private functions only is not the correct one.

Thanks @piccolbo for reporting. Let me do more debugging on this later today.

BTW @hlin09 one thing you could try is to debug using plyrmr directly. @piccolbo can probably tell us if there are any setup instructions we should use.

I think it's a good idea because also of SPARKR-238. The instructions talk
about installing hadoop first, and I think you can just ignore that.
I think if you cut it to the chase you just need to do
library(devtools)
install_github("RevolutionAnalytics/rmr2", subdir = "pkg")
install_github("RevolutionAnalytics/plyrmr", subdir = "pkg")
We don't normally give these instructions because we need regular users to
install the official latest version.  You guys are not regular users. I see
some warnings but it seems to work. Otherwise let me know and I will point
you to the long way.
Then R CMD check path-to-plyrmr will repro 237
On Fri, Mar 20, 2015 at 4:28 PM, Shivaram Venkataraman <
<EMAIL_ADDRESS>wrote:

BTW @hlin09 https://github.com/hlin09 one thing you could try is to
debug using plyrmr directly. @piccolbo https://github.com/piccolbo can
probably tell us if there are any setup instructions we should use.
—
Reply to this email directly or view it on GitHub
https://github.com/amplab-extras/SparkR-pkg/pull/229#issuecomment-84193663
.

@piccolbo Thanks for the helpful instructions. I have just done some tests. Please try this patch and let me know if it works.

The tests pass the original error point, but fail elsewhere. From the error message, it seems an instance of SparkR-238, not 237. My suggestion is that we can assume 237 fixed and focus on 238, but maybe wait to close it until all plyrmr tests pass cleanly (I am assuming that all problems will prove to be related to changes in SparkR, which is only a working hypothesis).


De-irisify examples

Because eugenics
https://github.com/gadenbuie/de-iris-my-repos

Yup. That's also why I used the penguins dataset for more recent examples.

Cool cool. I'm working on it right now for all the other stuff, mostly just so I can remember how all the moving parts work 😂

Would it be worth adding palmerpenguins as a dependency, or just using mtcars or something?

I'm okay adding it as a dependency. It's a super light dependency and unlikely to change, and it gives us some good categorical variables to play around with.


If resource material is null in the material component & you try to change color T_[Fatal] P_[Medium] F_[Always]

Date of Detection

18/02/2021

Description

Removing the Component Material of a game object and adding it again, when trying to change the material color, engine crashes.

Reproduction

Game Object with material: First remove material component from the inspector. Second add a new material component using the selector under, last try to change the difuse color of the new material.

Expected Behaviour

The new material should addapt to the new color.

Engine Version

0.1

Additional context

Suggested Assignees

Any programmer

This issue has been fixed.


Done window on Login to Facebook

Hello all,
When I click on Login to facebook button, I get the done window in my ios as well as android device.
this window does not close automatically.
Please do the needful.

@shital0390 Have you found a solution for it? I am struggling with the same problem now


 Github isn't the place for this crude behavior, satire or not)

@NimuDevALTACC despite equally hostile responses from contributors/peers recently, a lot of your behavior is bannable; just take a moment to consider your account reported. (seriously, who is jimmy? Github isn't the place for this crude behavior, satire or not)

wise man, wise

@NimuDevALTACC despite equally hostile responses from contributors/peers recently, a lot of your behavior is bannable; just take a moment to consider your account reported. (seriously, who is jimmy? Github isn't the place for this crude behavior, satire or not)

Already reported her, cry about it NimuDev


getRawLinks() function working with linkedin, twitter, whatsapp, instagram.

ERROR
htmlspecialchars(): Argument #1 ($string) must be of type string, array given
When using the getRawLinks()  function with linkedin, twitter, instagram and other it pops up with the error above, please help.
Though its working fine with facebook.

I am facing the same problem here.  When I call this,
Share::currentPage()->twitter()->getRawLinks()
it returns,
array:2 [▼   "facebook" => ".......dummy link"   "twitter" => ".......dummy link" ]
So, It return previously generated all links whenever I called getRawlinks().
Simply problem is fixed with calling array index.
Share::currentPage()->twitter()->getRawLinks()['twitter']


cannot deploy pipeline with release.yaml

Expected Behavior
Actual Behavior
Deploy pipeline with kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.42.0/release.yaml.
While pipeline controller deploy failed, and the pod output with the log:
flag provided but not defined: -git-image
Usage of /ko-app/kubeconfigwriter:
-clusterConfig string
json string with the configuration of a cluster based on values from a cluster resource. Only required for external clusters.
-destinationDir string
destination directory where generated kubeconfig file will be stored.

Steps to Reproduce the Problem

kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.42.0/release.yaml

Additional Info

Tekton Pipeline version: v0.41.x ~ v0.42.0

More
I find it that the Entrypoint in the image .../controller:v0.40.2 is /ko-app/controller, but it has been changed to /ko-app/kubeconfigwriter in .../controller:v0.42.0 .

resolved


New package: SDeMo v0.0.1

Registering package: SDeMo
Repository: https://github.com/PoisotLab/SpeciesDistributionToolkit.jl
Created by: @tpoisot
Version: v0.0.1
Commit: 233bb3552e00b6f4641e72a6add33ae5f671f4df
Reviewed by: @tpoisot
Reference: https://github.com/PoisotLab/SpeciesDistributionToolkit.jl/commit/233bb3552e00b6f4641e72a6add33ae5f671f4df#commitcomment-147044411
Description: Work with species distributions in Julia

[noblock] The name is a mix between SDM (Species Distribution Model) and "demo", as it's meant to provide methods used in teaching -- this is meant to be loaded internally by another package so users are unlikely to only install this one

[noblock] It would be good to add a README to the subfolder to give this context

[noblock] fair point - done


probably_prime is skipping lots of primes, including primes below 2⁶⁴

From the documentation for probably_prime:

ProbablyPrime is 100% accurate for inputs less than 2⁶⁴.  See Menezes et al., Handbook of Applied Cryptography, 1997, pp. 145-149, and FIPS 186-4 Appendix F for further discussion of the error probabilities.

I have found counterexamples which show this assertion to be false:
assert!(probably_prime(&BigUint::from_u64(1579751).unwrap(), 20));
assert!(probably_prime(&BigUint::from_u64(1884791).unwrap(), 20));
assert!(probably_prime(&BigUint::from_u64(3818929).unwrap(), 20));
assert!(probably_prime(&BigUint::from_u64(4080359).unwrap(), 20));
assert!(probably_prime(&BigUint::from_u64(4145951).unwrap(), 20));

All 5 of these prime numbers are lower than 2⁶⁴, yet none cause probably_prime to return true.

The algorithm is based on the implementation in math/big from golang, including the reference. So it would be good to check if there is an issue in either the original implementation, the go implementation, or just this implementation.

Looks like it works fine in Go: https://go.dev/play/p/IfJc2JqaCjL

Thanks for checking, that is not good.

@darconeous I have a fix, at least for the primes you posted in https://github.com/dignifiedquire/num-bigint/pull/54

In my initial testing, this seems to be performing much, much better. The output now looks equivalent to OpenSSL's BN_is_prime function.

Thanks a lot for reporting and testing!


Serverless, FaaS, and how to implement it in gcp

剛好公司有個讀書會正在做這個主題，如果順利的話應該可以拿來分(ㄏㄨㄣˋ)享(ㄈㄣ)。

What's Serverless?
What's Faas(Function as a Service)?
What's thw difference?
Demo on gcp

Hi papago89さん,
My topic is Serverless, and FaaS is in regard to it. I think it will lose sight of the main point If I talk about microservice or PaaS and so on.
If just talk some trash, of course I can. But I think you are the ghost of microservice, maybe this agenda is more suitable for you.
I’m looking forward to your next seminar.


Consider running checkdoc on rust-mode.el in the test suite

checkdoc does some simple sanity checks to be sure that everything is well-documented.
http://cedet.sourceforge.net/checkdoc.shtml

I doubt anybody is motivated to add it.

Let's keep that open for now, and gradually improve the state of the doc.

I'll close this now. checkdoc can be pretty annoying when adding changes. And we obviously already have issues with contributions.


[Feature Request] Auto Player Sell at Futbin sell price

Being able to sell at the price that is in futbin.
Example: I am looking for the filter to buy common golds. Well, when buying each common gold, take the player's name, do a search for that player in futbin (through scrapping or futbin API) and automatically put it to sell at the lowest price that appears in futbin.
This could be implemented with a switch button (Futbin sell price on / off) and a textfield to say in which platform (PC,PS4, XONE) it has to be set.

Futbin is not so reliable this year. I think that checking and selling at the lowest price an on the market would be perfect.


refactor(client): docs, ts and test challenges

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

The chances for these utilities to have an incorrect output are low. Nevertheless small refactor with documentation, tests and TS for challenges page component and to learn path utility.
Related to #42256 since it is "cleanup" on update on a ts file.
Notes

Moved original test that were on challenges.test.ts to to-learn-path.test.ts

Nothing has changed since @huyenltnguyen's review, so I'm going to merge this as is.  Thanks again for your efforts to clean up our codebase, Victor.


Add Support For PostgreSQL Arrays In FromQueryResult Implementation Of JsonValue

I wanted to add tests and I tried to as well, but this particular change isn't testable with Mock database because with Mock database, the into_json works as expected even without this change since it directly serializes any rust type into json without matching column type for various backends.
PR Info
Bug Fixes

[x] If a PostgreSQL Model contains array fields, and is serialized as json while querying (using into_json()), the array fields are always skipped. This is because the current implementation of FromQueryResult for JsonValue doesn't handle postgres arrays at all. This PR adds support for the same.

For example, consider the following model (I'm skipping the obvious stuff like derive macros):
pub struct Pizza {
    #[sea_orm(primary_key, auto_increment = false)]
    pub id: i64,
    pub name: String,
    pub toppings: Vec<String>,
}

We also assume that the toppings field is not an empty array in the db for any rows.
If we query this model and expect a json result:
let result = pizza::Entity::find().into_json().all(db).await?;

The final JSON output is always:
{
    "id": 1,
    "name": "Pepperoni"
}

but the expected output is:
{
    "id": 1,
    "name": "Pepperoni",
    "toppings": ["Cheese", "Pepperoni"]
}

Hello guys, is anything lacking in this PR? This is a fix that we need for our project and have to hack around with it right now.
If you feel like something is missing or incorrectly done, let me know. But no activity doesn't help.

root json arrays would be very helpful to me as well, thanks @anshap1719

HI @tyt2y3, can you please review this PR? Thanks.

@tyt2y3 wanna take a look?

@billy1624 @tyt2y3 Guys?

Hey @anshap1719, sorry, we will revisit this tonight :)

@billy1624 Any updates?

For some reason it missed my inbox. However this seems to have touched a deep and quite difficult part of the library.
Need a fresh pair of eyes to review.

@tyt2y3 Totally understandable. Would it be okay if I just add comments to changes in the "Files changed" view?

@tyt2y3 Totally understandable. Would it be okay if I just add comments to changes in the "Files changed" view?

Sure, that'd be appreciated.

@tyt2y3 Done. Hope that helps.

@tyt2y3 Did you get a chance to review this again yet?

@tyt2y3 Sorry, I accidentally hit "Close with comment" for my last comment 😅

@tyt2y3 Any updates on this one? Would really appreciate it if we can get this into the next release whenever that happens.

@billy1624 @tyt2y3 Guys?

Got you. I'll put this on my pipeline

Thanks @tyt2y3

Thank you for your patience.

Awesome, thanks for your efforts as well @billy1624 that improved the PR.


cmd/compile: generic error does not identify relevant type

% cat /tmp/x.go
package p

type T[X, Y any] struct {
	x X
	y Y
}

var _ T[int]

func t(x, y int) int

var _ = t(1)
% go build /tmp/x.go
# command-line-arguments
/tmp/x.go:8:7: got 1 arguments but 2 type parameters
/tmp/x.go:12:11: not enough arguments in call to t
	have (number)
	want (int, int)
%

Note the difference in errors.
The ordinary parameter error says "not enough arguments in call to t" and then gives the argument types.
The generic error says "got 1 arguments but 2 type parameters" which does not identify the relevant type (T in this case) and is also easily misread to mean "got 1 arguments and got 2 type parameters but these numbers don't match". It would be better for this error to be worded more like the non-generic error. Perhaps:
/tmp/x.go:8:7: not enough type arguments for type T: have 1, want 2

or even
/tmp/x.go:8:7: not enough type arguments for type T
	have (int)
	want (any, any)

/cc @griesemer

@gopherbot - Assign this me.

Changed to 1.22 again. The CL was ready before the change to 1.23. The change simply produces a better error message in case of an error. This is safe, even if late in the game.


Upgrade to DTDLv3

Upgraded context to dtmi:dtdlcontext;3. Made this an array for all models so it would be sent to and retrieved from ADT consistently.
Canonicalized the locations which had verbose dtdl schemas to simple form (enums, maps, etc.)
Added quantitativeTypes extension where required.

Looks good to me too.


Simple SDK app does not recover after networking service restart

What happened?
The resampler is not able to get power metrics after restarting the networking service where a simple SDK application is running
__main__ INFO:Latest battery consumption: Sample(timestamp=datetime.datetime(2024, 8, 12, 12, 49, 57, tzinfo=datetime.timezone.utc), value=Power(value=0.0, exponent=0))
__main__ INFO:Latest net consumption: Sample(timestamp=datetime.datetime(2024, 8, 12, 12, 49, 57, tzinfo=datetime.timezone.utc), value=None)
frequenz.sdk.timeseries._resampling WARNING:No relevant samples found for: component_metric_request<namespace=grid-c01a4328-2e56-4017-b3df-594723abe827,component_id=1001,metric_id=ACTIVE_POWER,start=None>
frequenz.sdk.timeseries._resampling WARNING:No relevant samples found for: component_metric_request<namespace=battery-pool-frozenset({2009, 2003, 2006})-80a2a06b-34db-4545-8d92-01eeb4ef53da,component_id=2002,metric_id=ACTIVE_POWER,start=None>
frequenz.sdk.timeseries._resampling WARNING:No relevant samples found for: component_metric_request<namespace=battery-pool-frozenset({2009, 2003, 2006})-80a2a06b-34db-4545-8d92-01eeb4ef53da,component_id=2005,metric_id=ACTIVE_POWER,start=None>
frequenz.sdk.timeseries._resampling WARNING:No relevant samples found for: component_metric_request<namespace=battery-pool-frozenset({2009, 2003, 2006})-80a2a06b-34db-4545-8d92-01eeb4ef53da,component_id=2008,metric_id=ACTIVE_POWER,start=None>

Also pleae notice that a similar behaviour is observed when pausing the application with ctrl-z and resuming it after +20 minutes.
What did you expect instead?
The resampler recovers getting new power values after a networking service restart.
Affected version(s)
Observed in v0.25.2, v1.0.0-rc601 and higher versions
Affected part(s)
Core components (data structures, etc.) (part:core), Microgrid (API, component graph, etc.) (part:microgrid)
Extra information
Simple application to reproduce the issue:
# License: All rights reserved
# Copyright © 2024 Frequenz Energy-as-a-Service GmbH

"""Application to read net and battery pool power consumption data."""

import asyncio
import logging
import os
from datetime import timedelta

from frequenz.channels import Receiver, select, selected_from
from frequenz.sdk.actor import Actor
from frequenz.sdk import actor, microgrid
from frequenz.sdk.timeseries import Power, Sample
from frequenz.sdk.timeseries._resampling import ResamplerConfig

_logger = logging.getLogger(__name__)

class PowerReadingActor(Actor):
    """Actor to read net and battery pool power consumption data."""

    def __init__(
        self,
        recv_net_consumption: Receiver[Sample[Power]],
        recv_bat_consumption: Receiver[Sample[Power]],
    ):
        """Initialize the actor.

        Args:
            recv_net_consumption: Receiver channel for grid power consumption
                without battery pool power consumption data.
            recv_bat_consumption: Receiver channel for battery pool power
                consumption data.
        """
        super().__init__()
        self._recv_net_consumption = recv_net_consumption
        self._recv_bat_consumption = recv_bat_consumption

    async def _run(self) -> None:
        """Run the actor."""
        async for selected in select(
            self._recv_net_consumption,
            self._recv_bat_consumption,
        ):
            if selected_from(selected, self._recv_net_consumption):
                net_consumption_sample = selected.message
                if not net_consumption_sample:
                    raise ValueError("Net consumption data channel closed.")
                _logger.info("Latest net consumption: %s", net_consumption_sample)

            elif selected_from(selected, self._recv_bat_consumption):
                bat_consumption_sample = selected.message
                if not bat_consumption_sample:
                    raise ValueError("Battery pool consumption data channel closed.")
                _logger.info("Latest battery consumption: %s", bat_consumption_sample)

async def run() -> None:
    """Run the actor."""
    logging.basicConfig(
        level=logging.DEBUG, format="%(asctime)s %(name)s %(levelname)s:%(message)s"
    )

    microgrid_url = os.getenv(
        key="MICROGRID_API_URL", default="grpc://[2a01:4f8:c010:1adf::1]:62060"
    )

    await microgrid.initialize(
        server_url=microgrid_url,
        resampler_config=ResamplerConfig(
            resampling_period=timedelta(seconds=1.0),
        ),
    )

    grid = microgrid.grid()
    battery_pool = microgrid.new_battery_pool(priority=1)

    net_power_formula = (grid.power - battery_pool.power).build("net_power")

    power_reading_actor = PowerReadingActor(
        recv_net_consumption=net_power_formula.new_receiver(),
        recv_bat_consumption=battery_pool.power.new_receiver(),
    )

    await actor.run(power_reading_actor)

def main() -> None:
    """Run the application."""
    asyncio.run(run())

if __name__ == "__main__":
    main()

Commands to restart the networking service:
sudo nmcli networking off
sleep 5
sudo nmcli networking on

Something to look into: using keepalive: https://grpc.io/docs/guides/keepalive/
We probably should add keepalive options (with some sane defaults) to the base client URL parsing, and my feeling is we need to re-create the gRPC channel if the connection dropped.

Nothing is received/raised calling the stream method after restarting the networking service and the retry strategy never kicked in, I'm referring to this line of code here https://github.com/frequenz-floss/frequenz-client-base-python/blob/v0.x.x/src/frequenz/client/base/streaming.py#L89
First problem is a missing timeout for the streaming component data, I mean the timeout is always set to None. Though adding a timeout only helps the retry strategy take effect but the gRPC stream still seems dead.
Then the stream method https://github.com/frequenz-floss/frequenz-client-base-python/blob/v0.x.x/src/frequenz/client/base/streaming.py#L40-L41 is called on each retry but it does not have any effect if the gRPC stream is already dead.
The client might need to recreate https://github.com/frequenz-floss/frequenz-client-microgrid-python/blob/v0.x.x/src/frequenz/client/microgrid/_client.py#L242-L244 when the gRPC stream is dead

The only working solution I found so far (without considering keepallive) is re-creating the gRPC channel

Tested using keepalive options and it works. This should probably be the long run solution

The fix needs to be addressed for https://github.com/frequenz-floss/frequenz-client-base-python/issues/68

Do you have any minimal test case to reproduce this that doesn't depend on the SDK (i.e. it uses only the client)? We need to figure out at which level we should re-create the channel too, or did you observed that when using keep-alive the channel automatically recovers (re-connects)?

I observed that using keep-alive the gRPC channel recovers.
I only have a small program to reproduce the problem without the SDK. You can set timeout or/and configure keep-alive to see the different behavior.
import asyncio
from typing import Any, cast

import grpc.aio as grpcaio
from frequenz.api.microgrid.microgrid_pb2 import ComponentData as PbComponentData
from frequenz.api.microgrid.microgrid_pb2 import ComponentIdParam as PbComponentIdParam
from frequenz.api.microgrid.microgrid_pb2_grpc import MicrogridStub
from frequenz.client.base import streaming

from frequenz.client.microgrid._component_data import MeterData

HOST = "[2a01:4f8:c010:1adf::1]"
PORT = 62060
COMPONENT_ID = 1001

TIMEOUT: float| None = None #10.0

keepalive_options = [
    # ("grpc.keepalive_time_ms", 10000),  # 10 seconds
    # ("grpc.keepalive_timeout_ms", 5000),  # 5 seconds
    # ("grpc.keepalive_permit_without_calls", 1),  # Allow pings even without active calls
    # ("grpc.http2.max_pings_without_data", 0),  # Unlimited pings without data
]

async def run() -> None:
    """Run the main function."""
    target = f"{HOST}:{PORT}"
    grpc_channel = grpcaio.insecure_channel(target, options=keepalive_options)
    microgrid_grpc_stub = MicrogridStub(grpc_channel)

    broadcaster = streaming.GrpcStreamBroadcaster(
        f"raw-component-data-{COMPONENT_ID}",
        lambda: cast(
            grpcaio.UnaryStreamCall[Any, PbComponentData],
            microgrid_grpc_stub.StreamComponentData(PbComponentIdParam(id=COMPONENT_ID),
                                                    timeout=TIMEOUT),
        ),
        transform=MeterData.from_proto,
        retry_strategy=None,
    )

    broadcaster_recv = broadcaster.new_receiver()

    async for data in broadcaster_recv:
        print(data)

asyncio.run(run())

Please note that there is no timeout currently set for the microgrid API client when it calls StreamComponentData to  construct GrpcStreamBroadcaster. In the example above I was using it just for testing purposes but it is probably not needed if gRPC channel keep-alive is configured.

Thanks @daniel-zullo-frequenz , I will have a look and do some tests soon and create issues where appropriate (most likely client-base).

I think we already figured out what the problem is and that it should be fixed at a lower level than the SDK (API client/server). So I will close for now, we can reopen if we feel we need to gather more info.


Incorrect least permissions for task "Invalidate refresh tokens of non-admins"

In the document in section Users it is listed the least privileged role for "Invalidate refresh tokens of non-admins" is Password Administrator.
This seams not to be correct. While testing on a non-admin-user both in the Portal and using Powershell this role does not grant this privilege. In the portal, the "revoke sessions" option is greyed out. In powershell you get a Forbidden as seen below.
Get-AzureADUser -SearchString << some user >> | Revoke-AzureADUserAllRefreshToken
Revoke-AzureADUserAllRefreshToken : Error occurred while executing RevokeUserAllRefreshTokens
Code: Authorization_RequestDenied
Message: Access to invalidate refresh tokens operation is denied.
RequestId: cb9dd4e4-8a5c-4e90-9124-6d8e9831f669
DateTimeStamp: Thu, 05 May 2022 07:28:45 GMT
HttpStatusCode: Forbidden
HttpStatusDescription: Forbidden
HttpResponseStatus: Completed

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

ID: 0f9558c0-abb6-24f8-81c8-9000b80539e8
Version Independent ID: a4739135-863b-27bb-1f2e-cf297f21b4cc
Content: Least privileged roles by task - Azure Active Directory
Content Source: articles/active-directory/roles/delegate-by-task.md
Service: active-directory
Sub-service: roles
GitHub Login: @rolyon
Microsoft Alias: rolyon

Update: the correct role for this task seems to be "Authentication Admin".

@Dawnes Apologies for the delay in the response and all the inconvenience caused because of the issue.
Thank you bringing this to our attention.
We have verified the above mentioned statement and we have created an internal item with our content team to make the required changes.


Web: Timeline Mobile Styling

the timeline inside a case is only optimized for desktop at the moment, looks really bad in mobile

is the same for Escrow V2 timeline:

this should be fixed inside the ui-components-library repository, then bump the npm version of the library and update the library version in kleros-v2, escrow-v2, and curate-v2 repos.

I'd like to help out.
We  could put the texts on the right such as Case #110, arbitration fees deposited below the title in the mobile screen.

If we want to avoid single line titles in desktop as such

We can add a character max-width of 40ch or something like so.

Before/After


Wrong server name for PureScript

The following gives an error.
LspInstall purescriptls
I had to use this instead.
LspInstall purescript

Ah, thanks!


Separating the Quake1 Example into 2 playable examples

I figured this out while working on #20
If I replace the player code that coded for normal collisions (BSP tree, collisions from MAP file, or -wrbrushes) with the other one that used a point as a shape that coded for clips, it might not work well for people who will use it for custom games, so I think we should separate the Quake1 example from the original I created specifically to view maps. So it lacks a lot of optimization (when reading a PAK file, it loads all files at once. which uses a lot of memory) to 2 examples :

For Quake-clone games : Implemented friendly for Godot users

Use normal collisions. Extracted from MAP brushes or -wrbrushes in BSPX if has
The entities are clean-room implemented in GDScript. No QuakeC code required

For playing Quake : Specifically implemented for playing PAK files

Use clip node collisions. Should be able to play with the original maps from ID1 paks
The entities do functionally follow the QuakeC code. Also include the monsters too (I've been secretly working on a QuakeC to GDScript)
Additional stuff like console commands and CVars (Or should be added to the above example too ?)

That sounds like a smart way to separate the two. The only thing to consider perhaps is that taking QuakeC code and translating it might still mean that the generated code has to be GPL compliant, which makes it not MIT licence compliant, and at that point I will not touch it anymore :) since it will mean making custom games with this project (if GPL) will be a pain for selling on platforms like mobile and consoles etc...

The clip nodes collision, etc, can be included in the project AFAIK it's just reading BSP data, but the later part of including QuakeC translated code might be an issue, maybe there is a separate "quake loader" game folder which can be separately released under GPL?

Unless, your QuakeC converter translates in realtime? Then someone could either use the quake PAK data or write custom QuakeC that is not GPL as well?

The latter example is also clean-room implemented (including the converter too). The content from PAKs whether the maps, models, or codes are real-time converted and will never be uploaded to this repository.
Regardless of whether the game contents are official, fanmade, GPL licensed, or not. It probably wouldn't affect the project as they don't contain any proprietary content. But this also means that the example should be only used for trying out the gameplay. (Sounds like an indirect GPL ;) )
And, of course, I won't let my project becomes GPL. It has to be MIT forever.

If you manage to make a runtime QuakeC interpreter/translator that sounds awesome, it would open the door for running mods and custom maps people make. Sound awesome. Although personally I'd preffer to write GDScript for custom stuff because QuakeC is kind of lame :P


disable mTLS using a flag

Please describe the Improvement and/or Feature Request

Disable mTLS using a flag on install: osm install --disable-mTLS For the first run, we may also want to require the --disable-access-control flag if you use --disable-mTLS if it helps us keep the osm-controller logic simple.
Scope

[x] New Functionality
[ ] Traffic Access Control
[ ] Traffic Specs
[ ] Traffic Metrics
[ ] Traffic Split

Possible use cases

As a user, I'd like to install OSM. I'm most familiar with metrics related features of service mesh so I'd like to start by disabling mTLS and access control. I only want to view metrics and shift traffic. Once I understand the value, then I'll add mTLS and access control features to my OSM setup.

We bulit OSM with the assumption that certs are always used for Envoy-to-Envoy and Envoy-to-ControlPlane communication. It'd take some work to turn off mTLS. We are leaving this issue open to hear from the community and see whether folks are interested in implementing this.

@addozhang hinted in https://github.com/openservicemesh/osm/issues/2012#issuecomment-730684175 that it would be desirable to turn off mTLS for gradual migration of new services into the mesh.

@shashankram thanks.
Yes, this is our requirement. We are running hundreds of spring cloud serivces on openshift. The Netflix Eureka acts as service discovery. Access among services is via pod-ip:port, and there is only ip:port existing in HOST field of request.
We are planing to migrate to mesh architech to lervage power of mesh, such as trafflic split.
At the same time, we hope the migration smoothly.

@shashankram thanks.
Yes, this is our requirement. We are running hundreds of spring cloud serivces on openshift. The Netflix Eureka acts as service discovery. Access among services is via pod-ip:port, and there is only ip:port existing in HOST field of request.
Except above, we hope that the matches(HttpRouteGroup) of v1alpha3.TrafficSplit could be implementd in RDS_Inbound route. During migration, the commucation mode is mixed: enovy to envoy, envoy to non-mesh and non-mesh to envoy.
With all above, it will help us to push the migration to mesh. I think not only us, many teams will welcome this. It will be like replace tire for a running car. After all, companies or teams are operating an existing system/architech.
we all hope the migration smoothly.

@addozhang your requirements make sense to me. I will try to summarize the high level requirements in https://github.com/openservicemesh/osm/issues/2012.


Small error in code

on this line:
https://github.com/rasbt/python-machine-learning-book-2nd-edition/blob/063b6734b5f857b18b1790e95526445ac62111af/code/ch12/neuralnet.py#L58
y.shape[0] is already a plain integer.

Thanks for the note, just removed the extra int casting. Kind of weird, it only appeared in the neuralnet.py code, seems like I already removed that some time ago in the actual book code in ch12.py / ch12.ipynb
Anyways, thanks!


Fast path for negative case when relating to unions of primtives

This PR implements a fast path for the negative case of relating a literal type to a union of primtive types. This reduces the check time of the example in #53191 from ~45s to ~0.4s.
Fixes #53191.

@typescript-bot test this
@typescript-bot user test this inline
@typescript-bot run dt
@typescript-bot perf test faster
@typescript-bot test top100

@typescript-bot pack this

RE: DT above, the results are still compared against nightly, so some of those are preexisting breaks caused elsewhere today and can be ignored. I think @gabritto is looking switching that to compare against main.
(In particular, DOM was updated which is most of the breaks, plus a dts emit change I need to go update in ramda.)

This likely supersedes https://github.com/microsoft/TypeScript/pull/50640 and thus fixes https://github.com/microsoft/TypeScript/issues/47511 and https://github.com/microsoft/TypeScript/issues/47481
I tested the case from #47481 and the check time went from 12s to 0.5s on my machine

@typescript-bot run DT

Should we add the test cases from https://github.com/microsoft/TypeScript/issues/47511, https://github.com/microsoft/TypeScript/issues/47481, and https://github.com/microsoft/TypeScript/issues/53191?

All that's interesting about those tests is their performance, and we don't measure that. So don't think so.

If they "fail", then they'll take long enough to take out the runner, or at least be suspiciously slow. Maybe that's enough, but I don't feel strongly.

The regression reported here can be traced back to this PR. The minimal~ repro case for it is this:
enum AutomationMode {
  NONE = "",
  TIME = "time",
  SYSTEM = "system",
  LOCATION = "location",
}

interface ThemePreset {
  id: string;
}

interface Automation {
  mode: AutomationMode;
}

interface UserSettings {
  presets: ThemePreset[];
  automation: Automation;
}

interface ExtensionData {
  settings: UserSettings;
}

export function getMockData(): ExtensionData {
  return {
    settings: {
      presets: [],
      automation: {
        mode: "",
      },
    } as UserSettings,
  }
}

TS playground


Add user interface logging

Investigate splitting this out into separate configurable JavaScript file, possibly on a separate branch.

Added in PR #39.


Update the segment write key for production

This change relates to #3255 -- Creating a new source in segment so that once the new version of the App is deployed that properly honors users data preferences, only clean data exists.


Add Authorization Bearer header

[x] Add Authorization Bearer header
[x] Remove cookie
[x] Introduce /api/v1/user_refresh_token entry point
[x] Minor refactor

Rebased on master

1.0.33~pr313-526 deployed on prod as discussed


[Suggestion] Position is continuously updated with apparently no filtering (android)

Is your feature request related to a problem? Please describe.
I am developing an app with a map display with overlays showing the current position. While testing it became obvious that the position is being rapidly updated continuously even though the test device is stationary. A similar native app I developed on android requests updates with a delay which slows it down. The snippet of code in  data_stream_factory.dart:
              final subscription =
                  Geolocator.getPositionStream().listen((position) {
                streamController.sink.add(position);
              });

does not appear to apply any conditions to the stream.
Describe the solution you'd like
According to the Geolocator.getPositionStream(). API, it is possible to add a distance filter. As the geolocation on devices is unlikely to be more accurate than about 5M, adding a distance filter of say 1M should slow it down considerably, while still tracking a moving device.
Describe alternatives you've considered
It is possible to disguise the issue by reducing the precision of the position overlay, but that is only hiding the issue.

Thank you for bringing this to our attention. The positionStream used in the CurrentLocationLayer of the flutter_map_location_marker relies on the default behavior of the Geolocator.getPositionStream() method, which indeed has a distanceFilter set to 0, meaning it will notify the stream for every minor change in position.
To incorporate your requirement for throttling the position updates, you can customize the positionStream by specifying a distanceFilter. This will ensure that the position updates are only received when the device has moved by the specified distance. You can set the distanceFilter to 1 meter or any other value that suits your needs.
Here is how you can provide a custom positionStream with a distanceFilter to the CurrentLocationLayer:
CurrentLocationLayer(
  positionStream: LocationMarkerDataStreamFactory().fromGeolocatorPositionStream(
    stream: Geolocator.getPositionStream(
      locationSettings: LocationSettings(distanceFilter: 1), // Set the distance filter to 1 meter
    ),
  ),
)

Please refer to the positionStream property documentation for further customization.
While we currently have no plans to change the default distanceFilter in the flutter_map_location_marker package, your feedback is valuable, and we'll consider it for future updates. Meanwhile, the solution above should address your concern by reducing the frequency of position updates when the device is stationary.


new error TypeError('must start with number, buffer, array or string')

wp-content/themes/projectname/scss/main.css found.
buffer.js:167
throw new TypeError('must start with number, buffer, array or string');
^
TypeError: must start with number, buffer, array or string
at fromObject (buffer.js:167:9)
at new Buffer (buffer.js:58:10)
at Transform.transform [as _transform] (/Users/username/dev/projectname/node_modules/gulp-combine-media-queries/index.js:152:21)
at Transform._read (/Users/username/dev/projectname/node_modules/gulp-combine-media-queries/node_modules/readable-stream/lib/_stream_transform.js:184:10)
at Transform._write (/Users/username/dev/projectname/node_modules/gulp-combine-media-queries/node_modules/readable-stream/lib/_stream_transform.js:172:12)
at doWrite (/Users/username/dev/projectname/node_modules/gulp-combine-media-queries/node_modules/readable-stream/lib/_stream_writable.js:237:10)
at writeOrBuffer (/Users/username/dev/projectname/node_modules/gulp-combine-media-queries/node_modules/readable-stream/lib/_stream_writable.js:227:5)
at Transform.Writable.write (/Users/username/dev/projectname/node_modules/gulp-combine-media-queries/node_modules/readable-stream/lib/_stream_writable.js:194:11)
at DestroyableTransform.ondata (/Users/username/dev/projectname/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:583:20)
at emitOne (events.js:77:13)
Segmentation fault: 11

+1
But as you can see last commit was a year ago.

I didn't notice that. :+1:
gulp-group-css-media-queries fix my problem

@prosenjit-itobuz thanks a lot for good replacement. :+1:

@prosenjit-itobuz  thanks!!!!!

@prosenjit-itobuz Thank you good sir!


Remove Unpin bound in wait_until and clean up CI

Hello, currently arc_waker and borrowed_waker do require predicate P to be unpin, so unconditionally implementing Unpin for WaitUntil is sound for those cases. DiatomicWaker::wait_until is no longer requiring P to be Unpin, and while it is unsafe function, it is not mentioning in it's documentation that P must be Unpin, so this is theoretically unsound (I guess will not happen in practice, as who would have !Unpin predicate?).
I assume it is some leftover after https://github.com/asynchronics/diatomic-waker/commit/4a208d2f8725a6d3b0343aa805e22c24c3bb82ba, this PR is continuing that commit, as safe versions did still required Unpin. Now Unpin is automatically implemented for WaitUntil, and if P would be !Unpin, WaitUntil would be too.

Thank you very much, including for the CI clean-up!


Fluid form

The problem
Carbon Design System has introduced fluid version of several controls, notably form controls.
The solution
Implement fluid variants for:

Text input
Text area
Dropdown
ComboBox
Multi-select
Date picker
Number input
Select

@asudoh This issue was discussed in the review meeting earlier today and the assumption was made that the purpose is to maintain feature parity with Cargon.  In order to determine the next steps, Jeff is wondering whether it would be possible to train other developers so that the work can be distributed among the team.