Kundera - Cassandra : Issue with Embedded UDT Entities

The issue is described below.
https://stackoverflow.com/questions/45467495/kundera-cassandra-jpql-with-compound-key
If I remove the ElementCollection attribute "Comments" (which is equivalent to Comments UDT in Cassandra) things work fine.
Any known issues around it?
The issue is observed with 3.8 release as well.

@crashedserver
Yes this is a bug. We will fix it and it will be available in next release.
-Karthik

Thanks Karthik for the confirmation. Any tentative schedule for the next
release?
On Aug 3, 2017 2:04 PM, "karthikprasad13"<EMAIL_ADDRESS>wrote:
@crashedserver https://github.com/crashedserver
Yes this is a bug. We will fix it and it will be available in next release.
-Karthik
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/impetus-opensource/Kundera/issues/953#issuecomment-319904965,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASWPt299cOLPOGSXcWAwZQ56nHVLvgHQks5sUYYEgaJpZM4OrdM3
.

@crashedserver
We planned our next release within 2 weeks.
-Karthik

Hi @crashedserver,
This has been fixed and will be available in Kundera 3.10
-Dev

Getting the following exception with 3.10.  Looks like dependency issue.  Using the following Cassandra dependency.

org.apache.cassandra
cassandra-all
3.11.0

com.google.guava
guava

    </dependency>

java.lang.NoSuchMethodError: org.apache.cassandra.serializers.ListSerializer.deserializeForNativeProtocol(Ljava/nio/ByteBuffer;I)Ljava/util/List;
at com.impetus.client.cassandra.datahandler.CassandraDataHandlerBase.setElementCollectionList(CassandraDataHandlerBase.java:1735)
at com.impetus.client.cassandra.datahandler.CassandraDataHandlerBase.setElementCollection(CassandraDataHandlerBase.java:1576)
at com.impetus.client.cassandra.datahandler.CassandraDataHandlerBase.populateViaThrift(CassandraDataHandlerBase.java:1154)
at com.impetus.client.cassandra.datahandler.CassandraDataHandlerBase.onColumn(CassandraDataHandlerBase.java:1054)
at com.impetus.client.cassandra.datahandler.CassandraDataHandlerBase.populateEntity(CassandraDataHandlerBase.java:653)
at com.impetus.client.cassandra.CassandraClientBase$CQLClient.executeQuery(CassandraClientBase.java:2301)
at com.impetus.client.cassandra.CassandraClientBase.executeSelectQuery(CassandraClientBase.java:926)
at com.impetus.client.cassandra.thrift.ThriftClient.executeQuery(ThriftClient.java:1062)
at com.impetus.client.cassandra.CassandraClientBase$CQLClient.find(CassandraClientBase.java:2421)
at com.impetus.client.cassandra.CassandraClientBase.populate(CassandraClientBase.java:787)
at com.impetus.client.cassandra.CassandraClientBase.find(CassandraClientBase.java:752)
at com.impetus.client.cassandra.CassandraClientBase.find(CassandraClientBase.java:686)
at com.impetus.client.cassandra.thrift.ThriftClient.find(ThriftClient.java:350)
at com.impetus.kundera.persistence.AbstractEntityReader.findById(AbstractEntityReader.java:81)
at com.impetus.client.cassandra.query.CassandraEntityReader.findById(CassandraEntityReader.java:93)
at com.impetus.kundera.lifecycle.states.ManagedState.handleFind(ManagedState.java:137)
at com.impetus.kundera.graph.Node.find(Node.java:500)
at com.impetus.kundera.persistence.PersistenceDelegator.find(PersistenceDelegator.java:225)
at com.impetus.kundera.persistence.PersistenceDelegator.findById(PersistenceDelegator.java:174)
at com.impetus.kundera.persistence.EntityManagerImpl.find(EntityManagerImpl.java:263)

Hi @crashedserver
Why are you adding cassandra-all dependency?
It's already added in Kundera-cassandra.
-Dev

@devender-yadav  Many Thanks. It works now. Will do some more testing around it and update in case of issues. Thanks for fixing it.

You're welcome @crashedserver!


Private registry push fail: server gave HTTP response to HTTPS client

My private registry worked well based on docker 1.10.3, but it can't pull/push images after docker updated to 1.12.0.
I had modified the /etc/sysconfig/docker as:
OPTIONS='--selinux-enabled=true --insecure-registry=myip:5000'
or
OPTIONS='--selinux-enabled=true --insecure-registry myip:5000'
but when I exec pull/push,I got this error:
$ docker pull myip:5000/cadvisor
Using default tag: latest
Error response from daemon: Get https://myip:5000/v1/_ping: http: server gave HTTP response to HTTPS client
when I change back docker to 1.10.3, it still work well as below:
$ docker pull myip:5000/cadvisor
Using default tag: latest
Trying to pull repository myip:5000/cadvisor ...
latest: Pulling from myip:5000/cadvisor
09d0220f4043: Pull complete
a3ed95caeb02: Pull complete
151807d34af9: Pull complete
14cd28dce332: Pull complete
Digest:
sha256:33b6475cd5b7646b3748097af1224de3eee3ba7cf5105524d95c0cf135f59b47
Status: Downloaded newer image for myip:5000/cadvisor:latest
As suggested by RichardScothern, some relative informations are listed below:
docker version
Client:
Version:      1.12.0
API version:  1.24
Go version:   go1.6.3
Git commit:   8eab29e
Built:
OS/Arch:      linux/amd64
Server:
Version:      1.12.0
API version:  1.24
Go version:   go1.6.3
Git commit:   8eab29e
Built:
OS/Arch:      linux/amd64
docker info
Containers: 4
Running: 1
Paused: 0
Stopped: 3
Images: 241
Server Version: 1.12.0
Storage Driver: devicemapper
Pool Name: docker-253:0-6809-pool
Pool Blocksize: 65.54 kB
Base Device Size: 107.4 GB
Backing Filesystem: xfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 5.459 GB
Data Space Total: 107.4 GB
Data Space Available: 34.74 GB
Metadata Space Used: 9.912 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.138 GB
Thin Pool Minimum Free Space: 10.74 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
WARNING: Usage of loopback devices is strongly discouraged for production use. Use '--storage-opt dm.thinpooldev' to specify a custom block storage device.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.107-RHEL7 (2016-06-09)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: host overlay null bridge
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-229.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 24
Total Memory: 62.39 GiB
Name: server_3
ID: TITS:BL4B:M5FE:CIRO:5SW6:TVIV:HW36:J7OS:WLHF:46T6:2RBA:WCNV
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 21
Goroutines: 32
System Time: 2016-08-02T10:33:06.414048675+08:00
EventsListeners: 0
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Insecure Registries:
<IP_ADDRESS>/8
docker exec <registry-container> registry -version
registry github.com/docker/distribution v2.2.1
After I restart the docker daemon in debug mode, the daemon logs when reproducing my problem are listed below:
DEBU[0794] Calling POST /v1.24/images/create?fromImage=<IP_ADDRESS>%3A5000%2Fcadvisor&tag=latest
DEBU[0794] hostDir: /etc/docker/certs.d/<IP_ADDRESS>:5000
DEBU[0794] hostDir: /etc/docker/certs.d/<IP_ADDRESS>:5000
DEBU[0794] Trying to pull <IP_ADDRESS>:5000/cadvisor from https://<IP_ADDRESS>:5000 v2
WARN[0794] Error getting v2 registry: Get https://<IP_ADDRESS>:5000/v2/: http: server gave HTTP response to HTTPS client
ERRO[0794] Attempting next endpoint for pull after error: Get https://<IP_ADDRESS>:5000/v2/: http: server gave HTTP response to HTTPS client
DEBU[0794] Trying to pull <IP_ADDRESS>:5000/cadvisor from https://<IP_ADDRESS>:5000 v1
DEBU[0794] hostDir: /etc/docker/certs.d/<IP_ADDRESS>:5000
DEBU[0794] attempting v1 ping for registry endpoint https://<IP_ADDRESS>:5000/v1/
DEBU[0794] Fallback from error: Get https://<IP_ADDRESS>:5000/v1/_ping: http: server gave HTTP response to HTTPS client
ERRO[0794] Attempting next endpoint for pull after error: Get https://<IP_ADDRESS>:5000/v1/_ping: http: server gave HTTP response to HTTPS client
ERRO[0794] Handler for POST /v1.24/images/create returned error: Get https://<IP_ADDRESS>:5000/v1/_ping: http: server gave HTTP response to HTTPS client
DEBU[1201] clean 2 unused exec commands
What's more, I just run a simple command to launch the private registry for test, anything else is by default:
docker run -d -p 5000:5000 --restart=always --name registry   -v 'pwd'/data:/var/lib/registry registry:2
Neither nginx nor proxy is configured. In summary, it is only a quiet sample environment for test.
Hope you guys giving me some suggestions ,thank you!

Please follow these instructions to help us diagnose your issue

create a new issue, with a succinct title that describes your issue:

bad title: "It doesn't work with my docker"
good title: "Private registry push fail: 400 error with E_INVALID_DIGEST"

copy the output of:

docker version
docker info
docker exec <registry-container> registry -version

copy the command line you used to launch your Registry
restart your docker daemon in debug mode (add -D to the daemon launch arguments)
reproduce your problem and get your docker daemon logs showing the error
if relevant, copy your registry logs that show the error
provide any relevant detail about your specific Registry configuration (e.g., storage backend used)
indicate if you are using an enterprise proxy, Nginx, or anything else between you and your Registry

@RichardScothern ,thank you for your comment and I will modify the issue with your suggestions.

Can we see your config @wudiapo135 ?  Do you have tls configured?

Looks like a docker configuration issue. The --insecure-registry=myip:5000 flag is not getting set on the daemon, causing this error. Try running the daemon manually with your desired options and see if you get the same issue.

I get helped from [http://stackoverflow.com/questions/38695515/can-not-pull-push-images-after-update-docker-to-1-12], two steps in total to solve this issue:

Create or modify /etc/docker/daemon.json
{ "insecure-registries":["myregistry.example.com:5000"] }
Restart docker daemon
sudo service docker restart

I agree with @dmcgowan

The--insecure-registry=myip:5000 flag is not getting set on the daemon

but I have no idea about why it only occurred under docker version 1.12. I will keep this issue open in next three days, any comments are welcome.

Can we see your config @wudiapo135 ? Do you have tls configured?
I had never change the config for tls, so tls config is setting by default.

why is this issue closed?
I am having same issue
Ubuntu 16.04.1 LTS
Docker version 1.12.1, build 23cf638
i have added
DOCKER_OPTS="--insecure-registry=dockerhub.example.com:5000"
to /etc/default/docker
and i tried editing the systemd file and returned
Failed to restart docker.service: Unit docker.service is not loaded properly: Invalid argument.
See system logs and 'systemctl status docker.service' for details

when i followed this https://docs.docker.com/engine/admin/systemd/ and added
EnvironmentFile=-/etc/default/docker

Please re-open, this issue is still happening and i was on docker version 1.11 and thought upgrade will help but not helping

Same problem here but with Docker for Mac Version 1.12.1-beta26.1 (build: 12100).
Solved adding the insecure registry in Docker Mac App preferences.
Why this issue is closed?

@daniloascione the OP closed this issue because he fixed the cause of the error by correctly setting the --insecure-registry flag.  If you are having a similar issue and this is not helping you then open another issue describing your problem.

@RichardScothern I see... so the correct way to set the insecure-registry flag is modifying /etc/docker/daemon.json, and the --insecure-registry=myip:5000 flag is not getting set on the daemon, as reported before. Thank you.

@wudiapo135, I did the same per your comments, but still got the same error: Private registry push fail: server gave HTTP response to HTTPS client
My docker version: Docker version 1.12.2, build bb80604

I also have the same problem with this docker version for Mac.
Docker version 1.12.2, build bb80604
registry added to insecure registries in preferences but no luck. Worked in 1.12.1.

With Docker For Mac, the registries setting doesn't seems to be very sticky. I originally added my registry as https:// and got this error. I changed the address to http and restarted Docker, but the error persisted.
After removing the setting altogether, restarting Docker, then adding the setting back and restarting again it stuck and started working. YMMV.

I have the same issue with docker 1.12.4.

Same issue with 1.13.1, solved using solution of @wudiapo135

I had a Beta version when I've installed the stable version the issue did not appear anymore.

I am still getting the issue in version 1.12.6 and running the registry using the command : docker run -d -p 5000:5000 --restart=always --name registry registry:2

i have same issue with docker 1.12.6.

Same issue since upgrading, adding --insecure-registry localhost:5000 fixed it(using the docker registry image in my case).
Would be nice to have localhost automagically added ...

Try adding --insecure-registry option to daemon in /etc/systemd/system/docker.service.d/docker.conf file.
Then sudo systemctl daemon-reload
And sudo service docker restart
It worked for me
OS: Ubuntu 16.04
Docker: 1.26

The same problem here, solved modifying the "/etc/docker/daemon.json" file just like @wudiapo135 suggested.
docker -v -> Docker version 17.03.1-ce, build c6d412e
uname -r -> 4.8.0-36-generic (Ubuntu 16.04.2 LTS Xenial Xerus)

For Centos 7, just modify ' /usr/lib/systemd/system/docker.service':
vi /usr/lib/systemd/system/docker.service
ExecStart=/usr/bin/dockerd --insecure-registry  XXX.YYY.ZZZ.WWW:5000
And now Reset docker:
systemctl daemon-reload
service docker restart
Where  XXX.YYY.ZZZ.WWW:5000  if the IP of the master node where the registry image is running.
Remember to apply this modification in the master node and also in the slaves

I have an aws ubuntu instance 14.04. I can login via the instance or host but cannot log in from outside.
http: server gave HTTP response to HTTPS client
Is this to do with docker?
Do i need to configure firewall and open ports in aws instance group policy? I have allowed 5000 http 80 and https 443.
bash [Service] EnvironmentFile=/etc/default/docker ExecStart= ExecStart=/usr/bin/docker daemon -H fd:// --insecure-registry ec2-35-160-82-207.us-west-2.compute.amazonaws.com:5000 <IP_ADDRESS>:5000
Ubuntu 16.04 aws instance
Docker version 17.03.1-ce, build c6d412e

Dear @pranay-91,
Check usual things: port 5000 is not in use, firewall configuration and Docker log entries.
User @saavkaar  ran it in Ubuntu 16.04 and Docker: 1.26

I had the insecure-registry url already, and while it worked once, it didn't work after a VM restart.
I just had to restart docker and it worked this time without the https gave http error.

I had the same problem as here, but with Docker on Windows. Turns out that the file at C:\ProgramData\docker\config\daemon.json isn't the only source of config here; if I right-click the docker icon in the taskbar and choose Settings...->Daemon and enable advanced config editing, I get a different set of settings.
Adding the insecure registry there, not in the daemon.json file on disk, seems to have solved my problem.

Also you can install haproxy and add config:
frontend http
        bind *:80
        redirect scheme https if !{ ssl_fc }

frontend https
        bind *:443 ssl crt {{{ your certificate  }}}
        acl host_docker hdr(host) -i docker.domain.com
        reqadd X-Forwarded-Port:\ 443
        reqadd X-Forwarded-Proto:\ https
        reqadd X-Forwarded-Scheme:\ https
        use_backend docker if host_docker

backend docker
        reqadd X-Forwarded-Host:\ docker.domain.com
        server docker <IP_ADDRESS>:5000

then you don't need --insecure-registry  flag

Is /etc/docker/daemon.json the correct file path to add {"insecure-registries": ["<IP_ADDRESS>:5000"]} on macOS Sierra Version 10.12.6?
docker --version --> Docker version 17.06.0-ce, build 02c1d87
I have private registry running on a Ubuntu VM on my Mac which is accessible via SSH on my Mac
On Ubuntu 14.04 VM:
docker --version --> Docker version 17.06.1-ce, build 874a737
I am able to push to private registry from within the Ubuntu VM, but when I try to push it from Mac using the VM's IP Address (that I use to SSH into my VM), I get the output
The push refers to a repository [<IP_ADDRESS>:5000/alpine-mymac]
Get https://<IP_ADDRESS>:5000/v2/: http: server gave HTTP response to HTTPS client

Note: <IP_ADDRESS> is my VM's IP Address

@ProProgrammer on mac OS X is daemon.json in path: ~/Library/Containers/com.docker.docker/Data/database/com.docker.driver.amd64-linux/etc/docker

@Applemann etc/docker do not exist in /Users/ds/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux for me. Should I just create the full path /Users/ds/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/etc/docker/daemon.json?

@ProProgrammer yes you can try it.

This is a mess, we have the same problem, it worked fine until now.
I have added the /etc/docker/daemon.json befor and it worked just fine....
How can we correct his issue?

If you are using Docker for Windows with linux containers, the 'insecure-registries' setting is here:
C:\Program Files\Docker\Docker\resources\linux-daemon-options.json
I'm using Docker for Windows, but I'm not actually using the 'for Windows' part.  Instead I followed the 'hyperv' instructions.

Install docker for windows but uncheck the 'start at login' box.  Instead, follow the instructions for creating a docker machine using hyperv - https://docs.docker.com/machine/drivers/hyper-v/ .  I called mine 'dockervm'

Create a scheduled task to run at startup 'C:\Program Files\Docker\Docker\resources\bin\docker-machine start dockervm'.  Make sure to not use double quotes as there is a bug in the windows 10 task scheduler.

After step 1 your docker machine is running, use 'docker-machine env dockervm' to get the environment, and set it in your global environment settings.

After a reboot, your dockervm should be running, and docker ps -a should return results.

Run the registry locally: docker run -d -p 5000:5000 --name registry registry:2

Open 'Hyper-V Manager' and select 'dockervm' (it should be running).  Click 'Connect...' under dockervm on the right to open a shell.  You should now be at a root shell prompt in your dockervm

From the root shell prompt, cd to /var/lib/boot2docker

vi profile

Add a new line to this part with your registry (my vm's IP is <IP_ADDRESS>)
EXTRA_ARGS='
--label provider=hyperv
--insecure-registry=<IP_ADDRESS>:5000
'
8. Restart the dockervm machine in hyperv manager
You should now be able to push to the registry

I'd like to clarify that you should add the { "insecure-registries":["myregistry.example.com:5000"] } to /etc/docker/daemon.json in the client machine.

I added the docker registry network CIDR  in '/etc/sysconfig/docker ' of clients eg: 'OPTIONS= - --insecure-registry=<IP_ADDRESS>/24' and is working fine.

For Mac users, it seems like they added the ability to configure insecure registries in the GUI, via Preferences > Daemon > Insecure registries.

tl;dr make sure you are using a correct user/password :-)

According to the https://docs.docker.com/registry/insecure/#deploy-a-plain-http-registry - message http: server gave HTTP response to HTTPS client does not mean it is a reason of the issue:

With insecure registries enabled, Docker goes through the following steps:
First, try using HTTPS.

If HTTPS is available but the certificate is invalid, ignore the error about the certificate.
If HTTPS is not available, fall back to HTTP.

docker login
$ echo corr3ctpassword | docker login -u user --password-stdin reg.mysite.com:80
Login Succeeded

$ journalctl -u docker -f
Jul 10 21:34:19 laptop dockerd[30795]: time="2018-07-10T21:34:19.365956391+02:00" level=info msg="Error logging in to v2 endpoint, trying next endpoint: Get https://reg.mysite.com:80/v2/: http: server gave HTTP response to HTTPS client"

docker login with the wrong password
$ echo wr0ngpassword | docker login -u user --password-stdin reg.mysite.com:80
Error response from daemon: Get http://reg.mysite.com:80/v2/: unauthorized: authentication required

$ journalctl -u docker -f
Jul 10 21:33:38 laptop dockerd[30795]: time="2018-07-10T21:33:38.200034001+02:00" level=info msg="Error logging in to v2 endpoint, trying next endpoint: Get https://reg.mysite.com:80/v2/: http: server gave HTTP response to HTTPS client"

Setup

docker version: 17.12.1-ce

Either A. or B., both cannot work together.
When you change docker.service files, do not forget to run systemctl daemon-reload && systemctl restart docker as root.

A) /etc/systemd/system/docker.service.d/insecure.conf

[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -H fd:// --insecure-registry :80

B) /etc/docker/daemon.json

{
  "insecure-registries" : ["reg.mysite.com:80"]
}

I try to add {"insecure-registries": ["localhost:5000"]} to /etc/docker/daemon.json
It's worked for me
you can try it
or  use   /etc/hosts  to resolve the domain you want

ubuntu
Edit configuration file /etc/systemd/system/multi-user.target.wants/docker.service
ExecStart=/usr/*************   --insecure-registry  yourip:5000

i added ExecStart=/usr/************* --insecure-registry yourip:5000 ,but still can't work, the same as {
"insecure-registries" : ["reg.mysite.com:80"]
}

For  Docker version 18.09.2,  I followed https://success.docker.com/article/using-systemd-to-control-the-docker-daemon

sudo systemctl edit docker
add below lines

[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -H fd://  --insecure-registry registry:5000

sudo systemctl daemon-reload
systemctl restart docker
systemctl status docker

For Docker version 19.03.1 on a Windows 10 machine, this is how I resolved it:
I opened up docker's settings in the gui:

Clicked on the Daemon section, click on the toggle button Basic to enable Advance mode:

Enter in your config. :)

I already config the "--insecure-registry localhost:5000" in /etc/sysconfig/docker and "systemctl restart docker". See below:
[root@dhcp-140-36 ~]# docker info
Containers: 5
 Running: 0
 Paused: 0
 Stopped: 5
Images: 40
Server Version: 1.13.1
...
Insecure Registries:
 localhost:5000
 <IP_ADDRESS>/8
...

But, still got errors: Unable to connect to the server: http: server gave HTTP response to HTTPS client. Anyone know how to solve it? Thanks!
[root@dhcp-140-36 db-731491371]# oc adm catalog build --appregistry-org=jiazha --to=localhost:5000/jiazha/catalog:v1 --loglevel=8
...
INFO[0003] directory                                     dir=/tmp/manifests-314255191 file=learn-operator load=package
I1125 16:15:48.553395   11938 builder.go:105] database written /tmp/db-251746264/bundles.db
I1125 16:15:48.566404   11938 builder.go:115] built db layer /tmp/archive-942757578/layer.tar.gz
I1125 16:15:48.566462   11938 config.go:137] looking for config.json at /root/.docker/config.json
I1125 16:15:48.566694   11938 config.go:145] found valid config.json at /root/.docker/config.json
I1125 16:15:48.566743   11938 round_trippers.go:420] GET https://localhost:5000/v2/
I1125 16:15:48.566753   11938 round_trippers.go:427] Request Headers:
I1125 16:15:48.567916   11938 round_trippers.go:446] Response Status:  in 1 milliseconds
I1125 16:15:48.567929   11938 round_trippers.go:449] Response Headers:
I1125 16:15:48.567952   11938 helpers.go:217] Connection error: Get https://localhost:5000/v2/: http: server gave HTTP response to HTTPS client
F1125 16:15:48.567961   11938 helpers.go:114] Unable to connect to the server: http: server gave HTTP response to HTTPS client

[root@dhcp-140-36 ~]# docker run -it --rm -p 5000:5000 registry
WARN[0000] No HTTP secret provided - generated random secret. This may cause problems with uploads if multiple registries are behind a load-balancer. To provide a shared secret, fill in http.secret in the configuration file or set the REGISTRY_HTTP_SECRET environment variable.  go.version=go1.11.2 instance.id=871badf0-b4d3-44fe-aca3-300b969ede4f service=registry version=v2.7.1
INFO[0000] redis not configured                          go.version=go1.11.2 instance.id=871badf0-b4d3-44fe-aca3-300b969ede4f service=registry version=v2.7.1
INFO[0000] Starting upload purge in 1m0s                 go.version=go1.11.2 instance.id=871badf0-b4d3-44fe-aca3-300b969ede4f service=registry version=v2.7.1
INFO[0000] using inmemory blob descriptor cache          go.version=go1.11.2 instance.id=871badf0-b4d3-44fe-aca3-300b969ede4f service=registry version=v2.7.1
INFO[0000] listening on [::]:5000                        go.version=go1.11.2 instance.id=871badf0-b4d3-44fe-aca3-300b969ede4f service=registry version=v2.7.1
INFO[0060] PurgeUploads starting: olderThan=2019-11-18 08:16:34.579628009 +0000 UTC m=-604739.979538633, actuallyDelete=true
INFO[0060] Purge uploads finished.  Num deleted=0, num errors=1
INFO[0060] Starting upload purge in 24h0m0s              go.version=go1.11.2 instance.id=871badf0-b4d3-44fe-aca3-300b969ede4f service=registry version=v2.7.1

I ran into this issue by following the instructions for Docker Registry, where I changed localhost.  I think it should be documented on that page that one must enable insecure-registries.

For Docker version 18.09.2, I followed https://success.docker.com/article/using-systemd-to-control-the-docker-daemon

sudo systemctl edit docker
add below lines

[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -H fd:// --insecure-registry registry:5000

sudo systemctl daemon-reload
systemctl restart docker
systemctl status docker

@santhoshkumarhirekerur  Thank you.  That link finally fixed mine.  That was 5 hours of pulling my hair out.  I wish I could buy you a beer!

Solution :
If you want to pull/push image on particular host let say <IP_ADDRESS> from private registry that you hosted on another node
then
1.go to /etc/hosts  of your host and gave same domain name to this ip <IP_ADDRESS> like -
<IP_ADDRESS>    myregistry.local.com
2.go to /etc/docker/daemon.json of you hosts
note: if daemon.json not present, create it inside /etc/docker/
3.open daemon.json and write following lines -
{
"insecure-registries": ["myregistry.local.com:5000"]
}
4.Restart docker
service docker stop
service docker start
5.try to pull image using  for eg : docker pull "myregistry.local.com:5000/username/imagename"
that's it!

If someone with GitLab CI docker:dind as a service comes here (as I did), here's the answer you're looking for: https://stackoverflow.com/a/50133074 .

Only this worked for me :
{
"insecure-registries" : ["<IP_ADDRESS>/8", "myregistrydomain.com:5000"]
}

I had similar issues and nothing seemed to work but I eventually resolved the problem because I found that either the insecure-registries or both the docker push command (in my situation) are case sensitive.
I had the following in /etc/docker/daemon.json:
{ "insecure-registries":["MYREGISTRY.example.com:5000"] }
And was running
docker push myregistry.example.com:5000/mysql-server
And still getting:
http: server gave HTTP response to HTTPS client
Changing the command to:
docker push MYREGISTRY.example.com:5000/mysql-server
Solved the push issue but the error is not remotely representitive of the issue at all as it was a URL case sensitivity problem...

If the daemon.json file does not exist, create it. Assuming there are no other settings in the file, it should have the following contents:
{
  "insecure-registries" : ["myregistrydomain.com:5000"]
}

i have setup a gitlab insecure container registry in my local machine and i added config for insecure registries to docker daemon.json file:
{"insecure-registries": ["<IP_ADDRESS>:5001"]}

and also to the /etc/default/docker:
DOCKER_OPTS="--insecure-registry <IP_ADDRESS>:5001"

and restart the docker (many times!!!)
and i can see the setting in docker info:
 Insecure Registries:
  <IP_ADDRESS>:5001
  <IP_ADDRESS>/8

i can login to the registry and start a push but as things progress it hits an error and start retrying:
The push refers to repository [<IP_ADDRESS>:5001/root/gohello]
393bd09b891b: Retrying in 12 seconds
bb63b571c364: Retrying in 12 seconds

and after that it fails with this error:
393bd09b891b: Pushing [==================================================>]   5.76MB/5.76MB
bb63b571c364: Pushing  2.048kB
http: server gave HTTP response to HTTPS client

i ran docker in debug mode and these are the logs:
level=debug msg="Trying to push <IP_ADDRESS>:5001/root/gohello to https://<IP_ADDRESS>:5001 v2"
level=debug msg="Error getting v2 registry: Get https://<IP_ADDRESS>:5001/v2/: http: server gave HTTP response to HTTPS client"
level=info msg="Attempting next endpoint for push after error: Get https://<IP_ADDRESS>:5001/v2/: http: server gave HTTP response to HTTPS client"
level=debug msg="Trying to push <IP_ADDRESS>:5001/root/gohello to http://<IP_ADDRESS>:5001 v2"
level=debug msg="Pushing repository: <IP_ADDRESS>:5001/root/gohello:latest"
level=debug msg="Pushing layer: sha256:bb6..."
level=debug msg="Pushing layer: sha256:393.."
level=debug msg="Assembling tar data for ac0..."
level=error msg="Upload failed, retrying: http: server gave HTTP response to HTTPS client

i am using docker 19.03.13
please help i have been stuck at this for the last 8 hours.

Hi,
Make sure the case is the same:
This error will appear if you use a different case in:

{ "insecure-registries":["myregistry.example.com:5000"] }
docker push MYREGISTRY.example.com:5000/mysql-server

Looks like your config is otherwise OK.
James
On Fri, 4 Dec 2020 at 21:11, jamshidian<EMAIL_ADDRESS>wrote:

i have setup a gitlab insecure container registry in my local machine and
i added config for insecure registries to docker daemon.json file:
{"insecure-registries": ["<IP_ADDRESS>:5001"]}
and also to the /etc/default/docker:
DOCKER_OPTS="--insecure-registry <IP_ADDRESS>:5001"
and restart the docker (many times!!!)
and i can see the setting in docker info:
Insecure Registries:
<IP_ADDRESS>:5001
<IP_ADDRESS>/8
i can login to the registry and start a push but as things progress it
hits an error and start retrying:
The push refers to repository [<IP_ADDRESS>:5001/root/gohello]
393bd09b891b: Retrying in 12 seconds
bb63b571c364: Retrying in 12 seconds
and after that it fails with this error:
393bd09b891b: Pushing [==================================================>]   5.76MB/5.76MB
bb63b571c364: Pushing  2.048kB
http: server gave HTTP response to HTTPS client
i ran docker in debug mode and these are the logs:
level=debug msg="Trying to push <IP_ADDRESS>:5001/root/gohello to https://<IP_ADDRESS>:5001 v2"
level=debug msg="Error getting v2 registry: Get https://<IP_ADDRESS>:5001/v2/: http: server gave HTTP response to HTTPS client"
level=info msg="Attempting next endpoint for push after error: Get https://<IP_ADDRESS>:5001/v2/: http: server gave HTTP response to HTTPS client"
level=debug msg="Trying to push <IP_ADDRESS>:5001/root/gohello to http://<IP_ADDRESS>:5001 v2"
level=debug msg="Pushing repository: <IP_ADDRESS>:5001/root/gohello:latest"
level=debug msg="Pushing layer: sha256:bb6..."
level=debug msg="Pushing layer: sha256:393.."
level=debug msg="Assembling tar data for ac0..."
level=error msg="Upload failed, retrying: http: server gave HTTP response to HTTPS client
i am using docker 19.03.13
please help i have been stuck at this for the last 8 hours.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/docker/distribution/issues/1874#issuecomment-739022883,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYYFMLEXZYZPQN74PPH4DDSTFGAXANCNFSM4CLFVBEQ
.


libsForQt5.libopenshot: use ffmpeg instead of ffmpeg_3

Motivation for this change
https://github.com/NixOS/nixpkgs/issues/94003 and #120372
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 120600 at 3af3db20 run on x86_64-linux 1

4 packages built successfully:

libsForQt5.libopenshot (libsForQt515.libopenshot ,plasma5Packages.libopenshot)
libsForQt512.libopenshot
libsForQt514.libopenshot
openshot-qt

3 suggestions:

warning: build-tools-in-build-inputs
swig is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/video/openshot-qt/libopenshot.nix:38:3:
   |
38 |   buildInputs =
   |   ^

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/applications/video/openshot-qt/libopenshot.nix:23:5:
   |
23 |     (fetchpatch {
   |     ^

warning: unused-argument
Unused argument: unittest-cpp.
Near pkgs/applications/video/openshot-qt/libopenshot.nix:5:3:
  |
5 | , unittest-cpp, cppzmq, zeromq
  |   ^


Disable Duplicated Tests

Description
It looks like tag database_integration from test_with_database_network make target is not used anywhere, which results in duplicated invocation of tests that are also invoked in previous targets.
Changes proposed in this pull request:

Remove unnecessary tests invocation.

Related issue(s)

Useless PR...


Handling InterruptedExceptions coming from DozerBeanMapper.initMappings

Hi there,
My company's application uses DozerBeanMapper for mapping objects like this:
public <I, O> void map(I source, O destination) throws MappingException {
    if (source == null) {
        return;
    }
    mapper.map(source, destination);
}

This works fine for the most part, but sometimes, possibly when the application is under load, we'll see a ton of InterruptedExceptions coming from DozerBeanMapper.initMappings:
[#|2015-12-09T17:18:14.709-0500|SEVERE|glassfish3.1.2|org.dozer.DozerBeanMapper|_ThreadID=385;_ThreadName=Thread-7;|Thread interrupted:
java.lang.InterruptedException
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301)
    at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
    at org.dozer.DozerBeanMapper.initMappings(DozerBeanMapper.java:327)
    at org.dozer.DozerBeanMapper.getMappingProcessor(DozerBeanMapper.java:192)
    at org.dozer.DozerBeanMapper.map(DozerBeanMapper.java:127)
    at com.mirth.commons.objectmapping.Mapper.map(Mapper.java:47)

What's the best way to handle these? Should we check if the thread has been interrupted in our map method and throw an exception if so? Something like this?
public <I, O> void map(I source, O destination) throws MappingException {
    if (source == null) {
        return;
    }
    mapper.map(source, destination);

    if (Thread.currentThread().isInterrupted()) {
        throw new RuntimeException("Dozer was interrupted, canceling request");
    }
}

https://docs.oracle.com/javase/8/docs/api/java/lang/InterruptedException.html

Closing as 'initMappings' code path doesnt exist anymore. If you still have problem with latest version 6.4.1, please open a new ticket with info.


Refactor read and write functions for new handlers

In this PR, our goal is to refactor code that is reusable between webhook handlers. We can reuse the code that is needed to read the incoming request, as well as provided the required responses, especially for errors.

/mutate
/mutate/sa
/mutate/ns (coming soon!)

Specifically, we are going to be adding another handler for new namespaces. We want to make sure everything is working as intended before hand. Without refactoring we would have to duplicate code between handlers up to 3x.

/assign

I have signed the CLA - good to go!


YARN-11380. Fix hadoop-yarn-api module Java Doc Errors.

JIRA: YARN-11380. Fix hadoop-yarn-api module Java Doc Errors.
When finishing YARN-11373, ps(#5146) has java-doc compilation errors, I will fix all java-doc compilation errors of hadoop-yarn-api module. I will pay attention to the java doc compilation of jdk8 & jdk11 at the same time.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc-no-fork (default-cli) on project hadoop-yarn-api: An error has occurred in Javadoc report generation:
[ERROR] Exit code: 1 - javadoc: warning - You have specified the HTML version as HTML 4.01 by using the -html4 option.
[ERROR] The default is currently HTML5 and the support for HTML 4.01 will be removed
[ERROR] in a future release. To suppress this warning, please ensure that any HTML constructs
[ERROR] in your comments are valid in HTML5, and remove the -html4 option.
[ERROR] /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-5146/ubuntu-focal/src/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/ApplicationBaseProtocol.java:97: warning: no description for @throws
[ERROR]    * @throws YarnException
[ERROR]      ^
[ERROR] /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-5146/ubuntu-focal/src/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/ApplicationBaseProtocol.java:98: warning: no description for @throws
[ERROR]    * @throws IOException
[ERROR]      ^
[ERROR] /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-5146/ubuntu-focal/src/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/ApplicationBaseProtocol.java:129: warning: no description for @throws
[ERROR]    * @throws YarnException
[ERROR]      ^
[ERROR] /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-5146/ubuntu-focal/src/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/api/ApplicationBaseProtocol.java:130: warning: no description for @throws
[ERROR]    * @throws IOException

@ayushtkn Can you help review this PR? Thank you very much!

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 35s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m 43s

trunk passed

+1 :green_heart:
compile
1m  1s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
0m 51s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 43s

trunk passed

+1 :green_heart:
mvnsite
1m  1s

trunk passed

-1 :x:
javadoc
0m 59s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-yarn-api in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 44s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
2m 20s

trunk passed

+1 :green_heart:
shadedclient
23m 10s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 39s

the patch passed

+1 :green_heart:
compile
0m 46s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
0m 46s

the patch passed

+1 :green_heart:
compile
0m 42s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
0m 42s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 20s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api: The patch generated 0 new + 133 unchanged - 19 fixed = 133 total (was 152)

+1 :green_heart:
mvnsite
0m 42s

the patch passed

-1 :x:
javadoc
0m 33s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-yarn-api in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 30s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08 with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08 generated 0 new + 0 unchanged - 146 fixed = 0 total (was 146)

+1 :green_heart:
spotbugs
1m 59s

the patch passed

+1 :green_heart:
shadedclient
23m  3s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m  7s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

103m 26s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux fcbe6bd5fa7d 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 39a5c9fb0c4171ade6ec822ed2a72d30ef8a54b1

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/1/testReport/

Max. process+thread count
563 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

The Jdk-11 one is still failing
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/1/artifact/out/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt

The Jdk-11 one is still failing
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/1/artifact/out/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt

Thank you very much for reviewing the code! I will fix it.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 35s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
39m 33s

trunk passed

+1 :green_heart:
compile
1m  3s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
0m 53s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 51s

trunk passed

+1 :green_heart:
mvnsite
0m 57s

trunk passed

-1 :x:
javadoc
0m 58s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-yarn-api in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 44s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
2m 15s

trunk passed

+1 :green_heart:
shadedclient
21m 42s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 43s

the patch passed

+1 :green_heart:
compile
0m 48s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
0m 48s

the patch passed

+1 :green_heart:
compile
0m 39s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
0m 39s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 22s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api: The patch generated 0 new + 133 unchanged - 26 fixed = 133 total (was 159)

+1 :green_heart:
mvnsite
0m 43s

the patch passed

-1 :x:
javadoc
0m 35s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-yarn-api in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 36s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08 with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08 generated 0 new + 0 unchanged - 146 fixed = 0 total (was 146)

+1 :green_heart:
spotbugs
1m 57s

the patch passed

+1 :green_heart:
shadedclient
21m 27s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m  2s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

98m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 58baf41df37e 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f1a136b5ef1cdcad3760c50bdbba3802fb4e63af

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/2/testReport/

Max. process+thread count
565 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

The following error is remaining: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/2/artifact/out/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
[ERROR] /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-5152/ubuntu-focal/src/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/factory/providers/package-info.java:18: error: unknown tag: InterfaceAudience.Private
[ERROR] @InterfaceAudience.Private
[ERROR] ^

Would you fix it?

The following error is remaining: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/2/artifact/out/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
[ERROR] /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-5152/ubuntu-focal/src/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/factory/providers/package-info.java:18: error: unknown tag: InterfaceAudience.Private
[ERROR] @InterfaceAudience.Private
[ERROR] ^

Would you fix it?

Thank you very much for your help reviewing the code, I will fix this problem.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
38m 32s

trunk passed

+1 :green_heart:
compile
0m 57s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
0m 52s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 40s

trunk passed

+1 :green_heart:
mvnsite
0m 57s

trunk passed

-1 :x:
javadoc
0m 57s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-yarn-api in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 51s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
2m 13s

trunk passed

+1 :green_heart:
shadedclient
21m 47s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 42s

the patch passed

+1 :green_heart:
compile
0m 46s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
0m 46s

the patch passed

+1 :green_heart:
compile
0m 44s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
0m 44s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 20s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api: The patch generated 0 new + 133 unchanged - 27 fixed = 133 total (was 160)

+1 :green_heart:
mvnsite
0m 43s

the patch passed

+1 :green_heart:
javadoc
0m 35s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 generated 0 new + 0 unchanged - 107 fixed = 0 total (was 107)

+1 :green_heart:
javadoc
0m 36s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08 with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08 generated 0 new + 0 unchanged - 146 fixed = 0 total (was 146)

+1 :green_heart:
spotbugs
2m  6s

the patch passed

+1 :green_heart:
shadedclient
21m 49s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m  8s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

98m 16s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux dfda7194caec 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 93c628570fa118cde0386e352a94a320ddde1bd2

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/3/testReport/

Max. process+thread count
679 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@ayushtkn @aajisaka Can you help to review the code again? Thank you very much! I have fixed the java doc problem of hadoop-yarn-api module.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 46s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
40m 11s

trunk passed

+1 :green_heart:
compile
0m 54s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
0m 49s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 41s

trunk passed

+1 :green_heart:
mvnsite
1m  1s

trunk passed

-1 :x:
javadoc
0m 55s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-yarn-api in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
2m 11s

trunk passed

+1 :green_heart:
shadedclient
22m 18s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 43s

the patch passed

+1 :green_heart:
compile
0m 45s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
0m 45s

the patch passed

+1 :green_heart:
compile
0m 40s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
0m 40s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 22s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api: The patch generated 0 new + 141 unchanged - 19 fixed = 141 total (was 160)

+1 :green_heart:
mvnsite
0m 42s

the patch passed

-1 :x:
javadoc
0m 39s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-yarn-api in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 33s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08 with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08 generated 0 new + 0 unchanged - 146 fixed = 0 total (was 146)

+1 :green_heart:
spotbugs
1m 59s

the patch passed

+1 :green_heart:
shadedclient
21m 16s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m  1s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
asflicense
0m 48s

The patch does not generate ASF License warnings.

99m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 10f81b9059fe 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0cd27fa13de1fb35122e5c3845cff855b9989b5b

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/4/testReport/

Max. process+thread count
619 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 35s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
38m 35s

trunk passed

+1 :green_heart:
compile
0m 59s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
0m 51s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
0m 41s

trunk passed

+1 :green_heart:
mvnsite
1m  6s

trunk passed

-1 :x:
javadoc
0m 56s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-yarn-api in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
0m 53s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
2m 13s

trunk passed

+1 :green_heart:
shadedclient
21m 53s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 40s

the patch passed

+1 :green_heart:
compile
0m 51s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
0m 51s

the patch passed

+1 :green_heart:
compile
0m 39s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
0m 39s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 21s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api: The patch generated 0 new + 133 unchanged - 27 fixed = 133 total (was 160)

+1 :green_heart:
mvnsite
0m 43s

the patch passed

+1 :green_heart:
javadoc
0m 36s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 generated 0 new + 0 unchanged - 107 fixed = 0 total (was 107)

+1 :green_heart:
javadoc
0m 31s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08 with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08 generated 0 new + 0 unchanged - 146 fixed = 0 total (was 146)

+1 :green_heart:
spotbugs
1m 57s

the patch passed

+1 :green_heart:
shadedclient
21m 37s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m  9s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

98m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 6c865aec7045 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b39efd703b2a93fe0bc113837df22668c455b2eb

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/5/testReport/

Max. process+thread count
656 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5152/5/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@ayushtkn Can you help to review this PR again? Thank you very much!

@ayushtkn @aajisaka Can you help to review this PR again? Thank you very much!

@ayushtkn @aajisaka Can you help to review this PR again? Thank you very much!

@ayushtkn @aajisaka Can you help to review this PR again? Thank you very much!


enable glob patterns on include

Thanks! This looks good. I think we should support globs on all (or most) the paths in this file (sources, and artifact come to mind) before the next release, but we can do that in different PRs.
Would you mind adding this to the end of the Include comment (before the type: ... line) in config/meta.go:
"This field supports glob patterns."

i was done half way done already, I have tested it better know. Seems to be OK for all the things you suggested

Thanks!
I refactored a bit to use a PathGlobs type. TransformConfig is a bit broken, I'll have to fix it tomorrow


added code for assignments 1 and 2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Added code for both assignment 1 and assignment 2
What did you learn from the changes you have made?
Assignment 1 - A simple image classifier using custom CNN models
Assignment 2 - using more complex CNNs for Text generation.
it's just the usual classification/regression problem with Neural nets instead of regression models
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
using ResNet/AlexNet for image classification and LLMs for text generation is a viable alternative approach
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
getting Tensorflow to run on the GPU was the worst part of this assignment. I had to install Ubuntu on a 2nd drive for it.
I am personally against using google collab so I had to get it to run locally.
How were these changes tested?
A reference to a related issue in your repository (if applicable)
Checklist

[X ] I can confirm that my changes are working as intended

Reviewed and marked as completed


Error inserting images with Django 1.11, no problems with 1.10

I tried upgrading to Django 1.11.2, but Summernote gives me this error when I try to insert an image:
Got an error uploading an image: AttributeError at /summernote/upload_attachment/
This QueryDict instance is immutable

Here's the traceback:
Internal Server Error: /summernote/upload_attachment/
Traceback (most recent call last):
  File "/home/couture/Developer/hackerspace/lib/python3.4/site-packages/django/core/handlers/exception.py", line 41, in inner
    response = get_response(request)
  File "/home/couture/Developer/hackerspace/lib/python3.4/site-packages/django/core/handlers/base.py", line 249, in _legacy_get_response
    response = self._get_response(request)
  File "/home/couture/Developer/hackerspace/lib/python3.4/site-packages/django/core/handlers/base.py", line 187, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "/home/couture/Developer/hackerspace/lib/python3.4/site-packages/django/core/handlers/base.py", line 185, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/couture/Developer/hackerspace/lib/python3.4/site-packages/django_summernote/views.py", line 59, in upload_attachment
    request.POST.pop("csrfmiddlewaretoken", None)
  File "/home/couture/Developer/hackerspace/lib/python3.4/site-packages/django/http/request.py", line 473, in pop
    self._assert_mutable()
  File "/home/couture/Developer/hackerspace/lib/python3.4/site-packages/django/http/request.py", line 431, in _assert_mutable
    raise AttributeError("This QueryDict instance is immutable")
AttributeError: This QueryDict instance is immutable
[04/Jun/2017 21:38:18] "POST /summernote/upload_attachment/ HTTP/1.1" 500 19091

This was fixed by https://github.com/summernote/django-summernote/commit/d887f1c5ad1f611e300f1868485efba9c2b34488. Please use the latest version.
Ref: https://github.com/summernote/django-summernote/issues/183


[1.0.0-beta3] Url Parameters are getting decoded once per nesting

Using React-Router 1.0.0-beta3
Let's say I have an URL like point/:some_token
Where some_token is encoded in base64, so it may contain a + sign. I encoded it using encodeURIComponent and got something like aaa%2Bbbb.
When I hit the url I can see from a console log that https://github.com/rackt/react-router/blob/master/modules/URLUtils.js#L118-L121 is getting hit twice with the URL. First time where v equals the whole url /point/aaa%2Bbbb (which gives /point/aaa+bbb, and then a second time with only the token but with the + sign already decoded once aaa+bbb => aaa bbb.  Which is no longer the valid token anymore.

My routes look like
<Router>
  <Route component={ApplicationWrapper}>
    <Route path="point/:some_token" component={MyComponent} />
  </Route>
</Router>

If I put the route as top level (no wrapper), it works eg:
<Router>
  <Route path="point/:some_token" component={MyComponent} />
</Router>

This is still an issue. My current workaround is to use a query param.

+1

added a test case that passes on master: 13f948b29d6fc1a0811e0ae6932880130cfd7c85

I should've have been clearer! It has to be nested route, I'll put up a PR with a failing test


Fix SetupGripper Bug

SetupGripper tries to destroy original prefab assets and crashes execution in the editor mode causing the UI to not spawn.

Resolved here


Add test for illegal path in match stage

For #2919.
Description

Readiness checklist

[ ] I added/updated unit tests.
[ ] I added/updated integration/compatibility tests.
[ ] I added/updated comments and checked rendering.
[ ] I made spot refactorings.
[ ] I updated user documentation.
[ ] I ran task all, and it passed.
[ ] I ensured that PR title is good enough for the changelog.
[ ] (for maintainers only) I set Reviewers (@FerretDB/core), Labels, Project and project's Sprint fields.
[ ] I marked all done items in this checklist.

#4341


Ability to set port on which the runner runs

The Mock runner seems to run on port 8080 by default. This is an issue when we want to run multiple SOAP UI projects. Is there any environmental variable similar to MOCK_SERVICE where we can set the port the soap ui mock service will run?
In my SOAP UI project, I have mentioned a different port (8200), yet it runs it on 8080.

You should use the -p option for this.
E.g. if I do the following (see the README.md):
docker pull fbascheper/soapui-mockservice-runner
mkdir -p $HOME/soapui-test-project
cd $HOME/soapui-test-project
wget https://raw.githubusercontent.com/fbascheper/SoapUI-MockService-Docker-image/master/soapui-prj/default-soapui-project.xml

docker run -P -it --rm \
        -p 30080:8080 \
        -v "$HOME/soapui-test-project:/home/soapui/soapui-prj/" \
        -e MOCK_SERVICE_NAME="BLZ-SOAP11-MockService" \
        -e PROJECT=/home/soapui/soapui-prj/default-soapui-project.xml \
        --privileged \
         fbascheper/soapui-mockservice-runner:latest

And open localhost:30080 I see a sample wsdl.


bump benchalerts version

Bumps benchalerts dependency to include

https://github.com/conbench/conbench/pull/1404

This should make this kind of notification make more sense by enumerating each benchmark name.

Do you have a preview of what the new updated notification will look like?

Yes, here's an expected (Velox!) notification from one of the end-to-end tests we run: https://github.com/conbench/conbench/blob/534762befe9429ae1080e42056e9c681afab9801/benchalerts/tests/integration_tests/test_alert_pipeline.py#L90-L97


JSDoc @this/@lends/@namespace tags are ignored inside Object

Issue Type: Bug
MyElement.d.ts
declare class MyElement {
    constructor(target: Element);
    target: Element
}

MyElement.js
@this on globally defined function works as expected, Ctrl+Space shows the correct type of target - Element!

@this before function in the object doesn't take into account!

@lends before the object itself is also not taken into account!

the same with @namespace

I couldn't find the way to point the correct "this" type for function in objects.
VS Code version: Code 1.42.0 (ae08d5460b5a45169385ff3fd44208f431992451, 2020-02-06T10:51:33.119Z)
OS version: Darwin x64 19.3.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 x 3600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
32.00GB (7.02GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Our JavaScript IntelliSense  is powered by the TypeScript project. Please file a bug report/feature request upstream


Include interface and change lws service timeout

Codecov Report

Merging #110 into parodus_lws will increase coverage by <.01%.
The diff coverage is 100%.

@@               Coverage Diff               @@
##           parodus_lws     #110      +/-   ##
===============================================
+ Coverage         89.4%   89.41%   +<.01%
===============================================
  Files               30       30
  Lines             2313     2314       +1
  Branches           145      145
===============================================
+ Hits              2068     2069       +1
  Misses             107      107
  Partials           138      138

Impacted Files
Coverage Δ

src/conn_interface.c
51.72% <100%> (ø)
:arrow_up:

src/connection.c
83.57% <100%> (+0.11%)
:arrow_up:

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 65f4b38...bc34387. Read the comment docs.


Migrate from ciscoconfparse to ciscoconfparse2 or fix the ciscoconfparse version

Description
When running the script, each time we get following logs:
2024-02-11 11:17:01.938 | INFO     | ciscoconfparse.ciscoconfparse:__init__:701 - As of version 1.9.17 and later, `ignore_blank_lines=True` is only honored when `factory=True`
2024-02-11 11:17:01.938 | INFO     | ciscoconfparse.ciscoconfparse:__init__:701 - As of version 1.9.17 and later, `ignore_blank_lines=True` is only honored when `factory=True`

When trying to see why this happens I've seen that ciscoconfparse is no longer being developed and ciscoconfparse2 is the replacement. Could we please force ciscoconfparse version to be 1.9.16 in short term and in long term migrate to ciscoconfparse2?

Removed warning in #462.
We need to move to ciscoconfparse2 soon. Let's track progress here.


Output column not created when input dataset is empty

Describe the bug
We have been working on text data of multiple languages involved. One of the tasks is to translate text in French into text in English. Language detection plugin helps identify languages of the text which are mainly in French and English. Based on that, we set apart French text and pass them through translation plugin. After translation recipe, we have a join recipe that is dependent on
to pull in the output column in output dataset generated by the translation recipe, for example, we have an input column "text" to the translation recipe and we expect to see an output column i.e. "text_en". It works fine when we have records in input dataset but it seems it does not create the output column when the input dataset is empty. In our flow, we are to process incremental records every week and we are fine by having no records in French and continuing the flow. The issue arises because without output column being created for empty input dataset, the join recipe fails and flow execution stops.
To Reproduce
Steps to reproduce the behavior:

Try this plugin with empty dataset
Select input column and target language.
Check output dataset if output column is created.

Expected behavior
I suggest that it should ideally create the output column in output dataset in case of empty dataset is fed to the recipe. Schema of output dataset should not change since it has an impact in downstream recipe like I mentioned before.
However, I placed a workaround solution meanwhile. With a python code recipe, I checked if the desired column is created in the output dataset. If not, I introduced an empty column i.e. "text_en"  in output dataset that participates in the join recipe.
If you could add this feature in this plugin, it would be great.
You may please advise me in case of any misunderstanding.
Screenshots
NA
Additional context
Add any other context about the problem here.

DSS version 10

Describe the bug We have been working on text data of multiple languages involved. One of the tasks is to translate text in French into text in English. Language detection plugin helps identify languages of the text which are mainly in French and English. Based on that, we set apart French text and pass them through translation plugin. After translation recipe, we have a join recipe that is dependent on to pull in the output column in output dataset generated by the translation recipe, for example, we have an input column "text" to the translation recipe and we expect to see an output column i.e. "text_en". It works fine when we have records in input dataset but it seems it does not create the output column when the input dataset is empty. In our flow, we are to process incremental records every week and we are fine by having no records in French and continuing the flow. The issue arises because without output column being created for empty input dataset, the join recipe fails and flow execution stops.
To Reproduce Steps to reproduce the behavior:

Try this plugin with empty dataset
Select input column and target language.
Check output dataset if output column is created.

Expected behavior I suggest that it should ideally create the output column in output dataset in case of empty dataset is fed to the recipe. Schema of output dataset should not change since it has an impact in downstream recipe like I mentioned before.
However, I placed a workaround solution meanwhile. With a python code recipe, I checked if the desired column is created in the output dataset. If not, I introduced an empty column i.e. "text_en" in output dataset that participates in the join recipe.
If you could add this feature in this plugin, it would be great. You may please advise me in case of any misunderstanding.
Screenshots NA
Additional context Add any other context about the problem here.

DSS version 10

Hey, I think this is indeed expected behavior of the plugin, but I agree that it'd be nicer to output an empty column instead.
Do you want to open a PR here to fix it? Else I will try tackle it in the coming days 👍

Can you ch

Describe the bug We have been working on text data of multiple languages involved. One of the tasks is to translate text in French into text in English. Language detection plugin helps identify languages of the text which are mainly in French and English. Based on that, we set apart French text and pass them through translation plugin. After translation recipe, we have a join recipe that is dependent on to pull in the output column in output dataset generated by the translation recipe, for example, we have an input column "text" to the translation recipe and we expect to see an output column i.e. "text_en". It works fine when we have records in input dataset but it seems it does not create the output column when the input dataset is empty. In our flow, we are to process incremental records every week and we are fine by having no records in French and continuing the flow. The issue arises because without output column being created for empty input dataset, the join recipe fails and flow execution stops.
To Reproduce Steps to reproduce the behavior:

Try this plugin with empty dataset
Select input column and target language.
Check output dataset if output column is created.

Expected behavior I suggest that it should ideally create the output column in output dataset in case of empty dataset is fed to the recipe. Schema of output dataset should not change since it has an impact in downstream recipe like I mentioned before.
However, I placed a workaround solution meanwhile. With a python code recipe, I checked if the desired column is created in the output dataset. If not, I introduced an empty column i.e. "text_en" in output dataset that participates in the join recipe.
If you could add this feature in this plugin, it would be great. You may please advise me in case of any misunderstanding.
Screenshots NA
Additional context Add any other context about the problem here.

DSS version 10

Hey, I think this is indeed expected behavior of the plugin, but I agree that it'd be nicer to output an empty column instead. Do you want to open a PR here to fix it? Else I will try tackle it in the coming days 👍

Thank you very much for looking into this. I am working within a restricted environment and have hardly any chance to test it internally before opening a PR. Thus, please work on it when you have a moment.

Can you check if https://github.com/dataiku/dss-plugin-nlp-amazon-translation/pull/6 works for you?


Test to check JMX metrics

Test to see whether JMX changes as you'd expect it to after running C*.

I haven't run this yet, but it looks good.

Find some other metrics for decrement, equal, and zero so we're sure the other tests work too, then looks good to merge to me.

Please check [CASSANDRA-9448] (https://issues.apache.org/jira/browse/CASSANDRA-9448), some of the metrics names will change in 3.0.

+1! Great job! :+1: :fireworks:


Automated cherry pick of #4362: fix: 更正腾讯云磁盘创建时间

Cherry pick of #4362 on release/2.12.
#4362: fix: 更正腾讯云磁盘创建时间

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@fd2843b). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             release/2.12   #4365   +/-   ##
==============================================
  Coverage                ?   6.84%
==============================================
  Files                   ?     501
  Lines                   ?   85284
  Branches                ?       0
==============================================
  Hits                    ?    5834
  Misses                  ?   78955
  Partials                ?     495

Flag
Coverage Δ

#aFlag
6.84% <ø> (?)

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 fd2843b...09cb1a5. Read the comment docs.

/approve
/lgtm


[NT-0] refac!: Refactor Authentication results

Some result types have been refactored to reduce the number of public result types, and to make the return value type more apparent.
BREAKING CHANGES:

UserSystem::LogOut now takes NullResultCallback instead of LogoutResultCallback. LogoutResultCallback is now private.
UserSystem::GetAgoraUserToken now takes StringResultCallback instead of UserTokenResultCallback. UserTokenResultCallback is now private.
UserSystem::GetCustomerPortalUrl now takes StringResultCallback instead of CustomerPortalUrlResultCallback. CustomerPortalUrlResultCallback is now private.
UserSystem::GetCheckoutSessionUrl now takes StringResultCallback instead of CheckoutSessionUrlResultCallback. CheckoutSessionUrlResultCallback is now private.
UserSystem::Ping now takes a NullResultCallback instead of a PingResponseReceivedCallback. PingResponseReceivedCallback has been removed.
LoginTokenReceived has been renamed LoginTokenInfoResult.
NewLoginTokenReceivedCallback has been renamed LoginTokenInfoResultCallback,
Non-const versions of result types' GetX members have been removed.

For the reviewer

[ ] If required, are the changes covered by appropriate tests?
[ ] Are any public-facing API changes well documented?
[ ] Is the code easily readable and extensible and/or follow existing conventions?

NOTE: This PR deals only with types in Authentication.h. Further PRs will be made to address refactoring types in other headers used by UserSystem.

I think the WASM check is failing here


geswarp, aerodermectasia (logical-conflict)

This pull request was generated by the 'mq' tool

/trunk merge


Structure conversion error

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Include the input file that goverter has problems with, and describe the steps
you took to trigger the bug
Expected behavior
A clear and concise description of what you expected to happen.
time.go
import "github.com/golang-module/carbon/v2"

type In struct {
	CreatedAt  carbon.DateTime
	ReleasedAt *carbon.DateTime
}

type Out struct {
	CreatedAt  carbon.DateTime
	ReleasedAt *carbon.DateTime
}

// goverter:converter
type Converter interface {
	ModelToDomain(source *In) (*Out, error)
}

If the unexported field is ignored, panic: runtime error: invalid memory address or nil pointer dereference

go run github.com/jmattheis/goverter/cmd/goverter --ignoreUnexportedFields --wrapErrors ./time.go

If unexported fields are not ignored, an error field mismatch will be reported

go run github.com/jmattheis/goverter/cmd/goverter  --wrapErrors ./time.go

Goverter doesn't know how to deeply clone carbon.DateTime so, you've to manually define the method. As far as I can see, carbon.DateTime is immutable and every call method call on it will return a new instance. Due to this, you can just pass the object through without doing any deep cloning, because you don't have to clone a value that is immutable.
// goverter:converter
// goverter:extend CloneDateTime
type Converter interface {
	Convert(*In) *Out
}

type In struct {
	CreatedAt  carbon.DateTime
	ReleasedAt *carbon.DateTime
}

type Out struct {
	CreatedAt  carbon.DateTime
	ReleasedAt *carbon.DateTime
}

func CloneDateTime(source carbon.DateTime) carbon.DateTime {
	return source
}

Thinks


keyboard access to filters and slicers

Visuals in the publicly shared web version of a PowerBI chart have an upside down pyramid icon that opens "Filters and slicers affecting this visual".  This popup lists all the slicers and filters affecting the visual.  There is no keyboard path listed for opening this.  Tab navigation in the visual does not focus it.

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

ID: 8df72ff6-206a-243a-a84a-0f6ac418a9b2
Version Independent ID: e6d1ac0d-3785-cb59-da9c-7dcac2876d2d
Content: Keyboard shortcuts in Power BI Desktop - Power BI
Content Source: powerbi-docs/create-reports/desktop-accessibility-keyboard-shortcuts.md
Service: powerbi
Sub-service: pbi-reports-dashboards
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @anmeeks-vt-edu. This issue has been assigned to the doc author for review.

Thanks for your comments. Looks like this is product feedback, rather than documentation feedback – you can submit product feedback or feature ideas by going to https://ideas.powerbi.com. You can also engage with the Power BI engineering team by being active in the Power BI Community, found at https://community.powerbi.com.


Chromium docs 3883038

Docs Build status updates of commit 1965210:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/progressive-web-apps.md
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/storage/images/application-storage-session-storage-domain-key-value-delete-selected.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/storage/images/application-storage-session-storage-domain-key-value-edit.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/storage/images/application-storage-session-storage-domain-key-value-new.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/storage/images/application-storage-session-storage-domain-key-value-selected.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/storage/images/application-storage-session-storage-domain.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/storage/images/application-storage-session-storage.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/storage/images/clear-icon.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/storage/images/console-domain-selection.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/storage/images/console-session-storage-keys.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/storage/images/delete-icon.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/storage/sessionstorage.md
:white_check_mark:Succeeded

microsoft-edge/toc.md
:white_check_mark:Succeeded

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


Grouping of extensions.

As it currently stands, the installed extensions tab is pretty disorganized, and is a pain sometimes to navigate and find the particular extension you wish to add, remove or disable, particularly if there are a bunch of related extensions, but their names are far off from each other.
It would be pretty neat if you could group together installed extensions into related categories such as language specific categories or theme related ones to make navigation easier, or even cutom ones that can by added to settings sync to make it easier when on ewants to switch which language they're using without having every other entension too.

/duplicate


Remove misleading warning.

The warning is misleading and causes users to run simulation with more than 10x too many resources. Since the magic cutoff is neither a lower bound, nor an upper bound (by many orders of magnitude), we should simply not print anything.

There's two version, the milder make it an info; and the better option just don't say anything.6

Thanks. I will close in favor of #67


Modbus integration post, needs author details adding

Description
Article on best practice for integrating modbus with Node-RED. We need to resolve how we credit the author as this was written by a non-employe of FlowForge

FYI @robmarcer https://github.com/flowforge/website/pull/706 is now merged. If you rebase this branch, then you'll be able to include guests as an author by adding their respective json into the /src/_data/guests/ folder

@robmarcer shoudl this PR be closed?

Yes, I created a new PR to avoid rebasing this work.


[eSteem mobile v2 iOS] After submiting post not displays on user profile page

Describe the bug
After successful submission of my last post using eSteem mobile v2 iOS release visited my profile page where the new post was unavailable. I tried to refresh the page but no avail and finally close the app and re-launch it then post displays properly in the profile page.
To Reproduce
Steps to reproduce the behavior:

Create a new post using eSteem mobile v2 ios release
Click on publish.
Visit your profile page.
You can see the error.
Expected behavior
I had expected that just after submitting my new post should appears on my profile page without any delay.

Screenshots or Video
Smartphone (please complete the following information):

Device: [ iPhone6]
OS: [e.g. iOS12]
Version []

Additional context
Add any other context about the problem here.

Thanx for feedback. Fixed.


dpi setting when exporting fig

How to set 'dpi' when exporting the fig? Hope this function could be considered.

Use the -r and/or -m parameters


imprv: guest user icon delete

Task
https://redmine.weseek.co.jp/issues/141838
┗https://redmine.weseek.co.jp/issues/145332


passing some data

how to pass the data from one step to next step?

Hi @tank777,
Please see #15 and #81

any example?

I think writing a section about that in Readme would prevent devs asking the same question over and over again.

@tank777 @arslancharyev31 I've added a sample in #98. Please let me know if this is sufficient in your opinion.

thank you

The sample is now available on the master branch.


Support for extracting hours/minutes/seconds/etc. from Time32/Time64 type in temporal kernels

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

In temporal kernels, only hour currently supports Time32/Time64 types:
https://github.com/apache/arrow-rs/blob/c57857031fb39559924df56e1c8e5f60a1a6e69a/arrow-arith/src/temporal.rs#L187-L216
Note this seems to only work for hour and not hour_dyn:
https://github.com/apache/arrow-rs/blob/c57857031fb39559924df56e1c8e5f60a1a6e69a/arrow-arith/src/temporal.rs#L178-L183
Describe the solution you'd like

Be able to call the following for Time32/Time64 types:

hour
minute
second
millisecond
microsecond
nanosecond

Describe alternatives you've considered

Additional context

label_issue.py automatically added labels {'arrow'} from #5337


Affinities can not be removed when editing a deployment

Steps to reproduce

Create a deployment with a node affinity

Next edit the deployment and remove the node affinity

What should happen
The node affinity gets removed from the deployment
What is happening
The node affinity remains at the deployment. This happens regardless if you just change the radio button back to "Run pods on any available node", or if you remove the rule beforehand.

On which rancher version can I reproduce this bug?
I tested the fix on v2.5-head (4115dee), works fine.
Test on master-head blocked on https://github.com/rancher/rancher/issues/31964

This is reproducible for me in 2.5.7.

Closing based on the validations done on 2.5-head here


How do I open the sav file and parse it？

How do I open the sav file and parse it？

(This project is outdated and I don't know if it still works with the latest Stardew Valley versions.)
OpenGameWindow is called from MainWindow.xaml.cs which is used to select a game save to open.
Parsing of the save file is in the OpenSavedGame method.


Flexible grouping of Application form fields

Is your feature request related to a problem? Please describe.
The current grouping feature assumes fields after Group fields block are part of the next group say 2. But some fields that appear after the grouper fields should always display on the page. Currently, if a user selects the second option of group field block, all fields after it are hidden.
Is your feature request related to an existing functionality? Please describe.
This is an addition to #1064
Priority

High (keeping you from completing day-to-day tasks)

Affected roles

Staff

Ideal deadline
Asap

@danblah @fourthletter  This is ready for test on test.
The group field now also have and end version. All fields between the two are part of that group.  This allows you to have multiple groups with optional non grouped fields in between.
(Nested groups are not possible but if needed @Parbhat has a way to implement that but it takes time.)

Created issue #1259 for the alternative implement using stream block for Q3.

Thanks for the details @frjo. One point to add is: Fields within group should be optional to successfully submit the form if user chooses second choice of group field.

Is this on test or prod?

Testing on test.


test cases for install-apps handle invalid appsDirectory values

@cthigh From what i can tell the integration tests are not running on my not configured case. Can you spot anything off in the pom?

@dnwarnock All the current changes look good. For the notconfigured case, you are missing information in the pom for creating the liberty server and running the failsafe tests. I remember they were originally there when we went through and creates the liberty-assembly test project.  For the war packaging type, you still needed the plugin configuration for the liberty-maven-plugin executions and for the failsafe plugin.  We could delete these from the liberty-assembly project because they were automatically bound. I didn't catch that you removed them from the non configured case.

@cthigh g2g?


[Chef manage global objects] organizations list & detail API

User story

Chef server global object organizations list API. https://docs.chef.io/server/api_chef_server/#get-1

Response
{
  "org_name1": https://url/for/org_name1",
  "org_name2": https://url/for/org_name2"
}

Chef server global object organization detail API. https://docs.chef.io/server/api_chef_server/#get-2

{
  "name": "chef",
  "full_name": "Chef Software, Inc.",
  "guid": "f980d1asdfda0331235s00ff36862"
     ...
}

We will handle it differently.


Release Google.Cloud.Speech.V1 version 2.5.0

Changes in this release:

Commit 09c3f7d: feat: add output_config request field

Created release for Google.Cloud.Speech.V1-2.5.0


Userdata is unsafe

Right now hlua checks type safety by writing the TypeId of the userdata in the index __typeid of its metatable.
However this could be easily modified by the library user or even maybe by a Lua script.
Of course it would be very stupid for a user to modify the value in __typeid. If all actors cooperate, then there's no unsafety. But safety is all or nothing. If for example you write a Lua REPL with hlua and take user input, then there is a security leak here.

One solution would be to never push a T alone, but always a (TypeId, T) instead.
Hlua's API would transparently add or remove the TypeId whenever you push or load a userdata.
Since reading a userdata expects a TypeId, this idea can only work if the user has no way of writing a userdata without that TypeId.


Support multiple package indexes

This issue was asked by @jeromecoutant.
Some vendors might have their own package index. Ex: Let's name https://www.keil.com/pack/index.pidx as Keil.pidx. It contains all known public packs. But ST might have their own package index, let's say ST.pidx.
While Keil.pidx contains ARM.CMSIS and hundreds of other packs, it might not contain an ST-only pack e.g. STM.Pack. Whereas ST.pidx contains STM.Pack, it won't list ARM.CMSIS in it.

@jkrech after you suggestion of using vidx2pidx to merge those 2 into a single index, it got me thinking about updating a list of all packs. Given that the merged pidx will only contain a single URL tag, which URL should that point to?

All vendors must maintain vendor.pidx files that only list packs from one vendor.
A maintainer of an index.pidx file need to maintain a provider.vidx file
The expectation is that both the provider.vidx and the resulting index.pidx are hosted at the same
Therefore the answer to your question is, that the   tag in the index.pidx is inherited from the vidx file that was used to generate the index.pidx.
I hope this makes sense?
Any consumer of an index.pidx file needs to be able to know which vendor's pidx files have been used to compile it.

Hi
My first thought was that, in CMSIS_PACK_ROOT, in .Web, instead of having only 1 index.pidx, there is Keil.pidx, STMicroelectronics.pidx, ARM.pidx, ....
Then when user is using cpackget pack add <vendor>.<name>, tool can get information in the correct vendor pidx file.

Hi Jerome,
I did understand your proposal but looking at it from an end user's perspective I don't want them being exposed to this. We should not present "fragmentation". At the same time we need to be transparent. I hope this is an acceptable compromise.

Please note if a tool does not find a valid  tag in the index.pidx I think there is simply no way for the tool to execute an update and should report this as an error.

@jeromecoutant and @chaws  are you happy to close this issue or specify what actions need to be taken?
e.g. @chaws do you need to raise an issue against vidx2pidx to derive the  tag content from the input vidx file? Which may also be an empty string.

@jkrech sorry for late answer on this issue.
But while I was building up an example for Jerome in order to merge such Keil.pidx and ST.pidx into a single index.pidx file using vidx2pidx I found a problem: the content of Keil.pidx (https://www.keil.com/pack/Keil.pidx) contains much smaller number of packs if compared to index.pidx (https://www.keil.com/pack/index.pidx). Is that expected? I can't use the latter in a vidx file because vidx2pidx uses the content of the Vendor tag in vidx file to build the URL of the pidx file.
So I think the solution here would be adding an ST tag such as:
<pidx vendor="ST" url="path/to/index/" />

Into <vindex> of https://www.keil.com/pack/Keil.vidx and then use vidx2pidx to generate a flat index.pidx file with ST packs int it as well. It would be ST's responsibility to maintain the file up-to-date against the original one in Keil.vidx.
If Keil.pidx contained the same contents of https://www.keil.com/pack/index.pidx, then ST would simply maintain their own vidx file pointing to Keil.pidx.

I'm closing down this issue. For now it will not be possible to have multiple indexes in cpackget.