Spanish admonitions corrections

Docs PR Template
Why this should be merged

How this works

How these changes were tested

To prevent any errors while building

[] run vale /docs/file/path on all changed .md files to ensure all grammar rules pass
[] run markdownlint /docs/file/path on all changed .md files to ensure all linting rules pass
[] complete the above two checks and all additional rules outlined in style-checker-notes.md to
ensure all checks pass

If a document was removed/deleted

[] the path to that doc must be redirected to a valid URL via the
_redirects file
[] _redirects were manually verified with the cloudflare preview link
[] sidebars.json reflects all changes made to file path

If a document was moved

[] all files that were moved from their current directory to a new path have had their paths
redirected via the _redirects file
[] _redirects were manually verified with the cloudflare preview link
[] sidebars.json reflects all changes made to file path

El El lun, 30 de octubre de 2023 a la(s) 11:33, Meaghan FitzGerald <
@.***> escribió:

Docs PR Template Why this should be merged How this works How these
changes were tested To prevent any errors while building

[] run vale /docs/file/path on all changed .md files to ensure all
grammar rules pass
[] run markdownlint /docs/file/path on all changed .md files to
ensure all linting rules pass
[] complete the above two checks and all additional rules outlined
in style-checker-notes.md to
ensure all checks pass

If a document was removed/deleted

[] the path to that doc must be redirected to a valid URL via the
_redirects file
[] _redirects were manually verified with the cloudflare preview link
[] sidebars.json reflects all changes made to file path

If a document was moved

[] all files that were moved from their current directory to a new
path have had their paths
redirected via the _redirects file
[] _redirects were manually verified with the cloudflare preview link
[] sidebars.json reflects all changes made to file path

You can view, comment on, or merge this pull request online at:
https://github.com/ava-labs/avalanche-docs/pull/1568
Commit Summary

903129f
https://github.com/ava-labs/avalanche-docs/pull/1568/commits/903129f3233cc4c68d229c67eb3083fb6cfbfa25
advertencia->warning
23415ea
https://github.com/ava-labs/avalanche-docs/pull/1568/commits/23415eaf87534055414407ca1afed3b127fea4e5
other admonitions

File Changes
(6 files https://github.com/ava-labs/avalanche-docs/pull/1568/files)

M
i18n/es/docusaurus-plugin-content-docs/current/build/subnet/upgrade/considerations-subnet-upgrade.md
https://github.com/ava-labs/avalanche-docs/pull/1568/files#diff-0dc7d4860ea6c7c2706dd9e28787c9b5ae551d9ef25f25412d6fc55e32154ddd
(2)
M
i18n/es/docusaurus-plugin-content-docs/current/nodes/configure/avalanchego-config-flags.md
https://github.com/ava-labs/avalanche-docs/pull/1568/files#diff-294c0558984bd7de2742b479fa1b1eef431cd36ee57894a20dcd9087ba86990e
(2)
M
i18n/es/docusaurus-plugin-content-docs/current/nodes/configure/chain-config-flags.md
https://github.com/ava-labs/avalanche-docs/pull/1568/files#diff-3b7d6b07344d42fb4438bbdecfbee5edc87b028d5327bad54ece913372fea658
(2)
M
i18n/es/docusaurus-plugin-content-docs/current/nodes/configure/subnet-configs.md
https://github.com/ava-labs/avalanche-docs/pull/1568/files#diff-3d303fc03fa9e0f7eb906faa310d26c3b2be7d3cc7666ac37fef9c04529b3a5f
(4)
M
i18n/es/docusaurus-plugin-content-docs/current/nodes/system-requirements.md
https://github.com/ava-labs/avalanche-docs/pull/1568/files#diff-91856b88c1c0a2a4440b33c3b75962fcdeb0e3e822f1db11714c401e0d999dd1
(4)
M
i18n/es/docusaurus-plugin-content-docs/current/nodes/validate/add-a-validator.md
https://github.com/ava-labs/avalanche-docs/pull/1568/files#diff-cdadf6a683d0426a457eaa3553bef2a8fb278a40ca0fcddce62d6690fcfcf20f
(2)

Patch Links:

https://github.com/ava-labs/avalanche-docs/pull/1568.patch
https://github.com/ava-labs/avalanche-docs/pull/1568.diff

—
Reply to this email directly, view it on GitHub
https://github.com/ava-labs/avalanche-docs/pull/1568, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKINCU66IZ3NZ5Q3NTGSNQLYB7QE7AVCNFSM6AAAAAA6WMZ3Y2VHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3DQOBYG43TINY
.
You are receiving this because your review was requested.Message ID:
@.***>


Implement static shortcuts for Open Food Facts

Summary:
Add feature for displaying static shortcuts to specific actions. Shortcuts let users quickly start common or recommended tasks within the app. Works on API 25 or above.
Expected behavior:
We can add shortcuts for specific actions like 'Scan Barcode' , 'History' and 'Search by barcode' to  let users quickly search the products and also quickly view their history.
Observed behavior:
No shortcuts as of now.
Screen-shots:

We already have a bug for App Shortcuts at https://github.com/openfoodfacts/openfoodfacts-androidapp/issues/171
Pinned Shortcuts would be cool as well :-)

Ohh I am sorry I didn't look up for that :(
Can I work on that issue?

@huzaifaiftikhar of course you can, I am going to close this issue as a duplicate :) Please continue your work on #171


docs: provide decision record for EdcHttpClient

What this PR changes/adds
Add decision record for EdcHttpClient that's a wrapper around OkHttpClient and Failsafe that will provide retry mechanism out-of-the-box. Ref. #1566
Why it does that
document
Further notes

Linked Issue(s)
Ref #1566
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[x] added/updated relevant documentation?
[x] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and Etiquette for pull requests for details)

Would be good if this wrapper service also performs some logic common to every call, such as checking whether response body is null, log if this is the case...
Would also greatly simplify the testing.

Would be good if this wrapper service also performs some logic common to every call, such as checking whether response body is null, log if this is the case... Would also greatly simplify the testing.

I think this is something we could introduce later on, I would start with the simplest approach but then it could grow based on needs


sift-saltstack missing sift/files/salt-minion/minion config file?

Using new ubuntu 16.04 LTS, followed steps in README.md.
sudo salt-call --local --file-root=/tmp/salt state.sls sift
returns:
 ID: salt-minion-config
    Function: file.managed
        Name: /etc/salt/minion
      Result: False
     Comment: Source file salt://sift/files/salt-minion/minion not found
     Started: 17:18:37.016508
    Duration: 1.446 ms
     Changes:

I created a new folder /tmp/salt/sift/files/salt-minion then copied the default /etc/salt/minion file into this folder and then the install ran to completion.  I'm not confident this was the "right" answer, any suggestions?
Attached file jlsalt.zip contains output of install that failed and then succeeded after my attempt at a workaround.
jlsalt.zip
Kind Regards,
James

Definitely a bug, I had this fixed locally, just hadn't pushed it up yet. Resolved in https://github.com/sans-dfir/sift-saltstack/commit/91982b4baad9857224033eca8928a02f6ab9c957


Add axon and apical dendrites information in synthesis_json

TODO: synthesis_json is not working for biological data as it is, as it expects a prefix of mtype.
TODO: there is a bug when the input is multiple files, that generates the same json more than once.

Current coverage is 100.00%

Merging #123 into master will not affect coverage as of 9c0140d

@@            master    #123   diff @@
======================================
  Files           30      30
  Stmts          988     988
  Branches         0       0
  Methods
======================================
  Hit            988     988
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 9c0140d

Powered by Codecov. Updated on successful CI builds.


add more fields to our baseclasses using data/types.py

port more advanced fields like tel, ipaddress,.. etc from types into fields.py file

Add the Email, path, URL, tel, IP address , DateTime, date, time, duration types to our fields
commits
https://github.com/js-next/js-ng/commit/6922d2679d76ba7e975101f1d9a016c7c249c3b6
https://github.com/js-next/js-ng/commit/6502a752b7d013708c1de04afd88f6a27c2def1e
https://github.com/js-next/js-ng/commit/89ce048be13080f27912f48d80c97df4a139fd56
https://github.com/js-next/js-ng/commit/1d0a0e665b9f83e70f7c5772feefc4ffe573cd4e
https://github.com/js-next/js-ng/commit/a0885c03e52b412c05b253ba70db0408e96ddfdb

Fixing some bugs and adding some enhancements
commit:
https://github.com/js-next/js-ng/pull/170/commits/102166da426e1cc71e9cf34662711663de86a72c

add tests to our fields and update the error message
commit
https://github.com/js-next/js-ng/pull/170/commits/f40d8be58bcdf9f2756fb20122db6c259bbfd615


Hoist CSS needs to be updated to account for new/removed AG27 css classes

For example the .ag-react-container class no longer exists but Hoist still has style definitions that expect it.
Noticed to be causing small but unexpected changes to styling in client app.
Demoed for tom via Screenshare.

Thanks for demoing the styling issues @febbraiod - please see PR here: https://github.com/xh/hoist-react/pull/3013


Start Order

Is your feature request related to a problem? Please describe.
Portainer has made acquiring images and deploying them dead easy - and it would be awesome if we could set the order the initialised/started up in - so (for example) a mysql image runs before anything else.
Once multiple containers are defined (and running, with volumes/environments) you can't (easily?) reverse engineer a yml/compose file with relevant "depends"
Describe the solution you'd like
A "Start Before" or "Start After" setting in the UI, with a dropdown to allow choice of container dependency.
Describe alternatives you've considered
Looked for some portainer stack examples but can't find any.  Can't see any obvious way to add "depends" to the config.v2.json files.

depends_on is a docker standalone feature that requires the use of a docker-compose.yml file. So, in essence you are requesting a way to build a stack (yml) file from already running containers and include the depends on functionality in this feature. This build stack from containers functionality is already a feature request which you can follow here: #2845 so I will close this as a duplicate


feat: improve transition-group support keep-alive(#10021)

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[x] New/updated tests are included

If adding a new feature, the PR's description includes:

[x] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)
issue number: 10021
Other information:

OMG, I found the error three times in ci test.


Qsrs for in dynamic args

Not sure where the conflicts are. Most likely will check them on Monday upon my return but here is the code to resolve #114

Some changes were meant to go to 0.1.3 version hence the way it was. Anyway, let's focus on 0.2 onwards. Here are my views:

Regarding the name qsrs_for I don't really care what is called. Refactoring will be even easier after some changes I have in mind and I want to do (e.g. #118 ). To save time would refactoring to make_qsrs_for be clear to you? Bear in mind it has to be short as it is a dictionary key and cannot contain pairs as not all QSRs might be dyadic.

I prefer to have it under the QSR namespace in dynamic args. Question is whether it is good to have a convenience globals and where to put it. The only three ways I see are a) the one currently implemented and b) and c) from Christian's comment above. I am against (a) for other development reasons.

To be short as I got to go I prefer the following:
qsrs_for a namespaces property that overwrites global qsrs_for with an additional reserved key called globals or for_all_qsrs that holds global parameters such as qsrs_for, quantisation_factor, and whatever others.


Add 300 in c language

File(s) Modified: 300-Longest-Increasing-Subsequence.c
Language(s) Used: c
Submission URL: _https://leetcode.com/submissions/detail/792263660/_

Thanks, @julienChemillier!


Is your feature request related to a problem? Please describe.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
最初由 @ninglin9985 在 https://github.com/trustwallet/assets/issues/24937 发布

Hello and thank you, I am asking you for the address of the support offices, I need you for a face-to-face meeting, consultation and guidance from the support specialist team to investigate the problems of delivering financial resources and my investments in digital currencies and OneFT Weske Token, which will be sent as a hash address. extracted from pools and reservoirs and mines and companies and projects and farms, thank you if you call me and make an appointment in person
A
al


Corrected link to newsletter

Just corrected the link to the newsletter registration with the link you provided via twitter.
See https://github.com/quickstrom/quickstrom.io/pull/1

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

The failing docker login does not seem to be related to this PR. 🤷♂

Awesome, thank you! I'll have to fix the GitHub Action to not do docker stuff on PRs.

👍
Yet it still feels weird that docker login works on main/master and not within a PR. Why should TTY be present on the former and not on the latter? 🤔
For now I guess one does not need to publish the docker image from a PR.
But still, should this be investigated further?

I added a conditional so it only does login and push on the main branch. Secrets aren't available in PR builds so it can't really work there, anyway.