Push notification permission fails on IOS 12 ?

For Discussion
Hello, I'm currently using react native 0.55.3 + IOS 12 beta version.
The following code works fine on IOS 10, but fails as soon as I update my iPad to IOS 12
const PushNotificationIOS = require("react-native").PushNotificationIOS;
getToken() {
    return new Promise((resolve, reject) => {
        PushNotificationIOS.requestPermissions(["alert", "badge", "sound"])
        .then(() => {
            PushNotificationIOS.addEventListener("register", token => {
                resolve(token);
            });
        });
    });
}

It is not even trying to ask user for the permission. I did get some kind of token back, but the token is totally useless, since no push notification is allowed to show up.
Interestingly, facebook's push notification works fine on IOS 12......

I've tried to follow the discussion template, could you reopen the issue or should I post a new one?


host: Support zero-downtime updates

Opening for early feedback on the approach.
All but the last 3 commits are in #1671 so will disappear once that is merged.

@titanous ready for a review (apologies for the large diff)

@titanous comments addressed (I've added a discoverd shutdown fix too)

Has this been tested to determine what happens to log streams (to disk and logaggregator) during/after the update? (no duplicate or dropped lines)

@titanous comments addressed, I've added a lot of small but related fixes, let me know if you would find them easier to review as separate PRs, but most have descriptions in the commit message.

What's left before we can merge this?

@titanous the only thing left is dealing with the possibility of getting EOF from the host API due to established connections not being closed (i.e. this discussion), but since the scheduler is now more robust (it will retry starting jobs on a host if it gets this error), I don't think this should prevent the PR from being merged.

LGTM!


Tagging dynatrace_web_application (Resource)

Describe the bug
There seems to be no way of tagging dynatrace_web_application Resource. These are Dynatrace Tags that are used within the Dynatrace Managament Zone rules. The user_tags are available but are for RUM. For example https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/resources/browser_monitor#tags
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Hello @yasin-amadmia-mck and @dmytro-malovany,
Your observation is correct - when it comes to tagging the REST API of Dynatrace is a bit inconsistent. Some resources allow for specifying the tags of the resource, some don't.
In order to tag a Web Application you can utilize the resource dynatrace_custom_tags, like in this example:
resource "dynatrace_custom_tags" "application_custom_tags" {
  entity_selector = "entityId(\"APPLICATION-################\")"
  tags {
    filter {
      context = "CONTEXTLESS"
      key     = "KeyA"
      value   = "ValueA"
    }
  }
}

Using the Entity Selector here, you can essentially target any kind of resource.
best regards,
Reinhard


Invalid context 0x0

Bug
App crashes a few seconds after launch when rendering linear gradient.
XCode logs after setting env var CG_CONTEXT_SHOW_BACKTRACE:
2019-05-31 15:15:25.613416+0200 MyApp[1460:164421] CGContextSetFillColorSpace: invalid context 0x0. Backtrace:
  <<redacted>+90>
   <<redacted>+228>
    <-[BVLinearGradientLayer drawInContext:]+84>
     <-[BVLinearGradientLayer display]+416>
      <<redacted>+208>
       <<redacted>+24>
        <<redacted>+320>
         <<redacted>+578>
          <<redacted>+162>
           <<redacted>+20>
            <<redacted>+282>
             <<redacted>+1358>
              <CFRunLoopRunSpecific+470>
               <CFRunLoopRunInMode+104>
                <GSEventRunModal+80>
                 <UIApplicationMain+150>
                  <main+70>
May 31 15:15:25  MyApp[1460] <Error>: CGContextSetFillColorSpace: invalid context 0x0. Backtrace:
	  <<redacted>+90>
	   <<redacted>+228>
	    <-[BVLinearGradientLayer drawInContext:]+84>
	     <-[BVLinearGradientLayer display]+416>
	      <<redacted>+208>
	       <<redacted>+24>
	        <<redacted>+320>
	         <<redacted>+578>
	          <<redacted>+162>
	           <<redacted>+20>
	            <<redacted>+282>
	             <<redacted>+1358>
	              <CFRunLoopRunSpecific+470>
	               <CFRunLoopRunInMode+104>
	                <GSEventRunModal+80>
	                 <UIApplicationMain+150>
	                  <main+70>
2019-05-31 15:15:25.616632+0200 MyApp[1460:164421] CGContextSetStrokeColorSpace: invalid context 0x0. Backtrace:
  <<redacted>+98>
   <<redacted>+228>
    <-[BVLinearGradientLayer drawInContext:]+84>
     <-[BVLinearGradientLayer display]+416>
      <<redacted>+208>
       <<redacted>+24>
        <<redacted>+320>
         <<redacted>+578>
          <<redacted>+162>
           <<redacted>+20>
            <<redacted>+282>
             <<redacted>+1358>
              <CFRunLoopRunSpecific+470>
               <CFRunLoopRunInMode+104>
                <GSEventRunModal+80>
                 <UIApplicationMain+150>
                  <main+70>

Environment info

React native info output:
  React Native Environment Info:
    System:
      OS: macOS 10.14.4
      CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
      Memory: 3.14 GB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 11.14.0 - ~/.nvm/versions/node/v11.14.0/bin/node
      Yarn: 1.15.2 - ~/.nvm/versions/node/v11.14.0/bin/yarn
      npm: 6.9.0 - ~/.nvm/versions/node/v11.14.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
      Android SDK:
        API Levels: 17, 22, 23, 24, 25, 26, 28
        Build Tools: 23.0.1, 23.0.3, 24.0.1, 24.0.2, 25.0.0, 25.0.2, 26.0.1, 26.0.2, 27.0.3, 28.0.1, 28.0.3
        System Images: android-17 | MIPS, android-17 | Google APIs ARM EABI v7a, android-23 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.4 AI-183.6<IP_ADDRESS>22156
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.1 => 16.6.1
      react-native: 0.58.6 => 0.58.6
    npmGlobalPackages:
      react-native-cli: 2.0.1
      react-native: 0.59.5

Library version: 2.5.4
Steps To Reproduce
Render a linear gradient. Non-deterministic, once every other app launch it crashes. Removing the rendering of the linear gradient component removes the issue.

I see the same issue in my app. It doesn't crash my app, but it breaks the layout. I integrated React Native in a Unity3d project and it started happening after I updated to the latest Unity version.
I noticed it has nothing to do with the gradient, I see that yoga is failing to determine the correct size of an element.
CGContextSetFillColorSpace: invalid context 0x0. Backtrace:
<+228>
<+296>
<-[BVLinearGradientLayer drawInContext:]+96>
<-[BVLinearGradientLayer display]+508>
<+516>
<+580>
<+92>
<+32>
<+412>
<+1436>
<CFRunLoopRunSpecific+552>
<GSEventRunModal+100>
<UIApplicationMain+236>
<main+212>                <+4>
CGContextSetStrokeColorSpace: invalid context 0x0. Backtrace:
<+240>
<+296>
<-[BVLinearGradientLayer drawInContext:]+96>
<-[BVLinearGradientLayer display]+508>
<+516>
<+580>
<+92>
<+32>
<+412>
<+1436>
<CFRunLoopRunSpecific+552>
<GSEventRunModal+100>
<UIApplicationMain+236>
<main+212>                <+4>

I believe I found the issue, it was caused by a component that had large dimensions (300 x 100.000 logical pixels) which iOS didn't want to allocate memory for. The issue trickled down from the methods display and drawInContext in BVLinearGradientLayer.m.
It should be fairly trivial to check for this and log the issue in a comprehensible way, but I'm afraid I'm not familiar with how to best log it.


The data service Schema types are not complete

The Schema interface describes properties as Record<string, any> but should be Record<string, TypeConfiguration>

The interface for ObjectConfiguration is missing the additionalProperties property.
Should contain something like:
interface ObjectConfiguration {
  type: 'object';
  // .... rest of the definition
  additionalProperties: TypeConfiguration;
}

Fixed in 8.4.1


[MM-39310] Add setTimeout to new server modal pop to make sure it renders correctly.

Summary
On Linux, the new server modal wasn't popping correctly due to some timing issue with when the BrowserView was added, and the user was not able to manually pop it. This PR fixes the issue by adding a setTimeout so that the modal pops slightly later.
Ticket Link
https://mattermost.atlassian.net/browse/MM-39310
Fixes #1808
Release Note
Fixed the new server modal not be accessible on Linux when no other servers exist.

Cherry pick is scheduled.


Unable to issue/renew certificate anymore

Recently I started having issues with the certificate renewal (worked a few months ago, but not any longer).
I0809 13:34:52.061900       1 main.go:78] Present: fqdn=_acme-challenge.somedomain.net., zone=somedomain.net., key=qUXCrf7evXjIQfBWEItLIwuCxzoDQCOpK5aRitCSMpc
I0809 13:34:52.061924       1 main.go:189] recordName: ResolvedZone=somedomain.net., ResolvedFQDN=_acme-challenge.somedomain.net.
I0809 13:34:52.066250       1 active24.go:37] FindTxtRecord: name=_acme-challenge, text=qUXCrf7evXjIQfBWEItLIwuCxzoDQCOpK5aRitCSMpc
E0809 13:34:52.295304       1 active24.go:41] "invalid API response" err="invalid response from api: 404" code="404 404"

Deployed using Helm chart v1.0.1 with image set to ghcr.io/rkosegi/cert-manager-webhook-active24:v1.0.1 (you've got it wrong in the v1.0.1 - it points to rkosegi/cert-manager-webhook-active24:1.0.1 which doesn't exist).
API key is correct (issued last year, still valid)
ClusterIssuer also appears correct (created last year, not changed since then)

Do you know if the Active24 API hasn't changed in any way?
I looked at https://api.active24.com/swagger-ui.html and tried some manual requests to get some records (using my API key) - those work and it appears to match what the https://github.com/rkosegi/active24-go/blob/main/active24/dns.go does. But maybe I'm missing something.
Note that I can't find the expected TXT record there - based on the above piece of log it should be at least created, but there's nothing visible in those records. Maybe even that part doesn't work properly, or it's just a consequence.

Petr, thanks for bug report.
I can confirm issue. Not sure about root cause, I'm sure this worked before.
Even stranger is what you pointed out already, swagger UI or curl are producing OK results while pretty same requests coming from this app not. Let me do more tests

This should be fixed in v1.0.2


Fix diffusion example imports.

Modulus Pull Request
Description
Updated diffusion example imports.
Checklist

[x] I am familiar with the Contributing Guidelines.
[ ] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[ ] The CHANGELOG.md is up to date with these changes.
[ ] An issue is linked to this pull request.

Dependencies

/blossom-ci

/blossom-ci

/blossom-ci


"About" tab is empty

The "About" tab is currently empty but should show

launcher README
launcher changelog
launcher license

How to reproduce:

Start the launcher from most recent develop branch
Select "About" tab
See that the "About" tab is empty

This is related to the changes done in #452, in particular commenting calls to updateGui().

Related to #462


wct fails locally on router suite

I cloned this to learn more about Polymer testing, but it is failing with below. Any ideas why it is failing? This is all on a local Linux  machine....no cloud. I use Chrome 53, not chromium.
four@localhost ~/github/ioweb2016 $ wct
Installing and starting Selenium server for local browsers
Selenium server running on port 48365
Web server running on port 2000 and serving from /home/four/github/ioweb2016
chrome 53                Beginning tests via http://localhost:2000/components/ioweb2016/generated-index.html?cli_browser_id=0
chrome 53                â app/scripts/helper/router_test.html Â» IOWA.Router_ Â» navigate runs page transition

  Cannot set property 'selectedPage' of undefined
    <unknown> at       Router.navigate at router.js:268:0
    <unknown> at   Context.<anonymous> at router_test.html:78:0

chrome 53                â app/scripts/helper/router_test.html Â» IOWA.Router_ Â» navigate updates router state

  Cannot set property 'selectedPage' of undefined
    <unknown> at       Router.navigate at router.js:268:0
    <unknown> at   Context.<anonymous> at router_test.html:107:0

chrome 53                â app/scripts/helper/router_test.html Â» IOWA.Router_ Â» runSubpageTransition

  Cannot read property 'selectedPage' of undefined
    <unknown> at                     <unknown> at router.js:229:0
    <unknown> at                   Object.then at router_test.html:131:0
    <unknown> at   Router.runSubpageTransition at router.js:223:0
    <unknown> at               Router.navigate at router.js:271:0
    <unknown> at           Context.<anonymous> at router_test.html:145:0

chrome 53 (5/0/3)

Note: I am not running the back end. But that shouldn't matter, correct? There should be mock data making the test suite independent?

We didn't use wct test this year. That's left over from https://github.com/GoogleChrome/ioweb2015

Oh, ok.... thanks! Did you replace wct with some other testing? Or did you decide to skip testing entirely for 2016?

We had backend tests but not frontend tests.

If I may ask, please, for my own learning. Since testing theories are constantly evolving:
What was the deciding factor in not testing the front end?
Was it because polymer is composed of Polymer elements that have already been tested? But that would leave the custom elements instance methods untested.
For E2E, I guess you could say that the router suite wct covered most of that?

Mainly because of time :)
The project is composed of a few 20% engineers that help out over the course of a few months. The site also goes through 5-6 phases (launches) that alter it quite a big during that time. It's a challenge to dev + write new tests + iterate for all those different short-lived pieces. The engineers are also working on session content, codelabs and other stuff for Google I/O in addition to working on the site.

:+1: This is valuable information, thank you so much!


enable user to have components side-by-side

maybe upon hover, show an extra button that toggles the component width?

(between full and half width?)
(between full, half-width, and 1/3?)

or maybe upon hover, show an extra button that toggles the component display: inline-block;?

only in the same context that the delete button gets showed for


[Feature]  Convert Package to Paclet

This PR converts the package into a paclet.

Documentation
Testing Resources (not working at the moment)

Note that TechNotes are formatted incorrectly in documentation, this does not seem to be an issue on my end, so I'll need to report this.

Closes #101


how to train the model

so i've created a pytorch model with this code:
model = UNet(n_channels=217,              num_classes=2,              use_bn=True,              mode='3D',              use_pooling=False              )
How do I actually train? My data is in two lists, original, and segmented (the first is the original and the second is the segmentation mask).
Additionally my image sizes are (217,512,512)

For more information, each of my lists has 20 images of size (217, 512, 512)

I tried model.forward() but i'm unsure of how to pass the masks and the original information to train.

Hi Palash,
The repository only contains code for the model. It is intended to be used by installing the model as a package and importing it in your training script. For pointers on how to create a training script and a custom dataset class, I'd suggest looking at the tutorials/examples from the PyTorch website: https://pytorch.org/tutorials/
Cheers,
Ishaan

Closing this issue, please open it if you need any further clarification.

So, I've made pretty good progress:
for epoch in range(max_epochs):
    # Training
    for local_batch, local_labels in training_generator:
        # Transfer to GPU
        local_batch, local_labels = local_batch.to(device), local_labels.to(device)

this is where i'm at. basically local_batch has the original and local_labels has the segmented image in it. I'm a bit confused how to actually fit it to your UNet though. Could you provide any insights?

nevermind fixed this issue.


Issue during release build - A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable

Description
Here's the issue that I've encountered during the release build of my app. I can't share the source code, so if you need anything to identify the problem, just ask me.
I was thinking that the issue is caused by the difference in Gradle versions between the one used by the framework and the one used by the dependencies.
Android gradle plugin: 7.4.2
Gradle: 8.0.1

But if that were the case, I shouldn't be able to build in debug mode.
Thank you in advance for the help provided
React Native Version
0.72.5
Output of npx react-native info
System:
  OS: macOS 13.4
  CPU: (8) arm64 Apple M1
  Memory: 85.11 MB / 8.00 GB
  Shell:
    version: 3.2.57
    path: /bin/bash
Binaries:
  Node:
    version: 18.17.1
    path: ~/.nvm/versions/node/v18.17.1/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.yarn/bin/yarn
  npm:
    version: 9.6.7
    path: ~/.nvm/versions/node/v18.17.1/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.12.1
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 22.4
      - iOS 16.4
      - macOS 13.3
      - tvOS 16.4
      - watchOS 9.4
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.10671973
  Xcode:
    version: 14.3.1/14E300c
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 11.0.20
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: ^18.2.0
  react-native:
    installed: 0.72.5
    wanted: 0.72.5
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: Not found

Steps to reproduce

Initialize react-native project in version 0.72.5
Install dependencies

  "dependencies": {
    "@gorhom/bottom-sheet": "^4.5.1",
    "@react-native-async-storage/async-storage": "^1.19.3",
    "@react-native-community/cli-platform-android": "^11.3.8",
    "@react-native-community/geolocation": "^3.1.0",
    "@react-native-community/push-notification-ios": "^1.11.0",
    "@react-native/gradle-plugin": "^0.72.11",
    "@react-navigation/bottom-tabs": "^6.5.8",
    "@react-navigation/drawer": "^6.6.3",
    "@react-navigation/native": "^6.1.7",
    "@react-navigation/native-stack": "^6.9.13",
    "@sayem314/react-native-keep-awake": "^1.2.2",
    "date-fns": "^2.30.0",
    "i18next": "^23.5.1",
    "mitt": "^3.0.1",
    "react-i18next": "^13.2.2",
    "react-native-device-info": "^10.11.0",
    "react-native-document-picker": "^9.0.1",
    "react-native-gesture-handler": "^2.13.1",
    "react-native-heroicons": "^3.2.0",
    "react-native-image-picker": "^7.0.0",
    "react-native-localize": "^3.0.2",
    "react-native-notifications": "^5.1.0",
    "react-native-pager-view": "^6.2.1",
    "react-native-permissions": "^3.9.2",
    "react-native-reanimated": "^3.5.4",
    "react-native-render-html": "^6.3.4",
    "react-native-safe-area-context": "^4.7.2",
    "react-native-screens": "^3.25.0",
    "react-native-svg": "^13.14.0",
    "react-native-tab-view": "^3.5.2",
    "react-native-video": "^5.2.1",
    "rn-fetch-blob": "^0.12.0",
    "tinycolor2": "^1.6.0",
    "zustand": "^4.4.1"
  },
  "devDependencies": {
    "@types/react-native-video": "^5.0.15",
    "@types/tinycolor2": "^1.4.4",
    "babel-plugin-module-resolver": "^5.0.0",
  },

Configure dependencies
Run the project on android in debug mode
Everything should works but we should have java deprecated warning
Run the android release build.
And it should crash with the following issue

> Task :app:mergeReleaseResources FAILED

> Task :react-native-safe-area-context:compileReleaseKotlin
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-safe-area-context/android/src/main/java/com/th3rdwave/safeareacontext/SafeAreaView.kt: (58, 23): 'getter for uiImplementation: UIImplementation!' is deprecated. Deprecated in Java

> Task :react-native-screens:compileReleaseKotlin
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/Screen.kt: (77, 22): 'constructor GuardedRunnable(ReactContext!)' is deprecated. Deprecated in Java
...
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:mergeReleaseResources'.
> A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
   > Android resource compilation failed
     ERROR:/Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/android/app/build/generated/res/createBundleReleaseJsAndAssets/drawable-mdpi/src_assets_icon.png: AAPT: error: file failed to compile.

* 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 1m 34s
error Failed to install the app.
info Run CLI with --verbose flag for more details.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Snack, screenshot, or link to a repository
> Task :app:mergeReleaseResources FAILED

> Task :react-native-safe-area-context:compileReleaseKotlin
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-safe-area-context/android/src/main/java/com/th3rdwave/safeareacontext/SafeAreaView.kt: (58, 23): 'getter for uiImplementation: UIImplementation!' is deprecated. Deprecated in Java

> Task :react-native-screens:compileReleaseKotlin
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/Screen.kt: (77, 22): 'constructor GuardedRunnable(ReactContext!)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/ScreenStackFragment.kt: (62, 28): 'setter for targetElevation: Float' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/ScreenStackFragment.kt: (119, 28): 'setter for targetElevation: Float' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/ScreenStackHeaderConfig.kt: (85, 34): 'getter for systemWindowInsetTop: Int' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/ScreenStackHeaderConfig.kt: (227, 37): 'setColorFilter(Int, PorterDuff.Mode): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/ScreenWindowTraits.kt: (65, 22): 'constructor GuardedRunnable(ReactContext!)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/ScreenWindowTraits.kt: (110, 22): 'constructor GuardedRunnable(ReactContext!)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/ScreenWindowTraits.kt: (137, 47): 'replaceSystemWindowInsets(Int, Int, Int, Int): WindowInsetsCompat' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/ScreenWindowTraits.kt: (138, 51): 'getter for systemWindowInsetLeft: Int' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/ScreenWindowTraits.kt: (140, 51): 'getter for systemWindowInsetRight: Int' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/ScreenWindowTraits.kt: (141, 51): 'getter for systemWindowInsetBottom: Int' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/SearchBarManager.kt: (100, 22): Parameter 'view' is never used
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/SearchBarManager.kt: (100, 43): Parameter 'placeholder' is never used
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/SearchBarView.kt: (141, 43): Parameter 'flag' is never used
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/HeaderAttachedEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/HeaderAttachedEvent.kt: (7, 42): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/HeaderAttachedEvent.kt: (17, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/HeaderAttachedEvent.kt: (18, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/HeaderBackButtonClickedEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/HeaderBackButtonClickedEvent.kt: (7, 51): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/HeaderBackButtonClickedEvent.kt: (17, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/HeaderBackButtonClickedEvent.kt: (18, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/HeaderDetachedEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/HeaderDetachedEvent.kt: (7, 42): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/HeaderDetachedEvent.kt: (17, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/HeaderDetachedEvent.kt: (18, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenAppearEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenAppearEvent.kt: (7, 40): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenAppearEvent.kt: (13, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenAppearEvent.kt: (14, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenDisappearEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenDisappearEvent.kt: (7, 43): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenDisappearEvent.kt: (13, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenDisappearEvent.kt: (14, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenDismissedEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenDismissedEvent.kt: (7, 43): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenDismissedEvent.kt: (13, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenDismissedEvent.kt: (17, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenTransitionProgressEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenTransitionProgressEvent.kt: (13, 5): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenTransitionProgressEvent.kt: (22, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenTransitionProgressEvent.kt: (27, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenWillAppearEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenWillAppearEvent.kt: (7, 44): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenWillAppearEvent.kt: (13, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenWillAppearEvent.kt: (14, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenWillDisappearEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenWillDisappearEvent.kt: (7, 47): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenWillDisappearEvent.kt: (13, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/ScreenWillDisappearEvent.kt: (14, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarBlurEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarBlurEvent.kt: (7, 41): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarBlurEvent.kt: (17, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarBlurEvent.kt: (18, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarChangeTextEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarChangeTextEvent.kt: (10, 5): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarChangeTextEvent.kt: (20, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarChangeTextEvent.kt: (23, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarCloseEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarCloseEvent.kt: (7, 42): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarCloseEvent.kt: (17, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarCloseEvent.kt: (18, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarFocusEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarFocusEvent.kt: (7, 42): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarFocusEvent.kt: (17, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarFocusEvent.kt: (18, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarOpenEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarOpenEvent.kt: (7, 41): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarOpenEvent.kt: (17, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarOpenEvent.kt: (18, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarSearchButtonPressEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarSearchButtonPressEvent.kt: (7, 81): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarSearchButtonPressEvent.kt: (17, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/SearchBarSearchButtonPressEvent.kt: (20, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/StackFinishTransitioningEvent.kt: (5, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/StackFinishTransitioningEvent.kt: (7, 52): 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/StackFinishTransitioningEvent.kt: (13, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/main/java/com/swmansion/rnscreens/events/StackFinishTransitioningEvent.kt: (14, 25): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/paper/java/com/swmansion/rnscreens/FabricEnabledViewGroup.kt: (7, 42): Parameter 'width' is never used
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-screens/android/src/paper/java/com/swmansion/rnscreens/FabricEnabledViewGroup.kt: (7, 54): Parameter 'height' is never used

> Task :react-native-gesture-handler:compileReleaseKotlin
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/core/GestureHandler.kt: (770, 11): Name shadowed: size
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/RNGestureHandlerEnabledRootView.kt: (9, 51): Unreachable code
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/RNGestureHandlerEnabledRootView.kt: (10, 80): Unreachable code
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/RNGestureHandlerRootHelper.kt: (80, 18): 'onChildStartedNativeGesture(MotionEvent!): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/RNGestureHandlerRootHelper.kt: (86, 42): Parameter 'disallowIntercept' is never used
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/RNGestureHandlerRootHelper.kt: (118, 28): Parameter 'viewTag' is never used
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/RNGestureHandlerTouchEvent.kt: (7, 44): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/RNGestureHandlerTouchEvent.kt: (14, 11): 'init(Int): Unit' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/RNGestureHandlerTouchEvent.kt: (30, 42): 'RCTEventEmitter' is deprecated. Deprecated in Java
w: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-gesture-handler/android/src/main/java/com/swmansion/gesturehandler/react/RNGestureHandlerTouchEvent.kt: (31, 21): 'receiveEvent(Int, String!, WritableMap?): Unit' is deprecated. Deprecated in Java
w: Detected multiple Kotlin daemon sessions at build/kotlin/sessions

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/8.0.1/userguide/command_line_interface.html#sec:command_line_warnings
204 actionable tasks: 189 executed, 15 up-to-date

info 💡 Tip: Make sure that you have set up your development environment correctly, by running react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor

Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note<EMAIL_ADDRESS>uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note<EMAIL_ADDRESS>uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-document-picker/android/src/main/java/com/reactnativedocumentpicker/RNDocumentPickerModule.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-image-picker/android/src/main/java/com/imagepicker/Utils.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-localize/android/src/main/java/com/zoontek/rnlocalize/RNLocalizeModuleImpl.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-permissions/android/src/main/java/com/zoontek/rnpermissions/RNPermissionsPackage.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-svg/android/src/main/java/com/horcrux/svg/VirtualView.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/node_modules/react-native-video/android/src/main/java/com/brentvatne/react/ReactVideoViewManager.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:mergeReleaseResources'.
> A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
   > Android resource compilation failed
     ERROR:/Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/android/app/build/generated/res/createBundleReleaseJsAndAssets/drawable-mdpi/src_assets_icon.png: AAPT: error: file failed to compile.

* 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 1m 34s
error Failed to install the app.
info Run CLI with --verbose flag for more details.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Just tried with the latest version (0.72.5)

You have a problem with this file:

ERROR:/Users/quentindrappier/Documents/Clients/Moderato2/moderato_mobile/android/app/build/generated/res/createBundleReleaseJsAndAssets/drawable-mdpi/src_assets_icon.png: AAPT: error: file failed to compile.

Could you share that file in particular?
Also can you provide a reproducer as suggested by the bot?

The file :

src_assets_icon.png.zip
Here is the image, and can you explain to me what you mean by 'a reproducer' ?

src_assets_icon.png.zip
Here is the image but even when the default icons the issue still the same.
And can you explain to me what you mean by 'a reproducer' ?

The issue is with this icon:
$ file ./src_assets_icon.png
./src_assets_icon.png: JPEG image data, JFIF standard 1.01, aspect ratio, density 1x1, segment length 16, progressive, precision 8, 200x200, components 3

The file is saved as .png but it's in reality a .jpg file. You need to use an image convertion tool to properly convert it to PNG.
Closing as this is not related to React Native

i have the same problem but i optimise all png files but it shows the same error

//This is the error
gokul@Gokul MINGW64 /e/Web development/js/Nodejs/React Native/Tieoda/android (main)
$ ./gradlew assembleRelease
Starting a Gradle Daemon, 5 stopped Daemons could not be reused, use --status for details

Configure project :react-native-reanimated
Android gradle plugin: 8.2.1
Gradle: 8.6

Task :app:mergeReleaseResources FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:mergeReleaseResources'.

Multiple task action failures occurred:
A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
Android resource compilation failed
ERROR: AAPT: com.tieoda.app-res-30:/drawable-mdpi/assets_images_dummy_profiles_profilepic2.png: error: failed to read PNG signature: file does not start with PNG signature.
E:\Web development\js\Nodejs\React Native\Tieoda\android\app\build\generated\res\createBundleReleaseJsAndAssets\drawable-mdpi\assets_images_dummy_profiles_profilepic2.png: error: file failed to compile.

A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
Android resource compilation failed
ERROR: AAPT: com.tieoda.app-res-30:/drawable-mdpi/assets_images_dummy_profiles_profilepic10.png: error: failed to read PNG signature: file does not start with PNG signature.
E:\Web development\js\Nodejs\React Native\Tieoda\android\app\build\generated\res\createBundleReleaseJsAndAssets\drawable-mdpi\assets_images_dummy_profiles_profilepic10.png: error: file failed to compile.

A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
Android resource compilation failed
ERROR: AAPT: com.tieoda.app-res-30:/drawable-mdpi/assets_images_recipes_spagetti.png: error: failed to read PNG signature: file does not start with PNG signature.
E:\Web development\js\Nodejs\React Native\Tieoda\android\app\build\generated\res\createBundleReleaseJsAndAssets\drawable-mdpi\assets_images_recipes_spagetti.png: error: file failed to compile.

A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
Android resource compilation failed
ERROR: AAPT: com.tieoda.app-res-30:/drawable-mdpi/assets_images_recipes_satay.png: error: failed to read PNG signature: file does not start with PNG signature.
E:\Web development\js\Nodejs\React Native\Tieoda\android\app\build\generated\res\createBundleReleaseJsAndAssets\drawable-mdpi\assets_images_recipes_satay.png: error: file failed to compile.

A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
Android resource compilation failed
ERROR: AAPT: com.tieoda.app-res-30:/drawable-mdpi/assets_images_dummy_profiles_profilepic6.png: error: failed to read PNG signature: file does not start with PNG signature.
E:\Web development\js\Nodejs\React Native\Tieoda\android\app\build\generated\res\createBundleReleaseJsAndAssets\drawable-mdpi\assets_images_dummy_profiles_profilepic6.png: error: file failed to compile.

A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
Android resource compilation failed
ERROR: AAPT: com.tieoda.app-res-30:/drawable-mdpi/assets_images_dummy_profiles_profile.png: error: failed to read PNG signature: file does not start with PNG signature.
E:\Web development\js\Nodejs\React Native\Tieoda\android\app\build\generated\res\createBundleReleaseJsAndAssets\drawable-mdpi\assets_images_dummy_profiles_profile.png: error: file failed to compile.

A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
Android resource compilation failed
ERROR: AAPT: com.tieoda.app-res-30:/drawable-mdpi/assets_images_recipes_laksa.png: error: failed to read PNG signature: file does not start with PNG signature.
E:\Web development\js\Nodejs\React Native\Tieoda\android\app\build\generated\res\createBundleReleaseJsAndAssets\drawable-mdpi\assets_images_recipes_laksa.png: error: file failed to compile.

A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
Android resource compilation failed
ERROR: AAPT: com.tieoda.app-res-30:/drawable-mdpi/assets_images_system_loginbackground.png: error: failed to read PNG signature: file does not start with PNG signature.
E:\Web development\js\Nodejs\React Native\Tieoda\android\app\build\generated\res\createBundleReleaseJsAndAssets\drawable-mdpi\assets_images_system_loginbackground.png: error: file failed to compile.

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.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.6/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD FAILED in 31s
147 actionable tasks: 28 executed, 119 up-to-date

now what i need to do

now what i need to do

i have same issue, any news for this issue?

now what i need to do

i tried to open the image on photoshop and save it with png again. and it worked. You can try this.

@Gokul0616 @DoHue97
To fix that issue, I had to import every asset I used in Figma and export them as PNGs. Then, I replaced the old files with the newly downloaded ones from Figma.

FIX
The issue was resolved by changing the file format to JPEG. Although the image was saved as a PNG, it showed as JPEG when opened in an editor. Renaming the file format fixed the problem.
Reason for the Error
The error occurred because appicon.co generated .png icon files from a JPEG input, causing a file format mismatch.


Rich Presence only shows idle

When I enter to a level de status dont change help please

i need help too

i need help too


[ANDROID] Exoplayer view + transform rotate does not work

Hi,
My goal is to rotate the video 90deg to display it in fullscreen, w/o flipping the device (the app is locked to Portrait). I'm trying to achieve this by using transform rotate on a Video parent. In result the Video "box" is rotated correctly, but the video surface itself still stays in the initial degree (which makes Big Buck Bunny not happy and confused as you can see on a screenshot).
Please note that I'm not trying to use native fullscreen mode, I'm just trying to rotate the Video box itself with transformation.

The code is just a new react-native project with Video:
import React, { Component } from 'react';
import {
  AppRegistry,
  StyleSheet,
  View
} from 'react-native';
import Video from 'react-native-video';

export default class videoRotateTest extends Component {
  render() {
    return (
      <View style={[styles.container, {
          transform: [{
            rotate: '40deg'
          }]
        }]}>
        <Video
        style={styles.container}
        paused={false}
        resizeMode={'contain'}
        source={{uri: 'http://<IP_ADDRESS>/vod/smil:BigBuckBunny.smil/playlist.m3u8'}}
        />
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: {
    position: 'absolute',
    top: 0,
    left: 0,
    bottom: 0,
    right: 0
  }
});

AppRegistry.registerComponent('videoRotateTest', () => videoRotateTest);

RN: 0.47
react-native-video: latest from master branch
Exactly the same thing works fine on iOS and the video is rotated. Seems like transformation props are not propagated to SurfaceView? I'm not an Android dev so can't say exactly.
I've also tried to use rotation prop of Video component itself, but it doesn't work either and it cannot be animated with useNativeDriver Animation anyway, so it's not an option.
@AndrewJack Seems like you've done initial Exoplayer integration, maybe you could share any suggestion about why it's happening? Would appreciate any help, thanks :)

Small update, this works fine with TextureView, I just set the flag useTextureView to true here.
So seems the problem is specifically with SurfaceView. Does it have any obvious advantages compared to TextureView?

https://source.android.com/devices/graphics/arch-tv#surface_or_texture Might be useful to you.
TextureView allows scaling and transforming whereas SurfaceView does not.
Generally it is better to use SurfaceView as it offers better performance.
Personally I'd just lock/unlock the orientation change when you want to allow and disallow it.
A library like https://github.com/yamill/react-native-orientation would help with this.

@AndrewJack Thanks, so basically SurfaceView does not allow any transformations, clear now.
I'll close the Bug then.


support https

please support https

HTTPS is supported. Do you face any specific problem?

I found some problems about https as below:
com.mashape.unirest.http.exceptions.UnirestException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

https://github.com/Mashape/unirest-java/issues/70

This is an issue with Java not with Unirest specifically


Vulnerable version of Google.ProtoBuf is used by STAN.CLIENT

Hi,
We found out that the STAN.CLIENT project is using Google.Profobuf 3.2.0 which has a serious (8.8./10 CVSS) heap overflow vulnerability reported: https://nvd.nist.gov/vuln/detail/2015-5237
It can be resolved by updating to 3.4.0.

We appreciate the heads up, from the CVE it does not mention which outputs this affects. Does this affect the generated C# code? (the CVE discusses buffer overflows, a la unmanaged code)

Yes, you're right, it would affect C/C++ protobuf implementation, from what I could conclude from the github issue description.


feat: handle clab topo "kinds"

we dont, and we need to. so... title?

This would also mean supporting defaults for a full resolution tree
defaults -> kinds -> node
In the long run this is definitely should be leveraging clab functions to not duplicate a considerable amount of code.

copy
yep, I think from c9s perspective its just literally copying the stuff into the sub topology, so not really anything for c9s to do. I guess at the most complicated end we could parse the kinds and only put the relevant kind in the sub topo but for pass 1 I dont think thats even needed.

I believe this is sorted now as we include kinds/defaults from parent topo into sub topos, so ima close for now!


Python script for automated download-dl tasks

I am working hard on learning python and write scripts that help me to automate downloads.
At the moment I am not able to do so therfore I ask for some help to get started with
For an experienced programmer it may just some lines of code for me it is a wall banging my head at the moment
so if somebody wants to help I would be very thankful
What I try to achive is to fill a text file with either a channel user name or a Playlist url to feed download-dl
I made some bat template files with standard download-dl commandprompt:
youtube-dl -ciw ytuser:TheSkillPedia -o d:\youtube\TheSkillPedia%%(playlist)s%%(title)s.%%(ext)s
youtube-dl\youtube-dl -ciw URL-of-Playlist_of_xyz -o d:\youtube\xyz%%(playlist)s%%(title)s.%%(ext)s
that I fill manually by hand each time
It would be really helpful to have a .py or .bat script that does analyze a simple text file formated like
user, Playlist_URL, Channel_URL
....
to run youtube-dl with parameters
youtube-dl\youtube-dl -ciw $Playlist_URL/&Channel_URL -o d:\youtube$user%%(playlist)s%%(title)s.%%(ext)s
I kow this isn't a direct youtube-dl issue but hopfully someone can help
Thanks in advance

Offtopic.


I receive an error for <> in mdx

I am using next-mdx-remote for mdx in my nextjs project. It uses @mdx-js/mdx under the hood.
I receive an error for << something>> in the mdx. The other features work fine in the plugin remark-smartypants.
test.. test... test..... test?..... test!....
!!!!!! ???? ,, - -- ---
"Smartypants, double quotes" and 'single quotes'
en dash (--), em dash (---)
# <<Hello World!>>

My readme suggested that it's possible, but I don't think it is, as angle quotes are invalid syntax in MDX. I updated the readme.

I digged the issue, after closing.
I realized that, the cause is @mdx-js/mdx. Because it expects an option for format, the default is mdx. In the code of @mdx-js/mdx I found that: link
const pipeline = unified().use(remarkParse)

if (format !== 'md') {
  pipeline.use(remarkMdx) // which is "remark-mdx"
}

pipeline
  .use(remarkMarkAndUnravel)
  .use(remarkPlugins || [])
  ...

Means that, remark-mdx comes prior to remarkPlugins and used just after remark-parse, and this causes the issue.
If the remark-mdx would used after the  remarkPlugins there would be no problem.


Bump to v16 nodejs

what

Bump to v16 nodejs

references

https://github.com/actions/setup-node/issues/32#issuecomment-1003854758

Thanks for this. Would you mind changing the github ci workflow to reference this as well?

@travi I setup the node github action to read from the .nvmrc file.


Various warning, compile and clippy fixes

This PR contains some cleanup regarding compilation and clippy. Some of the clippy lints are just suppressed (large_enum_variant and too_many_arguments) and I'm not sure how to deal with that.
Feel free to merge partially. ;-)

Looks great. You saved me a ton of time :). Will test and merge this tomorrow

I added a basic Travis configuration. Would be great if you could add this repo to the AtherEnergy Travis account.


Parse UVs from triangle meshes

It would probably be best to also parse tangents (parameter "S") from triangle meshes, and to implement this for quad meshes, but I have no models to test it with.

Yep; I'm not aware of any models that have that, so wouldn't worry. I don't think I've ever seen any model that uses anything other than vertex positions and maybe normals and uv....


The mod is not working on the current build of the game.

I'd thank you kindly to give this due consideration this time before per-maturely closing it. Since you were quick to assume I didn't know what I was doing, let me walk you through my steps. I followed the full tutorial. I downloaded the latest release. I unblocked the zip. I extracted it to the root of the game folder. I ran the installer. Booting the game has it hang on the "loading" screen just before the main menu comes up. Simply uninstalling through the patcher allows the game to run normally, suggesting that the issue may lie in the single dll file the patcher interacts with. It's possible perhaps that a recent update to the experimental build altered something in the dll file and now your patcher is incompatible and requires an update.
Here's the log:
2018-02-04 23:52:25.8893 INFO Application Start - v0.10.3+gc104bad8ea
2018-02-04 23:52:25.9049 DEBUG Validate Paths requested.
2018-02-04 23:52:25.9049 INFO Found Steam install directory. [c:/program files (x86)/steam]
2018-02-04 23:52:25.9049 INFO Found Subnautica install directory. [c:/program files (x86)/steam/steamapps/common/Subnautica]
2018-02-04 23:52:25.9049 INFO Found Subnautica Data directory. [c:/program files (x86)/steam/steamapps/common/Subnautica\Subnautica_Data\Managed]
2018-02-04 23:52:25.9527 DEBUG Checking DLL for existin patch.
2018-02-04 23:52:27.4191 DEBUG Install Requested
2018-02-04 23:52:27.4191 DEBUG Changing working dir: c:/program files (x86)/steam/steamapps/common/Subnautica\Subnautica_Data\Managed
2018-02-04 23:52:27.4191 DEBUG Validate Paths requested.
2018-02-04 23:52:27.4191 INFO Found Steam install directory. [c:/program files (x86)/steam]
2018-02-04 23:52:27.4191 INFO Found Subnautica install directory. [c:/program files (x86)/steam/steamapps/common/Subnautica]
2018-02-04 23:52:27.4191 INFO Found Subnautica Data directory. [c:/program files (x86)/steam/steamapps/common/Subnautica\Subnautica_Data\Managed]
2018-02-04 23:52:27.4347 DEBUG Backup of DLL requested.
2018-02-04 23:52:27.4347 INFO Backup of Assembly-CSharp.dll created as 'Assembly-CSharp.dll.subnautica-watcher-backup.20180204T235227'.
2018-02-04 23:52:27.4347 INFO Updating Assembly-CSharp.dll to load SubnauticaWatcherMod.
2018-02-04 23:52:27.4347 DEBUG Checking DLL for existin patch.
2018-02-04 23:52:27.4503 INFO Saving Assembly.
2018-02-04 23:52:27.9671 INFO Assembly-CSharp.dll successfully updated.
2018-02-04 23:52:27.9671 DEBUG Restoring working dir: C:\Program Files (x86)\Steam\SteamApps\common\Subnautica\SubnauticaWatcherInstaller
2018-02-04 23:52:27.9671 DEBUG Checking DLL for existin patch.
2018-02-04 23:52:59.6999 INFO Application Exited.
2018-02-04 23:53:58.1792 INFO Application Start - v0.10.3+gc104bad8ea
2018-02-04 23:53:58.1948 DEBUG Validate Paths requested.
2018-02-04 23:53:58.1948 INFO Found Steam install directory. [c:/program files (x86)/steam]
2018-02-04 23:53:58.1948 INFO Found Subnautica install directory. [c:/program files (x86)/steam/steamapps/common/Subnautica]
2018-02-04 23:53:58.1948 INFO Found Subnautica Data directory. [c:/program files (x86)/steam/steamapps/common/Subnautica\Subnautica_Data\Managed]
2018-02-04 23:53:58.2260 DEBUG Checking DLL for existin patch.
2018-02-04 23:53:59.3190 DEBUG Uninstall Requested.
2018-02-04 23:53:59.3190 DEBUG Changing working dir: c:/program files (x86)/steam/steamapps/common/Subnautica\Subnautica_Data\Managed
2018-02-04 23:53:59.3190 DEBUG Checking DLL for existin patch.
2018-02-04 23:53:59.3502 DEBUG Backup of DLL requested.
2018-02-04 23:53:59.3502 INFO Backup of Assembly-CSharp.dll created as 'Assembly-CSharp.dll.subnautica-watcher-backup.20180204T235359'.
2018-02-04 23:53:59.3502 INFO Removing System.Void SubnauticaWatcherMod.Patching.Patcher::Patch()
2018-02-04 23:53:59.3658 INFO Removed System.Void SubnauticaWatcherMod.Patching.Patcher::Patch()
2018-02-04 23:53:59.3658 INFO Saving Assembly.
2018-02-04 23:53:59.8816 DEBUG Restoring working dir: C:\Program Files (x86)\Steam\SteamApps\common\Subnautica\SubnauticaWatcherInstaller
2018-02-04 23:53:59.8816 DEBUG Checking DLL for existin patch.

Contrary to the readme, I'm using this mod on the live release of the game
and it works great. I have no idea if it works with the Experimental branch
right now. Maybe try the live version?
On Sun, Feb 4, 2018 at 10:08 PM, Merik2013<EMAIL_ADDRESS>wrote:

I'd thank you kindly to give this due consideration this time before
per-maturely closing it. Since you were quick to assume I didn't know what
I was doing, let me walk you through my steps. I followed the full
tutorial. I downloaded the latest release. I unblocked the zip. I extracted
it to the root of the game folder. I ran the installer. Booting the game
has it hang on the "loading" screen just before the main menu comes up.
Simply uninstalling through the patcher allows the game to run normally,
suggesting that the issue may lie in the single dll file the patcher
interacts with. It's possible perhaps that a recent update to the
experimental build altered something in the dll file and now your patcher
is incompatible and requires an update.
Here's the log:
2018-02-04 23:52:25.8893 INFO Application Start - v0.10.3+gc104bad8ea
2018-02-04 23:52:25.9049 DEBUG Validate Paths requested.
2018-02-04 23:52:25.9049 INFO Found Steam install directory. [c:/program
files (x86)/steam]
2018-02-04 23:52:25.9049 INFO Found Subnautica install directory.
[c:/program files (x86)/steam/steamapps/common/Subnautica]
2018-02-04 23:52:25.9049 INFO Found Subnautica Data directory. [c:/program
files (x86)/steam/steamapps/common/Subnautica\Subnautica_Data\Managed]
2018-02-04 23:52:25.9527 DEBUG Checking DLL for existin patch.
2018-02-04 23:52:27.4191 DEBUG Install Requested
2018-02-04 23:52:27.4191 DEBUG Changing working dir: c:/program files
(x86)/steam/steamapps/common/Subnautica\Subnautica_Data\Managed
2018-02-04 23:52:27.4191 DEBUG Validate Paths requested.
2018-02-04 23:52:27.4191 INFO Found Steam install directory. [c:/program
files (x86)/steam]
2018-02-04 23:52:27.4191 INFO Found Subnautica install directory.
[c:/program files (x86)/steam/steamapps/common/Subnautica]
2018-02-04 23:52:27.4191 INFO Found Subnautica Data directory. [c:/program
files (x86)/steam/steamapps/common/Subnautica\Subnautica_Data\Managed]
2018-02-04 23:52:27.4347 DEBUG Backup of DLL requested.
2018-02-04 23:52:27.4347 INFO Backup of Assembly-CSharp.dll created as
'Assembly-CSharp.dll.subnautica-watcher-backup.20180204T235227'.
2018-02-04 23:52:27.4347 INFO Updating Assembly-CSharp.dll to load
SubnauticaWatcherMod.
2018-02-04 23:52:27.4347 DEBUG Checking DLL for existin patch.
2018-02-04 23:52:27.4503 INFO Saving Assembly.
2018-02-04 23:52:27.9671 INFO Assembly-CSharp.dll successfully updated.
2018-02-04 23:52:27.9671 DEBUG Restoring working dir: C:\Program Files
(x86)\Steam\SteamApps\common\Subnautica\SubnauticaWatcherInstaller
2018-02-04 23:52:27.9671 DEBUG Checking DLL for existin patch.
2018-02-04 23:52:59.6999 INFO Application Exited.
2018-02-04 23:53:58.1792 INFO Application Start - v0.10.3+gc104bad8ea
2018-02-04 23:53:58.1948 DEBUG Validate Paths requested.
2018-02-04 23:53:58.1948 INFO Found Steam install directory. [c:/program
files (x86)/steam]
2018-02-04 23:53:58.1948 INFO Found Subnautica install directory.
[c:/program files (x86)/steam/steamapps/common/Subnautica]
2018-02-04 23:53:58.1948 INFO Found Subnautica Data directory. [c:/program
files (x86)/steam/steamapps/common/Subnautica\Subnautica_Data\Managed]
2018-02-04 23:53:58.2260 DEBUG Checking DLL for existin patch.
2018-02-04 23:53:59.3190 DEBUG Uninstall Requested.
2018-02-04 23:53:59.3190 DEBUG Changing working dir: c:/program files
(x86)/steam/steamapps/common/Subnautica\Subnautica_Data\Managed
2018-02-04 23:53:59.3190 DEBUG Checking DLL for existin patch.
2018-02-04 23:53:59.3502 DEBUG Backup of DLL requested.
2018-02-04 23:53:59.3502 INFO Backup of Assembly-CSharp.dll created as
'Assembly-CSharp.dll.subnautica-watcher-backup.20180204T235359'.
2018-02-04 23:53:59.3502 INFO Removing System.Void
SubnauticaWatcherMod.Patching.Patcher::Patch()
2018-02-04 23:53:59.3658 INFO Removed System.Void
SubnauticaWatcherMod.Patching.Patcher::Patch()
2018-02-04 23:53:59.3658 INFO Saving Assembly.
2018-02-04 23:53:59.8816 DEBUG Restoring working dir: C:\Program Files
(x86)\Steam\SteamApps\common\Subnautica\SubnauticaWatcherInstaller
2018-02-04 23:53:59.8816 DEBUG Checking DLL for existin patch.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MartinSGill/SubnauticaWatcher/issues/18, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AiOQfZf-FkHH_isXO9pljViJyR0FYvB-ks5tRozUgaJpZM4R47Mn
.

It works both on the Live (Stable) version as well as on experimental. I was playing with it on experimental for 5 hours last night, so I can confirm that as well.
Please note that when the game is updated, you may need to re-run the installer; as indicated in the release notes. This is because it modifies a core game file which is frequently replaced during updates.

Re-installed Subnautica from scratch (on the experimental branch) and installed the latest mod release.
It worked without issue. I am therefore unable to reproduce your issue.


Add the support to specify the version of the binaries

This PR changes the task name from release to releaseBinaries in
order to make it consistent in the release process. It also adds
packageVersion as a parameter to specify the version of the binaries
to be released.
Partially-closes: apache/incubator-openwhisk-release#9

@jonpspri Please help me review this PR, thanks.

@jonpspri Thank you. I have changed this PR based on the comments.

LGTM


Scroll the  to the center of the browser?

Is it possible?

Do you mean a horizontalscroll? Currently no support for that.

Is it possible to add extra space on the top of the <Element>?

Yes, padding with CSS or offset in the api.


State of Test Kitchen Suite

This is an ongoing issue to track the test kitchen state across the mongodb cookbook.  As I get some time I will run these tests initially to get a view of where we stand. From there we can choose what tests to fix, enhance, remove etc...

Instance
Driver
State
Comments

default-ubuntu-1204
Vagrant
Passing
one test, checks mongo started

default-ubuntu-1004
Vagrant
Passing
one test, checks mongo started

default-debian-720
Vagrant
Passing
one test, checks mongo started

default-centos-70
Vagrant
Passing
one test, checks mongo started

default-centos-65
Vagrant
Passing
one test, checks mongo started

default-centos-510
Vagrant
Passing
one test, checks mongo started

default-mongodb-org-repo-ubuntu-1204
Vagrant
Failing
#49

default-mongodb-org-repo-ubuntu-1004
Vagrant
Failing
#50

default-mongodb-org-repo-debian-720
Vagrant
Failing
#51

default-mongodb-org-repo-centos-70
Vagrant
Converging
No Tests

default-mongodb-org-repo-centos-65
Vagrant
Converging
No Tests

default-mongodb-org-repo-centos-510
Vagrant
Converging
No Tests

replicaset-ubuntu-1204
Vagrant
Failing
#52

replicaset-debian-720
Vagrant
Failing
#53 Two tests: start mongo, replica set up(failing)

replicaset-centos-70
Vagrant
Failing
#54

replicaset-centos-65
Vagrant
Not Executed

replicaset-centos-510
Vagrant
Not Executed

configserver-ubuntu-1204
Vagrant
Not Executed

configserver-ubuntu-1004
Vagrant
Not Executed

configserver-debian-720
Vagrant
Not Executed

configserver-centos-70
Vagrant
Not Executed

configserver-centos-65
Vagrant
Not Executed

configserver-centos-510
Vagrant
Not Executed

mongos-ubuntu-1204
Vagrant
Not Executed

mongos-ubuntu-1004
Vagrant
Not Executed

mongos-debian-720
Vagrant
Not Executed

mongos-centos-70
Vagrant
Not Executed

mongos-centos-65
Vagrant
Not Executed

mongos-centos-510
Vagrant
Not Executed

mms-monitoring-agent-ubuntu-1204
Vagrant
Not Executed

mms-monitoring-agent-centos-70
Vagrant
Not Executed

mms-monitoring-agent-centos-65
Vagrant
Not Executed

mms-backup-agent-ubuntu-1204
Vagrant
Not Executed

mms-backup-agent-centos-70
Vagrant
Not Executed

mms-backup-agent-centos-65
Vagrant
Not Executed

user-management-ubuntu-1204
Vagrant
Failing
#48

user-management-debian-720
Vagrant
Failing
#47

user-management-centos-70
Vagrant
Passing
Three tests: Start mongo, require authentication, create user

user-management-centos-65
Vagrant
Not Executed

user-management-centos-510
Vagrant
Not Executed

Thanks for opening this issue @zarry. I'll run tests throughout the day and post results of each individually so we can get a better idea of where we stand.

Likewise @rex I will be running them on and off throughout the day/evening.  I will start from the top maybe you start from bottom so we don't overlap?

@zarry Sounds like a plan!

As an aside, just to make sure we're on the same page: I am going to run tests from the current state of the master branch. Additionally, I'm not going to modify any code if a test fails. This is purely to assess the current state of affairs in the master branch so that we can plan our next moves.

@rex :+1: agreed.

Hmm. I'm getting a weird failure in my first test. hostnamectl: command not found. It doesn't seem particularly related to this cookbook, which suggests it's a configuration issue. I'm looking into it, but have you seen anything like this on your end @zarry?
Full stack trace:
    default: Guest Additions Version: 4.3.8
    default: VirtualBox Version: 5.0
==> default: Setting hostname...
STDERR: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

hostnamectl set-hostname 'user-management-ubuntu-1204'

Stdout from the command:

Stderr from the command:

stdin: is not a tty
bash: line 2: hostnamectl: command not found
---- End output of vagrant up --no-provision --provider virtualbox ----
Ran vagrant up --no-provision --provider virtualbox returned 1/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/mixlib-shellout-2.1.0/lib/mixlib/shellout.rb:289:in `invalid!'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/mixlib-shellout-2.1.0/lib/mixlib/shellout.rb:276:in `error!'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/shell_out.rb:70:in `run_command'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/kitchen-vagrant-0.18.0/lib/kitchen/driver/vagrant.rb:318:in `run_command'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/kitchen-vagrant-0.18.0/lib/kitchen/driver/vagrant.rb:302:in `run'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/kitchen-vagrant-0.18.0/lib/kitchen/driver/vagrant.rb:348:in `run_vagrant_up'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/kitchen-vagrant-0.18.0/lib/kitchen/driver/vagrant.rb:88:in `create'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:424:in `public_send'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:424:in `block in perform_action'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:485:in `call'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:485:in `block in synchronize_or_call'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:483:in `synchronize'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:483:in `synchronize_or_call'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:453:in `block in action'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:452:in `action'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:424:in `perform_action'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:352:in `create_action'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:341:in `block in transition_to'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:340:in `each'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:340:in `transition_to'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:160:in `verify'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:189:in `block in test'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/instance.rb:185:in `test'
/Users/piercemoore/.rvm/gems/ruby-2.1.5/gems/test-kitchen-1.4.1/lib/kitchen/rake_tasks.rb:54:in `block (3 levels) in define'
Tasks: TOP => kitchen:user-management-ubuntu-1204
(See full trace by running task with --trace)

@rex I did not hit this issue on any of the boxes I tested thus far, however I ran the ubuntu 12.04 user-management test and it did error out in the same spot for me locally.

@zarry Alright I'm running into another issue with a separate test. I think it's going to be a good idea to just create new issues for each failing test with the name of the test and the full stack trace output.

Failing test: user-management-debian-720 https://github.com/chef-brigade/mongodb-cookbook/issues/47

@rex That sounds like a good plan to me.  I started with most of the defaults so we are passing now ok, but tests are really vanilla, should be good enough for now though.

@zarry Cool. Something to build on :)
Failing test: user-management-ubuntu-1204 #48

Moved to the wiki. https://github.com/chef-brigade/mongodb-cookbook/wiki/State-of-Test-Kitchen-Suite

hmm, once you get all these running, I may start building a terrible home-brewed nightly builder. Don't really want to use travis for that since it's a little easy to abuse.

@josephholsten Funny you should say that. I wrote and open sourced this for the company I work at.  I would also be able to give it a few cycles nightly.
https://github.com/commercehub-oss/sous_chef

@josephholsten I'm honestly not worried about using up the resources of Travis or other CI cloud providers that offer unlimited free builds to open source projects. That's what they're there for and the integrations they give us are invaluable. I am all about writing scripts or an app that keeps builds/tests running all the time, but I would prefer to leave the implementation to cloud services.

@rex that's fine for specs, but not for kitchen runs. We'd need to actually provide a place for them to provision to.
If you can figure out a way to do that which isn't attached to a credit card, that would be awesome!


Support custom logging levels

Waiting for tests: dcc70760b9fa42807a75de9bd1973ca942751375

New test builds, minor implementation changes cb062b98539b21bda1da33fd852d8f272e1843f2

Tests passed.


Fix(import): Added List import to report.py file

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

Comparison is base (2b817a0) 85.08% compared to head (ef22bc1) 85.08%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #513   +/-   ##
=======================================
  Coverage   85.08%   85.08%
=======================================
  Files         200      200
  Lines       26336    26336
=======================================
  Hits        22407    22407
  Misses       3929     3929

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


Get 'Segmentation Fault' while running benchmark for NEON

Hi all,
I get the 'Segmentation Fault' when running ACL benchmark for NEON.
ACL benchmark for CL can run to the end successfully.
I just follow the instructions that ACL document mentioned.
Dose anyone hit the same issue?
I ran the benchmark on V17.09 and V17.10 and both got the same error.
Thanks for your help.
Best regards,
Henry

Hello @mstfc,
Can you provide more information?
How do you build the library? Where it fails (Any particular tests)? Where do you run it?

Hi George,
Thanks for reply.
I ran it on Raspberry PI3 model B.
Cross-compiled ACL on Linux X86_64 PC, tool chain version is (Linaro GCC 4.9-2017.01)4.9.4.
Here is the compile command :
scons Werror=1 -j4 debug=1 neon=1 cppthreads=0 openmp=0 opencl=0 os=linux arch=armv7a standalone=0 examples=1 embed_kernels=1 benchmark_tests=1
I traced the code and found it failed at AlexNetNetwork.h : run() : act2.run();
It's just the first test case.
I also found that, in AlexNet.cpp : NEAlexNetFixture, there are 2 NEConvolutionLayer and is different from CL.
I replaced one NEConvolutionLayer with NEDirectConvolutionLayer just like CL does and the first can finish AlexNetNetwork.h : run() function but got " *** Error in `./arm_compute_benchmark': double free or corruption (out): 0x7667b008 *** " error message after than.
I'm still trying to debug, but the progress is too slow.
Hope that I can get some hints from you.
Thank you.
Best regards,
Henry

No updates, closing.


[BUG] ADX TulipIndicator not working all the time

Note: for support questions, please join our Discord server

I'm submitting a ...
[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Action taken (what you did)
trying to use ADX indicator in a Strat (Rsi_Bull_Bear_Adx)

Expected result (what you hoped would happen)
that adx will be calculated on every candle (using 5min candles and adx(5)

Actual result (unexpected outcome)
adx very irregular (or sometimes regular) gives= adx=NaN...

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

I made all updates.. so I have the latest node, latest Tulipind library.. and so on..
I tried it on different machines (linux and Mac)
it is happening in backtests and in live too...

since 2 days it is happening all the time in USDTBTC and ETHETC but in the back tests (over a lot of months) ist is always happening...

a log of a couple of candles with the data and the adx output change is attached....

I tried to figure out the problem with the C code of the indicator... but I couldn't come very far...
please help :)
Adx.log

I solved it here with a lot of help in discord. https://github.com/TulipCharts/tulipnode/pull/34


Add support for overriding settings per request

This commit adds res.settings, an object on to which properties can be defined that will override application settings within Express internals (the values returned from app.get() are not altered, therefore any middleware/components that wants to respect the override would need to be updated to use res.settings instead of app.get()).
At present, this affects the following settings:

view
view engine
views
etag fn
json replacer
json spaces
jsonp callback name

The res.settings object is passed through to view rendering code by adding property _settings to the options parameter of app.render().
The entry key for the view cache was changed to prepend the views setting to ensure the cache continues to work correctly if views is overridden to a different value (eg if view 'users' was cached
from /projdir/views/a but views was overridden to point to /projdir/views/b for this request, it should not retrieve the 'users' view from the cache for /projdir/views/a).
res.settings sets its __proto__ to be the settings property of the current application so settings read from the object will default to the application settings.
As the request progresses through routing, the __proto__ will be updated to ensure values always defalt to the settings of the current application.

Fixes #2849

One thing I'm not sure on is the whether a "views" value of "/a" should be considered different to "/a/" or "/a/b/.." etc. The PR assumes the conservative position that they are different and each would create a distinct cached view. If Express can assume these represent hierarchical file paths for all view engines, then it might make sense to canonicalise them when calculating the cacheKey.

This will need modifying to address the "special" options 'etag', 'query parser' and 'trust proxy'.
See https://github.com/expressjs/express/blob/5.0/lib/application.js#L357

#2935

Related #3536


docs: update embedding networks notebook

What does this implement/fix? Explain your changes
Commit 109d7e9cda98cf9c75579592be7f974ad925c3d9 renamed the embedding networks notebook. This PR adjusts sources to changes.
Does this close any currently open issues?
Fixes # (issue)
Any relevant code examples, logs, error output, etc?
...
Any other comments?
...
Checklist
Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask. We're here to
help! This is simply a reminder of what we are going to look for before merging
your code.

[x] I have read and understood the contribution
guidelines
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have reported how long the new tests run and potentially marked them
with pytest.mark.slow.
[ ] New and existing unit tests pass locally with my changes
[x] I performed linting and formatting as described in the contribution
guidelines
[x] There are no conflicts with the main branch

For the reviewer:

[x] I have reviewed every file
[x] All comments have been addressed.

Thanks a lot for the pointer and the fix!


Conventions around into_inner()

Real-world example: flate2::read::GzEncoder::into_inner.

The failure crate uses inner() instead of into_inner() in https://github.com/withoutboats/failure/commit/9ec4e6ee4cdf9b8be0a8609d876a5654b31b4a70. @withoutboats do you think this is a better convention everywhere that currently uses into_inner(), or is there something unique to failure that made inner() better?

Nope, if the convention is into_inner that would be a better name there!

I documented this convention in 1bd903f893e29a1470747ced6175f127ea29ba4d.


Adaptive Status Bar Icon

The icon doesn't change color when the status bar changes color.
In macos, you set a menuitem image from an asset to enable adaptive icons (black / white status bar toggle)
Adding a channel for the following code allows for use of the asset
func setStatusBarImage(_ call: FlutterMethodCall, _ result: FlutterResult)
{
let assetName = call.arguments as? String
if assetName != nil {
statusItem?.button?.image = NSImage.init(named: assetName!)
result(true)
}
result(false)
}

You need to add below line
statusItem?.button?.image?.isTemplate = true

Have you found a solution to this issue? If so, could you share it with us? Thanks in advance


gh: refactor community files

This PR aims to move the CONTRIBUTING.md and CODE_OF_CONDUCT.md file inside the .github/ dir. Github looks for a contribution guideline file in the following order: .github dir > project root > docs dir (source). Moving the file to the .github/ dir leads to a minimal project structure without any functional change.
I recently proposed this change in (https://github.com/spacetelescope/stdatamodels/pull/139) but it was rejected on the grounds of being dissimilar to this template repository. I'm raising this PR hopefully to start the conversation again on this proposed refactor.

Thank you for your interest and contribution! Unfortunately, I have to reject this particular patch on the same basis as https://github.com/astropy/astropy/pull/14451 . Furthermore, this template is currently not actively maintained.


Fix RadioTap decoding panic

On rare occasions, it is possible that the length field in the RadioTap layer is bigger than the actual data length which results in a panic when trying to reference the payload. If it's bigger, simply truncate the RadioTap length to the length of the actual data to allow processing of what we can safely.

hi. can you please attach a pcap file that causes this issue.

Certainly! We're you after just a pcap which creates the panic? Do you want that committed somewhere? Or were you more after realistic traffic - although that's going to be a lot harder to find/create/sanitize.

I'm looking to build a test case that fails before this PR and is successful after this PR. at least to know what the corner case actually is :)

Hrmm I have no idea how you actually upload a pcap to GH but we can just use the unit test I added and make a pcap with Python+scapy:
from scapy.all import *
import codecs

pkt = RadioTap(codecs.decode('0000ff002e48000010026c09a000c6070000d4000000881fa1ae9dcbc6304b4b', 'hex'))
wrpcap('panic.pcap', pkt)

Then manually testing with something like:
func main() {
	filePath := flag.String("file", "", "Path to pcap file")
	flag.Parse()

	if *filePath == "" {
		fmt.Println("Provide the path to the pcap file using -file flag")
		os.Exit(1)
	}

	handle, err := pcap.OpenOffline(*filePath)
	if err != nil {
		log.Fatal(err)
	}
	defer handle.Close()

	data, _, err := handle.ZeroCopyReadPacketData()

	if err != nil {
		fmt.Println(err)
	}

	var radioTap layers.RadioTap
	if err := radioTap.DecodeFromBytes(data, gopacket.NilDecodeFeedback); err != nil {
		fmt.Println(err)
	}
	fmt.Println(radioTap.Length)
}

That at least shows the corner case as I set the RadioTap.Length to 255:
$ go run main.go -file ~/panic.pcap
panic: runtime error: slice bounds out of range [255:32]

goroutine 1 [running]:
github.com/gopacket/gopacket/layers.(*RadioTap).DecodeFromBytes(0x38772788?, {0x1f89e50?, 0x6dbd80?, 0x20?}, {0x5ecae8?, 0xc33b20?})
        /home/user/go/pkg/mod/github.com/gopacket/gopacket@v1.2.0/layers/radiotap.go:868 +0xbbc
main.main()
        /home/user/tmp/main.go:37 +0x257
exit status 2

Then obviously with the patch it just runs and shows the Length has been truncated to the frame size:
$ go run main.go -file ~/panic.pcap
32


Remove -Xverify:none and -noverify flags from Gradle plugin

On Java 13, the JVM flags -Xverify:none and -noverify was deprecated.
It is necessary to remove from the default configuration.
Message from JVM:
OpenJDK Client VM warning: Options -Xverify:none and -noverify were deprecated
in JDK 13 and will likely be removed in a future release.

Plugin PR: https://github.com/ev3dev-lang-java/gradle-plugin/pull/13 (merged)
Library PR: https://github.com/ev3dev-lang-java/ev3dev-lang-java/pull/686
Examples PR: https://github.com/ev3dev-lang-java/examples/pull/6
Template project PR: https://github.com/ev3dev-lang-java/template-project-gradle/pull/36

Pending review

Fixed


Features/usecase 4 postprocessing

Adapt postprocessing to usecase 4

Most of the code in the postprocessing scripts has to be wrapped into a main() method to work properly.


FTTH down

My fiber has been cut and so my home internet connection is down.
I don't have an ETA as a technician must come and the ISP doesn't have an ETA.

Fiber has been repaired.