ouimeaux 0.7.3 always crashes

On a 5K iMac with 10.10.2, via the command line:
$ wemo list
python(5890,0x7fff77f02300) malloc: *** mach_vm_map(size=18446744073599025152) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug

or via the api:
In [1]: from ouimeaux.environment import Environment

In [2]: env = Environment()

In [3]: env.start()
python(5879,0x7fff77f02300) malloc: *** mach_vm_map(size=18446744073599025152) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug

This is a memory allocation error.
While I don't know enough about them to help you resolve the issue, I would suggest you ensure that your python environment is installed properly and up to date. Apple ships a custom version of python so who knows that may be the problem... It is generally recommending to install from the Official Python Source.


fix: patching of otel middleware to work with subclasses

Description

This should allow workarounds like OpenTelemetrySingletonMiddleware from https://github.com/litestar-org/litestar/issues/3056
to work with the patching applied in https://github.com/litestar-org/litestar/pull/3689

@all-contributors add @vikigenius for code


(docs) use with-as for driver initialization

In particular, the current example does not close() the connection causing two (non-critical) warnings appear at termination of the Python script: https://github.com/neo4j/neo4j-python-driver/issues/290
Using with exactly prevents forgotten close() calls.

This issue have been resolved with 4.0 releases.


Add "isShiftPressed", "isAltPressed", "isCtrlPressed" convenience properties to onKeyPressed event

This might not be possible? The terminal seems really reluctant to share keypress information with us, and I can't tell yet if this information is available from jline.
See also:

https://stackoverflow.com/questions/43991528/detect-ctrl-and-alt-keys-at-a-java-console
(Maybe?) https://github.com/kwhat/jnativehook


pins2lts-sym.c is now only compiled once, meaning that compile flags dont have any effect.

Such as flags defined in pins-impl.h.

#111 is affected as well.

Tom has a patch on his branch (a partial revert of the compile-once commit).

Okay, I'll close this issue when Tom's commits are merged.

I'll do a pull request of some of the commits
On Tue, May 30, 2017 at 1:32 PM, Jeroen Meijer<EMAIL_ADDRESS>wrote:

Okay, I'll close this issue when Tom's commits are merged.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/utwente-fmt/ltsmin/issues/112#issuecomment-304851002,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAlcXc8bE53oKRDutk-cPjg3TTue_dDwks5r-_5fgaJpZM4NqKMJ
.

#114 also fixes it and leaves the one-time compilation intact

I think the best solution for now is to do a pull request of @trolando's next branch. And postpone the refactoring of the symtool to v3.1.0.

I ended up cherry-picking a necessary commit from @trolando next branch: 93b5abb5f1b2350e87fcecce48a27021d9181eca.
This issue is solved now.


To add a Json file to save the details of Contact Us form

Description
FEATURE
I feel it would be great if we create a simple Database to track the records of people filling the Contact Us form.
It will enhance the project as it will have a simple DB to save data.
SOLUTION
The above mentioned can be achieved by accessing the contents of the Contact form using JS and writing them in the JSON file (as dictionaries)
I want to work in this issue for Hacktoberfest-2022.
Would be glad if you assign this to me :) @SauravMukherjee44 @Adhetya @LaLiLuLeLoPS @
Screenshots
No response

kindly, give me  this task I will do it very efficiently

@pooranjoyb Go for it!
For support join our discord community: https://discord.com/servers/codein-community-831388874118660156

Thanks a lot @SauravMukherjee44 Da, getting into it asap :)


Pre-Publish Functionality / Salesforce Publish Integration

Summary | Résumé
https://github.com/cds-snc/platform-forms-client/issues/2605
+
https://github.com/cds-snc/platform-forms-client/issues/3313
Test instructions | Instructions pour tester la modification
Create form. Go to settings page, set the new setting.
Unresolved questions / Out of scope | Questions non résolues ou hors sujet
-> Out of scope: Full [User] Lifecycle.
-> Department Identification
Pull Request Checklist
Please complete the following items in the checklist before you request a review:

[ ] Have you completely tested the functionality of change introduced in this PR? Is the PR solving the problem it's meant to solve within the scope of the related issue?
[x] The PR does not introduce any new issues such as failed tests, console warnings or new bugs.
[x] If this PR adds a package have you ensured its licensed correctly and does not add additional security issues?
[x] Is the code clean, readable and maintainable? Is it easy to understand and comprehend.
[x] Does your code have adequate comprehensible comments? Do new functions have docstrings?
[ ] Have you modified the change log and updated any relevant documentation?
[ ] Is there adequate test coverage? Both unit tests and end-to-end tests where applicable?
[ ] If your PR is touching any UI is it accessible? Have you tested it with a screen reader? Have you tested it with automated testing tools such as axe?

Couple of linting errors if you missed them :)
https://github.com/cds-snc/platform-forms-client/pull/3647/commits/5ed3d9a8118e6d420879dcdd541751287d9e6a17#file-app-gcforms-locale-form-administration-form-builder-id-settings-components-responsedelivery-tsx-L145


Rename setting program to schema

Rename setting program to schema
Closes #928

+1
This is obviously correct/ok.
I have to say, the fact that this change required 14 files to be edited was a bit shocking.
Somehow I feel an opportunity to generate a bunch of artifacts from a common spec has been missed. Maybe not, but that was my visceral reaction.

Yes, so the reason for the TS and JS files is because the JS file directly interacts with the DOM/UI of the WebView. For the scripting of WebViews it only directly support JS and not TS, so we use JS to interact with UI and then forward that information to the TS. We also use JS to update the UI based on information sent back to the JS from the TS. So, overall JS is used mostly for DOM and UI interaction and the TS does everything else but they communicate back and forth with each other using the VSCode API. The JS version of that API in this case has a lot less capabilities than the VSCode in the TS and that is why we don't use only JS for this as well.
Does that help or make it more confusing?

@shanedell @mbeckerle FYI there is a mechanism to deprecate configuration settings, which emits a warning, although the deprecated property needs to be supported. See https://code.visualstudio.com/api/references/contribution-points#Configuration-property-schema under "deprecationMessage".
It would look like this in our usage:


fix #53: added default profile image and removed it from .gitignore

Issue: 53
Description:

added a default profile image and removed it from .gitignore

Looks Good . Thanks


mkcloud: nicer cleanup failure handling

:+1:

:+1:

I don't understand why this was done?  Now if it fails, doesn't the user have no idea which device(s) removal failed?


The Cosmos binary use incompatible versions of Swift 5

The Cosmos binary use incompatible versions of Swift 5
Please update it.

Thanks for reporting the issue, @UzumakiAlfredo. I've created a new app in Xcode 10.2 (10E125) and Cosmos worked fine (please see the demo project attached). What kid of issues do you have?
DemoCosmos.zip

You are right. I tested in on a new project & it works.
Seems like that is my project issue...
Sorry.


Add clipboard auto delete timer

It will be awesome if the clipboard can delete history after a given interval.

That should be possible (I think) but would require an async rewrite, which isn’t as easy and straightforward as it might sound. I don’t have the time for that right now, but I’ll leave this issue open.

ic :(

I am sorry to inform you that I deem this feature to be out of scope. After thinking about this more, it does not make sense to restrict that option to wl-clip-persist, as other persons who dont wan't to use this application might want to clear their clipboard after a specified amount of time, too. Therefore, I think it should be its own program, and I'm confident that it would work alongside this application.
It seems like there are already some scripts for what you want: https://knrdl.github.io/posts/wayland-clipboard-clean/
It might have its disadvantages, but it might be good enough.


Error (panicked) at FgbReader::open when reading an EPSG:25832 fgb file

Hi there, thank you for making such a great lib! I'm pretty new to both rust and flatgeobuf, and facing an issue when opening a fgb dataset with CRS EPSG:25832. It complains with:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Geometry("Utf8 error for string in 196..1969: invalid utf-8 sequence of 1 bytes from index 1542\n\twhile verifying table field `wkt` at position 188\n\twhile verifying table field `crs` at position 60\n")'

The dataset is a subset of Bavaria cycling network from https://www.ldbv.bayern.de/produkte/weitere/opendata.html , selected and exported to fgb format with QGIS. I am able to open it in QGIS, but met the above issue when reading it with flatgeobuf lib. For other dataset with EPSG:4326 system, there is no such problem. But I am not sure if the CRS is the reason. Could you help shed some light? Thanks a lot! For some reason, I could not upload the sample dataset here. sorry about that!

Thanks for your interest @tumluliu, this does seem unexpected and I will try to get to the bottom if it. Likely need help from Rust maintainer @pka though.

Hi @tumluliu
I've converted the Shapfile to FGB with GDAL 3.4.0:
ogr2ogr -f FlatGeobuf Radweg_gesamt.fgb  Radweg_gesamt.shp

ogrinfo -al -so Radweg_gesamt.fgb
INFO: Open of `Radweg_gesamt.fgb'
      using driver `FlatGeobuf' successful.

Layer name: Radweg_gesamt
Geometry: Line String
Feature Count: 34974
Extent:<PHONE_NUMBER>00, 5238334.501000) -<PHONE_NUMBER>00, 5604729.181000)
Layer SRS WKT:
PROJCRS["ETRS89 / UTM zone 32N",
    BASEGEOGCRS["ETRS89",
        DATUM["European Terrestrial Reference System 1989",
            ELLIPSOID["GRS 1980",6378137,298.257222101,
                LENGTHUNIT["metre",1]]],
        PRIMEM["Greenwich",0,
            ANGLEUNIT["degree",0.0174532925199433]],
        ID["EPSG",4258]],
    CONVERSION["UTM zone 32N",
        METHOD["Transverse Mercator",
            ID["EPSG",9807]],
        PARAMETER["Latitude of natural origin",0,
            ANGLEUNIT["degree",0.0174532925199433],
            ID["EPSG",8801]],
        PARAMETER["Longitude of natural origin",9,
            ANGLEUNIT["degree",0.0174532925199433],
            ID["EPSG",8802]],
        PARAMETER["Scale factor at natural origin",0.9996,
            SCALEUNIT["unity",1],
            ID["EPSG",8805]],
        PARAMETER["False easting",500000,
            LENGTHUNIT["metre",1],
            ID["EPSG",8806]],
        PARAMETER["False northing",0,
            LENGTHUNIT["metre",1],
            ID["EPSG",8807]]],
    CS[Cartesian,2],
        AXIS["(E)",east,
            ORDER[1],
            LENGTHUNIT["metre",1]],
        AXIS["(N)",north,
            ORDER[2],
            LENGTHUNIT["metre",1]],
    USAGE[
        SCOPE["unknown"],
        AREA["Europe - 6°E to 12°E and ETRS89 by country"],
        BBOX[38.76,6,83.92,12]],
    ID["EPSG",25832]]
Data axis to CRS axis mapping: 1,2
FGN: String (254.0)
FKN: String (20.0)
FTY: String (20.0)
LANDKREIS: String (50.0)
STAND: String (15.0)

The degree symbol in the SRS looks suspicious!
vim Radweg_gesamt.fgb shows:
AREA["Europe - 6Â°E to 12Â°E and ETRS89 by country"]

@bjornharrtell: A non-UTF8 SRS would be against the spec, right?
But the following test passes:
    let mut filein = BufReader::new(File::open("../../test/data/Radweg_gesamt.fgb")?);
    let mut fgb = FgbReader::open(&mut filein)?;
    let count = fgb.select_all()?;
    assert_eq!(count, 34974);

    let feature = fgb.next()?.unwrap();
    assert_eq!(feature.property("FTY"), Some("Radweg".to_string()));

    assert_eq!(fgb.header().crs().unwrap().code(), 25832);
    assert_eq!(
        fgb.header().crs().unwrap().wkt(),
        Some(
            r#"PROJCRS["ETRS89 / UTM zone 32N",BASEGEOGCRS["ETRS89",DATUM["European Terrestrial Reference System 1989",ELLIPSOID["GRS 1980",6378137,298.257222101,LENGTHUNIT["metre",1]]],PRIMEM["Greenwich",0,ANGLEUNIT["degree",0.0174532925199433]],ID["EPSG",4258]],CONVERSION["UTM zone 32N",METHOD["Transverse Mercator",ID["EPSG",9807]],PARAMETER["Latitude of natural origin",0,ANGLEUNIT["degree",0.0174532925199433],ID["EPSG",8801]],PARAMETER["Longitude of natural origin",9,ANGLEUNIT["degree",0.0174532925199433],ID["EPSG",8802]],PARAMETER["Scale factor at natural origin",0.9996,SCALEUNIT["unity",1],ID["EPSG",8805]],PARAMETER["False easting",500000,LENGTHUNIT["metre",1],ID["EPSG",8806]],PARAMETER["False northing",0,LENGTHUNIT["metre",1],ID["EPSG",8807]]],CS[Cartesian,2],AXIS["(E)",east,ORDER[1],LENGTHUNIT["metre",1]],AXIS["(N)",north,ORDER[2],LENGTHUNIT["metre",1]],USAGE[SCOPE["unknown"],AREA["Europe - 6°E to 12°E and ETRS89 by country"],BBOX[38.76,6,83.92,12]],ID["EPSG",25832]]"#
        )
    );

How did you get the panic?

Made a minimal excerpt near Switzerland :switzerland::
ogr2ogr -where "FKN='005910'" -f FlatGeobuf Radweg_ETRS89.fgb Radweg_gesamt.shp

Radweg_ETRS89.zip
Can you reproduce the panic with that file?

Hi @pka , thank you for your digging and the very detailed info! The degree symbol looks like the cause indeed. I will try with the file you created right now

@pka some results from my quick tests:

my program doesn't panic with your test dataset Radweg_ETRS89.fgb
it still panic with the subset I created with qgis for Munich area at the line let mut fgb = FgbReader::open(&mut filein).unwrap();

I also checked my file with your ogrinfo command, and got this:
INFO: Open of `munich_radweg.fgb'
      using driver `FlatGeobuf' successful.

Layer name: munich_radweg
Geometry: Multi Line String
Feature Count: 1268
Extent:<PHONE_NUMBER>00, 5310799.318000) -<PHONE_NUMBER>00, 5350043.924000)
Layer SRS WKT:
PROJCRS["ETRS89 / UTM zone 32N",
    BASEGEOGCRS["ETRS89",
        DATUM["European Terrestrial Reference System 1989",
            ELLIPSOID["GRS 1980",6378137,298.257222101,
                LENGTHUNIT["metre",1]]],
        PRIMEM["Greenwich",0,
            ANGLEUNIT["degree",0.0174532925199433]],
        ID["EPSG",4258]],
    CONVERSION["UTM zone 32N",
        METHOD["Transverse Mercator",
            ID["EPSG",9807]],
        PARAMETER["Latitude of natural origin",0,
            ANGLEUNIT["degree",0.0174532925199433],
            ID["EPSG",8801]],
        PARAMETER["Longitude of natural origin",9,
            ANGLEUNIT["degree",0.0174532925199433],
            ID["EPSG",8802]],
        PARAMETER["Scale factor at natural origin",0.9996,
            SCALEUNIT["unity",1],
            ID["EPSG",8805]],
        PARAMETER["False easting",500000,
            LENGTHUNIT["metre",1],
            ID["EPSG",8806]],
        PARAMETER["False northing",0,
            LENGTHUNIT["metre",1],
            ID["EPSG",8807]]],
    CS[Cartesian,2],
        AXIS["(E)",east,
            ORDER[1],
            LENGTHUNIT["metre",1]],
        AXIS["(N)",north,
            ORDER[2],
            LENGTHUNIT["metre",1]],
    USAGE[
        SCOPE["unknown"],
        AREA["Europe - 6°E to 12°E and ETRS89 by country"],
        BBOX[38.76,6,83.92,12]],
    ID["EPSG",25832]]
Data axis to CRS axis mapping: 1,2
FGN: String (254.0)
FKN: String (20.0)
FTY: String (20.0)
LANDKREIS: String (50.0)
STAND: String (15.0)

I'm trying to convert the subset of Munich from shp to fgb and test it again, but may report the result tomorrow

okay, I got the result as well for 3: it doesn't panic for the dataset converted with ogr2ogr from shp.
I also compared the two fgb data files' ogrinfo, and found there is only one difference which is Geometry type:
❯ diff munich_radweg.fgb.info munich_radweg_ogr.fgb.info
1c1
< INFO: Open of `munich_radweg.fgb'
---
> INFO: Open of `munich_radweg_ogr.fgb'
5c5
< Geometry: Multi Line String
---
> Geometry: Line String

The problematic one generated with QGIS has the Multi Line String geometry type. Could this be the reason?

Still rather confusing, not sure what to make of it.
The crs string encoding is also strange but unsure if related.

Which GDAL version does QGIS use (Help -> About -> About) and which version do you have on the command line (ogrinfo --version)? On which OS are you? If you create the minimal excerpt yourself, is it working, too?

thanks for the further hints! @pka

Which GDAL version does QGIS use (Help -> About -> About)
I'm using qgis 3.20 whose bundled gdal is 3.3.0

which version do you have on the command line (ogrinfo --version)?
my gdal from cmd is 3.4.0

On which OS are you?
qgis is on windows;
gdal cmd and the rust test codes are from ubuntu 20.04

If you create the minimal excerpt yourself, is it working, too?
yes, it worked with no panic

I'm searching if there is any relevant known issue in gdal 3.3.0 when converting to flatgeobuf...

So I think the underlying cause is https://github.com/OSGeo/gdal/issues/5060.

@pka since we have instances of this in the wild and likely other reader implementations isn't that sensitive about it.. can the rust code be persuaded to give up and treat invalid utf-8 as null or empty in this case?

As I understand, the UTF-8 check is done as part of the flatbuffers verification. I can't find a flag to turn this check off, so an option for disabling verification would be needed. I'm hesitating adding this and would prefer telling people how to fix their FGB file. I could return a better message for that.

@pka I think it would at least make sense to be able to turn off verification, it can also be a performance thing for cases where your data is trusted.
Anyway, https://github.com/OSGeo/gdal/issues/5060 is now fixed (hopefully) but it will likely take a long time before it reaches users unfortunately.

With b6c975c03f0b2e51a767ef578a361a5ada6d41ce there is now a method open_unchecked which skips FlatBuffers verfication.


PR to add changes in development to staging

What Does This PR Do?
This PR adds changes in development branch to staging
Description of Task to be Completed
The task will sync of staging with current content in development.
Development branch contains the backend MVP of the entire project
Any Background Context You Want to Provide?
N/A
Screenshot(s)
N/A
What Are The Relevant Pivotaltracker Stories?
N/A

Changes Unknown when pulling 80a8c12ac46347221861286f061ee8aa3eb46fae on development into ** on staging**.


Remove beta remarks

Not sure what has happened there, perhaps some rebase faults, but this should be gone

Thanks @DurgNomis-drol 💥

It's there for quite some time now, you just didn't notice it 😀

Ou, you are right. I just though we fixed it in https://github.com/leikoilja/ha-google-home/pull/143/, but it was a different file 😄


[6.1.x] Update wormhole to fix upgrade issue

I'm going to merge this as the upgrade failures are due to another existing issue.


[meta] update package.json, actions

node 18 is broken due to https://github.com/nodejs/node/issues/42638#issuecomment-1105543393, so i'm going to make it an allowed failure for now.

Unfortunately, continue-on-error shows up this way - as failures on "not the required" checks

update one more time to add a "everything's done" job after the matrix is finished


Redesign Package Search and Profile Pages

Related to #4005 and #4012

@microsoftsam Ready for review

Is this a bug? Should this be 6 hours ago? not "in 6 hours".

It seems that moment.js isn't localizing datetimes properly. It seems that this affects the package details page as well, but I'm not sure why this is happening just yet.

Screenshots please.

Added screenshots.


Cache requests

It should support

[ ] http, https
[ ] redirects
[ ] default path? /tmp, node_modules/.cache, DENO_DIR
[ ] custom path

Should redirects be cached?

Cool plugin. I don't thing it should cache redirects, but what deno is doing is that it cache headers. So... the answer is probably yes they should.
By the way, what's the difference with import-http/rollup from EGOIST?


Dapr sidecar injector does not complete its job

In what area(s)?

/area runtime

/area operator

What version of Dapr?

1.5.1

Expected Behavior
After installing dapr runtime in the kubernetes cluster (EKS) I expect that a new deployment will trigger the sidecar injector to add a dapr sidecar to my pod.
Actual Behavior

However, it seems to do this half-way, it creates a new service (my manifest didn't contain one) with the same name of the deployment and a suffix "-dapr", but my pod keeps as 1/1 Running.
Steps to Reproduce the Problem
I tried three different ways to deploy dapr to my cluster

via cli dapr init -k
via helm with ha
via helm without ha

None of them seem to make a difference. To simplify I settled with helm no-ha and logLevel set to DEBUG and some resource limits and requests as per recommendation, this is the values.yaml file:
global:
  ha:
    enabled: false

dapr_operator:
  resources:
    requests:
      memory: "100Mi"
      cpu: "100m"
    limits:
      memory: "200Mi"
      cpu: "1"
  logLevel: DEBUG

dapr_sidecar_injector:
  resources:
    requests:
      memory: "30Mi"
      cpu: "100m"
    limits:
      memory: "200Mi"
      cpu: "1"
  logLevel: DEBUG

dapr_sentry:
  resources:
    requests:
      memory: "30Mi"
      cpu: "100m"
    limits:
      memory: "200Mi"
      cpu: "1"
  logLevel: DEBUG

dapr_placement:
  resources:
    requests:
      memory: "75Mi"
      cpu: "250m"
    limits:
      memory: "150Mi"
      cpu: "1"
  logLevel: DEBUG

dapr_dashboard:
  resources:
    requests:
      memory: "20Mi"
      cpu: "50m"
    limits:
      memory: "200Mi"
      cpu: "200m"
  logLevel: DEBUG

Deploy dapr to my cluster using this helm command:
helm upgrade --install dapr dapr/dapr   --version=1.5.1   --namespace dapr-system --create-namespace --values values.yaml --wait
Inspect everything is deployed:
$ kubectl get all -n dapr-system
NAME                                         READY   STATUS    RESTARTS   AGE
pod/dapr-dashboard-5b5cf466d9-fhsxs          1/1     Running   0          108s
pod/dapr-operator-54f9fb574c-r26lb           1/1     Running   0          108s
pod/dapr-placement-server-0                  1/1     Running   0          108s
pod/dapr-sentry-7cbd5bcb7b-t9jpm             1/1     Running   0          108s
pod/dapr-sidecar-injector-7f76c88cb8-xbszl   1/1     Running   0          108s

NAME                            TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)              AGE
service/dapr-api                ClusterIP   <IP_ADDRESS>   <none>        80/TCP               108s
service/dapr-dashboard          ClusterIP   <IP_ADDRESS>   <none>        8080/TCP             108s
service/dapr-placement-server   ClusterIP   None            <none>        50005/TCP,8201/TCP   108s
service/dapr-sentry             ClusterIP   <IP_ADDRESS>   <none>        80/TCP               108s
service/dapr-sidecar-injector   ClusterIP   <IP_ADDRESS>   <none>        443/TCP              108s
service/dapr-webhook            ClusterIP   <IP_ADDRESS>   <none>        443/TCP              108s

NAME                                    READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/dapr-dashboard          1/1     1            1           108s
deployment.apps/dapr-operator           1/1     1            1           108s
deployment.apps/dapr-sentry             1/1     1            1           108s
deployment.apps/dapr-sidecar-injector   1/1     1            1           108s

NAME                                               DESIRED   CURRENT   READY   AGE
replicaset.apps/dapr-dashboard-5b5cf466d9          1         1         1       108s
replicaset.apps/dapr-operator-54f9fb574c           1         1         1       108s
replicaset.apps/dapr-sentry-7cbd5bcb7b             1         1         1       108s
replicaset.apps/dapr-sidecar-injector-7f76c88cb8   1         1         1       108s

NAME                                     READY   AGE
statefulset.apps/dapr-placement-server   1/1     108s

NAME                               AGE
configuration.dapr.io/daprsystem   109s

Deploy a very simple test deployment (taken from the docs) with annotations, this is the file node-test.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nodeapp
  namespace: default
  labels:
    app: node
spec:
  replicas: 1
  selector:
    matchLabels:
      app: node
  template:
    metadata:
      labels:
        app: node
      annotations:
        dapr.io/enabled: "true"
        dapr.io/app-id: "nodeapp"
        dapr.io/app-port: "3000"
    spec:
      containers:
      - name: node
        image: dapriosamples/hello-k8s-node
        ports:
        - containerPort: 3000
        imagePullPolicy: Always

Next, deploy the yaml manifest via kubectl cli.
$ kubectl apply -f node-test.yaml
deployment.apps/nodeapp created

Inspect the pod in default namespace, see it gets 1/1 instead of 2/2 or even 1/2 with some errors.
$ kubectl get pods
NAME                       READY   STATUS    RESTARTS   AGE
nodeapp-86977644bf-ltm2v   1/1     Running   0          19s

Inspect the services in default namespace.
$ kubectl get svc
NAME           TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                               AGE
kubernetes     ClusterIP   <IP_ADDRESS>   <none>        443/TCP                               352d
nodeapp-dapr   ClusterIP   None         <none>        80/TCP,50001/TCP,50002/TCP,9090/TCP   73s

There is in fact a new services that is not part of the manifest above.
Inspecting the logs from the sidecar injector, that's all I can see, which is not a lot considering it's set to debug.
$ kubectl logs -l app=dapr-sidecar-injector -n dapr-system
time="2021-12-31T10:23:20.28080175Z" level=info msg="log level set to: DEBUG" instance=dapr-sidecar-injector-7f76c88cb8-xbszl scope=dapr.injector type=log ver=unknown
time="2021-12-31T10:23:20.287660639Z" level=info msg="metrics server started on :9090/" instance=dapr-sidecar-injector-7f76c88cb8-xbszl scope=dapr.metrics type=log ver=unknown
time="2021-12-31T10:23:20.287918191Z" level=info msg="starting Dapr Sidecar Injector -- version 1.5.1 -- commit c6daae8e9b11b3e241a9cb84c33e5aa740d74368" instance=dapr-sidecar-injector-7f76c88cb8-xbszl scope=dapr.injector type=log ver=unknown
time="2021-12-31T10:23:20.294688331Z" level=info msg="Healthz server is listening on :8080" instance=dapr-sidecar-injector-7f76c88cb8-xbszl scope=dapr.injector type=log ver=unknown
time="2021-12-31T10:23:20.342776209Z" level=info msg="Sidecar injector is listening on :4000, patching Dapr-enabled pods" instance=dapr-sidecar-injector-7f76c88cb8-xbszl scope=dapr.injector type=log ver=unknown

Inspecting the logs from the operator, this is what I see:
$ kubectl logs -l app=dapr-operator -n dapr-system
time="2021-12-31T10:23:22.648268454Z" level=info msg="Successfully patched webhook in CRD \"subscriptions.dapr.io\"" instance=dapr-operator-54f9fb574c-r26lb scope=dapr.operator type=log ver=unknown
time="2021-12-31T10:23:23.250022707Z" level=info msg="certificates detected" instance=dapr-operator-54f9fb574c-r26lb scope=dapr.operator type=log ver=unknown
time="2021-12-31T10:23:23.250218933Z" level=info msg="tls certificates loaded successfully" instance=dapr-operator-54f9fb574c-r26lb scope=dapr.operator type=log ver=unknown
time="2021-12-31T10:23:23.251309199Z" level=info msg="Healthz server is listening on :8080" instance=dapr-operator-54f9fb574c-r26lb scope=dapr.operator type=log ver=unknown
time="2021-12-31T10:23:23.251236324Z" level=info msg="starting gRPC server" instance=dapr-operator-54f9fb574c-r26lb scope=dapr.operator.api type=log ver=unknown
I1231 10:23:37.812139       1 leaderelection.go:253] successfully acquired lease dapr-system/webhooks.dapr.io
I1231 10:23:38.213286       1 leaderelection.go:253] successfully acquired lease dapr-system/operator.dapr.io
time="2021-12-31T10:29:28.091732407Z" level=debug msg="no service for deployment found, deployment: default/nodeapp" instance=dapr-operator-54f9fb574c-r26lb scope=dapr.operator.handlers type=log ver=unknown
time="2021-12-31T10:29:28.091873278Z" level=debug msg="enableMetrics: true" instance=dapr-operator-54f9fb574c-r26lb scope=dapr.operator.handlers type=log ver=unknown
time="2021-12-31T10:29:28.115135878Z" level=debug msg="created service: default/nodeapp-dapr" instance=dapr-operator-54f9fb574c-r26lb scope=dapr.operator.handlers type=log ver=unknown

These are the logs from placement server:
$ kubectl logs -l app=dapr-placement-server -n dapr-system
time="2021-12-31T10:23:22.30186249Z" level=debug msg="votes%!(EXTRA []interface {}=[needed 1])" instance=dapr-placement-server-0 scope=dapr.placement.raft type=log ver=1.5.1
time="2021-12-31T10:23:22.301880426Z" level=debug msg="vote granted%!(EXTRA []interface {}=[from dapr-placement-0 term 2 tally 1])" instance=dapr-placement-server-0 scope=dapr.placement.raft type=log ver=1.5.1
time="2021-12-31T10:23:22.301891832Z" level=debug msg="election won%!(EXTRA []interface {}=[tally 1])" instance=dapr-placement-server-0 scope=dapr.placement.raft type=log ver=1.5.1
time="2021-12-31T10:23:22.301905706Z" level=debug msg="entering leader state%!(EXTRA []interface {}=[leader Node at <IP_ADDRESS>:8201 [Leader]])" instance=dapr-placement-server-0 scope=dapr.placement.raft type=log ver=1.5.1
time="2021-12-31T10:23:23.250471283Z" level=info msg="certificates detected" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.5.1
time="2021-12-31T10:23:23.250588085Z" level=info msg="tls certificates loaded successfully" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.5.1
time="2021-12-31T10:23:23.250614509Z" level=info msg="placement service started on port 50005" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.5.1
time="2021-12-31T10:23:23.252695682Z" level=info msg="cluster leadership acquired" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.5.1
time="2021-12-31T10:23:23.251580746Z" level=info msg="Healthz server is listening on :8080" instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.5.1
time="2021-12-31T10:23:23.255296003Z" level=info msg="leader is established." instance=dapr-placement-server-0 scope=dapr.placement type=log ver=1.5.1

The logs from sentry:
$ kubectl logs -l app=dapr-sentry -n dapr-system
time="2021-12-31T10:23:21.755778275Z" level=info msg="Healthz server is listening on :8080" instance=dapr-sentry-7cbd5bcb7b-t9jpm scope=dapr.sentry type=log ver=unknown
time="2021-12-31T10:23:23.685422816Z" level=warning msg="issuer credentials changed. reloading" instance=dapr-sentry-7cbd5bcb7b-t9jpm scope=dapr.sentry type=log ver=unknown
time="2021-12-31T10:23:23.685579499Z" level=info msg="certificate authority loaded" instance=dapr-sentry-7cbd5bcb7b-t9jpm scope=dapr.sentry type=log ver=unknown
time="2021-12-31T10:23:24.685505545Z" level=warning msg="issuer credentials changed. reloading" instance=dapr-sentry-7cbd5bcb7b-t9jpm scope=dapr.sentry type=log ver=unknown
time="2021-12-31T10:23:24.694114225Z" level=info msg="trust root bundle loaded. issuer cert expiry: 2022-12-31 10:23:21 +0000 UTC" instance=dapr-sentry-7cbd5bcb7b-t9jpm scope=dapr.sentry type=log ver=unknown
time="2021-12-31T10:23:24.69571272Z" level=info msg="validator created" instance=dapr-sentry-7cbd5bcb7b-t9jpm scope=dapr.sentry type=log ver=unknown
time="2021-12-31T10:23:24.695752327Z" level=info msg="sentry certificate authority is running, protecting ya'll" instance=dapr-sentry-7cbd5bcb7b-t9jpm scope=dapr.sentry type=log ver=unknown
time="2021-12-31T10:23:25.685641524Z" level=warning msg="issuer credentials changed. reloading" instance=dapr-sentry-7cbd5bcb7b-t9jpm scope=dapr.sentry type=log ver=unknown
time="2021-12-31T10:23:26.68606082Z" level=warning msg="issuer credentials changed. reloading" instance=dapr-sentry-7cbd5bcb7b-t9jpm scope=dapr.sentry type=log ver=unknown
time="2021-12-31T10:23:27.686858708Z" level=warning msg="issuer credentials changed. reloading" instance=dapr-sentry-7cbd5bcb7b-t9jpm scope=dapr.sentry type=log ver=unknown

I can see no errors in any of the logs, could anyone point me out where else to look for some more information ?
Additional information
The cluster I'm using is hosted on Amazon EKS, this is the version:
$ kubectl version --short
Client Version: v1.21.2
Server Version: v1.21.2-eks-0389ca3

I tried all this in a computer running minikube and it works 100% correctly.
In the past I've had issues deploying additions to the cluster due to the network CNI, I'm using Calico from https://docs.projectcalico.org/manifests/calico-vxlan.yaml, I only tweaked the IPv4 pool CIDR to a different range. Most issues were related to the control plane not being able to  reach the pods and services (due to calico networking) so I had to set the hostNetwork to true is several occasions. Could this be the case this time ?
Release Note
RELEASE NOTE: Not sure what to put here, it might be a condition specific of my cluster and not actual bug.

I've looked in the controller manager logs in CloudWatch from EKS control plane and I found this error, but not sure if it has anything to do with the behaviour I'm experiencing
Error syncing deployment" deployment="default/nodeapp" err="Operation cannot be fulfilled on deployments.apps "nodeapp": the object has been modified; please apply your changes to the latest version and try again"
The whole block of logs at the time I deployed the nodeapp is below:
I0109 16:32:37.498147       1 event.go:291] "Event occurred" object="default/nodeapp" kind="Deployment" apiVersion="apps/v1" type="Normal" reason="ScalingReplicaSet" message="Scaled up replica set nodeapp-86977644bf to 1"
I0109 16:32:37.498467       1 replica_set.go:559] "Too few replicas" replicaSet="default/nodeapp-86977644bf" need=1 creating=1
I0109 16:32:37.515814       1 deployment_controller.go:490] "Error syncing deployment" deployment="default/nodeapp" err="Operation cannot be fulfilled on deployments.apps \"nodeapp\": the object has been modified; please apply your changes to the latest version and try again"
I0109 16:32:37.544184       1 event.go:291] "Event occurred" object="default/nodeapp-86977644bf" kind="ReplicaSet" apiVersion="apps/v1" type="Normal" reason="SuccessfulCreate" message="Created pod: nodeapp-86977644bf-g7kdw"

I also found in kube-apiserver-audit logs inside CloudWatch from EKS control plane as well, something that gives a hint that the mutation is not happening.
"webhook\":\"sidecar-injector.dapr.io\",\"mutated\":false

"annotations": {
        "authorization.k8s.io/decision": "allow",
        "authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding \"system:controller:replicaset-controller\" of ClusterRole \"system:controller:replicaset-controller\" to ServiceAccount \"replicaset-controller/kube-system\"",
        "mutation.webhook.admission.k8s.io/round_0_index_2": "{\"configuration\":\"dapr-sidecar-injector\",\"webhook\":\"sidecar-injector.dapr.io\",\"mutated\":false}",
        "mutation.webhook.admission.k8s.io/round_0_index_3": "{\"configuration\":\"pod-identity-webhook\",\"webhook\":\"iam-for-pods.amazonaws.com\",\"mutated\":false}",
        "mutation.webhook.admission.k8s.io/round_0_index_4": "{\"configuration\":\"vpc-resource-mutating-webhook\",\"webhook\":\"mpod.vpc.k8s.aws\",\"mutated\":false}",
        "podsecuritypolicy.policy.k8s.io/admit-policy": "eks.privileged",
        "podsecuritypolicy.policy.k8s.io/validate-policy": "eks.privileged"
    }

The whole log document  is here:
{
    "kind": "Event",
    "apiVersion": "audit.k8s.io/v1",
    "level": "RequestResponse",
    "auditID": "eedaf53c-a3d5-4a20-9cd9-9b28a2c96caf",
    "stage": "ResponseComplete",
    "requestURI": "/api/v1/namespaces/default/pods",
    "verb": "create",
    "user": {
        "username": "system:serviceaccount:kube-system:replicaset-controller",
        "uid": "08b3224e-93e3-402b-99ae-317c89c0157b",
        "groups": [
            "system:serviceaccounts",
            "system:serviceaccounts:kube-system",
            "system:authenticated"
        ]
    },
    "sourceIPs": [
        "<IP_ADDRESS>"
    ],
    "userAgent": "kube-controller-manager/v1.21.2 (linux/amd64) kubernetes/8a4e27b/system:serviceaccount:kube-system:replicaset-controller",
    "objectRef": {
        "resource": "pods",
        "namespace": "default",
        "apiVersion": "v1"
    },
    "responseStatus": {
        "metadata": {},
        "code": 201
    },
    "requestObject": {
        "kind": "Pod",
        "apiVersion": "v1",
        "metadata": {
            "generateName": "nodeapp-86977644bf-",
            "creationTimestamp": null,
            "labels": {
                "app": "node",
                "pod-template-hash": "86977644bf"
            },
            "annotations": {
                "dapr.io/app-id": "nodeapp",
                "dapr.io/app-port": "3000",
                "dapr.io/enabled": "true"
            },
            "ownerReferences": [
                {
                    "apiVersion": "apps/v1",
                    "kind": "ReplicaSet",
                    "name": "nodeapp-86977644bf",
                    "uid": "5b9f9a98-a432-4e22-80cc-3c14f0d82981",
                    "controller": true,
                    "blockOwnerDeletion": true
                }
            ]
        },
        "spec": {
            "containers": [
                {
                    "name": "node",
                    "image": "dapriosamples/hello-k8s-node",
                    "ports": [
                        {
                            "containerPort": 3000,
                            "protocol": "TCP"
                        }
                    ],
                    "resources": {},
                    "terminationMessagePath": "/dev/termination-log",
                    "terminationMessagePolicy": "File",
                    "imagePullPolicy": "Always"
                }
            ],
            "restartPolicy": "Always",
            "terminationGracePeriodSeconds": 30,
            "dnsPolicy": "ClusterFirst",
            "securityContext": {},
            "schedulerName": "default-scheduler",
            "enableServiceLinks": true
        },
        "status": {}
    },
    "responseObject": {
        "kind": "Pod",
        "apiVersion": "v1",
        "metadata": {
            "name": "nodeapp-86977644bf-g7kdw",
            "generateName": "nodeapp-86977644bf-",
            "namespace": "default",
            "uid": "d522ec30-2bb3-437a-9bfa-86f497c2b165",
            "resourceVersion": "104848856",
            "creationTimestamp": "2022-01-09T16:32:37Z",
            "labels": {
                "app": "node",
                "pod-template-hash": "86977644bf"
            },
            "annotations": {
                "dapr.io/app-id": "nodeapp",
                "dapr.io/app-port": "3000",
                "dapr.io/enabled": "true",
                "kubernetes.io/psp": "eks.privileged"
            },
            "ownerReferences": [
                {
                    "apiVersion": "apps/v1",
                    "kind": "ReplicaSet",
                    "name": "nodeapp-86977644bf",
                    "uid": "5b9f9a98-a432-4e22-80cc-3c14f0d82981",
                    "controller": true,
                    "blockOwnerDeletion": true
                }
            ],
            "managedFields": [
                {
                    "manager": "kube-controller-manager",
                    "operation": "Update",
                    "apiVersion": "v1",
                    "time": "2022-01-09T16:32:37Z",
                    "fieldsType": "FieldsV1",
                    "fieldsV1": {
                        "f:metadata": {
                            "f:annotations": {
                                ".": {},
                                "f:dapr.io/app-id": {},
                                "f:dapr.io/app-port": {},
                                "f:dapr.io/enabled": {}
                            },
                            "f:generateName": {},
                            "f:labels": {
                                ".": {},
                                "f:app": {},
                                "f:pod-template-hash": {}
                            },
                            "f:ownerReferences": {
                                ".": {},
                                "k:{\"uid\":\"5b9f9a98-a432-4e22-80cc-3c14f0d82981\"}": {
                                    ".": {},
                                    "f:apiVersion": {},
                                    "f:blockOwnerDeletion": {},
                                    "f:controller": {},
                                    "f:kind": {},
                                    "f:name": {},
                                    "f:uid": {}
                                }
                            }
                        },
                        "f:spec": {
                            "f:containers": {
                                "k:{\"name\":\"node\"}": {
                                    ".": {},
                                    "f:image": {},
                                    "f:imagePullPolicy": {},
                                    "f:name": {},
                                    "f:ports": {
                                        ".": {},
                                        "k:{\"containerPort\":3000,\"protocol\":\"TCP\"}": {
                                            ".": {},
                                            "f:containerPort": {},
                                            "f:protocol": {}
                                        }
                                    },
                                    "f:resources": {},
                                    "f:terminationMessagePath": {},
                                    "f:terminationMessagePolicy": {}
                                }
                            },
                            "f:dnsPolicy": {},
                            "f:enableServiceLinks": {},
                            "f:restartPolicy": {},
                            "f:schedulerName": {},
                            "f:securityContext": {},
                            "f:terminationGracePeriodSeconds": {}
                        }
                    }
                }
            ]
        },
        "spec": {
            "volumes": [
                {
                    "name": "kube-api-access-njms7",
                    "projected": {
                        "sources": [
                            {
                                "serviceAccountToken": {
                                    "expirationSeconds": 3607,
                                    "path": "token"
                                }
                            },
                            {
                                "configMap": {
                                    "name": "kube-root-ca.crt",
                                    "items": [
                                        {
                                            "key": "ca.crt",
                                            "path": "ca.crt"
                                        }
                                    ]
                                }
                            },
                            {
                                "downwardAPI": {
                                    "items": [
                                        {
                                            "path": "namespace",
                                            "fieldRef": {
                                                "apiVersion": "v1",
                                                "fieldPath": "metadata.namespace"
                                            }
                                        }
                                    ]
                                }
                            }
                        ],
                        "defaultMode": 420
                    }
                }
            ],
            "containers": [
                {
                    "name": "node",
                    "image": "dapriosamples/hello-k8s-node",
                    "ports": [
                        {
                            "containerPort": 3000,
                            "protocol": "TCP"
                        }
                    ],
                    "resources": {},
                    "volumeMounts": [
                        {
                            "name": "kube-api-access-njms7",
                            "readOnly": true,
                            "mountPath": "/var/run/secrets/kubernetes.io/serviceaccount"
                        }
                    ],
                    "terminationMessagePath": "/dev/termination-log",
                    "terminationMessagePolicy": "File",
                    "imagePullPolicy": "Always"
                }
            ],
            "restartPolicy": "Always",
            "terminationGracePeriodSeconds": 30,
            "dnsPolicy": "ClusterFirst",
            "serviceAccountName": "default",
            "serviceAccount": "default",
            "securityContext": {},
            "schedulerName": "default-scheduler",
            "tolerations": [
                {
                    "key": "node.kubernetes.io/not-ready",
                    "operator": "Exists",
                    "effect": "NoExecute",
                    "tolerationSeconds": 300
                },
                {
                    "key": "node.kubernetes.io/unreachable",
                    "operator": "Exists",
                    "effect": "NoExecute",
                    "tolerationSeconds": 300
                }
            ],
            "priority": 0,
            "enableServiceLinks": true,
            "preemptionPolicy": "PreemptLowerPriority"
        },
        "status": {
            "phase": "Pending",
            "qosClass": "BestEffort"
        }
    },
    "requestReceivedTimestamp": "2022-01-09T16:32:37.515715Z",
    "stageTimestamp": "2022-01-09T16:32:37.543843Z",
    "annotations": {
        "authorization.k8s.io/decision": "allow",
        "authorization.k8s.io/reason": "RBAC: allowed by ClusterRoleBinding \"system:controller:replicaset-controller\" of ClusterRole \"system:controller:replicaset-controller\" to ServiceAccount \"replicaset-controller/kube-system\"",
        "mutation.webhook.admission.k8s.io/round_0_index_2": "{\"configuration\":\"dapr-sidecar-injector\",\"webhook\":\"sidecar-injector.dapr.io\",\"mutated\":false}",
        "mutation.webhook.admission.k8s.io/round_0_index_3": "{\"configuration\":\"pod-identity-webhook\",\"webhook\":\"iam-for-pods.amazonaws.com\",\"mutated\":false}",
        "mutation.webhook.admission.k8s.io/round_0_index_4": "{\"configuration\":\"vpc-resource-mutating-webhook\",\"webhook\":\"mpod.vpc.k8s.aws\",\"mutated\":false}",
        "podsecuritypolicy.policy.k8s.io/admit-policy": "eks.privileged",
        "podsecuritypolicy.policy.k8s.io/validate-policy": "eks.privileged"
    }
}

If you don't see any logs from the sidecar injector, it means its either not called or the Kubernetes API server is failing to call it. Are there any more EKS control plane logs you can pull?

Also, I found this: https://github.com/aws/amazon-eks-pod-identity-webhook/issues/83.
It might be a cluster level issue. Can you please spin up a different cluster and see if this reproduced?

@yaron2 Thanks for the pointer, I had a read about that, it seems related. I kept digging in EKS Control Plane logs, this time the API Server logs (not audit) and I found these two lines:
W0110 09:22:20.873262       1 dispatcher.go:170] Failed calling webhook, failing open sidecar-injector.dapr.io: failed calling webhook "sidecar-injector.dapr.io": Post "https://dapr-sidecar-injector.dapr-system.svc:443/mutate?timeout=10s": Address is not allowed
--
E0110 09:22:20.873303       1 dispatcher.go:171] failed calling webhook "sidecar-injector.dapr.io": Post "https://dapr-sidecar-injector.dapr-system.svc:443/mutate?timeout=10s": Address is not allowed

It seems like somehow service url is not fully qualified

@yaron2 The hostNetwork setting did the trick for me, I manually updated the chart by adding an extra value to the dapper injector deployment, I tested it in my cluster with the setting set to true and it worked successfully.
Is this a change you guys would like to accept from me ? I'm preparing a pull request with this particular solution in place.
There are other ideas explained very well in this article: https://medium.com/@denisstortisilva/kubernetes-eks-calico-and-custom-admission-webhooks-a2956b49bd0d. It's very well described what the problem is and a few different solutions where using the hostNetwork is one of them and it worked for my scenario.

@yaron2 The hostNetwork setting did the trick for me, I manually updated the chart by adding an extra value to the dapper injector deployment, I tested it in my cluster with the setting set to true and it worked successfully.
Is this a change you guys would like to accept from me ? I'm preparing a pull request with this particular solution in place.
There are other ideas explained very well in this article: https://medium.com/@denisstortisilva/kubernetes-eks-calico-and-custom-admission-webhooks-a2956b49bd0d. It's very well described what the problem is and a few different solutions where using the hostNetwork is one of them and it worked for my scenario.

So the issue was that you're using Calico as the CNI plugin for your EKS cluster? Yeah a PR would be welcome. It needs to be a well understood, and documented Helm setting.

Yes, exactly, so it will help anyone with that setup.
PR is on the way https://github.com/dapr/dapr/pull/4120
I'll be happy to expand in the docs repo


[kedro-docker] Layers size optimization

Description
Follow-up of #79
This PR brings a few optimizaions for image layers:

added --no-cache to the pip install so it clears downloaded packages after being installed
optimized user code layers: current templates in kedro-docker create 3 layers with user code for every build (due to separate copy->chown->chmod stages), but it's not necessary, as we can specify owner of the files at COPY and preserve access mode
split to 2-stage build: one with runtime-environment (a base image with no user code that can be cached and reused across projects) and second with project code only
default base image changed to slim flavor and bumped python version to a modern 3.9
redundant Spark and Hadoop libs removed from the Dockerfile.spark template + tests to cover this modification -> they are not necessary, because after installing pyspark via pip you have all the libraries downloaded already

Development notes
Tested locally by building the docker image and examining the filesystem. Layers optimization reduce both build time and image size. Multi-stage build doesn't bring any extra benefits, but makes it easier to deploy Kedro in cloud environments like Azure.
Checklist

[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[x] Added a description of this change in the relevant RELEASE.md file
[x] Added tests to cover my changes

@noklam This is a continuation of #79. I've measured optimizations as you asked, using the official starters.
Images built using current kedro-docker 0.3.0:

pandas-iris (using kedro docker build): 1.58GB
pyspark-iris (using kedro docker build --with-spark): 3.83GB

Same images built via kedro-docker code from this PR:

pandas-iris: 1.44GB - reduced by 8.8%
pyspark-iris: 1.91GB - reduced by 50.1%

I think that those changes bring a real value and some best practices that are currently missing in the Dockerfile generated by kedro-docker.
Plus, @szczeles went an extra mile to fix the tests 👏🏻

It's great that the slim image passes the e2e tests, did you manage to do any manual testing with the slim base image?

Thanks! I did, on production we run slim images only. I've checked also that there is no issue running pip install torch tensorflow xgboost on the slim image (3.9) - it looks that all major ML frameworks publish binaries already.

Excellent, that's good to hear. It's something we have to keep in mind if we start getting reports of things not working as they should, but I think slim is the right way to go.

Thanks for your reviews @jmholzer and @noklam, do you think it would be possible to merge this to master branch and release new plugin version?

Thanks for your reviews @jmholzer and @noklam, do you think it would be possible to merge this to master branch and release new plugin version?

Yes 🙂 on it now.

FROM runtime-environment
# copy the whole project except what is in .dockerignore
ARG KEDRO_UID=999
ARG KEDRO_GID=0
COPY --chown=${KEDRO_UID}:${KEDRO_GID} . .

I suspect this change is causing bug when UID and GID is specifcied.


CAMEL-8538 Add inOut support to the camel-rabbitmq component

This adds several major features to the camel-rabbitmq component that the camel-jms component has. InOut support that spins up a temporary reply queue that supports timeouts. Serializing / de-serializing objects that implement Serializable. Transfers exceptions that occur in consumers.
Added the following URI options (same usage as camel-jms)
transferException
requestTimeout
requestTimeoutCheckerInterval

Is this PR ready to go? And is there any documentation updates needed?

Hi Claus,
We migrated all our customers from activemq to this about a month ago and have not had any issues.
Docs do need to be updated to include the new URI options (listed above). The usage is identical to activemq so it should be easy to copy paste.
How do you want to handle that?  Do you usually edit them pre-merge or post?

The docs are usually edited after commit.

@brreitme are you able to rebase this PR with latest code from master branch as the camel-rabbitmq source code has changed since and there is too many conflicts for me to resolve.

@davsclaus do you need it rebased and squashed into a single commit or is it ok now? I was able to fetch and merge from camel/master without any conflicts.

@davsclaus Sorry about that. I rebased and squashed everything into a single commit.

Thanks @brreitme  - when we pull in PRs we do a pull and then a --rebase afterwards so the git tree is flatten and the pull is applied on top. And therefore we can hit merge errors.

Thanks the code has been pushed.
Do you mind working on fixing the code formatting issues. You can get a report by running
 davsclaus:~/workspace/camel/components/camel-rabbitmq (master)/$ mvn compile -Psourcecheck

Then open a new PR with those fixes.

Thanks @davsclaus. I should be able to fix the formatting issues today. I'm waiting on my ICLA but plan on editing the docs


Add hello world problem

Closes https://github.com/exercism/todo/issues/42.

This build failed because at the time Travis was testing with PHP 5.5. If someone with privileges can re-run the build then I think it should pass, and is good to be merged.


fix version number

Coverage remained the same at 65.456% when pulling 7b3f6197e5f7c31a97c96c2e62e7f1acabc7a55b on fix-version into 247ed6f295300f224832ba968ddc857948fd9b7e on master.


NDT map generation

Hello,
I have a question about how to generate NDT maps. Right now, I have a batch of .pcd files and ground truth poses. All the pcd files are collecting by LiDAR. I wonder how to generate the NDT maps. Could I just stitch all the points from pcd files together, which means use the poses as offsets and combine all the points together?
Thank you very much.

你好，
我对如何生成NDT地图有疑问。现在，我有一批.pcd文件和真实情况。LiDAR正在收集所有pcd文件。我想知道如何生成NDT地图。我可以将pcd文件中的所有点缝合在一起，这意味着将姿势用作偏移并将所有点组合在一起吗？
非常感谢你。
Hello, how do you build a .bag into multiple .pcd


Scripts cannot have data- attributes

🐛 Bug Report
For use with Plausible analytics a script needs to be added to the website, however Plausible uses data- attributes. These do not pass the validation of the scripts section.
Have you read the Contributing Guidelines on issues?
Yes.
To Reproduce
(Write your steps here:)

Create a script in the scripts section that uses data-domain property

Expected behavior

data-domain property would pass validation and be added to the script.
Actual Behavior

Crashes on Error: "scripts[0]" does not match any of the allowed types
Your Environment

Docusaurus version used: 2.0.0-alpha.62
Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0): node v12.18.3
Operating system and version (desktop or mobile): Windows 10

Reproducible Demo
(Paste the link to an example repo, including a siteConfig.js, and exact instructions to reproduce the issue.)

Show config

module.exports = {
  title: "Commitsar",
  tagline: "Conventional commit compliance made easy",
  url: "https://commitsar.tech",
  baseUrl: "/",
  favicon: "img/favicon.ico",
  organizationName: "aevea", // Usually your GitHub org/user name.
  projectName: "commitsar", // Usually your repo name.
  themeConfig: {
    navbar: {
      title: "Commitsar",
      logo: {
        alt: "My Site Logo",
        src: "img/logo.svg",
      },
      items: [
        {
          to: "docs/",
          activeBasePath: "docs",
          label: "Docs",
          position: "left",
        },
        { to: "blog", label: "Blog", position: "left" },
        {
          href: "https://github.com/facebook/docusaurus",
          label: "GitHub",
          position: "right",
        },
      ],
    },
    footer: {
      style: "dark",
      links: [
        {
          title: "More",
          items: [
            {
              label: "Blog",
              to: "blog",
            },
            {
              label: "GitHub",
              href: "https://github.com/aevea/commitsar",
            },
          ],
        },
      ],
      copyright: `Copyright © ${
        new Date().getFullYear()
      } My Project, Inc. Built with Docusaurus.`,
    },
    algolia: {
      apiKey: process.env.ALGOLIA_KEY || "none",
      indexName: "commitsar",
    },
  },
  presets: [
    [
      "@docusaurus/preset-classic",
      {
        docs: {
          sidebarPath: require.resolve("./sidebars.js"),
          // Please change this to your repo.
          editUrl: "https://github.com/aevea/commitsar/edit/master/www/",
        },
        blog: {
          showReadingTime: true,
          // Please change this to your repo.
          editUrl: "https://github.com/aevea/commitsar/edit/master/www/",
        },
        theme: {
          customCss: require.resolve("./src/css/custom.css"),
        },
      },
    ],
  ],
  scripts: [
    {
      src: "https://plausible.io/js/plausible.js",
      async: true,
      defer: true,
      // "data-domain": "commitsar.tech",
    },
  ],
};

Thanks, will be fixed in https://github.com/facebook/docusaurus/pull/3385


[FLINK-26440] CompactorOperatorStateHandler can not work with unaligned checkpoint.

What is the purpose of the change
CompactorOperatorStateHandler can not work with unaligned checkpoint currently. We should fix this or add a warning in the document. This PR is trying to fix this issue.
Brief change log

Refactor CompactorOperatorStateHandler to support unaligned checkpoint, i.e., to make it able to accept more than or less than 1 summary and the committable belonging to it during a checkpoint.
This PR is based on FLINK-26403, so is containing the changes of this PR. They are not included in the scope of this PR.

Verifying this change
This change added tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

Thanks @pltbkd for the updates! I do not have other comments except for the above one


Folder

Folder Chooser can be turned into a handy File Picker  by setting isShowingFiles() from the Builder.

As mentioned in the issue, it's not intended for that.


docs: Reviewed and modified the new contents + modified the icons in the sidebar

14-Mar-24: @avishnu @Abhinandan-Purkait @niladrih @datacore-gthomas
We have modified & the reviewed the 1st two sections (Introduction to OpenEBS & Concepts).
Kindly verify and share your feedback, if any by EOB 15-Mar-24. :-)

Looks good. I personally think we should not repeat the word "Guide" everywhere in the tree view (if possible).

We have modified & the reviewed the Troubleshooting section.
Kindly verify and share your feedback.

19-Mar-24: @avishnu @Abhinandan-Purkait @niladrih @datacore-gthomas
We have modified & the reviewed the below sections:

QuickStart Guide
- QuickStart
- Installation
- Deploy a Test Application
FAQs
Community
Commercial Support

Note: Deploy a Test Application section contains the Mayastor Configuring docs as well. We need the contents for Deploy a Test Application & Configuration of Local Engine.
Based on our review, we would suggest we can have a separate page for Deployment and a separate page for Configuration.
Kindly verify and share your feedback.

20-Mar-24: @avishnu @Abhinandan-Purkait @niladrih @datacore-gthomas
We have modified & the reviewed the below sections:

Local Engine Prerequisites
Local Engine Installation

Kindly verify and share your feedback.


Read only select-one question is still select able on Enketo UI

The select-one choices are select able though the answer is not populated in the submitted xml file.
On the ODK app it shows the choices as disabled which gives some visual clue to the user that the answers are read-only.
Is the Enketo UI being select able intentional?

Thanks. Not intentional.  this is a long-standing bug that somehow never got turned into a github issue. I consider it a very low priority, but it should be fixed.

This issue is affecting us. We would be happy to try and fix it and put together a PR, but we haven't done any development on Enketo before. @MartijnR could you point us in the right direction?

PR would be welcome! This is where the fix would go: https://github.com/enketo/enketo-core/blob/master/src/widget/select-desktop/selectpicker.js (and it's sibling sass file).

Sorry I removed the link, because I mistakenly thought this referred to select question with the minimal appearance. Not sure if that's the case.
Wherever it occurs, the best solution is probably to add the disabled property to the <input> elements.

The notewidget is probably the place to do this: https://github.com/enketo/enketo-core/blob/master/src/widget/note/notewidget.js

Actually you'd think that built-in HTML behaviour would make inputs with a readonly attribute not-selectable. If that attribute is missing, the solution would be to add this in enketo-xslt.

Ok, last msg for today :). It might be fixable by changing this line to:
$el.find( '[readonly]' ).addClass( 'ignore' ).prop('disabled', true);


php standalone samples

PTAL

Codecov Report

Merging #2151 into master will increase coverage by 0.04%.
The diff coverage is 97.14%.

@@             Coverage Diff             @@
##             master   #2151      +/-   ##
===========================================
+ Coverage     86.85%   86.9%   +0.04%
- Complexity     5086    5107      +21
===========================================
  Files           453     455       +2
  Lines         20160   20251      +91
  Branches       2151    2158       +7
===========================================
+ Hits          17510   17599      +89
- Misses         1894    1898       +4
+ Partials        756     754       -2

Impacted Files
Coverage Δ
Complexity Δ

...oogle/api/codegen/gapic/GapicGeneratorFactory.java
91.29% <100%> (+0.26%)
11 <0> (+1)
:arrow_up:

...e/api/codegen/transformer/php/PhpSurfaceNamer.java
92.4% <100%> (+0.09%)
42 <1> (+1)
:arrow_up:

...en/transformer/php/PhpGapicSurfaceTransformer.java
93.12% <100%> (-1.69%)
43 <1> (-2)

...en/transformer/php/PhpGapicSamplesTransformer.java
100% <100%> (ø)
8 <8> (?)

.../com/google/api/codegen/viewmodel/CallingForm.java
100% <100%> (ø)
1 <0> (ø)
:arrow_down:

...odegen/transformer/php/PhpMethodViewGenerator.java
91.66% <91.66%> (ø)
9 <9> (?)

... and 1 more

Continue to review full report at Codecov.

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


Music Assistant Crashing After Youtube Music Cookie Setup

What version of Music Assistant has the issue?
2.3.3
What version of the Home Assistant Integration have you got installed?
2024.11.3
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
Music Assistant runs for less than 2 minutes before crashing. The issue seems to have started after youtube switched to cookie authorization. Removal of MA server and data and resintallation did not fix the issue, it started crashing again as soon as I entered the cookie info back in.
How to reproduce
Add Youtube music cookie. Wait for info from youtube music to load on the album/artists/etc tabs, soon after addon will crash.
Music Providers
Youtube Music
Player Providers
Didnt make it far enough to select a player
Full log output
d5369777_music_assistant_2024-11-26T05-07-27.796Z.log
Additional information
Supervisor 2024.11.4
Cookie obtained from Brave browser
What version of Home Assistant Core are your running
2024.11.3
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Linux

@MarvinSchenkel

Im attempting to try the cookie from other browsers, but Im getting a lot of errors that say I dont have a youtube premium account. I do, and I did get the cookie from the playlist page after logging in, just like the tutorial.

Please confirm that if you do nothing with YouTube then MA works without problem. If that is the case then confirm that with the YouTube provider added not configured that MA works without problem.
if the above is true then restart MA and then download and attach the log. Then attempt to authenticate YT. Download the log each time you do something until the server crashes. When that occurs go to the HA supervisor logs and shows what it says there.

It randomly stopped crashing and now runs with youtube music configured, but all of the youtube music content is greyed out and unselectable.

I also continue to get an error saying that I dont have youtube premium

Then this is a duplicate of https://github.com/music-assistant/hass-music-assistant/issues/3138 So please continue over there


Directive Information Entity

Please see discussion on the OBI tracker for the IAO term Directive Information Entity: https://github.com/obi-ontology/obi/issues/988

Update: in the last OBI call, we agreed to and would like to suggest the following definition:
"an information content entity that can be concretized as a realizable entity or a part thereof"
per discussion in
obi-ontology/obi/issues/988

Maybe this could be encoded in OWL and the human definition could be more human-friendly?

Current logical axioms of 'Directive Information Entity' is
'is about' some 'realizable entity'
Based on Chris suggestion, we can update it as
'is concretized as' some ('realizable entity' or 'part of' some 'realizable entity') (according proposed textual entity)
or simplify it as:
'is concretized as' some 'realizable entity'
Any thought?
@cmungall Any suggestion on the textual definition? Thanks!
The current definition is "An information content entity whose concretizations indicate to their bearer how to realize them in a process."
Proposed definition is "an information content entity that can be concretized as a realizable entity or a part thereof".

Maybe this could be encoded in OWL and the human definition could be more human-friendly?

Bringing this back for objective specification and other directive information entities needed over in the UN SDGIO.
The textual definitions really must be more human-readable.  For example, the first part of the objective specification definition is fine:
A directive information entity that describes an intended process endpoint.

But the second part isn't:
When part of a plan specification the concretization is realized in a planned process in which the bearer tries to effect the world so that the process endpoint is achieved.

The grammar doesn't even make sense as far as I can tell.
Redefinitions
Directive information entity

@cmungall Any suggestion on the textual definition? Thanks!
The current definition is "An information content entity whose concretizations indicate to their bearer how to realize them in a process."
Proposed definition is "an information content entity that can be concretized as a realizable entity or a part thereof".

An information content entity which, when understood by an agent, indicates how a process should unfold.

I think that's general enough and accurate enough to work for both objective and plan specifications. A more technical def can be placed in another AP if needed.
Objective specification

I think, it would help to link to here with a 'term tracker item' AP on the respective classes, to help users understand the current definitions better?


Add tests and clean things up

Fixes #
Changes made in this Pull Request:

PR Checklist

[ ] Tests?
[ ] Docs?
[ ] CHANGELOG updated?
[ ] Issue raised/referenced?

Codecov Report

Merging #100 (ab07884) into main (dab0350) will increase coverage by 1.54%.
Report is 1 commits behind head on main.
The diff coverage is 100.00%.

Additional details and impacted files


Allow for getting schemas from nested structures

This PR handles the case where a class has attributes which are also classes. These can also be part of another data type, such as a list of that new class, for example:
from fastcore.utils import *

class Turn:
    "Turn between two speakers"
    def __init__(
        self,
        speaker_a:str, # First speaker to speak
        message_a:str, # First speaker's message
        speaker_b:str,  # Second speaker to speak
        message_b:str, # Second speaker's message
    ): store_attr()

class Conversation:
    "A conversation between two speakers"
    def __init__(
        self,
        turns:list[Turn], # Turns of the conversation
    ): store_attr()

    __repr__ = basic_repr(['turns'])

get_schema(Conversation)

This now outputs the following schema:
{'name': 'Conversation',
 'description': 'A conversation between two speakers',
 'input_schema': {'type': 'object',
  'properties': {'turns': {'type': 'array',
    'description': 'Turns of the conversation',
    'items': {'$ref': '#/$defs/Turn'}}},
  'title': 'Conversation',
  'required': ['turns'],
  '$defs': {'Turn': {'type': 'object',
    'properties': {'speaker_a': {'type': 'string',
      'description': 'First speaker to speak'},
     'message_a': {'type': 'string', 'description': "First speaker's message"},
     'speaker_b': {'type': 'string', 'description': 'Second speaker to speak'},
     'message_b': {'type': 'string',
      'description': "Second speaker's message"}},
    'title': 'Turn',
    'required': ['speaker_a', 'message_a', 'speaker_b', 'message_b']}}}}

This is useful for structured outputs from APIs like Anthropic's Claude. Using this locally via Claudette, I can do something like this:
from claudette import *

model = models[-1] # haiku 3
sp = "You will help create quotes."
cli = Client(model)
prompt = "Generate a conversation between Albert Einstein and Oppenheimer"
convo = cli.structured(prompt, temp=1, tools=Conversation)[0]
convo

Outputs:
__main__.Conversation(turns=[{'speaker_a': 'Albert Einstein', 'message_a': "Hello, Robert. I've been thinking a lot about the implications of the work you and your team have been doing on the atomic bomb.", 'speaker_b': 'J. Robert Oppenheimer', 'message_b': "Ah, yes, Einstein. The power we've unlocked is both wondrous and terrifying. I worry about how it will be used."}, {'speaker_a': 'Albert Einstein', 'message_a': 'That is exactly my concern. The sheer destructive potential of these weapons is beyond anything humanity has ever seen. We must find a way to ensure they are never used.', 'speaker_b': 'J. Robert Oppenheimer', 'message_b': "I share your worries deeply. The responsibility we bear is immense. As the 'father of the atomic bomb', I feel a great moral burden."}, {'speaker_a': 'Albert Einstein', 'message_a': 'You are not alone in that burden, my friend. We must work together to promote international cooperation and find peaceful applications for this technology. The future of humanity depends on it.', 'speaker_b': 'J. Robert Oppenheimer', 'message_b': 'You are absolutely right. I will dedicate myself to ensuring these weapons are never used, and that the incredible scientific breakthroughs are channeled toward the betterment of mankind. We owe it to the world to get this right.'}])

Previously, this was not possible with Claudette's tool calling since it would not be able to see the structure of the Turn class to know which fields to use.
I've made sure to follow the JSON schema spec that Claude, OpenAI, and others adhere to for these types of schemas. I also verified that it is similar to ones generated by the instructor library. It handles lists, sets, tuples, and even dictionaries.
I also made a change to the _types function to handle custom classes.

Nice! :D Can you please #| hide the test cells you added since AFAICT they're not designed to appear in the docs. Also, could you try to have tests for each of the non-trivial functions placed immediately after the function?


add translations to tree map tooltips, missing translation on share.

this looks good to go once we update translations


Modify ... Build the Docker image for the solver service

Description of the modifications
I followed the instructions on build solver container in these tutorial https://dyna.docs.pyansys.com/version/stable/getting-started/index.html#run-pydyna-server-in-a-docker-container.
But in the step building docker image with the docker build -t dyna_solver_v04 .
It get error messenger:
process "/bin/sh -c yum -y install openssh-clients openssh-server bind-utils sudo python3 unzip &>/dev/null && yum clean all" did not complete successfully: exit code: 1
Does anyone meet these problems?
Useful links and references
No response

The root cause here is that the Dockerfile is built on top of CentOS 7, which has reached its end-of-life. The package repositories that yum install uses are no longer available.
The Dockerfile should be amended to either include the following statement [1]:
RUN \
  sed -i s/mirror.centos.org/vault.centos.org/g /etc/yum.repos.d/*.repo && \
  sed -i s/^#.*baseurl=http/baseurl=http/g /etc/yum.repos.d/*.repo && \
  sed -i s/^mirrorlist=http/#mirrorlist=http/g /etc/yum.repos.d/*.repo

or updated to be based on a newer base OS (e.g. RockyLinux 8).
The PyDyna devs would know which is the correct action in this case.
[1] from https://serverfault.com/questions/1161816/mirrorlist-centos-org-no-longer-resolve


fix(default-theme):unknown element SwButton

The "add to cart"  button does not work due to an error:

[Vue warn]: Unknown custom element:  - did you register the component correctly? For recursive components, make sure to provide the "name" option.

Changes

Checklist

[ ] the list of features is updated (if it's a feature and it's relevant)
[ ] I followed contributing guidelines

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


Disable enable agent through config

We should be able to enable/disable agents through the config. We can define enabled flag in AgentConfig.
message AgentConfig {
 google.protobuf.BoolValue enabled = 5;
}

If enabled is set to false, then the agent will not do tracing and data capture.

+1 LGTM

+1 LGTM

+1
On Fri, 29 Jan 2021, 17:34 Pavol Loffay<EMAIL_ADDRESS>wrote:

+1 LGTM
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hypertrace/agent-config/issues/45#issuecomment-769911346,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYAQBHYF4HSSC43ZY3B3S4LPSRANCNFSM4WZD3AHA
.

+1
On Fri, 29 Jan 2021, 17:34 Pavol Loffay<EMAIL_ADDRESS>wrote:

+1 LGTM
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hypertrace/agent-config/issues/45#issuecomment-769911346,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYAQBHYF4HSSC43ZY3B3S4LPSRANCNFSM4WZD3AHA
.


Compute Module 5 experience

Hi,
I know that is too early to test / have a Compute Module 5 but I see that has exposed the sync out / sync in pin and also support PTP.
I do not know if the PHY drivers support unicast delays as is on CM4, because on RPI5 only multicast delays supported..... so a test would highly appreciated.
If someone have the CM5 or plan to buy it let as know if support PTP unicast delays.
Also if someone has a solution how to use the Network manager hook instead of dhcpd would be grate.
Regards,
Jim

I have a CM5.
Most important thing I have found out so far is that the silkscreen on the CM5 IO board is wrong: SYNC_OUT is pin 6 not pin 9.
The PHY on the RPi 5 (BCM54213) is different from the CM5: it doesn't support hardware timestamping. RPi 5 hardware timestamping is supported via the MAC driver.
I wouldn't expect any difference between the CM5 and CM4 as regards PTP support since they have exactly the same PHY (the BCM54210PE), but I haven't tested yet.

Hi @jclark,
That is why I am seeing on RPI5 that have hardware support on PHY and I was wondering what is going on, but as you say is MAC driver.
Here is the output of the RPI5:
Time stamping parameters for eth0:

   Capabilities:
        hardware-transmit
        software-transmit
        hardware-receive
        software-receive
        software-system-clock
        hardware-raw-clock
  PTP Hardware Clock: 0
  Hardware Transmit Timestamp Modes:
        off
        on
        onestep-sync
  Hardware Receive Filter Modes:
        none
        all

If you have time give a try on CM5 to see if have any difference.
Best regards,
Jim


About PREST dataset

Hello! Firstly, Thanks for your sharing!
Second, I wonder how can we get the dataset PREST mentioned in your paper？
I will be grateful if you can answer me this question. Thank you.

Sorry, the PREST recordings are collected from MGH and Beth Israel, which is private and could not be shared.


Generic unsupported u64 type

Aim
Why is the u64 type not supported? Is this how it should be, or is it a bug?
nargo - 0.32.0
bb - 0.46.1
Expected Behavior
Expected to use u64 type
Bug

error: The only supported numeric generic types are u1, u8, u16, and u32
┌─ /home/user/nargo/github.com/noir-lang/noir-bignumv0.2.2/src/lib.nr:296:6
│
296 │ impl<let N: u64, Params> std::ops::Mul for BigNum<N, Params> where Params: BigNumParamsTrait + RuntimeBigNumParamsTrait  {
│      ----------
│
error: The only supported numeric generic types are u1, u8, u16, and u32
┌─ /home/user/nargo/github.com/noir-lang/noir-bignumv0.2.2/src/lib.nr:306:6
│
306 │ impl<let N: u64, Params> std::ops::Div for BigNum<N, Params> where Params: BigNumParamsTrait + RuntimeBigNumParamsTrait  {
│      ----------
│
error: The only supported numeric generic types are u1, u8, u16, and u32
┌─ /home/user/nargo/github.com/noir-lang/noir-bignumv0.2.2/src/lib.nr:313:6
│
313 │ impl<let N: u64, Params> std::cmp::Eq for BigNum<N, Params> where Params: BigNumParamsTrait + RuntimeBigNumParamsTrait  {
│      ----------
To Reproduce

Workaround
None
Workaround Description
None
Additional Context
None
Project Impact
None
Blocker Context
None
Nargo Version
No response
NoirJS Version
No response
Proving Backend Tooling & Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response

u64 is mainly only unsupported due to internal implementation details that can be changed.
The other reason is that there's not much of a use case for it currently since the index & length type in Noir is u32 not u64.
Looks like the bignum library was just updated to use u32 - it was a bit out of date.


Make Machine class stateless

Nice to see this coming in :)

@LiuYuHui sorry for the delays, I was meant to do this a while ago. I rebased your branch now and it should be good to merge soon. Feel free to review in case I messed up the rebase


Alternative fonts other than those in /usr/fonts (for CJK & powerline support)?

The title describes my question quite clearly. I've tried placing a ttf or otf font in /accounts/1000/shared, but obviously it didn't work (huge font size, the default font and still squares for powerline / CJK characters).
Some CJK characters (Chinese & Japanese) for testing:
Chinese:
這是一個測試。ㄓㄜˋㄕˋㄧˉㄍㄜˋㄘㄜˋㄕˋ。
信（ㄒㄧㄣˋ） 相片（ㄒㄧㄤˋㄆㄧㄢˋ） 車票（ㄔㄜˉㄆㄧㄠˋ） 地圖（ㄉㄧˋㄊㄨˊ）

Japanese:
これはテストです。
手紙(てがみ)　写真(しゃしん)　切符(きっぷ)　地図(ちず)

I don't speak Korean, and it's not included here.

Unfortunately, I do not have a good answer to this one.
Term48 uses a single TTF file for all glyphs. It expects the glyphs to be monospaced, and all glyphs to be of equal size. You can change which font you're using by editing the font_path setting in .term48rc, and the specified path can be either absolute or relative to $HOME. If Term48 cannot open the font, or otherwise encounters an error when starting up, then it will try to revert to the default configuration, which uses the default courier font.
So in order to get good CJK coverage, you're looking for a single file, ttf, monospaced font that includes all the glyphs you're interested in. I don't know of one of these offhand, and my searches were not very fruitful (I suppose there is the GNU unifont, but it's a bitmap font, and doesn't seem to render well on my passport).
Sorry I cannot be more helpful. If you do find a nice font that includes better CJK coverage than the bundled fonts that come with BB10, I would be very happy to bundle it with Term48 to provide a better out-of-box experience (license permitting, of course).

In full-blown (modern) terminal emulators on PC, CJK characters are double-width (they are by nature) except some single-width katakana's, and if Term48 has to display all characters single-width'ly, this can be difficult to adapt. (I don't know how things are done in those terminals like Konsole or rxvt-unicode, I'll try digging in the source code and see) Actually there are single TTF files which include both CJK and Latin fonts (Noto Sans Mono CJK JP for example), but i've tried those and they won't get recognized by term48.
Another part of the issue, which may seem easier, is the powerline fonts. Powerline is a project about more beautiful and useful statuslines for vim, emacs and shells. It makes use of some special single-width characters (which should work fine on term48 in contrary to CJK characters) and needs proper fonts (here) to render correctly. I downloaded them and term48 refuses to use them as well. These are just normal TTF (most of them are) fonts with the characters needed replaced by the correct typefaces. If these can be working, life will be much happier (they're real eye candy as you can see on the project page linked above).

Where are you finding the TTF versions of the Noto Mono CJK fonts? I can only find OTF versions, which don't usually work. Desktop terminal emulators usually leverage a system font manager that includes fallback fonts, etc., which is why they seem to have full glyph coverage. Term48 doesn't do this. I previously had tried to leverage the BB10 text rendering facilities to get this, but it had unwanted side effects on text input. Otherwise, patching Term48 to identify double width characters and handling them appropriately would be a bit of work, assuming it could be done relatively easily.
For powerline, I downloaded the DejaVu Sans Mono for Powerline TTF and set it to be the .term48 font, and it seems to work. I have attached a screenshot showing various unicode glyphs that seem to render correctly. I didn't have to do anything special to make the glyphs work - I just saved the ttf to my home directory as dejavu.ttf, then edited .term48rc to use font_path = "dejavu.ttf", then restarted Term48.

Thanks for the powerline font notice. (maybe I had a typo in my previous try, who knew)
Font formats can be converted to each other easily. FontForge or even this online site can do them quite easily. If you really need some TrueType CJK font, I suggest looking into WenQuanYi series (they're TrueType compared to Noto being OpenType).

Ah, I had not looked into converting fonts, or merging several together. If good CJK support depends on supporting double width glyphs though, then we'd have to get that first.
I am glad you got the powerline font working. Cheers!


Init repo

In this project, I have refactored the JavaScript code with the following methods.
Changed named functions into arrow functions.
Introduced functions and classes through modules.
Displayed date using luxon library.

Hi @sameedmohsin28 😊,
STATUS: APPROVED! 🥇 💯

Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit: 🚀
Congratulations! 🎉
Highlights
✅ Project has met all the technical aspects you needed for this project. Keep rocking!
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


release artifacts for release v1.0.7

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

To be merged after https://github.com/aws-controllers-k8s/ec2-controller/pull/149


tag for sponsor

Please update script and add tag for sponsor proxy...

Use Official MTProxy instead,

no, i need use MTProxy for windows

Please, try to use https://github.com/alexbers/mtprotoproxy. It can run on any architecture that Python supports. But the installing of pycrypto or its analog is recommended (pip install cryptodome), otherwise it will work, but very slow.

You can also Install Docker For Windows then run pull and run Official Docker Image

This is the best library in this field. But why not support the tag?
please update script
thanks

please add sponsor tag
official not working perfectly :(

Please add sponsor tag

@mahdiazarm No
you can add 1 sponsor tag to every server!
and you can add 1 channel to unlimited server !

How to sponsor in Windows?


Document how to compose at the LINQ level

To avoid people dropping down to the expression builder when it is not required.

See https://github.com/aspnet/EntityFrameworkCore/issues/19380. Explain how to correctly do this.


DGC Template Guidelines

Hello,
I have a general question, will you use the graphic design of DGC in a mobile application according to the DGC Template Guidelines? Or do you use a different design?

Hi @jtomasuzis
PL has created own design based on the current national verification app.


fix: blank identifier cause panic

Fixes #252

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


Update tunnelblick to 3.7.1beta02,4810

After making all changes to the cask:

[x] `brew cask audit --download {{cask_file}}` is error-free.
[x] `brew cask style --fix {{cask_file}}` left no offenses.
[x] The commit message includes the cask’s name and version.

Is there a specific reason why the cask has been updated to a beta version and not kept at the stable release?

I did so beause it was marked as Latest release on github. Please feel free to revert if you disagree with the update.
https://github.com/Tunnelblick/Tunnelblick/releases


pngjs package version update

Hi
Thanks for the awesome package to compare image.
There are some missing updates in a package pngjs in file i.e /node_modules/node-resemble-js/node_modules/pngjs/lib/bitmapper.js file  and function mapImage8Bit
There are missing line of code in the previous version of package i.e
var idx = pixelBppMap[bpp][i];
        if (idx === 0xff) {
          pxData[pxPos + i] = 0xff;
        } else {
          var dataPos = idx + rawPos;
          if (dataPos === data.length) {
            throw new Error('Ran out of data');
          }
          pxData[pxPos + i] = data[dataPos];
        }

So we need to update the version of this package to resolved the issue in their previous releases.
So, I have updated the package pngjs in your package.json of node-resemble.js.Please update to resolve future issues.
Thanks
Regards
afzydev

Thanks!


HBASE-7003 Moved backup examples into hbase-examples

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
19
Docker mode activated.

_ Prechecks _

+1
hbaseanti
0
Patch does not have any anti-patterns.

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

+1
test4tests
0
The patch appears to include 25 new or modified test files.

_ master Compile Tests _

0
mvndep
27
Maven dependency ordering for branch

+1
mvninstall
264
master passed

+1
compile
88
master passed

+1
checkstyle
144
master passed

+1
shadedjars
277
branch has no errors when building our shaded downstream artifacts.

0
findbugs
0
Skipped patched modules with no Java source: hbase-checkstyle

+1
findbugs
225
master passed

+1
javadoc
60
master passed

_ Patch Compile Tests _

0
mvndep
14
Maven dependency ordering for patch

+1
mvninstall
252
the patch passed

+1
compile
86
the patch passed

+1
cc
86
the patch passed

+1
javac
86
the patch passed

+1
checkstyle
142
root: The patch generated 0 new + 0 unchanged - 68 fixed = 0 total (was 68)

+1
whitespace
1
The patch has no whitespace issues.

+1
xml
1
The patch has no ill-formed XML file.

+1
shadedjars
275
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
520
Patch does not cause any errors with Hadoop 2.7.4 or 3.0.0.

+1
hbaseprotoc
72
the patch passed

0
findbugs
0
Skipped patched modules with no Java source: hbase-checkstyle

+1
findbugs
276
the patch passed

+1
javadoc
61
the patch passed

_ Other Tests _

+1
unit
11
hbase-checkstyle in the patch passed.

+1
unit
7533
hbase-server in the patch passed.

+1
unit
107
hbase-examples in the patch passed.

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

10618

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-145/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/145

Optional Tests
dupname  asflicense  checkstyle  javac  javadoc  unit  xml  findbugs  shadedjars  hadoopcheck  hbaseanti  compile  cc  hbaseprotoc

uname
Linux 8c422b1ce546 4.4.0-143-generic #169~14.04.2-Ubuntu SMP Wed Feb 13 15:00:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/testptch/patchprocess/precommit/personality/provided.sh

git revision
master / f30d6c958a

maven
version: Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z)

Default Java
1.8.0_181

findbugs
v3.1.11

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-145/1/testReport/

Max. process+thread count
4627 (vs. ulimit of 10000)

modules
C: hbase-checkstyle hbase-server hbase-examples U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-145/1/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

I thought one of the consensus points for getting the backup/restore stuff into master was that it would be isolated in the one module. Maybe I'm misremembering though?

Wasn't aware of it. Should I remove the changes to the backup/restore stuff from this patch?

Yes, it was important that the backup be totally contained in a module. In fact, now we have alternatives, backup should be moved out of core to something like hbase-operator-tools. Can bring it up on dev lists.
That said, your patch here looks like good cleanup @HorizonNet .  You are fixing formatting, line lengths, over-imports. Is that the nature of this patch no? If so, lets get it in.

Core of the patch is to move everything into hbase-examples, but I tried to ensure that we don't get any Checkstyle issues during the move.

Could we have a patch that has your cleanup only? i.e. no move to hbase-examples? There is good stuff in here. Would be shame to throw away? Maybe a new issue? Kill this one?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
26
Docker mode activated.

_ Prechecks _

+1
hbaseanti
0
Patch does not have any anti-patterns.

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

+1
test4tests
0
The patch appears to include 24 new or modified test files.

_ master Compile Tests _

0
mvndep
25
Maven dependency ordering for branch

+1
mvninstall
269
master passed

+1
compile
95
master passed

+1
checkstyle
136
master passed

+1
shadedjars
275
branch has no errors when building our shaded downstream artifacts.

0
findbugs
0
Skipped patched modules with no Java source: hbase-checkstyle

+1
findbugs
247
master passed

+1
javadoc
60
master passed

_ Patch Compile Tests _

0
mvndep
14
Maven dependency ordering for patch

+1
mvninstall
252
the patch passed

+1
compile
94
the patch passed

+1
cc
94
the patch passed

+1
javac
94
the patch passed

+1
checkstyle
139
root: The patch generated 0 new + 0 unchanged - 27 fixed = 0 total (was 27)

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
2
The patch has no ill-formed XML file.

+1
shadedjars
274
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
787
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
hbaseprotoc
73
the patch passed

0
findbugs
0
Skipped patched modules with no Java source: hbase-checkstyle

+1
findbugs
275
the patch passed

+1
javadoc
63
the patch passed

_ Other Tests _

+1
unit
10
hbase-checkstyle in the patch passed.

-1
unit
8511
hbase-server in the patch failed.

+1
unit
107
hbase-examples in the patch passed.

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

12164

Reason
Tests

Failed junit tests
hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-145/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/145

Optional Tests
dupname  asflicense  checkstyle  javac  javadoc  unit  xml  findbugs  shadedjars  hadoopcheck  hbaseanti  compile  cc  hbaseprotoc

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

Build tool
maven

Personality
/testptch/patchprocess/precommit/personality/provided.sh

git revision
master / ada772a1d3

maven
version: Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z)

Default Java
1.8.0_181

findbugs
v3.1.11

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-145/3/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-145/3/testReport/

Max. process+thread count
4717 (vs. ulimit of 10000)

modules
C: hbase-checkstyle hbase-server hbase-examples U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-145/3/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

Closing this one and will open a new ticket. @saintstack Should I also close the corresponding ticket?


Let magic Prophecy methods accept specific Argument tokens

Following issue #29, also support

Argument::type('null')
Argument::exact
Argument::is

for magic Prophecy methods

Or any other way to provide a TokenInterface of Prophecy.