ci: install package with yalc when linting real repository

This should get the transitive dependencies.

:tada: This PR is included in version 9.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Documents should have a note and link to contribute

We will add a note in an unobtrusive location on each document page to provide customers with a link to our contributing guide, so that they can get involved.

This will get handled by the system that builds the HTML from the markdown files.

Closing this. The links are now part of the chrome for docs.


(m)TLS replication is broken in 2.9.0

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
2.9.0
Minimal reproduce step
When upgrading Kvrocks from 2.8.0 to 2.9.0, we started to get SSL/TLS errors when trying to connect a slave to the master. No problem on replication without TLS.
 Rolling back the master to 2.8.0 and keeping the replica on 2.9.0 is working so it is definitely on the "server/master" part.
When both were on 2.9.0, using redis-cli on the slave instance to connect to the master was working with the certificates so they are fine:
No errors (on replica instance):
redis-cli -h kvrocks-master \
  -p 6379 \
   --tls \
   --cacert /ca/kvrocks/ca.crt \
   --cert /tls/kvrocks/tls.crt \
   --key /tls/kvrocks/tls.key

Errors (replica instance, see below):
kvrocks -c kvrocks.conf \
      --dir /var/lib/kvrocks \
      --pidfile /var/run/kvrocks/kvrocks.pid \
      --masterauth "xxx" \
      --slaveof "kvrocks-master 6379" \
      --tls-ca-cert-file /ca/kvrocks/ca.crt \
      --tls-key-file /tls/kvrocks/tls.key \
      --tls-cert-file /tls/kvrocks/tls.crt \
      --tls-replication yes \
      --bind <IP_ADDRESS>

What did you expect to see?
A working (m)TLS replication that either does psync or full synchronization
What did you see instead?
Server (MASTER) :

kvrocks I20240813 08:37:26.913834   121 cmd_replication.cc:60] Slave <IP_ADDRESS>:45098, listening port: 6379, announce ip: <IP_ADDRESS> asks for synchronization with next sequence: 1 replication id: not supported, and local sequence: 344837857
kvrocks E20240813 08:37:26.918999   121 redis_connection.cc:109] [connection] Going to remove the client: <IP_ADDRESS>:45098, while encounter error: Success, SSL Error: error:0A000126:SSL routines::unexpected eof while reading
kvrocks I20240813 08:37:26.986922   193 cmd_replication.cc:242] [replication] Succeed sending full data file info to <IP_ADDRESS>
kvrocks W20240813 08:37:27.038514   194 cmd_replication.cc:299] [replication] Fail to send file CURRENT to <IP_ADDRESS>, error: Success
kvrocks I20240813 08:37:37.086854   195 cmd_replication.cc:242] [replication] Succeed sending full data file info to <IP_ADDRESS>
kvrocks W20240813 08:37:37.127951   196 cmd_replication.cc:299] [replication] Fail to send file CURRENT to <IP_ADDRESS>, error: Success

Client (REPLICA) :

W20240813 08:00:12.653694    50 replication.cc:935] [fetch] Fail to fetch file 005813.sst, err: fetch file err: read sst file: failed to read from SSL connection: error:00000000:lib(0)::reason(0)
W20240813 08:00:12.655525    49 replication.cc:935] [fetch] Fail to fetch file 009665.sst, err: fetch file err: read sst file: failed to read from SSL connection: error:00000000:lib(0)::reason(0)
W20240813 08:00:12.660212    51 replication.cc:935] [fetch] Fail to fetch file 008792.sst, err: fetch file err: read sst file: failed to read from SSL connection: error:00000000:lib(0)::reason(0)
W20240813 08:00:12.661721    52 replication.cc:935] [fetch] Fail to fetch file 005736.sst, err: fetch file err: read sst file: failed to read from SSL connection: error:00000000:lib(0)::reason(0)

Anything Else?
Is it safe to downgrade to 2.8.0 on instances where I need (m)tls replication? Could it be due to the switch to Debian?
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Could it be due to the switch to Debian?

Have you tried to build kvrocks in your own environment and see if TLS replication works well?

Could it be due to the switch to Debian?

Have you tried to build kvrocks in your own environment and see if TLS replication works well?

We use Kvrocks in Kubernetes with the official Docker images

I tried with the unstable/nightly Docker tag for the master instance: I don't have the error. I then rollbacked to 2.9.0, the error is gone and does not reappear. Really weird.
I still have some running instances (on other clusters) where I didn't upgrade to nightly so the problem is still there, do you want me to run some checks/commands in order to get some ideas about what this is happening?

I built Kvrocks 2.9.0 with the Docker Alpine image from 2.8: no replication errors. The image is here: https://hub.docker.com/r/hivacruz/kvrocks-alpine/tags


Additonal test cases for backup NHG action

TE11.3 - case 3: tunnel viability triggers decap.
TE11.3 - case 4: resolution failure on new tunnels triggers decap in the backup NHG.

Pull Request Functional Test Report for #3135 / f7798432ac9de19a59774663fc9d0e1928319bb8
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

TE-11.3: Backup NHG: ActionsTE-11.31: Backup NHG: Actions with PBF
d05a176d
Log

Cisco 8000E

TE-11.3: Backup NHG: ActionsTE-11.31: Backup NHG: Actions with PBF
abed788b
Log

Cisco XRd

TE-11.3: Backup NHG: ActionsTE-11.31: Backup NHG: Actions with PBF
52f54abf
Log

Juniper ncPTX

TE-11.3: Backup NHG: ActionsTE-11.31: Backup NHG: Actions with PBF
b9947d19
Log

Nokia SR Linux

TE-11.3: Backup NHG: ActionsTE-11.31: Backup NHG: Actions with PBF
443eb0d3
Log

Openconfig Lemming

TE-11.3: Backup NHG: ActionsTE-11.31: Backup NHG: Actions with PBF
7e7fcc77
Log

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

TE-11.3: Backup NHG: ActionsTE-11.31: Backup NHG: Actions with PBF

Cisco 8808

TE-11.3: Backup NHG: ActionsTE-11.31: Backup NHG: Actions with PBF

Juniper PTX10008

TE-11.3: Backup NHG: ActionsTE-11.31: Backup NHG: Actions with PBF

Nokia 7250 IXR-10e

TE-11.3: Backup NHG: ActionsTE-11.31: Backup NHG: Actions with PBF

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls


Fix cluster.connectivity.proxy.noProxy template

What does this PR do?
Fix "cluster.connectivity.proxy.noProxy" template to correctly render values from specified template (a bug was introduced in https://github.com/giantswarm/cluster/pull/50).
What is the effect of this change to users?
NO_PROXY is correctly rendered.
Any background context you can provide?
https://github.com/giantswarm/cluster-aws/pull/479#discussion_r1455411843
Should this change be mentioned in the release notes?

[x] CHANGELOG.md has been updated (if it exists)

There is a rendering diff because I updated the test (dummy) template.


add events in calculator.js

What I DId✍🏽:
[ ] Implement click event handlers using the math logic from calculate.js and operate.js in my React component
[ ] Add events in calculator.js to make all calculator buttons work according to their functionality e.g. the - button (minus button) subtracts a given value

Revision:
[ ] Prop implemented in App.js


Hovering behaviour seems off in "add node" popup window

In the "add node" popup window, when you hover over a title (eg. Name) a hand icon is displayed, but no actions are linked to the title .. Hovering should only display the hand icon, when you can fire an action (eg. a hyperlink)

nice catch I'll make a PR tommorow

Closing since this was merged.


Discuss how to convert data pages

I have started to convert some of the easy parts of the data pages that I think we can continue to use.
Check them out @BGranberg and let's start to think about what to do with the tabbed content.


Maps ready not firing on app to foreground with cordova

As per example I set up my code, if the map renders, the first time the marker will be created. Then if you push the app into the background, and then launch back into the foreground, the map will refresh without creating the marker. Essentially, the ready call in the onCreated never gets called again. So the map refreshes without any of the ready information.
To get around this, I've put my ready function inside the helper, and it works as a workaround for now, however, the downside is you cant launch anything reactive from the ready function or in the helper at all, because obviously the map will just keep re rendering every time anything reactive changes.
Test this out on any device (cordova):
Template.map.onCreated(function () {
    GoogleMaps.ready('map', function(map){
        new google.maps.Marker({
            position: new google.maps.LatLng(47.617974, -122.321506),
            map: map.instance
        });
    });
});

Template.map.helpers({
    mapOptions: function() {
        return {
            center: new google.maps.LatLng(47.617974, -122.321506)
        }
    }
});

Hey @pmwisdom interesting bug there, what device (or devices?) are you seeing the bug on? I wouldn't have expected onCreated to not fire.

Devices that I test on are iPhone 4s, 5, 6, for apple, and I have a nexus 5 for android. All of them see that same issue. When you enter the app from the background ( app still running in background) and with the map previously rendered to the foreground, you can see the map flash quickly, and re render, like the helper is re-firing, but not the ready function. I tried putting the ready function in rendered as well, but it didn't seem to work any differently.

Can you confirm this same bug happens on the demo app?

I realise it's basically the same code that you've pasted above, though your mapOptions helper is missing the check on GoogleMaps.loaded()

Oops yeah, I did miss that, got it in the real code though.

@dburles  I'll load that up on a phone when I get the chance and report back.

That'd be great, if it's no good, I'll take a look into it.

Hey, looks like this was again another issue with my own setup. If you want to know the issue, I was returning a cursor.findOne in my routes data (which I used in the corresponding template), which caused the route to hit every time the object changed, which I normally wouldnt notice, aside from the map reloading. Feel like thats pretty weird behavior of iron router. To solve I just made a helper that returned that cursor instead and wah-lah, non refreshing map.

Btw if you want your demo example to work out of the box with cordova, create a mobile-config.js file at the root and put
App.accessRule('*.google.com/*');
App.accessRule('*.googleapis.com/*');
App.accessRule('*.gstatic.com/*');

In it. Cheers!

Thanks, I'll put that in the docs as I've seen many people run into confusion with that.


Add and use a cmake_generate macro for running cmake against a suitable target [phab:D706]

Created by shahms at 2016-02-11 21:29:16:
Turn the cmake shenanigans into a rule

schroederc wrote at 2016-02-11 21:40:25:
So this is what has become of us.  We're using a subset of a superset of Python to program a build system to run a build system which generates a configuration for another build system.  \meme{idontwanttoliveonthisplanetanymore}

schroederc accepted this revision at 2016-02-11 21:41:29

shahms closed via commit a586adaeb3638ab6b501f50f97ec250fff7be82c at 2016-02-11 21:46:25


Added AccountLinking webhook support

Added AccountLinking callback and fixed :read callback.

Coverage decreased (-0.3%) to 99.316% when pulling d6cb9bd48917b63146bb78359857e78e003c998e on dmitryshagin:master into a72a09c86e92acc58752028d523a84f65a24a33b on hyperoslo:master.

Coverage increased (+0.02%) to 99.66% when pulling d19cad2c4bc32e97eab078c3c89758a7f23c3d09 on dmitryshagin:master into a72a09c86e92acc58752028d523a84f65a24a33b on hyperoslo:master.

Travis is now passing. Seems to be done.

Coverage increased (+0.4%) to 100.0% when pulling f85685bd86a235343ef7f13f52d73e024bc0f2d2 on dmitryshagin:master into a72a09c86e92acc58752028d523a84f65a24a33b on hyperoslo:master.

Thanks!


[cgroup support] How to calculate pod resources?

When I am developing "host cgroup" support feature for kata containers (PR: #734  , issue: #344 ) , I realized that we don't have an all-agreed policy on how to calculate POD resources, take this pod spec as an example:
apiVersion: v1
kind: Pod
metadata:
  name: nginx-untrusted
  annotations:
    io.kubernetes.cri.untrusted-workload: "true"
spec:
  containers:
  - name: nginx
    image: nginx
    resources:
      requests:
        memory: "64Mi"
        cpu: "250m"
      limits:
        memory: "128Mi"
        cpu: "500m"
  - name: busybox
    image: busybox
    command: ['top']

If one container ”nginx“ has a resource limit of 128M memory and 0.5 core CPU, another container "busybox" in same POD has no resource limit(in other words, unlimited resources), how should we calculate the POD resource?
Should we give the pod 128M and 0.5 core because this is the specified resource limit?
Or should we give each container a default resource(let's say 1 core, 128M), and calculated this as 128M+128M+128M（pause container） and 0.5core+1core+1core ?

ack. Once we have agreed how we calculate resources (memory and CPU) that are assigned to the VM, I'd really like to see this clearly documented somewhere in an MD file, and not just in the code :-)
This might also make a nice topic for a blog, whitepaper or conference presentation :-)
/cc @devimc

@WeiZhang555  in your spec you are not specifying 7 cpus, ptal https://github.com/kata-containers/documentation/blob/master/constraints/cpu.md

@devimc I'm specifying 0.7 cpu, note that
      limits:
        cpu: "500m"

means 0.5 core, according to our documentation:
https://github.com/kata-containers/documentation/blob/master/constraints/cpu.md#container-with-cpu-constraint

The runtime calculates the number of vCPUs required by a container with CPU constraints using the following formula: (quota + (period -1)) / period, where quota specifies the number of microseconds per CPU Period that the container is guaranteed CPU access and period specifies the CPU CFS scheduler period of time in microseconds. The result determines the number of vCPU to hot plug into the virtual machine. Once the vCPUs have been added, the agent places the container inside a CPU cgroup. This placement allows the container to use only its assigned resources.

Aparently 0.5 core is calculated as 1 vcpu to hotplug, 0.2 (200m) core is also calculated as 1 vcpu to hotplug, plus pause container, that's why I got 3 cpu inside the VM. It's a resource waste and not correct.

@WeiZhang555

Aparently 0.5 core is calculated as 1 vcpu to hotplug, 0.2 (200m) core is also calculated as 1 vcpu to hotplug, plus pause container, that's why I got 3 cpus inside the VM. It's a resource waste and not correct.

https://github.com/kata-containers/runtime/pull/696#issuecomment-418834574

@devimc I missed a good conversation... I think @bergwolf is right, https://github.com/kata-containers/runtime/pull/696#issuecomment-419051458
I agree with his opinion, we calculated the VCPU number in a wrong way.
This issue contains two problem:

we leave a default_vcpu for unconstrainted container, this is duplicate issue with https://github.com/kata-containers/runtime/issues/695
for 0.5 core vcpu, we calculated as 1 vcpu, so this makes it worse, 2 containers with 0.5 core and 0.2 core finally gets 2 vcpus, but actually 1 vcpu is enough, with host cgroup support, we can limit the 1 vcpu to finer granularity- 0.7 core

@WeiZhang555

for 0.5 core vcpu, we calculated as 1 vcpu, so this makes it worse, 2 containers with 0.5 core and 0.2 core finally gets 2 vcpus, but actually 1 vcpu is enough, with host cgroup support, we can limit the 1 vcpu to finer granularity- 0.7 core

I agree


When reposting a service bus message after a failure, the Diagnostic-Id field is not reset/clear.

Library name and version
Azure.Messaging.ServiceBus 7.17.5
Describe the bug
When reposting a service bus message after a failure, the Diagnostic-Id field is not reset/clear.
Expected behavior
Diagnostic-Id field should be cleared.
Actual behavior
The same Diagnostic-Id values is kept for unrelated messages.
Reproduction Steps
await using var serviceBusSender = serviceBusClient.CreateSender(topicName);
await serviceBusSender.SendMessageAsync(
new ServiceBusMessage(message)
{
ApplicationProperties =
{
[configuration.ReviveForProperty] = subscriptionName,
[configuration.RetryCounterProperty] = retryCounter + 1
},
ScheduledEnqueueTime = DateTimeOffset.UtcNow.Add(TimeSpan.FromSeconds(retryDelay))
});
Environment
Azure Function App
.NET SDK:
Version:           8.0.300
Commit:            326f6e68b2
Workload version:  8.0.300-manifests.4e5ea2d8
MSBuild version:   17.10.4+10fbfbf2e
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.22000
OS Platform: Windows
RID:         win-x64
Base Path:   C:\Program Files\dotnet\sdk\8.0.300\
.NET workloads installed:
[aspire]
Installation Source: VS 17.10.34928.147
Manifest Version:    8.0.0/8.0.100
Manifest Path:       C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.aspire\8.0.0\WorkloadManifest.json
Install Type:        FileBased
Host:
Version:      8.0.5
Architecture: x64
Commit:       087e15321b

@EmilDamian:  Thank you for reaching out and we regret that you're experiencing difficulties.   I'm not sure that I understand the end-to-end scenario that you're describing.   Can you please provide more context for what a "failure" is in this scenario and what you believe the expected behavior should be?


Docker-Compose fails: Can't copy

Hi,
I am trying to run cd docker && docker-compose up and it fails with the next error message:
Building conductor-server
Step 1/10 : FROM java:8-jre-alpine
 ---> fdc893b19a14
Step 2/10 : MAINTAINER Netflix OSS<EMAIL_ADDRESS> ---> Using cache
 ---> 6d29fc75be25
Step 3/10 : RUN mkdir -p /app/config /app/logs /app/libs
 ---> Using cache
 ---> f66429ad9cda
Step 4/10 : COPY ./docker/server/bin /app
ERROR: Service 'conductor-server' failed to build: COPY failed: stat /var/lib/docker/tmp/docker-builder868234431/docker/server/bin: no such file or directory

https://netflix.github.io/conductor/intro/#or-start-all-the-services-using-docker-compose
Any ideas what is wrong here? am I doing something here wrong here? or the docker file?

Seems to be a docker version issue:
Try editing the UI and Server Docker files and remove the ./ on all the COPY commands ...
conductor/docker/server/Dockerfile
Copy the project directly onto the image
COPY ./docker/server/bin /app
COPY ./docker/server/config /app/config
COPY ./server/build/libs/conductor-server-*-all.jar /app/libs
to
Copy the project directly onto the image
COPY docker/server/bin /app
COPY docker/server/config /app/config
COPY server/build/libs/conductor-server-*-all.jar /app/libs
and
conductor/docker/ui/Dockerfile
Copy the ui files onto the image
COPY ./docker/ui/bin /app
COPY ./ui /app/ui
to
Copy the ui files onto the image
COPY docker/ui/bin /app
COPY ui /app/ui
Then before you bring up your compose file build the individual images...
docker build -f docker/server/Dockerfile.build -t conductor:server-build .
docker run -v $(pwd):/conductor conductor:server-build
docker build -f docker/server/Dockerfile -t conductor:server .
docker build -f docker/ui/Dockerfile -t conductor:ui .

The solution provided by @unicurva solved it for me. Thanks!

Beware that "bin" is in .gitignore file in the conductor's root directory. Thus, make sure that the file that is declared to be copied in the Dockerfile really exists (./docker/server/bin).


SwiftDriver: avoid use of fatalError in the driver

Present a diagnostic for the failure rather than invoking fatalError. This ensures that the user sees a proper diagnostic for the failure and also enables the test suite to run to completion in case of an error.

@swift-ci please test

@swift-ci please test


BridgeBot union data format

While working on BridgeBot I became convinced that it does require some sort of union data format. I'll try to define it here, and keep it updated as the code evolves.

Here is a first version, as a strawman:
{
  identifiers: Set<string>;
  title: string;
  completed: boolean;
  comments: string[];
}

The identifiers set can be used to link local identifiers for issues together across synced systems.

Version 2:
issue:
{
  identifiers: Set<string>;
  title: string;
  completed: boolean;
}

comment:
{
  identifiers: Set<string>;
  text: string;
  issueId: string;
}


[Comp-Req]: Skeleton Loader

Component Name
NXW-Skeleton
Use-case
Make loading state more user friendly by showing a temporary placeholder skeleton
Example
https://vuetifyjs.com/en/components/skeleton-loaders/#usage

added in version 0.7.0


support v2 invite output from issue_invite.sh

Supports the v2 format introduced introduced here:
https://github.com/uProxy/uproxy-docker/pull/55

Closing this for now, since I don't think uProxy will be issuing additional invites for users at launch.

I'm actually making changes here so that issue_invite.sh just outputs the 3 fields needed for uProxy to generate the invite (host, user, key).  Once this is done, we will have uProxy doing v2 invites and issue_invite.sh won't need to worry about the invite format anymore


Use Google as a backup DNS resolver

Some systems fail to resolve the TXT record after creation. This PR adds Google's primary DNS server as a backup (note: it's not foolproof as some networks may block Google traffic).
Example failure:
LOG: 2022/11/10 20:29:41.859639 /home/smasoud/git/kubefirst/internal/aws/aws.go:233: kubefirst-liveness.k8s.example.com
LOG: 2022/11/10 20:29:41.861470 /home/smasoud/git/kubefirst/internal/aws/aws.go:236: []
LOG: 2022/11/10 20:29:41.861616 /home/smasoud/git/kubefirst/internal/aws/aws.go:239: Could not get record name kubefirst-liveness.k8s.example.com - waiting 10 seconds and trying again:
error: lookup kubefirst-liveness.k8s.example.com on <IP_ADDRESS>:53: cannot marshal DNS message
LOG: 2022/11/10 20:29:51.864912 /home/smasoud/git/kubefirst/internal/aws/aws.go:233: kubefirst-liveness.k8s.example.com
LOG: 2022/11/10 20:29:51.866569 /home/smasoud/git/kubefirst/internal/aws/aws.go:236: []
LOG: 2022/11/10 20:29:51.866668 /home/smasoud/git/kubefirst/internal/aws/aws.go:239: Could not get record name kubefirst-liveness.k8s.example.com - waiting 10 seconds and trying again:
error: lookup kubefirst-liveness.k8s.example.com on <IP_ADDRESS>:53: cannot marshal DNS message
LOG: 2022/11/10 20:30:01.868958 /home/smasoud/git/kubefirst/internal/aws/aws.go:233: kubefirst-liveness.k8s.example.com
LOG: 2022/11/10 20:30:01.871266 /home/smasoud/git/kubefirst/internal/aws/aws.go:236: []
LOG: 2022/11/10 20:30:01.871382 /home/smasoud/git/kubefirst/internal/aws/aws.go:239: Could not get record name kubefirst-liveness.k8s.example.com - waiting 10 seconds and trying again:
error: lookup kubefirst-liveness.k8s.example.com on <IP_ADDRESS>:53: cannot marshal DNS message
LOG: 2022/11/10 20:30:11.874855 /home/smasoud/git/kubefirst/internal/aws/aws.go:233: kubefirst-liveness.k8s.example.com
LOG: 2022/11/10 20:30:11.876884 /home/smasoud/git/kubefirst/internal/aws/aws.go:236: []
LOG: 2022/11/10 20:30:11.877042 /home/smasoud/git/kubefirst/internal/aws/aws.go:239: Could not get record name kubefirst-liveness.k8s.example.com - waiting 10 seconds and trying again:
error: lookup kubefirst-liveness.k8s.example.com on <IP_ADDRESS>:53: cannot marshal DNS message
LOG: 2022/11/10 20:30:21.878077 /home/smasoud/git/kubefirst/internal/aws/aws.go:233: kubefirst-liveness.k8s.example.com
LOG: 2022/11/10 20:30:21.879615 /home/smasoud/git/kubefirst/internal/aws/aws.go:236: []
LOG: 2022/11/10 20:30:21.879868 /home/smasoud/git/kubefirst/internal/aws/aws.go:239: Could not get record name kubefirst-liveness.k8s.example.com - waiting 10 seconds and trying again:
error: lookup kubefirst-liveness.k8s.example.com on <IP_ADDRESS>:53: cannot marshal DNS message
LOG: 2022/11/10 20:30:31.881783 /home/smasoud/git/kubefirst/internal/aws/aws.go:233: kubefirst-liveness.k8s.example.com
LOG: 2022/11/10 20:30:31.884125 /home/smasoud/git/kubefirst/internal/aws/aws.go:236: []
LOG: 2022/11/10 20:30:31.884208 /home/smasoud/git/kubefirst/internal/aws/aws.go:239: Could not get record name kubefirst-liveness.k8s.example.com - waiting 10 seconds and trying again:
error: lookup kubefirst-liveness.k8s.example.com on <IP_ADDRESS>:53: cannot marshal DNS message

@saidmasoud thank you so much again for your valuable contribution! This will lead to a faster DNS resolution, and decrease the required installation time.

@saidmasoud: I know it's been a while you created that PR, but I would love to send you some swag to thank you for your first PR on Kubefirst. If you want, fill that form please

Submitted, thanks Frédéric!
On Wed, Feb 8, 2023, 4:34 PM Frédéric Harper @.***>
wrote:

@saidmasoud https://github.com/saidmasoud: I know it's been a while you
created that PR, but I would love to send you some swag to thank you for
your first PR on Kubefirst. If you want, fill that form
https://docs.google.com/forms/u/2/d/1NZM6JOfmZRUZGn_mFhU1VZ6d6RkcY7IeRL2i2V0AD5U/edit
please
—
Reply to this email directly, view it on GitHub
https://github.com/kubefirst/kubefirst/pull/710#issuecomment-1423268873,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFR4VPPWAHQDAXNC6ZQR2RLWWQGOVANCNFSM6AAAAAAR5E4MU4
.
You are receiving this because you were mentioned.Message ID:
@.***>


Enforce that we only see substituted requirements in checkRequirement()

Requirement checking asks questions about concrete types, so if a requirement still contains type parameters we cannot answer questions about it, because we don't have a generic signature. Asserting here instead of just reporting the requirement as unsatisfied uncovered various issues throughout the compiler.

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please smoke test


Allow cmd/jv to validate yaml files

If a file provided to cmd/jv ends in .yaml or .yml, instead of unmarshalling as a JSON file it's instead unmarshalled as YAML and validated as per the instructions in the README file.
A few other cleanups of cmd/jv were done at the same time:
Move validation to a separate func so defer file.Close() calls Close sooner (current behaviour holds the file handles open for every file being validated due to defer being called within a for loop)
Create a separate go.mod file for cmd/jv so the newly added yaml dependency doesn't pollute the main library
Fix .gitignore file to not ignore the entire cmd/jv folder
Make error output include the filename

the main reason it is not added to cmd/vm is: I do not like seeing yaml dependency in go.mod file.
for this reason, the sample code is provided as playground link in readme

i noticed you added separate go.mod file in cmd/jv.
Does this change resolve Issue #42

hey yeah I made the cmd module not be under v5 since major versioning of the cmd tool doesn't really make as much sense as it does for the library. you might need to make a separate tag for it though, specifically a tag "cmd/jv/v1.0.0" (or some other v1.x.x version) I believe should do the trick.
the separate go.mod file also prevents needing the yaml dependency in the library go.mod at the top level -> so anyone using this as a library won't pull in the yaml dependency for their project

Thanks @santhosh-tekuri for this great project !
The code snipet to validate yaml document is quite useful for developers using this project as a library.
For users of the cli, it would be great to have built-in yaml support, is it something that you would still consider ?

@gberche-orange
the reason why this pull request is not yet merged. I am not sure how multiple go.mod files work in single git repository.
I looked at https://stackoverflow.com/questions/55041915/multiple-modules-within-the-same-project.
but still not clear
also I don't want to add yaml dependency to main go.mod file

thanks @santhosh-tekuri for your quick answer.
I'm not a go developer, so I won't be able to help much hands on.
However I have the intuition that a distinct repo to host the jv binary is suboptimal as it would imply different gh issues, release cycles etc...
Reading the gomod documentation, I understand that there can be multiple modules within a single git repo, each with its own go.mod file:
https://go.dev/ref/mod#go-mod-init

The go mod init command initializes and writes a new go.mod file [...]
init accepts one optional argument, the module path for the new module. See Module paths for instructions on choosing a module path. If the module path argument is omitted, init will attempt to infer the module path using import comments in .go files, vendoring tool configuration files, and the current directory (if in GOPATH).

https://go.dev/ref/mod#module-path

A module path is the canonical name for a module, declared with the module directive in the module’s go.mod file. A module’s path is the prefix for package paths within the module.
A module path should describe both what the module does and where to find it. Typically, a module path consists of a repository root path, a directory within the repository (usually empty), and a major version suffix (only for major version 2 or higher).

May be you could declare a new module for the jv cli, with its own go.mod file.
This way library users could still import the go.mod without pulling the yaml dependency, and the jv releases binary could include the yaml support built-in. You might be able to find
You might get some inspirations from other repos with multiple go.mod files on how they structure their build to produce different build artefacts. kubernetes/kubernetes is in this case, although it might be a complex example due to its size https://github.com/search?q=repo%3Akubernetes%2Fkubernetes+path%3A*%2Fgo.mod+&type=code
Hope this helps

or we could create separate GitHub project for jv command

I see that https://github.com/neilpa/yajsv has taken this approach based on https://github.com/xeipuuv/gojsonschema

@gberche-orange let me give a try and see if it works

@gberche-orange
I added yaml support and created tag cmd/jv/v0.1.0
now you can install it using either command:
go install github.com/santhosh-tekuri/jsonschema/cmd/jv@latest
or
go install github.com/santhosh-tekuri/jsonschema/cmd/jv
could you please try and let me know if it works

thanks @santhosh-tekuri !
Here what I tried
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) go install github.com/santhosh-tekuri/jsonschema/cmd/jv@latest
package github.com/santhosh-tekuri/jsonschema/cmd/jv@latest: can only use path@version syntax with 'go get'
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) go install github.com/santhosh-tekuri/jsonschema/cmd/jv
go: finding module for package github.com/santhosh-tekuri/jsonschema/cmd/jv
go: downloading github.com/santhosh-tekuri/jsonschema v1.2.4
go: downloading github.com/santhosh-tekuri/jsonschema/cmd/jv v0.1.0
go: found github.com/santhosh-tekuri/jsonschema/cmd/jv in github.com/santhosh-tekuri/jsonschema/cmd/jv v0.1.0
go: downloading github.com/santhosh-tekuri/jsonschema/v5 v5.1.1

guillaume@guillaume-dev-box:~/public-code/goss$ jv --help
jv [-draft INT] [-output FORMAT] [-assertformat] [-assertcontent] <json-schema> [<json-doc>]...
  -assertcontent
        enable content assertions with draft >= 2019
  -assertformat
        enable format assertions with draft >= 2019
  -draft int
        draft used when '$schema' attribute is missing. valid values 4, 5, 7, 2019, 2020 (default 2020)
  -output string
        output format. valid values flag, basic, detailed

jv docs/goss-json-schema.yaml docs/rendered_goss.yaml
jsonschema file:///home/guillaume/public-code/goss/docs/goss-json-schema.yaml compilation failed: invalid json file:///home/guillaume/public-code/goss/docs/goss-json-schema.yaml: invalid character '$' looking for beginning of value

So I'm not sure that I'm runnning the right version and whether the yaml support should be built-in

you got the error can only use path@version syntax with 'go get'
it seems you are using golang older version
module support is enabled by default since golang 1.16. you can check your version by go version
in older versions you can enable module support explicitly. for example you can try following:
GO111MODULE=on go install github.com/santhosh-tekuri/jsonschema/cmd/jv@latest
I guess the above command should work.

thanks @santhosh-tekuri
It's better with a recent go version
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) go version
go version go1.19.4 linux/amd64
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) go install github.com/santhosh-tekuri/jsonschema/cmd/jv@latest
go: downloading github.com/santhosh-tekuri/jsonschema/cmd/jv v0.2.0
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) which jv
/home/guillaume/go/bin/jv
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) ls -al /home/guillaume/go/bin/jv
-rwxrwxr-x 1 guillaume guillaume 7936962 janv.  4 12:08 /home/guillaume/go/bin/jv
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) date
mer. 04 janv. 2023 12:09:33 CET
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) jv -h
jv [-draft INT] [-output FORMAT] [-assertformat] [-assertcontent] <json-schema> [<json-or-yaml-doc>]...
  -assertcontent
    	enable content assertions with draft >= 2019
  -assertformat
    	enable format assertions with draft >= 2019
  -draft int
    	draft used when '$schema' attribute is missing. valid values 4, 5, 7, 2019, 2020 (default 2020)
  -output string
    	output format. valid values flag, basic, detailed

It now seems that jv is only supporting json schemas in json format, and not yet in yaml format:
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) jv docs/goss-json-schema.yaml docs/rendered_goss.yaml
jsonschema file:///home/guillaume/public-code/goss/docs/goss-json-schema.yaml compilation failed: invalid json file:///home/guillaume/public-code/goss/docs/goss-json-schema.yaml: invalid character '$' looking for beginning of value

Here is my sample json schema in yaml format https://github.com/goss-org/goss/blob/ba8d39eabeb235bb322082a4f4bfac96e93f9128/docs/goss-json-schema.yaml if you can further refine the yaml support for schemas

Only the document being validated can be either json or yaml. The schema still requires json document currently

@gberche-orange
I added support for yaml schemas. please try it with following commands:
go install -v github.com/santhosh-tekuri/jsonschema/cmd/jv@latest
or
go install -v<EMAIL_ADDRESS>

awesome, thanks @santhosh-tekuri !  This properly validates my yaml schema :-)
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) go install -v<EMAIL_ADDRESS>go: downloading github.com/santhosh-tekuri/jsonschema/cmd/jv v0.3.0
github.com/santhosh-tekuri/jsonschema/cmd/jv

guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) jv docs/goss-json-schema.yaml docs/rendered_goss.yaml
[I#] [S#] doesn't validate with https://github.com/goss-org/goss/master/docs/goss-json-schema.yaml#
  [I#/service/sshd] [S#/properties/service/additionalProperties/$ref] doesn't validate with '/definitions/serviceTest'
    [I#/service/sshd] [S#/definitions/serviceTest/required] missing properties: 'skip'
  [I#/process/chrome] [S#/properties/process/additionalProperties/$ref] doesn't validate with '/definitions/processTest'
    [I#/process/chrome] [S#/definitions/processTest/required] missing properties: 'skip'

ps: I'm wondering if the output flag is expected to have effects when there are validation errors, as I don't currently observe different outputs
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) jv docs/goss-json-schema.yaml docs/rendered_goss.yaml -output flag
[I#] [S#] doesn't validate with https://github.com/goss-org/goss/master/docs/goss-json-schema.yaml#
  [I#/service/sshd] [S#/properties/service/additionalProperties/$ref] doesn't validate with '/definitions/serviceTest'
    [I#/service/sshd] [S#/definitions/serviceTest/required] missing properties: 'skip'
  [I#/process/chrome] [S#/properties/process/additionalProperties/$ref] doesn't validate with '/definitions/processTest'
    [I#/process/chrome] [S#/definitions/processTest/required] missing properties: 'skip'
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) jv docs/goss-json-schema.yaml docs/rendered_goss.yaml -output basic
[I#] [S#] doesn't validate with https://github.com/goss-org/goss/master/docs/goss-json-schema.yaml#
  [I#/service/sshd] [S#/properties/service/additionalProperties/$ref] doesn't validate with '/definitions/serviceTest'
    [I#/service/sshd] [S#/definitions/serviceTest/required] missing properties: 'skip'
  [I#/process/chrome] [S#/properties/process/additionalProperties/$ref] doesn't validate with '/definitions/processTest'
    [I#/process/chrome] [S#/definitions/processTest/required] missing properties: 'skip'
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix) jv docs/goss-json-schema.yaml docs/rendered_goss.yaml -output detailed
[I#] [S#] doesn't validate with https://github.com/goss-org/goss/master/docs/goss-json-schema.yaml#
  [I#/service/sshd] [S#/properties/service/additionalProperties/$ref] doesn't validate with '/definitions/serviceTest'
    [I#/service/sshd] [S#/definitions/serviceTest/required] missing properties: 'skip'
  [I#/process/chrome] [S#/properties/process/additionalProperties/$ref] doesn't validate with '/definitions/processTest'
    [I#/process/chrome] [S#/definitions/processTest/required] missing properties: 'skip'
guillaume@guillaume-dev-box:~/public-code/goss$ (json-schema-fix)

@gberche-orange looks some thing wrong. options does not seem to be working. let me check

it works if you pass flags before passing arguments. i.e, the following works
jv -output detailed docs/goss-json-schema.yaml docs/rendered_goss.yaml
if you specify flags at end, they are getting ignored, seems golang flags package works like that

I also made small enhancement, if you give multiple files to validate, then it used to stop when any file validation fails.
I changed it to validate all given files always

closing: now jv supports yaml files


Chaining jsonSet allowed but doesn't work as expected

As a developer, I sometimes need to update multiple JSON subfields. Chaining multiple .jsonSet in the update callback is seemingly allowed (there are no typing or runtime errors), but generates unexpected SQL. Only the last jsonSet is actually taken into account.
class PostTable extends BaseTable {
  readonly table = "post"

  columns = this.setColumns(t => ({
    id: t.serial().primaryKey(),
    data: t.json<{ foo?: string, bar?: string }>(),
  }))
}

await db.post.find(1).update({
  data: q => q
    .jsonSet("data", ["foo"], "FOO")
    .jsonSet("data", ["bar"], "BAR"),
})

generates:
UPDATE "post" SET "data" = jsonb_set("post"."data", '{bar}', $1) WHERE "post"."id" = $2 ['"BAR"', 1]

What I would expect is the respective chained jsonb_set(jsonb_set(...), ...) call in SQL.

Chaining them in SQL can't be the way, because you can technically chain jsonSets for different columns.
I'm thinking about something like:
await db.post.find(1).update({
  data: q => q.jsonModify('data', (json) =>
    json
      .set(['path1'], value1)
      .set(['path2'], value2)
      .insert(['path2arr'], value3)
      .remove(['path2arr', index])
  )

A better idea, this all can be chained with a minimal syntax:
await db.post.find(1).update({
  data: q => q.get('data')
    .jsonSet(['path1', value1])
    .jsonSet(['path2', value2])
    .jsonInsert(['path2arr', value])
    .jsonInsert(['path2arr', index])
});

But, a signature for json* has to change for this so it is a breaking change. Would you mind it?

Published update, now you can use and chain jsonSet, jsonInsert, jsonRemove after get (or ref instead of get would be equivalent inside update).
await db.post.find(1).update({
  data: q => q.get('data')
    .jsonSet("foo", "FOO")
    .jsonSet("bar", "BAR"),
})

Renamed jsonPathQuery to jsonPathQueryFirst because it's using jsonb_path_query_first from Postgres, and maybe more similar methods will be added in the future.
Updated docs, and breaking changes.


Add ability to deprecate properties and parameters

It appears that there is no way to deprecate a parameter or property in swagger spec. The deprecate: true statement applies only at operation level

This is a duplicate of #584.  (I know it's hard to tell by the issue subject but there is an explicit request in that issue to allow deprecating parameters and properties.)

@whitlockjc you seem to have made a reference to current issue instead of another.

Woops.

Thanks for the update.  It's a duplicate of #524.  I crossed my streams.


feat: backoff in retry helper

I really like 0.2, 0.2, 0.4, 0.6, 1.0, 1.6, 2.6, 4.6, 5, 5...
We should export some statergy in fedimint-core but naming is hard.

adding backport label, it would be nice to have in fedi.

Successfully created backport PR for releases/v0.3:

#4769


ocamlPackages.cow: 2.2.0 -> 2.4.0

Motivation for this change
Update cow. Contains switch to dune which makes the package cleaner. Also fixed the package name, attribute was correct.
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"
[ ] 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.

@GrahamcOfBorg build ocamlPackages.cow

@vbgl Any concerns merging this? This also works with a local ocaml project.

@GrahamcOfBorg build ocamlPackages.cow


tabs issue in vars.yml

I got errors when I tried running the ansible-playbook command:
ERROR: Syntax Error while loading YAML script, /home/oren/p/5minutes/vars.yml
Note: The error may actually appear before this position: line 9, column 1

user_public_keys:
        - ~/.ssh/id_rsa.pub
^

I had to remove the spaces in line 9 and put tab instead. I had to do that for more lines in that file.
Maybe it's because my laptop is Ubuntu?

Oh it's tabs vs spaces again ;)
My editor uses spaces as default, so you need to adjust your machine.

got it. thanks


Deleting stash doesn't remove the stash from the list - have to refresh

GitLens Version: 9.9.3
VSCode Version: 1.37.1
-OS: Windows 10

Steps to Reproduce:

Stash something
In GitLens right click -> Delete Stashed Changes
The list doesn't update. If you try to delete again, it deletes another stash. Potentially disastrous bug.

If you refresh the whole view, then it disappears from the view.

@admehta01 I can't reproduce this behavior. Do you have automatic refresh of the Repositories view turned off?

Here are my settings:

@admehta01 Hrm, can you please enable output channel logging by setting "gitlens.outputLevel": "debug" in your settings.json. This will enable logging to the GitLens channel in the Output pane. Once enabled, please reproduce the issue and attach the log lines from the GitLens channel. Thanks!

[2019-08-26 03:41:21:751] [1a4c] GitService.stashDelete — e=c:/Github/app, t=stash@{0}
[2019-08-26 03:41:24:292] [c:/Github/app] git stash drop stash@{0} • 2541 ms
[2019-08-26 03:41:24:293] [1a4c] GitService.stashDelete completed • 2541 ms

@admehta01 I need the logs that happen after the stashDelete call too -- I want to look at how the view responds (or doesn't) to the repository change

Hmm, those are the only lines I see.
On Sun, Aug 25, 2019, 9:12 PM Eric Amodio<EMAIL_ADDRESS>wrote:

@admehta01 https://github.com/admehta01 I need the logs that happen
after the stashDelete call too -- I want to look at how the view responds
(or doesn't) to the repository change
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eamodio/vscode-gitlens/issues/826?email_source=notifications&email_token=AAO3H5VFWQW5KKAC46TBARTQGNJ4XA5CNFSM4IOMKVO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5DGUEA#issuecomment-524708368,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAO3H5RCCXQUFRYZIRP4OZDQGNJ4XANCNFSM4IOMKVOQ
.

If you click on the ... menu of the Repositories view do you see this:

Does it say enable or disable?

Because of this error, deleting changes from the Stashes list can be very dangerous. May result in erroneous deletion of changes. :disappointed:

@admehta01 @ShinaZin I can't seem to reproduce this for the life of me. Is there any other specific details that you can provide? OS, using VS Code remote? Remote file system? File share? etc?

VS Code
Version: 1.38.1 (user setup)
Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0
Date: 2019-09-11T13:35:15.005Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 6.1.7601
GitLense v10.0.1

Using filesystem: NTFS
Repo .git/config file:
[core]
	repositoryformatversion = 0
	filemode = false
	bare = false
	logallrefupdates = true
	symlinks = false
	ignorecase = true
	autocrlf = false
[remote "origin"]
	url = deleted
	fetch = deleted
[branch "master"]
	remote = origin
	merge = refs/heads/master
[gui]
	wmstate = normal
	geometry = 1005x515+358+184 175 196

Ah! Now I see. Thank you @ShinaZin for the full screenshot! So the basic issue is that the repository it outside of the opened workspace -- so vscode (and in turn) GitLens is unable to get file system change events for it. So I will need to manually cause a refresh when actions are taken.
While its subtle, you can see in the Repositories view there is a <!> next to the repository name -- which is the indicator of this (and it mentions it in the tooltip for the repo as well).
@admehta01 is this the same for you? Do you see a <!> indicator next to the repositories that you are experiencing this issue with?

Yes, that's in my screenshot as well. What do you mean by "repository it outside of the opened workspace"?


Mobile apps for Android and iOS

In this day and age, it seems like shooting yourself in the foot to not have native apps for mobile. There is plenty of reading on mobile first design, why it's so important strategically, and how to do it well.

There's a new (not yet public project) to port bitmarkets to a pure web client using webRTC for p2p communications. This would support all platforms with a modern web browser.

ah, that sounds great. hope it can be made public soon


Fix the new user login bug by correctly reporting new user objects we create

The issue we were seeing (where new users would inexplicably end up on the root page which just says 'OK') turns out to be due to the login process failing at the very end. The condition at https://github.com/mozilla/mozilla-django-oidc/blob/master/mozilla_django_oidc/views.py#L101 was not being met, and indeed, self.user was None. authenticate gets the user from get_or_create_user: https://github.com/mozilla/mozilla-django-oidc/blob/master/mozilla_django_oidc/auth.py#L290 , which will, in turn call create_user if the user is new: https://github.com/mozilla/mozilla-django-oidc/blob/master/mozilla_django_oidc/auth.py#L329 , which we had overridden in such a way that it did not return the new object. A subsequent log in attempt would succeed, because filter_users_by_claims would be able to find the user object persisted in the database.

Both good suggestions; I've opened https://github.com/scimma/scimma-admin/issues/24 to remind myself to carry them out.


Build error: gradlew.bat failed with exit code 1

Hi,
After a few months of doing other projects and enjoying the summer I decided to get back to work on my Nativescript project. Reading the documentation, I decided to update to version 2.2.1. Armed with the update manual I followed the instuctions. But when building my project for the first time I noticed a build error:  /gradlew.bat failed with exit code 1
Reading similar issues on stackoverflow.com and here I tried several options to resolve the issue, but no luck so far. Things I tried:

Instructions on Android plugins and Windows path size issues
Removing and adding the android platform (tns platform remove android, tns platform add android)
Removing the node_modules folder
Updating the Andoid SDK
gradlew clean in folder /platforms/android

Nothing helped. Anyone for a good hint?
Version numbers:
tns: 2.2.1
Cross-platform modules: 2.2.1
Package.json of project:
{
  "nativescript": {
    "id": "nl.progig.handsonlifesupport",
    "tns-android": {
      "version": "2.2.0"
    }
  },
  "dependencies": {
    "dateformat": "^1.0.12",
    "intl": "^1.1.0",
    "tns-android": "^2.2.0",
    "tns-core-modules": "^2.2.1"
  },
  "devDependencies": {
    "babel-traverse": "6.14.0",
    "babel-types": "6.14.0",
    "babylon": "6.9.1",
    "lazy": "1.0.11"
  }
}

--log trace output:
$ tns build android --log trace
execFile: D:\android-sdk\platform-tools\adb "help"
execFile: D:\android-sdk\platform-tools\adb "help"
spawn: D:\android-sdk\platform-tools\adb "--help"
Socket {
  _connecting: false,
  _hadError: false,
  _handle:
   Pipe {
     bytesRead: 0,
     _externalStream: {},
     fd: -1,
     writeQueueSize: 0,
     owner: [Circular],
     onread: [Function: onread],
     reading: true },
  _parent: null,
  _host: null,
  _readableState:
   ReadableState {
     objectMode: false,
     highWaterMark: 16384,
     buffer: [],
     length: 0,
     pipes: null,
     pipesCount: 0,
     flowing: null,
     ended: false,
     endEmitted: false,
     reading: true,
     sync: false,
     needReadable: true,
     emittedReadable: false,
     readableListening: false,
     resumeScheduled: false,
     defaultEncoding: 'utf8',
     ranOut: false,
     awaitDrain: 0,
     readingMore: false,
     decoder: null,
     encoding: null },
  readable: true,
  domain: null,
  _events:
   { end: { [Function: g] listener: [Function: onend] },
     finish: [Function: onSocketFinish],
     _socketEnd: [Function: onSocketEnd],
     close: [Function] },
  _eventsCount: 4,
  _maxListeners: undefined,
  _writableState:
   WritableState {
     objectMode: false,
     highWaterMark: 16384,
     needDrain: false,
     ending: false,
     ended: false,
     finished: false,
     decodeStrings: false,
     defaultEncoding: 'utf8',
     length: 0,
     writing: false,
     corked: 0,
     sync: true,
     bufferProcessing: false,
     onwrite: [Function],
     writecb: null,
     writelen: 0,
     bufferedRequest: null,
     lastBufferedRequest: null,
     pendingcb: 0,
     prefinished: false,
     errorEmitted: false,
     bufferedRequestCount: 0,
     corkedRequestsFree: CorkedRequest { next: null, entry: null, finish: [Function] } },
  writable: false,
  allowHalfOpen: false,
  destroyed: false,
  _bytesDispatched: 0,
  _sockname: null,
  _writev: null,
  _pendingData: null,
  _pendingEncoding: '',
  server: null,
  _server: null }
Exec npm -v
 stdout: 2.15.9

 stderr:
spawn: java "-version"
Exec node-gyp -v
 stdout:
 stderr: 'node-gyp' is not recognized as an internal or external command,
operable program or batch file.

Exec "D:\android-sdk\platform-tools\adb" version
 stdout: Android Debug Bridge version 1.0.36
Revision 8f855a3d9b35-android

 stderr:
spawn: D:\android-sdk\tools\android.bat "-h"
Result when throw error is false:
{ stdout: '\n       Usage:\n       android [global options] action [action options]\n       Global options:\n  -s --silent     : Silent mode, shows errors only.\n  -v --verbose    : Verbose mode, shows errors, warnings and all messages.\n     --clear-cache: Clear the SDK Manager repository manifest cache.\n  -h --help       : Help on a specific command.\n\n                                                                    Valid\n                                                                    actions\n                                                                    are\n                                                                    composed\n                                                                    of a verb\n                                                                    and an\n                                                                    optional\n                                                                    direct\n                                                                    object:\n-    sdk              : Displays the SDK Manager window.\n-    avd              : Displays the AVD Manager window.\n-   list              : Lists existing targets or virtual devices.\n-   list avd          : Lists existing Android Virtual Devices.\n-   list target       : Lists existing targets.\n-   list device       : Lists existing devices.\n-   list sdk          : Lists remote SDK repository.\n- create avd          : Creates a new Android Virtual Device.\n-   move avd          : Moves or renames an Android Virtual Device.\n- delete avd          : Deletes an Android Virtual Device.\n- update avd          : Updates an Android Virtual Device to match the folders\n                        of a new SDK.\n- create project      : Creates a new Android project.\n- update project      : Updates an Android project (must already have an\n                        AndroidManifest.xml).\n- create test-project : Creates a new Android project for a test package.\n- update test-project : Updates the Android project for a test package (must\n                        already have an AndroidManifest.xml).\n- create lib-project  : Creates a new Android library project.\n- update lib-project  : Updates an Android library project (must already have\n                        an AndroidManifest.xml).\n- create uitest-project: Creates a new UI test project.\n- update adb          : Updates adb to support the USB devices declared in the\n                        SDK add-ons.\n- update sdk          : Updates the SDK by suggesting new platforms to install\n                        if available.\n',
  stderr: '',
  exitCode: 0 }
Exec mono --version
 stdout:
 stderr: 'mono' is not recognized as an internal or external command,
operable program or batch file.

Exec git --version
 stdout: git version 2.6.1.windows.1

 stderr:
Exec gradle -v
 stdout:
 stderr: 'gradle' is not recognized as an internal or external command,
operable program or batch file.

Exec "C:\Program Files\Java\jdk1.8.0_31\bin\javac" -version
 stdout:
 stderr: javac 1.8.0_31

System information:
{ procInfo: 'nativescript/2.2.1',
  platform: 'win32',
  os: 'Windows 8.1 Pro 6.3.9600',
  shell: 'C:\\WINDOWS\\system32\\cmd.exe',
  dotNetVer: '4.5.51650',
  procArch: 'x64',
  nodeVer: 'v4.5.0',
  npmVer: '2.15.9',
  javaVer: '1.8.0',
  nodeGypVer: null,
  xcodeVer: null,
  xcodeprojGemLocation: null,
  itunesInstalled: false,
  cocoapodVer: null,
  adbVer: 'Android Debug Bridge version 1.0.36',
  androidInstalled: true,
  monoVer: null,
  gitVer: '2.6.1.windows.1',
  gradleVer: null,
  javacVersion: '1.8.0_31' }
Starting watch on killswitch C:\Users\MyUserName\AppData\Local\Temp\MyUserName\KillSwitches\cli
Initializing analytics statuses.
Analytics statuses:
{ TrackFeatureUsage: 1, TrackExceptions: 0 }
Trying to track feature 'Non-interactive' with value 'build'.
Looking for project in 'D:\git\holsa-app'
Project directory is 'D:\git\holsa-app'.
Analytics statuses:
{ TrackFeatureUsage: 1, TrackExceptions: 0 }
Trying to track feature 'Non-interactive' with value 'build|android'.
Hooks directories: [ 'C:\\Users\\MyUserName\\AppData\\Roaming\\npm\\node_modules\\nativescript\\lib\\hooks',
  'C:\\Users\\MyUserName\\AppData\\Roaming\\npm\\node_modules\\nativescript\\lib\\common\\hooks',
  'D:\\git\\holsa-app\\hooks' ]
BeforeHookName for command prepare is before-prepare
Existing AndroidManifest.xml is correct.
Existing AndroidManifest.xml is correct.
spawn: D:\android-sdk\tools\android.bat "list" "targets"
Result when throw error is false:
{ stdout: 'Available Android targets:\n----------\nid: 1 or "android-23"\n     Name: Android 6.0\n     Type: Platform\n     API level: 23\n     Revision: 3\n     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in, AndroidWearRound, AndroidWearRound360x360, AndroidWearRound400x400, AndroidWearRound480x480, AndroidWearRoundChin320x290, AndroidWearRoundChin320x300, AndroidWearRoundChin360x325, AndroidWearRoundChin360x326, AndroidWearRoundChin360x330, AndroidWearSquare, AndroidWearSquare240x240, AndroidWearSquare320x320, AndroidWearRound, AndroidWearRound360x360, AndroidWearRound400x400, AndroidWearRound480x480, AndroidWearRoundChin320x290, AndroidWearRoundChin320x300, AndroidWearRoundChin360x325, AndroidWearRoundChin360x326, AndroidWearRoundChin360x330, AndroidWearSquare, AndroidWearSquare240x240, AndroidWearSquare320x320\n Tag/ABIs : android-tv/armeabi-v7a, android-tv/x86, android-wear/armeabi-v7a, android-wear/x86, default/armeabi-v7a, default/x86, default/x86_64\n----------\nid: 2 or "android-24"\n     Name: Android 7.0\n     Type: Platform\n     API level: 24\n     Revision: 2\n     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in, AndroidWearRound, AndroidWearRound360x360, AndroidWearRound400x400, AndroidWearRound480x480, AndroidWearRoundChin320x290, AndroidWearRoundChin320x300, AndroidWearRoundChin360x325, AndroidWearRoundChin360x326, AndroidWearRoundChin360x330, AndroidWearSquare, AndroidWearSquare240x240, AndroidWearSquare320x320, AndroidWearRound, AndroidWearRound360x360, AndroidWearRound400x400, AndroidWearRound480x480, AndroidWearRoundChin320x290, AndroidWearRoundChin320x300, AndroidWearRoundChin360x325, AndroidWearRoundChin360x326, AndroidWearRoundChin360x330, AndroidWearSquare, AndroidWearSquare240x240, AndroidWearSquare320x320\n Tag/ABIs : android-tv/x86, android-wear/armeabi-v7a, android-wear/x86, default/arm64-v8a, default/armeabi-v7a, default/x86, default/x86_64\n----------\nid: 3 or "Google Inc.:Google APIs:23"\n     Name: Google APIs\n     Type: Add-On\n     Vendor: Google Inc.\n     Revision: 1\n     Description: Android + Google APIs\n     Based on Android 6.0 (API level 23)\n     Libraries:\n      * com.android.future.usb.accessory (usb.jar)\n          API for USB Accessories\n      * com.google.android.media.effects (effects.jar)\n          Collection of video effects\n      * com.google.android.maps (maps.jar)\n          API for Google Maps\n     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in, AndroidWearRound, AndroidWearRound360x360, AndroidWearRound400x400, AndroidWearRound480x480, AndroidWearRoundChin320x290, AndroidWearRoundChin320x300, AndroidWearRoundChin360x325, AndroidWearRoundChin360x326, AndroidWearRoundChin360x330, AndroidWearSquare, AndroidWearSquare240x240, AndroidWearSquare320x320, AndroidWearRound, AndroidWearRound360x360, AndroidWearRound400x400, AndroidWearRound480x480, AndroidWearRoundChin320x290, AndroidWearRoundChin320x300, AndroidWearRoundChin360x325, AndroidWearRoundChin360x326, AndroidWearRoundChin360x330, AndroidWearSquare, AndroidWearSquare240x240, AndroidWearSquare320x320\n Tag/ABIs : google_apis/armeabi-v7a, google_apis/x86, google_apis/x86_64\n',
  stderr: '',
  exitCode: 0 }
Available Android targets:
----------
id: 1 or "android-23"
     Name: Android 6.0
     Type: Platform
     API level: 23
     Revision: 3
     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in, AndroidWearRound, AndroidWearRound360x360, AndroidWearRound400x400, AndroidWearRound480x480, AndroidWearRoundChin320x290, AndroidWearRoundChin320x300, AndroidWearRoundChin360x325, AndroidWearRoundChin360x326, AndroidWearRoundChin360x330, AndroidWearSquare, AndroidWearSquare240x240, AndroidWearSquare320x320, AndroidWearRound, AndroidWearRound360x360, AndroidWearRound400x400, AndroidWearRound480x480, AndroidWearRoundChin320x290, AndroidWearRoundChin320x300, AndroidWearRoundChin360x325, AndroidWearRoundChin360x326, AndroidWearRoundChin360x330, AndroidWearSquare, AndroidWearSquare240x240, AndroidWearSquare320x320
 Tag/ABIs : android-tv/armeabi-v7a, android-tv/x86, android-wear/armeabi-v7a, android-wear/x86, default/armeabi-v7a, default/x86, default/x86_64
----------
id: 2 or "android-24"
     Name: Android 7.0
     Type: Platform
     API level: 24
     Revision: 2
     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in, AndroidWearRound, AndroidWearRound360x360, AndroidWearRound400x400, AndroidWearRound480x480, AndroidWearRoundChin320x290, AndroidWearRoundChin320x300, AndroidWearRoundChin360x325, AndroidWearRoundChin360x326, AndroidWearRoundChin360x330, AndroidWearSquare, AndroidWearSquare240x240, AndroidWearSquare320x320, AndroidWearRound, AndroidWearRound360x360, AndroidWearRound400x400, AndroidWearRound480x480, AndroidWearRoundChin320x290, AndroidWearRoundChin320x300, AndroidWearRoundChin360x325, AndroidWearRoundChin360x326, AndroidWearRoundChin360x330, AndroidWearSquare, AndroidWearSquare240x240, AndroidWearSquare320x320
 Tag/ABIs : android-tv/x86, android-wear/armeabi-v7a, android-wear/x86, default/arm64-v8a, default/armeabi-v7a, default/x86, default/x86_64
----------
id: 3 or "Google Inc.:Google APIs:23"
     Name: Google APIs
     Type: Add-On
     Vendor: Google Inc.
     Revision: 1
     Description: Android + Google APIs
     Based on Android 6.0 (API level 23)
     Libraries:
      * com.android.future.usb.accessory (usb.jar)
          API for USB Accessories
      * com.google.android.media.effects (effects.jar)
          Collection of video effects
      * com.google.android.maps (maps.jar)
          API for Google Maps
     Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in, AndroidWearRound, AndroidWearRound360x360, AndroidWearRound400x400, AndroidWearRound480x480, AndroidWearRoundChin320x290, AndroidWearRoundChin320x300, AndroidWearRoundChin360x325, AndroidWearRoundChin360x326, AndroidWearRoundChin360x330, AndroidWearSquare, AndroidWearSquare240x240, AndroidWearSquare320x320, AndroidWearRound, AndroidWearRound360x360, AndroidWearRound400x400, AndroidWearRound480x480, AndroidWearRoundChin320x290, AndroidWearRoundChin320x300, AndroidWearRoundChin360x325, AndroidWearRoundChin360x326, AndroidWearRoundChin360x330, AndroidWearSquare, AndroidWearSquare240x240, AndroidWearSquare320x320
 Tag/ABIs : google_apis/armeabi-v7a, google_apis/x86, google_apis/x86_64

Directories found in D:\android-sdk\build-tools are 23.0.2, 23.0.3, 24.0.0, 24.0.2
Versions found in D:\android-sdk\build-tools are 23.0.2, 23.0.3, 24.0.0, 24.0.2
Selected version is:  23.0.3
Selected targetSdk is: 23
Directories found in D:\android-sdk\extras\android\m2repository\com\android\support\appcompat-v7 are 18.0.0, 19.0.0, 19.0.1, 19.1.0, 20.0.0, 21.0.0, 21.0.2, 21.0.3, 22.0.0, 22.1.0, 22.1.1, 22.2.0, 22.2.1, 23.0.0, 23.0.1, 23.1.0, 23.1.1, 23.2.0, 23.2.1, 23.3.0, 23.4.0, 24.0.0, 24.0.0-alpha1, 24.0.0-alpha2, 24.0.0-beta1, 24.1.0, 24.1.1, 24.2.0, maven-metadata.xml, maven-metadata.xml.md5, maven-metadata.xml.sha1
Versions found in D:\android-sdk\extras\android\m2repository\com\android\support\appcompat-v7 are 18.0.0, 19.0.0, 19.0.1, 19.1.0, 20.0.0, 21.0.0, 21.0.2, 21.0.3, 22.0.0, 22.1.0, 22.1.1, 22.2.0, 22.2.1, 23.0.0, 23.0.1, 23.1.0, 23.1.1, 23.2.0, 23.2.1, 23.3.0, 23.4.0, 24.0.0, 24.0.0, 24.0.0, 24.0.0, 24.1.0, 24.1.1, 24.2.0
Selected version is:  23.4.0
Selected AppCompat version is: 23.4.0
Project successfully prepared (android)
AfterHookName for command prepare is after-prepare
spawn: D:\git\holsa-app\platforms\android\gradlew.bat "buildapk" "-PcompileSdk=android-23" "-PtargetSdk=23" "-PbuildToolsVersion=23.0.3" "-PsupportVersion=23.4.0"

:config phase:  createDefaultIncludeFiles
        +found plugins: tns-core-modules-widgets

:config phase:  createPluginsConfigFile
         Creating product flavors include.gradle file in D:\git\holsa-app\platforms\android/configurations folder...

:config phase:  pluginExtend
        +applying configuration from: D:\git\holsa-app\platforms\android\configurations\include.gradle
        +applying configuration from: D:\git\holsa-app\platforms\android\configurations\tns-core-modules-widgets\include.gradle

:config phase:  copyAarDependencies

:config phase:  addAarDependencies
        +adding dependency: D:\git\holsa-app\platforms\android\libs\aar\nativescript.aar
        +adding dependency: D:\git\holsa-app\platforms\android\libs\aar\widgets-release.aar
Incremental java compilation is an incubating feature.
:preBuild UP-TO-DATE
:preF0DebugBuild UP-TO-DATE
:checkF0DebugManifest
:preF0ReleaseBuild UP-TO-DATE
:prepareComAndroidSupportAnimatedVectorDrawable2340Library UP-TO-DATE
:prepareComAndroidSupportAppcompatV72340Library UP-TO-DATE
:prepareComAndroidSupportSupportV42340Library UP-TO-DATE
:prepareComAndroidSupportSupportVectorDrawable2340Library UP-TO-DATE
:prepareAppCompanyNameRuntimeUnspecifiedLibrary UP-TO-DATE
:prepareNativescriptLibrary UP-TO-DATE
:prepareWidgetsReleaseLibrary UP-TO-DATE
:prepareF0DebugDependencies
:compileF0DebugAidl UP-TO-DATE
:compileF0DebugRenderscript UP-TO-DATE
:generateF0DebugBuildConfig UP-TO-DATE
:cleanLocalAarFiles
:ensureMetadataOutDir
:collectAllJars
:setProperties
:asbg:generateInterfaceNamesList
:asbg:runAstParser UP-TO-DATE
:asbg:generateBindings UP-TO-DATE
:mergeF0DebugShaders UP-TO-DATE
:compileF0DebugShaders UP-TO-DATE
:generateF0DebugAssets UP-TO-DATE
:mergeF0DebugAssets UP-TO-DATE
:generateF0DebugResValues UP-TO-DATE
:generateF0DebugResources UP-TO-DATE
:mergeF0DebugResources UP-TO-DATE
:processF0DebugManifest UP-TO-DATE
:processF0DebugResources UP-TO-DATE
:generateF0DebugSources UP-TO-DATE
:incrementalF0DebugJavaCompilationSafeguard UP-TO-DATE
:compileF0DebugJavaWithJavac UP-TO-DATE
:compileF0DebugNdk UP-TO-DATE
:compileF0DebugSources UP-TO-DATE
:buildMetadataException in thread "main" java.lang.IllegalArgumentException: Class com.tns.TypeIDs conflict: D:\git\holsa-app\platforms\android\build\intermediates\exploded-aar\nativescript\jars\classes.jar and D:\git\holsa-app\platforms\android\build\intermediates\exploded-aar\AppCompanyName\runtime\unspecified\jars\classes.jar
        at com.telerik.metadata.ClassRepo.cacheJarFile(ClassRepo.java:21)
        at com.telerik.metadata.Builder.build(Builder.java:39)
        at com.telerik.metadata.Generator.main(Generator.java:44)
 FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':buildMetadata'.
> Process 'command 'C:\Program Files\Java\jdk1.8.0_31\bin\java.exe'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 17.428 secs
Error: Command D:\git\holsa-app\platforms\android\gradlew.bat failed with exit code 1
    at FiberFuture.Future.wait (C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\node_modules\fibers\future.js:566:15)
    at C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\lib\common\errors.js:128:33
    at Function.settle (C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\node_modules\fibers\future.js:249:26)
    at FiberFuture.Future.wait (C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\node_modules\fibers\future.js:565:10)
    at C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\lib\common\services\commands-service.js:84:106
    at Function.settle (C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\node_modules\fibers\future.js:249:26)
    at FiberFuture.Future.wait (C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\node_modules\fibers\future.js:565:10)
    at C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\lib\common\yok.js:208:124
    at Function.settle (C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\node_modules\fibers\future.js:249:26)
    at FiberFuture.Future.wait (C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\node_modules\fibers\future.js:565:10)
    at C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\lib\common\services\commands-service.js:51:55
    at Function.settle (C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\node_modules\fibers\future.js:249:26)
    at FiberFuture.Future.wait (C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\node_modules\fibers\future.js:565:10)
    at C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\lib\common\errors.js:128:33
    at Function.settle (C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\node_modules\fibers\future.js:249:26)
    at FiberFuture.Future.wait (C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\node_modules\fibers\future.js:565:10)
    - - - - -
    at ChildProcess.<anonymous> (C:\Users\MyUserName\AppData\Roaming\npm\node_modules\nativescript\lib\common\child-process.js:91:38)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at maybeClose (internal/child_process.js:829:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
Analytics statuses:
{ TrackFeatureUsage: 1, TrackExceptions: 0 }
Trying to track feature 'Non-interactive' with value 'help'.
List of registered commands: /?, appstore, appstore|upload, autocomplete, autocomplete|disable, autocomplete|enable, autocomplete|status, build, build|android, build|ios, create, debug, debug|android, debug|ios, deploy, dev-generate-help, dev-generate-messages, dev-post-install, dev-preuninstall, dev-test, dev-test|android, dev-test|ios, device, device|android, device|get-file, device|ios, device|list-applications, device|list-files, device|log, device|put-file, device|run, device|stop, device|uninstall, doctor, emulate, emulate|android, emulate|ios, error-reporting, help, info, init, install, livesync, platform, platform|add, platform|clean, platform|remove, platform|update, plugin, plugin|add, plugin|find, plugin|install, plugin|remove, plugin|search, plugin|update, prepare, publish, publish|ios, run, run|android, run|ios, test, test|android, test|init, test|ios, usage-reporting
Reading help for command 'build|android'. FileName is 'build-android.md'.
# build android
┌─────────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Usage   │ Synopsis                                                                                │
│ General │ $ tns build android [--compileSdk <API Level>] [--key-store-path <File Path> --key-store-password <Password> --key-store-alias <Name> --key-store-alias-password <Password>] [--release] [--static-bindings] [--copy-to <File Path>] │
└─────────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

Builds the project for Android and produces an APK that you can manually deploy on device or in the native emulator.

### Options

    * --compileSdk - Sets the Android SDK that will be used to build the project.
    * --release - If set, produces a release build. Otherwise, produces a debug build. When set, you must also specify the --key-store-* options.
    * --key-store-path - Specifies the file path to the keystore file (P12) which you want to use to code sign your APK. You can use the --key-store-* options along with --release to produce a signed release build. You need to specify all --key-store-* options.
    * --key-store-password - Provides the password for the keystore file specified with --key-store-path. You can use the --key-store-* options along with --release to produce a signed release build. You need to specify all --key-store-* options.
    * --key-store-alias - Provides the alias for the keystore file specified with --key-store-path. You can use the --key-store-* options along with --release to produce a signed release build. You need to specify all --key-store-* options.
    * --key-store-alias-password - Provides the password for the alias specified with --key-store-alias-password. You can use the --key-store-* options along with --release to produce a signed release build. You need to specify all --key-store-* options.
    * --copy-to - Specifies the file path where the built .apk will be copied. If it points to a non-existent directory, it will be created. If the specified value is directory, the original file name will be used.

### Attributes
<API Level> is a valid Android API level. For example: 22, 23.

Analytics statuses:
{ TrackFeatureUsage: 1, TrackExceptions: 0 }
Trying to track exception with message 'Command D:\git\holsa-app\platforms\android\gradlew.bat failed with exit code 1'.
AnalyticsInstallationID: 3ff34634-399a-4aa1-98da-ed65577f3ec6
monitor not started
monitor not started
monitor not started
monitor has started, connecting to http://5752dabccfc54c4ab82aea9626b7338e.monitor-eqatec.com/json.ashx
Analytics statuses:
{ TrackFeatureUsage: 1, TrackExceptions: 0 }
Trying to track feature 'NodeJSVersion' with value '4_5_0'.
Waiting for analytics to send information. Will check in a 1000ms.
Statistics was sent successfully (xhr).
Statistics was sent successfully (xhr).
Waiting for analytics to send information. Will check in a 1000ms. Remaining time is: 29000

Hi @progig,
The error you're seeing:
Class com.tns.TypeIDs conflict:
build\intermediates\exploded-aar\nativescript\jars\classes.jar and
build\intermediates\exploded-aar\AppCompanyName\runtime\unspecified\jars\classes.jar

means you have two competing jars. Try searching for nativescript.jar and if you find it delete it and run the build again.
It would be really helpful if you to send us a way to reproduce your problem so we can help you. For future reference please follow the issue template we provided to help us help you.

Hi Plamen5kov,
Thanks for responding. I searched for nativescript.jar on my machine, but couldn't find it.
To reproduce the problem, upgrade nativescript from version 1.7 to 2.2.1 and try to (re)build an existing project with tns build android
I also tried to build the old version of sample-Groceries I had on disk, same problem occurred. After deleting it and cloning it again (newest version) , it built just fine.

Sorry @progig, I couldn't reproduce your problem. The steps I followed wre:

tns create oldapp (using cli 1.7.0)
cd oldapp
tns paltform add android (using cli 1.7.0)
tns build android (using cli 2.2.1)

I successfully reproduced your problem only when I forcefully moved the /platforms/android/libs/nativescript.jar into the new project template by doing:

tns create oldapp (using cli 1.7.0)
cd oldapp
tns paltform add android (using cli 2.2.1)
cp nativescript.jar ./platforms/android/ (nativescript jar came from the 1.7.0 template)
tns build android (using cli 2.2.1)

That means you have a nativescript.jar or classes.jar leftover in platforms/android or node_modules folder.
How you can try and fix this issue?

Try searching nativescript.jar inside of your projects folder and delete it.
Try to find which two jars contain: com.tns.TypeIDs class and remove the file not in /pltforms/android/ folder.
Provide us with a sample repo that reproduces the problem, so we can figure it out.

@Plamen5kov, thanks for taking the time to help me.

That means you have a nativescript.jar or classes.jar leftover in platforms/android or node_modules folder.

How can that be? I've removed both the platforms/android and node_modules folder with tns platform remove android and rm -Rf node_modules before building.

Try searching nativescript.jar inside of your projects folder and delete it.

I couldn't find such a file on my machine

Try to find which two jars contain: com.tns.TypeIDs class and remove the file not in /pltforms/android/ folder.

I tried to find that class in the jars in my project folder, but there's no such class in the jar files I found.

Provide us with a sample repo that reproduces the problem, so we can figure it out.

Please see the attachment for the repo
holsa-app.zip

@Plamen5kov
FYI and what it's worth: after building I see 2 different classes.jar files of different size:
/platforms/android/src/F0/widgets-release.aar size: 86.562 bytes
/platforms/android/libs/runtime-libs/nativescript.aar size: 86.424 bytes

@progig I was able to reproduce this erroneous behavior - as it turns out, you had the android runtime as both a platform, and a dependency of your project.
A simple way to fix this is to delete "tns-android": "^2.2.0" from your dependencies object in your package.json.
Make sure to delete both node_modules and the platforms dirs before running your app to delete any leftovers of the faulty module.

@Pip3r4o
Thanks! You made my day!
Still I wonder how "tns-android": "^2.2.0" ended up as a dependency object in my package.json.
I'm pretty sure I didn't put it there myself...

I have the same issue and deleting  "nativescript": {
"id": "org.nativescript.HelloWorld",
"tns-android": {
"version": "2.5.0"
} no fixe like this
`C:\Users\cvega.BI\Desktop@NGAndroid\HelloWorld>tns run android
Executing before-prepare hook from<EMAIL_ADDRESS>Preparing project...
Unzipping C:\Users\cvega.BI.gradle\wrapper\dists\gradle-2.10-bin\baigpnfu14tdk6ztbfwcl8275\gradle-2.10-bin.zip to C:\Users\cvega.BI.gradle\wrapper\dists\gradle-2.10-bin\baigpnfu14tdk6ztbfwcl8275
Exception in thread "main" java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:219)
at java.util.zip.ZipFile.(ZipFile.java:149)
at java.util.zip.ZipFile.(ZipFile.java:163)
at org.gradle.wrapper.Install.unzip(Install.java:159)
at org.gradle.wrapper.Install.access$500(Install.java:26)
at org.gradle.wrapper.Install$1.call(Install.java:69)
at org.gradle.wrapper.Install$1.call(Install.java:46)
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:65)
at org.gradle.wrapper.Install.createDist(Install.java:46)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:126)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
Processing node_modules failed. Error: Command<EMAIL_ADDRESS>failed with exit code 1
Sending exception report (press Ctrl+C to stop).....
C:\Users\cvega.BI\Desktop@NGAndroid\HelloWorld>`

@cesarvega looks like you have a faulty archive of the gradle wrapper, it happens at times as a result of poor connection. Navigate to your %USER_HOME%.gradle/ and delete the wrapper/dists/gradle-2.10-bin directory to allow the wrapper to be redownloaded.

Thanks that fixed it
On Thu, Apr 20, 2017 at 3:09 PM, Peter Kanev<EMAIL_ADDRESS>wrote:

@cesarvega https://github.com/cesarvega looks like you have a faulty
archive of the gradle wrapper, it happens at times as a result of poor
connection. Navigate to your %USER_HOME%.gradle/ and delete the
wrapper/dists/gradle-2.10-bin directory to allow the wrapper to be
redownloaded.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NativeScript/android-runtime/issues/553#issuecomment-295862685,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABwmodjphedy-3XEMKdqskiZ2QXKLrNJks5rx61YgaJpZM4J4B6y
.

--
Cesar Vega
Software Engineer
Where Great Brands Begin®
http://www.brandinstitute.com/images/logo.jpg
http://www.brandinstitute.com/images/logo.jpg

@cesarvega had the same problem just now. Used the sdk 22 with nativescript 2.5.0. Did what @Pip3r4o said but had the same exact problem. No problems building for sdk 23.

@Dimitrievskislavcho What cesarvega described has little to do with the sdk used to build a project.
As for the gradle.bat exited with error code 1 - this is the generic message output whenever an android build fails.

tns run android
Executing before-prepare hook from C:\projet\hello-world\hooks\before-prepare\nativescript-dev-android-snapshot.js
Preparing project...
Unzipping C:\Users\Khouloud.gradle\wrapper\dists\gradle-2.10-bin\baigpnfu14tdk6ztbfwcl8275\gradle-2.10-bin.zip to C:\Users\Khouloud.gradle\wrapper\dists\gradle-2.10-bin\baigpnfu14tdk6ztbfwcl8275
Exception in thread "main" java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:219)
at java.util.zip.ZipFile.(ZipFile.java:149)
at java.util.zip.ZipFile.(ZipFile.java:163)
at org.gradle.wrapper.Install.unzip(Install.java:159)
at org.gradle.wrapper.Install.access$500(Install.java:26)
at org.gradle.wrapper.Install$1.call(Install.java:69)
at org.gradle.wrapper.Install$1.call(Install.java:46)
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:65)
at org.gradle.wrapper.Install.createDist(Install.java:46)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:126)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
Processing node_modules failed. Error: Command C:\projet\hello-world\platforms\android\gradlew.bat failed with exit code 1
I have the same issue :(

@khalkhaloud I've already explained the fix above. Simply follow the steps and you are good to go.

@Pip3r4o  i have  delete "tns-android": "^2.2.0" from your dependencies object in my  package.json But I have the same problem :(

@khalkhaloud you aren't reading correctly.
https://github.com/NativeScript/android-runtime/issues/553#issuecomment-295862685

can you explain more  please

C:\prjt\Groceries
λ tns run android
Skipping prepare.
Searching for devices...
Starting Android emulator with image Nexus_5X_API_25
Waiting for emulator device initialization.......
Building project...
Downloading https://services.gradle.org/distributions/gradle-2.10-bin.zip
..........................................................................................................................................................................................................................................................................................
Unzipping C:\Users\Khouloud.gradle\wrapper\dists\gradle-2.10-bin\baigpnfu14tdk6ztbfwcl8275\gradle-2.10-bin.zip to C:\Users\Khouloud.gradle\wrapper\dists\gradle-2.10-bin\baigpnfu14tdk6ztbfwcl8275
Exception in thread "main" java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:219)
at java.util.zip.ZipFile.(ZipFile.java:149)
at java.util.zip.ZipFile.(ZipFile.java:163)
at org.gradle.wrapper.Install.unzip(Install.java:159)
at org.gradle.wrapper.Install.access$500(Install.java:26)
at org.gradle.wrapper.Install$1.call(Install.java:69)
at org.gradle.wrapper.Install$1.call(Install.java:46)
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:65)
at org.gradle.wrapper.Install.createDist(Install.java:46)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:126)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
Command C:\prjt\Groceries\platforms\android\gradlew.bat failed with exit code 1
plz help me :(

i redownloaded the wrapper but nothing change !! the same error again
2017-04-28 14:06 GMT+02:00 Peter Kanev<EMAIL_ADDRESS>
@khalkhaloud https://github.com/khalkhaloud I am repeating myself here,
but there you go -> #553 (comment)
https://github.com/NativeScript/android-runtime/issues/553#issuecomment-295862685
looks like you have a faulty archive of the gradle wrapper, it happens at
times as a result of poor connection. Navigate to your %USER_HOME%.gradle/
and delete the wrapper/dists/gradle-2.10-bin directory to allow the wrapper
to be redownloaded.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NativeScript/android-runtime/issues/553#issuecomment-297981130,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AavpyD1j_WALr7qCc1VWQ3Uv8SSNC2p-ks5r0dYrgaJpZM4J4B6y
.

@khalkhaloud Unfortunately corrupted gradle wrapper archives is not something that we can fix, since we do not manage them - https://discuss.gradle.org/t/making-the-wrapper-more-resilient-to-corrupted-downloads/22066/4. Gradle are aware of these issues, and are working on resolving them.
Your best bet is to try to redownload the wrapper multiple times, or follow the gradle wrapper guidelines at https://docs.gradle.org/current/userguide/gradle_wrapper.html.
If you wish to, you could also install the release candidate version 3.0 tns platform add android@rc which distributes a different version of the gradle wrapper. We cannot guarantee however that the wrapper package will be valid.

I had the same issue and with gradle 3.3. Apparently, when I installed nativescript cli it wasn't downloaded properly. To fix the problem I removed entire folder .grandle in my USER_HOME directory and run the command 'tsn run' again. It downloaded new gradle and it works just fine now.

@Nogostradamus  Yeah that works for me some times but sometimes it does not , I keep getting errors for no reason I delete the gradle but my app its mot working anymore this is so frustrating
      `* What went wrong:
      Execution failed for task ':mergeF0F1F2F3F4DebugResources'.
      > Error: Failed to crunch file C:\Users\cvega.BI\Desktop\@SIDEKICK\nativescript-marketplace-
        demo\platforms\android\build\intermediates\exploded-aar\com.google.android.gms\play-services-
         base\10.2.6\res\drawable-xxhdpi-
         v4\common_google_signin_btn_icon_light_normal_background.9.png into
       C:\Users\cvega.BI\Desktop\@SIDEKICK\nativescript-marketplace-
       demo\platforms\android\build\intermediates\res\merged\F0F1F2F3F4\debug\drawable-xxhdpi-
       v4\common_google_signin_btn_icon_light_normal_background.9.png

     * Try:
     Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more
     log output.
     Unable to apply changes on device: emulator-5554. Error is: Command gradlew.bat failed with exit
     code 1.`

@cesarvega we are in the process of updating the Gradle version, which supposedly has fixes for those problems you are facing. I'll let you know when they hit the master branch so you can test the changes!

Any ideas?
G:\Escritorio\nativescript\test-firebase\dist>tns run android
Searching for devices...
Skipping prepare.
Building project...
Gradle build...
         + setting applicationId
         + applying user-defined configuration from G:\Escritorio\nativescript\test-firebase\dist\app\App_Resources\Android\app.gradle
         + adding nativescript runtime package dependency: nativescript-optimized-with-inspector
         + adding aar plugin dependency: G:\Escritorio\nativescript\test-firebase\dist\node_modules\nativescript-plugin-firebase\platforms\android\firebase-release.aar
         + adding aar plugin dependency: G:\Escritorio\nativescript\test-firebase\dist\node_modules\nativescript-plugin-firebase-common\platforms\android\nativescript_plugin_firebase_common.aar
         + adding jar plugin dependency: G:\Escritorio\nativescript\test-firebase\dist\node_modules\nativescript-plugin-firebase-common\platforms\android\firebase-client-android-2.5.2.jar
         + adding aar plugin dependency: G:\Escritorio\nativescript\test-firebase\dist\node_modules\tns-core-modules-widgets\platforms\android\widgets-release.aar
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
C:\Users\Manuel\.gradle\caches\transforms-1\files-1.1\appcompat-v7-27.0.2.aar\a1f2d02a605d5a2aaa25afeb26781598\res\values-v26\values-v26.xml:9:5-12:13: AAPT: error: resource android:attr/colorError not found.

C:\Users\Manuel\.gradle\caches\transforms-1\files-1.1\appcompat-v7-27.0.2.aar\a1f2d02a605d5a2aaa25afeb26781598\res\values-v26\values-v26.xml:13:5-16:13: AAPT: error: resource android:attr/colorError not found.

C:\Users\Manuel\.gradle\caches\transforms-1\files-1.1\appcompat-v7-27.0.2.aar\a1f2d02a605d5a2aaa25afeb26781598\res\values-v26\values-v26.xml:17:5-93: AAPT: error: style attribute 'android:attr/keyboardNavigationCluster' not found.

C:\Users\Manuel\.gradle\caches\transforms-1\files-1.1\appcompat-v7-27.0.2.aar\a1f2d02a605d5a2aaa25afeb26781598\res\values\values.xml:252:5-69: AAPT: error: resource android:attr/fontStyle not found.

C:\Users\Manuel\.gradle\caches\transforms-1\files-1.1\appcompat-v7-27.0.2.aar\a1f2d02a605d5a2aaa25afeb26781598\res\values\values.xml:252:5-69: AAPT: error: resource android:attr/font not found.

C:\Users\Manuel\.gradle\caches\transforms-1\files-1.1\appcompat-v7-27.0.2.aar\a1f2d02a605d5a2aaa25afeb26781598\res\values\values.xml:252:5-69: AAPT: error: resource android:attr/fontWeight not found.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:processDebugResources'.
> Failed to process resources, see aapt output above for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 3s
Unable to apply changes on device: 1018679f. Error is: Command gradlew.bat failed with exit code 1.

G:\Escritorio\nativescript\test-firebase\dist>

Same problem here.. I deleted all the gradle files in C:/%USER/.gradle but no solution..
        + applying user-defined configuration from C:\wamp\www\ns-vue-tabs-auth                         \dist\app\App_Resources\Android\app.gradle          + add include.gradle from C:\wamp\www\ns-vue-tabs-auth\dist\node_module                         s\nativescript-background-http\platforms\android\include.gradle          + add include.gradle from C:\wamp\www\ns-vue-tabs-auth\dist\node_module                         s\nativescript-camera\platforms\android\include.gradle          + add include.gradle from C:\wamp\www\ns-vue-tabs-auth\dist\node_module                         s\nativescript-google-maps-sdk\platforms\android\include.gradle          + applying plugin configuration from C:\wamp\www\ns-vue-tabs-auth\dist\                         platforms\android\app\build\configurations\nativescript-background-http\include.                         gradle          + applying plugin configuration from C:\wamp\www\ns-vue-tabs-auth\dist\                         platforms\android\app\build\configurations\nativescript-camera\include.gradle          + applying plugin configuration from C:\wamp\www\ns-vue-tabs-auth\dist\                         platforms\android\app\build\configurations\nativescript-google-maps-sdk\include.                         gradle          + adding nativescript runtime package dependency: nativescript-optimize                         d          + adding aar plugin dependency: C:\wamp\www\ns-vue-tabs-auth\dist\node_                         modules\nativescript-background-http\platforms\android\nativescript_background_h                         ttp.aar          + adding aar plugin dependency: C:\wamp\www\ns-vue-tabs-auth\dist\node_                         modules\nativescript-camera\platforms\android\nativescript_camera.aar          + adding aar plugin dependency: C:\wamp\www\ns-vue-tabs-auth\dist\node_                         modules\nativescript-google-maps-sdk\platforms\android\nativescript_google_maps_                         sdk.aar          + adding aar plugin dependency: C:\wamp\www\ns-vue-tabs-auth\dist\node_                         modules\tns-core-modules-widgets\platforms\android\widgets-release.aar false Unable to apply changes on device: emulator-5554. Error is: Command gradlew.bat                          failed with exit code 1.
I'll remove the nativescript-google-maps-sdk plugin and try with the other one...

Hi @wa05 , I think I have found a solution, but I have to try more deeply.
Steps

npm run clean
template\app\App_Resources\Android\app.gradle

android {
  compileSdkVersion 26
  buildToolsVersion "26.0.0-beta2"
  defaultConfig {
    multiDexEnabled true
    generatedDensities = []
    applicationId = "___XXX___"
  }
  aaptOptions {
    additionalParameters "--no-version-vectors"
  }
}

Being XXX whatever you have.
As you can see, I have added compileSdkVersion and buildToolsVersion. Also multiDexEnabled  because with SDK a new error appears.
Try it!

I continue having the same error

I still have this issue. I can't build for android. I've tried all the solutions above. Any idea?

Getting the same error here.


Kernel Uncompress Failure on Raspberry Pi 4 in Scarthgap Yocto Release

Description:
Issue:
Encountering a error during kernel uncompression on the Raspberry Pi 4 when utilizing the Scarthgap Yocto Release and meta-raspberrypi layer on the master branch. This issue manifests specifically with kernel version 6.6 on the raspberrypi4 machine. Upon booting, following the u-boot initialization, the kernel uncompression process triggers an error, causing the board to enter a reboot loop.
Error Log from U-Boot:
U-Boot 2024.01 (Jan 08 2024 - 15:37:48 +0000)

DRAM:  628 MiB (effective 3.6 GiB)
RPI 4 Model B (0xc03111)
Core:  212 devices, 16 uclasses, devicetree: board
MMC:   mmcnr@7e300000: 1, mmc@7e340000: 0
Loading Environment from FAT... OK
In:    serial,usbkbd
Out:   serial,vidconsole
Err:   serial,vidconsole
Net:   eth0: ethernet@7d580000
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
PCI: Failed autoconfig bar 10
starting USB...
Bus xhci_pci: dm_pci_bus_to_phys: invalid physical address
xhci-pci init cannot map PCI mem bar
probe failed, error -5
No working controllers found
Hit any key to stop autoboot:  2  1  0
Card did not respond to voltage select! : -110
** Booting bootflow<EMAIL_ADDRESS>with script
Working FDT set to 273e2400
8520088 bytes read in 370 ms (22 MiB/s)
## Booting kernel from Legacy Image at 00080000 ...
   Image Name:   Linux-6.6.22-v7l
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    8520024 Bytes = 8.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 273e2400
   Booting using the fdt blob at 0x273e2400
Working FDT set to 273e2400
   Loading Kernel Image
uncompressed: uncompress error -28
Must RESET board to recover
resetting ...
B/

Observations:
Curiously, this issue does not persist when utilizing the raspberrypi4-64 variant. In this case, the kernel operates without encountering any issues.
Steps to Reproduce:
Utilize the Scarthgap Yocto Release on a Raspberry Pi 4.
Ensure the kernel version is 6.6.
Observe the boot process, noting the error during kernel uncompression.
Expected Behavior:
The kernel should uncompress successfully on the Raspberry Pi 4 using the Scarthgap Yocto Release, allowing the board to boot normally without encountering errors.
Additional Information:
This issue is specific to the raspberrypi4 machine and kernel version 6.6.
No similar issues have been observed with the raspberrypi4-64 variant.
When using the kernel 6.1 the problem does not occur.
Any insights or resolutions would be greatly appreciated.
Thank you for your attention to this matter.

For the record: I ran into the same situation with machine raspberrypi4 on Scarthgap and as described in this issue the board boots fine with image built for raspberrypi4-64.

I also see this error. Does anybody know if there is a workaround?

To add a little more info:
raspberrypi4-64 uses the Image format and the booti command
raspberrypi4 uses the uImage format and the bootm command
If you take the uImage and extract it to a zImage you can boot it with bootz. The extracted zImage is identical to the kernel built without u-boot support.
Doing some research the error uncompressed: uncompress error -28 can happen if the kernel is larger than CONFIG_SYS_BOOTM_LEN, the default is 8M, and the kernel we are trying to boot is 8.2M.
Setting CONFIG_SYS_BOOTM_LEN to a larger number or making the kernel smaller should fix that issue.
I am new to Yocto so I don't know how to change kernel u-boot options. But both use kconfig so I would expect that meta-raspberrypi handles both in the same way.

I just came across this issue, @ashlin4010 thanks for pointing out where the bug is.
To set CONFIG_SYS_BOOTM_LEN to a higher value, create a bbappend for u-boot like this:
File structure:
meta-your-layer/
├── recipes-bsp
│   └── u-boot
│       ├── files
│       │   └── memory_size.cfg
│       └── u-boot_%.bbappend

u-boot_%.bbappend:
FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
SRC_URI:append = " file://memory_size.cfg"

memory_size.cfg:
CONFIG_SYS_BOOTM_LEN=0x1000000

The memory_size.cfg is picked up by u-boot and merged into the config.


Fixed eye gaze pose transformation.

This fixes the eye gaze incorrectly being calculated, it now properly transforms into a normalized cartesian. This also fixes the edge-locking eye bug and properly uses the left and right eye datas.

@regzo2 Thanks!


Fix issue with container types using JsonSerializable as a value

Description
Redesigns JsonSerializableSerializer to add a serializer for JsonSerializable rather than a modifier. This is safe to do for serialization as toJson is an interface method that all instances will need to define. JsonSerializableDeserializer recently had a fix for a similar issue, that still needs to use the modifier pattern as not all JsonSerializable implementations must implement fromJson as that is a static method on the interface which most implementations hide with their own implementation.
The modifier pattern didn't work with serialization as collection types (List, Map, []) modifiers sometimes don't have enough information about the container type being serialized. They also use a different and more complex system than non-container value serialization for modifying.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.