[issue#790]fix defaultTopicPerm and defaultGroupPerm values which are in yaml config file dosen't work.

What is the purpose of the change
fix defaultTopicPerm and defaultGroupPerm values which are in yaml config file dosen't work.
Brief changelog
I have just fixed the issue,and the adjusted code are as follows.
I have just fixed the code which are in the PlainPermissionLoader class file.
Verifying this change
I have already verified the changed codes in local enviroment.
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.06%) to 44.762% when pulling 27f9994ab7912b865b4236b4a75e093a7ad48f0c on zongtanghu:develop into 6a573a773a87edbcdcc138614b756019fc280988 on apache:develop.


Unify usages of GetCultureInfo and fix LocalisationManager throwing on invalid culture

Closes #5328

CultureInfoHelper.TryGetCultureInfo unifies the two usages of GetCultureInfo/new CultureInfo, fixing LocalisationManager crashing on startup when an invalid culture is set.
CultureInfo.GetCultureInfo still sometimes fabricates cultures when using predefinedOnly: true so the ZZZ check will have to remain.

I'm not sure how this got merged before I could see it, but this is very breaking. Now the culture for threads on a new installation of a game is InvariantCulture, meaning that anything looking to source the user's culture will not work.


Fixes the odo logout issue.

The logout command can be triggered outside the context directory.
fixes #1836

✗  Failed To Update Config To Component Deployed
[odo]  ✗  Applying configuration [2m]

/retest

[odo]  ✗  waited 4m0s but couldn't find running pod matching selector: 'deploymentconfig=nodejs-app'

/retest

Are we able to add a test? We could add an integration test.

I had a discussion with @amitkrout . He asked me to add the integration test in this manner.

 Waiting for component to start [4m]
[odo]  ✗  waited 4m0s but couldn't find running pod matching selector: 'deploymentconfig=nodejs-app'

/retest

Running oc with args: [exec nodejs-app-1-deploy --namespace vzyoeseqla -- ls -lai /opt/app-root/src]
[oc] error: unable to upgrade connection: container not found ("deployment")

/retest

/retest

/retest

/lgtm


Add ability to pull back only one proxy

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[ X ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose

add the ability to only look up one proxy account if needed
Approach

add parameter and filter based on the parameter.
Commands to test

Screenshots

Learning

awesome thank you!


File manager takes an extremely long time to start

The Issue
AS ytsync publisher
I WANT TO start lbrynet-daemon as fast as possible
SO THAT I can publish my videos rapidly
This is currently not possible after several channels have been published because the file manager takes longer and longer to start.
Steps to reproduce

Publish 10k videos
start lbrynet
...
get a coffee
...
There we go

Expected behaviour
lbrynet should start in seconds and allow publishing ASAP
Actual behaviour
Publishing is possible only after about 7-8 minutes
2018-05-03 18:58:15,893 INFO     lbrynet.daemon.Daemon:516: Starting the file manager
2018-05-03 18:58:19,301 INFO     lbrynet.file_manager.EncryptedFileManager:134: Starting 18761 files

2018-05-03 19:05:25,167 INFO     lbrynet.file_manager.EncryptedFileManager:141: Started 18761 lbry files
2018-05-03 19:05:25,467 INFO     lbrynet.file_manager.EncryptedFileManager:48: Started file manager
2018-05-03 19:05:25,468 INFO     lbrynet.daemon.Daemon:520: Done setting up file manager

System Configuration
{
  "id": null,
  "jsonrpc": "2.0",
  "result": {
    "build": "rc",
    "ip": "<IP_ADDRESS>",
    "lbrynet_version": "0.20.0rc9",
    "lbryschema_version": "0.0.15",
    "lbryum_version": "3.2.1",
    "os_release": "4.4.0-121-generic",
    "os_system": "Linux",
    "platform": "Linux-4.4.0-121-generic-x86_64-with-Ubuntu-16.04-xenial",
    "processor": "x86_64",
    "python_version": "2.7.12"
  }
}

Anything Else
While this behavior is probably expected for normal usage I think there should be a set of options to do the following:

Flag to disable file manager such as to just publish and not worry about serving content
Flag to skip announcing all blobs on startup or ever while still reflecting and announcing new blobs
Flag to disable reannouncement of blobs (this could be hacked by setting the reannounce interval time very high)

Ideally the daemon should be able to start in a few seconds only, no matter how many claims have been made previously.

the problem gets exponentially worse as more files are added (13 minutes startup now):
2018-05-07 11:26:23,170 INFO     lbrynet.daemon.DaemonControl:75: Starting lbrynet-daemon from command line
2018-05-07 11:38:19,172 WARNING  lbrynet.daemon.auth.server:211: error processing api request: This method is unavailable until the daemon is fully started
traceback:
2018-05-07 11:38:21,765 INFO     lbrynet.file_manager.EncryptedFileManager:124: Started 500 files
2018-05-07 11:39:35,830 INFO     lbrynet.file_manager.EncryptedFileManager:141: Started 21410 lbry files
2018-05-07 11:39:37,671 INFO     lbrynet.file_manager.EncryptedFileManager:48: Started file manager
2018-05-07 11:39:37,672 INFO     lbrynet.daemon.Daemon:520: Done setting up file manager
2018-05-07 11:39:37,672 INFO     lbrynet.daemon.Daemon:316: Peer protocol listening on TCP 3333
2018-05-07 11:39:37,675 INFO     lbrynet.daemon.Daemon:250: Starting balance: 1.6853845
2018-05-07 11:39:37,676 INFO     lbrynet.daemon.Daemon:253: Started lbrynet-daemon

⌂122% 1d [lbry@ytsync2:~] 16m50s 130 $ ls /mnt/blobs/lbrynet/blobfiles/ | wc -l
1445659

@nikooo777 Closing this as 1195 has been merged. Please monitor and re-open if it's still an issue.


Use setuptools_scm for Python versioning

This uses git tags for versioning the Python package. The version tags are baked into the package on python setup.py bdist_wheel or python setup.py sdist and do not require the git information to be present for end-users.
Its main benefit is during development where you get versions like duckdb-0.1.1.dev191+g9b57b5ad.d20190821-cp37-cp37m-macosx_10_9_x86_64.whl and thus can identify from which commit your local build stems from.

Thanks, merged


Content Navigation: css class "active" set on the wrong link Element

If you click on the last element in the content nav, sometimes it shows the wrong "active" heading:
Example

Click on "Open WC project generator" link (https://lit.dev/docs/getting-started/#open-wc-project-generator)
The blue rhombus is shown at "Install locally from npm" nav <li> link

The nav element is <nav id="rhsToc">.

Thanks for the report, I have noticed this too.
The reason it happens is that the way the table of contents is implemented means that the first section that is visible on screen will be the highlighted one. There is probably something a bit smarter we could do here, especially relating to sections at the end of each page.
https://github.com/lit/lit.dev/blob/ce62231f63b734b91c02087650e2badca4efdc4b/packages/lit-dev-content/src/pages/docs.ts#L77 is the relevant part of the code.


Which version of coco dataset do you use?

2014?

BTW, how many images did you use in the coco dataset for training?


(Android) Crash on react-native 0.49.5 (RuntimeExceptionSimpleSettableFuture)

Is this a bug report?
Yes
Environment
There was a crash on one of our Android users devices (Samsung SM-T110 Android 4.2.2 API 17) while they were using the production version of our app and we received this bug report from their device:
Environment:
  OS: macOS Sierra 10.12.6
  Node: 8.9.1
  Yarn: 1.0.2
  npm: 5.5.1
  Watchman: 3.9.0
  Xcode: Xcode 9.1 Build version 9B55
  Android Studio: 3.0 AI-171.4408382

Packages: (wanted => installed)
  react: 16.0.0-beta.5 => 16.0.0-beta.5
  react-native: 0.49.5 => 0.49.5

Steps to Reproduce
Here's the exact stack trace:
java.lang.RuntimeException java.lang.InterruptedException
    SimpleSettableFuture.java:102 com.facebook.react.common.futures.SimpleSettableFuture.getOrThrow
    MessageQueueThreadImpl.java:199 com.facebook.react.bridge.queue.MessageQueueThreadImpl.startNewBackgroundThread
    MessageQueueThreadImpl.java:146 com.facebook.react.bridge.queue.MessageQueueThreadImpl.create
    ReactQueueConfigurationImpl.java:87 com.facebook.react.bridge.queue.ReactQueueConfigurationImpl.create
    CatalystInstanceImpl.java:105 com.facebook.react.bridge.CatalystInstanceImpl.<init>
    CatalystInstanceImpl.java:39 com.facebook.react.bridge.CatalystInstanceImpl.<init>
    CatalystInstanceImpl.java:569 com.facebook.react.bridge.CatalystInstanceImpl$Builder.build
    ReactInstanceManager.java:1015 com.facebook.react.ReactInstanceManager.createReactContext
    ReactInstanceManager.java:107 com.facebook.react.ReactInstanceManager.access$600
    ReactInstanceManager.java:832 com.facebook.react.ReactInstanceManager$4.run
    Thread.java:856 java.lang.Thread.run

Caused by: java.lang.InterruptedException
    AbstractQueuedSynchronizer.java:1277 java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly
    CountDownLatch.java:202 java.util.concurrent.CountDownLatch.await
    SimpleSettableFuture.java:66 com.facebook.react.common.futures.SimpleSettableFuture.get
    SimpleSettableFuture.java:100 com.facebook.react.common.futures.SimpleSettableFuture.getOrThrow
    MessageQueueThreadImpl.java:199 com.facebook.react.bridge.queue.MessageQueueThreadImpl.startNewBackgroundThread
    MessageQueueThreadImpl.java:146 com.facebook.react.bridge.queue.MessageQueueThreadImpl.create
    ReactQueueConfigurationImpl.java:87 com.facebook.react.bridge.queue.ReactQueueConfigurationImpl.create
    CatalystInstanceImpl.java:105 com.facebook.react.bridge.CatalystInstanceImpl.<init>
    CatalystInstanceImpl.java:39 com.facebook.react.bridge.CatalystInstanceImpl.<init>
    CatalystInstanceImpl.java:569 com.facebook.react.bridge.CatalystInstanceImpl$Builder.build
    ReactInstanceManager.java:1015 com.facebook.react.ReactInstanceManager.createReactContext
    ReactInstanceManager.java:107 com.facebook.react.ReactInstanceManager.access$600
    ReactInstanceManager.java:832 com.facebook.react.ReactInstanceManager$4.run
    Thread.java:856 java.lang.Thread.run

Here are the threads:

Actual Behavior
There was a crash
Other hints:
Here's the breadcrumbs we got that lead to the error:

Came to post this exactly same issue, but found this before 😃
But im using RN 0.45, and something i notice is lots of CONNECTION_STATE_CHANGE and CONNECTIVITY_CHANGE, for now i have around 600 ocurrences of this errors in my app.
If could help this is my breadcrumb

Having the exact same issue on 0.49.5, java.lang.InterruptedException occurs. Log is same as the above. Please share if you find any solution, I'll do the same :)

We also have the same issue on 0.49.5. Here is our report from appcenter crashes:

I started to observe a similar crash as well recently. I am using react-native 0.49.3. Although, the crash is intermittent but still can be seen now and then. Below is the call stack reported on Sentry

Is any of you able to create a demo project that illustrates the problem?

@SudoPlz I have no idea whats causing it, so i cant reproduce, i just complainig about this because i have seen a lot of this error in my logs, but cant figure out whats the cause, i cant even play it in my device
@ varungupta85 @Agontuk @SudoPlz What do you think of post our package.json file? at least the dependencies part, maybe we found a common plugin, or something like that.

My package.json
{
    "name": "PrimeiraMesa2",
    "version": "0.0.1",
    "private": true,
    "scripts": {
        "start": "node node_modules/react-native/local-cli/cli.js start",
        "test": "jest"
    },
    "dependencies": {
        "axios": "^0.16.2",
        "jest-haste-map": "^20.0.4",
        "moment": "^2.18.1",
        "native-base": "2.2.0",
        "prop-types": "^15.5.10",
        "react": "16.0.0-alpha.12",
        "react-devtools-core": "^2.3.3",
        "react-native": "0.45.1",
        "react-native-check-box": "^1.0.4",
        "react-native-communications": "^2.2.1",
        "react-native-credit-card-input": "^0.3.3",
        "react-native-device-info": "^0.12.0",
        "react-native-fabric": "^0.5.1",
        "react-native-fbsdk": "^0.6.0",
        "react-native-google-places-autocomplete": "^1.2.12",
        "react-native-gps-state": "^0.0.2",
        "react-native-image-picker": "^0.26.3",
        "react-native-keyboard-aware-scroll-view": "^0.2.9",
        "react-native-linear-gradient": "react-native-community/react-native-linear-gradient",
        "react-native-masked-text": "^1.5.1",
        "react-native-modal": "^2.4.0",
        "react-native-multiple-select": "^0.2.1",
        "react-native-navigation": "^1.1.134",
        "react-native-onesignal": "^3.0.5",
        "react-native-push-notification": "^3.0.0",
        "react-native-scrollable-tab-view": "^0.6.7",
        "react-native-star-rating": "^1.0.7",
        "react-native-swiper": "^1.5.4",
        "react-native-vector-icons": "^4.0.1",
        "react-redux": "^5.0.6",
        "redux": "^3.7.2",
        "redux-logger": "^3.0.6",
        "redux-thunk": "^2.2.0",
        "tcomb-form-native": "^0.6.9",
        "underscore": "^1.8.3"
    },
    "devDependencies": {
        "babel-eslint": "^8.0.1",
        "babel-jest": "19.0.0",
        "babel-preset-react-native": "1.9.1",
        "eslint": "^4.4.5",
        "eslint-config-airbnb": "^16.1.0",
        "eslint-plugin-import": "^2.8.0",
        "eslint-plugin-jsx-a11y": "^6.0.2",
        "eslint-plugin-react": "^7.4.0",
        "jest": "19.0.2",
        "react-test-renderer": "16.0.0-alpha.6"
    },
    "jest": {
        "preset": "react-native"
    }
}

Sure, here's mine:
"dependencies": {
    "axios": "0.17.1",
    "babel-preset-react-native": "2.0.0",
    "bugsnag-react-native": "2.7.3",
    "clone": "^2.1.1",
    "creditcards": "^2.1.2",
    "currency-formatter": "1.3.1",
    "eslint-config-airbnb": "16.0.0",
    "immutable": "3.8.2",
    "instabug-reactnative": "^2.0.15",
    "key-mirror": "github:SudoPlz/key-mirror",
    "moment": "2.19.2",
    "moment-timezone": "0.5.14",
    "normalize-css-color": "^1.0.2",
    "performance-now": "2.1.0",
    "prop-types": "15.6.0",
    "querystring": "0.2.0",
    "react": "16.0.0-beta.5",
    "react-clone-referenced-element": "^1.0.1",
    "react-native": "0.49.5",
    "react-native-action-button": "2.8.3",
    "react-native-amplitude-analytics": "^0.1.10",
    "react-native-animatable": "1.2.4",
    "react-native-background-timer": "1.3.0",
    "react-native-blur": "^3.2.2",
    "react-native-code-push": "5.2.0-beta",
    "react-native-collapsible": "^0.9.0",
    "react-native-fcm": "10.0.3",
    "react-native-fetch-blob": "0.10.8",
    "react-native-i18n": "2.0.9",
    "react-native-image-picker": "0.26.7",
    "react-native-image-progress": "1.0.1",
    "react-native-keyboard-aware-scrollview": "github:SudoPlz/react-native-keyboard-aware-scrollview",
    "react-native-keychain": "1.2.1",
    "react-native-linear-gradient": "2.3.0",
    "react-native-maps": "^0.17.1",
    "react-native-modal-datetime-picker": "^4.13.0",
    "react-native-modalbox": "^1.4.2",
    "react-native-navigation": "1.1.295",
    "react-native-orientation": "github:yamill/react-native-orientation",
    "react-native-pages": "^0.6.1",
    "react-native-picker": "4.3.0",
    "react-native-root-toast": "^2.2.0",
    "react-native-simple-store": "1.3.0",
    "react-native-store-review": "^0.1.3",
    "react-native-swipeout": "github:SudoPlz/react-native-swipeout",
    "react-native-vector-icons": "4.4.2",
    "react-native-version-check": "^2.0.1",
    "react-native-wheel-picker": "github:SudoPlz/react-native-wheel-picker",
    "react-redux": "5.0.6",
    "react-test-renderer": "16.0.0",
    "redux": "3.7.2",
    "redux-thunk": "2.2.0",
    "rn-snoopy": "^2.0.0",
    "uglify-js": "3.2.0",
    "undefined": "0.1.0",
    "underscore": "latest",
    "url-parse": "1.2.0",
    "validate.js": "0.12.0"
  },
  "devDependencies": {
    "eslint": "^4.12.0",
    "eslint-plugin-import": "^2.8.0",
    "eslint-plugin-jsx-a11y": "^6.0.2",
    "eslint-plugin-react": "^7.5.1",
    "jest-cli": "^21.2.1",
    "remote-redux-devtools": "^0.5.12",
    "remotedev-server": "^0.2.4",
    "whatwg-fetch": "2.0.3"
  }

I see axios, react-native-navigation, react-native-image-picker, react-native-linear-gradient as the most important common libs.

Here is mine:
"version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "watchman watch-del-all && (adb reverse tcp:8081 tcp:8081 || true) && node node_modules/react-native/local-cli/cli.js start",
    "android": "cd android ; ./gradlew installDebug",
    "xcode": "open ios/react_native_navigation_bootstrap.xcodeproj"
  },
  "dependencies": {
    "assert": "^1.4.1",
    "babel-plugin-transform-runtime": "^6.23.0",
    "babel-preset-es2015": "^6.24.1",
    "babel-preset-stage-2": "^6.24.1",
    "bignumber": "^1.1.0",
    "bluebird": "^3.5.1",
    "browserify-zlib": "^0.1.4",
    "buffer": "^4.9.1",
    "console-browserify": "^1.1.0",
    "constants-browserify": "^1.0.0",
    "crypto": "^1.0.1",
    "dns.js": "^1.0.1",
    "domain-browser": "^1.1.7",
    "events": "^1.1.1",
    "https-browserify": "0.0.1",
    "human-standard-token-abi": "^1.0.2",
    "path-browserify": "0.0.0",
    "process": "^0.11.10",
    "prop-types": "*",
    "querystring-es3": "^0.2.1",
    "react": "^16.1.1",
    "react-native": "^0.49.5",
    "react-native-crypto": "^2.1.1",
    "react-native-http": "github:tradle/react-native-http#834492d",
    "react-native-level-fs": "^3.0.0",
    "react-native-modal-dropdown": "^0.5.0",
    "react-native-navigation": "^1.1.280",
    "react-native-os": "^1.1.0",
    "react-native-randombytes": "^3.0.0",
    "react-native-svg": "^5.4.2",
    "react-native-tcp": "^3.3.0",
    "react-native-udp": "^2.1.0",
    "react-native-ui-kitten": "^2.0.1",
    "react-navigation": "^1.0.0-beta.13",
    "react-number-format": "^3.0.2",
    "react-redux": "^5.0.6",
    "readable-stream": "^1.0.33",
    "redux": "^3.7.2",
    "redux-orm": "^0.9.4",
    "redux-persist": "^4.10.1",
    "redux-thunk": "^2.2.0",
    "reselect": "^3.0.1",
    "stream-browserify": "^1.0.0",
    "string_decoder": "^0.10.31",
    "timers-browserify": "^1.4.2",
    "tty-browserify": "0.0.0",
    "url": "^0.10.3",
    "util": "^0.10.3",
    "victory-native": "^0.15.0",
    "vm-browserify": "0.0.4",
    "web3": "^0.20.2",
    "web3-provider-engine": "^13.3.2"
  },
  "devDependencies": {
    "babel-preset-react-native": "^2.1.0",
    "rn-nodeify": "github:mvayngrib/rn-nodeify"
  },
  "react-native": {
    "zlib": "browserify-zlib",
    "console": "console-browserify",
    "constants": "constants-browserify",
    "crypto": "react-native-crypto",
    "dns": "dns.js",
    "net": "react-native-tcp",
    "domain": "domain-browser",
    "http": "react-native-http",
    "https": "https-browserify",
    "os": "react-native-os",
    "path": "path-browserify",
    "querystring": "querystring-es3",
    "fs": "react-native-level-fs",
    "_stream_transform": "readable-stream/transform",
    "_stream_readable": "readable-stream/readable",
    "_stream_writable": "readable-stream/writable",
    "_stream_duplex": "readable-stream/duplex",
    "_stream_passthrough": "readable-stream/passthrough",
    "dgram": "react-native-udp",
    "stream": "stream-browserify",
    "timers": "timers-browserify",
    "tty": "tty-browserify",
    "vm": "vm-browserify",
    "tls": false
  },
  "browser": {
    "zlib": "browserify-zlib",
    "console": "console-browserify",
    "constants": "constants-browserify",
    "crypto": "react-native-crypto",
    "dns": "dns.js",
    "net": "react-native-tcp",
    "domain": "domain-browser",
    "http": "react-native-http",
    "https": "https-browserify",
    "os": "react-native-os",
    "path": "path-browserify",
    "querystring": "querystring-es3",
    "fs": "react-native-level-fs",
    "_stream_transform": "readable-stream/transform",
    "_stream_readable": "readable-stream/readable",
    "_stream_writable": "readable-stream/writable",
    "_stream_duplex": "readable-stream/duplex",
    "_stream_passthrough": "readable-stream/passthrough",
    "dgram": "react-native-udp",
    "stream": "stream-browserify",
    "timers": "timers-browserify",
    "tty": "tty-browserify",
    "vm": "vm-browserify",
    "tls": false
  }
}

Do you think the trouble maker is once again react-native-navigation ?

I think it is very probable. I have migrated from react-navigation to react-native-navigation. There was no problem with react-navigation. I started project from this repo https://github.com/wix/react-native-navigation-bootstrap.
I'll try to reproduce the issue with blank react-native-navigation-bootstrap and RN-0.49.5

Below are my dependencies and I am also using react-native-navigation.
"dependencies": {
    "buffer": "^5.0.7",
    "firebase": "^4.6.0",
    "invariant": "^2.2.2",
    "libphonenumber-js": "^0.4.37",
    "lodash": "^4.17.4",
    "moment-timezone": "^0.5.13",
    "prop-types": "^15.6.0",
    "raven-js": "^3.19.1",
    "react": "16.0.0-beta.5",
    "react-native": "^0.49.3",
    "react-native-animatable": "^1.2.4",
    "react-native-collapsible": "^0.9.0",
    "react-native-communications": "^2.2.1",
    "react-native-contacts": "^1.0.2",
    "react-native-country-picker-modal": "github:varungupta85/react-native-country-picker-modal",
    "react-native-device-info": "^0.12.1",
    "react-native-dialogs": "^0.0.20",
    "react-native-elements": "^0.17.0",
    "react-native-fbsdk": "^0.6.3",
    "react-native-firebase-analytics": "^4.0.1",
    "react-native-gifted-chat": "github:varungupta85/react-native-gifted-chat",
    "react-native-i18n": "^2.0.8",
    "react-native-image-crop-picker": "^0.18.0",
    "react-native-ios-notification-actions": "holmesal/react-native-ios-notification-actions",
    "react-native-keyboard-aware-scroll-view": "^0.3.0",
    "react-native-keyboard-spacer": "^0.4.1",
    "react-native-navigation": "^1.1.295",
    "react-native-parsed-text": "0.0.20",
    "react-native-permissions": "^1.0.1",
    "react-native-push-notification": "github:varungupta85/react-native-push-notification#multiple-features-android-active",
    "react-native-radio-buttons": "^1.0.0",
    "react-native-searchbar": "github:varungupta85/react-native-searchbar",
    "react-native-sound": "github:varungupta85/react-native-sound",
    "react-native-swiper": "^1.5.13",
    "react-native-uuid": "^1.4.9",
    "react-native-vector-icons": "^4.4.2",
    "react-redux": "^5.0.6",
    "redux": "^3.7.2",
    "redux-persist": "^4.10.1",
    "redux-thunk": "^2.2.0",
    "reduxsauce": "^0.7.0",
    "reselect": "^3.0.1",
    "uuid": "^3.1.0",
    "wordwrap": "^1.0.0"
  },

Here is my list of dependencies. @SudoPlz so the last candidate is react-native-navigation ......
"dependencies": {
    "babel-preset-flow": "^6.23.0",
    "deep-diff": "^0.3.8",
    "deepmerge": "^2.0.1",
    "flow-bin": "0.46",
    "hoist-non-react-statics": "^2.3.1",
    "lodash.get": "^4.4.2",
    "lottie-react-native": "^2.2.7",
    "moment": "^2.19.1",
    "prop-types": "^15.5.10",
    "react": "16.0.0-beta.5",
    "react-native": "0.49.5",
    "react-native-animatable": "^1.2.4",
    "react-native-audio": "^3.5.0",
    "react-native-code-push": "^5.1.3-beta",
    "react-native-device-info": "^0.11.0",
    "react-native-elements": "^0.18.4",
    "react-native-fabric": "^0.5.0",
    "react-native-fbsdk": "^0.6.3",
    "react-native-fcm": "^10.0.0",
    "react-native-fetch-blob": "^0.10.8",
    "react-native-firebase": "^3.0.5",
    "react-native-firebase-analytics": "^4.0.1",
    "react-native-gifted-chat": "https://github.com/peteroid/react-native-gifted-chat.git",
    "react-native-image-crop-picker": "^0.18.1",
    "react-native-image-picker": "^0.26.3",
    "react-native-lightbox": "https://github.com/gravitons-inc/react-native-lightbox",
    "react-native-maps": "^0.17.1",
    "react-native-mixpanel": "^0.0.16",
    "react-native-modal": "^4.1.1",
    "react-native-modal-dropdown": "^0.5.0",
    "react-native-mov-to-mp4": "^0.2.1",
    "react-native-navigation": "^1.1.250",
    "react-native-parsed-text": "^0.0.20",
    "react-native-progress": "^3.4.0",
    "react-native-sentry": "^0.30.0",
    "react-native-sound": "^0.10.3",
    "react-native-timeline-listview": "^0.2.2",
    "react-native-vector-icons": "^4.2.0",
    "react-native-video": "^2.0.0",
    "react-navigation": "^1.0.0-beta.21",
    "react-navigation-is-focused-hoc": "^1.0.0",
    "react-redux": "^5.0.6",
    "redux": "^3.7.2",
    "redux-logger": "^3.0.6",
    "redux-persist": "^5.0.0-rc.6",
    "redux-saga": "^0.16.0",
    "sentry-cli-binary": "^1.24.1",
    "uuid": "^3.1.0",
    "why-did-you-update": "https://github.com/maicki/why-did-you-update.git"
  },
  "devDependencies": {
    "babel-eslint": "^8.0.1",
    "babel-jest": "^21.2.0",
    "babel-plugin-ignite-ignore-reactotron": "^0.3.0",
    "babel-plugin-transform-export-extensions": "^6.22.0",
    "babel-plugin-transform-remove-console": "^6.8.5",
    "babel-preset-react-native": "^4.0.0",
    "jest": "^21.2.1",
    "react-test-renderer": "16.0.0-alpha.12",
    "reactotron-react-native": "^1.12.3",
    "standard": "^10.0.3"
  },

Here's our dependencies, we're also using react-native-navigation. I think it's highly probable that it's RNN issue. But we've to reproduce it first.
"dependencies": {
    "appcenter": "^1.0.1",
    "appcenter-analytics": "^1.0.1",
    "appcenter-crashes": "^1.0.1",
    "async": "^2.4.1",
    "axios": "^0.15.3",
    "immutability-helper": "^2.2.2",
    "invariant": "^2.2.2",
    "lodash": "^4.17.4",
    "moment": "^2.19.2",
    "prop-types": "^15.5.10",
    "react": "16.0.0-beta.5",
    "react-native": "0.49.5",
    "react-native-code-push": "https://github.com/Microsoft/react-native-code-push.git#cccdc1c2de",
    "react-native-collapsible-toolbar": "^0.1.1",
    "react-native-config": "^0.9.0",
    "react-native-facebook-account-kit": "^0.9.0",
    "react-native-fbsdk": "https://github.com/facebook/react-native-fbsdk.git#67d5e6f3b3",
    "react-native-fcm": "^10.0.3",
    "react-native-image-picker": "^0.26.7",
    "react-native-keyboard-aware-scroll-view": "^0.4.1",
    "react-native-material-dropdown": "^0.1.0",
    "react-native-modal-datetime-picker": "^4.13.0",
    "react-native-navigation": "^1.1.274",
    "react-native-photo-view": "^1.5.2",
    "react-native-radio-buttons": "^1.0.0",
    "react-native-sentry": "^0.30.3",
    "react-native-star-rating": "^1.0.8",
    "react-native-vector-icons": "^4.4.2",
    "react-native-version": "^2.3.1",
    "react-redux": "^5.0.3",
    "redux": "^3.6.0",
    "redux-axios-middleware": "^4.0.0",
    "redux-devtools-extension": "^2.13.0",
    "redux-logger": "^3.0.1",
    "redux-persist": "^4.8.0",
    "redux-saga": "^0.15.6"
  }

I have the same crash but it happened only after take picture from camera. I have react-native-image-crop-picker
ImagePicker.openCamera({
            cropping: true,
            width: 300,
            height: 300,
            includeExif: false,
            cropperCircleOverlay: false,
            compressImageMaxWidth: 640,
            compressImageMaxHeight: 480,
            compressImageQuality: 0.5,
        }).then((image: PickerImage) => {
        }).catch(e => console.debug(e));

Android: 4.4.4
Android Build: KTU84P
Manufacturer: Xiaomi
Model: HM NOTE 1S
Thread: Thread-642-642
CrashReporter Key: 53AAF253-78AD-C833-AEE2-5825359AF87D10F89447
Start Date: Tue Dec 05 14:30:15 EET 2017
Date: Tue Dec 05 14:30:15 EET 2017

java.lang.RuntimeException: java.lang.InterruptedException
	at com.facebook.react.common.futures.SimpleSettableFuture.getOrThrow(SimpleSettableFuture.java:102)
	at com.facebook.react.bridge.queue.MessageQueueThreadImpl.startNewBackgroundThread(MessageQueueThreadImpl.java:199)
	at com.facebook.react.bridge.queue.MessageQueueThreadImpl.create(MessageQueueThreadImpl.java:146)
	at com.facebook.react.bridge.queue.ReactQueueConfigurationImpl.create(ReactQueueConfigurationImpl.java:87)
	at com.facebook.react.bridge.CatalystInstanceImpl.<init>(CatalystInstanceImpl.java:105)
	at com.facebook.react.bridge.CatalystInstanceImpl.<init>(CatalystInstanceImpl.java:39)
	at com.facebook.react.bridge.CatalystInstanceImpl$Builder.build(CatalystInstanceImpl.java:569)
	at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:1015)
	at com.facebook.react.ReactInstanceManager.access$600(ReactInstanceManager.java:107)
	at com.facebook.react.ReactInstanceManager$4.run(ReactInstanceManager.java:832)
	at java.lang.Thread.run(Thread.java:841)
Caused by: java.lang.InterruptedException
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1279)
	at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:202)
	at com.facebook.react.common.futures.SimpleSettableFuture.get(SimpleSettableFuture.java:66)
	at com.facebook.react.common.futures.SimpleSettableFuture.getOrThrow(SimpleSettableFuture.java:100)

"dependencies": {
        "immutability-helper": "^2.4.0",
        "jest-html-reporter": "^0.5.3",
        "moment": "^2.19.2",
        "prop-types": "^15.6.0",
        "q": "^1.5.1",
        "rc-swipeout": "^2.0.4",
        "react": "16.0.0-beta.5",
        "react-native": "0.49.5",
        "react-native-adjust": "^4.11.7",
        "react-native-extended-stylesheet": "^0.8.0",
        "react-native-google-analytics-bridge": "^5.3.3",
        "react-native-i18n": "^2.0.8",
        "react-native-image-crop-picker": "^0.18.1",
        "react-native-maps": "^0.17.1",
        "react-native-navigation": "1.1.284",
        "react-native-pages": "^0.6.1",
        "react-native-parallax-scroll-view": "^0.20.1",
        "react-native-percentage-circle": "^1.0.6",
        "react-native-radio-buttons": "^1.0.0",
        "react-native-root-modal": "^2.1.0",
        "react-native-status-bar-size": "^0.3.2",
        "react-native-svg": "5.5.1",
        "react-native-swipeout": "^2.3.1",
        "react-native-tts": "^1.4.0",
        "react-native-vector-icons": "^4.4.2",
        "react-redux": "^5.0.6",
        "redux": "^3.7.2",
        "redux-create-reducer": "^1.1.1",
        "redux-logger": "^3.0.6",
        "redux-persist": "^4.10.1",
        "redux-thunk": "^2.2.0",
        "remote-redux-devtools": "^0.5.12",
        "uuid": "^3.1.0"
    }

It looks like most of us use react-native-image-picker too

I think people have a mix of react-native-image-picker and react-native-image-crop-picker. Trying to find a solution for this issue as soon as possible as many production app users have experienced this issue after I updated to react-native 0.49.3 but the issue is very intermittent and I am not able to find any defined steps to reproduce the problem in order to debug it.

@guyca at Wix said that they use in MainApplication.java
 @Override
    public boolean clearHostOnActivityDestroy() {
        return false;
    }

in Wix app which fixes a lot of issues when external activities/apps are launched, which might be the issue if you're using a camera component. Has anyone of you using it in your app?
If you do decide to give it a try, you will need to change the app startup as mentioned here for Android.
https://wix.github.io/react-native-navigation/#/android-specific-use-cases?id=compatibility-with-headlessjs
I have updated my app with the above changes and trying to reproduce the bug again. Haven't been successful yet which is a good sign I guess.
Also, I started to see this issue after I updated to RNN .295 from RNN .253. Not sure if that rings a bell for anyone else.

We also have this issue. Looks like it only occur for some devices and only when they open the app from the "google play store".
Our dependencies:
"dependencies": {     "@mapbox/polyline": "0.2.0",     "bugsnag-react-native": "2.3.2",     "date-fns": "1.28.2",     "lottie-react-native": "^2.2.7",     "phone": "1.0.12",     "react": "16.0.0-alpha.12",     "react-native": "0.48.4",     "react-native-actionsheet": "2.3.0",     "react-native-appsflyer": "git://github.com/AppsFlyerSDK/react-native-appsflyer.git",     "react-native-background-geolocation": "2.9.4",     "react-native-country-picker-modal": "0.3.0-rc1",     "react-native-credit-card-input": "0.3.3",     "react-native-device-info": "0.11.0",     "react-native-fbsdk": "git://github.com/facebook/react-native-fbsdk.git#065507aa1d2b8b0b6cb50d13117694123f8303fa",     "react-native-fcm": "8.0.1",     "react-native-google-analytics-bridge": "5.2.2",     "react-native-image-crop-picker": "0.18.0",     "react-native-image-zoom-viewer": "2.0.5",     "react-native-linear-gradient": "2.2.0",     "react-native-maps": "0.17.0",     "react-native-navigation": "^1.1.299",     "react-native-parallax-view": "2.0.6",     "react-native-permissions": "1.0.1",     "react-native-prompt": "1.0.0",     "react-native-scrollable-tab-view": "0.6.7",     "react-native-swiper": "1.5.9",     "react-native-vector-icons": "4.3.0",     "react-redux": "5.0.5",     "redux": "3.7.1",     "redux-logger": "2.10.2",     "redux-thunk": "2.2.0",     "remote-redux-devtools": "0.5.12",     "reselect": "3.0.1",     "tipsi-stripe": "^4.4.0"   },

@acintyo this code, cause the app re-launch

@Thadeu What do you mean by app re-launch? When does the app re-launch?

True, I get the same behaviour as @Thadeu :O I didn't even know that until his comment.

Ok now I'm super confused.
I can't get the app to crash now, and I can't get it to restart. I was working on a totally irrelevant problem, and it now works. Not sure if I did anything wrong or right, and I know I'm not much help now.
The thing is, right now it's not crashing with:
@Override
    public boolean clearHostOnActivityDestroy() {
        return false;
    }

¯_(ツ)_/¯

@Thadeu Ok I think we're getting somewhere with the restarting issue. It's totally irrelevant to the crash. The restarting issue is because the camera intent takes too much memory, and the OS shuts everything else down to allow the camera to take the photo

I use react-native-image-crop-picker and that works without any problems with the fix. I had some other issues with the above fix due to which I have to remove it but those are completely related to my app and not issues in general. So, I am still looking for a fix.

We upgraded to RN 0.51 and still waiting for this crash to happen, but nothing so far which is a good sign I guess.

But doesn't the app restart when you guys take a photo?
If so what settings are you using, are you limiting the size of the photo?
The app restarts whenever the user takes a photo now, no matter if I clearHostOnActivityDestroy or not.

@SudoPlz Same here.

@varungupta85 I'll also try to react-native-image-crop-picker
Thanks for now.

@Thadeu I tried react-native-image-crop-picker today, and it also restarts the app.
@varungupta85 are you using RN 0.51 and react-native-navigation?

@SudoPlz I am using RN 0.49.3 and RNN 1.1.305. I am able to use react-native-image-crop-picker without any problems. I am not sure why does it cause the app to restart in your case. Are you observing it in both development and production?
Also, I'm using a Nexus 5X on 8.1.0 and react-native 0.51.0
With react-native-image-crop-picker I received the following error:
E/CAM_StateSavePic: exception while saving result to URI: Optional.of(content://com.test.app.android.provider/app_images/Pictures/image-5900b551-fd35-485e-997b-a8eadfe32b397411249060724805767.jpg)
  java.io.FileNotFoundException: No content provider: content://com.test.app.android.provider/app_images/Pictures/image-5900b551-fd35-485e-997b-a8eadfe32b397411249060724805767.jpg
      at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:1251)
      at android.content.ContentResolver.openOutputStream(ContentResolver.java:1007)
      at android.content.ContentResolver.openOutputStream(ContentResolver.java:983)
      at cys.e(PG:18)
      at cys.b(PG:52)
      at cni.b(PG:13)
      at cni.a(PG:38)
      at cyh.a(PG:5)
      at emm.run(PG:8)
      at android.os.Handler.handleCallback(Handler.java:790)
      at android.os.Handler.dispatchMessage(Handler.java:99)
      at android.os.Looper.loop(Looper.java:164)
      at android.app.ActivityThread.main(ActivityThread.java:6494)
      at java.lang.reflect.Method.invoke(Native Method)
      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)

but I'm not sure what I must change.

I'm having same crash, also using react-native-navigation but no react-native-image-crop-picker

anyone has an update for this?  There is also related issue on RNN repo - https://github.com/wix/react-native-navigation/issues/2364

Also having this issue using react-native-navigation

I also have this crash, and I am using great-native-navigation, and I do not use the camera or image picker

Also having this issue using react-native-navigation

I don't see the issue after upgrading react-native to 0.53 and react-native-navigation to 1.1.375.

ok bot...as if upgrading to the latest RN version is such an easy task...

I am getting this error on specific MI devices ( Mi Note 5 MEI7).
Steps to reproduce :

Go to settings and then go to app settings.
Go to permission
Switch on any permission (Location or contact).
Open the app
keep the app in background and then again switch off the permission
Open the app.
Result -> App relaunched and crashed with exception

    java.lang.RuntimeException: java.lang.InterruptedException         at com.facebook.react.common.futures.SimpleSettableFuture.getOrThrow(SimpleSettableFuture.java:102)         at com.facebook.react.bridge.queue.MessageQueueThreadImpl.startNewBackgroundThread(MessageQueueThreadImpl.java:199)         at com.facebook.react.bridge.queue.MessageQueueThreadImpl.create(MessageQueueThreadImpl.java:146)         at com.facebook.react.bridge.queue.ReactQueueConfigurationImpl.create(ReactQueueConfigurationImpl.java:87)         at com.facebook.react.bridge.CatalystInstanceImpl.<init>(CatalystInstanceImpl.java:101)         at com.facebook.react.bridge.CatalystInstanceImpl.<init>(CatalystInstanceImpl.java:42)         at com.facebook.react.bridge.CatalystInstanceImpl$Builder.build(CatalystInstanceImpl.java:563)         at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:978)         at com.facebook.react.ReactInstanceManager.access$600(ReactInstanceManager.java:109)         at com.facebook.react.ReactInstanceManager$4.run(ReactInstanceManager.java:802)         at java.lang.Thread.run(Thread.java:760)      Caused by: java.lang.InterruptedException         at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301)         at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:203)         at com.facebook.react.common.futures.SimpleSettableFuture.get(SimpleSettableFuture.java:66)         at com.facebook.react.common.futures.SimpleSettableFuture.getOrThrow(SimpleSettableFuture.java:100)         at com.facebook.react.bridge.queue.MessageQueueThreadImpl.startNewBackgroundThread(MessageQueueThreadImpl.java:199)          at com.facebook.react.bridge.queue.MessageQueueThreadImpl.create(MessageQueueThreadImpl.java:146)          at com.facebook.react.bridge.queue.ReactQueueConfigurationImpl.create(ReactQueueConfigurationImpl.java:87)          at com.facebook.react.bridge.CatalystInstanceImpl.<init>(CatalystInstanceImpl.java:101)          at com.facebook.react.bridge.CatalystInstanceImpl.<init>(CatalystInstanceImpl.java:42)          at com.facebook.react.bridge.CatalystInstanceImpl$Builder.build(CatalystInstanceImpl.java:563)          at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:978)          at com.facebook.react.ReactInstanceManager.access$600(ReactInstanceManager.java:109)          at com.facebook.react.ReactInstanceManager$4.run(ReactInstanceManager.java:802)          at java.lang.Thread.run(Thread.java:760)


Traction Documentation - Use Case videos

Videos of Traction (old version) have been removed.
Decide whether they need to be replaced and log more issues to have them created and posted (where?) if needed.

As far as just Tenant UI I think it would be good to make a tenant/innkeeper reservation flow video. Just because I demo it enough that having that around would be good.
Probably the following too

Invitations/connections
Make tenant an issuer
Schema creation and credential offer and revocation.

But then yeah, worth a discussion if making API-centric ones is worthwhile at this point.


Do you have plans for an UWP App version?

Hi! How are you? Well, I read your code and I notice that is a WPF App, right? So I started to question my self, why did you not try to make an UWP App instead. Because, honestly, the app looks so awesome, congrats, but I missed the UI pattern from Windows 10 and some other cool APIs available in Windows Runtime like notifications, live tiles and some others. So I need to know, do you have any plan to port it for UWP? We can access registry using an "alternative" executable using FullTrust capibility. If yes, I can help you with that. I already have in mind to port it after all, but I don't know how to give you the credits. Thank you for attention and congrats.

Hi @marck7jr, indeed it's a WPF C# app. I've started initially creating an UWP (and love how UWP looks) but for me it was a troubling task to access the registry and the task scheduler. I want to add more features to the app (I'm working on changing the Windows theme based on time - that includes cursors, sounds, slideshows, etc.). Those features still require a more "low" level access to Windows and UWP is too sandboxed.
Thank you for your support! You can port the app in UWP and let me know the progress, code example or if it supports the features present in this initial release. I am curious of your approach.
Also, if I port it to UWP I would like it to publish to the Store but I think it may get rejected because it accesses forbidden parts of the OS.

I make some progress to the UWP version, but I don't know if he could support for calling .exe files inside WindowsApps folder (where the UWP apps are installed), but I know that taks can be scheduled with reg like showed in this article. Until now I didn't tried to register the taks yet, but I can use FullTrustProcessLauncher to a WPF App to perfome some actions perfectly.

How do you prefer to read the code? Pull Request? Or another repository?

@marck7jr This is great but the first I suggest you to do is to see if you are able to:

Edit the registry
Call executables and starts processes
Access the TaskScheduler
DllImport

These are crucial for the app to do what it does, otherwise it is just a pretty UI 😢

This will not be implemented. Closing this ticket.


Bug when editing

Exception in valueChanged callback!
Traceback (most recent call last):
  File "/mnt/sdb1/virtuald/src/frc/pynetworktables/networktables2/networktablenode.py", line 157, in fireTableListeners
    listener.valueChanged(None, key, value, isNew)
  File "/mnt/sdb1/virtuald/src/frc/pynetworktables/networktables/networktable.py", line 43, in valueChanged
    self.listener(key, value, isNew)
  File "/mnt/sdb1/virtuald/src/frc/RoboRIO-webdash/webdash/networktables_controller.py", line 29, in val_listener
    set_local_value(key, value)
  File "/mnt/sdb1/virtuald/src/frc/RoboRIO-webdash/webdash/networktables_controller.py", line 65, in set_local_value
    target_table[value_key] = value
TypeError: list indices must be integers, not str
Exception in valueChanged callback!
Traceback (most recent call last):
  File "/mnt/sdb1/virtuald/src/frc/pynetworktables/networktables2/networktablenode.py", line 157, in fireTableListeners
    listener.valueChanged(None, key, value, isNew)
  File "/mnt/sdb1/virtuald/src/frc/pynetworktables/networktables/networktable.py", line 43, in valueChanged
    self.listener(key, value, isNew)
  File "/mnt/sdb1/virtuald/src/frc/RoboRIO-webdash/webdash/networktables_controller.py", line 29, in val_listener
    set_local_value(key, value)
  File "/mnt/sdb1/virtuald/src/frc/RoboRIO-webdash/webdash/networktables_controller.py", line 65, in set_local_value
    target_table[value_key] = value
TypeError: list indices must be integers, not str

What type of entry were you editing to get this error?

I don't remember.


Git ignore modifications

According to this https://nodejs.dev/learn/the-package-lock-json-file I was wrong and we need store this file to repo. But docker files should be updated to avoid using npm install. nom ci should be used instead (it should be double checked).


Keybinding modal window

Implementation of feature #1568
Allows for new binding preview, remove binding and set it to default.
The layout needs to be worked a bit but its functional.

Can one of the admins please verify this patch?

Gooey: Test this please
ok to test
Thanks for this @Sk0ut ! Will test as soon as able :-)

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/344/
Hooray Jenkins reported success with all tests good!

Reviewed, tested, and merged! Nice work and some handy lambdas as well :-)
I noted a few minor issues or related quirks and submitted #2064 for further work. Feel free to take a look and tweak some more if you're up for it!


[MNT] CI fixes and pytest options

Fixes the current periodic and main CI failures. Mainly leftover get_test_params from PRs before the refactor. numba vectorize is apparently not disabled by the environmental variable, so disabling  njit for the function called in it breaks it since it needs to be a numba function.

@fspinna does the BORF numba function change make sense to you? I'm pretty sure there are identical in output though maybe not efficiency. Ideally we want everything to be able to run even with numba disabled.


Problems with installing older apps

I keep getting this kind of error when trying to Bypass Low Target SDK Block on older apps:
com.dotgears.flappybird INSTALL_FAILED_NO_MATCHING_ABIS: INSTALL FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113
I tried two different apps
On Pixel 7 Pro, on Android 15 Beta

This has nothing to do with SDK, it tells you that the package doesn't contain the necessary libraries (ABIs) for your CPU, which only supports arm64-v8a, this app can't bypass that to install ones with armeabi-v7a. I've seen a Magisk module (root) that claims to be able to bypass this stupid restrictions, but the new CPUs just don't any longer support the instructions set. Your's is one of those that still does I think, but the restriction/limitation is placed by Google on a software level, rather than hardware like in Snapdragon 8 Gen 3 that no longer supports 32-bit.

I have same problem with installing daydream apks on pixel 7, android 14.

In that case and considering my comment above - I don't see a point in posting this, given that it's not this app's fault and that it can't do anything about this.


[bitswap] Frequent "received empty message" log entries from multiple peers

We are observing frequent log entries indicating that the Bitswap server is receiving empty messages from multiple peers.
Logs:
Below are some example log entries showing the empty messages received:
2024-12-13T10:48:20.916Z INFO bitswap/server/decision decision/engine.go:679 received empty message from 12D3KooWNB1QiE9bgkgXjk5LDq8YHfABNYnKcEip6Zqx1WdWsdaN
2024-12-13T10:48:21.002Z INFO bitswap/server/decision decision/engine.go:679 received empty message from 12D3KooWAaQge1CXX7Tr2Vkv9GELbryzyN8nrfDJC9G7ifYkhN3d
2024-12-13T10:48:21.477Z INFO bitswap/server/decision decision/engine.go:679 received empty message from 12D3KooWG622N7QE4m5ypuEC4AmZheAWsU5NZ1X8AxjkABBwMzND
2024-12-13T10:48:21.750Z INFO bitswap/server/decision decision/engine.go:679 received empty message from 12D3KooWCqMWrEvgwN64SZRcjG3HCtNaCLodxT3v4Kfh6aCfCJGW
2024-12-13T10:48:21.795Z INFO bitswap/server/decision decision/engine.go:679 received empty message from 12D3KooWGF8tGiodVoWceegJUwpfWjZxvRvC9f3xsFqMa3P1pxPb

Observed
Across all of the mainnet DA nodes v0.20.4 approximately every 60 seconds.

@aWN4Y25pa2EK, do you see peer ids repeat in the logs? Are these the same peers sending use empty messages every ~60s or arr they different every time? If they are the same, can you post sever adjacent logs coming from the same peer? I would need to know the time between each message exactly


Feature request: Reset all changes

Sometimes one would want to give control back to iLO's control system. For example when you are not at home and it's a very hot day, and server life is more important than noise.
I think the only way to do this is by resetting iLO. One can do that via the web interface:
Information -> Diagnostics -> Reset iLO -> Reset

Maybe one can reset the iLO controller via SSH too, but via the web interface might be quicker.

Unfortunately, I never thought about this feature and I can't come up on how I could add it without messing up with the UI/UX.


Passthru test options

This is a replacement for #48319 to simply passthru the --test or --pest option to the underlying make:controller call. This allows the controller test to also be created.
In addition, the --test option is automatically set to true when the -a option is used to generate a default test, unless the --pest option is set to specifically generate Pest tests.

Man, thank you so much for making this so much simpler than I was able to.  I've been fighting it all night and yours looks way better.

Actually, I spoke too soon.  For whatever reason, even if you set $this->input->setOption('test'); or $this->input->setOption('pest'); the $this->handleTestCreation() method that gets added by the trait never gets called.  I've been working on a PR for a bit and I had to create a separate method that called it because I couldn't figure out any other way to trigger it.

I won't actually send in my PR, but you can see what I was trying here: https://github.com/laravel/framework/commit/1cbb6da483180019d38b73f4f6c010fa648813cf

I definitely like the sniff out. But I'd like wait and see what the core team thinks about adding tests with the -a option in general before I refine.
For me the win is passing the test options down to the controller. Personally, I'm comfortable writing make:model -a --test to be explicit.

Totally understand.  Thanks for clarifying.


Docker image should have environment variables to configure basic startup settings like database password and default admin password

Gitea version (or commit ref): as in "latest" docker image from 2017-04-20
Git version: as in "latest" docker image from 2017-04-20
Operating system: as in "latest" docker image from 2017-04-20
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
The docker image should have environment variables to configure basic startup settings like database password and default admin password instead of just a graphical wizard. While a wizard is completely fine for a manual install, docker containers are usually launched automatically and most of the popular well-written ones can be booted in a working state immediately without much manual intervention.
For a comparable startup script, check the gitlab omnibus container: apart from arbitrary config values (which wouldn't be necessarily needed for gitea but nice to have), it allows specifying the admin login password and the database access password so that on first launch, it starts immediately ready to use without any additional configuration needed. The postgresql container you recommend for use in the gitea docker tutorial is also a good example, it allows setting a password, a user and even automatically creating a database by name on first launch purely with environment variables specified on container creation.
Adding this would allow a more automated setup of gitea instances with docker.

The only thing we'd need is a startup-script that populates custom/conf.ini based on environment variables. So this is kind/deployment, not kind/feature 🙂

These variables now exist, check out gitea's docker docs for instructions.


[DO NOT MERGE] Splitting test suite to see which files contain flakey tests 4/4

What this PR does / why we need it:
Splitting test suite to see which files contain flakey tests 4/4
/cc @fgimenez

/hold


fixFix cancelled tasks with running status

The state of writing the log first and changing it later resulted in the memory state being cancelled and the state after restarting being running

run buildall

run performance


authenticated encryption

Added an interface class for authenticated encryption with associated data as well as two implementations: GCM and CBC with HMAC.
See also issues #100 #112 #46

This looks great! Thanks! Could you perhaps rebase on top of the recent registry changes?? Then I can test and merge it!

That would be really great to have GCM implementation on the master branch. Is there any update on that PR?

This looks so helpful!
Just to confirm, but if I need AES/CCM, that will still require porting from BouncyCastle (but would be based on the AEADBaseCipher from this PR)?

I rebased this PR on master + PR #175 + PR #174 (Seems to work OK for me!), and I ported AES/CCM from BouncyCastle. At first I tried to re-use the functions in AEADBaseCipher, but that didn't work for me -- I ended up with a more direct port from BouncyCastle (so, perhaps that base class has a bit too much, or I used it incorrectly). Other than that, I was able to build on top of this quite easily.
I have a PR ready (for the AES/CCM) for when this gets merged.

Unable to wait too long for this PR to get merged, I've rebased this on master and I've also merged #174 and #175  in my fork na2axl/pointycastle and i'm happy to see that everything works fine. I'm using this feature for a secured chat application with a server written in Golang sending and receiving encrypted messages from web (Javascript) and mobile (Dart/Flutter) clients through websockets, with AES/GCM implemented on each endpoints and working without problems.

@na2axl, there are two small issues I found so far in your fork, the GCM block cipher is not registered, and it fails with NPE if no associated text is present.
https://github.com/knopp/pointycastle/commit/389d6e3745446db006ac4071a73f3d8509b91fd5
https://github.com/knopp/pointycastle/commit/9f46f8e914aabe4e435d86bd49763af013ff6018

Thanks @knopp I've merged your changes in my fork.

I'm archiving this repo as per #239 (see the issue for more info).


kubelet_hostname_override leads to some ugly errors in kube-proxy

When kubelet_hostname_override setting is enabled, the kube-proxy gives the following startup errors:
E0112 06:07:10.274956       1 server.go:421] Can't get Node "kube1", assuming iptables proxy, err: nodes "kube1" not found
W0112 06:07:10.277165       1 server.go:468] Failed to retrieve node info: nodes "kube1" not found
W0112 06:07:10.277296       1 proxier.go:249] invalid nodeIP, initialize kube-proxy with <IP_ADDRESS> as nodeIP

I'm not sure of the symptoms of this error.  I was having multiple networking issues so it was hard to correlate which error messages caused which issues.  The errors can be cleared though by passing the --hostname-override setting to kube-proxy as well as kubelet, which is apparently required according to https://github.com/kubernetes/kubernetes/issues/18104#issuecomment-161456732.

Full kube-proxy logs
E0112 06:07:10.274956       1 server.go:421] Can't get Node "kube1", assuming iptables proxy, err: nodes "kube1" not found
I0112 06:07:10.276098       1 server.go:215] Using iptables Proxier.
W0112 06:07:10.277165       1 server.go:468] Failed to retrieve node info: nodes "kube1" not found
W0112 06:07:10.277296       1 proxier.go:249] invalid nodeIP, initialize kube-proxy with <IP_ADDRESS> as nodeIP
W0112 06:07:10.277347       1 proxier.go:254] clusterCIDR not specified, unable to distinguish between internal and external traffic
I0112 06:07:10.277415       1 server.go:227] Tearing down userspace rules.
I0112 06:07:10.287037       1 conntrack.go:81] Set sysctl 'net/netfilter/nf_conntrack_max' to 131072
I0112 06:07:10.287505       1 conntrack.go:66] Setting conntrack hashsize to 32768
I0112 06:07:10.287732       1 conntrack.go:81] Set sysctl 'net/netfilter/nf_conntrack_tcp_timeout_established' to 86400
I0112 06:07:10.287818       1 conntrack.go:81] Set sysctl 'net/netfilter/nf_conntrack_tcp_timeout_close_wait' to 3600

sorry took so long @ravishivt! @aric49 thanks for taking this on, and cleaning things up. resolves issue #45


Tutorials tracking

Create a way for us to track tutorials ideas and interests (or just doing it in issues here!?)

Duplicate of #61

Duplicate of #61


Added support for puppetlabs-apt >= 2.0

This is needed for puppetlabs-apt >= 2.0 support.

Hi,
I'm not planning to only support the 2.0 apt module since older PE versions are possibly pinned down to older apt module versions.
In the readme i specified for now that I'm only supporting pl-apt 1.8 and lower.
When 1.0 is out i will revise it.


Problem on Image Hide

there is a problem when the image is hidden from the beginning, not the center fits well to show the image.

@puped  can you produce jsfiddle for me buddy?


PEP 8 Compliance for python code

PEP 8 (official python style guide) compliance. No change to functionality except replacing x == False with not x and x == True with x, which assumes x will always be True or False (if it is not, falsey values will be interpreted as False and truthy values will be interpreted as True, so this way has hopefully less surprising behaviour).
Also letting the json module handle reading the input file, and no need to close the file explicitly when you use with.

Closing as penile wants to use a different style guide.


avoid loop in DevNodes::next_entry() and return Ok(None) when exhausted

This PR is similar to #79 but for the asynchronous variant DevNodes instead. Basically, next_entry() is rewritten such that when the underlying next_entry() is exhausted, it returns Ok(None) to indicate that the iterator has been exhausted.

Thanks for doing this! and dealing with my reviews, haha


Update default mysql engine to 5.5.40a for AWS RDS

The old MySQL engine version (5.5.31) seems to no longer be available as an
option for RDS.  Updated default version to 5.5.40a.

@cppforlife I sent in the CLA yesterday and got a response back that it was good to go.  Don't know what else I need to do..

@epoelke thanks. we'll pull this in soon: https://www.pivotaltracker.com/story/show/86960650


RKE2 Documentation

Is there any mechanism available that could allow turtles to deploy RKE2 clusters? Digging around I am struggling to find any information on how or if turtles can even be used to deploy RKE2 clusters. In my example I am attempting to deploy to vsphere, I saw some references to kubeadm so I assume the default is to deploy RKE, is this all accurate?

Thanks @Daemonslayer2048 . You could use the CAPRKE2 providers with Rancher Turtles.  Using CAPRKE2 is different to creating an RKE2 cluster with the existing provisioning mechanisms in Rancher in that it doesn't currently support any of the day 2 operations (i.e. etcd snapshot restore, cert rotation). If you car about those types of day 2 operations with RKE2 then its best to use the existing provisioning mechanisms.
Are you currently part of the early adopter programme for Rancher Turtles?

Hey @richardcase, I am not part of the early adopter program. My Github profile does not really show it much but I am a Rancher Government Solutions employee, I am looking into Turtles and as you can imagine I have a particular interest in RKE2. My hope was Turtles docs could keep RKE2 deployments in mind, and preferably provide some docs on how this could be done.

Thanks @Daemonslayer2048 - Rancher Turtles will certainly be keeping RKE2 in mind :wink:  . Lets chat.


HomeWork 5 & 6: Young

轻钱包地址 ： t1o5doelpvfaquee24kehegyckq2h3qr2lkqsgyti
轻钱包转账Hash : bafy2bzacebcu3o4mtnvhqs27fswydtkikevkwlbisamzvfcukju4tdihrrero
默认地址 ： t1xtzcl55f6ct7lrzdrddofun5wpikyto6nj53q5i
存储交易CID ： bafyreifvtgfc5uvnvmt3n34zfo4ppk2fb2o6aegwa4sgivemleup37a7oy

Also Homework6 for young
NFT : YBAYC is used to test the bayc nft in testnet
contract Address : 0x5377D9388C37C7143E8735c67cCb747e5153eA68
contract creation Hash : 0x5c525b8ab26b1aca2678c8d4b011bcf8c59b9118ada074d3015133f86a76ad60
Owner Address : 0x2e55A4deF72Ab5e2988eCc7750FAdac973C55555
NFT Hash : 0xfae2eda1f5a20665f7643da5bd1f382574cfb5f47649960622fd6b8bdacefd4d

BTW I encountered an error using hardhar to deploy contract
Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}
Is it something to do with the proxy or keep-alive tcp connection?

@Yang94J will you be able to fix the issue with Hardhat ?


Excel's celll format does not support numeric types

Background
We need to use excel to display a large amount of data, including percentages, decimals, currency, time, and text.
Problem
The “decimal” cannot control the number of digits and the format is not a decimal
(the below picture shows what I want)

but most of them(I mean all the numFmt ID I test) shows "custom"
I know use "customNumFmt" can control the number of digits but the format is "custom"!
Thanks!

Thanks for your feedback. But sorry, I don't understand what you exactly mean. This problem may be similar to issue #705, and you can use build-in number format ID 2 for the numeric data type values. You can find more built-in number format mapping details in the documentation.

I am so sorry that my English is poor, the more detail is below:
I used to use number format ID 2:

At the same time, all the built-in numFmts can not control the digits's decimal places, it always 2 places!
Thanks for answer!

Please use the custom number format for the Kingsoft WPS, but which will incompatible with Microsoft Excel for Mac:
customNumFmt := "0.00_ "
styleID, err := f.NewStyle(&excelize.Style{CustomNumFmt: &customNumFmt})
if err != nil {
    fmt.Println(err)
    return
}

the code you pin seems don't work, it shows the format is "General".

( the format "0.00_" seems invalid?)

btw my wps is kingsoft.

Which version of Excelize library and Kingsoft WPS are you using?

exelize: 1.4.1
wps 4.4.2

It seems your provided Kingsoft WPS version is incorrect, version 4.4.2 was released in 2001, which does not support the spreadsheet in xlsx format, I have tested with version <IP_ADDRESS>63, and it works well.

but I can't find any other version info in wps

（when I click the update button, it shows the wps is the newest version🥺）

Thanks for your feedback. Here is an example for you reference, and it works on WPS Office for Mac:
package main

import (
    "fmt"

    "github.com/xuri/excelize/v2"
)

func main() {
    f := excelize.NewFile()
    defer func() {
        if err := f.Close(); err != nil {
            fmt.Println(err)
        }
    }()
    if err := f.SetCellValue("Sheet1", "A1", 23.455667); err != nil {
        fmt.Println(err)
        return
    }
    customNumFmt := "0.00_ "
    styleID, err := f.NewStyle(&excelize.Style{CustomNumFmt: &customNumFmt})
    if err != nil {
        fmt.Println(err)
        return
    }
    if err := f.SetCellStyle("Sheet1", "A1", "A1", styleID); err != nil {
        fmt.Println(err)
        return
    }
    if err := f.SaveAs("Book1.xlsx"); err != nil {
        fmt.Println(err)
    }
}

It seems still not have enough info or feedback for this issue, so I'll close this issue, if you have any questions, please let me know to reopen this anytime.

The question has been resolved. and the code did work!  Thanks a lot!!!  ❤


Available Test Data

Is there any test data that can be supplied?
For example, in the instructions it mentions that inputs are metadata.txt, and data.tab.
I would need this test data in order to write a conda wrapper for feht.

Oh oops, I added the --delimiter flag and used the data in the data/ folder.

Hi Matt,
Thanks for making the conda wrapper.
I'm working on an update for Genevieve that I will push up next week to address some of the issues she was having, which will include additional tests.
Let me know if you need anything.
Chad


python 3.9 + Window10 mpire problem with freeze_support, should I fix runpy.py file?

Sorry for asking similar issue with #40 #41 .
However, I don't know where should I input below line as you mentioned before
from multiprocessing import freeze_support()
I can find if name == 'main' in the last part of runpy.py file.
Should I fix that file to use empire module in Window Pycharm?
or change the code style which can only run by terminal line.

I'm not entirely sure which situation applies to you, but let me go over a few of them:

When you're creating a script that you just want to call using python some_script.py, then it's good practice to include the if __name__ == "__main__" line and start from there. I.e., avoid doing stuff globally. And when you have the if, you usually call the freeze_support right after it, such that it will be the first thing that's executed.

if __name__ == "__main__":
    freeze_support()

    # do other stuff

Now, you can also create a script without the if __name__ == "__main__". That will still work. In that case, you have to call freeze_support as soon as possible such that it will be the first thing that's being executed (aside from the imports). For example, you can put it right after the import statements.

When you're creating a library/package then it's normal you don't have an if __name__ == "__main__" line, as your code will be called from somewhere else. In this case, you don't have to add it and it's up to the user of your package to include it.

Hope this helps

Thanks for replying.
I check the freeze_support() works right when I run the code on the terminal.
However, I want to know when I run the codes while I write down and test them into Pycharm or Jupyter, etc without running on the terminal or cmd.
I tried freeze_support using the code starts but it's not working.
Is there any option to solve this problem? (I think changing the default Windows setting is needed to solve but have no idea..)

I have difficulty following what you're saying.
Perhaps the easiest way to give advice is if you can copy and paste your code here, including the error message + traceback.

Not that different. I mean just run in pycharm.
Run into pycharm, freeze_support looks like don't work

Looking at https://docs.python.org/3.9/library/multiprocessing.html#the-spawn-and-forkserver-start-methods and then the Safe importing of main module section, it says that for Windows you should always put your scripts inside an if __name__ == '__main__':, not in the global. Not doing so can cause the RuntimeError that you see.
Earlier, you said I can find if name == 'main' in the last part of runpy.py file.. So if you can find that, then freeze_support() should be the first line in that if clause

Closing due to inactivity


[Qt6, PyQt6 6.6.1] Breaks keyboard shortcuts layout in Preferences

🐛 Bug Report
With PyQt6 6.6.1 the keyboard shortcuts layout is broken with the action names prematurely truncated.
6.6.1

6.6.0 (and 6.5.3, 6.5.0)

(note when testing old versions you need to force install the matching version of PyQt6-Qt6)
💡 Steps to Reproduce
Install latest PyQt6 (6.6.1) with matching PyQt6-Qt6 package.
Open the keyboard shortcuts Preference panel.
💡 Expected Behavior
The full action names should be shown.
🌎 Environment
napari: 0.5.0a2.dev483+g65ffc895
Platform: macOS-14.2.1-arm64-arm-64bit
System: MacOS 14.2.1
Python: 3.11.7 | packaged by conda-forge | (main, Dec 23 2023, 14:38:07) [Clang 16.0.6 ]
Qt: 6.6.1
PyQt6:
NumPy: 1.26.3
SciPy: 1.11.4
Dask: 2024.1.0
VisPy: 0.14.1
magicgui: 0.8.1
superqt: 0.6.1
in-n-out: 0.1.9
app-model: 0.2.4
npe2: 0.7.3
OpenGL:

GL version: 2.1 Metal - 88
MAX_TEXTURE_SIZE: 16384

Screens:

screen 1: resolution 2056x1329, scale 2.0
screen 2: resolution 1920x1200, scale 1.0

Settings path:

/Users/sobolp/Library/Application Support/napari/napari-dev-pyqt6_44a57b2eefd248abfe19ee6d23ba0bf2f2a31d6d/settings.yaml

💡 Additional Context
This is breaking behavior added by https://github.com/napari/napari/pull/5679

@dalthviz Do you have any ideas where to start to try to debug this?

Hi there, maybe something changed regarding word wrapping or maybe the way to make cells use all the space available :thinking: Will give this a check and let you know if I find something :+1:

@psobolewskiPhD I was able to reproduce this on Windows and the only way I have found (at least for the moment) to properly setup an initial column and row size was setting a maximum section size for the table horizontal header while also using the QHeaderView.ResizeMode.ResizeToContents mode for the table horizontal and vertical headers. So changing the code at:
https://github.com/napari/napari/blob/0be7f18fb67d4f68876a0e5ca04c619dd343f456/napari/_qt/widgets/qt_keyboard_settings.py#L233-L238
For something like:
            # Column and rows size set up.
            self._table.horizontalHeader().setMaximumSectionSize(370)
            self._table.horizontalHeader().setSectionResizeMode(
                QHeaderView.ResizeMode.ResizeToContents
            )
            self._table.verticalHeader().setSectionResizeMode(
                QHeaderView.ResizeMode.ResizeToContents
            )

Makes things have a proper size even when using PyQt6 6.6.1, PyQt6 6.6.0 or PyQt5 5.15.9.  A preview on how things end up looking for me on Windows with the change:

However, one thing that could be thought as a regression with the change above is that it will be impossible to resize the columns manually (so no mouse pointer change indicating a posible column resize when passing the mouse over the column header edge).
Following that caveat, not totally sure if the change above is a good enough fix, but anyhow, pushed a branch with the change in case you want to check/play with it: https://github.com/napari/napari/compare/main...dalthviz:napari:issue_6601
Let me know what do you think!

It looks related to this bug in Qt: https://bugreports.qt.io/browse/QTBUG-120418
In the comments, there is information about setting parentship that solves the problem.

Gave the Qt bug link a check and although changing the parent of the QTableWidget didn't change the behavior (creating an intermediate widget to set as the table parent) seems like indeed something regarding size definition is breaking when you set programatically a stylesheet for widgets. Commenting out the setStyleSheet calls that are done to the table/table header instances at:
https://github.com/napari/napari/blob/374caa6ea37428d38b8240742fe142714c6fe763/napari/_qt/widgets/qt_keyboard_settings.py#L206-L208
https://github.com/napari/napari/blob/374caa6ea37428d38b8240742fe142714c6fe763/napari/_qt/widgets/qt_keyboard_settings.py#L240-L241
helps setting the correct columns size once you manually trigger the table regeneration (by selecting a different group of shortcuts):

Quite a strange behavior so indeed seems like a Qt bug, right?

This is fixed with PyQt6_Qt6-6.6.3 -- note PyQt6 is still 6.6.1


XDT transform problems

I'm trying to learn how to utilize applicationHost.xdt and XDT transformations to add features to my website. The simplest possible example I can think of is to add a new app setting through an applicationHost.xdt file.
I create a new file named applicationHost.xdt in the D:\home\site folder. The file has the following content:
<?xml version="1.0"?>
<configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform">
  <appSettings xdt:Transform="InsertIfMissing">
    <add key="Hello" value="World" xdt:Locator="Match(key)" xdt:Transform="InsertIfMissing" />
  </appSettings>
</configuration>

I've created a small test website, that does nothing more than get the value of Hello and display it on the screen. No value is shown on screen.
I've remembered to restart the site after saving the applicationHost.xdt file. I've also checked D:\home\LogFiles\Transform for errors. No errors are shown in the log file for neither scm nor main.
Any ideas to help me move forward?

Closing this since I found out why this isn't working as I expected. When adding appSettings like this, app settings are added to the applicationHost.config file, which isn't supported or what I really want.


Fully parametrize model definition

Just keeping this as a todo
There are additional ways to parametrize the model defintion for example define the number or encoder/decoder layers, channel dimension decrease rate (1 to keep the same n channel as of now, 2 to divide by a factor of 2 each time etc...).
This allow for much better dyamic parametrization of the model, as an example: https://github.com/SIMEXP/DeepNeuroAN/blob/28750d81e046816dd1edbad1564344ed5ccd4dcd/deepneuroan/models.py#L547

https://github.com/SIMEXP/gcn_package/pull/11


Using clang-sys for header paths breaks any non-default-target builds

This breaks msvc (or really any non-default-target bindings generation):
When llvm/clang is built for the gnu target by default (needed for msvc bindings generation, because it's easier to use those default include paths and let the msvc target get them from $INCLUDE), clang behaves properly:
$ vladimir@glacier[5307]$ clang -E -x c++ - -v
Target: x86_64-w64-windows-gnu
[...]
#include "..." search starts here:
#include <...> search starts here:
 W:\msys64\mingw64\include\c++\6.1.0
 W:\msys64\mingw64\include\c++\6.1.0\x86_64-w64-mingw32
 W:\msys64\mingw64\include\c++\6.1.0\backward
 C:\proj\llvm\build-mingw64\bin\..\lib\clang\3.9.0\include
 W:\msys64\mingw64\lib\gcc\x86_64-w64-mingw32\6.1.0\include
 W:\msys64\mingw64\lib\gcc\x86_64-w64-mingw32\6.1.0\include-fixed
 W:\msys64\mingw64\x86_64-w64-mingw32\include
 W:\msys64\mingw64\include
End of search list.

$ vladimir@glacier[5307]$ clang --target=x86_64-pc-win32 -E -x c++ - -v
Target: x86_64-pc-windows-msvc
[...]
#include "..." search starts here:
#include <...> search starts here:
 C:\proj\llvm\build-mingw64\bin\..\lib\clang\3.9.0\include
 C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include
 C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\include
 C:\Program Files (x86)\Windows Kits\10\include\10.0.10586.0\ucrt
 C:\Program Files (x86)\Windows Kits\10\include\10.0.10586.0\shared
 C:\Program Files (x86)\Windows Kits\10\include\10.0.10586.0\um
 C:\Program Files (x86)\Windows Kits\10\include\10.0.10586.0\winrt
End of search list.

But when rust-bindgen is passed --target=x86_64-pc-win32, it gets:
$ ./etc/bindings.sh msvc14
...
Target: x86_64-pc-windows-msvc
#include "..." search starts here:
#include <...> search starts here:
 ../target/debug/build/mozjs_sys-4ab490f4d99d7124/out/dist/include
 W:\msys64\mingw64\include\c++\6.1.0
 W:\msys64\mingw64\include\c++\6.1.0\x86_64-w64-mingw32
 W:\msys64\mingw64\include\c++\6.1.0\backward
 C:\proj\llvm\build-mingw64\bin\..\lib\clang\3.9.0\include
 W:\msys64\mingw64\lib\gcc\x86_64-w64-mingw32\6.1.0\include
 W:\msys64\mingw64\lib\gcc\x86_64-w64-mingw32\6.1.0\include-fixed
 W:\msys64\mingw64\x86_64-w64-mingw32\include
 W:\msys64\mingw64\include
 C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include
 C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\include
 C:\Program Files (x86)\Windows Kits\10\include\10.0.10586.0\ucrt
 C:\Program Files (x86)\Windows Kits\10\include\10.0.10586.0\shared
 C:\Program Files (x86)\Windows Kits\10\include\10.0.10586.0\um
 C:\Program Files (x86)\Windows Kits\10\include\10.0.10586.0\winrt
End of search list.

which then totally breaks the generation.
I'm going to hack around this by skipping the clang-sys isystem stuff (why is it needed?) if --target is specified.

This was fixed in #54, thanks vlad :)


Run SpatNav on up/down (in Android TV's WebView)

Run SpatNav on up/down (in Android TV's WebView)
Background:
Spatial Navigation is Chromium's DPAD-mechanics
that runs in Android WebView on Android TV and
if you run Chrome with --enable-spatial-navigation.
SpatNav runs as Chrome's default action on keydown.
Problem:
Once focus goes to a search box, DPAD_UP/DOWN
in Android TV's WebViews can not move focus
outside the search box. Focus gets trapped.
This happens because react-autosuggest always
prevents the default action (Spatial Navigation
in Android TV's WebViews).
Solution:
Do not prevent Spatial Navigation from running
when no suggestions are shown.
Testing done:

npm start
Quit Chrome.
chrome --enable-spatial-navigation
http://localhost:3000/demo/dist/index.html
Ensure that the arrow keys can move between
all fields and links.

@aberezkin, could you review this change? It unblocks Android TV.

@saltas888, could you review this change?
Especially, could you apply this change locally and try it out on your web site? Does this break anything for you?

Looks great! :+1: :+1: :+1:

Thanks @pimterry!
So let's to step up the package version so we can get this change out there? :) Do you have access to publish a new version to npm? I don't...
I see that https://www.npmjs.com/package/react-autosuggest mentions 10.0.2 as the last version. I don't know how this works because our package.json still says "version": "10.0.1". We should probably step it up to 10.0.3?

So let's to step up the package version so we can get this change out there?

Yep, definitely aiming to do that today, I just want to wrap up #773 first, just need to finish some of the test markups.

Do you have access to publish a new version to npm?

I do! (I think, although I haven't tested it yet)

I see that npmjs.com/package/react-autosuggest mentions 10.0.2 as the last version. I don't know how this works because our package.json still says "version": "10.0.1". We should probably step it up to 10.0.3?

Oh boy, that's not great. Doing so digging in<EMAIL_ADDRESS>to<EMAIL_ADDRESS>and looking through the commits from back in May, it looks like https://github.com/moroshko/react-autosuggest/commit/9f1ce67ac99b2944ca5c2f088ea4906214bc8567 was published as 10.0.2, but that package.json commit is on a branch, and not on the merged commit on master (which is here https://github.com/moroshko/react-autosuggest/commit/43bd217938fc983a3e6b82d7a91c66f7dd1b2587). It's on the PR branch for #740, but committed & pushed after the branch was already merged, easy mistake to make.
I think it's probably best to leave the github tags as they are, given that (since there really is a correct 10.0.2 tag), but yes we should update straight to 10.0.3 when we release proper.

Now published :+1:


SSL Error on outgoing request

I have a Spin app running in k8s that works fine until I make an outgoing request to another resource.  This using the latest 0.9.2.
When do I get a generic error from the spin's stdout:
Handler returned an error: Uncaught SyntaxError: unexpected token: 'Uncaught'
    at <input>:1
    at parse (native)
    at <anonymous> (script.js:397)
    at call (native)
    at step (script.js:306)
    at <anonymous> (script.js)
    at fulfilled (script.js)

But looking at the containerd logs, I see this more specific error:
Outbound HTTP connection error: URL https://dummyjson.com/products/1, error detail reqwest::Error { kind: Request, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("dummyjson.com")), port: None, path: "/products/1", query: None, fragment: None }, source: hyper::Error(Connect, Ssl(Error { code: ErrorCode(5), cause: Some(Ssl(ErrorStack([Error { code:<PHONE_NUMBER>, library: "system library", function: "file_open", file: "providers/implementations/storemgmt/file_store.c", line: 267, data: "calling stat(/usr/local/ssl/certs)" }, Error { code:<PHONE_NUMBER>, library: "system library", function: "file_open", file: "providers/implementations/storemgmt/file_store.c", line: 267, data: "calling stat(/usr/local/ssl/certs)" }, Error { code:<PHONE_NUMBER>, library: "system library", function: "file_open", file: "providers/implementations/storemgmt/file_store.c", line: 267, data: "calling stat(/usr/local/ssl/certs)" }, Error { code:<PHONE_NUMBER>, library: "system library", function: "file_open", file: "providers/implementations/storemgmt/file_store.c", line: 267, data: "calling stat(/usr/local/ssl/certs)" }, Error { code: 167772294, library: "SSL routines", function: "tls_post_process_server_certificate", reason: "certificate verify failed", file: "ssl/statem/statem_clnt.c", line: 1889 }]))) }, X509VerifyResult { code: 20, error: "unable to get local issuer certificate" })) }
Any quick work arounds that I can look at to resolve?

Could this help? https://github.com/deislabs/containerd-wasm-shims/blob/main/images/slight/Dockerfile#L10C1-L10C36

I can try that @Mossaka, I didn't have to before with other versions of the shims.

Okay if you didn't run into this before with other versions, it might be a regression from either the Spin runtime or containerd-shim-wasm crate.
@jprendes have you seen this issue before?

I haven't seen it before.
@stevesloka could you share a reproduction example?

@jprendes yup, I essentially have an OCI image that I build and add the compiled wasm into. This all runs in k8s on EKS. I just was working to support Spin v1.5 so I used the latest 0.9.2 containerd-wasm-shim and deployed that into my cluster.
Doing some testing I noticed the runtime errors, locally they all work fine (i.e. not using the shim).
Here's my simple Spin app:
const encoder = new TextEncoder("utf-8")
const decoder = new TextDecoder("utf-8")

export async function handleRequest(request) {
    const res = await fetch("https://dummyjson.com/products/1")

    const body = decoder.decode(await res.arrayBuffer() || new Uint8Array())

    return {
        status: 200,
        body: encoder.encode(body).buffer
    }
}

If I have code that just returns static data, say a string, it works fine, but whenever I make an outgoing call as in the example previous, I get the containerd error noted in the first post.
Are there any other details that I can share that would help out?

I ran into exactly the same issue while experimenting with Spin and k8s during a hackathon. Eventually found out by digging through containerd logs of the workers. I tried both the Go and Python version of the outbound http example. The latter gave me a non-descriptive AssertionError: runtime-error (error 4) in the browser.
Dockerfile used:
FROM scratch
COPY ./spin.toml /spin.toml
COPY ./app.wasm /app.wasm
ENTRYPOINT ["/spin.toml"]

manifest:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: wasm-random-animal-fact
spec:
  replicas: 1
  selector:
    matchLabels:
      app: wasm-random-animal-fact
  template:
    metadata:
      labels:
        app: wasm-random-animal-fact
    spec:
      runtimeClassName: spin-test
      containers:
        - name: wasm-random-animal-fact
          imagePullPolicy: Always
          image: docker.io/hrak/random-animal-fact-wasm:0.0.2
          command: ["/"]
---
apiVersion: v1
kind: Service
metadata:
  name: wasm-random-animal-fact
spec:
  ports:
    - protocol: TCP
      port: 80
      targetPort: 80
  selector:
    app: wasm-random-animal-fact

Dec 01 12:32:12 testor-md-0-w5sgd containerd[1405]: time="2023-12-01T12:32:12.282773715Z" level=info msg="instantiate_async;"
Dec 01 12:31:25 testor-md-0-w5sgd containerd[1405]: time="2023-12-01T12:31:25.994484003Z" level=warn msg="Outbound HTTP connection error: URL https://random-data-api.fermyon.app/animals/json, error detail reqwest::Error { kind: Request, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("random-data-api.fermyon.app")), port: None, path: "/animals/json", query: None, fragment: None }, source: hyper::Error(Connect, Ssl(Error { code: ErrorCode(5), cause: Some(Ssl(ErrorStack([Error { code:<PHONE_NUMBER>, library: "system library", function: "file_open", file: "providers/implementations/storemgmt/file_store.c", line: 267, data: "calling stat(/usr/local/ssl/certs)" }, Error { code:<PHONE_NUMBER>, library: "system library", function: "file_open", file: "providers/implementations/storemgmt/file_store.c", line: 267, data: "calling stat(/usr/local/ssl/certs)" }, Error { code:<PHONE_NUMBER>, library: "system library", function: "file_open", file: "providers/implementations/storemgmt/file_store.c", line: 267, data: "calling stat(/usr/local/ssl/certs)" }, Error { code:<PHONE_NUMBER>, library: "system library", function: "file_open", file: "providers/implementations/storemgmt/file_store.c", line: 267, data: "calling stat(/usr/local/ssl/certs)" }, Error { code: 167772294, library: "SSL routines", function: "tls_post_process_server_certificate", reason: "certificate verify failed", file: "ssl/statem/statem_clnt.c", line: 1889 }]))) }, X509VerifyResult { code: 20, error: "unable to get local issuer certificate" })) }"ec 01 12:32:12 testor-md-0-w5sgd containerd[1405]: time="2023-12-01T12:32:12.482456071Z" level=error msg="Error processing request: error while executing at wasm backtrace:
Dec 01 12:32:12 testor-md-0-w5sgd containerd[1405]:     0: 0xcac9 - <unknown>!runtime.runtimePanicAt.llvm.2870195029891959485
Dec 01 12:32:12 testor-md-0-w5sgd containerd[1405]:     1: 0x59c1 - <unknown>!runtime.nilPanic.llvm.2870195029891959485
Dec 01 12:32:12 testor-md-0-w5sgd containerd[1405]:     2: 0x35958 - <unknown>!spin_http_handle_http_request
Dec 01 12:32:12 testor-md-0-w5sgd containerd[1405]:     3: 0x360af - <unknown>!__wasm_export_spin_http_handle_http_request
Dec 01 12:32:12 testor-md-0-w5sgd containerd[1405]:     4: 0x470ae - wit-component:adapter:wasi_snapshot_preview1!fermyon:spin/inbound-http#handle-request
Dec 01 12:32:12 testor-md-0-w5sgd containerd[1405]: Caused by:
Dec 01 12:32:12 testor-md-0-w5sgd containerd[1405]:     wasm trap: wasm `unreachable` instruction executed"

This is now fixed in https://github.com/spinkube/containerd-shim-spin/issues/44.


feat: hide sensitive information from the repository

…ation about it
Pull Request

Description

Type of Change

[x] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality
to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Task linked: CU-8689rrgmd Hide sensite information on the repository


Add custom template for "sysvinit" service provider

The default template looks very tricky and it doesn't work well on RHEL 6: there are some artifacts in the console output while we are doing service consul <stop | start>:
https://github.com/poise/poise-service/blob/d9a5135dbe5711214c377c8ee2e7af029b1f10b7/chef/templates/default/sysvinit.sh.erb
This PR adds a custom template for sysvinit provider which looks pretty clear and works fine.
It was inspired by the init script form "consul-rpm" project: consul.init
Verified on CentOS 6.7 and Debian 7.9
P.s. This PR could be related to https://github.com/johnbellone/consul-cookbook/issues/235, but it doesn't fix this issue. For  RHEL/CentOS 6 we still have to set provider to :sysvinit in explicit to avoid the usage of :upstart (https://github.com/johnbellone/consul-cookbook/issues/235#issuecomment-172462543).

:+1:


documentation is missing new features from blog

The following features mentioned in blog is missing in document:

[ ] Import type
[ ] Type cast
[ ] Flow comments
[ ] Bounded polymorphism

Yeah, doc updates are long overdue :( Will get to them soon.

8 months later...
As a newcomer to flow, I've found the docs quite hard to understand.

@mrjackdavis Soon now.

New documentation seems to cover everything on the list


Documents Updated

Hi, I'm a new and happy user of Compose and Transporter. But I see that if I update an doc on mongo, I have an new doc in ES. There is some way to update the same doc (with the same mongoID) also on ES?

Is this ES 2.0 or later?

I use ES 2.1.0

Please see pull request https://github.com/compose/transporter/pull/168

fixed in the latest release v0.1.2


lang: add built-in dynamic arrays

Extend the source language with a built-in dynamic array type (i.e., a run-time sized homogeneous sequence): seq. Sequence values are constructed with the Seq operator, sequence types with SeqTy.
Dynamic arrays are an important feature, needed by almost every program beyond the most simple test. The plan is to eventually have the type be a standard-library type, but due the source language lacking the necessary features (user-defined type constructors, type parameters for procedures, array types, pointer types, and var-like parameters) to implement it as such, the type is implemented as a language built-in for the moment.
seq element access is not implemented as part of this PR, as it requires a panic mechanism, which is better implemented separately.

To-Do

[x] implement the internal allocator (alloc, realloc, and dealloc)
[ ] implement the internal prepareAdd routine
[ ] implement destructor generation and destructor call injection
[ ] implement copy/clone generation and copy call injection
[ ] add tests for Seq and SeqTy
[ ] add tests for add, len, and clear
[ ] write a proper commit message

To keep the implementation simple(r) for now, and in order to not further complicate the still-in-progress pass rework, there's going to be no separate copy-to-move optimization pass or destructor injection pass (like there is in the NimSkull compiler).
Instead, all destructors and copy calls will be injected right away, as part of source2il. As a consequence, all usages of seq l-values outside of len, clear, and add calls require a full copy to be made. Once the pass rework is done, a copy-to-move optimization pass and the associated intermediate languages can be added, which will address this inefficiency.

I'm going to split the parts related to the allocator into their own PR, as they're quite involved and not dependent on the seq implementation.


test against Python 3.8

This PR is an attempt to test against Python 3.8.

Python 3.8 is passing!
The DISTUTILS_USE_SDK case is now failing because I removed Python 3.4 where it was being used and moved this case to 3.5. I think the util/appveyor/build.cmd would have to be updated to use a different version of MSVC/SDK than 3.4 did.

I think we should just remove DISTUTILS_USE_SDK and all will be well

Actually the tests for 3.8 were not run on Travis due to some pytest-related import error causing 0 tests to be found:
https://travis-ci.org/PyWavelets/pywt/jobs/599345508#L917-L954

I don't understand the import error on Travis, particularly the following section
../../../../virtualenv/python3.8.0/lib/python3.8/distutils/__init__.py:4: in <module>

    import imp

In my local copy of Python 3.8 there is no import imp at this location.
The test suite ran normally on Python 3.8 when I tried it locally on a 64-bit linux machine.

Codecov Report

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

@@            Coverage Diff            @@
##             master     #525   +/-   ##
=========================================
  Coverage          ?   63.51%
=========================================
  Files             ?       23
  Lines             ?     3892
  Branches          ?      467
=========================================
  Hits              ?     2472
  Misses            ?     1351
  Partials          ?       69

Continue to review full report at Codecov.

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

Marking this as WIP for now. I don't think it is useful to merge as is since the tests on 3.8 are not currently being run.
They did get run over at MacPython/pywavelets-wheels#9 and are passing there, so I think we can work on this again after the 1.1 release.

Ah I missed this one - should we merged as is?

Let me take a quick look again first. I think #540 might have fixed one of the issues here, but I think we may not need  8bb8661 and I see that the Appveyor case is still commented out here for some reason.

Okay, I think this looks good now. Probably want to squash the commits on merge to get rid of some of the noise (or I can do it manually if you prefer)


Fixed SpringArm3D::margin documentation

Fixes https://github.com/godotengine/godot/issues/76220
Fixes https://github.com/godotengine/godot-docs/issues/7189
This class behavior changed when ClippedCamera3D was removed by https://github.com/godotengine/godot/commit/b11bb595d137c82bbf30340ef7d8fdf6d6dc08de.
This PR is partially compatible with 3.x for cherrypick, see the list below regarding 3.x:

The margin is also not used when the shape is defined and the documentation does not explain it;
The line "This margin is useful for when the SpringArm has a [Camera]..." can be kept as is true in 3.x;
The part  " or when there is a [Camera3D] as direct child of the SpringArm3D" can be removed because https://github.com/godotengine/godot/commit/b11bb595d137c82bbf30340ef7d8fdf6d6dc08de wasn't merged in 3.x.

Hey @akien-mga I have reviewed on the issue and I don't think this is a documentation issue but rather a bug in the way SprintArm and ClippedCamera were merged into one.

@QbieShay I aggre that the behavior is a bug, but this documentation update reflects the actual state of the SpringArm3D.

I agree. While it's tempting to update the docs to describe a bug that affects the current behavior, this doesn't help resolve the problem. Perhaps the misleading statement can be removed until the bug is fixed, but documenting the bugged behavior as a normal part of the feature is not a good idea.