Update robotext message when thread type is changed

Currently, robotext says "you updated thread's type to "3"", and this doesn't give much information about new type

Steps to handle this:

[ ] extract logic to determine label for threads, introduced in D626, into function in thread-utils
[ ] add label for personal threads
[ ] update robotext to use new function and determine label for type

Steps to handle this:

[ ] extract logic to determine label for threads, introduced in D626, into function in thread-utils
[ ] add label for personal threads
[ ] update robotext to use new function and determine label for type

All done

All done


Could not find com.github.troZee:ViewPager2:v1.0.6.

Bug report

Summary
After installed via yarn add I cannot install app with npx react-native run-android. I've tried latest and older versions (4.0.1, 4.0.0).

`error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment. Run CLI with --verbose flag for more details.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':app:preDebugBuild'.

Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
Could not find com.github.troZee:ViewPager2:v1.0.6.
Searched in the following locations:
- file:/Users/leonamdepaula/.m2/repository/com/github/troZee/ViewPager2/v1.0.6/ViewPager2-v1.0.6.pom
- file:/Users/leonamdepaula/.m2/repository/com/github/troZee/ViewPager2/v1.0.6/ViewPager2-v1.0.6.jar
- file:/Users/leonamdepaula/MEGAsync/SciPet/CrowdPetRN/node_modules/react-native/android/com/github/troZee/ViewPager2/v1.0.6/ViewPager2-v1.0.6.pom
- file:/Users/leonamdepaula/MEGAsync/SciPet/CrowdPetRN/node_modules/react-native/android/com/github/troZee/ViewPager2/v1.0.6/ViewPager2-v1.0.6.jar
- file:/Users/leonamdepaula/MEGAsync/SciPet/CrowdPetRN/node_modules/jsc-android/dist/com/github/troZee/ViewPager2/v1.0.6/ViewPager2-v1.0.6.pom
- file:/Users/leonamdepaula/MEGAsync/SciPet/CrowdPetRN/node_modules/jsc-android/dist/com/github/troZee/ViewPager2/v1.0.6/ViewPager2-v1.0.6.jar
- https://dl.google.com/dl/android/maven2/com/github/troZee/ViewPager2/v1.0.6/ViewPager2-v1.0.6.pom
- https://dl.google.com/dl/android/maven2/com/github/troZee/ViewPager2/v1.0.6/ViewPager2-v1.0.6.jar
- https://jcenter.bintray.com/com/github/troZee/ViewPager2/v1.0.6/ViewPager2-v1.0.6.pom
- https://jcenter.bintray.com/com/github/troZee/ViewPager2/v1.0.6/ViewPager2-v1.0.6.jar
- https://sdks.instabug.com/nexus/repository/instabug-cp/com/github/troZee/ViewPager2/v1.0.6/ViewPager2-v1.0.6.pom
- https://sdks.instabug.com/nexus/repository/instabug-cp/com/github/troZee/ViewPager2/v1.0.6/ViewPager2-v1.0.6.jar
Required by:
project :app > project :react-native-community_viewpager`

Environment info

react-native info output:
System:
    OS: macOS 10.15.6
    CPU: (8) x64 Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
    Memory: 78.21 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.14.0 - ~/.nvm/versions/node/v12.14.0/bin/node
    Yarn: 1.22.4 - ~/.yarn/bin/yarn
    npm: 6.13.4 - ~/.nvm/versions/node/v12.14.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28
      Build Tools: 19.1.0, 20.0.0, 21.1.2, 22.0.1, 23.0.1, 23.0.2, 23.0.3, 24.0.0, 24.0.1, 24.0.2, 24.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.1, 26.0.2, 26.0.3, 27.0.1, 27.0.3, 28.0.2, 28.0.3
      System Images: android-17 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom_64, android-25 | Google APIs Intel x86 Atom_64, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-N | Intel x86 Atom, android-N | Intel x86 Atom_64
  IDEs:
    Android Studio: 3.6 AI-192.7<IP_ADDRESS>92135
    Xcode: 11.6/11E708 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.5 => 0.61.5

Library version: x.x.x
Steps to reproduce

…
…

Describe what you expected to happen:

…
…

Reproducible sample code

Hey,
Thank you for reporting an issue. I was trying to reproduce you issue here : https://github.com/troZee/viewPagerExample/commit/71912f8845bf38017610fe7184677f5f5f53a72e
But it seems like everything works fine. You can also try to add below code to path/to/your/project/example/android/build.gradle
buildscript {
    repositories {
         ....
        maven { url 'https://jitpack.io' }
    }
}

allprojects {
    repositories {
     .......
        maven { url 'https://www.jitpack.io' }
    }
}

Hey,
Thank you for reporting an issue. I was trying to reproduce you issue here : troZee/viewPagerExample@71912f8
But it seems like everything works fine. You can also try to add below code to path/to/your/project/example/android/build.gradle
buildscript {
    repositories {
         ....
        maven { url 'https://jitpack.io' }
    }
}

allprojects {
    repositories {
     .......
        maven { url 'https://www.jitpack.io' }
    }
}

Thanks a lot! That solved the issue!


Passwordless login should have less errors using Verify

Switch Auth0 to twilio verify via cloudflare workers
To improve success rate with passwordless sms auth

[x] worker should parse auth0 message and call twilio verify API
[x] return 200 on success or 400 on exception
[x] add authnetication with jsonwebtoken or simple secret in get params
[x] log errors to sentry - see GoodCFWorker
[x] setup auth0 to work with worker

https://auth0.com/docs/connections/passwordless/guides/use-sms-gateway-passwordless
https://www.twilio.com/docs/verify/api

finished development
waiting for integration with auth0

@sirpy passwordless login/sign up  works without errors
Checked on  QA 1.10.1-1
Desktop: Windows 10 // Google Chrome   87.0.4280.66


Update README

Updates some outdated text in the README re: Node version support and import syntax.
Adds jsdoc as an explicit dependency to suppress peerDependency warning.

Pull Request Test Coverage Report for Build 121

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

Totals

Change from base Build 120:
0.0%

Covered Lines:
351

Relevant Lines:
351

💛  - Coveralls


what are the mechnisms of "keywords" and "summary"? any documents about them?

 Issue by myrainbowandsky
Wed Aug 12 12:07:12 2020
Originally opened as https://github.com/codelucas/newspaper/issues/833

hey so any answers on how is the summary and the keywords are being generated i looked through the code too and found nothing ;-;


Register runBioSimulations namespace with Identifiers.org

Since we're trending toward treating simulation ids as permanent and encouraging authors to use them to reference simulations, I think we should register runBioSimulations with Identifers.org.
Here's the registration page: https://registry.identifiers.org/prefixregistrationrequest

Namespace Name: runBioSimulations
Description: runBioSimulations is a platform for sharing simulation experiments and their results. runBioSimulations enables investigators to use a wide range of simulation tools to execute a wide range of simulations. runBioSimulations permanently saves the results of these simulations, and investigators can share results by sharing URLs similar to sharing URLs for files with DropBox and Google Drive.
Requested prefix: runbiosimulations
Sample id: 60151262b20a749db077036e
Regex pattern: [0-9a-z]{24,24}
ROR id: https://ror.org/04a9tmd77

Home URL: https://icahn.mssm.edu/

Copy Institution details: Yes
Provider code: icahn
URL Pattern: https://run.biosimulations.org/simulations/{$id}

@bilalshaikh42 is the regex pattern for ids above correct? Would you like to submit this to Identifiers.org?

I submitted a request

Namespace is approved!


remove allow_merge

After the introduction of ci-orchestrator this is no longer needed

Codecov Report

Merging #91 (0611466) into main (02a3126) will decrease coverage by 22.42%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main      #91       +/-   ##
===========================================
- Coverage   81.53%   59.11%   -22.42%
===========================================
  Files         328      360       +32
  Lines        6131     7632     +1501
  Branches      597        0      -597
===========================================
- Hits         4999     4512      -487
- Misses        919     2897     +1978
- Partials      213      223       +10

see 243 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


GridMap: Initialize "navigation" pointer

Should fix #5122, but not tested.

I tested this, and it seems to work. The game hasn't crashed like it was doing before.

Tested too. Works good.
Without this patch, when using GridMap with NavMeshInstance, gotot might crash even 9/10 times
With this patch applied, after many runs it not crashed even once.
Good work :+1: