[Snyk] Fix for 20 vulnerabilities

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

src/frontend/package.json
src/frontend/package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

696/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS) SNYK-JS-ANSIREGEX-1583908
Yes
Proof of Concept

786/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 9.3
Incomplete List of Disallowed Inputs SNYK-JS-BABELTRAVERSE-5962462
Yes
Proof of Concept

586/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-GLOBPARENT-1016905
Yes
Proof of Concept

586/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-HTMLMINIFIER-3091181
Yes
Proof of Concept

703/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 6.2
Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116
Yes
Proof of Concept

681/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.2
Command Injection SNYK-JS-LODASHTEMPLATE-1088054
Yes
Proof of Concept

479/1000  Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-MARKED-174116
No
No Known Exploit

586/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-MARKED-2342073
Yes
Proof of Concept

586/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-MARKED-2342082
Yes
Proof of Concept

479/1000  Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-MARKED-451540
No
No Known Exploit

520/1000  Why? Has a fix available, CVSS 5.9
Regular Expression Denial of Service (ReDoS) SNYK-JS-MARKED-584281
Yes
No Known Exploit

696/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS) SNYK-JS-NTHCHECK-1586032
No
Proof of Concept

479/1000  Why? Has a fix available, CVSS 5.3
Improper Input Validation SNYK-JS-POSTCSS-5926692
Yes
No Known Exploit

589/1000  Why? Has a fix available, CVSS 7.5
Prototype Pollution SNYK-JS-UNSETVALUE-2400660
Yes
No Known Exploit

654/1000  Why? Has a fix available, CVSS 8.8
Cross-site Scripting (XSS) npm:marked:20150520
No
No Known Exploit

589/1000  Why? Has a fix available, CVSS 7.5
Cross-site Scripting (XSS) npm:marked:20170112
No
No Known Exploit

589/1000  Why? Has a fix available, CVSS 7.5
Cross-site Scripting (XSS) npm:marked:20170815
No
No Known Exploit

454/1000  Why? Has a fix available, CVSS 4.8
Cross-site Scripting (XSS) npm:marked:20170815-1
No
No Known Exploit

589/1000  Why? Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS) npm:marked:20170907
No
No Known Exploit

696/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS) npm:marked:20180225
No
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: marked
    The new version differs by 250 commits.

ae01170 chore(release): 4.0.10 [skip ci]
fceda57 🗜 build [skip ci]
8f80657 fix(security): fix redos vulnerabilities
c4a3ccd Merge pull request from GHSA-rrrm-qjm4-v8hf
d7212a6 chore(deps-dev): Bump jasmine from 4.0.0 to 4.0.1 (#2352)
5a84db5 chore(deps-dev): Bump rollup from 2.62.0 to 2.63.0 (#2350)
2bc67a5 chore(deps-dev): Bump markdown-it from 12.3.0 to 12.3.2 (#2351)
98996b8 chore(deps-dev): Bump @ babel/preset-env from 7.16.5 to 7.16.7 (#2353)
ebc2c95 chore(deps-dev): Bump highlight.js from 11.3.1 to 11.4.0 (#2354)
e5171a9 chore(release): 4.0.9 [skip ci]
41990a5 🗜 build [skip ci]
a9696e2 fix: retain line breaks in tokens properly (#2341)
6aacd13 chore(deps-dev): Bump jasmine from 3.10.0 to 4.0.0 (#2343)
55e5df9 chore(deps-dev): Bump @ babel/core from 7.16.5 to 7.16.7 (#2344)
4f4cab4 chore(deps-dev): Bump eslint-plugin-import from 2.25.3 to 2.25.4 (#2345)
97ea9f2 chore(deps-dev): Bump eslint from 8.5.0 to 8.6.0 (#2346)
4c3b853 chore(deps-dev): Bump rollup-plugin-license from 2.6.0 to 2.6.1 (#2347)
9396896 chore(deps-dev): Bump rollup from 2.61.1 to 2.62.0 (#2338)
103a56c chore(deps-dev): Bump @ babel/preset-env from 7.16.4 to 7.16.5 (#2333)
be771c9 chore(deps-dev): Bump eslint from 8.4.1 to 8.5.0 (#2334)
67d5a65 chore(deps-dev): Bump @ babel/core from 7.16.0 to 7.16.5 (#2335)
991493a chore(deps-dev): Bump eslint-plugin-promise from 5.2.0 to 6.0.0 (#2336)
59375fb chore(release): 4.0.8 [skip ci]
4734c82 🗜 build [skip ci]

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Cross-site Scripting (XSS)
🦉 Improper Input Validation
🦉 More lessons are available in Snyk Learn

fixed


Refactor notifications

Put them all into a class so we don't repeat code

part of #262, so it's already happening


Preview position to be centered

I can not reproduce this behavior on my screen.
Are you sure that your repository was up to date when your are test?


Draft: [ENH] Make embeddings functions optional in js client

The current problem with optional embeddings functions in the js client
Currently when you do import { ChromaClient } from 'chromadb'; you will load the code of all embeddings functions which at least would throw errors or warnings when you don't have installed the dependencies of the embedding functions.
In some cases this will also lead to additional issues because of loading code you don't want to load.
currently

'chromadb' exports

ChromaClient
Collection
IEmbeddingFunction
OpenAIEmbeddingFunction
CohereEmbeddingFunction
WebAIEmbeddingFunction
TransformersEmbeddingFunction

with this change

'chromadb' exports

ChromaClient
Collection

'chromadb/openai' exports

OpenAIEmbeddingFunction

'chromadb/cohere' exports

CohereEmbeddingFunction

'chromadb/webai' exports

WebAIEmbeddingFunction

'chromadb/transformers' exports

TransformersEmbeddingFunction

So when you require/import anything from chromadb, you will actually only load the chromadb code into your js project. And only if you are importing something from 'chromadb/*' you will import the embeddings function.
Description of changes

Improvements & Bug fixes

define js embedding functions as optional and not reference it in the main chromadb client. Instead one would have to explicit import them from e.g. chromadb/openai.

this resolves problems we try to workaround with #956
instead of the workaround, in this pr we'll resolve the problem while introducing a breaking change

typescript support included import { OpenAIEmbeddingFunction } from 'chromadb/openai'; will not throw any ts errors and type definitions are loaded for the embedding functions.

I had to add a gulp script to make the import work and make typescript transpilers understand that there are sub-packages

I added the README.md and LICENCE to the package build and removed the src folder

Test plan
I've tested it locally using this project: https://github.com/jeffchuber/nextjs-chroma

@perzeuss to clarify...
The current behavior is this:

By moving the imports for embedding functions into their own path - this goes away.
This would be a (small) breaking change.
Can you help me understand the role of build.js and gulpfile.js here?
thanks!

@perzeuss to clarify...
The current behavior is this:
By moving the imports for embedding functions into their own path - this goes away.
This would be a (small) breaking change.
Can you help me understand the role of build.js and gulpfile.js here?
thanks!

Sure! To tell typescript that e.g. the module chromadb/openai exists, we need to define a type definition /openai.d.ts for that and to support all environments even those who don't understand the exports syntax, we also place a file e.g. /openai.js.
 gulpfile.js contains scripts to generate these files.
build.js will build cjs and esm builds, and run some scripts to generate:

the package.exports entries dynamically based on the folders in src/embeddings (each folder gets an own entry)
the package.files includes all generated files
the root files e.g. /openai.js and /openai.d.ts to support the sub-packages

@perzeuss to clarify...
The current behavior is this:
By moving the imports for embedding functions into their own path - this goes away.

Yes and it prevents further problems like here #953

I verified this works! I am not going to take a fine-tooth comb pass through it.

thanks @visheratin ! cc @perzeuss

This looks correct! I gather you've run the code to just make sure it outputs numbers?

Actually, I haven't had the chance to test it yet. I don't even have a cohere api key to test it.

Is there a workaround for this @jeffchuber @perzeuss ? Vercel is rejecting my builds.

Is there a workaround for this @jeffchuber @perzeuss ? Vercel is rejecting my builds.

What do you mean with workaround?

Is there a workaround for this @jeffchuber @perzeuss ? Vercel is rejecting my builds.

What do you mean with workaround?

These are the errors that show up for me during deployment on Vercel while using import { ChromaClient } from chromadb.
https://jmp.sh/MM2JSJ3Z
I believe this PR will fix these errors however what's a good workaround until this is merged and built as a package? Any suggestions?

I think we've closed all these issues for now.


How to start the dbeaver with params

Hi expert,

Command line parameters might be passed directly to dbeaver[.exe] executable

How can i pass the params, can you give an example?

In Windows you can also use dbeaver-cli.exe executable (it does not spawn a new window so you can see the output messages).
Please also share where i can find the dbeaver-cli.exe , it is better to give a example also

Also, you can add parameters in the dbeaver.ini configuration file - in the beginning of the file and each parameter on its own line.
It is very appreciated to give an example also

Can you also share where the code to load the params for the first and the third way?

Hello @nilawafer,
This feature will be fixed within #14284 in DBeaver 21.2.4.


[E] [PayoutManager] [eth1] Payment processing failed System.InvalidOperationException: This NpgsqlTransaction has completed; it is no longer usable.

For now, I can mine the block in Ethereum Ropsten Network, but when the miningcore execute the PPLNS payment process for the miners, it can't send ether to miner address, always shows the ERROR below:

I use geth --ropsten --datadir=/www/data --snapshot=false --cache=21000 --maxpeers=250 --txpool.globalslots=1000 --http --http.port=8545 --http.api=eth,net,web3,miner -ws --ws.port=8546 --ws.api=eth,net,web3,miner --keystore='/www/.ethereum/keystore' --unlock='0xDD1de78b63dE187304E709bE4A75842700bEd940' --password='/www/password' --allow-insecure-unlock --miner.etherbase='0xDD1de78b63dE187304E709bE4A75842700bEd940' --mine --miner.threads=0 to start the geth, and use the following config.json in miningcore:
{
"logging": {
"level": "info",
"enableConsoleLog": true,
"enableConsoleColors": true,
"logFile": "",
"logBaseDirectory": "",
"perPoolLogFile": false
},
"banning": {
"manager": "Integrated",
"banOnJunkReceive": true,
"banOnInvalidShares": false
},
"notifications": {
"enabled": false,
"email": {
"host": "smtp.example.com",
"port": 587,
"user": "user",
"password": "password",
"fromAddress"<EMAIL_ADDRESS>"fromName": "support"
},
"admin": {
"enabled": false,
"emailAddress"<EMAIL_ADDRESS>"notifyBlockFound": true
}
},
"persistence": {
"postgres": {
"host": "<IP_ADDRESS>",
"port": 5432,
"user": "miningcore",
"password": "some-secure-password",
"database": "miningcore"
}
},
"paymentProcessing": {
"enabled": true,
"interval": 100,
"shareRecoveryFile": "recovered-shares.txt"
},
"api": {
"enabled": true,
"listenAddress": "<IP_ADDRESS>",
"port": 4000,
"metricsIpWhitelist": [
"<IP_ADDRESS>"
],
"rateLimiting": {
"disabled": true
}
},
"pools": [
{
"id": "eth1",
"enabled": true,
"coin": "ethereum",
"address": "0xDD1de78b63dE187304E709bE4A75842700bEd940",
"rewardRecipients": [
{
"type": "op",
"address": "0xDD1de78b63dE187304E709bE4A75842700bEd940",
"percentage": 0
}
],
"enableDaemonWebsocketStreaming": false,
"blockRefreshInterval": 50,
"clientConnectionTimeout": 600,
"banning": {
"enabled": true,
"time": 600,
"invalidPercent": 50,
"checkThreshold": 50
},
"ports": {
"8008": {
"listenAddress": "<IP_ADDRESS>",
"difficulty": 3,
"varDiff": {
"minDiff": 3,
"maxDiff": null,
"targetTime": 15,
"retargetTime": 90,
"variancePercent": 30
}
}
},
"daemons": [
{
"host": "<IP_ADDRESS>",
"port": 8545,
"portWs": 8546,
"notifyWorkUrl": "http://<IP_ADDRESS>:8107"
}
],
"paymentProcessing": {
"enabled": true,
"minimumPayment": 0.01,
"payoutScheme": "PPLNS",
"payoutSchemeConfig": {
"factor": 0.5
}
}
}
]
}
@oliverw

Still a thing, see discussion #1103. Maybe reopen this issue @oliverw

Current status of this?

This can happen during payouts when the number of shares to be deleted is so high that the time spent on the deletion of the database records for the shares make this the ambient transaction to hit the timeout.  Possible fix is to increase the commandTimeout property of the postgres configuration in config.json from the default 120 to 300 or 600.

In case you still have the data when this bug occurred, could you check if the last confirmed block was an uncle, and if the height difference between the first pending and last confirmed is less than 50?

Yeah that definitely helped and confirmed my theory.
Unfortunately I'm a bit busy for next weeks but I will test a few things and if it works I'll open a PR.
I think the root cause is how mc tries to determine if a block was included as uncle.

Yeah that definitely helped and confirmed my theory. Unfortunately I'm a bit busy for next weeks but I will test a few things and if it works I'll open a PR.
I think the root cause is how mc tries to determine if a block was included as uncle.

I agree. ETH reward determination is a mess, always been.


Databricks Integration

Not able to integrate databricks with Visual Studio

Hi @HasanthiEV, could you elaborate more on your request?


retrieving the solution values of all variables at once

Hi all,
is there a way of retrieving the values of all variables after having optimized, at once?
I am currently iterating as in
[model.getVars()[i].getLPSol() for i in range(len(model.getVars()))]

Thanks for your quick response! I know model.getVal(x) but i guess there is no iterater free way due to the SCIP code, right?


📊 Update IMF WEO October 2023

Update issue: https://github.com/owid/owid-issues/issues/1266

Hey @pabloarosado, thanks for the help (in advance!)
For now I'm running into this at the meadow step:
2023-11-02 15:39:35,243 - [bugsnag] WARNING - No API key configured, couldn't notify
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/edouard/git/etl/.venv/lib/python3.10/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/Users/edouard/git/etl/.venv/lib/python3.10/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/Users/edouard/git/etl/.venv/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/edouard/git/etl/.venv/lib/python3.10/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/Users/edouard/git/etl/etl/run_python_step.py", line 34, in main
    _import_and_run(path, dest_dir)
  File "/Users/edouard/git/etl/etl/run_python_step.py", line 54, in _import_and_run
    module.run(dest_dir)
  File "/Users/edouard/git/etl/etl/steps/data/meadow/imf/2023-11-02/world_economic_outlook.py", line 80, in run
    tb.underscore()
  File "/Users/edouard/git/etl/.venv/lib/python3.10/site-packages/pandas/core/generic.py", line 5902, in __getattr__
    return object.__getattribute__(self, name)
AttributeError: 'DataFrame' object has no attribute 'underscore'

Most of the code I used there was copied over from the older version (data/meadow/imf/2023-05-02/world_economic_outlook.py) so presumably the DataFrame object I'm using isn't the right one anymore.

Hi @edomt I've converted this PR into a draft, as I understand that it's not ready to be reviewed or merged for now. Let me know if you need help with the remaining steps.

@pabloarosado I've now added the garden and grapher steps :)
A few more questions:

I've run the grapher step (ENV=.env.edouard poetry run etl grapher/imf/2023-11-02/world_economic_outlook --grapher) on my staging server, apparently successfully, but the dataset page show no metadata and no indicator.
In etl-wizard, clicking on "Charts" in the left-hand menu only shows an empty page titled "🧑🍳 Chart revisions baker", and streamlit seems to crash (my terminal shows zsh: segmentation fault  ENV=.env.edouard etl-wizard). Is this what I should be using?

@pabloarosado I've now added the garden and grapher steps :)
A few more questions:

I've run the grapher step (ENV=.env.edouard poetry run etl grapher/imf/2023-11-02/world_economic_outlook --grapher) on my staging server, apparently successfully, but the dataset page show no metadata and no indicator.
In etl-wizard, clicking on "Charts" in the left-hand menu only shows an empty page titled "🧑🍳 Chart revisions baker", and streamlit seems to crash (my terminal shows zsh: segmentation fault  ENV=.env.edouard etl-wizard). Is this what I should be using to transfer the charts from old var id to new var id?

Hi @edomt we have a new option, which is to work on a temporary server created for this specific PR.
Then, you can do the chart revisions on the temporary server that is created for this PR, and once that's finished, you don't have to repeat the revision in live.
The workflow is as follows:

Set the PR to "Ready for review" (feel free to assign me as a reviewer, and I'll do it next week, but on Wednesday at the earliest). I think at that point the server begins to be created (it may take 20-30 minutes).
Execute the chart revision tool on the temporary server:

STAGING=add-imf-weo-october-2023 etl-wizard charts

Assuming the PR was accepted and the chart revision went well, merge the PR.
Sync the charts in the temporary server with production. To do that, open an ssh tunnel to production, and run:

etl-staging-sync stag
ing-site-add-imf-weo-october-2023 .env.live --dry-run

(where .env.live or .env.prod is your .env file with the credentials for production). If the result in your command line looks good, then execute the same command without the --dry-run.
Does that make sense? If you have problems with step 4 I can run that for you.


Fix character overlay spine rotation when moving diagonally

Before:

After:

The character's spine only allows rotation while aiming, so transitioning from the Aiming to ViewDirection rotation mode causes the spine to snap back to a non-rotated state instead of blending with the rest of the animation transition. This is especially apparent when moving at 45 degree angles, as the spine snaps to the pelvis's yaw rotation offset independent of the blend between the two animation states.
By allowing the spine to rotate in any rotation mode besides VelocityDirection, we produce more natural looking transitions after aiming, while maintaining the function of the spine rotating to match the pelvis.
This also allows the user more control over the spine's rotation through the ViewBlock and AllowAiming animation curves because of their new use in UAlsAnimationInstance::RefreshSpineRotation() when the character is not aiming. For example, if the user wants the spine to not rotate back to the pelvis's yaw rotation during an overlay pose, they can set AllowAiming to 1 for the duration of that overlay's pose.

There is a drawback to this fix - the spine continues to follow the camera, so it can "snap" when the player rotates the camera at a very high speed or in slow motion.
I've tried to tackle this issue before, but without success, so I'm not sure about this fix.
https://github.com/Sixze/ALS-Refactored/assets/16257871/1d3794bb-7e1c-45b8-956e-2fdd1a50ab7b

I have reworked the spine rotation logic. It now produces a similar result to this PR, but without causing new issues.
6ed5c89699972cac294ec6fe1b9d6b5cec0c9117


How to get item id when clicked

How i can get item id when click the board's item? thanks

Please read the usage area, found on the first page of this project. There you will find what you are looking for. Cheers,
You'll need to fill in the click function and then interrogate the dom element. And in many cases code the rest.
The Demo also found on the first page of this project, is also a good place to see an example of the click function and interrogating the passed-in dom element. Please note: you'll need to code the item id to be unique.


tree2: DocumentSchema rename

Description
Rename DocumentSchema to TreeSchema.
Breaking Changes
Rename DocumentSchema to TreeSchema.
Rename toDocumentSchema to intoSchema.
Reviewer Guidance
The review process is outlined on this wiki page.

Is it supposed to be intoSchema or toSchema? I would assume the latter - please confirm with Nick/spec.

I specifically asked about "to" vs "into" when we discussed this. I suggested (and used in my origional version of this API) "into" because APIs which finalize/consume an object (and thus the thing the method was call on is no longer usable) are commonly named "into" as a convention and to better capture the semantics. Typically, "to" is used for APIs which do a copying convert, not a consuming conversion. At least how it works in my head.
its hard to search for things like "into" and "to" for examples, especially since consuming style builders are not super common in TypeScript, but at least in rust this pattern is explicitly provided by https://doc.rust-lang.org/std/convert/trait.Into.html (note that the input is owned there, so it consumes)
The name with "into" was what got oked in that discussion. I have now updated the spec to match this.

Is it supposed to be intoSchema or toSchema? I would assume the latter - please confirm with Nick/spec.

I specifically asked about "to" vs "into" when we discussed this. I suggested (and used in my origional version of this API) "into" because APIs which finalize/consume an object (and thus the thing the method was call on is no longer usable) are commonly named "into" as a convention and to better capture the semantics. Typically, "to" is used for APIs which do a copying convert, not a consuming conversion. At least how it works in my head.
its hard to search for things like "into" and "to" for examples, especially since consuming style builders are not super common in TypeScript, but at least in rust this pattern is explicitly provided by https://doc.rust-lang.org/std/convert/trait.Into.html (note that the input is owned there, so it consumes)
The name with "into" was what got oked in that discussion. I have now updated the spec to match this.

That makes sense. I have the same intuition - into sounds less like a copy than to.


Request headers not available in connected callback

In my WebSocketService I'd like to inspect some headers on a new websocket connection. The headers are often incorrectly shown as empty when read from the connected(connection: WebSocketConnection) callback.
I've done some debugging and found out the root cause. The HTTPServerRequest object doesn't strongly retain the headers. Instead, it has a weak reference to a httpParser which contains the headers. The connected callback is called asynchronously here, by which time the httpParser is often released.
My guess is that the WebSocketConnection should retain the httpParser to make sure the data stays alive for the lifetime of the connection. I'm not sure if this is safe to do, though.
In production this bug doesn't happen 100% of the time. It depends on the timing of the two threads. I think this should repro pretty consistently:
func connected(connection: WebSocketConnection) {
   print("Headers usually present here: \(Array(connection.request.headers))")
   sleep(3) // Give time for other thread to release the httpParser
   print("Headers usually empty here: \(Array(connection.request.headers))")
}

Meta-question: Is this the right place to talk about bugs? Or should all bugs go to the main Kitura repo? This bug in particular might need fixes in Kitura-Net, for example.

I have a fix for this pushed in the branch issue_12. It also needs the latest Kitura-net (1.7.3).
This should get merged tomorrow morning.

Thank you! It works great now. I really appreciate the great work you've done with this framework.


Updated translation, grammar, and accentuation errors

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

@viavn Thank you for  creating this PR.  However, since it was created, the underlying document has changed.  Can you please review and resolve the current merge conflicts?  It could be the changes to the underlying document are so significant that your changes are no longer relevant.  If the latter is the case, it might be easier to just close this PR and create a new PR with any changes you still feel are important to make.
If you need any assistance or have questions about resolving the merge conflicts, please reply back or contact someone in the Contributors Room on Gitter.
Thank you.

Hey @RandellDawson . I've just searched on Portuguese dictionary and picked up an article on Google Scholar and finally found an answer.
Yes, it does mean Internet in Portuguese.
Here are links:

[Article] http://www.inf.ufsc.br/~fernando.gauthier/EGC6006/material/Aula 3/Ontologia_Web_semantica Freitas.pdf

[Dictionary] http://michaelis.uol.com.br/busca?r=0&f=0&t=0&palavra=web

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Allows to specify target of a DelayedTask on command line.

First shot at implementing #20: allowing to specify targets and delayed tasks of DelayedTask's on the command line.
This is based on doit 0.27.0, to be able to test it with Nikola's earlytask_impl branch (see https://github.com/getnikola/nikola/pull/1632).

(Sorry it took that long... There were too many other things happening :) )

Hi, thanks for working on this.
I would like to know more about your concrete use-case. For which targets in Nikola you would use this. I am asking this because I am thinking that attaching regexp to identify which targets a task creates might be a better solution.
regexp advantages:

result is always correct, even on first run because a task_dep will be executed
no need to load DelayedTasks that wont be used
cleaner implementation

regexp disavantages:

It might not be possible unambiguosly describe task targets by a regexp

I guess that in real life a regexp should be suitable, so lets check your use-case with Nikola :)
Also related to this is #30 (but about basename instead of target)

Well, there are two main reasons I'd like this feature:

More meta: to make nikola's earlytask_impl branch more compatible with current behavior;

More conrete: I want to be able to tell nikola to build specific targets, which isn't possible in the earlytask_impl branch as all tasks (which specify the targets) are created by delayed task loaders.

I also don't think this collides with regexps, as there's always the choice to choose ".*" as a regexp describing the generated tasks' targets. (And for some tasks, it might not even be possible to specify something more concrete.)
I think regexp support would be nice to have (as task generators which can specify quite clearly which targets they generate don't have to be loaded), but especially for backwards compatbility with older plugins (or in some cases, when it is not possible to say anything more concrete about targets except that they are in output/, for example) this won't help much.

I agree this feature is useful, what I am saying is that regexp is superior in many aspects and its limitations are not very relevant in practice. I forgot to mention another big regexp disavantage: you need to werite the regexp!
For my own Nikola based blog, I guess it would not be hard to make a regexp for each target.

indexes: "/output/index(.*).html"
posts: "/output/posts/(.*).html"
categories: "/output/categories/(.*).html"
archives: "/output/(\d\d\d\d)/(.*).html"

Yes it would affect backward compatibility with plugins but this is also not coming for free...
What makes me unconfortable with this change is that doit might do the right thing or not depending on the state of previous runs. It is very bad for  build-tool when people stop trusting it.

I just implemented https://github.com/pydoit/doit/commit/03f0cf7e1b4b6915c35619ceab367bdda77e8efd to allow specifying a sub-task from a DelayedTask. It is almost the same as what it would take to implement specifying targets (but a bit easier).
The patch itself made it even more clear to me that use of regexp is the right way to go.
I am sorry if you feel that I mislead you to implement a patch that I wont accept, sometime it is hard to
make a call before actually looking at an implementation. Sorry my mistake.

I still don't see what you want to do in case you find two regexs matching a target, or if a delayed task creates a task which name it didn't announce before. Or is that not allowed? (Which would be ways to strict, from my point of view.)

@felixfontein please check if this branch is good enough for you: https://github.com/pydoit/doit/compare/delayed-target-regex?expand=1
Announcing a name is optional. There is no support for 2 regex matching a target (but could be added).

I don't think it is always possible to avoid having not two regexps matching the same target. At least, not with an extreme amount of PITA and (even worse) user interaction. In particular for Nikola, I don't want to force end-users to start writing regexps, and I neither want to reduce Nikola's flexibility of allowing to put things where you want them. So I'm still convinced that the code I wrote (or something else doing something similiar) is needed.

The code could be improved to handle more than one matching regexps.
As I said before the problem with your code is that it doesnt work if the targets intermediates were never built. IMO that would make doit not trustable ... Any other idea ?

But how is that different from when you specify a delayed task on the command line, where the targets also have dependencies which are produced by some other delayed task? What does doit currently do in that situation?


feat(core): [Paypal] Add session_token flow for Paypal sdk

Type of Change

[ ] Bugfix
[X] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Add session_token flow to enable Paypal via Paypal SDK

Accept data in metadata field of the MCA - create call
Return that data in the sessions call
Change payment_experience for paypal via paypal to sdk

Additional Changes

[x] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

#4698
How did you test it?

Checklist

[X] I formatted the code cargo +nightly fmt --all
[X] I addressed lints thrown by cargo clippy
[X] I reviewed the submitted code
[ ] I added unit tests for my changes where possible

Can you add api contracts foe each of the api calls?


Link to library examples using Create React App

I would like to compile a list of React-related libraries whose examples use Create React App for build setup. Redux examples except for the universal and counter-vanilla all use it. React Router 4 examples are all copy-pasteable into App.js generated with Create React App.
Please help me find more such examples!

Update: help wanted porting libraries! See the instructions below.

"Boilerplate" examples that use CRA for build setup and showcase how to do something in React are welcome too! Please let me know if you find or create any.

Does this count? https://github.com/zebapy/create-react-app-parse-redux

I'll be creating some examples for https://github.com/smalldots/smalldots using CRA soon, but it's not ready yet :(

This is where I first cam across CRA:
https://github.com/marmelab/admin-on-rest/blob/master/docs/Tutorial.md

This might fall under boilerplate example - component-template. It's built with CRA to help enable folks to publish components built on top of reactstrap or react components in general. Planning to add a getting started guide to reactstrap that uses CRA as well. Happy to hear feedback on this use or abuse of CRA : ]

https://github.com/vinpac/base-kit
It comes with redux, react-router 4, basic components ( e.g. Dropdown, Modal ), sass support and a configurable and awesome style library based on bootstrap 4.
Example of use: https://vinpac.github.io/base-kit/

Here is good list of popular React libraries. For those that offer components and have examples with custom build setups and don’t need server rendering or exotic features, let’s send PRs that use Create React App for example code? If the authors don’t them, let’s also collect feedback in this thread.
Please comment if you’d like to help out with this!

vjeux/most-npm-installed-projects
Created 9 months ago
Can we ask @vjeux to update the statistics? For example, there is no aphrodite, however there are some examples, that can be moved to CRA.

Yeah, this is the only list I found so far but it shouldn’t be hard to compile a better one (or use “awesome” and “ecosystem” lists). You’re welcome to add more lists in comments, and I’ll put them into the post.

I would love to see a Visual Studio Code Extension for react-create-app that also generates required vscode configuration. A sample configuration can be found in this boilerplate project: https://github.com/skolmer/react-hot-boilerplate-vscode
Details about vscode extensions https://code.visualstudio.com/docs/extensions/overview
If someone is interested to cooperate on an extension please let me know!

@gaearon I'll take a look at updating react-loader

As @gaearon said, this is a pretty good list too for react tools: awesome

@gaearon I'll take react-intl

I spent an entire day getting the information from https://react.parts/ and it was painful. I'd love if we could ask the authors of that website for the information as they already have it in their db rather than trying to crawl it again.

What's the recommended process for setting up an examples folder. Should you comment the dist code from the libraries build task then reference this in the examples?

Not sure what you mean, could you clarify? You can look at Redux examples folder to see how CRA can be used in this context.

My thinking is if the library has an examples folder e.g.
package.json
src/
--- library.js
dist/
--- libaray.min.js
examples/
--- (CRA) has the create app with some examples of the library in use

inside the examples and importing the library should this be from the dist version or from npm?
Sorry is this is still vauge. Is there a link to the examples in Redux where CRA is being used?

inside the examples and importing the library should this be from the dist version or from npm?

I think importing from npm is the best way. (Author may not agree, but this is why I’m saying we collect feedback.) The reason I prefer importing from npm is because people often try to copy-paste examples as top-level folders and try to play with them, and importing library source doesn’t really work in that scenario.

@gaearon I'll take belle

Please see my review of this PR: https://github.com/yahoo/react-intl/pull/669#pullrequestreview-1746957. I think it’s important we don’t add unnecessary files, preserve original intention (like important <script>s and <title>), don’t appear too spammy, and, most importantly, clarify why we are sending PRs in the first place. You can use my comment there as a reference.

Hey, I'm running into an issue.

belle is using :: operator of ES2016. CRA seems to not like it and according to this issue #167, we can't configure .babelrc yet or we need to run eject. Is it still the case?
Ejecting CRA won't follow the point of this thread to make it easy for beginners to understand examples right? So is there another solution or should we not consider updating belle example anymore @gaearon?

belle is using :: operator of ES2016

:: is not a part of ES2016. It is a stage 0 proposal that might never make it into the language. Moreover, it is not the best for performance reasons, as it binds a new function on every render().
I suggest using stage 2 Class Properties proposal instead. It is supported by Create React App because we use it at Facebook, and if its syntax changes, we’ll make sure to release a codemod to automatically migrate the code for Create React App users.
Here is how equivalent code looks like with Class Properties:
  _renderDay(day) {
    const date = day.getDate();
    return (
      <div onMouseDown={this._onMouseDown}>
        🎁{ date }
      </div>
    );
  },

  _onMouseDown = (event) => {
    event.stopPropagation();
  },

If you’re confused about the changes, I removed :: and instead used an arrow in _onMouseDown definition so that it gets autobound.

That was a quick answer, thanks!
Ok I got it but this is a change in a lib component not my example, so it might be a choice of the author of the lib.
Should we still do the change? (It might happen in other components I guess)

As I noted before, I’d recommend making examples use library version from npm: https://github.com/facebookincubator/create-react-app/issues/737#issuecomment-249708654. In this case library components would all be compiled. I don’t know whether it works well for Belle authors, but it’s worth suggesting. It’s always possible to use npm link for local development.

That said DatePickerPlayground.js is definitely in examples folder, not in a library component. This alias makes belle resolve to src so you’d need to add belle explicitly to package.json.

I am going to migrate spectacle-boilerplate.
CRA will dramatically simplify setup there.

 However, in the end I couldn't work out how to refer to my own ES6 source, which resided outside of the create-react-app created src/ dir.
Since one on the main uses (for me, and since this issue invites comments on use cases that might not work) in having an example directory is to develop my library against, importing from npm didn't seem like a great way to go (I can see in other cases that might be ok). I want to build a new example, or modify and existing one, get my code working, and only then publish to npm.
So instead I made my whole project a CRA project, with its src/ dir, then under that my own source directory called components/ and another directory called examples/. This worked, but I'm not super excited about the structure.

I believe I mentioned this in a comment before: https://github.com/facebookincubator/create-react-app/issues/737#issuecomment-249708654. I also used to link examples to the source. However I've stopped doing it now because of all the people who try to run them as standalone apps and who can't figure out why configuration breaks once you extract the example into a standalone folder outside the project. So these days I don't use webpack config for that, and instead use npm link for local development of examples. The downside is that I have to rebuild my library/component to refresh the example. Depending on the project, this may or may not be an acceptable tradeoff, but that's the only option CRA allows right now.

@gaearon yes, I read that comment, but from a library author's perspective, I'm explaining why that isn't a workable solution. At least for me. But you clearly understand the use case and the downside, so my work is done here.

@gaearon I'll take react-countup

@gaearon What about web apps created with create-react-app?

@gaearon I'm getting a lot of warnings with belle. CRA is using react 15.3.2 and belle 15.0.0-rc.2. The author blocked the version in the packages.json ("react": "=15.0.0-rc.2").
Examples with CRA are running fine though.
My question is, should I fixed all the warnings in this PR? Or we consider this is not related to this PR and I create another issue saying belle should update its react version?
For info, these are the warnings I get:

Unknown prop
You are manually calling a React.PropTypes validation function

Or we consider this is not related to this PR and I create another issue saying belle should update its react version?

Updating React should be a separate PR but I understand it might be a large undertaking. I’m sure Belle users would appreciate it though!

@tbillington That would be cool too!

@gaearon I push a PR for react-datalist too

@gaearon I'll take a look at react-motion

@gaearon I'll take a look at react-google-login-component

@gayancharith thank you for the PR! You think you can make one for the react-facebook-login-component?

@kennetpostigo sure I will

For anyone who ends up here an looking for a good React library starting point that uses create-react-app for an example, check out react-modern-library-boilerplate.


Disable version check for engine project

Describe your changes
Added PLOOMBER_VERSION_CHECK_DISABLED=true under jobs: post_create_environment: in .readthedocs.yml
Issue number
Closes https://github.com/ploomber/contributing/issues/26
Checklist before requesting a review

[ ] Performed a self-review of my code
[ ] Formatted my code with pkgmt format
[ ] Added tests (when necessary).
[ ] Added docstring documentation and update the changelog (when needed)

:books: Documentation preview :books:: https://ploomber-engine--79.org.readthedocs.build/en/79/

readthedocs outputs None

alright, so that didn't work.
let's try this in the pre build step:
- mkdir -p $HOME/.ploomber/stats/
- echo 'version_check_enabled: false' >> $HOME/.ploomber/stats/config.yaml

then in the test notebook
!cat ~/.ploomber/stats/config.yaml


Fixed spelling of OUTPUT

I know this is a late response back, but:
Thanks a lot for the help! I hadn't noticed I made that grammar mistake and will keep on the lookout for more...


Any method to add clickable link to label?

Hi,
Thanks for this awesome project.
I want to add a clickable link to labelFileProcessingComplete for my users take some action on succeed uploading.
e.g. "Upload succeed. Go to view data"
But it seems that the HTML is escaped in the label.
Any method or planned feature for this?
Regards.

No feature planned for this, I'd advise to hide FilePond or show the message above the drop area instead of in the file itself where space is limited.

No feature planned for this, I'd advise to hide FilePond or show the message above the drop area instead of in the file itself where space is limited.

Got it. Thanks.


Downloaded PDF incomplete

The downloadable PDF is incomplete.  It generates a 506 page document but pages after 224 are all blank.
This is in the midst of the Workload solutions and scenarios -> Administration and migration -> Tenant management -> Step 2. Optimal Networking   section.

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

ID: 5603021e-457e-dfca-5f5c-6ab09be9c9b0
Version Independent ID: 0f06f7a0-89a4-297a-cfe0-2548f95dbcd9
Content: Microsoft 365 Enterprise architecture design principles
Content Source: microsoft-365/solutions/design-principles.md
Product: microsoft-365-enterprise
GitHub Login: @samanro
Microsoft Alias: samanro

@samanro Please help us in resolving this issue. Thanks

@dstrome , do you know if this issue would be with the platform? How do we troubleshoot PDF downloads from the library?

@traya1 - please take a look at what's going on with the PDF generation for this docset.

Can do

Hi @bholzmmc,
Can you try accessing the downloadable PDF on your end again? I ran a manual PDF generation and I now see no issues with the PDF, on my end, but what to confirm if the issue is resolved on your end.
I'm still looking into what may have caused the issue in the first place.
Thanks!

Looks fine now.
You can close the Issue.
Brian
From: Thomas Raya @.>
Sent: Wednesday, February 23, 2022 1:18 PM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Holzman, Brian @.>; Author @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Downloaded PDF incomplete (Issue #7755)
Hi @bholzmmchttps://github.com/bholzmmc,
Can you try accessing the downloadable PDF on your end again? I ran a manual PDF generation and I now see no issues with the PDF, on my end, but what to confirm if the issue is resolved on your end.
I'm still looking into what may have caused the issue in the first place.
Thanks!
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/7755#issuecomment-1049073720, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI4UQ5Z5LTZ2ESKWMDIHEE3U4UQFPANCNFSM5OZAG7MQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

This e-mail, including any attachments that accompany it, may contain
information that is confidential or privileged. This e-mail is
intended solely for the use of the individual(s) to whom it was intended to be
addressed. If you have received this e-mail and are not an intended recipient,
any disclosure, distribution, copying or other use or
retention of this email or information contained within it are prohibited.
If you have received this email in error, please immediately
reply to the sender via e-mail and also permanently
delete all copies of the original message together with any of its attachments
from your computer or device.


optimize: diff zero address(for mint) with dead address(for burn)

if we use zero address as mint address and burn address, we can't be know how many tokens are burned in scan platform. For users, this part of the information is lost

Please submit issues or PRs to OpenZeppelin/openzeppelin-contracts instead of here. Additionally, please review the contribution guidelines, in particular:

Any non-trivial code contribution must be first discussed with the maintainers in an issue


xtokens weights

Xtokens extrinsics weight is determined like this: https://github.com/open-web3-stack/open-runtime-module-library/blob/19afb58a300faac6ceb0e6e4e341859282897c53/xtokens/src/lib.rs#L214-L215
Where the weight pretty much boils down to the weight of the equivalent xcm message: https://github.com/open-web3-stack/open-runtime-module-library/blob/19afb58a300faac6ceb0e6e4e341859282897c53/xtokens/src/lib.rs#L860-L877
Wouldn't this underestimate the weight, since it doesn't account for a bunch of logic that constructs the actual message?

Yeah we need some improvement on this.


Add simplecov.coverageDirectory config property to allow coverage directory to be configured

Add new config property that defaults to existing hardcoded 'coverage' value. Fixes #6.
I've tested this by manually building and installing the extension with vsce package and this appears to work for both the default value (if I move my coverage folder to coverage/), and custom values (if I configure simplecov.coverageDirectory to .coverage and move my coverage folder there).
This is my first time touching a VSCode extension codebase, please let me know if I've done anything silly 🙏

Confirmed to work for me locally as well, thanks for adding this! I'll update the README and publish a new release and report back.


question about replica = movedReplica in moveReplicasViaGTID

https://github.com/openark/orchestrator/blob/855e930e89c0cf7934a4bd05281cc010c9cde589/go/inst/instance_topology.go#L692-L695
"if replicaErr != nil && movedReplica != nil {" seems like should be
"if replicaErr == nil && movedReplica != nil {" ?
what's the original thought here?
cc @yangeagle

After moveInstanceBelowViaGTID(replica, other) , movedReplica contains the lastest infomation about the instance replica.

The condition if replicaErr != nil && movedReplica != nil {
means:   update replica only if an error occured.

moveInstanceBelowViaGTID() called by relocateReplicasInternal(),
and then relocateReplicasInternal() call itself under some condition:
https://github.com/openark/orchestrator/blob/5126b849ae4f655e1cbe0fbddfa0d7299674f712/go/inst/instance_topology.go#L2738-L2750

Sum up, I guess the purpose is:  using the lastest information to try again.

@yangeagle thx got it


AndroidTV app tunnel listing forces the selection to the last (bottom) profile

Great app for the AndroidTV! The main functionality with split tunneling works great. The only issue I am having is when pressing the up and down buttons on my Chromecast with GoogleTV remote on the Home (Tunnel listing) screen. No matter how many times I press up the selection jumps to the last tunnel listing. I have about 5 tunnels added in and can only turn on the last one.

Thank you for the detailed explanation of the issue! I'll look into this.

@tonyhardcode This fix is now available on Google Play. Subtle difference in behavior is you now need to click once when hovering over a tunnel to access the controls/buttons, but you should be able to reach all tunnel controls now. Let me know if anything isn't working as desired! Thank you!

This issue seems to have come back up again. I'm on version 3.4.6


Doesn't work with Backhand mod

Main hand:

Backhand:

it DOES work with battlegear, but it doesn't work with backhand like you claim in the description

oh you know what, my issue might be related to this, I do use backhand + atomicstryker dynamic light

oh you know what, my issue might be related to this, I do use backhand + atomicstryker dynamic light

yo, the new version of angelica dynamic lights supports backhand and battlegear as of today. you'll have to build it yourself tho, or i can send a jar

What version of Backhand you two uses?

The guy,c0508383,moved mods.battlegear2.api.core.InventoryPlayerBattle to xonin.backhand.api.core.InventoryPlayerBackhand in newer version so old code doesnot work.

Every fork of Battlegear2 I konw renamed their package/class/method name.Not a big problem but annoying.

I will fix it later.


Error while pushinfg

Hello,
I've been using drive for quite a while.
lately I'm encountering the following error while running my back up script:
`Get https://www.googleapis.com/drive/v2/files?alt=json&q="root"+in+parents+and+title+%3D+".config"+and+trashed%3Dfalse: oauth2: cannot fetch token: 400 Bad Request
Response: {
"error" : "invalid_grant"
}
Get https://www.googleapis.com/drive/v2/about?alt=json: oauth2: cannot fetch token: 400 Bad Request
Response: {   "error" : "invalid_grant" }
`

Hello there @AmitLevin, thank you for filing the issue and welcome to drive!
For starters would you mind telling me your drive version?
Did you perhaps revoke OAuth access from your account?
If so, you can always re-initialize it by running
$ drive init .

at the root of your drive's parent directory and follow the steps printed out.

Thank you for the fast response!
Re-initing solved it.
I was working on my backup script the other day and ran:
drive init .
On another directory.
Any way it works again.

Aye aye, I'll close the issue then. Please reopen if it persists.


DataPlugin should set stackPointers to false

Describe the bug
When setting the DataType via ChooseDataTypeAction (Data->Choose Data Type, or 'T'), the stackPointers value passed to CreateDataCmd() in DataPlugin.createDataAtLocation() is true.  I think that this leads to unexpected behavior and would be more predictable if it was set to false.
To Reproduce
Existing DataType is "pointer".
If I decide that it isn't really a pointer, but should be an int instead, I go to Data->Choose Data Type, type in "int", click OK, and the result is "int *".
Even if I decide to refine it to be a pointer to an int, so I enter "int *", I get "int **" instead.
If I discover that this pointer is actually a member of a structure that starts at that address, select out 12 bytes for the structure to sit in, then choose the datatype to be my 12-byte structure, I end up with three pointers to my structure.
Expected behavior
When I specify the datatype I want there, then I would expect that to be the datatype created.  It seems unexpected to get a pointer to the chosen DataType instead.
Environment (please complete the following information):
This is in Ghidra 10.1.5, but it has been a longstanding behavior.
Additional context
If there is a reason why the existing behavior is useful in some way, then perhaps a tool option could be used to set the behavior.

I did identify an error when choosing a datatype to apply on a selection (DataPlugin.createDataForSelection when instantiating CreateDataBackgroundCmd), however I do not see an issue for the createDataAtLocation case which does forward stackPointers param passed from ChooseDataTypeAction.  There are other cases (e.g., drag-n-drop) which do set stackPointers=true.


Implement tabs for program list.

Right now, both the HexGenerator and the serial programs assume Sword/Shield and put everything into a single list. This isn't scalable once the new games arrive.
Extend the UI to add tabs so that each game/category gets its own tab.

https://github.com/PokemonAutomation/Arduino-Source/commit/68e882e6e1f7295d0e1663cfcfa28b60dcacaae6


Sonar rebrand updates

Updates to icon and brand named to align with Sonar rebrand.

@microsoft-github-policy-service agree [company="{SonarSource}"]
I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company=SonarSource

@microsoft-github-policy-service agree company=SonarSource


Remark on Documentation Notes for  "PostProcessing.nodal_displacement(...)" and "PostProcessing.nodal_component_stress(...)" and maybe others?

Description of the modifications
Dear pyMAPDL-Team,
I came upon the following issue you might want to look into:
On the Documentation pages of the commands: "PostProcessing.nodal_displacement(...)" and "PostProcessing.nodal_component_stress(...)" it says in the "Notes" section:
"This command always returns all nodal displacements regardless of if the nodes are selected or not."
After (the solution of a static analysis and) the reselection of a subset of nodes both commands gave me a list with only the nodal displacements/component stresses of the selected nodes. (see code below)
I find this (consider node selection) more useful than the commands always returning all displacements/stresses, but it is in contrary to the current Notes on the documentation pages.
Thank you
Sven
Links to the documentation pages:
https://mapdl.docs.pyansys.com/version/0.67/api/_autosummary/ansys.mapdl.core.post.PostProcessing.nodal_displacement.html
https://mapdl.docs.pyansys.com/version/0.67/api/_autosummary/ansys.mapdl.core.post.PostProcessing.nodal_component_stress.html
Useful links and references

        test = mapdl.post_processing.nodal_component_stress('x').tolist()   # len() = 2503

        print(mapdl.esel("all"))
        print(mapdl.nsle("R", "corner"))    # Element: SHELL281

        test2 = mapdl.post_processing.nodal_component_stress('x').tolist()  # len() = 691

        sel = mapdl.post_processing.selected_nodes.tolist()                 # len() = 2503   True if node is selected.
        sptest = [ x for x in test if sel[test.index(x)] ]                  # len() = 691

        # test2 and sptest are identical, despite Documentation Notes saying the selected nodes do not matter.

Hi @SvenKan !!
Thank you a lot for reporting this! I will have a look and fix the documentation if needed.


Usage with import * from / require

Hi there,
I wanted to do the following with ES6/Babelify + Sassify:
import document from 'globals/document';
import * as stylesheet from './stylesheet.scss';

const cssEl = document.createElement('style');
cssEl.type = 'text/css';
cssEl.innerHTML = stylesheet.toString();
document.head.appendChild(cssEl);

But for some reason I have an [object Object] instead of a CSS string (the content of the transpiled Sass code).
Is there any way to inject code on our own, without relying on auto-inject option?
Thanks.

blah = Object {one: 1, three: Object}
blah.toString() >> "[object Object]"
JSON.stringify(blah) >> "{"one":1,"three":{"foure":2}}"

Actually what works for me is
import style from './style.scss';

const cssEl = document.createElement('style');
cssEl.type = 'text/css';
cssEl.innerHTML = style;
document.head.appendChild(cssEl);


Bumping haskell-language-server versions don't occur automatically

There are periodic releases of the haskell-language-server, for instance, as of the time of writing this issue, v2.8.0 has already been released.
Contrary to other Mason packages, those releases are not detected unless there is a PR for the manual version bump.
Fix this registry's entry for that package so it's able automatically detect and upgrade package's version without relying on a manual PR.

Maybe this could be worked on as soon as @williamboman investigates why CI is failing on #6444?
As for me, I really have no idea why renovate is not bumping this to being with. packages.yaml looks okay.


Fix getclaimbyoutpoint if no claim exists at outpoint

getclaimbyoutpoint will throw an exception if there is no claim attached to txid (claims becomes None and None is not iterable).
Return None if no claim exists at txid

I think the output is supposed to be {"success":False, "error":"something..."} for resolve commands
But not all commands return that consistently so that needs to be fixed though in a different PR.


EKS worker nodes not joining the EKS Cluster

Goal:
I am trying to launch EKS cluster on wavelength.
Issue Description
After creating the cloudformation stack using the template, the worker nodes aren't joining to the created eks stack. I also verified on the aws dashboard that eks cluster didn't have any nodes attached to it and it seemed to have all required permissions.
Reproducing the error:
I launched the cloudformation template using the cli command provided in the readme and was able to successfuly create the cloudformation stacks.
aws cloudformation create-stack \
--stack-name myWavelengthStack \
--template-body <selected-cfn-file> \
--parameters ParameterKey=EnvironmentName,ParameterValue=WavelengthCloudFormation \
--capabilities CAPABILITY_NAMED_IAM

The small modifications I made to the template was to change

Wavelength zone geo to default to us-west-2-wl1-sfo-wlz-1
ParentRegion(1/2)Geo default to us-west-2a/b

I then got the kubeconfig context
aws eks update-kubeconfig --name {my_cluster_name} --kubeconfig <local file>

Then using the aws-auth-cm.yml setup in README, I was able to apply the configmap to the cluster.
At this point, I am able to reach the cluster and the aws-auth config map is applied
$ kubectl get configmaps -n kube-system
NAME                                 DATA   AGE
aws-auth                             1      11h
coredns                              1      12h
cp-vpc-resource-controller           0      12h
eks-certificates-controller          0      12h
extension-apiserver-authentication   6      12h
kube-proxy                           1      12h
kube-proxy-config                    1      12h

Querying the events provides failed scheduling due to no nodes
$ kubectl get events --all-namespaces
NAMESPACE     LAST SEEN   TYPE      REASON             OBJECT                                            MESSAGE
kube-system   2m40s       Warning   FailedScheduling   pod/coredns-5946c5d67c-p9mf8                      no nodes available to schedule pods
kube-system   2m40s       Warning   FailedScheduling   pod/coredns-5946c5d67c-zlrxw                      no nodes available to schedule pods

With no nodes returning:
$ kubectl get nodes
No resources found in default namespace.

As a side note, I am able to launch regular eks instances using eksctl.
The README does mention attaching carrier ips, but I'm not sure how/why this needs to be done and if this is the issue. If this is the issue, is there a way to do it automatically?

For Public Cluster, ECR/EC2 endpoints are Optional but you must manually attach Carrier IP to public-facing instaces

I was also debugging with https://aws.amazon.com/premiumsupport/knowledge-center/eks-worker-nodes-cluster/ and did notice the eks subnets did not have a wavelength zone. I'm not sure if this could be the issue.

Fixed by using the boto3 client to attach to do the association of the carrier ip.
    ##Create ENI
    eni=client.create_network_interface(SubnetId=subnet_id)
    eni_id=eni["NetworkInterface"]["NetworkInterfaceId"]
    print("ENI created..")

    ##Associate IP to ENI
    assoc = client.associate_address(
    AllocationId=ipAddress["AllocationId"],
    NetworkInterfaceId=eni_id,
    )
    print("Association of Carrier IP to ENI complete..")


Does kr8s support a declarative way of updating, akin to kubectl apply

Which project are you requesting an enhancement for?
kr8s
What do you need?
I only see create or patch in the methods, but no way to do something like that's akin to kubectl apply

Never mind :D

I'm curious why you closed this out? Currently we do not support apply() but I definitely want to add it at some point.
I started an implementation in #75 but it has gone stale and I need to revisit it. There is some complexity around client-side and server-side applies which makes this slightly less trivial than implementing a traditional upsert.

Sure it is similar, but the .patch() implementation in kr8s is the same as the kubectl patch implementation. There are some differences between kubectl patch and kubectl apply.

@jacobtomlinson is this something you plan on reviving?

It's on the backlog but I haven't gotten to it yet. It's definitely something we should add.


Update cache-configure.md

The seem to be memory policy available for Enterprise cache too other that just no eviction one. Hence, proposing the changes for review.

@Amrinder-Singh29 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


travis: add 1.9.x instead 1.8 go version

Codecov Report

Merging #826 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #826   +/-   ##
=======================================
  Coverage   45.03%   45.03%
=======================================
  Files          34       34
  Lines        2727     2727
=======================================
  Hits         1228     1228
  Misses       1309     1309
  Partials      190      190

Continue to review full report at Codecov.

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

Please replace 1.9.x with 1.9 since x is not a valid go release number.

@gdbelvin 1.9.x match all 1.9 minor releases.


Document structure fixes

First commit I tried some simple/quick fixes here for overall structure. The manual refs are a problem if you add/change sections and actually lots of the references were already wrong. Automatic section numbering is also broken because the two docs are actually done as subsections. Instead, I enabled permalinks so we can deep-ref any sections, and replaced all manual text references with automatic label/refs.
Second commit re-arranges the fuzzing sections to make more sense, plus some small updates/fixes.

Thank you very much Steffen, this looks great! Merging


feat: scaffold new backend

Context

context of #194

Changes
Updates for the backend package:
Container

we are now using a container to register and resolve bindings;
bindings can be registered as singletons or transient (it will return a new instance every time we are trying to resolve a registered binding);

Structure

controllers and services are now separated
we are using classes to define services and controllers

Auth

switched from JWT to iron-session
iron-session advantages:

is stateless (like JWT) - we can save user information in the cookie without querying the database to retrieve information about the user.
no need to refresh the tokens
the data stored in the cookie is encrypted
password rotation

Tests

we are still using testcontainers along with jest
we use node-mocks-http to mock request and response
tests are isolated - every test suite will now have it's own database (they will not overlap each other)

:muscle::bear:


Permission to copy the schematics and pcb design in KiCAD and publish it.

Hello Angelo,
Thank you very much for sharing this awesome project with the world. I learned a whole lot about synchronous buck converters and mppt, all thanks to your instructable.
I'm wondering if you would find it ok if I would copy your design in KiCAD and put it on Github (with full credits to you of course). I noticed there is no free version of the Proteus PCB Design software. And I would like to mod your design a bit for higher output current (50-60A).
Planning to build a solar boat with 2S5P solar panel configuration which would give a Voc of 100V and a Imp of 50A. The output would be a 48V lead-acid battery bank and a 3 kW electric motor. So while cruising, I'd need around 40A of output current for the motor plus some charging current if the battery is not full.
I intend to copy your schematics and pcb in KiCAD and, if it's ok with you, I'll share both the (copied) original and a version with my modifications on github.
Thanks again for sharing this project!

Hello @Istria1704 , I was just wondering if you ever started work on this. I would like to contribute as well and build off this ref design!

No, but not long after I opened this issue, I came across someone who had already done exactly that (copied it to KiCAD). I'll see if I can find it again later. If I do I'll post the url. It might even be one of the issues here.


fix MMC bug on calculating n_labels

#136

Codecov Report

Merging #137 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #137   +/-   ##
=======================================
  Coverage   89.69%   89.69%
=======================================
  Files          34       34
  Lines        1358     1358
=======================================
  Hits         1218     1218
  Misses        140      140

Impacted Files
Coverage Δ

..._strategies/multilabel/maximum_margin_reduction.py
97.77% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Cache our migration files to improve test-backend startup time.

Right now we are checking if migrations are needed in a slightly inefficient way when running test-backend.   Instead, per Tim's suggestions, we could optimize this by caching the files in zerver/migrations and only performing this check if a file is dirty.
From Tim's comment here:

[manage.py showmigrations], to figure out whether there are new migrations since we last rebuilt the database. I bet we can optimize that significantly by caching e.g. sha1sum /migrations/.py and only doing that check if the content has changed. This could save ~0.5s (out of the 4s on my machine). Definitely worth doing.

To add a few more notes:

The code for doing this check is in zerver/lib/text_fixtures.py, template_database_status and the function it calls, what_to_do_with_migrations.
We already have nice functions like check_file_hash for checking individual files.
We probably just need code to hash-and-compare */migrations/*.py and then return migrations_are_latest if it's the same.

@zulipbot claim


Graalvm support for Bolt for Java

Category

[x] bolt (Bolt for Java)
[ ] bolt-{sub modules} (Bolt for Java - optional modules)
[ ] slack-api-client (Slack API Clients)
[ ] slack-api-model (Slack API Data Models)
[ ] slack-api-*-kotlin-extension (Kotlin Extensions for Slack API Clients)
[ ] slack-app-backend (The primitive layer of Bolt for Java)

Requirements
I have a small POC where I use Quarkus and com.slack.api:bolt:1.22.3.
I have managed to build the project and produce a native executable,
I had to add the following configuration
quarkus.native.additional-build-args=--initialize-at-run-time=com.slack.api.Slack,--initialize-at-run-time=com.slack.api.SlackConfig,--initialize-at-run-time=com.slack.api.scim.SCIMConfig,--initialize-at-run-time=com.slack.api.token_rotation.TokenRotator,--initialize-at-run-time=com.slack.api.audit.AuditConfig,--initialize-at-run-time=com.slack.api.methods.MethodsConfig

in order to achieve it.
However when I try to execute a call to MethodsClient.chatPostMessage I am getting the following error
 ERROR [org.jbo.res.rea.com.cor.AbstractResteasyReactiveContext] (vert.x-eventloop-thread-0) Request failed: com.oracle.svm.core.jdk.UnsupportedFeatureError: Code that was considered unreachable by closed-world analysis was reached.
        at com.oracle.svm.core.util.VMError.unsupportedFeature(VMError.java:89)
        at com.oracle.svm.core.snippets.SnippetRuntime.unsupportedFeature(SnippetRuntime.java:175)
        at java.lang.reflect.Method.invoke(Method.java:568)
        at com.google.gson.internal.UnsafeAllocator$1.newInstance(UnsafeAllocator.java:50)
        at com.google.gson.internal.ConstructorConstructor$16.construct(ConstructorConstructor.java:272)
        at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:211)
        at com.google.gson.Gson.fromJson(Gson.java:991)
        at com.google.gson.Gson.fromJson(Gson.java:956)
        at com.google.gson.Gson.fromJson(Gson.java:905)
        at com.google.gson.Gson.fromJson(Gson.java:876)
        at com.slack.api.methods.impl.MethodsClientImpl.parseJsonResponseAndRunListeners(MethodsClientImpl.java:3239)
        at com.slack.api.methods.impl.MethodsClientImpl.parseJsonResponseAndRunListeners(MethodsClientImpl.java:3226)
        at com.slack.api.methods.impl.TeamIdCache.lambda$lookupOrResolve$0(TeamIdCache.java:44)
        at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1708)
        at com.slack.api.methods.impl.TeamIdCache.lookupOrResolve(TeamIdCache.java:67)
        at com.slack.api.methods.impl.TeamIdCache.lookupOrResolve(TeamIdCache.java:40)
        at com.slack.api.methods.impl.MethodsClientImpl.postFormWithTokenAndParseResponse(MethodsClientImpl.java:3124)
        at com.slack.api.methods.impl.MethodsClientImpl.chatPostMessage(MethodsClientImpl.java:1497)
        at com.slack.api.methods.impl.MethodsClientImpl.chatPostMessage(MethodsClientImpl.java:1502)
        at com.slack.api.methods.BeanConfiguration_ProducerMethod_slackClient_b716f310108cdb64e1cf609cdebc303aa904c176_ClientProxy.chatPostMessage(Unknown Source)
        at com.tymit.ExampleResource.postMessage(ExampleResource.java:27)
        at com.tymit.ExampleResource$quarkusrestinvoker$postMessage_819d25448cb79a900296f7c48403c34ec62c2530.invoke(Unknown Source)
        at org.jboss.resteasy.reactive.server.handlers.InvocationHandler.handle(InvocationHandler.java:29)
        at io.quarkus.resteasy.reactive.server.runtime.QuarkusResteasyReactiveRequestContext.invokeHandler(QuarkusResteasyReactiveRequestContext.java:108)
        at org.jboss.resteasy.reactive.common.core.AbstractResteasyReactiveContext.run(AbstractResteasyReactiveContext.java:141)
        at org.jboss.resteasy.reactive.server.vertx.VertxResteasyReactiveRequestContext$1$1.handle(VertxResteasyReactiveRequestContext.java:74)
        at org.jboss.resteasy.reactive.server.vertx.VertxResteasyReactiveRequestContext$1$1.handle(VertxResteasyReactiveRequestContext.java:71)
        at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100)
        at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:63)
        at io.vertx.core.impl.EventLoopContext.lambda$runOnContext$0(EventLoopContext.java:38)
        at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
        at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.lang.Thread.run(Thread.java:833)
        at com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:704)
        at com.oracle.svm.core.posix.thread.PosixPlatformThreads.pthreadStartRoutine(PosixPlatformThreads.java:202)

Are there any plans for supporting native builds any time soon?
Thanks

Hi @nikosk686 thanks for writing in!
Currently we do not support quarkus native builds, the recommended way uses the jvm approach.
To my knowledge this feature has not been brought up by the team, currently there is no timeline to support it.
I will bring it up as a potential new feature!

@nikosk686
This SDK depends on gson, okhttp, and slf4j-api. If all of these dependencies are available for GraalVM apps in the future, we may be able to support the native build too. However, I don't expect gson to be available for GraalVM as it relies reflection APIs (this is the cause of the error you encountered). I haven't thoroughly checked other potential errors but there may be some others apart from gson internals.
As @WilliamBergamin mentioned, we don't have any timeline for this and our recommendation is to go with the JavaVM builds.

Hello!
GraalVM support looks very useful for cloud deployments, as Slack webhook timeout is 3 seconds and from what I tried with cloud run, an elementary JVM app that accepts an event from Slack and publishes it to cloud task  starts in 5+ seconds. Cloud run timeout is 10 seconds, so the app gets a request, but Slack displays an error in the UI and the user most probably would like to re-attempt which is quite a bad UX for the integration. With GraalVM the same app starts within 1.5 seconds, which is acceptable.
Regarding okhttp and slf4j-api (tried backed by logback) there are not many problems, just a fixed amount of settings for GraalVM, still annoying, but quite a limited scope.
With Gson it's different, because of the following reasons:

Many data transfer objects using Gson should be listed in the reflections config of GraalVM.
If you miss something you'll get issues just at runtime on the transfer object serialization/deserialization, which could sometimes happen unexpectedly and after a long time running with no issues, depending on usage.

What do you think about using an approach used in Quarkus, when you explicitly state that some classes need to be registered for reflection?
Later on, in the build step, it allows to build a configuration for GraalVM.
Currently, there is a Lombok's @Data annotation on data transfer objects, but it can't be used as a marker as it has RetentionPolicy.SOURCE.
It looks like at a reasonably low cost (by adding the annotation to data transfer objects), it is possible to make GraalVM usage more smooth.

Hello team! Is there any update on GraalVM support? As @achugr said, there are lots of benefits in running in native mode.

@achugr @fnobilia, thank you for your comments. Technically, it might already be possible to add GraalVM support in some way, but we don't have plans to work on it in the short term. I understand the benefits of native builds, especially for the use cases you've mentioned. However, we have other priorities to focus on, and the number of GraalVM users seems significantly smaller in comparison to JavaVM users.
We may revisit this in the long run depending on the popularity of GraalVM and industry trends, but right now it's not the best timing for us.

Are there any updates on adding GraalVM support? Thanks

A bit off-topic, but it's worth mentioning as one of the potential solutions to the problem of slow startups, which are crucial in serverless environments. You could try CRaC. Here's an article about how to configure it. I haven't used CRaC myself yet, but I have tried a native build. In terms of configuration effort, CRaC seems even simpler than a native build, and I hope it will become trivial once it is supported through buildpacks.

A bit off-topic, but it's worth mentioning as one of the potential solutions to the problem of slow startups, which are crucial in serverless environments. You could try CRaC. Here's an article about how to configure it. I haven't used CRaC myself yet, but I have tried a native build. In terms of configuration effort, CRaC seems even simpler than a native build, and I hope it will become trivial once it is supported through buildpacks.

thank you!


Add support for optional explicit 'link' selector

Fixes https://github.com/wezm/rsspls/issues/13

Thanks for this and the other PR. I'm currently travelling. I should be able to review next week.


Ruby 2.4.2 fails to build on Ubuntu 16.04

I have installed Ruby 2.4.1 successfully on my Ubuntu 16.04 Desktop, but failed to build Ruby 2.4.2.
Here are the last lines of error log:
make[2]: Entering directory '/tmp/ruby-build.20171106150424.32381/ruby-2.4.2/ext/digest/md5'
compiling md5init.c
linking shared-object digest/md5.so
/usr/bin/ld: /usr/local/lib/libcrypto.a(md5_dgst.o): relocation R_X86_64_PC32 against symbol `md5_block_asm_data_order' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
Makefile:262: recipe for target '../../../.ext/x86_64-linux/digest/md5.so' failed
make[2]: *** [../../../.ext/x86_64-linux/digest/md5.so] Error 1
make[2]: Leaving directory '/tmp/ruby-build.20171106150424.32381/ruby-2.4.2/ext/digest/md5'
exts.mk:198: recipe for target 'ext/digest/md5/all' failed
make[1]: *** [ext/digest/md5/all] Error 2
make[1]: Leaving directory '/tmp/ruby-build.20171106150424.32381/ruby-2.4.2'
uncommon.mk:220: recipe for target 'build-ext' failed
make: *** [build-ext] Error 2

I have the same problem on ubuntu 17.10 for all ruby versions I have tried to install
Re-installing rbenv did not seem to help.

[UPDATE]
I succeeded to install Ruby 2.4.2 on the clean installed Ubuntu 16.04 Desktop.
It seems that something goes wrong on my working Ubuntu 16.04.
I will close this issue after researching just a little bit more.

I have not detected the root cause of the problem, I found a workaround:

Build openssl from the source:

$ cd /tmp
$ curl -LO https://www.openssl.org/source/openssl-1.1.0f.tar.gz
$ tar xvfz openssl-1.1.0f.tar.gz
$ cd openssl-1.1.0f
$ ./config --prefix=/opt/openssl/1.1.0f
$ make
$ sudo make install

Build ruby with CONFIGURE_OPTS environment variable:

$ CONFIGURE_OPTS="--with-openssl-dir=/opt/openssl/1.1.0f" rbenv install 2.4.2

I have the same problem.  Apt-Get installed versiion on Ubuntu 17.10 is Ruby Build version: 20161225-1
No version of Ruby installs now through rbenv.  Error reportd:
BUILD FAILED (Ubuntu 17.10 using ruby-build 20170914-5-gf41e847) .... ends in "segmentation fault, core dumped."
Since rbenv appears to have a gem version of ruby-build (did "gem update" under rbenv do this, because I did not?) I issued "gem uninstall ruby-build) and ran "rbenv install 2.3.1" using the Ubuntu installed version of Ruby-Build, but the same error and version number of Ruby-build appears.
Next step to is to uninstall + purge rbenv and to sea if Ubuntu supplied Ruby will be sufficient for my needs.

Purging rbenv and the ~/.rbenv directory and a clean install of rbenv performed.
Running "rbenv install 2.3.1" produced a similar error:

@casperl I think your problem is different from mine.
I don't encounter with any segmentation faults. My problem is related to linker.

@casperl
According to a bug report, you shoud type:
CC=/usr/bin/gcc-6 rbenv install 2.3.1

@kuroda that worked for me. Thanks!

Upon the release of Ruby 2.5.0, I tried to build on my Ubuntu 16.04. I got following error messages:
BUILD FAILED (Ubuntu 16.04 using ruby-build 20171215-3-ga97a138)

Inspect or clean up the working tree at /tmp/ruby-build.20171226020853.23177
Results logged to /tmp/ruby-build.20171226020853.23177.log

Last 10 log lines:
make[2]: Leaving directory '/tmp/ruby-build.20171226020853.23177/ruby-2.5.0/ext/digest/sha1'
exts.mk:259: recipe for target 'ext/digest/sha1/all' failed
make[1]: *** [ext/digest/sha1/all] Error 2
linking shared-object digest.so
make[2]: Leaving directory '/tmp/ruby-build.20171226020853.23177/ruby-2.5.0/ext/continuation'
make[2]: Leaving directory '/tmp/ruby-build.20171226020853.23177/ruby-2.5.0/ext/-test-/string'
make[2]: Leaving directory '/tmp/ruby-build.20171226020853.23177/ruby-2.5.0/ext/digest'
make[1]: Leaving directory '/tmp/ruby-build.20171226020853.23177/ruby-2.5.0'
uncommon.mk:240: recipe for target 'build-ext' failed
make: *** [build-ext] Error 2

As I did for Ruby 2.4.2, after building the openssl from the source, I succeeded to compile ruby with this command:
CONFIGURE_OPTS="--with-openssl-dir=/opt/openssl/1.1.0f" rbenv install 2.5.0

I am also getting the similar error, please could you help me.

Did you try to install this list of dependency in your Ubuntu system ?:
sudo apt-get install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm3 libgdbm-de

As far as I know, (and tested) Ruby versions < 2.4 requires libssl1.0, while >2.4 libssl1.1+. The two libssl packages conflict with each other, so you can't have both of them, so I had to juggle the libs in order to install the required ruby version. To make things even funnier (or more complicated), Ruby <2.4 tends to require gcc-6 instead of the current upstream version (which is 7).
So, usually it looks like that:
# for ruby <2.4
apt install libssl1.0-dev
CC=$(which gcc-6) rbenv install `version`

# for ruby >2.4
apt install libssl-dev
rbenv install `version`

I also faced this problem. This resource helped me to solve the problem.
https://www.digitalocean.com/community/tutorials/how-to-install-ruby-on-rails-with-rvm-on-ubuntu-18-04

Can this issue not be closed, as both the gcc-6 and libssl dependencies for earlier Rubies are documented in the wiki (here and here)?
After installing gcc-6 and libssl1.0-dev I was able to install both pre and post 2.4 Rubies on Ubuntu 18.04 as per the solution offered by @kubakrzempek without a problem. BTW it appears I do have both libssl libraries installed:
$ /sbin/ldconfig -pv|grep libssl
   libssl3.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libssl3.so
   libssl.so.1.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libssl.so.1.1
   libssl.so.1.0.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
   libssl.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libssl.so

Why should it be closed? What's the point of using a tool that works with all ruby envs if you have to dive into the docs for a compile error? At the very least it should check for these dependencies before building and get them or tell you they are missing so you can install them.

@kubakrzempek

for ruby <2.4

apt install libssl1.0-dev
CC=$(which gcc-6) rbenv install version
for ruby >2.4
apt install libssl-dev
rbenv install version
this worked very well.

# for ruby <2.4
apt install libssl1.0-dev
CC=$(which gcc-6) rbenv install `version`

# for ruby >2.4
apt install libssl-dev
rbenv install `version`

saved me installing an older Ruby version for a project I inherited.

As far as I know, (and tested) Ruby versions < 2.4 requires libssl1.0, while >2.4 libssl1.1+. The two libssl packages conflict with each other, so you can't have both of them, so I had to juggle the libs in order to install the required ruby version. To make things even funnier (or more complicated), Ruby <2.4 tends to require gcc-6 instead of the current upstream version (which is 7).
So, usually it looks like that:
# for ruby <2.4
apt install libssl1.0-dev
CC=$(which gcc-6) rbenv install `version`

# for ruby >2.4
apt install libssl-dev
rbenv install `version`

You're an angel!

This issue was fixed at the first reporter.


Fixed issue with CloseHand() for ADA in sim

Note that MoveHand function ignores collisions and will always terminate with the hand fully closed, even if it is penetrating an object. The robot.task_manipulation.CloseFingers() function simulates closing the fingers until they are in collision. This is why we have separate functions for CloseFingers and OpenFingers.

@Stefanos19 Can you take a look at my comment above?

I think the issue is that the command:  robot.task_manipulation.prob.SendCommand('CloseFingers') returns the following error:
[grasperplanner.cpp:258 PlanPath] no objects in environment

I will merge this for now. However, it is really not correct - we should figure out why CloseFingers is failing.
@Stefanos19 Please make an issue about this.


gitlab MR -> github PR support

it would be extremely useful, if your tool would be able to handle github PRs as well utilizing the same interface, because preferring gitlab for the actual private development work while contributing code to github hosted upstream repositories is a very common scenario, which isn't satisfyingly supported by any other tool right now.

I agree that would be useful. However, this repo was really only planned as a code-repository for my blog-post about this.
Especially the name would probably have to change, if the tool were to support more backends than Gitlab. :D
Anyway, if there is interest in such a tool, it might make sense to move it out here and make it more general. :)

yes -- it would be indeed a change/improvement, which goes far beyond the actual implementation, nevertheless it could be a really interesting project, because there is nothing similar available right now.
but it's of course up to you, whether you like to work any further on this kind of stuff at all. i just wanted to send you a little bit of feedback resp. new inspirations. ;)


Load function requires an object for the return value

Describe the bug
When returning nothing in a load function (as perceived to be permitted by the docs ) an error is thrown that doesn't pin point the actual issue - which may not even need to be one - which is that I wrote return; at the end of the load function instead of return {};
Logs
Cannot read property 'error' of undefined
TypeError: Cannot read property 'error' of undefined
at normalize (node_modules/@sveltejs/kit/dist/ssr.js:517:13)
at load_node (node_modules/@sveltejs/kit/dist/ssr.js:829:11)
at async respond_with_error (node_modules/@sveltejs/kit/dist/ssr.js:904:17)
at async respond$1 (node_modules/@sveltejs/kit/dist/ssr.js:1119:13)
at async render_page (node_modules/@sveltejs/kit/dist/ssr.js:1186:20)
at async render (node_modules/@sveltejs/kit/dist/ssr.js:1537:10)
at async Object.handle (/src/hooks:26:19)
at async respond (node_modules/@sveltejs/kit/dist/ssr.js:1510:10)
at async Immediate. (node_modules/@sveltejs/kit/dist/chunks/index.js:3305:23)
To Reproduce
in any @type {import('@sveltejs/kit').Load} function, change current return value to return;
Expected behavior
To set default object with status 200
Information about your SvelteKit Installation:

Diagnostics
System:
    OS: macOS 11.3.1
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
    Memory: 172.27 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.15.4 - ~/.nvm/versions/node/v14.15.4/bin/node
    npm: 7.12.1 - ~/.nvm/versions/node/v14.15.4/bin/npm
  Browsers:
    Chrome: 90.0.4430.212
    Firefox: 87.0
    Safari: 14.1
  npmPackages:
    @sveltejs/kit: next => 1.0.0-next.107
    svelte: ^3.34.0 => 3.38.2

Severity
Not severe, easily fixable.
Additional context
If this is by design, perhaps the docs could be updated to reflect this? With it currently saying that all keys are optional you'd assume you wouldn't have to pass an empty object to an all optional object but rather nothing at all.
Thanks for all the hard work!

Do you have a more specific reproduction for what you're seeing? Returning a falsy value from a load function should result in a 404 (see https://kit.svelte.dev/docs#routing-advanced-fallthrough-routes). This error sounds like you've written an __error.svelte component that is trying to handle it, but its own load function isn't properly passing the error object as a prop to the component.

Seems to be directly related to using the load function within the __layout.svelte component, which I'm not too sure is even a thing/allowed.
I was trying to use it as a 'catch all routes' function. I used it because I was looking for a way to redirect, and the load docs actually had the 'redirect' property listed so I thought this was the way to do it.
Looking at the handle hook it makes more sense to have the logic there - the docs are just a bit lacking here in what this is capable of doing.
I ended up moving the logic into the hooks.js as it was better suited there for authentication purposes but basically the code was this in __layout.svelte:
<script context="module">
	/**
	 * @type {import('@sveltejs/kit').Load}
	 */
	export async function load({ page, session }) {
		if (!session.person.uid && page.path !== '/login') {
			return {
				redirect: '/login',
				status: '302'
			}
		}
		return
	}
</script>

This threw the error I listed and if I removed the last return, it threw the same error. The only fix was to say return {} which seemed a bit odd to me. Bearing in mind it is a weird use case for load (hence why I've moved it) but someone might do something similar and run into the same issue.
I haven't added an __error.svelte component to my project and you can replicate the issue by adding the above code to __layout.svelte component in the demo app.

This __layout thing is the key here I think. I don't know though if this considered "works as designed" and we should update the docs to make clear that a load function in a __layout file needs to return something, or if this is a bug and this should be treated as if someone did not enhance the load function at all. I'd say both:

It should be okay to not return anything in the load function of a __layout file and treat this as if there was no load function at all
We should enhance documentation on https://kit.svelte.dev/docs#layouts and provide a short info that you can use the load function for passing context and for doing work like guarding against unallowed access.

Ah I see. I think this is probably a bug, yeah, but I'll let Rich weigh in. For route fallthrough purposes, I can't see a reason why you'd want different behavior when returning falsy from a layout load.

The error message for this is dramatically better now. I think it got updated when I turned on strict typing for TypeScript in the most recent releases. Now it says:

Error: /src/routes/__layout.svelte - load must return a value except for page fall through

The main issue remaining here is that it just shows it on a blank page instead of the normal error page:
https://github.com/sveltejs/kit/blob/2a1e9795ad9773e04669a7b9d0234caa0b688ade/packages/kit/src/runtime/server/page/load_node.js#L269
But I guess that happens because since this error is on a layout page it occurs on the error page and so since the error page can't be rendered it just shows a blank page with the error. I don't have any ideas how to do that differently, so am going to call this one solved


API guide for configuring NSX

Hi, I'm trying to automate the whole process of PKS deployment including the NSX part.
I''m facing some issues with the API guide of VMWARE which does not behave the same as the GUI based guide.
Do you have instructions how to do the same NSX related tasks using NSX's API guide?
Thanks

Sorry, we don't have that. Please refer to the NSX API documentation here: https://code.vmware.com/apis/547/nsx-t. Thanks.


Poulet4: Dune-based build

Right now, we have a hybrid build setup where, at the top level, make first invokes opam for the dependencies coq-poulet4 and ocaml-poulet4, which in turn calls dune to build those dependencies, and then make calls dune on the OCaml code. This works OK, but one downside is that changes in coq-poulet4 do not cause the OCaml code to be extracted again and rebuilt. We also miss out on some of the features of dune, such as build parallelization.
This PR puts the poulet4 code in one package again, and uses dune's support for Coq to build the Coq code, extract the right modules, and then build the OCaml code.
Because dune places the compiled source files in the _build directory, I have changed the _CoqProject to point there. My editor picks this up and allows me to do interactive edits as before, but it's worth verifying that this also works for other people.
One other change is that paths for imports now require the Poulet4 prefix. I'm not sure if it's possible to avoid this, but I kind of like it - it makes explicit which imports are local to us, and which come from the standard library. This used to be ambiguous in some cases.

Merged this after getting confirmation from multiple people that these changes are compatible with their workflow.


Missing entity MEASURE_kg_0 on staging

Very similar to last error. Is there way to test these missing entity errors?
Error: missing entity MEASURE_kg_0
    at makeDummyEntity (/opt/almond-cloud/node_modules/genie-toolkit/lib/utils.js:199:15)
    at makeDummyEntities (/opt/almond-cloud/node_modules/genie-toolkit/lib/utils.js:215:35)
    at Promise.all.minibatch.map (/opt/almond-cloud/node_modules/genie-toolkit/lib/sentence-generator/index.js:449:30)
    at Array.map (<anonymous>)
    at ContextualSentenceGenerator._process (/opt/almond-cloud/node_modules/genie-toolkit/lib/sentence-generator/index.js:446:54)
Emitted 'error' event at:
    at errorOrDestroy (internal/streams/destroy.js:107:12)
    at ContextualSentenceGenerator.onerror (_stream_readable.js:733:7)
    at ContextualSentenceGenerator.emit (events.js:198:13)
    at errorOrDestroy (internal/streams/destroy.js:107:12)
    at onwriteError (_stream_writable.js:436:5)
    at onwrite (_stream_writable.js:461:5)
    at ContextualSentenceGenerator.afterTransform (_stream_transform.js:94:3)
events.js:174
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at WriteWrap.afterWrite [as oncomplete] (net.js:788:14)
Emitted 'error' event at:
    at errorOrDestroy (internal/streams/destroy.js:107:12)
    at onwriteError (_stream_writable.js:436:5)
    at onwrite (_stream_writable.js:461:5)
    at _destroy (internal/streams/destroy.js:49:7)
    at Socket._destroy (net.js:613:3)
    at Socket.destroy (internal/streams/destroy.js:37:8)
    at WriteWrap.afterWrite [as oncomplete] (net.js:790:10)

It is actually the same error - the new version of genie hasn't hit staging yet, see #524


Encounter build error caused by redefinition of declarations on Windows

Describe the bug
A build error caused by redefinitions of c macro and function declarations.
To Reproduce
Steps to reproduce the behavior:

cd samples\hello_world
set BOARD=npcx9m6f_evb
west build -p always
See error

Expected behavior
build successfully.
Logs and console output
Please refer attached build_error.zip. We found lots of  redefined warnings/errors in syscall_list.h and kernel.h generated by gen_syscalls.py
In file included from C:/Users/TomChang/Desktop/zephyrproject/zephyr/include/zephyr/syscall.h:11,
                 from C:/Users/TomChang/Desktop/zephyrproject/zephyr/include/zephyr/kernel_includes.h:31,
                 from C:/Users/TomChang/Desktop/zephyrproject/zephyr/include/zephyr/kernel.h:17,
                 from C:/Users/TomChang/Desktop/zephyrproject/zephyr/arch/arm/core/offsets/offsets_aarch32.c:28,
                 from C:/Users/TomChang/Desktop/zephyrproject/zephyr/arch/arm/core/offsets/offsets.c:9:
C:/Users/TomChang/Desktop/zephyrproject/zephyr/samples/hello_world/build/zephyr/include/generated/syscall_list.h:215: warning: "K_SYSCALL_CLOCK_GETTIME" redefined
  215 | #define K_SYSCALL_CLOCK_GETTIME 206
      |
C:/Users/TomChang/Desktop/zephyrproject/zephyr/samples/hello_world/build/zephyr/include/generated/syscall_list.h:6: note: this is the location of the previous definition
    6 | #define K_SYSCALL_CLOCK_GETTIME 0

Environment (please complete the following information):

OS:  Windows
Toolchain - Zephyr SDK, 15.1
Commit SHA: 32fae07f299aa326

@dcpleung seems possibly related to your recent change?

Issue fixed on my side after applying commit 59350
Time to rock on zephyr 3.4. Thanks :)


Do not allow a device to become a leader when the router role is disabled

Fixes a bug reported by @nibanks.

LGTM 👍


Accessibility disable option

When accessibility open VoiceOver says the systemImage name every time on the cell.  I can avoid this using anyView instead of systemImage. But I think we shouldn't use anyView inside ForEach loops.

Hi, I'm sorry but I'm not familiar with Voice over. I have just tried it out and it seems that swiping does not work at all with accessibility voice over, at least I don't know how. I also tried it out in Apple Mail (where you can swipe each email list cell - left and right), it also does not work. Please provide more information on how I can help exactly. You can also fork my project and then make a pull request after modifying the code.