vagrant: Allow running several dev VMs concurrently

This pull request solves the conflict on the forwarded port of the dev VM to allow running several instances concurrently.

This change is

Coverage decreased (-0.003%) to 45.561% when pulling ac095a6846712bfbcfbede023f73b0328ca2d2a0 on pr/pchaigno/fix-conflict-vagrant-vms into 39729f31b0a06b93e22eab42e3be0840edf38180 on master.

@aanm 2 test VMs? test/Vagrantfile has the correct option set.

@pchaigno no, 2 dev VMs

@pchaigno NFS=1 K8S=1 NWORKERS=1 ./contrib/vagrant/start.sh

@aanm You mean you run this command in 2 different clones and it works? :thinking:

@pchaigno ah that I never tried. Only in the same clone

With NWORKERS=1, workers don't have forwarded ports, only the master does since we only need to connect kubectl to the master.


Faster atom.packages.getAvailablePackages

Description of the Change

Removes the unnecessary directory existence check. This path is read from fs.readdir, and so we are sure that it exists!

Increasing the performance of getting the list of all available atom packages

Quantitative Performance Benefits
For my setup (having 209 packages), it speeds up the command by ~10ms.
Possible Drawbacks
Nothing I can think of
Verification Process
I measured it using this method:
const t1 = window.performance.now()
const packages = atom.packages.getAvailablePackages()
console.log(window.performance.now() - t1)

// to check the result
console.log(packages)

Also, by using this change, it decreased the loading time of my package package-switch by using this custom command which implements the change:
https://github.com/aminya/package-switch/blob/003894af9eb31bb279721bb102788194078da086/src/bundles.ts#L90
Applicable Issues
Release Notes

Increasing the performance of getting the list of all available atom packages

The macOS single test failure is totally unrelated to this PR.

I believe that check is for whether it is a directory or file not whether the directory exists.
I'm guessing it will fail if there is a file in the packages directory without that check.

@UziTech I used the native withFileTypes in readdir to filter out non-folders. This is both fast and reliable.

Hey @aminya, thanks for the contribution 🙇♂
Please check the CI failure or even better run script/lint locally.

im new in the club , how to code is their any simple chain or blocks to learn plz help me.

@tada369 here are some "learn programming" beginner experiences, I hope they can help you!
https://www.javascript.com/try
https://try.ruby-lang.org/


no web page using Jruby 9.0.0

Hi.  I started a fresh middleman project, ensuring the right bundles & versions (list attached).
When I point firefox at either:

http://<IP_ADDRESS>:4567/
http://localhost:4567/

There's an unable to connect.  The console output when --Verbose is set, show a NIL object some place:

The exception comes from start, so looks fairly basic.
[2015-03-21 21:25:11] ERROR NoMethodError: undefined method `[]' for nil:NilClass

The first questions are,

Does middleman run with JRuby?
Are the right gems and version installed?
How can I find what is going wrong with all thos NIL object exceptions?
Since I've done nothing just a middleman init and server commands -- What can I do to trouble shoot this kind of thing?

Are there log or diagnostic options I can turn-on, etc?
Hope you can point me in the right direction.
Regards,
Will
Projects bundler list
----------------
jruby -S bundler list
Gems included by the bundle:
  * activesupport (4.1.10)
  * bundler (1.8.5)
  * celluloid (0.16.0)
  * chunky_png (1.3.4)
  * coffee-script (2.3.0)
  * coffee-script-source (1.9.1)
  * compass (1.0.3)
  * compass-core (1.0.3)
  * compass-import-once (1.0.5)
  * em-websocket (0.5.1)
  * erubis (2.7.0)
  * eventmachine (1.0.7)
  * execjs (2.4.0)
  * ffi (1.9.8)
  * haml (4.0.6)
  * hike (1.2.3)
  * hitimes (1.2.2)
  * hooks (0.4.0)
  * http_parser.rb (0.6.0)
  * i18n (0.7.0)
  * json (1.8.2)
  * kramdown (1.6.0)
  * listen (2.9.0)
  * middleman (3.3.10)
  * middleman-core (3.3.10)
  * middleman-livereload (3.1.1)
  * middleman-sprockets (3.4.2)
  * minitest (5.5.1)
  * multi_json (1.11.0)
  * padrino-helpers (0.12.5)
  * padrino-support (0.12.5)
  * rack (1.6.0)
  * rack-livereload (0.3.15)
  * rack-test (0.6.3)
  * rb-fsevent (0.9.4)
  * rb-inotify (0.9.5)
  * sass (3.4.13)
  * sprockets (2.12.3)
  * sprockets-helpers (1.1.0)
  * sprockets-sass (1.3.1)
  * thor (0.19.1)
  * thread_safe (0.3.5)
  * tilt (1.4.1)
  * timers (4.0.1)
  * tzinfo (1.2.2)
  * tzinfo-data (1.2015.1)
  * uber (0.0.13)
  * uglifier (2.7.1)

some -verbose output ...
----------------------
W:...> jruby -S middleman server  --verbose
WARN: Unresolved specs during Gem::Specification.reset:
      activesupport (>= 3.1, ~> 4.1.0)
WARN: Clearing out unresolved specs.
 Looks like current release is not yet final.

I'm doing some issue-gardening 🌿🌷🌾 and came across this issue.
Sorry that this has lingered for quite a while! I'd suggest either closing this issue or submitting a PR with an implementation as a starting point for discussion around this.


[Experimental]-[Tools]-[Documentation] Price update

Make slight changes to Updating_Legacy_JSON.md
Create price_to_string.py
Run price_to_string.py on all mods, grouped by folder.
Run black on all scripts.

some of this pr wasn't needed as its in another pr, pacifically "time": "$ m"

please appease TypoCheck and check typos in json, don't add them to .typo-ci.yml if its a typo fix it.

some of this pr wasn't needed as its in another pr, pacifically "time": "$ m"

I will make sure to check in future.

please appease TypoCheck and check typos in json, don't add them to .typo-ci.yml if its a typo fix it.

Didn’t TypoCheck pass? I didn’t touch typo-ci.yml.


Don't append :443 to https URLs

On an HTTPS domain using the standard port (443) it's redundant to append ":443" to the URL. This prevents adding the port to the URL unless the port is non-standard.

Thanks for the contribution!


How to use another button in the form

I want to use another button (not submit button) to do a action in the form.
When I click on the button, the form is submitted..
How to do that ?

Give it a type of "button" (type="button"). If you are using reactstrap's Button, simply handling the click (via onClick function) will have reactstrap set the type to "button".
HTML default is submit. Check out: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.

I did not give the type "button" to the reactstrap's Button.


Add test cases

chart:

[x] commons/util/chartutil

command:

[x]         command/showCommand
[x]         command/commandResult
[x]         parser/showCommandParser (one function not tested)

student (just some functions missing):

[ ]         student/assessment
[x]          student/name
[x]  student/score
[ ]  student/student
[ ]  student/uniqueStudentList(hashcode)
[ ]  student/tag
[ ]  student/nameEqualsPredicate

student lists (some functions missing):

[ ]         student/assessmentlist
[ ]  student/grouplist

chart analysis:

[x] student/assessmentStatistics - @ganhongyao
[x]        student/group + studentStatistics

model:

[x]         model/util/addressbook
[x]         model/util/modelmanager
[x]         model/util/userPref(hashcode)

i'm not sure if testable:

[x] logic/logicManager

I'll handle LogicManager and the non-student model tests.

@nbvannhi I finished some of showCommand already, but mostly missing the execute success cases. Can you add on from there?

I will do

student/assessment
student/assessmentlist
student/score

@nbvannhi I finished some of showCommand already, but mostly missing the execute success cases. Can you add on from there?

Hmm I just take a look at your PR and actually I have the same problem with testing charts. Perhaps @ganhongyao or @zhing22 can take a look at it #258

Hmm I just take a look at your PR and actually I have the same problem with testing charts. Perhaps @ganhongyao or @zhing22 can take a look at it #258

@leonghongfai @nbvannhi  May I know what's the issue with testing charts?

Hmm I just take a look at your PR and actually I have the same problem with testing charts. Perhaps @ganhongyao or @zhing22 can take a look at it #258

@leonghongfai @nbvannhi May I know what's the issue with testing charts?

There seems to be an issue with doing studentstatistics.toLineChart() in the test file. Tldr I couldnt seem to generate a Chart object properly.

oh no my problem. I'll try to fix it

let me know if anyone is doing anything under student, if not i will finish them up probably by tmr mid aftn

let me know if anyone is doing anything under student, if not i will finish them up probably by tmr mid aftn

@leonghongfai I'm doing Assessment, AssessmentList and Score

let me know if anyone is doing anything under student, if not i will finish them up probably by tmr mid aftn

@leonghongfai I'm doing Assessment, AssessmentList and Score

Okay noted!


docs: re-add Coming from OpenAPI

resolves https://github.com/asyncapi/website/issues/1856
adding https://www.asyncapi.com/docs/tutorials/getting-started/coming-from-openapi to v3
The only document that I think can talk about AsyncAPI 2.0 as it makes sense to have official document that talks about AsyncAPI evolution.

You made some JS changes, so you also need a JS code owner such as Akshat Nema to approve to merge 😄.
(inspired to give me JS maintainer access yet? 😂) @derberg

These fields are colored by default.

yes, it was intentional, it is like this in https://www.asyncapi.com/docs/tutorials/getting-started/coming-from-openapi (some props set to true by default). But anyway, I did some errors in colouring, now it is perfected 😄

Also, I see Parameters field not getting compared in this component.

not compared like others, only entire components is. Why do you think it ain't right?

not compared like others, only entire components is. Why do you think it ain't right?

I thought both are same 😅

/rtm

@alequetzalli you can approve again

/rtm


Implemented ExpressionStarter to eliminate the default 1=0 or 1=1 stub expressions

See comments from here:
https://github.com/scottksmith95/LINQKit/issues/30

Quick question ; is the 'Extend' method also gone?

I don't see it. Perhaps I removed too much?
I can easily put the extend method back before you accept the pull request if you want.

Yes please put that one back.

I put it back. I didn't see any unit tests specific to that method. But all Unit Tests are still passing after restoring that method.

I updated the readme and added the Extend extension method to ExpressionStarter too.

Thanks.
I'll merge all changes into the 'development' branch.

Merged into development branch, please review. If it's all correct, I'll merge to master and create a new NuGet.

I checked out the development branch. I think there is an issue with the DbAsyncTests breaking the build.
The type or namespace name 'TestContext' could not be found (are you missing a using directive or an assembly reference?)	LinqKit.Microsoft.EntityFrameworkCore.Tests..NETCoreApp,Version=v1.0
It looks like a using statement is comment out and it shouldn't be?
Line 7 //using LinqKit.EntityFramework.Tests;
Once I uncommented that, I had to change a few variables called db to _db. Then it all builds.
I ran the Unit Tests and it all passes. So update DbAsyncTests and it will be good to go. I had to modify four lines.
line 7  using LinqKit.EntityFramework.Tests;
line 29            _db = new TestContext(builder.Options);
line 30            _db.Database.EnsureCreated();
line 49            _db.Database.EnsureDeleted();

Fix in dev.


Proposal: Documentation enhancement in requirements

Please add in "Prerequisites" section on which not yet officially released functionalities of kernel/iproute2 cilium depends.

Good point. Being addressed in PR #236

Fixed in #236


Sap system health computation

Implement the SAP systems and HANA database health computation. The health is used to display the green/yellow/red icons in the SAP systems list, and in the future in the new home dashboard.
The health is computed in the next way:

If 1 of the instances in the SAP system is in RED - System is RED
If 1 of the instances in the SAP system is in YELLOW, and there is not RED - System is YELLOW
If 1 of the instances in the SAP system is GRAY, and the previous conditions don't match - System is GRAY
GREEN otherwise

The attached HANA databases health on the SAP systems is used as well to compute the system health

@arbulu89 didn't read the code, but what happens if the agent cannot collect the info. Like, the system worked before, but suddenly we cannot collect the data anymore? I assume it should raise Red on the system too.

This is out of scope. We have not defined what would happen in that scenario, when we don't have updates, and actually it is not something easy to do. By now, we agreed with @abravosuse to only use the current sapcontrol output to compute the health.
But I guess in the future we can start thinking about what to do when we don't have updates, like using the health of the hosts belonging to this system as additional info, and if we don't have an heartbeat them, set the system health as red/warning.

@arbulu89 all good... @abravosuse one more item for backlog ;)


Filter results using properties in a jsonb column

This feature allows you to query /table?col->>prop=eq.value or path deeper into the json with /table?col->foo->bar->>prop=eq.value. It fixes #118

@begriffs this is awesome! Could you add it to the docs though? I couldn't find it anywhere.

@adilapapaya good point. Want to try contributing it to the docs? The README at https://github.com/begriffs/postgrest-docs describes how to clone the repo and preview changes locally. You could open a PR and I'd be happy to review it and answer any questions you might have about the process.


Refresh token on success

I'm using your library, good job making this its so useful!,
the response i'm getting when i login with google (doesn't have a refresh token)
why there is no refresh_token returned?, my business requires a refresh token, but i can't get it using your library, can you kindly support?

https://github.com/MomenSherif/react-oauth/issues/6#issuecomment-1127381653
authorization code flow and exchange it with tokens

tmam shukrn lek gdn <3
On Wednesday, July 10, 2024 at 12:27:11 PM GMT+3, MomenSherif @.***> wrote:
#6 (comment)
authorization code flow and exchange it with tokens
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Unable to start this project, fresh out of the box on gitpod.io

Unable to start out of the box; with following errors after npm install build etc. Posting in hope that someone might be able to figure out and help future users.
Regards,
Asad.
Gitpod:
https://cfd00c96-4858-446a-aee3-1effe4e0b3d8.ws-eu01.gitpod.io/#/workspace/react-app-rewired
gitpod /workspace/react-app-rewired $ npm run-script build

<EMAIL_ADDRESS>build /workspace/react-app-rewired
yarn --cwd 'test/react-app' build

yarn run v1.22.0
$ react-app-rewired build
Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run next command yarn upgrade caniuse-lite browserslist
Failed to compile.
Failed to minify the bundle. Error: static/js/main.432ca667.chunk.js from Terser
TypeError: Cannot read property 'minify' of undefined
at compiler.run (/workspace/react-app-rewired/node_modules/react-scripts/scripts/build.js:169:23)
at finalCallback (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:210:39)
at hooks.done.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:226:13)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR<EMAIL_ADDRESS>start: yarn --cwd 'test/react-app' start
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/gitpod/.npm/_logs/2020-03-02T14_29_29_171Z-debug.log
gitpod /workspace/react-app-rewired $ npm install
npm WARN deprecated<EMAIL_ADDRESS>Way too old
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated<EMAIL_ADDRESS>use String.prototype.padStart()
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit https://github.com/lukeed/kleur/releases/tag/v3.0.0\ for migration path(s).
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN rm not removing /workspace/react-app-rewired/node_modules/.bin/jest as it wasn't installed by /workspace/react-app-rewired/node_modules/jest
npm WARN rm not removing /workspace/react-app-rewired/node_modules/.bin/uglifyjs as it wasn't installed by /workspace/react-app-rewired/node_modules/uglify-js
npm WARN rm not removing /workspace/react-app-rewired/node_modules/.bin/regjsparser as it wasn't installed by /workspace/react-app-rewired/node_modules/regjsparser
npm WARN rm not removing /workspace/react-app-rewired/node_modules/.bin/json5 as it wasn't installed by /workspace/react-app-rewired/node_modules/json5
npm WARN rm not removing /workspace/react-app-rewired/node_modules/.bin/jsesc as it wasn't installed by /workspace/react-app-rewired/node_modules/jsesc
npm WARN rm not removing /workspace/react-app-rewired/node_modules/.bin/esparse as it wasn't installed by /workspace/react-app-rewired/node_modules/esprima
npm WARN rm not removing /workspace/react-app-rewired/node_modules/.bin/esvalidate as it wasn't installed by /workspace/react-app-rewired/node_modules/esprima
npm WARN rm not removing /workspace/react-app-rewired/node_modules/.bin/cssesc as it wasn't installed by /workspace/react-app-rewired/node_modules/cssesc

<EMAIL_ADDRESS>postinstall /workspace/react-app-rewired/node_modules/core-js
node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:

https://opencollective.com/core-js
https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
npm notice created a lockfile as package-lock.json.  Did you mean to npm run-script build?
gitpod /workspace/react-app-rewired $ npm start

<EMAIL_ADDRESS>start /workspace/react-app-rewired
yarn --cwd 'test/react-app' start

yarn run v1.22.0
$ react-app-rewired start
/bin/sh: 1: react-app-rewired: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR<EMAIL_ADDRESS>start: yarn --cwd 'test/react-app' start
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/gitpod/.npm/_logs/2020-03-02T14_32_39_849Z-debug.log
gitpod /workspace/react-app-rewired $ npm install react-app-rewired
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/react-scripts/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

<EMAIL_ADDRESS>added 1 package, removed 75 packages and audited 39498 packages in 17.748s

28 packages are looking for funding
run npm fund for details
found 66 vulnerabilities (63 low, 2 moderate, 1 high)
run npm audit fix to fix them, or npm audit for details
gitpod /workspace/react-app-rewired $ npm audit fix
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/react-scripts/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
removed 75 packages in 15.33s
28 packages are looking for funding
run npm fund for details
fixed 0 of 66 vulnerabilities in 39498 scanned packages
1 package update for 66 vulnerabilities involved breaking changes
(use npm audit fix --force to install breaking changes; or refer to npm audit for steps to fix these manually)
gitpod /workspace/react-app-rewired $ npm build
npm WARN build npm build called with no arguments. Did you mean to npm run-script build?
gitpod /workspace/react-app-rewired $ npm run-script build

<EMAIL_ADDRESS>build /workspace/react-app-rewired
yarn --cwd 'test/react-app' build

yarn run v1.22.0
$ react-app-rewired build
internal/modules/cjs/loader.js:638
throw err;
^
Error: Cannot find module 'customize-cra'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object. (/workspace/react-app-rewired/test/react-app/config-overrides.js:3:5)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: yarn --cwd 'test/react-app' build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/gitpod/.npm/_logs/2020-03-02T14_34_52_297Z-debug.log
gitpod /workspace/react-app-rewired $ npm install -save customize-cra
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/react-scripts/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

<EMAIL_ADDRESS>added 2 packages from 4 contributors, removed 75 packages and audited 39500 packages in 18.211s

28 packages are looking for funding
run npm fund for details
found 66 vulnerabilities (63 low, 2 moderate, 1 high)
run npm audit fix to fix them, or npm audit for details
gitpod /workspace/react-app-rewired $ npm run-script build

<EMAIL_ADDRESS>build /workspace/react-app-rewired
yarn --cwd 'test/react-app' build

yarn run v1.22.0
$ react-app-rewired build
Creating an optimized production build...
Failed to compile.
./src/index.js
Cannot find module: 'react'. Make sure this package is installed.
You can install this package by running: yarn add react.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: yarn --cwd 'test/react-app' build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/gitpod/.npm/_logs/2020-03-02T14_36_18_282Z-debug.log
gitpod /workspace/react-app-rewired $ yarn add react
yarn add v1.22.0
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 4 new dependencies.
info Direct dependencies
├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>info All dependencies
├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>Done in 15.41s.
gitpod /workspace/react-app-rewired $ npm run-script build

<EMAIL_ADDRESS>build /workspace/react-app-rewired
yarn --cwd 'test/react-app' build

yarn run v1.22.0
$ react-app-rewired build
Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run next command yarn upgrade caniuse-lite browserslist
Failed to compile.
./src/index.js
Cannot find module: 'react-dom'. Make sure this package is installed.
You can install this package by running: yarn add react-dom.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: yarn --cwd 'test/react-app' build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/gitpod/.npm/_logs/2020-03-02T14_37_09_968Z-debug.log
gitpod /workspace/react-app-rewired $ yarn add react-dom
yarn add v1.22.0
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 2 new dependencies.
info Direct dependencies
└─<EMAIL_ADDRESS>info All dependencies
├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>Done in 7.96s.
gitpod /workspace/react-app-rewired $ npm run-script build

<EMAIL_ADDRESS>build /workspace/react-app-rewired
yarn --cwd 'test/react-app' build

yarn run v1.22.0
$ react-app-rewired build
Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run next command yarn upgrade caniuse-lite browserslist
Failed to compile.
Failed to minify the bundle. Error: static/js/main.432ca667.chunk.js from Terser
TypeError: Cannot read property 'minify' of undefined
at compiler.run (/workspace/react-app-rewired/node_modules/react-scripts/scripts/build.js:169:23)
at finalCallback (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:210:39)
at hooks.done.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:226:13)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/workspace/react-app-rewired/node_modules/tapable/lib/Hook.js:154:20)
at onCompiled (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:224:21)
at hooks.afterCompile.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:553:14)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/workspace/react-app-rewired/node_modules/tapable/lib/Hook.js:154:20)
at compilation.seal.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:550:30)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/workspace/react-app-rewired/node_modules/tapable/lib/Hook.js:154:20)
at hooks.optimizeAssets.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compilation.js:1295:35)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/workspace/react-app-rewired/node_modules/tapable/lib/Hook.js:154:20)
at hooks.optimizeChunkAssets.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compilation.js:1286:32)
Read more here: http://bit.ly/CRA-build-minify
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: yarn --cwd 'test/react-app' build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/gitpod/.npm/_logs/2020-03-02T14_38_06_041Z-debug.log
gitpod /workspace/react-app-rewired $ yarn upgrade caniuse-lite browserslist
yarn upgrade v1.22.0
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Rebuilding all packages...
success Saved lockfile.
success Saved 0 new dependencies.
Done in 7.26s.
gitpod /workspace/react-app-rewired $ yarn upgrade build-scripts
yarn upgrade v1.22.0
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Rebuilding all packages...
success Saved lockfile.
success Saved 0 new dependencies.
Done in 7.04s.
gitpod /workspace/react-app-rewired $ npm run-script build

<EMAIL_ADDRESS>build /workspace/react-app-rewired
yarn --cwd 'test/react-app' build

yarn run v1.22.0
$ react-app-rewired build
Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run next command yarn upgrade caniuse-lite browserslist
Failed to compile.
Failed to minify the bundle. Error: static/js/main.432ca667.chunk.js from Terser
TypeError: Cannot read property 'minify' of undefined
at compiler.run (/workspace/react-app-rewired/node_modules/react-scripts/scripts/build.js:169:23)
at finalCallback (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:210:39)
at hooks.done.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:226:13)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/workspace/react-app-rewired/node_modules/tapable/lib/Hook.js:154:20)
at onCompiled (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:224:21)
at hooks.afterCompile.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:553:14)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/workspace/react-app-rewired/node_modules/tapable/lib/Hook.js:154:20)
at compilation.seal.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:550:30)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/workspace/react-app-rewired/node_modules/tapable/lib/Hook.js:154:20)
at hooks.optimizeAssets.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compilation.js:1295:35)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/workspace/react-app-rewired/node_modules/tapable/lib/Hook.js:154:20)
at hooks.optimizeChunkAssets.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compilation.js:1286:32)
Read more here: http://bit.ly/CRA-build-minify
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: yarn --cwd 'test/react-app' build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/gitpod/.npm/_logs/2020-03-02T14_39_47_104Z-debug.log
gitpod /workspace/react-app-rewired $ yarn upgrade caniuse-lite browserslist
yarn upgrade v1.22.0
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Rebuilding all packages...
success Saved lockfile.
success Saved 0 new dependencies.
Done in 7.41s.
gitpod /workspace/react-app-rewired $ npm run-script build

<EMAIL_ADDRESS>build /workspace/react-app-rewired
yarn --cwd 'test/react-app' build

yarn run v1.22.0
$ react-app-rewired build
Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run next command yarn upgrade caniuse-lite browserslist
Failed to compile.
Failed to minify the bundle. Error: static/js/main.432ca667.chunk.js from Terser
TypeError: Cannot read property 'minify' of undefined
at compiler.run (/workspace/react-app-rewired/node_modules/react-scripts/scripts/build.js:169:23)
at finalCallback (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:210:39)
at hooks.done.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:226:13)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/workspace/react-app-rewired/node_modules/tapable/lib/Hook.js:154:20)
at onCompiled (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:224:21)
at hooks.afterCompile.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:553:14)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/workspace/react-app-rewired/node_modules/tapable/lib/Hook.js:154:20)
at compilation.seal.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compiler.js:550:30)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/workspace/react-app-rewired/node_modules/tapable/lib/Hook.js:154:20)
at hooks.optimizeAssets.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compilation.js:1295:35)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/workspace/react-app-rewired/node_modules/tapable/lib/HookCodeFactory.js:32:10), :6:1)
at AsyncSeriesHook.lazyCompileHook (/workspace/react-app-rewired/node_modules/tapable/lib/Hook.js:154:20)
at hooks.optimizeChunkAssets.callAsync.err (/workspace/react-app-rewired/node_modules/webpack/lib/Compilation.js:1286:32)
Read more here: http://bit.ly/CRA-build-minify
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: yarn --cwd 'test/react-app' build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/gitpod/.npm/_logs/2020-03-02T14_41_11_154Z-debug.log

Did you create the initial project using create-react-app? Reading the log it looks like you've tried to run react-app-rewired without actually creating a CRA project first. A CRA project should have already installed the react & react-dom dependencies (along with a whole lot of other things) so that you wouldn't have had errors stating that those packages were not found in your build log.


The plugin stop tracking location randomly until user manually open the app again

Your Environment

Plugin version: 4.10.0
Platform: iOS and Android (provided logs are from Android device, but the client I'm developing this app for, has reported this same problem in iOS, before I've implemented the logger, if it happens again, will post those logs too)
Device OS version: Android 13 (under MIUI 14)
Device manufacturer / model: Xiaomi 11T Pro
XCode version: -
Capacitor info (npx cap doctor)

  @capacitor/cli: 4.7.1
  @capacitor/core: 4.7.1
  @capacitor/android: 4.7.1
  @capacitor/ios: 4.7.1

Installed Dependencies:

  @capacitor/core: 4.4.0
  @capacitor/cli: 4.4.0
  @capacitor/android: 4.4.0
  @capacitor/ios: 4.4.0

Plugin config provided to #ready:

{
            // Geolocation Config
            desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_LOW,
            distanceFilter: 100,
            // Activity Recognition
            stopTimeout: 5,
            // Application config
            // debug: true, // <-- enable this hear sounds for background-geolocation life-cycle.
            logLevel: BackgroundGeolocation.LOG_LEVEL_DEBUG,
            logMaxDays: 7,
            stopOnTerminate: false,   // <-- Allow the background-service to continue tracking when user closes the app.
            startOnBoot: true,        // <-- Auto start tracking when device is powered-up.,
            url: environment.apiUrl + '/jwt/ubicacion/update',
            params: {
                tipo: this.platform.is('ios') ? 'ios' : 'android',
                userId: this.usuario.id
            },
            authorization: {
                strategy: 'JWT',
                accessToken: this.token
            },
            backgroundPermissionRationale: {
                title: 'Permitir a {applicationName} acceder a la ubicación del dispositivo en segundo plano?',
                message: 'Para poder mantener tu ubicación actualizada en segundo plano, por favor activa {backgroundPermissionOptionLabel} en los permisos de Ubicación. Esto es necesario para que la aplicación funcione correctamente y puedas compartir con tus amigos tu ubicación actual. Puedes desactivar esta funcionalidad en cualquier momento desde el menú de inicio.',
                positiveAction: 'Cambiar a {backgroundPermissionOptionLabel}',
                negativeAction: 'Cancelar'
            },
            locationAuthorizationAlert: {
                titleWhenOff: 'Activa tu ubicación en modo SIEMPRE',
                titleWhenNotEnabled: 'Activa tu ubicación en modo SIEMPRE',
                instructions: 'Para poder mantener tu ubicación actualizada en segundo plano, por favor activa "Siempre" en los permisos de Ubicación. Esto es necesario para que la aplicación funcione correctamente y puedas compartir con tus amigos tu ubicación actual. Puedes desactivar esta funcionalidad en cualquier momento desde el menú de inicio.',
                cancelButton: 'Cancelar',
                settingsButton: 'Configuración'
            },
            notification: {
                priority: BackgroundGeolocation.NOTIFICATION_PRIORITY_MIN,
                text: 'Actualizando tu ubicación',
                smallIcon: 'drawable/ic_stat_onesignal_default',
                largeIcon: 'drawable/ic_stat_onesignal_default',
            }
            // batchSync: true,
            // autoSyncThreshold: 5
        }

Expected Behavior
Plugin should keep tracking location despite the user manually open the app or not
Actual Behavior
If the user doesn't manually open the app, it randomly stops tracking location until it's manually opened again
Steps to Reproduce

Init the plugin
Close the app and don't manually open it again
I don't know which one is the exact trigger, but the attached logs clearly shows the problem

Context
Trying to correctly track the device location without manually opening every few hours/days (and without rebooting the device).
I've manually opened the app on 03-22 16:10:36, took a flight from Santiago to Lima on 03-23 10:27:18, went out on destination (by car and by foot) after arrival on 03-23 13:46:12, took a flight back to Santiago on 03-24 16:20:03 - until this point everything worked perfectly. Landed on 03-24 19:46:44, turned off airplane mode, the app sent some location points from Lima airport and then stopped tracking at all. Took a 30km car ride back home and nothing, it didn't showed up the persistent notification either (it's important to mention that this same trip correctly shows up on Google Timeline). Two hour after that on 03-24 21:51:28 I've manually opened the app, got the correct location (but the app didn't sent it to the server) and the day after, on 03-25 12:49:12 went out by foot and the app started tracking back. So from 03-24 19:46:44 until 03-25 12:49:12, our server thought I was still at Lima airport, when in fact I was back home by 03-24 21:05.
The relevant time points in the logs have the same hours as described above.
UPDATE:
I don't know if it could be related, but I went out by foot again on 03-25 16:38:45 where the logs shows up something, but the plugin didn't tracked the first location point and sent it to the server until 03-25 16:45:03.
Debug logs

Logs
Github throws "There was an error creating your Issue: body is too long, body is too long (maximum is 65536 characters)."

Please download it from https://www.dropbox.com/s/rkatrnw6khy7bdh/background-geolocation%282%29.log.gz?dl=0

At 03-24 19:46, the plugin correctly entered the stationary state and monitored a geofence around that position at the airport.  The device was only able to provide a poor accuracy location of hAcc=1200.0.

03-24 19:47:22.844 DEBUG [TSGeofenceManager startMonitoringStationaryRegion]
  🎾  Start monitoring stationary region (radius: 150.0m -33.3896022,-70.7861659 hAcc=1200.0)
03-24 19:47:22.855 DEBUG [AbstractService start]
  🎾  TrackingService [eventCount: 1]
03-24 19:47:22.855 INFO [TrackingService handleMotionChangeResult]
╔═════════════════════════════════════════════
║ TrackingService motionchange: false
╠═════════════════════════════════════════════

About 30s later, a providerchange change location was acquired (again with a poor accuracy of hAcc=1299.999 meters.  The plugin reacquires the stationary geofence here, at the other side of the airport.

╔═════════════════════════════════════════════
║ providerchange LocationResult: 5
╠═════════════════════════════════════════════
╟─ 📍  Location[fused -33.386979,-70.801404 hAcc=1299.999 et=+4d5h57m35s931ms vel=0.0], age: 1499ms, time:<PHONE_NUMBER>614

03-24 19:48:17.119 INFO [TSLocationManager onSingleLocationResult]
  🔵  Acquired providerchange position
03-24 19:48:17.128 DEBUG [LocationRequestService handleLocationResult] SingleLocationRequest 5 isFinished? true
03-24 19:48:17.128 DEBUG [AbstractService finish] ⚙  finish LocationRequestService [eventCount: 0, sticky: false]
03-24 19:48:17.130 INFO [b persist]
  ✅  INSERT: 2354e899-3dd4-4306-b10a-79aba4cc3b75
03-24 19:48:17.130 DEBUG [AbstractService finish] ⚙  finish LocationRequestService [eventCount: 0, sticky: false]
03-24 19:48:17.131 DEBUG [TSLocationManager$b onLocation]
  ℹ  Distance from last location: 2452658.2
03-24 19:48:17.132 DEBUG [TSGeofenceManager startMonitoringStationaryRegion]
  🎾  Start monitoring stationary region (radius: 150.0m -33.3869792,-70.8014035 hAcc=1299.999)

The plugin will automatically initiate tracking when the device exits that 150m geofence.  Geofences are monitored by the OS -- It's up to the OS to fire a geofence event if the device exits that area or the motion-activity API (also monitored by the OS) reports that the device is in-motion (on_foot, in_vehicle, on_bicycle, etc).
Sometimes, due to the environment and/or the device, things just don't work.

Thanks, what are the possible reasons for Google Timeline to be correctly tracking the airport-home trip, while the plugin didn't? Just the geofence? Is there any setting that could be tested against this problem?
I can keep providing the logs when this happen again with other devices, but for instance I remember a few weeks ago something similar happened with my own device: took a car from point A to point B (around 1 linear KM), the plugin didn't tracked the trip, 2 hours later, went by foot from point B to point A and less than a minute from the start point B, the persistent notification showed up and the plugin started tracking the trip correctly (without opening the app or doing anything else).
I understand (and totally agree) from the technical point of view that sometimes thing just don't work, but if it's not possible to keep this situations at minimal occurrences with another settings, I'll need to explain to my client with simple words why.

Google Timeline to be correctly tracking the airport-home trip, while the plugin didn't? Just the geofence?

Geofence + motion api did not trigger.

Is there any setting that could be test against this problem

no
I do not have any issues like this on my devices.  See https://dontkillmyapp.com
Your problem is likely related to your particular device.  There are many Android devices that have problems (as seen at https://dontkillmyapp.com)

I guess that if an app gets killed it doesn't autostart later by its own?

Yes it does.

Today it happened again, with an iPhone 8 (iOS 14.8) this time. My client was at point A, we met at point B and I was at point C.
My device correctly tracked from point C to B and then back from B to C. His device correctly tracked from point A (2023-03-28 11:11:35) to point B (2023-03-28 11:48:23), then got stuck at point B. When he was back to point A, he manually opened the app (2023-03-28 13:36:24) and some location points from 40 minutes before that time-point (when he started the trip back) started being sent out to the server. It's important to mention that from point A to point B he was constantly using the app every few minutes, then for the trip back I've asked him to keep it closed the entire trip to check the background behavior.
Please find the logs on this link: https://www.dropbox.com/s/od2jiu533fb1xi1/background-geolocation(3).log.gz?dl=0

Your DB data is not interesting to me.  I suggest you fetch the plug-in logs and see what the plug-in was saying in its logs during any times of interest.

See wiki “Debugging” to learn about using the .emailLog method to fetch plug-in logs.

That was the second message as support for the first one that has the plugin logs, fetched with .emailLog as seen on "Debugging" on the Wiki.
First message: https://github.com/transistorsoft/capacitor-background-geolocation/issues/156#issuecomment-1487309709
Second message: https://github.com/transistorsoft/capacitor-background-geolocation/issues/156#issuecomment-1487336448

logLevel: BackgroundGeolocation.LOG_LEVEL_DEBUG

When you have a problem, use LOG_LEVEL_VERBOSE.

When you see the following in the logs, your app has been re-launched after being terminated (terminated by the user, the OS, or your app crashed)
2023-03-28 13:38:03.862 ℹ-[TSLocationManager init]
╔═════════════════════════════════════════════
║ TSLocationManager (build 388)
╠══════════════════════════════════════════════
{

Thanks, I've just uploaded the new version with VERBOSE level.
Meanwhile, why if the app is being terminated, is still recording the location points, but not uploading them unless the user manually opens the app?
And then it kept uploading them (I guess that in the same queue order) for more than an hour: from 2023-03-28 13:36:25 to 2023-03-28 14:43:32 it kept uploading the corresponding points from 2023-03-28 12:56:00 to 2023-03-28 13:29:00.
Also it has a 100m distanceFilter, and on trip from B to A (not working as expected) recorded around 10-15 different location points per minute on a car trip, while on trip from A to B (worked as expected), it recorded 1-3 max different location points per minute. Same conditions for both trips. Does that tells anything about the problem?

I suggest you post a map view of your points here or configure the plug-in to upload locations to the demo server at tracker.transistorsoft.com (see api docs TransistorAuthorizationToken).

Sure,
Trip from point A to point B, 29 minutes, 54 location points uploaded real time:

Trip from point B to point A, 37 minutes (includes a 5 minute walk to his car), 434 location points uploaded over 4.5 hours (the upload started when the user manually opened the app, when he got back at point A):

Here's another case of the same problem, iPhone XR iOS 16.3.1 this time. Please take a look to 2023-04-11 12:37, until that point everything worked as expected that day. Then the user didn't opened the app until the next log entry 2023-04-12 19:09. At that point and until 2023-04-12 20:22, it started to upload hundreds of location points corresponding from 2023-04-11 13:10:00 to 2023-04-12 19:02:00. Then it suddenly stopped uploading, until the next time the user manually opened the app at 2023-04-13 18:16:05 when started to upload the rest of that trip from 2023-04-12 19:02:00 to 2023-04-12 19:20:00.
Here are some screens of the trips the user made, and their upload time:

Please find the log on this link: https://www.dropbox.com/s/mt6cy018utsyuoh/background-geolocation(10).log.gz?dl=0
When the upload finished, it worked OK for some points and then began the exact same behavior, starting at 2023-04-14 20:03:40, as seen on this second log file: https://www.dropbox.com/s/mpvwxwa9oqqufs2/background-geolocation(11).log.gz?dl=0
Please let me know if you need any further information.

@christocracy did you had a chance to check on this issue? It seems to be working fine in Android, but it's randomly showing up this behavior across Apple devices. I have two more cases on two different iPhone's, in case you need those logs.
It's always the same: the route it's being correctly recorded, but it's not uploaded to the server unless the user manually open the app. Also, when this behavior appears, it begins to record way more location points than it should (currently it's configured for 150m and in car trips the location points are being recorded about every 80m or even less).

I suggest you install the /example app in this repo onto your device and compare its performance.

(currently it's configured for 150m and in car trips the location points are being recorded about every 80m or even less).

Your logs show the plugin is clearly configured for distanceFilter = 75
If your app enters the background while the plugin is in the stationary state (that is, where location-services are OFF), iOS provides exactly 30s of background-time for you app to remain alive.
If the plugin has a large amount of records queued up in its SQLite database while in that state, the OS is only going to allow the plugin to upload for 30s.  The next time the app comes to foreground, the plugin's HTTP service will resume.
Also, the plugin is subscribed to background-fetch events which will also periodically allow the plugin's HTTP service to resume for 30s blocks of time.
One odd thing about your logs I see is a constant loss of speed reading between locations (speed 3.86 mps, speed -1.00 mps).  When speed shows -1 and `accuracy 40-60m, it means that the location likely didn't come from GPS (likely came from Wifi).
2023-04-10 15:49:31.174
📍<-33.40064475,-70.54767574> +/- 6.32m (speed 3.86 mps / course 209.97) @ 10-04-23 15:49:31 Chile Standard Time
.
.
.
2023-04-10 15:49:44.692
📍<-33.40197558,-70.54836166> +/- 40.00m (speed -1.00 mps / course -1.00) @ 10-04-23 15:49:44 Chile Standard Time
.
.
.

The plugin auto-scales distanceFilter based upon speed.
When there is no speed available (speed is provided by GPS satellites), the plugin must reset its distanceFilter to the configured value (75 in your case).

I don't think this is a problem with the plugin -- I think it's related to the environment.

Thanks Chris, that's very useful information. If you take a look to the last log, you can see that the distanceFilter have been changed from 75 to 150. In the screens set (with 75m configured), when the problem shows up, the distance goes down to about 30m. But in the last log, with 150m configured as distance filter, it goes down to about 80m.
We're testing different configurations in order to study different behaviors, right now we're going to test it with distanceFilter=250, disableElasticity=true and DESIRED_ACCURACY_HIGH. I'm waiting for the AppStore release of that version.
During the week I've been doing some DB analysis also. One key finding is that the problem started right away after the release of the first version on the AppStore. For instance, for a given person, using the same device, same user, same settings, same environment, same daily routes, etc, it gave less than 1% of delays on the uploaded location points while we were testing the app over TestFlight during a 7 weeks period. After the release to the AppStore, for that same person/device, it gave 29% of delays on the uploaded points for a similar 7 weeks period.
Do you have any idea what could be causing something like that on the release version?
About half of the Apple users shows that same behavior: over TestFlight, 10 users and all of them with less than 1% (there was just one user with 2.5% as maximum). Over AppStore, 18 users, 17% of delays in average, with 1% minimum and 48% maximum. 10 users with less than 5% and the other 8 with 28% in average.

Do you have any idea what could be causing something like that on the release version?

I have no idea.  This plug-in has thousands of customers (with presumably millions of device installs).  Nobody else is reporting this sort of thing.
iOS 16.4 made some changes.  If I were you, I would configure showsBackgroundLocationIndicator: true.
If I were concerned with too much data, i would definitely not configure disableElasticity: true

Thanks, I've added showsBackgroundLocationIndicator: true to the next version.
I have the results of the last version test. With this last information we can assure that there's definitively something wrong with the plugin, at least while this behavior is present. I understand that the other 1000's customers aren't reporting this problem, but that doesn't make it disappear by it's own.
I've added an additional API POST (using Angular Http) inside the onLocation event and that one is working flawless until now at least (less than 1% delays).
As you can see on the following screens, this is the same trip, uploaded by the plugin's built-in API POST mechanism:

And then the one uploaded by the API call inside onLocation event:

The built-in API POST didn't started uploading the trip until the user manually opened the app at 2023-04-30 16:46:08, while the onLocation event API POST started right away when the user started the trip at 2023-04-30 15:35:51.
Also there was nothing being logged between 2023-04-30 11:53:44 and 2023-04-30 16:46:07, despite I'm making a direct call to "debug" logger method inside onLocation event (I've added some custom messages in order to track onLocation and onHttp events).
Beside that, the points are being recorded about each 60m, while the configuration is 250m with disableElasticity=true. But when the plugin works correctly, it does record about 250m (all the screens are from the same user, same device, same trip, even same day):

So in short, when this behavior appears, neither the plugin built-in API POST nor the plugin logger nor the distanceFilter/disableElasticity settings are working, while Angular Http POST is working without problems inside onLocation event.
The same has already happened in 3 different devices.
Please find the respective logs here: https://www.dropbox.com/s/nefe6wstb8d8nlp/background-geolocation(13).log.gz?dl=0
Any ideas? Could you add up something on your side in order to debug this issue? And thanks in advance, as a developer myself, I know that this kind of issues are the worst ones.

I suggest you install the /example app in this repo and compare its results.
the /example app is configured to post data to my demo server at tracker.transistorsoft.com.

How that would help at all to solve this issue? There's something failing inside the plugin here, that's seems to be caused by my particular development, so please lets focus on that.
I have another theory that would explain this behavior, there's any scenario where the plugin takes the default configuration parameters instead of the ones provided inside the ready method? That would explain the built-in API POST, the logger and the distanceFilter/disableElasticity not working as expected (no api, logger off and default distance/elasticity).

How that would help at all to solve this issue? There's something failing inside the plugin here,

I don’t believe that’s the case until I see it reproduced in isolation of your app.  So please go ahead and install the /example app.

I am also facing the exact same scenarios whatever mentioned above with some IOS devices (IPhone 14)
@ikleiman did you find the solution of it?

See wiki "Debugging".  Learn to fetch and analyze the logs.  Also search api docs "Logger".

@christocracy I already read the debugging in wiki.
let me go through the logs generated by plugin and will get back to you.
One thing which i didn't find in the docs is that, if user gave all the location permissions in the ios expect the motion activity
then what happend, how we find in the plugin event that user didn't gave the motion activity permission.
like in provider change event we have this object:
"provider": {             "network": true,             "enabled": false,             "accuracyAuthorization": 1,             "gps": true,             "status": 3         }
    Which key indicates that user didn't gave the motion activity permission and denied it

Motion permission is not required for the plugin to operate.  Motion permission has nothing to with the "Location Provider" thus does not appear in the onProviderChange event.

background-geolocation.log (1).zip
@christocracy
here is the debugging log of my app,
At line 3567, there is a log entry for the HTTP Service with a count of 38. This seems to indicate that 38 location entries have been stored in the SQL database. However, you're puzzled as to why these entries were saved without corresponding HTTP API calls.
Line 3578 provides more insight with a response code of 0, accompanied by an error message stating that the host "api.server.com" could not be resolved because no address is associated with the hostname. Despite this error, you’ve noted that your API appears to be functioning correctly.
Lastly, line 3889 mentions that the HTTP service is busy, followed by an HTTP 200 response, which typically indicates success. Subsequently, only one record is deleted, yet the log suggests that all 38 records were transmitted sequentially.
Can you please help me to understand these debugging logs so I can find out why my tracking stopped in b/w and then started in the middle but old locations data came first and then the latest

@tanuj-g yes, not completely, but managed to reduce the delays to less than 1%. Not quite sure what specifically did the trick, but first I've restructured my app in order to be more like the /example app, in the following way:

Moved my BG plugin logic from app.component.ts to home.page.ts (my app logic is login => home => (other logged user pages), so home is the first logged user reachable page)
My API works with a JWT token that I was saving on a "this.token" variable inside home.page.ts, changed that to a function that always retrieves the token directly from the device storage

Then, in addition to the Http post feature of the plugin, I've implemented my own upload function inside onLocation event, then on the server I'm ordering the location points according the timestamp and skipping the duplicates using that information too. You must be aware that this approach is not the most efficient in battery matters, but was the only one that solved my delay scenarios.

HTTP Requests are synchronous, the next one executes only after the previous returns a response of 20x.
I encountered a situation where the plugin abruptly ceased transmitting location updates in the background until I opened the app manually. Referring to the log, at line 5123 with the timestamp 11-17 16:27:59.704, there's a message indicating that the BackgroundTaskService stopped. Subsequently, there are no further log entries, nor any background updates. Despite the user travelling around 5 miles, no updates were received during this period.
Later, at 11-17 17:14:36.000, when I manually activated the app, an update was immediately recorded, as evident in the subsequent log entry at line 5125.
I'm puzzled about what occurred post-16:27, especially since there are no corresponding log entries to shed light on the issue.
╔═════════════════════════════════════════════ ║ TSLocationManager version: 3.4.0 (420) ╠═════════════════════════════════════════════ ╟─ realme RMX2156 @ 12 (capacitor) {   "activityRecognitionInterval": 10000,   "allowIdenticalLocations": false,   "authorization": {},   "autoSync": true,   "autoSyncThreshold": 0,   "backgroundPermissionRationale": {     "title": "Allow Chaine to access to this device's location in the background?",     "message": "Chaine needs location permission when you are assigned load to provide updates. This app collects location data to enable sharing tracking updates with your customers even when the app is closed or not in use.",     "positiveAction": "Change to {backgroundPermissionOptionLabel}",     "negativeAction": "Cancel"   },   "batchSync": false,   "configUrl": "",   "debug": false,   "deferTime": 0,   "desiredAccuracy": -2,   "desiredOdometerAccuracy": 100,   "disableAutoSyncOnCellular": false,   "disableElasticity": false,   "disableLocationAuthorizationAlert": true,   "disableMotionActivityUpdates": false,   "disableProviderChangeRecord": false,   "disableStopDetection": false,   "distanceFilter": 200,   "elasticityMultiplier": 4,   "enableHeadless": false,   "enableTimestampMeta": false,   "extras": {     "androidSDKVersion": 31,     "appVersion": "3.0.10",     "batteryLevel": 0.699999988079071,     "connectionType": "wifi",     "deviceID": "5b484dd8eabde232",     "deviceManufacturer": "realme",     "deviceModel": "RMX2156",     "deviceName": "realme narzo 30",     "deviceOS": "android",     "deviceOSVersion": "12",     "devicePlatform": "android",     "driverPhone": "4052955384",     "iOSVersion": null,     "isDeviceCharging": false,     "isDeviceVirtual": false,     "isNetworkConnected": true,     "languageCode": "en",     "userID": "eb0713b8-010e-49ed-981e-c1698999b909"   },   "fastestLocationUpdateInterval": -1,   "foregroundService": true,   "geofenceInitialTriggerEntry": true,   "geofenceModeHighAccuracy": false,   "geofenceProximityRadius": 1000,   "geofenceTemplate": "",   "headers": {     "ContentType": "application\/json"   },   "headlessJobService": "com.chaineapp.driver.BackgroundGeolocationHeadlessTask",   "heartbeatInterval": -1,   "httpRootProperty": "location",   "httpTimeout": 60000,   "isMoving": true,   "locationAuthorizationRequest": "Always",   "locationTemplate": "",   "locationTimeout": 60,   "locationUpdateInterval": 1000,   "locationsOrderDirection": "ASC",   "logLevel": 5,   "logMaxDays": 3,   "maxBatchSize": -1,   "maxDaysToPersist": 1,   "maxRecordsToPersist": -1,   "method": "POST",   "minimumActivityRecognitionConfidence": 75,   "motionTriggerDelay": 0,   "notification": {     "layout": "",     "title": "",     "text": "Location Service activated",     "color": "",     "channelName": "TSLocationManager",     "channelId": "",     "smallIcon": "",     "largeIcon": "",     "priority": 0,     "sticky": false,     "strings": {},     "actions": []   },   "params": {},   "persist": true,   "persistMode": 2,   "schedule": [],   "scheduleUseAlarmManager": false,   "speedJumpFilter": 300,   "startOnBoot": true,   "stationaryRadius": 25,   "stopAfterElapsedMinutes": 0,   "stopOnStationary": false,   "stopOnTerminate": false,   "stopTimeout": 5,   "triggerActivities": "in_vehicle, on_bicycle, on_foot, running, walking",   "url": "https:\/\/api.chaineapp.com\/apps\/events\/v1\/mobile\/chaine\/locations",   "useSignificantChangesOnly": true,   "enabled": true,   "schedulerEnabled": false,   "trackingMode": 1,   "odometer": 0,   "isFirstBoot": false,   "didLaunchInBackground": false,   "didDeviceReboot": false }
The settings are being output in the log. Could you help me understand what might have happened, and explain the log's content that I might be missing or not fully comprehending at the moment?
log.gz

When you see this, your app process has been relaunched after being terminated.
11-17 17:14:36.001 INFO [LoggerFacade$a a]
╔═════════════════════════════════════════════
║ TSLocationManager version: 3.4.0 (420)
╠═════════════════════════════════════════════
╟─ realme RMX2156 @ 12 (capacitor)
{

When the device is detected to be moving, the OS will automatically relaunch your app process to resume tracking.
If your device is sitting stationary for long periods of time, the OS can and will terminate your app process to free up memory for the app currently running in the foreground.  If the device moves about 200 meters from last known location, tracking WILL resume, even if the OS terminated your app.

When you see this, your app process has been relaunched after being terminated.
11-17 17:14:36.001 INFO [LoggerFacade$a a]
╔═════════════════════════════════════════════
║ TSLocationManager version: 3.4.0 (420)
╠═════════════════════════════════════════════
╟─ realme RMX2156 @ 12 (capacitor)
{

When the device is detected to be moving, the OS will automatically relaunch your app process to resume tracking.
If your device is sitting stationary for long periods of time, the OS can and will terminate your app process to free up memory for the app currently running in the foreground. If the device moves about 200 meters from last known location, tracking WILL resume, even if the OS terminated your app.

@christocracy
The above should be expected behaviour but my app is not relaunched by itself I am moving for almost 6-7 miles still app is not restarted and plugin didn't send any location update.
at 11-17 17:14:36.001 - I opened the app manually to restart the tracking
is there any scenario where app will not restart itself if the user is moving

@tanuj-g post a new issue.


No device configuration for 1440px (@4x/xxxhdpi) Android devices

It would be really handy if we could get devices configurations added for 1 or more 1440px Android devices.
Facebook have released device images for Galaxy Note 5 and Nexus 6P (https://facebook.github.io/design/devices). These could possibly be used for the device images.

I'd be more than happy to submit a pull request for these changes.

There is a massive device + hand update coming up.


Add missing file name for tailwind.config.mjs

What does this PR fix?
Fix: #263
It adds the tailwind.config.mjs file name to the symbol-icon-theme.json file names list
Before:

Now:

@victorbadaro,
Adding the tailwind.config.mjs is great... But you formatted the symbol-icon-theme.json file maybe you should fix that.

@victorbadaro,
Adding the tailwind.config.mjs is great... But you formatted the symbol-icon-theme.json file maybe you should fix that.

Thank you, mate! I think the file wasn't formatted before, actually.
I really formatted it wrong the first time (ignoring the biome settings), but I've already fixed it.
Also, the file, as it is now, reflects the result of running npm run format.

@victorbadaro thanks for the PR, I think your formatter may have changed the format. Running npm run format on main does not produce the same as your PR. Do you mind undoing those? Thanks.

Done!
It might have been some bug in my vscode or something like that (maybe a default formatter).
Even after running npm run format, the file stayed the same.
Now, it's fixed!
Sorry about that, guys! 😅
@sebastiandotdev @miguelsolorio


Remove pagination on the list page in favour of filtering the table

Unfortunately the table filter JavaScript module doesn't support
filtering over multiple pages, which would defeat the object of
having it there. I've therefore made the decision to remove the
pagination on the "list accepted short URLs page" and add a
search-like box to make finding a previous short URL a lot easier.

(Roo agrees that this is a good idea. :sunny: Taken most of the code from Transition when we did a similar thing.)
Before:

After:

(Of course, the data differences are preview vs. my dev VM's latest replication.)

I like this very much. :smile:


Barbican KMS: use persistent client

What this PR does / why we need it:
It adds a persistent barbican client and avoid keystone auth on every Encryption/Decryption call.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #787
Special notes for your reviewer:
@adisky I'm probably missing some not obvious use cases, which led to the current logic. Feel free to correct me if I'm wrong.
Release note:

Barbican KMS: use persistent client

/test cloud-provider-openstack-format

/test cloud-provider-openstack-acceptance-test-csi-cinder

/test cloud-provider-openstack-acceptance-test-flexvolume-cinder

/test cloud-provider-openstack-acceptance-test-keystone-authentication-authorization

/test cloud-provider-openstack-acceptance-test-standalone-cinder

/ok-to-test

@kayrus I am ok with your changes, i don't remember why i have not used persistent client,
one more thing, have you tested these changes as barbican does not have a CI job??
If possible for you please set up a CI job for barbican KMS

@adisky it was tested by @sfxworks in #741

@adisky it was tested by @sfxworks in #741. Unfortunately I don't have enough resources to setup a CI for barbican.

currently i also do not have barbican setup, considering @sfxworks tested the PR, i am approving this, @sfxworks could you help us in setting up CI job for barbican KMS?

/lgtm
/approve

@adisky Sure! I've never made one for OpenLab before, but I'd be more than happy to get started on one!


Footer social media links (Twitter, LinkedIn) not opening in new tabs

Description:
The social media links in the footer, specifically for Twitter and LinkedIn, are currently opening in the same browser tab instead of a new tab. This behavior may disrupt user experience by navigating away from our site unexpectedly.
Steps to reproduce:

Navigate to any page with the site footer visible
Locate the social media icons in the footer
Click on either the Twitter (X) or LinkedIn icon

Current behavior:
The link opens in the same browser tab, replacing our website.
Expected behavior:
The link should open in a new browser tab, keeping our website open in the original tab.
NOTE: I would love to work on this issue and solve it. I shall raise a PR very soon.

I'm a new contributor to Zuplin. So far I've set up the repository and am ready to work on it.
Can I start with this small issue?

hey are you going to do it??

Hi @Harshinireddy05 , I noticed this issue and would like to contribute by working on it. Is anyone already working on this? If not, I'd be happy to start looking into it. Please let me know if there are any specific guidelines or things I should consider while addressing this issue.

@zulipbot claim

@zulipbot!
Is this issue still open, can I proceed on this?

This has been fixed, as can be verified by testing on zulip.com.


[Feature][Dependence] Reform dependence mode

Search before asking

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

Description
Present situation: The current dependency is on a single task and All. In fact, All depends on workflow, not all tasks
Planned reform:

The mode of relying on a single task remains unchanged. All is changed to rely on all tasks in the workflow, and a new type of workflow dependency is added.
The front end adds a radio box in the dependency area to select dependent tasks or workflows. If you select dependent tasks, the task selection box will be displayed. If you now rely on workflows, the task selection box will be hidden
For the backend, All is still 0 for the task code. When workflow is relied on, the corresponding task code can be represented by - 1 or other

当前状况：当前的依赖是依赖单个任务和All，这里的All其实是依赖工作流，并不是依赖所有的任务
计划改造：
1、依赖单个任务的方式不变，All改造成依赖工作流中所有任务，新增一种类型依赖工作流。
2、前端在依赖的地方增加个单选框，选择依赖任务或者工作流，如果选择依赖任务，任务的选择框显示出来，如果现在依赖工作流，任务的选择框隐藏
3、对于后端，All对于的任务code还是0，依赖工作流时，对应的任务code可使用-1或其他表示
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi, I will contribute this feature.
The dependency mode for dependent node in dev branches will be modified.

The logic of Dependent on ALL will be changed from checking the workflow state to checking the state of all task instances in the workflow.
A new Dependent on workflow is added that is responsible for checking the workflow state.
For compatibility with user history data, Constants.DEPENDENT_WORKFLOW_CODE will be assigned a value of 0, replacing the original Constants.DEPENDENT_ALL_TASK_CODE, and Constants.DEPENDENT_ALL_TASK_CODE will be assigned a value of -1.

I'll add a drop-down select box that controls the type of dependency to the front-end code to support this feature. The select box options include Dependent on workflow and Dependent on task. When Dependent on workflow is selected, it looks like the following image:

When Dependent on task is selected, as shown below:

closed by #14824


Dosen´t refresh the collection when i ban a user

Hi everyone! Excelent work with the package!!!
I have found in one of my tests that the variable that contained the user model instance was not updated after applying the ban() function to it.
Example:
$user = User::find($id);
$user->ban();
if i look into the $user dosen´t have updated the field banned_at.
I think this should not be the case and should be updated.
Hope this helps!
Thanks!!!

How can we reproduce this issue? How are you checking that model was not updated?

I was able to reproduce this issue, with PHP 8.0 and Laravel 9, I'm not sure if this is a cache configuration, I did it through tinker @antonkomarev

It will be great to reproduce bug in integration tests, it will help a lot

@antonkomarev Sure, I'll try to add a test


Working on react native?

Is there a version for react native?

sorry this library is mostly built for desktop usage. this may be possible at some point if the underlying library (vx) were to support it. See the relevant discussion in vx.


⚠ Fortnite has degraded performance

In 8ccbd09, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1521 ms

Resolved: Fortnite performance has improved in d546bd4.


Adds truncate_prompt_tokens param for embeddings creation

This adds the truncate_prompt_tokens to the embeddings' creation request - truncation is already implemented at the tokenizer, so it only propagates the parameter so that API users can send a value to it.

Default value is None;
If truncate_prompt_tokens is greater than max_model_len an error is returned;
If truncate_prompt_tokens is smaller than max_model_len, then the value is passed to the tokenizer;
In case of any other value, then truncate_prompt_tokens is set to max_model_len.

Please provide feedback on this!
cc: @njhill

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.

Make sure custom ops are registered following PyTorch guidelines: Custom C++ and CUDA Operators and The Custom Operators Manual
Custom operations that return Tensors require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.
Use torch.libary.opcheck() to test the function registration and meta-function for any registered ops.  See tests/kernels for examples.
When changing the C++ signature of an existing op, the schema must be updated to reflect the changes.
If a new custom type is needed, see the following document: Custom Class Support in PT2.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

Please merge from our main branch to resolve some of the CI errors. Afterwards we can really check whether your PR works or not.


Limit

Is there no way i can change the limit of how many i can catch?

There are ways to do that but you have to develop it by yourself since I made this bot to prevent the limit for catches like in other bots.

Would that be something u can help with?
I keep hitting the 180 limit over the hour period

Wdym by 180 limit ? Can you explain more about it as I am not an active poketwo player since long time

This is what i keep getting, im being limited by something
[Symbol(kOutHeaders )]: [Object: null proto
type]
_ ,
[ Symbol (kUniqueHeaders)]: null
},
data: 'You may only perform this action upto maximum 180 number of times within 3600 seconds
}
TypeError: Cannot read properties of undefined ( reading 'ParsedResults')
at main (/home/runner/Poketwo-Autocatcher/in dex.js:119:34)
[antiCrash] :: Unhandled Rejection/Catch
DiscordAPIError: Cannot send an empty message
at RequestHandler.execute /home/runner/Poke two-Autocatcher/node_modules/discord.js-self/src
/rest/RequestHandler.js:170:25) {
method:
'post'
path:
"/channels/1064509511232127006/messages'


Create OSM Network Dataset

Hi,
I have tried createing OSM network dataset in both ArcMap 10.1 and 10.3 and they fail.
I'm getting this error:
--- snap ---
Assigning Network Connectivity Groups
Extracting Turn Restrictions
Exception from HRESULT: 0x80040353
at ESRI.ArcGIS.Geodatabase.IDatasetContainer2.CreateDataset(IDEDataset DataElement)
at ESRI.ArcGIS.OSM.GeoProcessing.NetworkDataset.CreateTempNDS()
at ESRI.ArcGIS.OSM.GeoProcessing.NetworkDataset.ExtractTurnRestrictions()
at ESRI.ArcGIS.OSM.GeoProcessing.RunTaskManager.ExecuteTask(String messageName, Action task)
at ESRI.ArcGIS.OSM.GeoProcessing.NetworkDataset.CreateNetworkDataset()
at ESRI.ArcGIS.OSM.GeoProcessing.OSMGPCreateNetworkDataset.Execute(IArray paramvalues, ITrackCancel TrackCancel, IGPEnvironmentManager envMgr, IGPMessages message)
Failed to execute (OSMGPCreateNetworkDataset).
Failed at Mon Aug 24 12:58:49 2015 (Elapsed Time: 11 minutes 14 seconds)
How to solve this?

Hello - one question: do you have the "Enable" box checked for Background Geoprocessing in the Geoprocessing options? It will be required for the tool to execute.
More on enabling/disabling background geoprocessing options here (doc for 10.2 works the same in other versions): http://resources.arcgis.com/en/help/main/10.2/index.html#//00210000003q000000

I have disabled the background processing. Else i can't run load osm from file.
I have tested on another machine 32 bit and it all worked. The machine having issues is running 64 bit but i think arcgis is 32 bit on the machine. Maybe This is causing problems?

The machine having issues is running 64 bit but i think arcgis is 32 bit on the machine. Maybe This is causing problems?

That shouldn't cause problems, 32 bit software can run without issues on 64 bit windows, and that includes ArcGIS. 32 bit software just can't take advantage of 64 bit address space and large RAM effectively.
Also see here:
http://windows.microsoft.com/en-us/windows/32-bit-and-64-bit-windows#1TC=windows-7
If the Create OSM Network Dataset tool requires large amounts of RAM to do its job properly, then that might be part of the answer to the question why its better to run it as 64 bit background geoprocessing process.

I am guessing that the 64bit geoprocessing option is installed on your machine. With this option installed and the GP environment set to Background you need to install the 64bit version of the OSM tools.
That is the second installer under 'ArcGISEditor10_3_x64'. This set of tools which contains the same functionality as the first installer is specifically needed to run in the 64bit context of desktop background and ArcGIS Server.
On more general terms, all 32bit software runs just fine on 64bit operating systems. This will not be an issue. However please do run the Create Network in the foreground if you are using a file geodatabase. We are aware of a locking issue if certain tools are running in succession. Creating large networks (even on 32bit) will not be an issue either, it might just mean that the tool's internal dynamic resource allocation kicks in a little sooner but all that are implementation details. Bottom line, running 32bit application on 64bit OSes just works.

I also get this problem...
Dose the configuration file cause it ?

Please run this tool as a foreground geoprocessing tool. Here is some documentation on the difference and how to switch http://desktop.arcgis.com/en/arcmap/latest/analyze/executing-tools/foreground-and-background-processing.htm

I am also getting this error, it is running in the foreground and I get the same exact failure initially reported.
Running 10.2.1.

Unfortunately the error message isn't revealing any reason for the error. By sure to follow the steps outlined in the wiki https://github.com/Esri/arcgis-osm-editor/wiki/Create-a-network-dataset-from-osm-data

I also had this problem. I was running with a new blank map. I changed the coordinate system to WGS84 and tried again and it worked for me.

After much trial and error with various things, I was able to make this work by first creating a simple network dataset, I then created a new configuration *.xml using the XMLFromNDS.py script, then using this in the Create OSM Network Dataset tool. I hope this helps someone!

@Chaz6 is it possible I can get a copy of your config file? this error is driving me insane, or are they very easy to do yourself?

I am also getting this error, it is running in the foreground and I get the same exact failure initially reported.
Running 10.2.1.
This is my error:
Start Time: Thu Feb 23 15:04:43 2017
Succeeded at Thu Feb 23 15:04:48 2017 (Elapsed Time: 5.00 seconds)
Assigning Network Connectivity Groups
Extracting Turn Restrictions
Exception from HRESULT: 0x80040353
at ESRI.ArcGIS.Geodatabase.IDatasetContainer2.CreateDataset(IDEDataset DataElement)
at ESRI.ArcGIS.OSM.GeoProcessing.NetworkDataset.CreateTempNDS()
at ESRI.ArcGIS.OSM.GeoProcessing.NetworkDataset.ExtractTurnRestrictions()
at ESRI.ArcGIS.OSM.GeoProcessing.RunTaskManager.ExecuteTask(String messageName, Action task)
at ESRI.ArcGIS.OSM.GeoProcessing.NetworkDataset.CreateNetworkDataset()
at ESRI.ArcGIS.OSM.GeoProcessing.OSMGPCreateNetworkDataset.Execute(IArray paramvalues, ITrackCancel TrackCancel, IGPEnvironmentManager envMgr, IGPMessages message)
Failed to execute (OSMGPCreateNetworkDataset).
Failed at Thu Feb 23 15:04:49 2017 (Elapsed Time: 9.45 seconds)
Any help solving this would be appreciated.

@DiegoSalcedo did you ever solve this problem?


LUCENE-10093: first cut at fixing conflicting test assert and improving TMP javadocs

Description
First cut trying to resolve a consistent random corner-case failure in TestTieredMergePolicy.testForcedMergesUseLeastNumberOfMerges.  This is not yet ready for commit!  There are at least two nocommits still.
Solution
I relaxed the test assertion so it matches the actual logic in TieredMergePolicy.
Tests
No new added tests.  Just getting the existing (sometimes failing) test to pass.
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Lucene maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[ ] I have run ./gradlew check.
[ ] I have added tests for my changes.

Yeah, sorry about it. We could add an exclusion to rat-checks but these proliferate over time... When you're switching branches, git will leave temporary files behind, it sometimes creates mess like this.

gradlew clean only cleans active modules. packaging has been renamed and no longer exists. Wipe all old cruft with:
git clean -xfd lucene

Aha! Thermonuclear clean, I like it. I'll try that. Thanks @dweiss.

That worked.  Thanks @dweiss.  I'll try to remember to try this next time.
I'll push shortly.


pod install fail？

CocoaPods could not find compatible versions for pod "TrezorCrypto":
In snapshot (Podfile.lock):
TrezorCrypto (= 0.0.5)
In Podfile:
TrustCore (~> 0.0.6) was resolved to 0.0.6, which depends on
TrezorCrypto
None of your spec sources contain a spec satisfying the dependencies: TrezorCrypto (= 0.0.5), TrezorCrypto.
You have either:

mistyped the name or version.
not added the source repo that hosts the Podspec to your Podfile.

Note: as of CocoaPods 1.0, pod repo update does not happen on pod install by default.

Do you develop this wallet?

Solved it!
In your navigate to Libs/react-native-golden-keystore and open the file 'react-native-golden-keystore.podspec' in a text editor.
Change  s.dependency 'TrezorCrypto', '0.0.6' to  s.dependency 'TrezorCrypto', '0.0.9' (that should be in or around line 21.

Hello, can we still use this wallet? Tronscan update but this wallet still too old to use

这个项目还是运行不起来。

💸💵💴


WHat am i doing wrong

Challenge Size your Images has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.

Let me know if this fixes it.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to
screenshots if possible.

Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/13359, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AYlbotZ3R6lm9Lrwij_0vUzy-W6B46jfks5rcoAWgaJpZM4MBSrB
.

Hi @HarryPeck
Thanks for the report. The issue tracker is for reporting bugs only.
Please use the chat rooms:

HTML/CSS help chat room
JavaScript help chat room
Other Official Rooms

or try looking through our forum for help with a specific challenge.
Happy Coding!

check de class name
it does not match
ie. small-image and smaller-image
On Feb 15, 2017 4:32 AM, "HarryPeck"<EMAIL_ADDRESS>wrote:

Challenge Size your Images has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to
screenshots if possible.

Purr jump eat the grass rip the couch scratched

sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip
scratched.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Mocking static methods?

I tried using
Functions\when('My_Plugin\Helpers\General_Helper::get_array_value')->justReturn('value');

For mocking static method in my unit test, but I get an error

Brain\Monkey\Name\Exception\InvalidName: ''My_Plugin\Helpers\General_Helper::get_array_value'' is not a valid function name.

Is there a way to mock static methods with Brain Monkey?

Ok I found out how I can do that. Not an elegant solution, but it works. I need to alias the helper class and then mock the static methods that will be used instead of the real ones.
http://docs.mockery.io/en/latest/reference/creating_test_doubles.html#creating-test-doubles-aliasing


Teachable Machine Audio Model - .wav, .mp3 as input?

Dear,
First of all, I appreciate this project - amazing that someone can transform complex calculations into a simple tool like this. Good work.
Is there a way how to import own sounds like .wav, or .mp3 format?
Thank you,
Martin.

I'm trying to do this also.. Have you got a solution?

Not yet, unfortunately.

Hi, thanks for this feature request. It's high on our list of things we want to get into the tool.

that would be awesome and very powerful if you managed that!

Hello, as this comment is from Feb so are there news is this feature is planned and if yes   when can be expected.
Thanks,

amazing ! that would be fantastic.

Thanks for your feature request idea. We're going to close this issue for now as we're not actively working on it just yet, but rest assured we've made a note of it.


Text overflow issue in "Simple" view in Admin Panel

It is clear that the members with 2 lines description (Lizette_Brown and Jaytee) are the only ones with a problem the “Simple” tab.

Additional note:

I also noted that they were the only persons who have updated their statuses.