fix(i18n): chinese test suite

Add localeTiltes, descriptions, and adjust test text and testStrings to get the automated test suite working. The changes to the testStrings here are from the current English curriculum.

[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] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

@scissorsneedfoodtoo @raisedadead I would prefer not merging this PR, because @ojeytonwilliams has a draft PR (#38040) that will use the English challenge seed, testStrings, and solutions for the non-English versions.  It will also warn if the number of tests does not match (to catch situations where tests in English have been removed or added).  My plan was to be able to use the feature of this PR to capture all Chinese challenges that have different testStrings (minus the assert arguments), so we would know those challenge's text need to be scrutinized.  More than likely, if a challenge's number of tests is different, then the text probably changed on one or more of the tests for the challenge.  Also, even if the number of tests is the same, but the testString is different, it means that we probably need to make sure the text reflects any changes to the textString.
If you merge this PR, then we will lose all the insight on which challenges' text` actually need to be reviewed in the Chinese version.

We do intend in releasing the Chinese Curriculum ASAP.
Can you confirm if we would have the draft PR ready sooner in the next week.
Is there anything that we can do to speed up the same.
Is branching off or melding the PR into the target or this PR going to help?

I don't think my PR should be rushed in. If I've messed something up, it could affect a huge number of challenges.  As for finishing it, the main barriers (aside from QA) are the concerns @ahmadabdolsaheb raised and I wrote up here: https://github.com/freeCodeCamp/freeCodeCamp/pull/38040#issuecomment-577699712 Until we've figured out how to resolve them, I don't think the PR can be used.
@RandellDawson if this PR is merged, could you not diff the merge commit with the previous one? You should still be able to see all the changes to the testStrings.

@RandellDawson, you bring up a very good point. Unfortunately, this PR would make it more difficult to figure out which Chinese challenges's text will need to be updated.
I think your method of determining whether the text or testString for a test or tests needs to be updated is sound. When I was going through this by hand, comparing the number of tests between the English and Chinese challenges was the most obvious indication that the English challenge had updated tests.
The most common problem with the current Chinese testStrings are the third arguments for the assert statements. A lot of them have been removed or fixed in the English curriculum, but on the Chinese side, a bunch of challenges have nested double quotes. There were also things like missing localeTitles, descriptions, and solutions that used // solution  required (with two spaces instead of one), which caused the solution to be tested and fail.
Like @raisedadead mentioned on a call yesterday, the next step could be to take the solutions from the English challenges and port them to the Chinese files. The errors there will give us a good idea of which tests will need to be updated.
After that, while it's not ideal, one thing we could do is ask Chinese contributors to keep a list of challenges where the test text or testStrings are different than the English versions. Then we should have a good idea of which challenges in other languages will need to be fixed before @ojeytonwilliams's PR lands.

Oliver, you have done some incredible work on the PR and you are correct, we would not want to rush you at all.
That said, the Chinese community has been waiting for the curriculum to go live and we have a good momentum over here in terms of the translation efforts.
The freeCodeCamp.one instance is running on the legacy code and is also becoming slower to manage. We could spend the time getting it upto speed or dedicate ourselves in bring the Curriculum at par with the current english version (which it self is getting a overhaul)
I would vote for bringing this PR in and moving forward. And like Randell has pointed it would make our lives difficult, but I would ask your opinion before moving forth.
Would you all be OK with merging this and handling the additional work to bring the consistency in the text and testStrings.
The reason being we can get this live real quick on the staging instance and have a lot of eyes from the Chinese community who are currently working on the legacy codebase here. That way, we can quickly iterate and bring in the quality that we are aiming for.
Thoughts?

Quick Update:
Randell has reached out to me, he is on vacation for a few days and will have completed all that he needs to do to capture the data.
He has already completed hours worth of work on this, and has requested us to wait a few days.
I would honor his request and put a hold on this until next week. Meanwhile, I should still be able to take the changes from this PR and manually land a build for our internal testing.
Thanks a lot to everyone for your flexibility, patience and work on this. I am sure the Chinese community will be looking forward to this, excited as we are.

Thank you @RandellDawson and @ojeytonwilliams for all of your hard work unifying these tests. It will go a long way towards maintenance between these two languages, and later, all of the other translations.
Please let me know if there's anything else I can do in this PR. Once we have a good idea of which English challenges have changed since the release last year, I'd be happy to go in and apply them to the text and testStrings here in the Chinese challenges.

BTW, I was wondering since this PR targets the next-chinese branch. We can merge this. It could wait there while the #38040 (aiming master) gets ready and Randell is back?
@ojeytonwilliams thoughts?

As I understand it, this only affects my PR indirectly through what Randell was doing (putting together the comment dictionary).  As long as he's happy, I can't see any reason not to go ahead with this.

Awesome, so I am landing this on the next-chinese branch and I will setup the pipelines, provision servers, etc.
Thanks for all your work Gentlemen.
/cc @freeCodeCamp/chinese


Rename & Reorder AD CP Trust In ADFS2016 Farm Level & Up

 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.:x: zjorz sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

This looks great, thank you @zjorz

This is my first time doing this on github. Did I do it correctly? Anything I need to do before my addition shows up?
Thanks

It looks good. It looks like you closed the pull request. If you reopen it (or make a new one with the same changes), then I can approve them and merge them into the master branch, where everyone will have access to them.


Use AbstractStorageDecl::isSettableInSwift to prohibit direct writes to optional requirements

Stop pretending that an optional requirement is immutable via the StorageImplInfo request. This approach has lead astray the conformance checker and may have had a negative impact on other code paths, and it doesn't work for imported declarations because they bypass the request. Instead, use a forwarding AbstractStorageDecl::isSettableInSwift method that special-cases optional requirements.

https://github.com/apple/swift/pull/42363#issuecomment-1101616601

@swift-ci Please test

Hi Anthony! I'm the one who's been making the minimized cases Joe's been sharing—happy to report this seems to fix the actual crashes in the project I've been minimizing cases from.

Glad to hear. Sorry for the trouble!

Switched to -import-objc-header. Also, added a separate non-iOS test for ObjCBool → Bool bridging in a key path accessor.

@swift-ci please test

@swift-ci please test

@swift-ci please test


[GHSA-rp65-9cf3-cjxr] Inefficient Regular Expression Complexity in nth-check

Updates

Affected products

Comments
There is a Regular Expression Denial of Service (ReDoS) vulnerability in nth-check that causes a denial of service when parsing crafted invalid CSS nth-checks.

Hi @29Kumait, I appreciate your contribution to GitHub's Advisory Database. Were you intentionally proposing to remove that function, if so, do you have a reference link to why?

@CallmeMari ,
Hey Mari,

Of course it would've be a pleasure indeed, much thanks, I was just practicing actually.

I encountered this :

added 2067 packages, and audited 2069 packages in 46s
139 packages are looking for funding
run npm fund for details
119 vulnerabilities (1 low, 98 moderate, 17 high, 3 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run npm audit for details.

With newly experience it was a bit scary; I though it to be quite serious I was following @Copilot unconsciously 🤐.


Update README.md

PR #1
I have refined the README.md according to the specifications and added  contribution guidelines.

You've removed two sections: Main Components Section and Design Decisions and Highlights. And the CONTRIBUTING.md file has not been committed. Apart from that, the table of contents and other modifications are to be appreciated!

I'll make those changes and get back to you

All good, thanks for your contributing ! ^^


[Feature Request] Support for keyboard mappings

Community Note

Please use a 👍 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Graph Explorer Version (and Graph Database and Version used if applicable)
All versions
Is your feature request related to a problem? Please describe.
When I want to quickly take an action using the keyboard (e.g., using the delete key to delete a displayed node/edge), this does not work with Graph Explorer. Other actions like ctrl/command+Z for undoing actions would be nice as well.
Describe the solution you'd like
Mapping of actions like delete, ctrl/command+Z, ctrl+a to the Graph Explorer app
Additional context
Add any other context or screenshots about the feature request here. Describe any alternatives you've considered.

Undo feature captured in #317

I could see this playing out as two iterations:

Add shortcuts for the most common actions

Open search
Zoom in/out
Delete node
Expand node

Add more granular actions

Open specific sidebar panels
Go to connections
Go to graph
Go to data explorer
Open/close graph table view
etc


Native support for cuPy/cuDF backed Anndata

This would be immensely useful for the GPU data science community as it would start to enable pipelines fully on GPU.

This would be great. I'm not sure how we'd run in on CI though. AFAIK cupy and cudf don't have a "mock gpu" backend at the moment, right?

Looks like the uarray project could be helpful in implementing the cupy side of this.
As for dataframes, this conversation on the ossdata discourse is probably worth following.

Any update on this issue?

I've opened #1080 to track cupy support. @Intron7, what do you think about cuDF support? Is it a high priority?
I'm kinda eye-ing the dataframe-api, which maybe we could leverage for more dataframe types. If that pans out we could go for cuDF support via that.

@cjnolet @ivirshup I think in general, it's a good idea to support cudf in the long term. cudf is insanely fast when it comes to correlations (significantly faster than cupy) and other math-related tasks. However, as far as I know, it still has some issues with apply and categorical data. I attempted to use cudf for the GPU port of squidpy's ligrec, but it lacked some key features. What would be advantageous in the future is a fully dynamic anndata where you can seamlessly switch everything in and out of VRAM, and cudf has the potential to assist with that.
It would be beneficial to load data directly to the GPU from text files. Unfortunately, h5 files are not yet accelerated. Currently, I'm also concerned about VRAM in general. There isn't much heavy math computation going on in dataframes for anndata.
The areas where I foresee the most immediate benefits are likely the creation of .X .Layers etc. from cudf.Dataframes.


bugfix on the search function (UI)

The search breaks if there are multiple stable streams (all stable streams are grouped by the version) since the elementID and the function name are redeclared.

/hold

/label tide/merge-method-squash

/unhold


Failed to load class "org.slf4j.impl.StaticLoggerBinder" during cql-to-elm-cli

I am getting a Failed to load class "org.slf4j.impl.StaticLoggerBinder"
Here is the command I am running
.\cql-to-elm-cli\build\install\cql-to-elm-cli\bin\cql-to-elm-cli --input "..\..\Examples\ChlamydiaScreening_CQM.cql"
The full output is as follows:
================================================================================
TRANSLATE ..\..\Examples\ChlamydiaScreening_CQM.cql
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Translation failed due to errors:
Error:[1:1, 56:5] jakarta.xml.bind.JAXBException: Implementation of Jakarta XML Binding-API has not been found on module path or classpath.
 - with linked exception:
[java.lang.ClassNotFoundException: org.glassfish.jaxb.runtime.v2.ContextFactory]
Error:[5:1, 5:69] Could not resolve model name System
Error:[6:1, 6:91] Could not resolve model name System
Error:[7:1, 7:69] Could not resolve model name System
Error:[8:1, 8:98] Could not resolve model name System
Error:[9:1, 9:106] Could not resolve model name System
Error:[10:1, 10:64] Could not resolve model name System
Error:[11:1, 11:58] Could not resolve model name System
Error:[12:1, 12:63] Could not resolve model name System
Error:[13:1, 13:112] Could not resolve model name System
Error:[14:1, 14:69] Could not resolve model name System
Error:[15:1, 15:63] Could not resolve model name System
Error:[16:1, 16:81] Could not resolve model name System
Error:[17:1, 17:100] Could not resolve model name System
Error:[18:1, 18:74] Could not resolve model name System
Error:[20:55, 20:58] Could not resolve model name System
Error:[20:61, 20:61] Could not resolve model name System
Error:[20:64, 20:64] Could not resolve model name System
Error:[20:67, 20:67] Could not resolve model name System
Error:[20:70, 20:70] Could not resolve model name System
Error:[20:73, 20:73] Could not resolve model name System
Error:[20:76, 20:76] Could not resolve model name System
Error:[20:46, 20:77] Could not determine signature for invocation of operator DateTime.
Error:[20:89, 20:92] Could not resolve model name System
Error:[20:95, 20:95] Could not resolve model name System
Error:[20:98, 20:98] Could not resolve model name System
Error:[20:101, 20:101] Could not resolve model name System
Error:[20:104, 20:104] Could not resolve model name System
Error:[20:107, 20:107] Could not resolve model name System
Error:[20:110, 20:110] Could not resolve model name System
Error:[20:80, 20:111] Could not determine signature for invocation of operator DateTime.
Error:[20:37, 20:112] Internal translator error.
Error:[20:1, 20:112] Could not determine parameter type for parameter MeasurementPeriod.
Error:[22:1, 22:15] Internal translator error.
Error:[25:24, 25:40] Could not resolve identifier MeasurementPeriod in the current library.
Error:[29:10, 29:62] Could not resolve type name Condition.
Error:[43:2, 43:16] Could not validate reference to expression InDemographic because its definition contains errors.
Error:[46:2, 46:5] Could not resolve model name System
Error:[49:10, 49:52] Could not resolve type name DiagnosticReport.
Error:[51:1, 51:18] Internal translator error.
Error:[53:31, 53:37] Could not resolve identifier Patient in the current library.

I am new to this code and unsure whether the example files should actually work or not. But I cannot get any of my own CQL files to convert either.
Before this against the last code from master branch I was able to run
gradlew build
which only failed to build task :cql-to-elm:test
and
gradlew installDist
which executed successfully.
Any advice appreciated,
Matthew Dugal

On second thought, maybe this is the actual error.
jakarta.xml.bind.JAXBException: Implementation of Jakarta XML Binding-API has not been found on module path or classpath.
 - with linked exception:
[java.lang.ClassNotFoundException: org.glassfish.jaxb.runtime.v2.ContextFactory]

Thanks for the report! The slf4j and jaxb errors are fixed in this PR which should be reviewed and merged shortly:
https://github.com/cqframework/clinical_quality_language/pull/1319
I took a look at the CQL examples and they are quite out of date, written for an earlier version of the spec. We'll have to go through and update those. That said, this should run cleanly for you now:
./cql-to-elm-cli/build/install/cql-to-elm-cli/bin/cql-to-elm-cli --input ../../Examples/CMS135_QDM.cql
It's a different example than you were using previously.

See #462 for examples being out of date.

That changed has been merged to master. Try the following:
gradlew build
./cql-to-elm-cli/build/install/cql-to-elm-cli/bin/cql-to-elm-cli --input ../../Examples/CMS135_QDM.cql


Launch add-on

Add-on Launch checklist:

[x] finish all v1 features;
[x] tag 1.0.0;
[x] make sure README.md is has clear description, screenshot, instructions;
[x] make sure LICENSE.md is correct (MIT for open-source, EULA for closed-source);
[x] give Write access to the entire team on Github;
[x] add to Packagist (if open-source) or our private Satis (if closed-source);
[ ] if closed-source, add to Backpack website as paid product (so people can buy it); consider having a launch discount (50%);
[ ] if closed-source, add to Backpack pricing page;
[x] include in our add-ons page;
[x] mention it in our docs;
[ ] write a blog post about it;
[ ] tweet about it (schedule 3 tweets - launch tweet, reminder tweet after a few weeks, reminder tweet after a few months);
[x] submit the add-on to directories like madewithlaravel.com
[ ] submit to Laravel News

@karandatwani92 I think I'm done here for the time being. We need

[ ] tweets
[ ] article

Then you can assign it back to me, to submit the link to Laravel News (waiting for one to be approved first).

Hey @tabacitu
Yes, They are ready.
Please review:
https://hackmd.io/cplcMWUpRLi6jx1fT00Z2A

This is done right ? If not please reopen and finish it @karandatwani92 🙏


Test fail on arches ppc64le and s390x

Hello,
I am in the process of packaging ewma for Fedora but I encountered problems running the tests. On both ppc64le and s390x arches, the following test fails:
+ export GOPATH=/builddir/build/BUILDROOT/golang-github-VividCortex-ewma-0-0.1.git4cc8cc5.fc27.ppc64le//usr/share/gocode:/usr/share/gocode
+ GOPATH=/builddir/build/BUILDROOT/golang-github-VividCortex-ewma-0-0.1.git4cc8cc5.fc27.ppc64le//usr/share/gocode:/usr/share/gocode
+ go test -compiler gc -ldflags '' github.com/VividCortex/ewma
--- FAIL: TestSimpleEWMA (0.00s)
	ewma_test.go:26: e.Value() is 4734.500946466117, wanted 4734.500946466118
--- FAIL: TestVariableEWMA (0.00s)
	ewma_test.go:40: e.Value() is 4734.500946466117, wanted 4734.500946466118
FAIL
FAIL	github.com/VividCortex/ewma	0.018s

Could you identify why there is a discrepancy in the value given versus the value expected, only on these two arches while others arches test are fine?

Not sure... maybe there's a subtle difference with floating point arithmetic? They're only off by 0.000000000001, so maybe we should change the tests so they check that the value is within some range.

Tagged v1.1.1. https://github.com/VividCortex/ewma/releases/tag/v1.1.1


Why are the snippets more contextual on old site vs new?

Compare:
https://nuremberg.law.harvard.edu/search/?q="hitler+said"&m=documents&m=transcripts&m=photographs
to our new:
https://nuremberg.revsys.dev/search/?q="hitler+said"&m=document&m=transcript&m=photograph
Old site seems to be somehow pulling more contextual snippets for the search results.

Review how snippets are generated in general so you can explain it to Paul.


Printing output of Mentat's execution on the Mentat Python Client

I'd like to suggest a feature to print the output of the steps Mentat takes on the Mentat Python client similar to how it prints out a bunch of outputs when you run mentat . via an terminal.
I'm looking for something like this but for the Mentat Python Client -

Hey @gssakash-SxT, take a look at how I use the accumulated message feature of PythonClient here: https://github.com/AbanteAI/mentat/pull/205/files
Does that work for your use case? It'd be more flexible than printing all the output

This can be closed now, I've managed to figure out a temporary fix similar to what has been suggested above ^^


Error npm run protractor

I need to help for this issue.
I don't understand why it doesn't work
npm run protractor

><EMAIL_ADDRESS>preprotractor C:\Users\Voldemort\Documents\Laboratorio\angular-seed
> npm run update-webdriver

><EMAIL_ADDRESS>preupdate-webdriver C:\Users\Voldemort\Documents\Laboratorio\angular-seed
> npm install

><EMAIL_ADDRESS>postinstall C:\Users\Voldemort\Documents\Laboratorio\angular-seed
> npm run copy-libs

><EMAIL_ADDRESS>copy-libs C:\Users\Voldemort\Documents\Laboratorio\angular-seed
> cpx "node_modules/{angular,angular-*,html5-boilerplate/dist}/**/*" app/lib -C

npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\karma\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

audited 3902 packages in 6.551s

3 packages are looking for funding
  run `npm fund` for details

found 6 vulnerabilities (5 low, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details

><EMAIL_ADDRESS>update-webdriver C:\Users\Voldemort\Documents\Laboratorio\angular-seed
> webdriver-manager update --gecko false

[18:56:54] I/config_source - curl -oC:\Users\Voldemort\Documents\Laboratorio\angular-seed\node_modules\protractor\node_modules\webdriver-manager\selenium\standalone-response.xml https://selenium-release.storage.googleapis.com/
[18:56:54] I/config_source - curl -oC:\Users\Voldemort\Documents\Laboratorio\angular-seed\node_modules\protractor\node_modules\webdriver-manager\selenium\chrome-response.xml https://chromedriver.storage.googleapis.com/
[18:56:56] I/update - selenium standalone: file exists C:\Users\Voldemort\Documents\Laboratorio\angular-seed\node_modules\protractor\node_modules\webdriver-manager\selenium\selenium-server-standalone-3.141.59.jar
[18:56:56] I/update - selenium standalone: selenium-server-standalone-3.141.59.jar up to date
[18:56:56] I/update - chromedriver: file exists C:\Users\Voldemort\Documents\Laboratorio\angular-seed\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_81.0.4044.69.zip
[18:56:56] I/update - chromedriver: unzipping chromedriver_81.0.4044.69.zip
[18:56:56] I/update - chromedriver: chromedriver_81.0.4044.69.exe up to date

><EMAIL_ADDRESS>protractor C:\Users\Voldemort\Documents\Laboratorio\angular-seed
> protractor e2e-tests/protractor.conf.js

[18:56:57] I/launcher - Running 1 instances of WebDriver
[18:56:57] I/local - Starting selenium standalone server...
[18:56:57] E/launcher - spawn C:\Program Files\Java\jdk1.8.0_251\bin\bin\java ENOENT
[18:56:57] E/launcher - Error: spawn C:\Program Files\Java\jdk1.8.0_251\bin\bin\java ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
    at onErrorNT (internal/child_process.js:415:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
[18:56:57] E/launcher - Process exited with error code 199
npm ERR! code ELIFECYCLE
npm ERR! errno 199
npm ERR<EMAIL_ADDRESS>protractor: `protractor e2e-tests/protractor.conf.js`
npm ERR! Exit status 199
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>protractor script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\Voldemort\AppData\Roaming\npm-cache\_logs\2020-05-01T21_56_57_477Z-debug.log

I have already solve the issue. My JAVA_HOME variable was wrong.


Humanizegranularity

New feature allowing to select the granularity of the humanize function. We can receive for example 65 minutes ago rather than 1 hour ago.

Current coverage is 100% (diff: 100%)

Merging #388 into master will not change coverage

@@           master   #388   diff @@
====================================
  Files          14     14
  Lines        2944   3011    +67
  Methods         0      0
  Messages        0      0
  Branches      215    224     +9
====================================
+ Hits         2944   3011    +67
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 4996bc9...9c6dee4


Add Linter

Is your feature request related to a problem? Please describe.
There is currently no Linter being used
Describe the solution you'd like
We would like to add a Linter
Describe alternatives you've considered
N/A
Additional context
N/A

Possibilities

Pylint

Logical (code errors and bad patterns)and statistical (formatting) linter
Install with: pip install pylint
Also a plugin with PyCharm
Run from command line: pylint example.py
e.g. output:

Flake8

https://flake8.pycqa.org/en/latest/
To Install: python<version> -m pip install flake8
To use: flake8 check.py
Seems to have less that it checks compared to Pylint
E.g. output:

Pylama

https://github.com/klen/pylama
To Install: pip install pylama
Can recursively run on current directory with pylama
Output similar to Pylint
E.g. output

Super-Linter

https://github.com/github/super-linter
Runs all of these linters automatically for Python3:
Easy to create a GitHub workflow action for by following the guide on GitHub
Might be a bit heavy for a project that is only involves Python
Can also run locally: https://github.com/github/super-linter/blob/main/docs/run-linter-locally.md
sudo docker run -e RUN_LOCAL=true -e DEFAULT_WORKSPACE=~/cfcfrj/taketwo-webapi -v /home/username/cfcfrj/taketwo-webapi:/home/username/cfcfrj/taketwo-webapi/taketwo-webapi github/super-linter
E.g. output

Possibilities
1. **Pylint**

* Logical (code errors and bad patterns)and statistical (formatting) linter

* Install with: `pip install pylint`

* Also a plugin with PyCharm

* Run from command line: `pylint example.py`

* e.g. output:
  ![Screenshot from 2022-02-17 20-39-55](https://user-images.githubusercontent.com/22651608/154613256-e1c27193-2318-44f2-9863-4ee55cf7cd47.png)

This can also be easily added as a Github Action/Workflow for pull requests using the following Marketplace action: https://github.com/marketplace/actions/pylint-action

Thank you for the detail comparison @nic-jol. Can you please also look at Black and post your results here. We can pick between flake8 and black.

Superlinter was added after discussing with the team.


Test Github actions based packaging for mobile - Android

Test Github actions based packaging for mobile - Android.
If possible, the apk could be automatically created and shared - check on a forked repository.

https://developer.fyne.io/started/cross-compiling
Supported:

GOOS
GOARCH

android
amd64

android
386

android
arm64

android
arm

Android arm64 will be selected as a default.

Done on a fork, will be included in a PR.


Set MySQL session timeouts on DBAPI connect

Executing the SET query once for each engine/bind during app init is
severely broken. It will only work if the underlying pool of the Engine
hands out only one connection and will never close this connection.
Using SQLalchemy's event system seems to be the proper way.

I will merge this, although first, I want to test that the timeouts really work.


Add support for TrueType (0, 0) cmap tables (issue 5501, issue 5574, and bug 1037973)

This is a tentative patch that adds support for (0, 0) cmap tables. References available here and here.
Since those tables use "standard" Unicode, I hope that my assumption to just use the charCodes as is, is a reasonable one!
Fixes #5501.
Fixes #5574.
Fixes bug 1037973.

/botio-windows preview

/botio test

Looks really good to me and I can confirm that this fixes the referenced issues. Nice work!

/botio makeref

/botio makeref

/botio-linux makeref

Nice work!


Unable to connect to MySQL instance with private IP address

Whenever I start the Cloud SQL Proxy, and try to connect to an instance (using mysql cli from another window), I get the following output:
$ cloud_sql_proxy -instances=INSTANCE_CONNECTION_STRING=tcp:3310 -ip_address_types=PRIVATE -log_debug_stdout -verbose
2020/01/08 15:02:24 using credential file for authentication; email=SERVICE_ACCOUNT_EMAIL
2020/01/08 15:02:24 Listening on <IP_ADDRESS>:3310 for INSTANCE_CONNECTION_STRING
2020/01/08 15:02:24 Ready for new connections
2020/01/08 15:03:24 New connection for "INSTANCE_CONNECTION_STRING"
2020/01/08 15:03:45 couldn't connect to "INSTANCE_CONNECTION_STRING": dial tcp INSTANCE_IP:3307: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2020/01/08 15:28:16 Received TERM signal. Waiting up to 0s before terminating.

I have tried opening up all firewall rules, but nothing changes. I've also tried every suggestion mentioned in #164. According to the logs, the connection does seem to go through and gets authorized, but somehow the proxy doesn't receive the response.
I want to use the proxy to connect to an instance that only has a private IP address from my local machine in order to manage it when necessary. This seems like the intended use of the proxy. However, there is no documentation on this error at all.
Can somebody tell me how to fix it?

I want to use the proxy to connect to an instance that only has a private IP address from my local machine in order to manage it when necessary. This seems like the intended use of the proxy.

This is incorrect - the Cloud SQL proxy provides IAM authentication only. Connections via private IP must still meet these requirements , which include being on the same VPC as the instance. To connect from a device outside the VPC (e.g., your local machine) you can use a public IP instead.
You can also check out the "About the Cloud SQL Proxy" page for more information about what the proxy does.

@kurtisvg does that mean I could run the proxy from a VM/Cloud Run instance in the VPC and then connect from my local machine using the IP of the VM?

@kurtisvg does that mean I could run the proxy from a VM/Cloud Run instance in the VPC and then connect from my local machine using the IP of the VM?

You could run it on a GCE instance (Cloud Run doesn't currently have VPC support AFAIK), but it's almost disadvantageous in every way over just adding a public IP to your instance:

Connecting with public IP requires some form of auth (proxy, ssl cert, or authorized by IP) to connect while GCE instances don't (by default). You can even make this more secure by requiring connections use the proxy, which means only users with the "Cloud SQL Connect" IAM role or higher can connect to the instance.
Connecting with public IP should have lower latency since it's a (more) direct connection, instead bouncing off a GCE VM first
Adding a public IP doesn't cost any more, but having a GCE VM run a proxy likely will


⚠ ClamAV has degraded performance

In c5dfed5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 227 ms

Resolved: ClamAV performance has improved in 5a9b6ab.


Makefile env tweak

PR summary
Tiny change. Now, instead of running make -f Makefile.local, I can just put MAKE_ENV="local" in my .bashrc and run make. Default without that env var is still to run the nix versions of tests / commands.
Review checklist

[ ] The story has unit or integration tests
[ ] No new bugs, and any tech-debt is identified and justified
[ ] There is enough API documentation (how to use)
[ ] There is enough code documentation (how the code works)

@ddd-mtl

ok.
I would probably prefer local as the default and have MAKE_ENV="nix", but I'm not using make for now so can't really tell from a user perspective.

I agree personally, but for consistency across the org, we're being asked to have nix be the default.


Ensure EOPNOTSUPP thrown via Data reading from a socket does not crash

On some platforms like Darwin, attempting to read Data from a path representing a socket can cause the EOPNOTSUPP error to be thrown, but POSIXError.Code is missing a case for this errno so we hit an assertion failure in our code. This patch works around this case to avoid the crash by dropping the posix info from the produced error while still asserting for other invalid errno's to catch cases where we incorrectly capture errno

@swift-ci please test


config: Update _config.yml(blog/blog?)

This is an example on the blog page of a link to a post on the blog.html:
https://ralphhightower.github.io/2024/09/27/WTF_Trump_GibberingAbout.html
There is no /blog/ in the path:
https://ralphhightower.github.io/blog/2024/09/27/WTF_Trump_GibberingAbout.html
Changing uri in _config.yml to "https://ralphhightower.github.io/blog/blog/" didn't work either.


Add due date and alarm date to the chore

[x] Rename all due_at and alarm_at references
[x] Add columns due_at and alarm_at to the Chore model
[x] Migration: Create the columns
[x] The Alarm model will be just a history of alarms
[x] The main alarm control will be done completely by querying Chore
[x] Fix all tests
[x] Fix Telegram bot (currently not fully covered by tests)
[x] Rename "finish" action to "pause", and don't add an alarm to history
[x] Migration: move data
[x] Fix broken tests

This change is

Codecov Report

Merging #98 into develop will increase coverage by 0.12%.
The diff coverage is 92.85%.

@@             Coverage Diff             @@
##           develop      #98      +/-   ##
===========================================
+ Coverage    76.75%   76.88%   +0.12%
===========================================
  Files           21       21
  Lines          753      757       +4
===========================================
+ Hits           578      582       +4
  Misses         175      175

Impacted Files
Coverage Δ

dontforget/utils.py
73.33% <100%> (+0.91%)
:white_check_mark:

dontforget/database.py
72.72% <100%> (+0.96%)
:white_check_mark:

dontforget/models.py
93.9% <88.88%> (ø)
:white_check_mark:

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 95854e8...214ee6d. Read the comment docs.

Reviewed 14 of 14 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable


feat(node-drain): Adding the node drain experiment

Signed-off-by: shubhamchaudhary<EMAIL_ADDRESS>

Logs
W0707 09:14:13.205435       1 client_config.go:541] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2020-07-07T09:14:13Z" level=info msg="[PreReq]: Getting the ENV for the  experiment"
time="2020-07-07T09:14:13Z" level=info msg="[PreReq]: Updating the chaos result of node-drain experiment (SOT)"
time="2020-07-07T09:14:13Z" level=info msg="[Info]: The application informations are as follows" Namespace=shubham Label="run=nginx" Ramp Time=0 Node Name=shubhamworker2-virtual-machine
time="2020-07-07T09:14:13Z" level=info msg="[Status]: Verify that the AUT (Application Under Test) is running (pre-chaos)"
time="2020-07-07T09:14:13Z" level=info msg="[Status]: Checking whether application pods are in running state"
time="2020-07-07T09:14:13Z" level=info msg="The running status of Pods are as follows" Pod=nginx-65f65459-98f8p Status=Running
time="2020-07-07T09:14:13Z" level=info msg="[Status]: Checking whether application containers are in running state"
time="2020-07-07T09:14:13Z" level=info msg="The running status of container are as follows" container=nginx Pod=nginx-65f65459-98f8p Status=Running
time="2020-07-07T09:14:13Z" level=info msg="[Status]: Verify that the Auxiliary Applications are running (pre-chaos)"
time="2020-07-07T09:14:13Z" level=info msg="[Status]: Checking whether application pods are in running state"
time="2020-07-07T09:14:13Z" level=info msg="The running status of Pods are as follows" Status=Running Pod=nginx-65f65459-98f8p
time="2020-07-07T09:14:13Z" level=info msg="[Status]: Checking whether application containers are in running state"
time="2020-07-07T09:14:13Z" level=info msg="The running status of container are as follows" container=nginx Pod=nginx-65f65459-98f8p Status=Running
time="2020-07-07T09:14:13Z" level=info msg="[Inject]: Draining the shubhamworker2-virtual-machine node ..."

time="2020-07-07T09:16:26Z" level=info msg="[Confirmation]: The application node has been drained successfully"
time="2020-07-07T09:16:26Z" level=info msg="[Status]: Verify that the AUT (Application Under Test) is running (post-chaos)"
time="2020-07-07T09:16:26Z" level=info msg="[Status]: Checking whether application pods are in running state"
time="2020-07-07T09:16:26Z" level=info msg="The running status of Pods are as follows" Pod=nginx-65f65459-98f8p Status=Running
time="2020-07-07T09:16:26Z" level=info msg="[Status]: Checking whether application containers are in running state"
time="2020-07-07T09:16:26Z" level=info msg="The running status of container are as follows" Status=Running container=nginx Pod=nginx-65f65459-98f8p
time="2020-07-07T09:16:26Z" level=info msg="[Status]: Verify that the Auxiliary Applications are running (post-chaos)"
time="2020-07-07T09:16:26Z" level=info msg="[Status]: Checking whether application pods are in running state"
time="2020-07-07T09:16:26Z" level=info msg="The running status of Pods are as follows" Pod=nginx-65f65459-98f8p Status=Running
time="2020-07-07T09:16:26Z" level=info msg="[Status]: Checking whether application containers are in running state"
time="2020-07-07T09:16:26Z" level=info msg="The running status of container are as follows" Status=Running container=nginx Pod=nginx-65f65459-98f8p
time="2020-07-07T09:16:26Z" level=info msg="[The End]: Updating the chaos result of node-drain experiment (EOT)"

While doing node drain the application pod gets removed from the node can we use it as post chaos check?

While doing node drain the application pod gets removed from the node can we use it as post chaos check?

@uditgaurav  we already have that check


feat: Wallet UI tweaks

All thanks to some excellent design mockups and ideas from Ben Weeks! 🙌 🙌 🙌
Will have:

Other wallet cards in the Wallet UI
Configurable bg image option (from admin as global and user if not set in admin)
Better exchange rate workflow
Button cleanup

So far....

Nice work :-)
Designs can be found here:
https://www.figma.com/design/ST7TmSeEKIvtZMvt7IHA6h/LNbits-redesign?node-id=0-1&t=cQ7068R0SdgBzScs-1

@SashaPavlova ...

Getting there


Help with "Many-to-many matching not allowed" in Sloth-generated Recording Rules

The Problem
My SLO alerts aren't firing. Here's an example of one that should have fired this week, but didn't.  (Indentations / spacing is my own for easier reading).
My graphs etc reflect what I'd expect in Grafana, but these alerts never fire. My alertmanager etc look to be working ok, no clear logging or errors. I do see some prometheus errors around some recording rules, but nothing that explicitly seems related to the recording rules / metrics referenced in this alert.
alert:
expr:
  (max without (sloth_window) (slo:sli_error:ratio_rate5m{sloth_id="bevy-production_grpc_edit_items_availability",sloth_service="bevy",sloth_slo="production_grpc_edit_items_availability"} > (14.4 * 0.01))
  and
  max without (sloth_window) (slo:sli_error:ratio_rate1h{sloth_id="bevy-production_grpc_edit_items_availability",sloth_service="bevy",sloth_slo="production_grpc_edit_items_availability"} > (14.4 * 0.01)))
  or
  (max without (sloth_window) (slo:sli_error:ratio_rate30m{sloth_id="bevy-production_grpc_edit_items_availability",sloth_service="bevy",sloth_slo="production_grpc_edit_items_availability"} > (6 * 0.01))
  and
  max without (sloth_window) (slo:sli_error:ratio_rate6h{sloth_id="bevy-production_grpc_edit_items_availability",sloth_service="bevy",sloth_slo="production_grpc_edit_items_availability"} > (6 * 0.01)))

labels:
  channel: #eng-releases
  severity: slack
  sloth_severity: page
  annotations:
  summary: {{$labels.sloth_service}} {{$labels.sloth_slo}} SLO error budget burn rate is over expected.
  title: (page) {{$labels.sloth_service}} {{$labels.sloth_slo}} SLO error budget burn rate is too fast.

What are some suggestions on how to correct this?

Note
When I query Thanos with this alert query, I get an empty query result (probably the issue). However if I update the query in thanos with the on() vector(0) before the > (6 * 0.01) etc, I actually see a graph that kind of looks like what I'd expect.

So I'm wondering if the answer here is some control (or an update to my PSLO objects, or how the prom rules are generated) so that the queries can get updated?  We're pretty much flying blind at the moment unless we keep our graphs opened all the time.  Even then there are too many to monitor manually.


readme has wrong link to releases

readme should link to https://github.com/JesseVii/StockScreener/releases rather than https://github.com/JesseVii/TTS/releases

Thanks! fixed it

Unrelated but do you happen to have time to look through https://github.com/JesseVii/TTS/pulls ? I also sent you a discord DM if you prefer to communicate over that channel


Please respect robots.txt

when crawling a website the robots.txt should be respected.

Sometimes circumventing censorship requires flexibility. It should be an option tho

Sometimes circumventing censorship requires flexibility. It should be an option tho

robots.txt is not a means to censor anyone. Censorship means that you're prevented from expressing ideas or other content, and you're not expressing yourself when scraping a website.
If a website blocks a user agent in its robots.txt file, it means that the providers ask you not to scrape their website.
Even wget respects this preference (by default), so it's only fair to ask a general-purpose scraping tool to at least do the same by default.

@Joshix-1 This is on the roadmap and it will be configurable.

@memoryhash there is a difference between open access (telling Disallow to get bent) vs spamming server request (respecting Crawl-delay out of courtesy), but people mix the latter with the former and that is very unfortunate.
For @archer-321 censorship is not just blocking freedom to express opinions, but also stopping the freedom to archive for historical purposes (looking at Internet Archive). People will throw lawyers just to try memory-hole the public.


Plugin fontsize doesn't change the value of textarea

Hi,
I have the latest version of trumbowyg (2.21.0) and I have a bug when I try to change the fontsize of the text, the plugin change the size but if I try to get the value of the textarea I get the text without the new font-size style. But if I do another change after (like new character in the text or bold for exemple, the text get the right style).
For exemple :
If I have a text :
Lorem ipsum dolor sit amet
And I change "ipsum" with the "18px" fontsize in the dropdown list.
$("textarea").trumbowyg( 	{ 		btns: [['strong'], ['fontsize']], 		plugins:  		{ 			fontsize: 			{ 				sizeList:  				[ 					'14px', 					'18px', 					'22px' 				], 				allowCustomSize: true 			} 		} 	}).on('tbwblur', function() 	{ 		console.log($("textarea").val()); 	});
When I change the fontsize (by 18px), the console return
Lorem ipsum dolor sit amet

But if I add a new word after like "Lorem ipsum dolor sit amet test" the console return
Lorem ipsum dolor sit amet

You can try without the event "tbwblur" too, after change de fontsize just enter "console.log($("textarea").val());" in the console you will see that nothing have change.
The bug only append with the "dropdown list / sizeList", but with the "custom" button (allowCustomSize) all is working well.
Thanks for your beautiful plugin, and I hope you will find a solution for this problem.

There is a fix on the develop branch that I need to tag :)
I will do that soon!

Ok thanks for your answer :)

Fixed in 2.22, same as #1117


[v2.5] KDM release: k8s june patches

Kubernetes updates:

This is a KDM release for new k8s versions: v1.18.20, v1.19.12 and v1.20.8.  It's not going out with any Rancher release, it's a KDM + RKE release only.

New k8s versions
Rancher versions

v1.18.20-rancher1-2
2.5.0+

v1.19.12-rancher1-1
2.5.0+

v1.20.8-rancher1-1
2.5.6+

Rancher updates:

v1.18.20-rancher1-2 will be v1.18.19-rancher1-1 from v2.4 with ACI images.
rke-tools is updated to v0.1.75

Developer changelog: - TBD

There are existing k8s versions in dev-v2.5 that haven't been released (absent in release-v2.5), so the same versions can be updated. Following versions need to be updated with their compatible rancher server versions:

update version from
to
update rancher version constraints

v1.20.5-rancher1-2
v1.20.6-rancher1-1
2.5.6+

v1.19.9-rancher1-2
v1.19.10-rancher1-1
2.5.0+

All existing v1.18.x versions in dev-v2.5 need to be released or have been released (are present in release-v2.4) so we need to introduce new k8s version. To introduce a new k8s version, basecopy the latest existing version in a separate commit, followed by another commit to update what's changed. Following versions need to be created with their compatible rancher server versions:

basecopy version from
create
set rancher version constraints

v1.18.17-rancher1-3
v1.18.18-rancher1-1
2.4.5+

Following system images need to be updated:

Name
Kubernetes Version
Version

etcd
v1.18.18-rancher1-2, v1.19.10-rancher1-1, v1.20.6-rancher1-1
v3.4.15-rancher1

nginx-ingress
v1.20.6-rancher1-1
nginx-0.43.0-rancher3

Update constraints for all addon versions so the new Kubernetes versions use the right template. Refer to the table below to confirm the template name.

 Confirm the versions for System Images and Addon templates are correct. Update this table if new versions get introduced. Click to view the full list.

Name
Kubernetes Version
Version
Update constraints for addon versions if required

etcd
v1.18.17
v3.4.3-rancher1

etcd
v1.19.9
v3.4.13-rancher1

etcd
v1.20.5
v3.4.14-rancher1

kube-dns
v1.18.17
v1.15.2
kubeDnsv116

kube-dns
v1.19.9, v1.20.5
v1.15.10
kubeDnsv116

core-dns
v1.18.17
v1.6.9
coreDnsv117

core-dns
v1.19.9
v1.7.0
coreDnsv117

core-dns
v1.20.5
v1.8.0
coreDnsv117

flannel
v1.18.17
v0.12.0
flannelv116

flannel
v1.19.9, v1.20.5
v0.13.0
flannelv116

calico, canal
v1.18.17
v3.13.4
canalv117PrivilegedCalico3134, calicov117Privileged

calico, canal
v1.19.9
v3.16.5
canalv3165, calicov3165

calico, canal
v1.20.5
v3.7.2
canalv3171, calicov3171

weave
v1.18.17
v2.6.4
weavev116

weave
v1.19.9
v2.7.0
weavev116

weave
v1.20.5
v2.8.1
weavev120

aci
all
<IP_ADDRESS>.1ae238a
aciv500

metrics-server
v1.18.17, v1.19.9
v0.3.6
metricsServerv18

metrics-server
v1.20.5
v0.4.1
metricsServerv120

podInfra
v1.18.17
3.1

podInfra
v1.19.9, v1.20.5
3.2

node local
v1.18.17
1.15.7
nodelocalv115

node local
v1.19.9, v1.20.5
1.15.13
nodelocalv115

rancher forks

dns-autoscaler
v1.18.17
v1.7.1

dns-autoscaler
v1.19.9, v1.20.5
v1.8.1

flannel-cni
all
v0.3.0-rancher6

ingress
v1.18.17, v1.19.9
nginx-0.35.0-rancher2
nginxIngressV11512

ingress
v1.20.5
nginx-0.43.0-rancher1
nginxIngressV11512

ingress-backend
all
1.5-rancher1

rke-tools
all
v0.1.71

windowsPodInfra
all
v0.1.6

Available to test with dev-v2.5 KDM and RKE RC v1.2.9-rc2 once drone passes, link: https://drone-publish.rancher.io/rancher/rke/1015

Verified the following kdm checks
Fresh install checks - 2.5.8 - pointing to dev-v2.5

Deployed clusters with k8s version v1.18.20-rancher1-2, v1.19.12-rancher1-1 ,v1.20.8-rancher1-1 on all network providers - weave/flannel/calico/canal
Validations of Network checks on all clusters look good
Validation tests on Canal cluster look good

Upgrade checks - v2.5.8 pointing to release-v2.5

Deployed cluster with k8s  v1.18.18-rancher1-2, v1.19.10-rancher1-1 ,v1.20.6-rancher1-1 version on all  network providers weave/flannel/calico/canal with KDM job pointing to release-v2.5
pre upgrade checks look good
Upgrade KDM to dev-v2.5
Upgrade K8s versions to new versions - v1.18.20-rancher1-2, v1.19.12-rancher1-1 ,v1.20.8-rancher1-1
Post upgrade checks look good.

Min checks on 2.5.3
Deployed 2.5.3 pointing to dev-v2.5
Created Clusters for k8s versions - v1.18.20-rancher1-2, v1.19.12-rancher1-1  with all network provider
Validations of Network checks on all clusters look good
RKE checks
Deployed a k8s cluster using RKE version v1.2.9-rc2 and k8s - v1.18.20-rancher1-2, v1.19.12-rancher1-1 ,v1.20.8-rancher1-1
Basic checks on this cluster worked.


Release Google.Cloud.Workflows.V1 version 2.3.0

Changes in this release:
No API surface changes; just dependency updates.

I'll open and close this PR to trigger some of the checks that have been queued for hours.

Created release for Google.Cloud.Workflows.V1-2.3.0


Export P&E Reports from Crossfeed UI

fixes #1468
🗣 Description
Allow upload and download of P&E reports from the Crossfeed UI.
Reports are uploaded and accessed from an S3 bucket.
Only organizations with a P&E tag will have this feature. If not, the page will still exist, but saying that the organization isn't registered with P&E and where to ask questions.

Need to make sure standard users can't add the P&E tag.

Andy: python backend worker updates
Ashwin: frontend vulnerabilities

Let's see if we can have a similar table to the domains table that shows all reports -- one column should be report type ("P&E/WAS/VS"), and users can filter by that column.

@rc-raizen Please take a look at this PR / fix the lint and test issues, and then we can work on https://github.com/cisagov/crossfeed/issues/1643 once it's merged.

frontend and backend checks green. Ready to merge @epicfaace

Updated table:

@aloftus23 Can you add a test that makes sure people can't export reports that aren't from their own orgs?

Added tests.


fix(guide):HTML replaced stub of blockquote element

added a concise explanation and example.

Description
Replaced stub with article
Pre-Submission Checklist
Common mandatory requirements

[x] This pull request targets the master branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/
(e.g. fix/signin-issue)
[x] Reviewed necessary guidelines in CONTRIBUTING.md.

By submitting this pull request, I have verified the following:

[x] Added descriptive name to pull request. (mandatory)
Your PR should NOT be called Update index.md, since it does not help the maintainer understand what has been changed.
Good Guide PR title examples:
fix(guide): Git - edit Git Commit article
feat(guide): PHP - create PHP section and add Data Structures article

Good Coding challenge PR title examples:
fix(coding): add tests to Basic HTML challenge
fix(coding): update instructions to CSS Grid challenge

Good Learning platform PR title examples:
fix(platform): fixed sign in api
fix(platform): removed css from editor

Issues Closures

[ ] Addressed currently open issue. (replace XXXXX with an issue no in next line)

Closes #XXXXX
Since this change is a copy edit or translation for Guide articles or Coding Challenges:

[x] I confirm no plagiarized, duplicate, or repetitive content that has been directly copied from another source.
[x] I am adding only https links to external sources.
[x] I am not adding short links instead of full URLs to webpages.
[x] I have followed the recomended style guides for the copy edit.

Requirements, for changes which are NOT simple copy editing or translations:
You may skip the below ONLY if your changes do not touch tests, ui logic, api-server, etc. Your PR may not be accepted, if you did not meet these mandatory requirements. Simply put, we can't assume it will work if we never saw it working.
Since this change adds, updates or removes coding challenge tests:

[ ] I completed the coding challenge locally, and the changes look good.
[ ] Other tests or user stories in instructions are not affected.

Since this change is for the Learning platform (UI, logic, etc.):

[ ] I confirm my changes look good by running freeCodeCamp locally.
[ ] All new and existing tests pass the command npm test.

(Optional) Additional Context and Screenshots:

:sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles:
Congratulations on your first contribution to freeCodeCamp/freeCodeCamp!
Thank you
:sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles: :sparkles:


fromEntity 'kube-apiserver' not working on AKS/GKE

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
When trying to set up NetworkPolicies for our clusters, we ran into an issue with ValidatingWebhooks. Here the Kubernetes API needs to be able to call the webhook, which we allowed as follows:
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:
  name: default
spec:
  endpointSelector: {}
  ingress:
[...]
    - fromEntities:
        - kube-apiserver
      toPorts:
        - ports:
            - port: "10250"
[...]
  egress:
[...]

However, the web hook cannot be reached (ArgoCD output on sync):
one or more objects failed to apply, reason: error when patching "/dev/shm/3539688072": Internal error occurred: failed calling webhook "validate.externalsecret.external-secrets.io": failed to call webhook: Post "https://external-secrets-webhook.external-secrets.svc:443/validate-external-secrets-io-v1beta1-externalsecret?timeout=5s": context deadline exceeded

Hubble shows the Source Identity of the dropped traffic as remote-node on AKS and konnectivity-agent on GKE. Adding remote-node to the fromEntities (AKS) or fromEndpoints konnectivity-agent(GKE) list resolved the issue.
Cilium Version
1.15.3
Kernel Version
Linux aks-spot-26938668-vmss00000J 5.15.0-1054-azure #62-Ubuntu SMP Mon Jan 15 15:51:19 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
AKS v1.28.5
Regression
No response
Sysdump
cilium-sysdump-20240401-174035.zip
Relevant log output
No response
Anything else?
On EKS the same call is correctly identified as coming from kube-apiserver.
Cilium Users Document

[X] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

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

Curious, so the inbound traffic is not classified as coming from kube-apiserver. Let's bounce over to the policy experts, maybe it's a known issue.

Possibly related: https://cilium.slack.com/archives/C01JALNQAR1/p1712576400445379

The identity for the kube-apiserver entry from the sysdump looks fine:
16777217   cidr:<IP_ADDRESS>/32
           reserved:kube-apiserver
           reserved:world

The corresponding IP entry also exists in the IPCache.

Hubble shows the Source Identity of the dropped traffic as remote-node on AKS and konnectivity-agent on GKE.

Do you have a JSON output of such a flow? In particular, for fromEntities: [kube-apiserver] to work, the ingress flow must directly come from the <IP_ADDRESS> IP (i.e. the endpoint of the Kubernetes service endpoint) and not be masqueraded.

{
   "flow":{
      "time":"2024-04-08T12:36:52.704115824Z",
      "uuid":"1239e6dd-0eb4-4bb3-82a5-95543088eb2a",
      "verdict":"DROPPED",
      "drop_reason":133,
      "ethernet":{
         "source":"4e:33:04:0f:e2:ef",
         "destination":"a6:48:fe:06:52:f5"
      },
      "IP":{
         "source":"<IP_ADDRESS>",
         "destination":"<IP_ADDRESS>",
         "ipVersion":"IPv4"
      },
      "l4":{
         "TCP":{
            "source_port":38148,
            "destination_port":10250,
            "flags":{
               "SYN":true
            }
         }
      },
      "source":{
         "identity":6,
         "labels":[
            "reserved:remote-node"
         ]
      },
      "destination":{
         "ID":519,
         "identity":49088,
         "namespace":"external-secrets",
         "labels":[
            "k8s:app.kubernetes.io/instance=external-secrets",
            "k8s:app.kubernetes.io/managed-by=Helm",
            "k8s:app.kubernetes.io/name=external-secrets-webhook",
            "k8s:app.kubernetes.io/version=v0.9.14",
            "k8s:helm.sh/chart=external-secrets-0.9.14",
            "k8s:io.cilium.k8s.namespace.labels.argocd.argoproj.io/instance=globalconfig",
            "k8s:io.cilium.k8s.namespace.labels.goldilocks.fairwinds.com/enabled=true",
            "k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=external-secrets",
            "k8s:io.cilium.k8s.policy.cluster=default",
            "k8s:io.cilium.k8s.policy.serviceaccount=external-secrets-webhook",
            "k8s:io.kubernetes.pod.namespace=external-secrets"
         ],
         "pod_name":"external-secrets-webhook-66c6d8c994-7rjrv",
         "workloads":[
            {
               "name":"external-secrets-webhook",
               "kind":"Deployment"
            }
         ]
      },
      "Type":"L3_L4",
      "node_name":"aks-spot-26938668-vmss00000p",
      "event_type":{
         "type":1,
         "sub_type":133
      },
      "traffic_direction":"INGRESS",
      "drop_reason_desc":"POLICY_DENIED",
      "Summary":"TCP Flags: SYN"
   },
   "node_name":"aks-spot-26938668-vmss00000p",
   "time":"2024-04-08T12:36:52.704115824Z"
}

Interestingly enough, I cannot relate that source IP (<IP_ADDRESS>) to any active pod.

That source IP is not present in the original sysdump, but if I had to guess I'd say this is the cilium_host (aka router) IP of a remote node (i.e. the IP that Cilium uses internally for node-to-pod traffic).
This likely means that traffic from the apiserver to the webhook is tunneled through something running in the host network namespace of a remote node (on AKS, probably tunnel-front or aks-link). In that case, you will not be able to use fromEntities: [kube-apiserver], because the policy engine only observes the traffic once it already has been mangled by the AKS infrastructure.
Unless AKS/GKE somehow are able to tell Cilium that this traffic indeed came from the kube-apiserver, I don't think there is anything the Cilium policy engine can do to address this. I think your current workaround of allowing remote-node and/or konnectivity are the way to go.

You are correct, observing the CiliumNode, that IP is mentioned as CiliumInternalIP.
Given the rest of your explanation, I'll understand why your hands are tied in this regard. Thanks for looking into it, a remark of this limitation here may be appropriate.

This has been documented: https://github.com/cilium/cilium/pull/32464
Closing, as we don't have any good way of fixing this in Cilium at the moment.


Exception in thread "Thread-8" java.lang.UnsatisfiedLinkError: no Microsoft.CognitiveServices.Speech.java.bindings in java.library.path

For SDK Java windows10 x64.
Using both netbeans and eclipse for building.
Trying to execute the jar file after build am getting this error message what could be the issue please
Knowing that the execution works fine without building the app

Facing same issue .

The current version of the Speech SDK for Java only supports 64bit JVM configurations.
Could you please execute:
java -version
and make sure it provides a "64-Bit* VM".
sometimes, it is necessary to add the following switch when calling the java executable:
java -d64 OTHER_OPTIONS

these are the results

The error message indicates that your jvm does not support 64-bit mode.
Please install a 64-bit version of your jvm. The Speech SDK currently does not support 32-bit configurations.

Alright thank you so much fmegen it worked well when changing to 64-bit jvm.
For people facing this too & wo don't know how to download it you can download the 64-bit jvm from here  directly :
https://java.com/fr/download/manual.jsp

Just one other question plz regarding this cuz we are at the point of making a choice btw java & c# sdks , wich one is best for windows 7+ or these versions are not supported at all for both c# and java ?


Formalize ENSIP-16 v2

Feature Request
During the implementation of the ENSIP-16 on the contracts and gateway side, some changes were required to have a more effective integration and usage of the data returned on the graphQL API.
Describe Preferred Solution
Summarize all changes made and integrate them with the External Resolver dApp.

https://www.notion.so/blockful/ENSIP-16-b6a519e7d09047d2862bf5df17f088a5

The backend implementation resulted in these changes to the specification, but surely there will be more changes when the Nameful dapp integrates with it.


New version: francWhite.reportify version 1.0.1

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Manual Validation ended with:

11:23:42 AM:  > 2023-10-26 11:23:41.846 [FAIL] Installer failed security check. Url: https://github.com/francWhite/reportify/releases/download/v1.0.1/reportify-v1.0.1-win-x64.zip Result: 0x80004005

This is similar to a Defender error. It might be a false positive and we can retry tomorrow.

Thank you for the information about the pipeline error. I'm closing this pullrequest because I already have a new release coming anyway. If the application still will trigger a Defender error, I will submit the exe to Microsoft as false positive.


Copilot - No "on behalf of" header for expense preview

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.41-2
Reproducible in staging?: Y
Reproducible in production?: N/A Unable to check
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Issue found when executing PR https://github.com/Expensify/App/pull/48594
Action Performed:
Precondition:

Log in as a copilot

Go to staging.new.expensify.com
Go to Account settings
Click on the account switcher
Select the other account that user has full access to
Go to DM
Split an expense

Expected Result:
There will be "on behalf of" header for the split preview and expense preview
Actual Result:
"on behalf of" header is only present for the split preview but not expense preview
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/9ba73d6e-3543-4d0d-a28c-fd8dba0d4906
View all open jobs on GitHub

We think that this bug might be related to #wave-control

Not. web-E blocker

Yeah I think that's right, we can close this. cc @dylanexpensify


Increase QPS limits to reduce client throttling in e2e tests?

I often see the following log messages in Antrea e2e test logs, especially when testing batch Pod creation and during NetworkPolicy tests.
I0528 05:44:56.035333   18605 request.go:668] Waited for 1.116069008s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:37891/api/v1/namespaces/x/pods?labelSelector=pod%!D(MISSING)a
I0528 05:45:06.235328   18605 request.go:668] Waited for 11.315672535s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:37891/api/v1/namespaces/y/pods?labelSelector=pod%!D(MISSING)c

Maybe we should consider increasing QPS limits for the client used for testing. I see that the default values for client-go are 5 for QPS and 10 for burst<EMAIL_ADDRESS>While the K8s e2e framework seems to be using 20 for QPS and 50 for burst: https://github.com/kubernetes/kubernetes/blob/5e58841cce77d4bc13713ad2b91fa0d961e69192/test/e2e/framework/framework.go#L151-L159. It may be good to use the same values, it could help speed up the tests at the very least.

Can I take this? Looking to get involved in Antrea

@kloading yes that would be great! assigning the issue to you. thanks!


Reporting a vulnerability

Hello!
I hope you are doing well!
We are a security research team. Our tool automatically detected a vulnerability in this repository. We want to disclose it responsibly.  GitHub has a feature called Private vulnerability reporting, which enables security research to privately disclose a vulnerability. Unfortunately, it is not enabled for this repository.
Can you enable it, so that we can report it?
Thanks in advance!
PS: you can read about how to enable private vulnerability reporting here: https://docs.github.com/en/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository

Thanks for reaching out.
Please contact us via https://github.com/cdklabs/cdk-monitoring-constructs/blob/main/CONTRIBUTING.md#security-issue-notifications


TraceSource managed memory leak at create channel

When creating channels frequently (We do not use channel tracing)

objects live up to generation 2, and will live until memory pressure appears

workaround:
var noopTraceSource = new TraceSource("noop", SourceLevels.Critical);

var options = new MultiplexingStream.Options
{
   DefaultChannelTraceSourceFactoryWithQualifier = (id, s) => noopTraceSource
};

Thanks for calling this out. The behavior of the MultiplexingStream is by design. I certainly disagree with the design of TraceSourc adding itself to a static collection, but I wouldn't call it a leak since the memory is eventually collected according to the GC rules.


Bulk Export requests on non-existent Patient or Group resources generate 500 errors instead of 404 errors

Describe the bug
Invoking /Group/abc/$export or /Patient/$export?patient=abc when the resources Group/abc and Patient/abc do not exists will start a batch job that fails with a 500 error.  We would expect the request to fail with a 404.
Expected behavior
Throw "not found 404" when the target of a bulk export does not exist.

Fixed in #4890


notebooks with video link annotations. Lesson 8,9

pull request for merging annotated .ipynb files

We will have to park this one for now, since the video links aren't supposed to be shared before Jeremy releases the MOOC part 2 in a few months!
So save those and please re-submit when MOOC part 2 is public.
Also for the future PRs please don't mix different changes, this PR includes other changes, besides video links, including errors from some missing modules and probably unintentionally deleted cells. So do a careful review before making a submit.


Add active job subscriber

Dude... please, take a look at my response to your prior PR #212.

@benlovell Sorry, man! I thought that if I create PR in the fork, no one sees it.  Thank you for a link and feedback. I will follow contributing guide.


net: clean up port parsing

https://go-review.googlesource.com/#/c/19720/ updated the parsing of port numbers, but now it accepts
stuff starting with a `+' sign, like:
   net.Dial("tcp", "foo.com:+80")

Nobody ever told me why that should be allowed, but the CL was submitted anyway. Or I missed it, but I can't find it.
Investigate and ideally fix.
/cc @mikioh @msiebuhr

Yes, I will send a followup CL for better consistency. FWIW, unfortunately the following snippet works w/ CGO_ENABLED=1 older versions or GODEBUG=netdns=cgo newer versions.
package main

import "net"

func main() {
	for _, arg := range []string{"<IP_ADDRESS>:+0", "<IP_ADDRESS>:-0"} {
		ln, err := net.Listen("tcp", arg)
		if err != nil {
			println(err.Error())
			continue
		}
		println(ln.Addr().String())
		ln.Close()
	}
}

Probably we should make consistent representation on transport service names and literal port numbers in ABNF for Dial/Listen APIs before Go 1.

Okay, if +n worked before, we don't need to do anything here. Still weird, but yay compatibility.


bugfix: add a piece handler API for supernode

Ⅰ. Describe what this PR did
related PR #582
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Added
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

@lowzj All mentioned above have been updated. PTAL. Thanks.


Support for "sources" parameter in the add() and add_batch() methods in datasets.metric - SARI

Is your feature request related to a problem? Please describe.
The methods add_batch and add from the Metric class does not work with SARI metric. This metric not only relies on the predictions and references, but also in the input.
For example, when the add_batch method is used, then the compute() method fails:
metric = load_metric("sari")
metric.add_batch(
    predictions=["About 95 you now get in ."],
    references=[["About 95 species are currently known .","About 95 species are now accepted .","95 species are now accepted ."]])
metric.compute()
> TypeError: _compute() missing 1 required positional argument: 'sources'

Therefore, the compute() method can only be used standalone:
metric = load_metric("sari")
result = metric.compute(
    sources=["About 95 species are currently accepted ."],
    predictions=["About 95 you now get in ."],
    references=[["About 95 species are currently known .","About 95 species are now accepted .","95 species are now accepted ."]])
> {'sari': 26.953601953601954}

Describe the solution you'd like
Support for an additional parameter sources in the add_batch and add of the Metric class.
add_batch(*, sources=None, predictions=None, references=None, **kwargs)
add(*, sources=None, predictions=None, references=None, **kwargs)
compute()

Describe alternatives you've considered
I've tried to override the add_batch and add, however, these are highly dependent to the Metric class. We could also write a simple function that compute the scores of a sentences list, but then we lose the functionality from the original add and add_batch method.
Additional context
These methods are used in the transformers pytorch examples.

Hi, thanks for reporting! We can add a sources: datasets.Value("string") feature to the Features dict in the SARI script to fix this. Would you be interested in submitting a PR?

Hi Mario,
Thanks for your message. I did try to add sources into the Features dict using a script for the metric:
            features=datasets.Features(
                {
                    "sources": datasets.Value("string", id="sequence"),
                    "predictions": datasets.Value("string", id="sequence"),
                    "references": datasets.Sequence(datasets.Value("string", id="sequence"), id="references"),
                }
            ),

But that only avoids a failure in encode_batch in the add_batch method:
        batch = {"predictions": predictions, "references": references}
        batch = self.info.features.encode_batch(batch)

The real problem is that add_batch(), add() and compute() does not receive a sources param:
def add_batch(self, *, predictions=None, references=None):
def add(self, *, prediction=None, reference=None):
def compute(self, *, predictions=None, references=None, **kwargs)

And then, it fails:
TypeError: add_batch() got an unexpected keyword argument sources
I need this for adding any metric based on SARI or alike, not only for sari.py :)
Let me know if I understood correctly the proposed solution.

The Metric class has been modified recently to support this use-case, but the add_batch + compute pattern still doesn't work correctly. I'll open a PR.


'\0' is translated to incorrect f*

The rust character '\0' is translated as '\000' in f* which is rejected with unexpected char by f*.
Writing 0x00 as char works as a workaround.

Oh, it seems that it's a bug in the pretty printer of F*

I opened https://github.com/FStarLang/FStar/issues/3560 on F*. But this will likely be fixed by #942: with that, we won't use F* pretty printer anymore.

This was closed by #1147


Update formatting writing extension package.json

Using two spaces and a final newline is consistent with npm, and probably most projects.
This is relevant, because __metadata is written when running VSCode extension tests.
Refs #148975

This does not seem right to me. Depending on internals can break things at anytime. This was mentioned in the issue already.

Sorry, but I don’t see how this is about “Depending on internals”. This is about VSCode altering extension source code when running tests. It’s not some weird test, it’s the official test example test script that modifies package.json.
For reference, this is the code that modifies package.json:
import { runTests } from '@vscode/test-electron';

await runTests({ extensionDevelopmentPath, extensionTestsPath });

This is also an open question in https://github.com/microsoft/vscode/issues/148975#issuecomment-1151207887, the issue was closed and the question went unanswered

It’s easily reproducible using vscode-remark, which is a very small extension. Its code doesn’t touch package.json.
Just clone the project, and reset to the commit before __metadata was added, dun npm install to setup the project:
git clone git@github.com:remarkjs/vscode-remark.git
cd vscode-remark
git reset --hard a22113963d07ac0d0a408c93db5b1d06a3e7016b
npm install

Now run tests:
npm test

Now notice __metadata was added and package.json has been reformatted. This doesn’t happen consistently, so you may need to run npm test a couple of times.


Typing two intellisense triggering character fast will cause completion list not showing up

Type in a normal speed:
Write-Host "C:
Expected: It should show the completion list.
Actual: No completion list shows though status bar indicates it seems having triggered IntelliSense

Potential same root cause as #109?

This one should have been covered in racing condition fix. @AndreSayreMSFT @EricMSFT

Agreed.  Closing this out.


Added YLab project to "in the wild"

YLab uses Embassy

https://github.com/schmettow/ystudio either doesn't exist or isn't public


Added Yow Brisbane 2017 and AISA Cyber Conference

Added Brisbane Yow from December, apparently we had 2  and AISA Security Conference for next year October

Hey @turagittech,
Your PR ran into conflict because after you created it, this PR was merged to master.
It contained quite a few changes which prevented Git from being able to apply your changes on top of these ones.
I resolved the conflicts.
Could you please double-check that it's fine so we can merge it?


ktp.next() for keys

As discussed in https://github.com/lowRISC/ot-sca/pull/115 and https://docs.google.com/document/d/1sZjASiUji_IT-t9jEFlK-kGc_Gw3mGfubNvpkM_IQT4/edit#heading=h.qd65x0y76b0e we should check the usage of key, text = ktp.next()  in cw/capture.py
Default behavior is that  ktp.next() returns const_key, random_plaintext. This default behavior can be changed with ctx.obj.ktp.fixed_key = False.
Afaik, we call ktp.next()[0] only once per function and use only the first call of the iterator to assign a constant key. For random keys we use ktp.next()[1]. Thus, I think we ware fine and can change the default behavior, but we should double check that and read the spec if the first call of the iterator still outputs a deterministic value. On the other hand, if we really rely on a constant non random value, we should use a constant and not a constant iterator.

backlog: With ctx.obj.ktp.fixed_key = False the internal lfsr is iterated twice per ktp.next(). This must be taken into account when using the batch-mode and thus, the lfsr on device side.
Possible solutions:

perform a dummy iteration on the device
use ktp.next_key() and ktp.next_text() instead of ktp.next()[0] and ktp.next()[1]

For otbn we are using the second solution. See https://github.com/lowRISC/opentitan/pull/17416 and https://github.com/lowRISC/ot-sca/pull/128 It's running smoothly, while the dummy iteration on the device creates a significant overhead.

The behaviour/use of the host-side PRNG is hard to understand for reasons described here.
Latest host-side batch capture implementation: https://github.com/lowRISC/ot-sca/pull/197
Does not use ktp.next().
PRNG likely replaced in future, hence deprioritizing this issue.


Logout url for a registered service

Handles https://github.com/Jasig/cas/issues/579
The roadmap proposes a separate logout url for every service as an optional setting. This is a url that is configured in the service registry that would receive logout requests. In the absence of this configuration, the original will be used.

Changeset seem ok to everyone? @leleuj ?

I just took a quick look. Are we sure we want to override the default logout url with a specific one for the back channel SLO?

I thought we were only targeting the front channel communication with this new specific logout url.

The same rationale applies to both front/back channel logins. A specific endpoint to receive a logout message is the same regardless of how that message is sent to that endpoint.

Yes, but I'm not sure it makes sense to have a specific url where to send CAS logout requests (instead of the service url). Which CAS client would work that way?
From my point of view, the specific logout url was only for front-channel and only to receive simple GET requests (like reusing the /j_spring_security_logout url from Spring Security).

cases where there is no cas client, or cases where the application would explicitly rather handle logout requests at an endpoint. if the application does not wish to rely on a cas client to intercept logout requests, it makes sense for those requests to be sent to a place where the app can process its own session clean up and perhaps other housekeeping tasks it needs to do before fulling voiding the session space.

Separating functionality like that would be confusing. Either there is a logout endpoint for the service to receive requests or there is none. If there is, those requests can either be sent via front or back channel. This to me is clear to understand, rather than to try and pick which url/setting would used when, etc.

Most CAS clients implement the back-channel logout mechanism. I don't see any need for a  specific logout url where applications would manage by themselves the CAS logout requests, which would not be that easy.
But for front-channel logout, many applications have created their own logout url like this logout.jsp:
<%
session.invalidate();
%>
Or endpoints for logout are available in proprietary software.
And this does not work with the CAS server. So my idea was to add a specific logout url so that the CAS server can call it. In addition to a more evolved front-channel mechanism which can be implemented later  on by CAS clients.

So what happens if I have:

No CAS client implemented to work with (and no possibility of using one)
Wish to receive logout request at a different endpoint than the service url because I have a custom servlet that does invalidate my session, calls my database, emails person X and rings the doorbell when a request comes :)

Will I have to change my settings from back-channel calls to front-channel, only to get a new url receptor and go through the browser to accept the request? What will have to change on the application side?

In my view, these two settings are completely separate and I would like to keep them as consistent as possible. Here's the story you'd write in docs:

Logout requests by default are sent to the service url
Optionally, you can change that behavior so they are sent to a new url endpoint

That's it. You will have then accommodated all possible scenarios. Because:

those who have implemented the client on the app side will simply set their config to back-channel and be happy.
those who have not implemented the client on the app side and wish to use back-channel with a custom url, will simply set their config to back-channel, a custom url and be happy.
those who have not implemented the client on the app side and wish to use fron channel will simply set their config to back-channel, a custom url and be happy.

It would also be easier on the service registry model, because if you are going to exclusively limit the logout url to front-channel, then we'd have to refactor the service registry to make sure configuration is relevant. Something like this:
LogoutStrategy:
- NoLogoutStrategy
- BackChannelLogoutStrategy
- FrontChannelLogoutStrategy
- ....Logout Url

and remove the enum.

You're right: it will be easier to have a consistent behaviour even if most deployments don't need the CAS logout request itself (but just the call),

Updated pull.

+1


RAS-1105 Update email-validator

What and why?
There is a vulnerability in Dnspython 2.5.0 which is used by email-validator, update email-validator to 2.1.1 which update Dnspython to 2.6.0
How to test?
Make sure tests pass and everything works as before
Jira

/deploy robinm3


#306 Injectable configuration format parsers

In short this PR introduces interface:
public interface ConfigurationFormatParser {
   JsonNode parse(InputStream stream);
   boolean shouldParse(URL url, String contentType);
}

and a new injection point in the BQCoreModuleExtender:
addConfigFormatParser(Class<? extends ConfigurationFormatParser> parserType)

This is good refactoring on its own, even aside from the Kotlin aspect. Merged.


Internal structure gets corrupted while parsing

I've two json files. One is stored using ASCII encoding and other is stored using UTF-8 encoding without BOM (using Notepad++'s encoding feature). When I load the UTF-8 file using json.hpp, its internal structure looks corrupted (very large array sizes) and you will see crash trying to read any of elements. The ASCII encoding seems to work fine. However the thing is that there are non-ASCII chars in the content.
Attached is the very small json file I'm trying to read.
settings.zip

The library fully supports UTF-8, and I can parse the file without problems:
#include "json.hpp"
#include <fstream>

using json = nlohmann::json;

int main()
{
    std::ifstream f("settings.json");
    json j = json::parse(f);
    std::cout << std::setw(2) << j << std::endl;
}

output:
{
  "Pixhawk": {
    "LocalHostIp": "<IP_ADDRESS>",
    "LogViewerHostIp": "<IP_ADDRESS>",
    "LogViewerPort": 14388,
    "Model": "Flamewheel",
    "OffboardCompID": 1,
    "OffboardSysID": 134,
    "QgcHostIp": "<IP_ADDRESS>",
    "QgcPort": 14550,
    "SerialBaudRate": 115200,
    "SerialPort": "*",
    "SimCompID": 42,
    "SimSysID": 142,
    "SitlIp": "<IP_ADDRESS>",
    "SitlPort": 14556,
    "UdpIp": "<IP_ADDRESS>",
    "UdpPort": 14560,
    "UseSerial": true,
    "VehicleCompID": 1,
    "VehicleSysID": 135
  },
  "RpcEnabled": false
}

The file does not contain any non-ASCII byte.
Can you provide more information?

I'm not able to reproduce this now so closing the issue. If I see this again, I'll re-open.

Ok. Thanks for checking back!

Hello, guys! Got exactly the same issue :)
Parses perfectly on Windows, but crashes on Ubuntu. After parsing an object, is_object() returns false, while is_array() returns true. No exception on parsing, but exception on getting access to parsed fields.
config.zip

Spent an hour :)
Even this do not work on Ubuntu: json jsonObj{ json_t::parse("{"x": "y"}") };

OMG...
json jsonObj{ json_t::parse("{"x": "y"}") }; - works fine on Windows with latest VS2017
json jsonObj = json_t::parse("{"x": "y"}"); - only such a variant works on Ubuntu with gcc -std=c++1y
Looks like different compilers chose different (copy?)constructors or something like that around initializer's list. Just WOW!

I'll have a look.

Thank you! BTW: Amazing lib! ;)

Sorry, for annoying, start from here:
class A
{
public:
A()
{
std::cout << "A()" << std::endl;
}
A(std::initializer_list list)
{
std::cout << "A(std::initializer_list list)" << std::endl;
}
A(const A& a)
{
std::cout << "A(const A& a)" << std::endl;
}
};
int main(int argc, char* argv[])
{
A a1;
A a2 = a1;
A a3{ a1 };
return 0;
}
Windows:
A()
A(const A& a)
A(const A& a)
Ubuntu:
A()
A(const A& a)
A(const A& a)
A(std::initializer_list list)

@sedapsfognik :

json jsonObj{ json_t::parse("{"x": "y"}") }; - works fine on Windows with latest VS2017
json jsonObj = json_t::parse("{"x": "y"}"); - only such a variant works on Ubuntu with gcc -std=c++1y

gcc has had problems with the unified initializer construct.  Although I thought that with version 7, it properly handled most of the legal constructs that clang/llvm and MSVS have been able to handle for years.
Also for the fun of it, is there any difference when you specifically use g++ instead of gcc for the command line?  I know that there are cases where clang will do something a little differently than clang++.

I can confirm that Clang and GCC (I tried version 5 to 8) behave differently when it comes to these lines:
json j1{ json::parse("{\"x\": \"y\"}") };
json j2 = json::parse("{\"x\": \"y\"}");

In all cases, j1 is returned as an array containing {"x":"y"}, whereas j2 is just the object {"x":"y"}.
I think there is nothing I can do from the library side.


Error running kitchen converge

Getting this when running converge:
       Running handlers:
       Running handlers complete
       Chef Client finished, 169/222 resources updated in 02 minutes 57 seconds
       Finished converging <cluster-native-ose12-centos-72> (3m37.12s).
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: 5 actions failed.
>>>>>>     Converge failed on instance <standalone-ose14-centos-72>.  Please see .kitchen/logs/standalone-ose14-centos-72.log for more details
>>>>>>     Converge failed on instance <cluster-native-ose14-centos-72>.  Please see .kitchen/logs/cluster-native-ose14-centos-72.log for more details
>>>>>>     Converge failed on instance <standalone-ose13-centos-72>.  Please see .kitchen/logs/standalone-ose13-centos-72.log for more details
>>>>>>     Converge failed on instance <cluster-native-ose13-centos-72>.  Please see .kitchen/logs/cluster-native-ose13-centos-72.log for more details
>>>>>>     Converge failed on instance <standalone-ose12-centos-72>.  Please see .kitchen/logs/standalone-ose12-centos-72.log for more details
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

What can you see in the logs @ianmiell?

Looks like the fourth time it's getting further. I'm wondering whether it
was due to resource constraints.
I'll get back.
On Mon, Feb 27, 2017 at 10:00 AM, Julien Pervillé<EMAIL_ADDRESS>wrote:

What can you see in the logs @ianmiell https://github.com/ianmiell?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IshentRas/cookbook-openshift3/issues/88#issuecomment-282676715,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGrczdP-OPjSbr9dKo5TqGHSi52qIJ9Gks5rgp6qgaJpZM4MM5K3
.

--
My book on Docker in Practice: Get 39% off with the code 39miell
http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62

6 suites, 1.5 Gb each, you need 9 Gb memory to converge the 6 suites at the time time. Or use kitchen test --concurrency=1 to do in sequence.

I think I need a bigger boat.
On Mon, Feb 27, 2017 at 10:03 AM, Julien Pervillé<EMAIL_ADDRESS>wrote:

6 suites, 1.5 Gb each, you need 9 Gb memory to converge the 6 suites at
the time time. Or use kitchen test --concurrency=1 to do in sequence.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IshentRas/cookbook-openshift3/issues/88#issuecomment-282677554,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGrczdW8AI9ZFryDBzMrkOXmCEW9EGGrks5rgp92gaJpZM4MM5K3
.

--
My book on Docker in Practice: Get 39% off with the code 39miell
http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62

You can run the suites explicitly if you want to save resources. for example:
$ kitchen list
Instance                        Driver   Provisioner  Verifier  Transport  Last Action    Last Error
standalone-ose14-centos-72      Vagrant  ChefZero     Inspec    Ssh        <Not Created>  <None>
cluster-native-ose14-centos-72  Vagrant  ChefZero     Inspec    Ssh        <Not Created>  <None>
standalone-ose13-centos-72      Vagrant  ChefZero     Inspec    Ssh        <Not Created>  <None>
cluster-native-ose13-centos-72  Vagrant  ChefZero     Inspec    Ssh        <Not Created>  <None>
standalone-ose12-centos-72      Vagrant  ChefZero     Inspec    Ssh        <Not Created>  <None>
cluster-native-ose12-centos-72  Vagrant  ChefZero     Inspec    Ssh        <Not Created>  <None>
$ for i in standalone-ose14-centos-72 cluster-native-ose14-centos-72 ; do kitchen converge $i && kitchen verify $i && kitchen destroy $i ; done

I have a bigger boat now, but want to get the Jenkinsfile process working first.

Done.

Cool (y)


not running on windows

2024-10-27 19:41:21 exec ./entrypoint.sh: no such file or directory

same here

+1

+1

Run find . -type f -print0 | xargs -0 dos2unix and rerun docker run,
Ranting: I do not know who high engineer(rocket scientist) decided to ignore this, but when we give sh file with windows end of lines that is creating the problem in docker, they should have done dos2unix before creating the docker container in windows docker, or at least give meaningful error or at least a warning 😄 but noo, better to say file not found

@ozkanpakdil Thankyou brother

I managed to run it on windows by doing

docker run -e ANTHROPIC_API_KEY=sk-ant-apiXX-YOURKEYYYYYYYYYY -v %USERPROFILE%.anthropic:/home/computeruse/.anthropic -p 5900:5900 -p 8501:8501 -p 6080:6080 -p 8080:8080 -it ghcr.io/anthropics/anthropic-quickstarts:computer-use-demo-latest

Proof:


goerli: can't click on the shark model

Explorer Alpha build version:
0.3.402-g7a23dc7e-main
Issue Description:

/goto 73,-8 The shark should play a bite animation when clicked, but it's not possible to do so at the moment. The GLTFShape is configured to use the visible mesh as the collider.
Evidence:

Additional Notes:

The object has no collider! Its not an input issue


Issue with platforms

Hello,
I am having the following issue:
+ read file
+ find temp_build/ -name '*.tar.bz2'
+ echo temp_build/noarch/premise-0.4.2-0.tar.bz2
+ for PLATFORM in "${PLATFORMS[@]}"
temp_build/noarch/premise-0.4.2-0.tar.bz2
+ conda convert --force --platform osx-64 temp_build/noarch/premise-0.4.2-0.tar.bz2 -o temp_build/
Traceback (most recent call last):
  File "/opt/conda/bin/conda-convert", line 11, in <module>
    sys.exit(main())
  File "/opt/conda/lib/python3.7/site-packages/conda_build/cli/main_convert.py", line 131, in main
    return execute(sys.argv[1:])
  File "/opt/conda/lib/python3.7/site-packages/conda_build/cli/main_convert.py", line 127, in execute
    api.convert(f, **args.__dict__)
  File "/opt/conda/lib/python3.7/site-packages/conda_build/api.py", line 300, in convert
    dry_run=dry_run, dependencies=dependencies)
  File "/opt/conda/lib/python3.7/site-packages/conda_build/convert.py", line 763, in conda_convert
    conversion_platform, source_platform, architecture = retrieve_package_platform(file_path)
  File "/opt/conda/lib/python3.7/site-packages/conda_build/convert.py", line 69, in retrieve_package_platform
    if platform.startswith('linux') or platform.startswith('osx'):
AttributeError: 'NoneType' object has no attribute 'startswith'

when using:
- name: Publish distribution 📦 to Anaconda if Push
        uses<EMAIL_ADDRESS>        with:
          # CondaDir: locate the directory containing your meta.yml, conda_build_config.yaml (...) files
          CondaDir: 'conda'
          # Channels: You can add more channel with a space separator
          Channels: 'conda-forge'
          # Platforms: remove one or more of these platforms
          Platforms: 'osx-64 linux-32 linux-64 win-32 win-64'
          CondaUsername: ${{ secrets.CONDA_USERNAME }}
          CondaPassword: ${{ secrets.CONDA_PASSWORD }}

Should I modify the list of platforms?
Thanks.

For information, I tried with:
Platforms: 'win-64' and also without the 'Platforms' argument, the result is the same.
And my conda meta.yaml is here.

Hello,
Your configuration looks like good.
All your librairies can be found on conda? Dependencies issues?

Not that I could see.
Finally, I resorted to writing a conda script for the upload.
If no one had that error before me, the issue was probably on my end.
Thanks for the help anyway.


Q> js.map routing errors w/ searchkit

I'm trying to use https://github.com/searchkit/searchkit with react_on_rails everything works apart from I'm getting a bunch of ActionController::RoutingError on .js.map files which exist within the npm package:
ActionController::RoutingError (No route matches [GET] "/assets/ValueState.js.map")
ActionController::RoutingError (No route matches [GET] "/assets/ViewSwitcherToggle.js.map")
etc... loads of these
I've followed the same setup as the boilerplate they provide at https://github.com/searchkit/searchkit-boilerplate but I get these routing errors anyone know whats up?
Why is it looking in the assets folder for the .js.map files when they exist within the node package

You should just add these files to public/assets for now.
If you want to go down the rabbit hole (and maybe submit a PR on this that helps everybody):

http://guides.rubyonrails.org/asset_pipeline.html
You set the destination directory in your webpack file, and those files get copied by Rails during deployment: https://github.com/shakacode/react_on_rails/blob/master/docs/additional-reading/rails-assets.md

Also, keep in mind the differences between development and production deployments.
Good luck. Keep us posted.
And feel free to request to re-open this issue.


Define version in fairing package

Should we define "fairing.version" so people can easily tell what version of fairing they have installed?
This might be useful for customer support; e.g. asking what version a user is using.

@karthikv2k Can we close this issue?


Failed to send commit transaction

error: Failed to send commit transaction
because: JSON-RPC error: RPC error response: RpcError { code: -26, message: "non-mandatory-script-verify-flag (Witness program was passed an empty witness)", data: None }
I will report this error when I cast the inscription

same

Happened to have this problem too with my ord wallet under ord 0.16.0, I don't know what's going on under the hood, but here's how I solved the problem:

remove the ord wallet which would be located under bitcoin core data dir
restore ord wallet with ord wallet restore --from-mnemonic
then try to inscribe again


V3

TODO:
Pre-API3:

Decide whether Specification.Image should be structured, like dockerImage{}
Perhaps move template-specifications into their own package? (templates?)
Alternatively, flesh out a pure factory-driven model with version-checks.
Should SetUp{Postgre,MySQL}Database really be a part of dockertest?

Whenever:

Reimplement DockerMachine and LocalDocker into separate Runners, autodetected during package load
? Perhaps should affect the API, moving options etc into the implementations rather than the globals?
Implement Docker Swarm as a runner

Thanks :raised_hands:


Getting blank screen with the latest flet install

Can you try it again now after the new release? Also please share the error message if there is one.

I think there's an error in the code on your homepage. I had to change the example from the line:
ft.flet.app(target=main)
to:
ft.app(target=main)
In order to make it work.


Add are-users-rejecting-bitcoin-forks to bitcoin-magazine/bitcoin-explained

This PR adds Are Users Rejecting Bitcoin Forks??? transcript to the bitcoin-magazine/bitcoin-explained directory.

Great addition of chapters and extra links! Thanks for the contribution @Radiokot!


help me

I installed PteroVM and got stuck at -----> VPS HAS STARTED <----

Can't install anything via pterosaur panel command line


land_detector: fix uninitialized value

Found with valgrind in SITL:
==6033== Thread 4 hpwork:
==6033== Conditional jump or move depends on uninitialised value(s)
==6033==    at 0x48188F: landdetection::MulticopterLandDetector::get_landed_state() (MulticopterLandDetector.cpp:167)
==6033==    by 0x481A89: landdetection::MulticopterLandDetector::update() (MulticopterLandDetector.cpp:118)
==6033==    by 0x481277: landdetection::LandDetector::cycle() (LandDetector.cpp:106)
==6033==    by 0x43D0FC: work_process (work_thread.c:148)
==6033==    by 0x43D14C: work_hpthread (work_thread.c:269)
==6033==    by 0x43C6EE: entry_adapter(void*) (px4_posix_tasks.cpp:104)
==6033==    by 0x4E3F6A9: start_thread (pthread_create.c:333)
==6033==    by 0x59EF13C: clone (clone.S:109)
==6033==

@tumbili FYI.

Yuck, that was me. Thanks!