[SUPPORT] Caused by: java.lang.IllegalArgumentException: ALREADY_ACQUIRED

Describe the problem you faced
A clear and concise description of the problem.
To Reproduce
1.flink sql create table
CREATE TABLE if not exists test_hudi_flink_mor_occ (
  uuid VARCHAR(200) PRIMARY KEY NOT ENFORCED,
  name VARCHAR(100),
  age INT,
  ts TIMESTAMP(0),
  `partition` VARCHAR(20)
)
PARTITIONED BY (`partition`
)
WITH (
  'connector' = 'hudi',
  'path' = '/project/ccr_ai_upgrade/ccr_ai_upgrade/aiui/flink/demo/test_hudi_flink_mor_occ',
  'table.type' = 'MERGE_ON_READ',
  'hoodie.datasource.write.keygenerator.class' = 'org.apache.hudi.keygen.ComplexAvroKeyGenerator',
  'hoodie.datasource.write.recordkey.field' = 'uuid',
  'write.precombine.field' = 'ts',
  'hoodie.datasource.write.hive_style_partitioning' = 'true',
  'hoodie.write.concurrency.mode' = 'optimistic_concurrency_control',
  'hoodie.cleaner.policy.failed.writes' = 'LAZY',
  'hoodie.write.lock.provider' = 'org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider',
  'hoodie.write.lock.hivemetastore.database' = 'hive',
  'hoodie.write.lock.hivemetastore.table' = 'test_hudi_flink_mor_occ_lock'
)

2.flink sql insert into
insert into test_hudi_flink_mor_occ values ('a','liangji',18,TIMESTAMP '2022-11-20 18:00:00','2022-11-20')

Environment Description

Hudi version :0.12.1

Flink version :1.14.0

Hadoop version :2.6.0

Stacktrace
org.apache.flink.util.FlinkException: Global failure triggered by OperatorCoordinator for 'stream_write: test_hudi_flink_mor_occ' (operator 905882b372467a732faa32d0b002df8d).
	at org.apache.flink.runtime.operators.coordination.OperatorCoordinatorHolder$LazyInitializedCoordinatorContext.failJob(OperatorCoordinatorHolder.java:545)
	at org.apache.hudi.sink.StreamWriteOperatorCoordinator.lambda$start$0(StreamWriteOperatorCoordinator.java:187)
	at org.apache.hudi.sink.utils.NonThrownExecutor.handleException(NonThrownExecutor.java:146)
	at org.apache.hudi.sink.utils.NonThrownExecutor.lambda$wrapAction$0(NonThrownExecutor.java:133)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
	at java.util.concurrent.FutureTask.run(FutureTask.java)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.hudi.exception.HoodieException: Executor executes action [handle end input event for instant<PHONE_NUMBER>1431329] error
	... 9 more
Caused by: java.lang.IllegalArgumentException: ALREADY_ACQUIRED
	at org.apache.hudi.common.util.ValidationUtils.checkArgument(ValidationUtils.java:40)
	at org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider.acquireLock(HiveMetastoreBasedLockProvider.java:137)
	at org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider.tryLock(HiveMetastoreBasedLockProvider.java:113)
	at org.apache.hudi.client.transaction.lock.LockManager.lock(LockManager.java:73)
	at org.apache.hudi.client.HoodieFlinkWriteClient.writeTableMetadata(HoodieFlinkWriteClient.java:280)
	at org.apache.hudi.client.BaseHoodieWriteClient.commit(BaseHoodieWriteClient.java:270)
	at org.apache.hudi.client.BaseHoodieWriteClient.commitStats(BaseHoodieWriteClient.java:235)
	at org.apache.hudi.client.HoodieFlinkWriteClient.commit(HoodieFlinkWriteClient.java:125)
	at org.apache.hudi.sink.StreamWriteOperatorCoordinator.doCommit(StreamWriteOperatorCoordinator.java:530)
	at org.apache.hudi.sink.StreamWriteOperatorCoordinator.commitInstant(StreamWriteOperatorCoordinator.java:506)
	at org.apache.hudi.sink.StreamWriteOperatorCoordinator.commitInstant(StreamWriteOperatorCoordinator.java:477)
	at org.apache.hudi.sink.StreamWriteOperatorCoordinator.handleEndInputEvent(StreamWriteOperatorCoordinator.java:420)
	at org.apache.hudi.sink.StreamWriteOperatorCoordinator.lambda$handleEventFromOperator$3(StreamWriteOperatorCoordinator.java:278)
	at org.apache.hudi.sink.utils.NonThrownExecutor.lambda$wrapAction$0(NonThrownExecutor.java:130)

My hudi version is 0.12.1, https://github.com/apache/hudi/pull/6272 is already merged. So it can not resolve my problem.

if flink support occ, I think it is a bug @danny0405 . And the lock hudi support  I think is not a reentrant lock

Yeah, seems a bug, we need some flag to indicate whether the lock is required.

Yeah, seems a bug, seems all the invocations of #writeTableMetadata are already guarded by the txn lock. We can remove the lock in #writeTableMetadata i think, please fire a JIRA and fix it if you are interested.

ok, I'll try

@danny0405 Please take a look at this pr #7320. If there is a problem, I will update.


Error(Apple Pay / Web): IntegrationError: show() must be called from a user gesture handler

Platform

[ ] Web

Describe the bug
Error: Uncaught (in promise): IntegrationError: show() must be called from a user gesture handler (such as a click handler,
To Reproduce
Steps to reproduce the behavior:

Go to open your demo on the safari browser
Click on apple create and then present
check the browser console
See error
Error: Uncaught (in promise): IntegrationError: show() must be called from a user gesture handler (such as a click handler,

Screenshots

Additional context
Add any other context about the problem here.

move https://github.com/wpkyoto/stripe-pwa-elements/issues/42


Version 0.4.0 not loading models from S3

Dear TF team,
we are experiencing a weird issue with the latest version of TensorFlow for Java - after upgrade it stopped loading models from S3.
Here's an example setup:
Java 8, a single dependency:
    <dependency>
      <groupId>org.tensorflow</groupId>
      <artifactId>tensorflow-core-platform</artifactId>
      <version>0.4.0</version>
    </dependency>

A single class:
import org.tensorflow.SavedModelBundle;

public class App {

  public static void main(String[] args) {
    SavedModelBundle.load("s3://some/location", "serve");
  }
}

Environment variable: AWS_REGION=eu-central-1
Outcome:
2022-03-09 20:53:24.893857: I external/org_tensorflow/tensorflow/cc/saved_model/reader.cc:43] Reading SavedModel from: s3://some/location
2022-03-09 20:53:24.893896: I external/org_tensorflow/tensorflow/cc/saved_model/loader.cc:283] SavedModel load for tags { serve }; Status: fail: NOT_FOUND: Could not find SavedModel .pb or .pbtxt at supplied export directory path: s3://some/location. Took 49 microseconds.
Exception in thread "main" org.tensorflow.exceptions.TensorFlowException: Could not find SavedModel .pb or .pbtxt at supplied export directory path: s3://some/location
	at org.tensorflow.internal.c_api.AbstractTF_Status.throwExceptionIfNotOK(AbstractTF_Status.java:101)
	at org.tensorflow.SavedModelBundle.load(SavedModelBundle.java:623)
	at org.tensorflow.SavedModelBundle.access$000(SavedModelBundle.java:67)
	at org.tensorflow.SavedModelBundle$Loader.load(SavedModelBundle.java:97)
	at org.tensorflow.SavedModelBundle.load(SavedModelBundle.java:357)
	at App.main(App.java:6)

Either of the changes below "fixes" the issue:

changing from S3 to local
changing from 0.4.0 to 0.3.3

Question: has anything changed since the previous version? Are we missing some important point that would make integration with S3 possible?
Thank you!

s3 support was removed from TF 2.6 (https://github.com/tensorflow/tensorflow/issues/51583) and split out into a separate TF IO package (https://github.com/tensorflow/io). If you download the appropriate version of TF IO, extract the so/dylib files from it, you should be able to register the filesystem plugin with org.tensorflow.internal.c_api.global.tensorflow.TF_RegisterFilesystemPlugin(String plugin_filename, TF_Status status). We don't provide a wrapper around that method like we do for library loading, because we hadn't noticed that upstream TF had split out the filesystem support into a separate package. We'll put it on the todo list.

Understood, thanks for the clarification, @Craigacp !

Hi @Craigacp and @dennisTS, I have the same problem. Could you mind to share the solution? Since I have downloaded the newest version of TF IO and installed it correctly, but I still found that issue?

You need to supply the path to libtensorflow_io_plugins.so which will have been installed into your python environment as an argument to the TF_RegisterFilesystemPlugin method that I mentioned above.

In v0.4.2 we added a method which makes it easier to load the native filesystem libraries. You'll still need to download the python wheel and extract it, but at least it's easier to load on the Java side now.


Retrofit2 403 Rate limit exceeded

When scrolling very fast, HTTP 403 Rate limit exceeded is thrown

It´s normal because GitHub api has a limit of Requests.. If you application is correct, like the example, you should have this problem when scroll fast at least 3 times...
The workaround for it (at least that´s what Github says on api), is: authentication.
https://developer.github.com/v3/rate_limit/

It's Github's limit, as @jsouza678 pointed out.


Id property description

The Id property is currently described as "for the timed metadata track"; should this not be "of the cue"?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 955367d8-ceaa-d9f1-960b-27b77a7f1d0f
Version Independent ID: 507e73f5-e6b1-2e23-d966-635dafb7c917
Content: DataCue.Id Property (Windows.Media.Core) - UWP app developer
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.media.core.datacue.yml&version=GBlive&_a=contents
Product: windows
Git Login: wdg-dev-content
Microsoft Alias: wdg-dev-content

This typo has been corrected. Thank you for bringing this issue to our attention.


Alert Boxes (Book Mobile)

See Req. 4.2 and See Req. 7.2

These do not show exactly what a user has to do to resolve the problem.
That doesn't make sense to implement, IMO 🤔
Should we rewrite the requirements?

I normally write check values or something but, we can rewrite it for the book mobile as you do have alert boxes telling an error has occured - which is fine with me.


leaderboard - clear leaderboard

Button inserted with functionality to clear leaderboard(via a local storage clear) and refresh page.


remove sdss

remove non-functional SDSS section

fyi the removed closes #188 from the OP would have closed the issue :)


Proto changes for port randomization

closing in favor of https://github.com/refraction-networking/gotapdance/pull/110. This was an informative draft.


Changing 'form' prop on mounted form does not initialise correctly

Today, I ran into an issue. I am not sure if this is intentional, but it sure bit me hard.
I have a form that will get its form property at runtime, based on the id of the entity the the form is supposed to edit. I am using react-router (who doesn't?) and in my case, the user can switch between the edited entity easily, causing the form not to be mounted again, but rather have its props changed (form and initialValues).
In that case, there is no new form created in the redux store and the displayed form is just broken. (Does not allow inputs as the reducer cannot put the edits into the store because a form with the given name does not exist and the initial values are also not set at all.)
I tried passing enableReinitialize at "design time" to enable proper behaviour, but to no avail. When I pass the form prop also at "design time" (so it is the same for all instances of that form) it works perfectly.
My assumption is that there is no support for changing the form prop after the form has been mounted. Is that intentional? What is the proper way to deal with this issue as I have the case where multiple instances of the same form are mounted on one page, but for different entities, which is not supported when I have a fixed form property for all instances.
Tested with version 6.2.0 and 6.2.1

I encountered the same issue as well, as I have a registration form for multiple participants in which you can jump between each participant with ease.
With redux 5 it was a non-issue as changing the formKey prop updated the form as expected. but with redux 6, this doesn't work anymore.
Looking at the code, it seems that the initial form prop is bound to the action creators, instead of using the context prop (which is always updated).
For now I have resorted to keeping multiple instances of the form on the page, but only showing the currently active one and hiding the others. Obviously this is not ideal however.

Sorry, I only half read your problem, but try adding key (not formKey) with the entity ID as a prop as well. This should cause React to re-render the component correctly.
Usually, you get a warning from React if you don't use this in a loop or map function, but you can add it only a single component and get the same result.

Closing this due to non response/age. If this is still an issue please request a re-open with reproduction steps / reproduction sandbox.


6362 dispute progress

Clubhouse Story
to Test:
after designate-report on market start disputing with dispute-contribute. When a dispute happens the progress bar should increase and the needed REP to fill bond value decreases in the dispute form.
From the reporting-dispute-market page there should be a dispute button on markets that have been initially reported on.
Submitter checklist

[x] Test covering functionality added/fixed in
Check the linked story includes the following:

[x] Steps to reproduce
[ ] Screenshot (If applicable)

Reviewer Checklist

[ ] Test/lint pass
[ ] Post merge, story marked complete

I noticed this, we need to get on the same page. I talked it over with Scott.
The DisputeRound data coming from AN indicates the round that has been completed. Therefore in the reporting dispute markets page is shows the round finished/completed. I increment the value indicating the current active round.
I'll make the change, best we look consistent, really it doesn't matter.


Fix IPv4 broadcast handling

A regression here meant broadcast IPv4 packets were ignored. Restore
handling those packets and also reply to broadcast ICMPv4 echo requests.
Closes #287.

@m-labs-homu r+

:pushpin: Commit ad65e2a has been approved by whitequark

:hourglass: Testing commit ad65e2a463dae4fc5fdd8924dda74f8adfdf977b with merge 0a21cb609da34b52fafe24e7b78d357b7ce1f6b7...

:broken_heart: Test failed - status-travis

@m-labs-homu retry

@m-labs-homu r+

:pushpin: Commit ed93a77 has been approved by whitequark

:hourglass: Testing commit ed93a77a460bb1f68f0aad0b4f28a7d0766384df with merge 5334b93158c954b61f5daf0d6d5d9d0c91588a26...

:sunny: Test successful - status-travis
Approved by: whitequark
Pushing 5334b93158c954b61f5daf0d6d5d9d0c91588a26 to master...


robots.txt 404 error

I can access robots.txt in local environment but gives 404 error in server (vercel)
"devDependencies": {
-------------------
"@nuxtjs/robots": "^2.5.0",
"nuxt": "^2.15.8",
}

Same issue for me.
Works when running npm run dev  and npm run build | npm run start locally, but neither work on the server. Also tested in development/production mode and, again, both work locally.
Server is nginx
 "@nuxtjs/robots": "^2.5.0", "nuxt": "2.15.8",

Just to clarify, you are not using bridge?

If he was using nuxt bridge, he would be using nuxt-edge and not nuxt library. He is using nuxt 2 without the bridge.


first prototype of a CS3 permissions service

This PR is part of the introduction of the permissions API to the CS3 APIs.
It implements the new permissions API.

:boom: Acceptance test localApiTests-apiSpaces-ocis failed. Further test are cancelled...

temporary hack for deleting a user
When deleting a user using the OCS api we want to delete the users home
space. Now to completely delete a space you need to send two requests.
First to 'disable' a space and a second one to really purge it.
This commit introduces this second purge request.
Furthermore the OCS api now also deletes all spaces owned by the user
not only the home space. This is needed since some tests create project
spaces and then lookup the space by name. When doing multiple runs
the tests will find several spaces with the same name and will sometimes
choose the wrong one which leads to test failures.
The whole test tear down should be changed to correctly clean up the
test setup.


[AJ-1652] Handle primary keys specified in request body

PUT and PATCH requests to /{instanceId}/records/{version}/{recordType}/{recordId} specify the record's primary key value in the URL via the recordId path parameter and, for PUT requests, the primaryKey query parameter. However, they may also specify the primary key value in the attributes in the request body.
Currently, WDS doesn't handle this consistently.

Creating a new record, whether or not the two primary key values match, the request succeeds.
Updating an existing record, whether or not the two primary key values match, results in an SQL error.

This updates that endpoint to require that, if a primary key value is specified in the request body, it must match the one in the URL. It they do match, the request now succeeds instead of producing an SQL error.

since you are looking at the primary key code, if you have a moment to check, Rob was able to upload a record without specifying the name of the primary key when using batch_insert from the python client (the primary key in that api is not required as a param) and the key ended up being called "sys_name" which is not a name that is allowed. (https://github.com/rtitle/terra-chess/blob/main/src/Prepare Data Table.ipynb?short_path=edd9f34#L306) not sure if this is exactly related but maybe?

That sounds like expected behavior? sys_name is the default name for the primary key column if none is specified.
https://github.com/DataBiosphere/terra-workspace-data-service/blob/0305a4094ea10a78920c0586d3198b6b5a5faf24/service/src/main/java/org/databiosphere/workspacedataservice/service/RecordService.java#L388

That sounds like expected behavior? sys_name is the default name for the primary key column if none is specified.
https://github.com/DataBiosphere/terra-workspace-data-service/blob/0305a4094ea10a78920c0586d3198b6b5a5faf24/service/src/main/java/org/databiosphere/workspacedataservice/service/RecordService.java#L388

ah okay, interesting! but when I download a file with sys_name and then try to reupload it via UI, it wont let me. So maybe then this is a terra-ui and wds behaviors not quite matching then?

Could be something related to TSV vs JSON APIs as well? Or new vs existing record type?
Your comments did prompt me to add a test case for including a sys_name field in the request to create a new record (https://github.com/DataBiosphere/terra-workspace-data-service/pull/555/commits/7dd008912ec40c87b421e16e96f90062b636dd16)


Fix: misc fixes on the repo

Fixes applied:

typo in media directory name
removing the use of a non-inclusive language ("guys")

thanks for help


Docker image missing on dockerhub

The docker images seems missing on dockerhub? Can you please push it there?

That's our bad. You can grab images from Docker Hub: https://hub.docker.com/r/moov/iso20022/tags


New HomeKit types?

Hi,
will you add new HomeKit types https://developer.apple.com/reference/homekit/1627282-homekit_constants?
Thanks.

Hi,
I'll be back tomorrow and let's see what I can do over the weekend.

@cflurin awesome! I'm looking forward ;)

@ArnieX I've just upload v0.2.0 to github.
This version supports the types as defined in:
https://github.com/KhaosT/HAP-NodeJS/blob/master/lib/gen/HomeKitTypes.js
Please install from github:
sudo npm install -g --unsafe-perm https://github.com/cflurin/homebridge-mqtt

@cflurin Great some of those that didn't work are working now.
But I have some issues with certain characteristics, for example battery status for sensors:
Service.TemperatureSensor = function(displayName, subtype) {
Service.call(this, displayName, '0000008A-0000-1000-8000-0026BB765291', subtype);

  // Required Characteristics
  this.addCharacteristic(Characteristic.CurrentTemperature);

  // Optional Characteristics
  this.addOptionalCharacteristic(Characteristic.StatusActive);
  this.addOptionalCharacteristic(Characteristic.StatusFault);
  this.addOptionalCharacteristic(Characteristic.StatusLowBattery);
  this.addOptionalCharacteristic(Characteristic.StatusTampered);
  this.addOptionalCharacteristic(Characteristic.Name);
};

Which I try to set like this:
{"name": "Outdoor Temperature","characteristic": "StatusLowBattery","value": 1}

But it return error:
{"ack":false,"message":"name 'Outdoor Temperature' characteristic do not match."}

How did you add the accessory? did you define the optional characteristic?
topic: homebridge/to/add
payload:
  {
    "name": "Outdoor Temperature",
    "service": "TemperatureSensor",
    "StatusLowBattery": "default"
  }

No. I didn't know this has to be defined when created ;). I'll do that and come back to you.

@cflurin Yes it works this way. Thank you for clarification.


Story 001 yarong

merge Yarong to mine

PR is added to the queue for testing as 2. task. (aaa8872)

PR is added to the queue for testing as 3. task. (aaa8872)

Test (Success) 48843357 build is completed (aaa8872)
See https://github.com/ThaliTester/TestResults/tree/48843357aaa8872_Story_001_yarong_DrJukka/ for the logs

Test (Success) 48843357 build is completed (aaa8872)
See https://github.com/ThaliTester/TestResults/tree/48843357aaa8872_Story_001_yarong_DrJukka/ for the logs

Test 48843357aaa8872(aaa8872) has failed
See https://github.com/ThaliTester/TestResults/tree/48843357aaa8872_Story_001_yarong_DrJukka/ for the fail logs


Motor coupling missing?

I printed all of the .stl parts from the V2 folder, but the wave generator is not the same as the one in your video, its obviously a newer version. There appears to be a coupling of some sort that goes between the wave generator and the motor. I've looked to see if I have missed a file, but I can't find it. Is that hiding somewhere?
Thanks for all of your work,
Eufrades

I think its meant to take a 20T GT2 timing belt pulley with the top flange popped off (based on a comment to the video here: https://www.youtube.com/watch?v=Emvo3bLT-Z4&t=16s).  I've got a stepper out of an old epson printer with a pulley that seems to match the wave generator... except I'm not sure because not sure how to pop the top flange off (blowtorch maybe?)
Since you are active, I have a question for you... have you figured out how the top housing is secured?  Seems to me like it would just fall off

Thats a good thought about the large bearing.  I bought one so in a few days I'll be able to tell.  That probably won't work for me either.  I was thinking of using it for a SCARA robot, so there will be force parallel to the motor shaft.  Maybe a stationary lid with a thrust bearing between will work for me, or something through the axle... What is your application?
Anyway the gear i had didnt actually fit, off by 2mm, so i made a bigger hole.  I also had elephant feet on my flex spline, so i fixed that by raising the teeth a tiny bit off the bed and printing with no supports.  I also put the skirt on the inside only.  I can give you the bkender models if you want.

What about the 688 bearings?  I think that they were originally on the motor shaft, but are not needed in the V2 design.

I think you're right on the bearings, it doesn't look like they're needed anymore. As long ans the motor is mounted solidly to the bottom housing.
My application isn't typical for this type of gearbox, I just needed something with a really big speed reduction in a small package. I'm planning to use it on a sand spreader on the back of my atv. There is a motor there that already spins the spreader, but I wanted to use the same motor to really slowly turn an agitator in the sand hopper because the sand keeps getting hung up in there.
I appreciate the offer of your files, but I think I'm going to modify this quite a bit more to slow it down even more for me.


[Bug] A lot of input lag

Checklist

[X] I will only use English in my report.
[X] I have used the search function for open and closed issues to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

Questions

[X] xCloud officially supports my country/region.
[X] The bug doesn't happen when I disable Better xCloud script.
[X] The bug didn't happen in previous Better xCloud version (name which one).

Device
Laptop
Device
Samsung Essentials E30
Operating System
win 10
Android app/Browser Version
newest
Better xCloud Version
newest
Game list
Ark survival ascended
Reproduction Steps
When I turn on better Xcloud, the transmission has a lot of input lag, transmission quality doesn't change, no image loss or aliasing, but the delay for the commands makes it unplayable, can you solve that, or do you know if this is some problem with Better xcloud?
Screenshot/video
No response

not enough info
what is your settings?


Cannot find apiKey

I cannot find my app apiKey to use this lib.
Please someone tell me how to get it on shopify :(

You can log in to https://partners.shopify.com. Select apps on the left side and click the app you want to use to see its settings and credentials.


Speed up CMIP6 processing

As discussed, @jbusecke, while it doesn't have a high priority at the moment, it'd be good to see if the main infrastructure of processing the CMIP6 data and deriving changes in extremes from the simulations can be made more efficient. This may be a good place to start.

@jbusecke I am revisting the old workflow here. Would be great if we could briefly discuss if/how this could be sped up in light of the many new datasets, during our meeting tomorrow!

Do you think this is solved by my work in https://github.com/jbusecke/CMIP6cex/tree/jbusecke_performance_regridding?
Or should I make a PR for that? FYI, I also mentioned this in a pangeo discourse topic recently. Hopefully for now we get a hacky yet sufficiently performant solution, but maybe in the future there is a more satisfying way to handle this in general.

@jbusecke yes and no, I incorporated your work in [https://github.com/Timh37/CMIP6cex/blob/main/cmip6_processing/testing/store_CMIP6_regridded_datasets.ipynb](https://github.com/Timh37/CMIP6cex/blob/main/cmip6_processing/testing/store_CMIP6_regridded_datasets.ipynb) which works like a charm. However, I am struggling to edit the workflow to regrid to tide gauges: https://github.com/Timh37/CMIP6cex/blob/main/cmip6_processing/testing/store_CMIP6_datasets_at_tgs.ipynb. I tried both using fancy indexing and regridding to each tide gauge in a loop, but both are slow (and failing to connect to the rescheduler at some point?). If you have a chance to take a look that would be appreciated!

Looks like this is solved by reducing the batch size! Will confirm when I know more.

Sounds good. We can put in some more effort here after mid Nov if needed.

I keep getting errors along these lines:
`/srv/conda/envs/notebook/lib/python3.10/site-packages/distributed/client.py:3141: UserWarning: Sending large graph of size 36.53 MiB.
This may cause some slowdown.
Consider scattering data ahead of time and using futures.
warnings.warn(
/srv/conda/envs/notebook/lib/python3.10/site-packages/distributed/client.py:3141: UserWarning: Sending large graph of size 33.03 MiB.
This may cause some slowdown.
Consider scattering data ahead of time and using futures.
warnings.warn(
Exception in callback None()
handle:
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.10/site-packages/tornado/iostream.py", line 1367, in _do_ssl_handshake
self.socket.do_handshake()
File "/srv/conda/envs/notebook/lib/python3.10/ssl.py", line 1342, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1007)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.10/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "/srv/conda/envs/notebook/lib/python3.10/site-packages/tornado/platform/asyncio.py", line 192, in _handle_events
handler_func(fileobj, events)
File "/srv/conda/envs/notebook/lib/python3.10/site-packages/tornado/iostream.py", line 691, in _handle_events
self._handle_read()
File "/srv/conda/envs/notebook/lib/python3.10/site-packages/tornado/iostream.py", line 1454, in _handle_read
self._do_ssl_handshake()
File "/srv/conda/envs/notebook/lib/python3.10/site-packages/tornado/iostream.py", line 1385, in _do_ssl_handshake
return self.close(exc_info=err)
File "/srv/conda/envs/notebook/lib/python3.10/site-packages/tornado/iostream.py", line 606, in close
self._signal_closed()
File "/srv/conda/envs/notebook/lib/python3.10/site-packages/tornado/iostream.py", line 636, in _signal_closed
self._ssl_connect_future.exception()
asyncio.exceptions.CancelledError
2023-10-24 22:17:33,777 - distributed.client - ERROR - Failed to reconnect to scheduler after 30.00 seconds, closing client
/srv/conda/envs/notebook/lib/python3.10/site-packages/distributed/client.py:3141: UserWarning: Sending large graph of size 42.76 MiB.
This may cause some slowdown.
Consider scattering data ahead of time and using futures.
warnings.warn(`
I think I will hold off from updating the workflow with the speed improvements until we can figure this out after mid November.


Fix conflict with View Report page revamp

This pr was reviewed previously, only last commit to be reviewed - https://github.com/fylein/fyle-mobile-app2/pull/751/commits/83f6e1e56dda3e6d0b94469ed40e5a4ed8821f84


Links on D3D12 "Capability Querying" page are broken

Link to article:
https://docs.microsoft.com/en-us/windows/desktop/direct3d12/capability-querying
Problem:
Links for D3D12_FEATURE_DATA_PROTECTED_RESOURCE_SESSION_SUPPORT and D3D12_FEATURE_DATA_SERIALIZATION are 404. It's not all of the links, only some of them, including these two

Filing as a reminder to myself to fix this later

A change has been pushed through to address this and I'm waiting for the results to show up on the page

This has been fixed. Thanks @stevewhims for your help!


Right-Alt key on MacOS is treated as Option instead of Meta

What did you expect to happen?
When pressing Right-Alt, it should be interpreted as Meta. This works as expected if I start Emacs with the -Q option (no config loaded), so this is a doom issue.
What actually happened?
When pressing Right-Alt, it is incorrectly interpreted as Option.
Steps to reproduce:

Install the latest doom on macos
start emacs and try any Meta command, such as M-< or M-> using Right-Alt as M

System information:

WARNING (:tools macos) module was moved to (:os macos)
```
SYSTEM  type       darwin
	config     x86_64-apple-darwin19.5.0
	shell      /usr/local/bin/fish
	uname      Darwin 19.4.0 Darwin Kernel Version 19.4.0: Wed Mar  4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64 x86_64
	path       (~/.cabal/bin ~/.ghcup/bin ~/.emacs.d/bin ~/.local/bin /usr/local/opt/node@12/bin ~/.cabal/bin ~/.ghcup/bin ~/.emacs.d/bin ~/.local/bin /Applications/Emacs.app/Contents/MacOS/ /usr/local/opt/node@12/bin ~/.cabal/bin ~/.ghcup/bin ~/.emacs.d/bin ~/.local/bin /usr/local/opt/node@12/bin ~/.cabal/bin ~/.ghcup/bin ~/.emacs.d/bin ~/.local/bin /usr/local/opt/node@12/bin /usr/local/bin /usr/bin /bin /usr/sbin /sbin /usr/local/share/dotnet ~/.dotnet/tools /Library/Frameworks/Mono.framework/Versions/Current/Commands<EMAIL_ADDRESS>EMACS   dir        ~/.emacs.d/
	version    27.1
	build      Aug 27, 2020
	buildopts  --disable-dependency-tracking --disable-silent-rules --enable-locallisppath=/usr/local/share/emacs/site-lisp<EMAIL_ADDRESS><EMAIL_ADDRESS>--with-xml2 --with-gnutls --without-dbus --with-imagemagick --with-modules --with-rsvg --with-ns --disable-ns-self-contained
	features   RSVG IMAGEMAGICK GLIB NOTIFY KQUEUE ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS JSON PDUMPER LCMS2 GMP
	traits     (batch server-running envvar-file)
DOOM    dir        ~/.doom.d/
	version    2.0.9
	build      HEAD -> develop, origin/develop, origin/HEAD 471028ce9 2020-10-27 23:47:59 -0400
	elc-files  0
	modules    (:completion company helm :ui doom doom-dashboard doom-quit hl-todo hydra modeline ophints (popup +defaults) treemacs vc-gutter vi-tilde-fringe workspaces :editor file-templates fold (format +onsave) snippets :emacs dired electric undo vc :checkers syntax :tools (debugger +lsp) (eval +overlay) lookup lsp :os macos :tools magit :lang cc csharp elm emacs-lisp (fsharp +lsp) (haskell +ghcide) json (java +lsp) (javascript +lsp) markdown org python rust (sh +fish) web yaml :config (default +bindings +smartparens))
	packages   ((zenburn-theme))
	unpin      (n/a)
	elpa       (n/a)
```

How I fixed it (for now)
(setq ns-right-alternate-modifier 'left)

This is intentional. These are Doom's default settings for MacOS modifiers:
(setq mac-command-modifier      'super
      ns-command-modifier       'super
      mac-option-modifier       'meta
      ns-option-modifier        'meta
      mac-right-option-modifier 'none
      ns-right-option-modifier  'none)

The rationale is this: left option can be used as meta, right option can be used for special character composition. I will close this since it isn't an issue.

My system does not seem to detect these changes. I've added hlissner's snippet from above and restarted emacs. Pressing on either option key results in "... is undefined" (Danish keyboard)
Details:
SYSTEM  info       (MacOS  . Darwin 18.7.0 x86_64)
	shell      /bin/zsh
	path<EMAIL_ADDRESS>/usr/local/opt/protobuf/bin ~/Work/CodeReadyContainers/crc-macos-1.21.0-amd64 ~/Work/self-serve/bin /usr/local/opt/coreutils/libexec/gnubin /usr/local/opt/gnu-sed/libexec/gnubin /usr/local/opt/node@12/bin /usr/local/opt/python/libexec/bin ~/.emacs.d/bin<EMAIL_ADDRESS>/usr/local/opt/protobuf/bin ~/Work/CodeReadyContainers/crc-macos-1.21.0-amd64 ~/Work/self-serve/bin /usr/local/opt/coreutils/libexec/gnubin /usr/local/opt/gnu-sed/libexec/gnubin /usr/local/opt/node@12/bin /usr/local/opt/python/libexec/bin /usr/local/bin /usr/bin /bin /usr/sbin /sbin /usr/local/go/bin /usr/local/MacGPG2/bin /usr/local/Cellar/emacs/27.1/libexec/emacs/27.1/x86_64-apple-darwin18.7.0)
EMACS   dir        ~/.emacs.d/
	version    (27.1 Sep 04, 2020)
	buildopts  --disable-silent-rules --enable-locallisppath=/usr/local/share/emacs/site-lisp --infodir=/usr/local/Cellar/emacs/27.1/share/info/emacs --prefix=/usr/local/Cellar/emacs/27.1 --with-gnutls --without-x --with-xml2 --without-dbus --with-modules --without-ns --without-imagemagick
	features   NOTIFY KQUEUE ACL GNUTLS LIBXML2 ZLIB MODULES THREADS JSON PDUMPER GMP
	traits     (batch envvar-file)
DOOM    dir        ~/.doom.d/
	version    (2.0.9 HEAD -> develop, origin/develop, origin/HEAD 5e8a66831 2021-02-14 21:14:07 -0500)
	modules    (:completion company ivy :ui doom doom-dashboard doom-quit hl-todo modeline ophints (popup +defaults) vc-gutter vi-tilde-fringe workspaces :editor (evil +everywhere) file-templates fold (format +onsave) snippets :emacs dired electric undo vc :checkers syntax (spell +flyspell) :tools (eval +overlay) lookup lsp magit :os macos :lang emacs-lisp (go +lsp) markdown org sh yaml :config (default +bindings +smartparens))
	packages   ((evil-tutor))
	unpin      (n/a)
	elpa       (n/a)

My system does not seem to detect these changes. I've added hlissner's snippet from above to "~/.doom.d/config.el" and restarted emacs. Pressing either option key results in "... is undefined" (Danish keyboard) as it did before I tried adding the snippet.

That means your "option" key is bound to something other than a modifier, because a modifier by itself is not a complete key sequence as far as Emacs is concerned. This can't be tampered with from within Emacs, so this is likely an issue with your OS or software you use to remap the option key.


sql: clarify region survivability ups replication factor to 5

In https://www.cockroachlabs.com/docs/v21.1/multiregion-overview.html#surviving-region-failures we disucss surviving region failures but we don't specify that we up the replication factor to 5. We want to be careful about exposing this in too much detail but its valuable to document it and to explain that this will allow one node failure without moving the leaseholder out of the region to protect read latency.

We probably need to introduce it in the architecture docs too https://www.cockroachlabs.com/docs/v21.1/architecture/replication-layer.html#non-voting-replicas

We don't expect users to directly set RF anymore--they should declare their survival goals to us and we will adjust the replicas accordingly. We don't want them to set it directly because it has complicated interactions with leaseholders, replica placement, and latency goals.

Andy is this request from a user?  If so do you mind adding more context about what we want to solve by doing this?
Presumably if you are a new user of the multi-region abstractions, you don't necessarily know about num_replicas=5 and zone configs, nor do you really need to care about it since we now handle that for you (right?)
And if you are a user of the old way of doing things transitioning to the new, you can still look at your zone configs after running the new SQL statements and find out what is happening using SHOW ZONE CONFIGURATIONS?  but then basically (AIUI) you should like, not touch it too much because you are likely to run into breaking the various multi-region zone config validations
If this is an internal ask I'd rather we do some internal docs/training and not add this to user-facing docs.
There is a cost here: if 5% of users need this, it's now in the docs adding complexity and tripping up the other 95% who don't.  Once you have to know about num_replicas, you have to know about zone configs.  Once you have to know about zone configs, you are down the rabbit hole and this is no longer an "abstraction" if you have to know all about how zone configs work in order to use it
ya know? or am I totes misunderstanding something here?

It's come up several times from internal folks needing to explain things to users (and to prove that certain failure domains work). I agree with the general spirit of your point that we don't want to confuse everyone for a more involved minority. However, I think this information needs to be available as a part of reference documentation. We absolutely do not want the average user to need to understand replication and quorum, but the advanced user should be able to discover this information.


Retry of failed upload uploaded image again

Summary:
I started an upload of an image and put my phone in the pocket. Next time I open it I have a notification that it failed. In the list on the main view of the app I pressed the retry icon in the lower right corner of the image. The image starts the upload again and it seems to succeed. When I later look at my contributions I noticed that the image actually did succeed the first time and it then uploaded the same image again:

https://commons.wikimedia.org/wiki/File:Timorstraat.jpg
https://commons.wikimedia.org/wiki/File:Timorstraat_2.jpg

In the app it looks like only the second one has been uploaded.
Steps to reproduce:
I don't know how to reproduce.
Device and Android version:
What make and model device (e.g., Samsung J7) did you encounter this on?
Samsung Galaxy S7 Edge
What Android version (e.g., Android 4.0 Ice Cream Sandwich or Android 6.0 Marshmallow) are you running?
Android version 8.0.0
Samsung Experience version 9.0
Is it the stock version from the manufacturer or a custom ROM ?
The stock version.
Commons app version:
2.11.0~93b948d20
Would you like to work on the issue?
No.

Thanks for figuring out this bug @Ainali. This must have been one of those cases when the image does get uploaded but one of the other steps fail.

Any newcomer willing to take this? :-)
Tip: To make an upload fail, switch Android to airplane mode just after the upload starts.

Hi, can I work on this??

It is yours @FernandaCG :) This can be a relatively complicated task, so please communicate with us about the steps you have done so that we can share ideas.

Hi @neslihanturan, I have been debugging the app, and I think that in the method retryUpload in ContributionViewHolder we could validate if the file already exists, but idk which attribute of the contribution could I use. Can you give me some feedback?

Hi guys, can I work in this issue?

I am having a similar issue.  However, I didn't have an uploading error message and it looks like only one copy of my image uploads commons.wikimedia.org the app showing two.
Summary:
After uploading photos, I see duplicate images in the app's "contributions" screen.
Steps to reproduce:

Upload an image to Wikimedia Commons using this Android App.
Look though your photos in the "contribution" for duplicate images (they may not be adjacent to each other in the image feed).
View your account's "uploads" on https://commons.wikimedia.org and look for any duplicate images.

I see duplicate images on the app but the website shows that the photo uploaded correctly (no duplicates).
System logs:
Logs exported from the app: https://privatebin.net/?6ccdcedda9153900#7YwYwPohymf1LZ6iBuUf8jBQBbj9hDzUjiZcwGvejr4i
Device and Android version:
API level: 29
Android version: 10
Device manufacturer: Google
Device model: Pixel 2
Device: walleye
Network type: wifi
App version name: 2.12.3~dc08a5e88
User name: Mds08011
Commons app version:
App version name: 2.12.3~dc08a5e88
I am currently using the Beta version but this issue occurred on the regular/stable version as well.
Screen-shots:
Duplicate photo in app:

Duplicate photo in app:

"Uplaods" on website showing only single images:

Would you like to work on the issue?
No.  I don't have the technical knowledge to address this.

@Ainali Do you mean all failed uploads show correctly after you retry them?  Thanks :-)

I think this issue is similar to what I have reproduced. The upload failed, an attempt to upload again failed even after the progress was complete. I restarted the app and noticed the image was uploaded yet it also showed the failed upload. I experienced this on 2 occasions...

Can I take this one one, please?

@michaelnares As a first step, can you try to reproduce this issue and list down the steps here.

@michaelnares As a first step, can you try to reproduce this issue and list down the steps here.

@maskaravivek I get https://stackoverflow.com/questions/38618885/error-rpc-failed-curl-transfer-closed-with-outstanding-read-data-remaining.  I have success after git clone https://github.com/commons-app/apps-android-commons.git --depth 1
and cd apps-android-commons/, but the same error after git fetch --unshallow.  Is there any issue with working on the repository without doing git fetch --unshallow, please?

Has anyone been able to reproduce this issue on the latest commits?

@ashishkumar468 I am having so many failed upload with recent versions, but retry always works perfectly. I guess this can be closed if nobody manages to reproduce with the latest version.

Hi @nicolas-raoul  Should we create a new issue for that, as this issue is related to retries?

There is already an issue about the failures. My comment above was only saying that retry works :-)

@nicolas-raoul  Ohh, okay, so we can close this issue right?

I think it is OK to close it, yes.

For reference, the issue regarding failed uploads is #3247 .


99 vulnerabilities found innpm audit

Hi,
I was trying out cloning this repo and doing install locally, npm install indicated 99 vulnerabilities found.
Reporting issue - so this does not fall out of track. (master branch)
added 2145 packages from 1770 contributors in 464.896s
[!] 99 vulnerabilities found [18775 packages audited]
    Severity: 42 Low | 23 Moderate | 32 High | 2 Critical
    Run `npm audit` for more detail

mj@my-lappy:~/GIT/ekstep-repos-all/sunbird-portal/src$ npm audit

                       === npm audit security report ===

# Run  npm install<EMAIL_ADDRESS>to resolve 21 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change

  Low             Prototype Pollution

  Package         lodash

  Dependency of   karma

  Path            karma > lodash

  More info       https://nodesecurity.io/advisories/577

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   karma [dev]

  Path            karma > connect > body-parser > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   karma [dev]

  Path            karma > connect > compression > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   karma [dev]

  Path            karma > connect > connect-timeout > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   karma [dev]

  Path            karma > connect > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   karma [dev]

  Path            karma > connect > express-session > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   karma [dev]

  Path            karma > connect > finalhandler > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   karma [dev]

  Path            karma > connect > morgan > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   karma [dev]

  Path            karma > connect > serve-index > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   karma [dev]

  Path            karma > connect > serve-static > send > debug

  More info       https://nodesecurity.io/advisories/534

  High            Regular Expression Denial of Service

  Package         minimatch

  Dependency of   karma [dev]

  Path            karma > minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         negotiator

  Dependency of   karma [dev]

  Path            karma > connect > compression > accepts > negotiator

  More info       https://nodesecurity.io/advisories/106

  High            Regular Expression Denial of Service

  Package         negotiator

  Dependency of   karma [dev]

  Path            karma > connect > serve-index > accepts > negotiator

  More info       https://nodesecurity.io/advisories/106

  High            Regular Expression Denial of Service

  Package         fresh

  Dependency of   karma [dev]

  Path            karma > connect > fresh

  More info       https://nodesecurity.io/advisories/526

  High            Regular Expression Denial of Service

  Package         fresh

  Dependency of   karma [dev]

  Path            karma > connect > serve-favicon > fresh

  More info       https://nodesecurity.io/advisories/526

  High            Regular Expression Denial of Service

  Package         fresh

  Dependency of   karma [dev]

  Path            karma > connect > serve-static > send > fresh

  More info       https://nodesecurity.io/advisories/526

  Moderate        Regular Expression Denial of Service

  Package         mime

  Dependency of   karma [dev]

  Path            karma > connect > serve-static > send > mime

  More info       https://nodesecurity.io/advisories/535

  High            Denial of Service

  Package         ws

  Dependency of   karma [dev]

  Path            karma > socket.io > socket.io-client > ws

  More info       https://nodesecurity.io/advisories/550

  High            DoS due to excessively large websocket message

  Package         ws

  Dependency of   karma [dev]

  Path            karma > socket.io > socket.io-client > ws

  More info       https://nodesecurity.io/advisories/120

  Low             Remote Memory Disclosure

  Package         ws

  Dependency of   karma [dev]

  Path            karma > socket.io > socket.io-client > ws

  More info       https://nodesecurity.io/advisories/67

  High            Regular Expression Denial of Service

  Package         minimatch

  Dependency of   karma [dev]

  Path            karma > glob > minimatch

  More info       https://nodesecurity.io/advisories/118

# Run  npm install<EMAIL_ADDRESS>to resolve 4 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   gulp-less

  Path            gulp-less > less > request > hawk > boom > hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   gulp-less

  Path            gulp-less > less > request > hawk > cryptiles > boom > hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   gulp-less

  Path            gulp-less > less > request > hawk > hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   gulp-less

  Path            gulp-less > less > request > hawk > sntp > hoek

  More info       https://nodesecurity.io/advisories/566

# Run  npm install<EMAIL_ADDRESS>to resolve 4 vulnerabilities

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   phantomjs-prebuilt

  Path            phantomjs-prebuilt > request > hawk > boom > hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   phantomjs-prebuilt

  Path            phantomjs-prebuilt > request > hawk > cryptiles > boom >
                  hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   phantomjs-prebuilt

  Path            phantomjs-prebuilt > request > hawk > hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   phantomjs-prebuilt

  Path            phantomjs-prebuilt > request > hawk > sntp > hoek

  More info       https://nodesecurity.io/advisories/566

# Run  npm install --dev<EMAIL_ADDRESS>to resolve 4 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change

  Low             Prototype Pollution

  Package         lodash

  Dependency of   gulp [dev]

  Path            gulp > vinyl-fs > glob-watcher > gaze > globule > lodash

  More info       https://nodesecurity.io/advisories/577

  High            Regular Expression Denial of Service

  Package         minimatch

  Dependency of   gulp [dev]

  Path            gulp > vinyl-fs > glob-stream > minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Dependency of   gulp [dev]

  Path            gulp > vinyl-fs > glob-watcher > gaze > globule > glob >
                  minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Dependency of   gulp [dev]

  Path            gulp > vinyl-fs > glob-watcher > gaze > globule > minimatch

  More info       https://nodesecurity.io/advisories/118

# Run  npm install --dev<EMAIL_ADDRESS>to resolve 11 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > body-parser > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > compression > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > connect-timeout > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > express-session > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > finalhandler > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > morgan > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > serve-index > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > serve-static > send > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > tiny-lr > body-parser > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > tiny-lr > debug

  More info       https://nodesecurity.io/advisories/534

# Run  npm install<EMAIL_ADDRESS>to resolve 2 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   jsonwebtoken

  Path            jsonwebtoken > joi > hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   jsonwebtoken

  Path            jsonwebtoken > joi > topo > hoek

  More info       https://nodesecurity.io/advisories/566

# Run  npm install --dev<EMAIL_ADDRESS>to resolve 6 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change

  Moderate        Memory Exposure

  Package         tunnel-agent

  Dependency of   gulp-imagemin [dev]

  Path            gulp-imagemin > imagemin > imagemin-gifsicle > gifsicle >
                  bin-build > download > caw > tunnel-agent

  More info       https://nodesecurity.io/advisories/598

  Moderate        Memory Exposure

  Package         tunnel-agent

  Dependency of   gulp-imagemin [dev]

  Path            gulp-imagemin > imagemin > imagemin-gifsicle > gifsicle >
                  bin-wrapper > download > caw > tunnel-agent

  More info       https://nodesecurity.io/advisories/598

  Moderate        Memory Exposure

  Package         tunnel-agent

  Dependency of   gulp-imagemin [dev]

  Path            gulp-imagemin > imagemin > imagemin-jpegtran > jpegtran-bin
                  > bin-build > download > caw > tunnel-agent

  More info       https://nodesecurity.io/advisories/598

  Moderate        Memory Exposure

  Package         tunnel-agent

  Dependency of   gulp-imagemin [dev]

  Path            gulp-imagemin > imagemin > imagemin-jpegtran > jpegtran-bin
                  > bin-wrapper > download > caw > tunnel-agent

  More info       https://nodesecurity.io/advisories/598

  Moderate        Memory Exposure

  Package         tunnel-agent

  Dependency of   gulp-imagemin [dev]

  Path            gulp-imagemin > imagemin > imagemin-optipng > optipng-bin >
                  bin-build > download > caw > tunnel-agent

  More info       https://nodesecurity.io/advisories/598

  Moderate        Memory Exposure

  Package         tunnel-agent

  Dependency of   gulp-imagemin [dev]

  Path            gulp-imagemin > imagemin > imagemin-optipng > optipng-bin >
                  bin-wrapper > download > caw > tunnel-agent

  More info       https://nodesecurity.io/advisories/598

# Run  npm install<EMAIL_ADDRESS>to resolve 2 vulnerabilities

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   helmet

  Path            helmet > connect > debug

  More info       https://nodesecurity.io/advisories/534

  Low             Regular Expression Denial of Service

  Package         debug

  Dependency of   helmet

  Path            helmet > connect > finalhandler > debug

  More info       https://nodesecurity.io/advisories/534

# Run  npm install --dev<EMAIL_ADDRESS>to resolve 1 vulnerability
SEMVER WARNING: Recommended action is a potentially breaking change

  Low             Prototype Pollution

  Package         lodash

  Dependency of   wiredep [dev]

  Path            wiredep > lodash

  More info       https://nodesecurity.io/advisories/577

# Run  npm install --dev<EMAIL_ADDRESS>to resolve 1 vulnerability
SEMVER WARNING: Recommended action is a potentially breaking change

  Low             Large gzip Denial of Service

  Package         superagent

  Dependency of   chai-http [dev]

  Path            chai-http > superagent

  More info       https://nodesecurity.io/advisories/479

# Run  npm update phantomjs-prebuilt --depth 2  to resolve 4 vulnerabilities

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   karma-phantomjs-launcher

  Path            karma-phantomjs-launcher > phantomjs-prebuilt > request >
                  hawk > boom > hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   karma-phantomjs-launcher

  Path            karma-phantomjs-launcher > phantomjs-prebuilt > request >
                  hawk > cryptiles > boom > hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   karma-phantomjs-launcher

  Path            karma-phantomjs-launcher > phantomjs-prebuilt > request >
                  hawk > hoek

  More info       https://nodesecurity.io/advisories/566

  Moderate        Prototype pollution

  Package         hoek

  Dependency of   karma-phantomjs-launcher

  Path            karma-phantomjs-launcher > phantomjs-prebuilt > request >
                  hawk > sntp > hoek

  More info       https://nodesecurity.io/advisories/566

                                 Manual Review
             Some vulnerabilities require your attention to resolve

          Visit https://go.npm.me/audit-guide for additional guidance

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp [dev]

  Path            gulp > vinyl-fs > glob-stream > glob > minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp-jshint [dev]

  Path            gulp-jshint > minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp-load-plugins [dev]

  Path            gulp-load-plugins > findup-sync > glob > minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp-load-plugins [dev]

  Path            gulp-load-plugins > multimatch > minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   wiredep [dev]

  Path            wiredep > glob > minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp-jasmine-node [dev]

  Path            gulp-jasmine-node > jasmine-node > gaze > minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-mocha > mocha > glob > minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp-jasmine-node [dev]

  Path            gulp-jasmine-node > jasmine-node > gaze > fileset > glob >
                  minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-istanbul > istanbul > fileset > glob >
                  minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-jshint > minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-load-plugins > findup-sync > glob >
                  minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-load-plugins > multimatch > minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp-jasmine-node [dev]

  Path            gulp-jasmine-node > jasmine-node > gaze > fileset >
                  minimatch

  More info       https://nodesecurity.io/advisories/118

  High            Regular Expression Denial of Service

  Package         minimatch

  Patched in      >=3.0.2

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-istanbul > istanbul > fileset > minimatch

  More info       https://nodesecurity.io/advisories/118

  Critical        Command Injection

  Package         growl

  Patched in      >=1.10.2

  Dependency of   gulp-jasmine-node [dev]

  Path            gulp-jasmine-node > jasmine-node > jasmine-growl-reporter >
                  growl

  More info       https://nodesecurity.io/advisories/146

  Critical        Command Injection

  Package         growl

  Patched in      >=1.10.2

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-mocha > mocha > growl

  More info       https://nodesecurity.io/advisories/146

  Low             Prototype Pollution

  Package         lodash

  Patched in      >=4.17.5

  Dependency of   asyncawait

  Path            asyncawait > lodash

  More info       https://nodesecurity.io/advisories/577

  Low             Prototype Pollution

  Package         lodash

  Patched in      >=4.17.5

  Dependency of   gulp-jshint

  Path            gulp-jshint > lodash

  More info       https://nodesecurity.io/advisories/577

  Low             Prototype Pollution

  Package         lodash

  Patched in      >=4.17.5

  Dependency of   gulp-jshint [dev]

  Path            gulp-jshint > jshint > lodash

  More info       https://nodesecurity.io/advisories/577

  Low             Prototype Pollution

  Package         lodash

  Patched in      >=4.17.5

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-jshint > jshint > lodash

  More info       https://nodesecurity.io/advisories/577

  Low             Prototype Pollution

  Package         lodash

  Patched in      >=4.17.5

  Dependency of   gulp-jshint [dev]

  Path            gulp-jshint > rcloader > lodash

  More info       https://nodesecurity.io/advisories/577

  Low             Prototype Pollution

  Package         lodash

  Patched in      >=4.17.5

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-istanbul > lodash

  More info       https://nodesecurity.io/advisories/577

  Low             Prototype Pollution

  Package         lodash

  Patched in      >=4.17.5

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-jshint > lodash

  More info       https://nodesecurity.io/advisories/577

  Low             Prototype Pollution

  Package         lodash

  Patched in      >=4.17.5

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-jshint > rcloader > lodash

  More info       https://nodesecurity.io/advisories/577

  Low             Prototype Pollution

  Package         lodash

  Patched in      >=4.17.5

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-load-plugins > findup-sync > lodash

  More info       https://nodesecurity.io/advisories/577

  Low             Prototype Pollution

  Package         lodash

  Patched in      >=4.17.5

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-help > lodash

  More info       https://nodesecurity.io/advisories/577

  High            Regular Expression Denial of Service

  Package         fresh

  Patched in      >= 0.5.2

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > fresh

  More info       https://nodesecurity.io/advisories/526

  High            Regular Expression Denial of Service

  Package         fresh

  Patched in      >= 0.5.2

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > serve-favicon > fresh

  More info       https://nodesecurity.io/advisories/526

  High            Regular Expression Denial of Service

  Package         fresh

  Patched in      >= 0.5.2

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > serve-static > send > fresh

  More info       https://nodesecurity.io/advisories/526

  High            Regular Expression Denial of Service

  Package         negotiator

  Patched in      >= 0.6.1

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > compression > accepts > negotiator

  More info       https://nodesecurity.io/advisories/106

  High            Regular Expression Denial of Service

  Package         negotiator

  Patched in      >= 0.6.1

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > serve-index > accepts > negotiator

  More info       https://nodesecurity.io/advisories/106

  High            Cross-Site Scripting

  Package         handlebars

  Patched in      >=4.0.0

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-istanbul > istanbul > handlebars

  More info       https://nodesecurity.io/advisories/61

  Low             Incorrect Handling of Non-Boolean Comparisons During
                  Minification

  Package         uglify-js

  Patched in      >= 2.4.24

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-istanbul > istanbul > handlebars >
                  uglify-js

  More info       https://nodesecurity.io/advisories/39

  Low             Incorrect Handling of Non-Boolean Comparisons During
                  Minification

  Package         uglify-js

  Patched in      >= 2.4.24

  Dependency of   karma [dev]

  Path            karma > socket.io > socket.io-client > uglify-js

  More info       https://nodesecurity.io/advisories/39

  Low             Regular Expression Denial of Service

  Package         uglify-js

  Patched in      >=2.6.0

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-istanbul > istanbul > handlebars >
                  uglify-js

  More info       https://nodesecurity.io/advisories/48

  Low             Regular Expression Denial of Service

  Package         uglify-js

  Patched in      >=2.6.0

  Dependency of   karma [dev]

  Path            karma > socket.io > socket.io-client > uglify-js

  More info       https://nodesecurity.io/advisories/48

  Moderate        Regular Expression Denial of Service

  Package         ms

  Patched in      >0.7.0

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-mocha > mocha > debug > ms

  More info       https://nodesecurity.io/advisories/46

  Moderate        Regular Expression Denial of Service

  Package         mime

  Patched in      >= 1.4.1 < 2.0.0 || >= 2.0.3

  Dependency of   gulp-connect [dev]

  Path            gulp-connect > connect > serve-static > send > mime

  More info       https://nodesecurity.io/advisories/535

  Low             Regular Expression Denial of Service

  Package         debug

  Patched in      >= 2.6.9 < 3.0.0 || >= 3.1.0

  Dependency of   gulp-test [dev]

  Path            gulp-test > gulp-mocha > mocha > debug

  More info       https://nodesecurity.io/advisories/534

[!] 99 vulnerabilities found - Packages audited: 18775 (18032 dev, 8557 optional)
    Severity: 42 Low | 23 Moderate | 32 High | 2 Critical

Thanks for reporting this. This should be tracked in a JiRA item.
On Wed 16 May, 2018 15:39 Manoj L<EMAIL_ADDRESS>wrote:

Hi,
I was trying out cloning this repo and doing install locally, npm install
indicated 99 vulnerabilities found.
Reporting issue - so this does not fall out of track.
added 2145 packages from 1770 contributors in 464.896s
[!] 99 vulnerabilities found [18775 packages audited]
Severity: 42 Low | 23 Moderate | 32 High | 2 Critical
Run npm audit for more detail
mj@my-lappy:~/GIT/ekstep-repos-all/sunbird-portal/src$ npm audit
                   === npm audit security report ===

Run  npm install<EMAIL_ADDRESS>to resolve 21 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change
Low             Prototype Pollution
Package         lodash
Dependency of   karma
Path            karma > lodash
More info       https://nodesecurity.io/advisories/577
Low             Regular Expression Denial of Service
Package         debug
Dependency of   karma [dev]
Path            karma > connect > body-parser > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   karma [dev]
Path            karma > connect > compression > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   karma [dev]
Path            karma > connect > connect-timeout > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   karma [dev]
Path            karma > connect > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   karma [dev]
Path            karma > connect > express-session > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   karma [dev]
Path            karma > connect > finalhandler > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   karma [dev]
Path            karma > connect > morgan > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   karma [dev]
Path            karma > connect > serve-index > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   karma [dev]
Path            karma > connect > serve-static > send > debug
More info       https://nodesecurity.io/advisories/534
High            Regular Expression Denial of Service
Package         minimatch
Dependency of   karma [dev]
Path            karma > minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         negotiator
Dependency of   karma [dev]
Path            karma > connect > compression > accepts > negotiator
More info       https://nodesecurity.io/advisories/106
High            Regular Expression Denial of Service
Package         negotiator
Dependency of   karma [dev]
Path            karma > connect > serve-index > accepts > negotiator
More info       https://nodesecurity.io/advisories/106
High            Regular Expression Denial of Service
Package         fresh
Dependency of   karma [dev]
Path            karma > connect > fresh
More info       https://nodesecurity.io/advisories/526
High            Regular Expression Denial of Service
Package         fresh
Dependency of   karma [dev]
Path            karma > connect > serve-favicon > fresh
More info       https://nodesecurity.io/advisories/526
High            Regular Expression Denial of Service
Package         fresh
Dependency of   karma [dev]
Path            karma > connect > serve-static > send > fresh
More info       https://nodesecurity.io/advisories/526
Moderate        Regular Expression Denial of Service
Package         mime
Dependency of   karma [dev]
Path            karma > connect > serve-static > send > mime
More info       https://nodesecurity.io/advisories/535
High            Denial of Service
Package         ws
Dependency of   karma [dev]
Path            karma > socket.io > socket.io-client > ws
More info       https://nodesecurity.io/advisories/550
High            DoS due to excessively large websocket message
Package         ws
Dependency of   karma [dev]
Path            karma > socket.io > socket.io-client > ws
More info       https://nodesecurity.io/advisories/120
Low             Remote Memory Disclosure
Package         ws
Dependency of   karma [dev]
Path            karma > socket.io > socket.io-client > ws
More info       https://nodesecurity.io/advisories/67
High            Regular Expression Denial of Service
Package         minimatch
Dependency of   karma [dev]
Path            karma > glob > minimatch
More info       https://nodesecurity.io/advisories/118
Run  npm install<EMAIL_ADDRESS>to resolve 4 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change
Moderate        Prototype pollution
Package         hoek
Dependency of   gulp-less
Path            gulp-less > less > request > hawk > boom > hoek
More info       https://nodesecurity.io/advisories/566
Moderate        Prototype pollution
Package         hoek
Dependency of   gulp-less
Path            gulp-less > less > request > hawk > cryptiles > boom > hoek
More info       https://nodesecurity.io/advisories/566
Moderate        Prototype pollution
Package         hoek
Dependency of   gulp-less
Path            gulp-less > less > request > hawk > hoek
More info       https://nodesecurity.io/advisories/566
Moderate        Prototype pollution
Package         hoek
Dependency of   gulp-less
Path            gulp-less > less > request > hawk > sntp > hoek
More info       https://nodesecurity.io/advisories/566
Run  npm install<EMAIL_ADDRESS>to resolve 4 vulnerabilities
Moderate        Prototype pollution
Package         hoek
Dependency of   phantomjs-prebuilt
Path            phantomjs-prebuilt > request > hawk > boom > hoek
More info       https://nodesecurity.io/advisories/566
Moderate        Prototype pollution
Package         hoek
Dependency of   phantomjs-prebuilt
Path            phantomjs-prebuilt > request > hawk > cryptiles > boom >
hoek
More info       https://nodesecurity.io/advisories/566
Moderate        Prototype pollution
Package         hoek
Dependency of   phantomjs-prebuilt
Path            phantomjs-prebuilt > request > hawk > hoek
More info       https://nodesecurity.io/advisories/566
Moderate        Prototype pollution
Package         hoek
Dependency of   phantomjs-prebuilt
Path            phantomjs-prebuilt > request > hawk > sntp > hoek
More info       https://nodesecurity.io/advisories/566
Run  npm install --dev<EMAIL_ADDRESS>to resolve 4 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change
Low             Prototype Pollution
Package         lodash
Dependency of   gulp [dev]
Path            gulp > vinyl-fs > glob-watcher > gaze > globule > lodash
More info       https://nodesecurity.io/advisories/577
High            Regular Expression Denial of Service
Package         minimatch
Dependency of   gulp [dev]
Path            gulp > vinyl-fs > glob-stream > minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Dependency of   gulp [dev]
Path            gulp > vinyl-fs > glob-watcher > gaze > globule > glob >
minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Dependency of   gulp [dev]
Path            gulp > vinyl-fs > glob-watcher > gaze > globule > minimatch
More info       https://nodesecurity.io/advisories/118
Run  npm install --dev<EMAIL_ADDRESS>to resolve 11 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change
Low             Regular Expression Denial of Service
Package         debug
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > body-parser > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > compression > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > connect-timeout > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > express-session > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > finalhandler > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > morgan > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > serve-index > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > serve-static > send > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   gulp-connect [dev]
Path            gulp-connect > tiny-lr > body-parser > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   gulp-connect [dev]
Path            gulp-connect > tiny-lr > debug
More info       https://nodesecurity.io/advisories/534
Run  npm install<EMAIL_ADDRESS>to resolve 2 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change
Moderate        Prototype pollution
Package         hoek
Dependency of   jsonwebtoken
Path            jsonwebtoken > joi > hoek
More info       https://nodesecurity.io/advisories/566
Moderate        Prototype pollution
Package         hoek
Dependency of   jsonwebtoken
Path            jsonwebtoken > joi > topo > hoek
More info       https://nodesecurity.io/advisories/566
Run  npm install --dev<EMAIL_ADDRESS>to resolve 6 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change
Moderate        Memory Exposure
Package         tunnel-agent
Dependency of   gulp-imagemin [dev]
Path            gulp-imagemin > imagemin > imagemin-gifsicle > gifsicle >
bin-build > download > caw > tunnel-agent
More info       https://nodesecurity.io/advisories/598
Moderate        Memory Exposure
Package         tunnel-agent
Dependency of   gulp-imagemin [dev]
Path            gulp-imagemin > imagemin > imagemin-gifsicle > gifsicle >
bin-wrapper > download > caw > tunnel-agent
More info       https://nodesecurity.io/advisories/598
Moderate        Memory Exposure
Package         tunnel-agent
Dependency of   gulp-imagemin [dev]
Path            gulp-imagemin > imagemin > imagemin-jpegtran > jpegtran-bin
> bin-build > download > caw > tunnel-agent
More info       https://nodesecurity.io/advisories/598
Moderate        Memory Exposure
Package         tunnel-agent
Dependency of   gulp-imagemin [dev]
Path            gulp-imagemin > imagemin > imagemin-jpegtran > jpegtran-bin
> bin-wrapper > download > caw > tunnel-agent
More info       https://nodesecurity.io/advisories/598
Moderate        Memory Exposure
Package         tunnel-agent
Dependency of   gulp-imagemin [dev]
Path            gulp-imagemin > imagemin > imagemin-optipng > optipng-bin >
bin-build > download > caw > tunnel-agent
More info       https://nodesecurity.io/advisories/598
Moderate        Memory Exposure
Package         tunnel-agent
Dependency of   gulp-imagemin [dev]
Path            gulp-imagemin > imagemin > imagemin-optipng > optipng-bin >
bin-wrapper > download > caw > tunnel-agent
More info       https://nodesecurity.io/advisories/598
Run  npm install<EMAIL_ADDRESS>to resolve 2 vulnerabilities
Low             Regular Expression Denial of Service
Package         debug
Dependency of   helmet
Path            helmet > connect > debug
More info       https://nodesecurity.io/advisories/534
Low             Regular Expression Denial of Service
Package         debug
Dependency of   helmet
Path            helmet > connect > finalhandler > debug
More info       https://nodesecurity.io/advisories/534
Run  npm install --dev<EMAIL_ADDRESS>to resolve 1 vulnerability
SEMVER WARNING: Recommended action is a potentially breaking change
Low             Prototype Pollution
Package         lodash
Dependency of   wiredep [dev]
Path            wiredep > lodash
More info       https://nodesecurity.io/advisories/577
Run  npm install --dev<EMAIL_ADDRESS>to resolve 1 vulnerability
SEMVER WARNING: Recommended action is a potentially breaking change
Low             Large gzip Denial of Service
Package         superagent
Dependency of   chai-http [dev]
Path            chai-http > superagent
More info       https://nodesecurity.io/advisories/479
Run  npm update phantomjs-prebuilt --depth 2  to resolve 4 vulnerabilities
Moderate        Prototype pollution
Package         hoek
Dependency of   karma-phantomjs-launcher
Path            karma-phantomjs-launcher > phantomjs-prebuilt > request >
hawk > boom > hoek
More info       https://nodesecurity.io/advisories/566
Moderate        Prototype pollution
Package         hoek
Dependency of   karma-phantomjs-launcher
Path            karma-phantomjs-launcher > phantomjs-prebuilt > request >
hawk > cryptiles > boom > hoek
More info       https://nodesecurity.io/advisories/566
Moderate        Prototype pollution
Package         hoek
Dependency of   karma-phantomjs-launcher
Path            karma-phantomjs-launcher > phantomjs-prebuilt > request >
hawk > hoek
More info       https://nodesecurity.io/advisories/566
Moderate        Prototype pollution
Package         hoek
Dependency of   karma-phantomjs-launcher
Path            karma-phantomjs-launcher > phantomjs-prebuilt > request >
hawk > sntp > hoek
More info       https://nodesecurity.io/advisories/566
                             Manual Review
         Some vulnerabilities require your attention to resolve

      Visit https://go.npm.me/audit-guide for additional guidance

High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp [dev]
Path            gulp > vinyl-fs > glob-stream > glob > minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp-jshint [dev]
Path            gulp-jshint > minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp-load-plugins [dev]
Path            gulp-load-plugins > findup-sync > glob > minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp-load-plugins [dev]
Path            gulp-load-plugins > multimatch > minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   wiredep [dev]
Path            wiredep > glob > minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp-jasmine-node [dev]
Path            gulp-jasmine-node > jasmine-node > gaze > minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-mocha > mocha > glob > minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp-jasmine-node [dev]
Path            gulp-jasmine-node > jasmine-node > gaze > fileset > glob >
minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-istanbul > istanbul > fileset > glob >
minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-jshint > minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-load-plugins > findup-sync > glob >
minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-load-plugins > multimatch > minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp-jasmine-node [dev]
Path            gulp-jasmine-node > jasmine-node > gaze > fileset >
minimatch
More info       https://nodesecurity.io/advisories/118
High            Regular Expression Denial of Service
Package         minimatch
Patched in      >=3.0.2
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-istanbul > istanbul > fileset > minimatch
More info       https://nodesecurity.io/advisories/118
Critical        Command Injection
Package         growl
Patched in      >=1.10.2
Dependency of   gulp-jasmine-node [dev]
Path            gulp-jasmine-node > jasmine-node > jasmine-growl-reporter >
growl
More info       https://nodesecurity.io/advisories/146
Critical        Command Injection
Package         growl
Patched in      >=1.10.2
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-mocha > mocha > growl
More info       https://nodesecurity.io/advisories/146
Low             Prototype Pollution
Package         lodash
Patched in      >=4.17.5
Dependency of   asyncawait
Path            asyncawait > lodash
More info       https://nodesecurity.io/advisories/577
Low             Prototype Pollution
Package         lodash
Patched in      >=4.17.5
Dependency of   gulp-jshint
Path            gulp-jshint > lodash
More info       https://nodesecurity.io/advisories/577
Low             Prototype Pollution
Package         lodash
Patched in      >=4.17.5
Dependency of   gulp-jshint [dev]
Path            gulp-jshint > jshint > lodash
More info       https://nodesecurity.io/advisories/577
Low             Prototype Pollution
Package         lodash
Patched in      >=4.17.5
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-jshint > jshint > lodash
More info       https://nodesecurity.io/advisories/577
Low             Prototype Pollution
Package         lodash
Patched in      >=4.17.5
Dependency of   gulp-jshint [dev]
Path            gulp-jshint > rcloader > lodash
More info       https://nodesecurity.io/advisories/577
Low             Prototype Pollution
Package         lodash
Patched in      >=4.17.5
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-istanbul > lodash
More info       https://nodesecurity.io/advisories/577
Low             Prototype Pollution
Package         lodash
Patched in      >=4.17.5
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-jshint > lodash
More info       https://nodesecurity.io/advisories/577
Low             Prototype Pollution
Package         lodash
Patched in      >=4.17.5
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-jshint > rcloader > lodash
More info       https://nodesecurity.io/advisories/577
Low             Prototype Pollution
Package         lodash
Patched in      >=4.17.5
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-load-plugins > findup-sync > lodash
More info       https://nodesecurity.io/advisories/577
Low             Prototype Pollution
Package         lodash
Patched in      >=4.17.5
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-help > lodash
More info       https://nodesecurity.io/advisories/577
High            Regular Expression Denial of Service
Package         fresh
Patched in      >= 0.5.2
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > fresh
More info       https://nodesecurity.io/advisories/526
High            Regular Expression Denial of Service
Package         fresh
Patched in      >= 0.5.2
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > serve-favicon > fresh
More info       https://nodesecurity.io/advisories/526
High            Regular Expression Denial of Service
Package         fresh
Patched in      >= 0.5.2
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > serve-static > send > fresh
More info       https://nodesecurity.io/advisories/526
High            Regular Expression Denial of Service
Package         negotiator
Patched in      >= 0.6.1
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > compression > accepts > negotiator
More info       https://nodesecurity.io/advisories/106
High            Regular Expression Denial of Service
Package         negotiator
Patched in      >= 0.6.1
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > serve-index > accepts > negotiator
More info       https://nodesecurity.io/advisories/106
High            Cross-Site Scripting
Package         handlebars
Patched in      >=4.0.0
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-istanbul > istanbul > handlebars
More info       https://nodesecurity.io/advisories/61
Low             Incorrect Handling of Non-Boolean Comparisons During
Minification
Package         uglify-js
Patched in      >= 2.4.24
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-istanbul > istanbul > handlebars >
uglify-js
More info       https://nodesecurity.io/advisories/39
Low             Incorrect Handling of Non-Boolean Comparisons During
Minification
Package         uglify-js
Patched in      >= 2.4.24
Dependency of   karma [dev]
Path            karma > socket.io > socket.io-client > uglify-js
More info       https://nodesecurity.io/advisories/39
Low             Regular Expression Denial of Service
Package         uglify-js
Patched in      >=2.6.0
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-istanbul > istanbul > handlebars >
uglify-js
More info       https://nodesecurity.io/advisories/48
Low             Regular Expression Denial of Service
Package         uglify-js
Patched in      >=2.6.0
Dependency of   karma [dev]
Path            karma > socket.io > socket.io-client > uglify-js
More info       https://nodesecurity.io/advisories/48
Moderate        Regular Expression Denial of Service
Package         ms
Patched in      >0.7.0
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-mocha > mocha > debug > ms
More info       https://nodesecurity.io/advisories/46
Moderate        Regular Expression Denial of Service
Package         mime
Patched in      >= 1.4.1 < 2.0.0 || >= 2.0.3
Dependency of   gulp-connect [dev]
Path            gulp-connect > connect > serve-static > send > mime
More info       https://nodesecurity.io/advisories/535
Low             Regular Expression Denial of Service
Package         debug
Patched in      >= 2.6.9 < 3.0.0 || >= 3.1.0
Dependency of   gulp-test [dev]
Path            gulp-test > gulp-mocha > mocha > debug
More info       https://nodesecurity.io/advisories/534
[!] 99 vulnerabilities found - Packages audited: 18775 (18032 dev, 8557 optional)
Severity: 42 Low | 23 Moderate | 32 High | 2 Critical
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/project-sunbird/sunbird-portal/issues/511, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGVqk9OTbpP-BSf4deDCoYB0JRQjlyeks5ty_rZgaJpZM4UBBjk
.


Platform+Flow: Add locale API and nodes V2.

Changes since V1:

Do not apply locales at startup.
Fail gracefully during the startup if /etc/locale.conf does not exist.
The node platform/locale now have ports to apply the locale values.

Closing in favor of #1190


PAR-158: Failed rollback buyer NFT when seller failed to accept the trade

Context: https://explorer.mainnet.near.org/transactions/EU8XA7QJ3mzjZJNN6Qie5YTqJZfAZWazhoAU3doRWRDA
NFT wasn't send back to the original owner after failed second transfer


Segmentation pipeline ends the process immediately.

Hello, dear ecker-lab.
I try to run segmentation pipeline.
'python tools/pipeline/pipeline.py --config configs/pipeline/pipeline.yaml'
But when generating tiles step start, it ends the process immediately.

It's so confuse. What I do wrong.

It looks like you are running the pipeline on your personal computer, which might not have enough RAM to support the running of the pipeline. I suggest running the pipeline on a smaller plot or using a compute cluster.

I think, I have enough RAM and storage for running the pipeline.

Without any error messages, I cannot assess where the error might come from. We also never ran the pipeline on a Windows machine. So we do not have any experience there as well. All I can recommend is to debug it yourself. According to your log, the error happens somewhere in the "generate_tiles" function here below "logger.info('voxelizing forest...')"

Because it not have any error messages, it make me so confuse. what's wrong with that. Thank you for your advice. your project is so incredible. It might helpful in my project.

I switched from running the code on Windows machine to using Jupyter Notebook, where I discovered the issue. The error message 'The kernel for ipynb appears to have died' was occurring because Open3D wasn't working properly. I've now fixed the problem.