Add Programming Language Specific Awesome Security Resources

This PR contains a bunch of lists:

https://github.com/guardrailsio/awesome-php-security
https://github.com/lirantal/awesome-nodejs-security
https://github.com/guardrailsio/awesome-golang-security
https://github.com/pxlpnk/awesome-ruby-security
https://github.com/guardrailsio/awesome-python-security
https://github.com/guardrailsio/awesome-dotnet-security
https://github.com/guardrailsio/awesome-java-security

Explain what this list is about and why it should be included here
Theses lists contain programming language specific awesome security resources, with a focus on application security.
Requirements for your pull request
You have to review at least 2 other [open pull requests]

PR 1538
PR 1541

(https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.

I have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/master/create-list.md).
This pull request has a descriptive title in the format Add Name of List (Example: Add Swift), not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

For https://github.com/guardrailsio/awesome-golang-security/issues/1.

One list suggestion per PR. Also make sure the list you submit follow all the guidelines in https://github.com/sindresorhus/awesome/blob/master/pull_request_template.md


Release<PHONE_NUMBER>-public Images Might be Wrong

Describe the bug
Hey guys, I'm here again.
This time, I noticed that the latest release<PHONE_NUMBER>-public) might not be built correctly -- When I deployed it, I saw that all the services that were meant to have new features, such as ngui, rest_api and herald, stayed exactly the same as before.
I created a new EC2 and did all the deployment again, from zero. The results were the same. I then cloned the repository with the latest changes and started ngui in local environment since I knew I could test my theory using the email verification workflow and, comparing the local ngui with the<PHONE_NUMBER>-public image, I instantly noticed that the cluster one didn't have the email verification workflow. Besides that, when I invoked verify_email using postman or the local ngui, it returned 404 as this image of rest_api also weren't updated yet.
P.S.: I also tried using the docker hub images directly (i.e.: hystax/rest_api:2024112501-public) since I wanted to rule out a possible issue with the deployment method, but got the same results.
I think the whole release might be compiled in a repo that didn't fetch the latest commits
To Reproduce
Steps to reproduce the behavior:
sudo su
apt update; apt install python3-pip sshpass git python3-virtualenv python3.9 python3.9-venv awscli -y

git clone https://github.com/hystax/optscale.git
cd optscale/optscale-deploy

virtualenv -p python3.9 venv
source venv/bin/activate
pip install -r requirements.txt

ansible-playbook -e "ansible_connection=local ansible_user=ubuntu" -i "<ip>," ansible/k8s-master.yaml

./runkube.py --with-elk -o overlay/user_template.yml -- optscale-deployment<PHONE_NUMBER>-public

Expected behavior
Upon deploying the<PHONE_NUMBER>-public release, all services (ngui, rest_api, herald, etc.) should include the latest features as per the recent commits
Screenshots

Fun fact
I spent almost 3 weeks trying to implement an email-verification workflow on OptScale, and after LOTS of struggles, I finally did it yesterday and it worked perfectly. It was beautiful! Then I noticed you did it about 4 days ago in this latest release 🫠
At least this experience has deepened my understanding on OptScale's structure and how to implement new ideas 🙂

Hi @GiovanniYuriMita, Email verification is not included in the release<PHONE_NUMBER>-public, the feature was merged later, on November 28th (https://github.com/hystax/optscale/commit/61300f60d00fb85389753e96ff0ccee5abdd8f5b). If you want to deploy the feature to a cluster, you can build images from the latest integration or from the commit I specified locally, using build.sh script in optscale repo and then start cluster with --no-pull flag and local as version


Window/Unix: Fix compilation with glxext header versions >=20180525

[x] Has this change been discussed on the forum or in an issue before?
[x] Does the code follow the SFML Code Style Guide?
[ ] Have you provided some example/test code for your changes?
[ ] If you have additional steps which need to be performed list them as tasks!

Description
When mesa updated their headers, they changed the include guard
from _glxext_h to _glx_glxext_h, which breaks compilation
due to conflicting declarations. This commit modifies the preprocessor
directives to allow for compilation with older and newer mesa header
versions.
Fixes: #1472
Tasks

[x] Tested on Linux
[ ] Tested on Windows
[ ] Tested on macOS
[ ] Tested on iOS
[ ] Tested on Android

How to test this PR?
Just trying to compile should be enough to test the PR on Linux with mesa should be enough. I tested it with the headers from mesa 18.1.6 and with headers from a current git mesa (9a96bf0ecd071219cb975fbd64f5c68849fd5697).

Merged in 87aaa9e145659d6a8fc193ab8540cf847d4d0def


add support for :ssl connections

closes #67
I thought this would be a more scary refactor but recently I was looking under the hood of mint and realized that :gen_tcp/:ssl/:inet are actually pretty friendly!
The basic idea is to do
transport_module =
  case transport do
    :tcp -> :gen_tcp
    :ssl -> :ssl
  end

(or :inet for tcp when setting the active: :once option)
and then you can use those modules are compatible for functions like send/2 and connect/4. I also removed the Extreme.Tcp module and moved that connect function over to Extreme.Connection since I think it fits better there now with ssl.
This is WIP as I try to figure out a good way to test it. One option is to do what we do in spear and use docker-compose to spin up some containers in CI (like so), but that can be a bit annoying because then you need docker-compose installed locally to test extreme. Maybe it makes sense to tag tests as @tag :ssl, exclude them by default, and have a separate Actions workflow for ssl tests? I'll think about it!

ok I think this is ready now: I ended up switching the ES 21.6.0 test to use SSL, and that also allows us to test @tag :authentication tests while we're on that version (since authentication is disabled when running in --insecure mode in v20+). I'm definitely open to other approaches (maybe a separate matrix thing for ssl?)
There was a little extra work I didn't catch on the first pass updating the call to :httpc.request/5 to use ssl as well but that's fixed now I believe.
I left the gossip test out since ex_vcr was unhappy with https and I'm not too familiar with ex_vcr.
The v21.10.0 LTS release is published to docker hub now so I'll be sure to follow up with a PR bumping the testing container to that version. (afaik there are no breaking changes that would affect extreme in 21.10.0.)

Hey @the-mikedavis , thanks a lot for this PR. I'll take a look at this one this week and I hope we'll have new version on hex next week. And thanks for hint for authentication and insecure ... It drove me crazy! :D


Can I work on your documentation?

Hey! 👋🏾
I'm Sunkanmi and I'm a Technical Writer looking to contribute to API documentation on Github. I want to know if I can submit a PR for a Swagger documentation for this API and help refine your Github readme as well.
Let me know if I can get started on this. :)
Hope to speak with you soon!

This is just a simple and repaired copy of the Gits https://github.com/cyanfish/python-lichess. Nothing more is being developed here. I check every now and then to see if the tool is still working. But not much will happen here.
If you want to help the Lichess API, have a look at much better projects like https://github.com/lichess-org/berserk


Additional German speech training data

Hey,
I'd like to bring to your attention the German corpus from our paper "CTC-Segmentation of Large Corpora for German End-to-end Speech Recognition". It consists of audiobooks from Librivox and a re-aligned spoken wikipedia corpus.
Sources and data an be found here:
https://github.com/lumaku/german-corpus-aligned
Tuda-DE and this dataset have a certain overlap.
Both contain the SWC. M-ailabs also contains a audiobooks from librivox.
Feel free to merge etc.!

We have now added Common Voice V8, bringing the total training data to a little over 1700 hours. We have a new WER record with the most recent model as well: 6.19% WER on Tuda Dev and 6.93% WER on Tuda Test :)


Manual model warmup to resolve AOT model warmup performance degradation

Use manual model warmup instead of AOT implemented model warmup, since with AOT, we observe performance degradation at higher batch size of maxtext configuration, mentioned in https://github.com/google/JetStream/pull/92:

OOM at higher batch size (after model warmup, during an active request)
Slower detokenizing generate step time exponentially at higher batch sizes

This has been verified that the detokenizing generate step time remains same as JetStream optimal behavior for all batch sizes.
curl --request POST --header "Content-type: application/json"
 -s localhost:8000/generate --data '{
    "prompt": "What are the top 5 programming languages",
    "max_tokens": 200
}'
{
    "response": " for data science in 2023?\n\n1. Python\n2. R\n3. SQL\n4. Java\n5. Scala\n\n**Note:** The order is based on popularity and demand in the data science industry in 2023."
}

Do we need to update unit tests?
Unit tests do not need to be updated because it is on the condition of engine.warm
QQ on the description,

we set the max pdbs when we start the server, this value should be within memory cap (based on calculation w the devices used), then it would not OOM right?
Yes, I think the storage of the compiled graphs from AOT and executing it from AOT is what takes up the memory. We observe the OOM at generate request.
Why higher actual batch size would have very slow detokenization? Could you share some investigation or profiles?
Yes, you can reference https://github.com/google/JetStream/pull/92 for some investigations. Also shared the doc internally.

ified that the detokenizing generate step time remains same as JetStream optimal behavior for all batch sizes.

Did you figure out what is the root cause of  performance issue and OOM for AOT?

ified that the detokenizing generate step time remains same as JetStream optimal behavior for all batch sizes.

Did you figure out what is the root cause of performance issue and OOM for AOT?

RCA has been attempted and the root cause of OOM can potentially be the added space to save the compiled graphs in executables alongside saving the cache in the compilation cache directory. The performance issue, has not been concluded. Could be unoptimal AOT executables. I can share the investigation offline


Error in Nuxt 3.4.3 when upgrading Pinia to 2.1.3 (from 2.0.36) - Internal Server error

Reproduction
No reproduction
Steps to reproduce the bug
After upgrading Pinia module in Nuxt 3.4.3 to Pinia version 2.1.3 (from version 2.0.36)
we get this error message :
The requested module 'vue-demi' does not provide an export named 'hasInjectionContext'            12:31:39 AM
at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
Expected behavior
when running in app in dev mode (npm run dev) that application should open in browser
Actual behavior
Resulting in application does not open in browser.
Additional information
When uninstalling Pinia and forcing back to version 3.0.36 problem is resolved.

see same problem
https://stackoverflow.com/questions/76295214/getting-500-internal-server-error-for-nuxt-3-and-pinia

As pointed ou in other issues, you need to upgrade Vue to 3.3

Please, search existing issues and pull requests before opening issues, it saves maintainers a lot of time 🙏


[Suggestion] Use GPT-Neo/GPT J as replacement for GPT3.

Goose AI offers API services for GPT Neo/GPT J and its much cheaper than OPEN AI. I don't  have much experience on LLMs and I think the AI will be more based and sassy as I've seen from YouTube videos. Not familiar on how to setup filters for words and topics the AI will avoid.

Whats the code to do that exactly?

i use bard instead of chat gpt

What are the beneifits? @meet447

What are the beneifits? @meet447

You don't need api key

https://github.com/meet447/MeuxVtuber
Check this out you don't need any api keys to use this @Sylensar

@meet447 how to use bard for Koischizo repository?


Release v2.1.0

Part of https://github.com/ZcashFoundation/zebra/issues/8997.
Prepare for the Release

[x] Make sure there has been at least one successful full sync test in the main branch since the last state change, or start a manual full sync.
[x] Make sure the PRs with the new checkpoint hashes and missed dependencies are already merged.
(See the release ticket checklist for details)

Summarise Release Changes
These steps can be done a few days before the release, in the same PR:
Change Log
Important: Any merge into main deletes any edits to the draft changelog.
Once you are ready to tag a release, copy the draft changelog into CHANGELOG.md.
We use the Release Drafter workflow to automatically create a draft changelog. We follow the Keep a Changelog format.
To create the final change log:

[x] Copy the latest draft changelog into CHANGELOG.md (there can be multiple draft releases)
[x] Delete any trivial changes

[x] Put the list of deleted changelog entries in a PR comment to make reviewing easier

[x] Combine duplicate changes
[x] Edit change descriptions so they will make sense to Zebra users
[x] Check the category for each change

Prefer the "Fix" category if you're not sure

README
README updates can be skipped for urgent releases.
Update the README to:

[x] Remove any "Known Issues" that have been fixed since the last release.
[x] Update the "Build and Run Instructions" with any new dependencies.
Check for changes in the Dockerfile since the last tag: git diff <previous-release-tag> docker/Dockerfile.
[x] If Zebra has started using newer Rust language features or standard library APIs, update the known working Rust version in the README, book, and Cargo.tomls

You can use a command like:
fastmod --fixed-strings '1.58' '1.65'

Create the Release PR

[x] Push the updated changelog and README into a new branch
for example: bump-v1.0.0 - this needs to be different to the tag name
[x] Create a release PR by adding &template=release-checklist.md to the comparing url (Example).
[x] Freeze the batched queue using Mergify.
[x] Mark all the release PRs as Critical priority, so they go in the urgent Mergify queue.
[x] Mark all non-release PRs with do-not-merge, because Mergify checks approved PRs against every commit, even when a queue is frozen.
[x] Add the A-release tag to the release pull request in order for the check_no_git_refs_in_cargo_lock to run.

Zebra git sources dependencies

[x] Ensure the check_no_git_refs_in_cargo_lock check passes.

This check runs automatically on pull requests with the A-release label. It must pass for crates to be published to crates.io. If the check fails, you should either halt the release process or proceed with the understanding that the crates will not be published on crates.io.
Update Versions and End of Support
Update Zebra Version
Choose a Release Level
Zebra follows semantic versioning. Semantic versions look like: MAJOR.MINOR.PATCH[-TAG.PRE-RELEASE]
Choose a release level for zebrad. Release levels are based on user-visible changes from the changelog:

Mainnet Network Upgrades are major releases
significant new features or behaviour changes; changes to RPCs, command-line, or configs; and deprecations or removals are minor releases
otherwise, it is a patch release

Zebra's Rust API doesn't have any support or stability guarantees, so we keep all the zebra-* and tower-* crates on a beta pre-release version.
Update Crate Versions
If you're publishing crates for the first time, log in to crates.io,
and make sure you're a member of owners group.
Check that the release will work:

[x] Update crate versions, commit the changes to the release branch, and do a release dry-run:

# Update everything except for alpha crates and zebrad:
cargo release version --verbose --execute --allow-branch '*' --workspace --exclude zebrad --exclude zebra-scan --exclude zebra-grpc beta
# Due to a bug in cargo-release, we need to pass exact versions for alpha crates:
cargo release version --verbose --execute --allow-branch '*' --package zebra-scan 0.1.0-alpha.4
cargo release version --verbose --execute --allow-branch '*' --package zebra-grpc 0.1.0-alpha.2
# Update zebrad:
cargo release version --verbose --execute --allow-branch '*' --package zebrad patch # [ major | minor | patch ]
# Continue with the release process:
cargo release replace --verbose --execute --allow-branch '*' --package zebrad
cargo release commit --verbose --execute --allow-branch '*'

Crate publishing is automatically checked in CI using "dry run" mode, however due to a bug in cargo-release we need to pass exact versions to the alpha crates:

[x] Update zebra-scan and zebra-grpc alpha crates in the release-crates-dry-run workflow script
[x] Push the above version changes to the release branch.

Update End of Support
The end of support height is calculated from the current blockchain height:

[x] Find where the Zcash blockchain tip is now by using a Zcash Block Explorer or other tool.
[x] Replace ESTIMATED_RELEASE_HEIGHT in end_of_support.rs with the height you estimate the release will be tagged.

Optional: calculate the release tagging height

Add 1152 blocks for each day until the release
For example, if the release is in 3 days, add 1152 * 3 to the current Mainnet block height

Update the Release PR

[x] Push the version increments and the release constants to the release branch.

Publish the Zebra Release
Create the GitHub Pre-Release

[ ] Wait for all the release PRs to be merged
[ ] Create a new release using the draft release as a base, by clicking the Edit icon in the draft release
[ ] Set the tag name to the version tag,
for example: v1.0.0
[ ] Set the release to target the main branch
[ ] Set the release title to Zebra  followed by the version tag,
for example: Zebra 1.0.0
[ ] Replace the prepopulated draft changelog in the release description with the final changelog you created;
starting just after the title ## [Zebra ... of the current version being released,
and ending just before the title of the previous release.
[ ] Mark the release as 'pre-release', until it has been built and tested
[ ] Publish the pre-release to GitHub using "Publish Release"
[ ] Delete all the draft releases from the list of releases

Test the Pre-Release

[ ] Wait until the Docker binaries have been built on main, and the quick tests have passed:

[ ] ci-tests.yml

[ ] Wait until the pre-release deployment machines have successfully launched

Publish Release

[ ] Publish the release to GitHub by disabling 'pre-release', then clicking "Set as the latest release"

Publish Crates

[ ] Run cargo login
[ ] Run cargo clean in the zebra repo (optional)
[ ] Publish the crates to crates.io: cargo release publish --verbose --workspace --execute
[ ] Check that Zebra can be installed from crates.io:
cargo install --locked --force --version 1.minor.patch zebrad && ~/.cargo/bin/zebrad
and put the output in a comment on the PR.

Publish Docker Images

[ ] Wait for the the Docker images to be published successfully.
[ ] Wait for the new tag in the dockerhub zebra space
[ ] Un-freeze the batched queue using Mergify.
[ ] Remove do-not-merge from the PRs you added it to

Release Failures
If building or running fails after tagging:

Tag a new release, following these instructions...

Fix the bug that caused the failure
Start a new patch release
Skip the Release Preparation, and start at the Release Changes step
Update CHANGELOG.md with details about the fix
Follow the release checklist for the new Zebra version

Omitted changelog entries:

add(ci): Check that dependencies have all been published to crates.io on release PRs (#8992)
book: add section about private testnet testing (#8937)
build(deps): bump rlespinasse/github-slug-action from 4 to 5 in the devops group (#9002)
build(deps): bump the devops group across 1 directory with 5 updates (#9061)
build(deps): bump the devops group across 1 directory with 5 updates (#8993)
chore(ci): do not default to tracing mode in jobs execution (#9004)
chore: Fix clippy lints (#9062)
chore: remove redundant words in comment (#9015)
chore: update CHANGELOG to better convey the 2.0.0 issue (#9007)
feat(actions): migrate Mergify to GitHub Merge Queue (#9005)
fix(actions): do not require the get-disk-name job for forks (#8988)
fix(ci): allow to run all lighwalletd tests in Docker (#9038)
fix(ci): fail cache disk creation if no db version is found (#8987)
fix(ci): remove scan-start-where-left-test from CI (#9026)
fix(mergify): align build job name across workflows (#9055)
fix(mergify): remove deprecated speculative_checks option (#9033)
fix(test): Update the reference Sapling treestate (#9051)
ref(mergify): use the new configuration format and keys (#9018)
ref: adjust GCP instances resources to better fit requirements (#8986)
refactor(mergify): streamline queue and priority rules (#9068)
fix(ci): remove scan-start-where-left-test from CI (#9026)
add pub functionality for zaino (#8964)
fix: typos correction docs (#9014)
release(docs): Update the release checklist pull request and issue templates (#9050)
feat(actions): migrate Mergify to GitHub Merge Queue (#9005)
chore(ci): do not default to tracing mode in jobs execution (#9004)
ref: adjust GCP instances resources to better fit requirements (#8986)
ref(mergify): use the new configuration format and keys (#9018)
fix(actions): do not require the get-disk-name job for forks (#8988)
fix(ci): allow to run all lighwalletd tests in Docker (#9038)
fix(ci): fail cache disk creation if no db version is found (#8987)
fix(mergify): align build job name across workflows (#9055)
fix(mergify): remove deprecated speculative_checks option (#9033)
fix(test): Update the reference Sapling treestate (#9051)
ref(mergify): use the new configuration format and keys (#9018)
refactor(mergify): streamline queue and priority rules (#9068)

Should a version of "add pub functionality for zaino" be included in the changelog?

I'd say so since it changes Zebra's external API.


Can I use this lib without "OIDC"?

This is a general question
I want to use with my angular app (v18)  two different external provided api's (over which I have no influence). Both of them are using OAuth 2 for auth. In order not to implement the entire OAuth workflow myself, I looked for existing Angular libraries and came across these.
After I integrated the lib and adjusted the configuration, I fail when using the first external API because the GET request ".../.well-known/openid-configuration" returns a 404 not found.
I then contacted API support to see if there was an alternative URL for the "well-known" request, but all I received was the answer:

"At this time our API only supports Oauth2.0 for authentication, if possible we recommend moving forward with Oauth2 and the PKCE flow for authorization."

Is there a way to use this lib so that it only handles the "plain" OAuth PKCE flow without OpenID Connect?
If it's possible, what exactly would I need to do to achieve this?
My second question: Is it possible to use 2 different OAuth APIs with this lib? So to store two different configurations?
Thank you for the support!

Yes, that's possible. you can set oidc to false and set everything the .well-known OIDC Discovery Document would have provided by hand.


dicarlo.BashivanKar2019

@stothe2 do you think it makes more sense to have many (>12) separate assemblies (@kohitij-kar suggested this) or merge those assemblies into one, but then having many NaN entries (that can again be filtered out by later splitting into separate assemblies)?
My intuition is that we should keep an assembly more self-contained, i.e. have one or two assemblies for this paper, so that we don't flood the assembly lookup.

Just to directly register the conversation, I am pasting it below. Also, I don’t understand assemblies etc very well. I don’t think of data that way anyways.  So I actually never made any specific suggestions: just explained what I thought is the case with this dataset. All I mean is please don’t consider my opinion very strongly during making decisions for this.
Jon: Each monkey looked a a completely different set of synthetic images, is that correct?  If I made synthetic into one single DataAssembly, it would be mostly NANs.  So, would it be appropriate to make three separate assemblies?
I assume I need to package curvature and naturalistic as one assembly each, too, to give context to the synthetic.  So that's five assemblies total.
Until now the data I've packaged had already been chopped into tidy rectangular blocks.  Where there are differing numbers of reps in a single assembly, do I chop off the excess, or leave some NANs in?
Ko: Here are my thoughts on the issues you mention.

Yes I think it’s best to treat each monkey, each session as separate.
Naturalistic images are same for both monkeys. But the curvature stimulus was different dependent on what receptive field we had for the neurons. I would either leave that out for now (and push this to later discussions) or include them as separate for each monkey.
I would use nans and not chop off any data
The problem may be that assemblies etc had been discussed so far with our usual data collection in mind. This was a very different type of experiment. So the data that exists is not completely consistent with everything else (yet I believe there is a way to make it such).

thanks Ko! This data is actually a really good case for us to more thoroughly define what we mean by an "assembly" -- i.e. whether it is a recording session or rather an entire experiment.
I'm leaning towards the latter because I think that users will mostly want to retrieve data for an experiment rather than for individual sessions. (And having all the data for a paper in one package feels more clean)

I agree. I will never advocate for an assembly per recording session. That’s too much. But I think as you will see that beyond that — things will quickly get more complicated as we do different types of experiments (which I believe will be a marker of the lab actually making SoTA experimental progress and not just churning out the same old stuff at more quantity).  For now, assemblies per dataset grouped by purpose of collection, e.g paper or specific analysis,  sounds reasonable to me.

@jjpr-mit Looking at the code you pushed, Jon, one thing that could be done to reduce the number of assemblies is to combine the sessions (at least). So, Monkey M/OHP/Session1/Nat - Monkey M/OHP/Session1/Synth (since the naturalistic stimuli in a given monkey and session were used for synthesis for same monkey and session), etc.
As for rest of the discussion (single vs multiple assemblies), I'm ambivalent. I see both as a short term solution (like Ko said, we need to start thinking of experiments people will be doing in the next ~2 years -- amygdala, muscimol, stimulation -- and come up with a more intuitive solution for the heterogeneous data).

So, Monkey M/OHP/Session1/Nat - Monkey M/OHP/Session1/Synth

@stothe2 Yes, I thought about combining each synth/nat pair, since they align on the neuroid axis.  I'd have to combine the synth and nat StimulusSets to do that, though, and they've got completely different metadata, so I settled for separating the stages of the experiment.

I'd have to combine the synth and nat StimulusSets to do that, though, and they've got completely different metadata

Fair point. It shouldn't matter for the assembly (since you would only include those columns which are common to both StimulusSets, for example, image_id), but I guess you're now dealing with NaNs in the StimulusSet (like dicarlo.BOLD5000). Even so, I would prefer having them combined since it makes it obvious to the user that they're meant to go together (i.e., we used responses to these naturalistic images for mapping, and then used the resulting mapped model for synthesising these other images).

only include those columns which are common to both StimulusSets

The metadata from the StimulusSet are automatically merged with the assembly on load.
Trying to combine two StimulusSets with different metadata into one just so we can combine pairs of assemblies introduces complexity, and reducing complexity is the point of combining.  So I think it defeats the purpose.  Until we upgrade DataAssembly to handle heterogeneous non-aligned datasets, we can't accommodate combining these assemblies.

@stothe2 @mschrimpf @kohitij-kar
I'm trying to figure out the right way to collect non-aligned chunks of data together.  The authors of xarray say that DataArray and Dataset are not intended for that:
https://stackoverflow.com/questions/53754243/xarray-hierarchical-data-organization

Finally, note that xarray (currently) does not have any version of a hierarchical data structure for non-aligned axes. Aligned axes are an intentional constraint of the data models for xarray.Dataset and xarray.DataArray. If you have sub-groups that are not aligned along common axes, you'll need to keep track of them in some separate data structure.
answered Dec 18 '18 at 18:52 shoyer

also:

Dataset groups #1092
Feature Request: Hierarchical storage and processing in xarray #4118

I don't think we should hold up this PR to refactor BrainIO with a hierarchical data solution.

yes agree, I thought what @stothe2 proposed was to have one assembly per session (with a bunch of NaNs from non-overlap -- i.e. no refactoring, just nans)

The shapes of the source data:

The shapes of the source data:

How synthetic sessions will be arranged as a single assembly (black is NaNs):

The image is reduced to a single repetition from each session for clarity.

How synthetic sessions will be arranged as a single assembly (black is NaNs):

The image is reduced to a single repetition from each session for clarity.

yes agree, I thought what @stothe2 proposed was to have one assembly per session (with a bunch of NaNs from non-overlap -- i.e. no refactoring, just nans)

From what it looks like, there are two NeuronAssemblies (and corresponding StimulusSets) -- one for naturalistic and one for synthetic. This works too!

yes agree, I thought what @stothe2 proposed was to have one assembly per session (with a bunch of NaNs from non-overlap -- i.e. no refactoring, just nans)

From what it looks like, there are two NeuronAssemblies (and corresponding StimulusSets) -- one for naturalistic and one for synthetic. This works too!


Add textX benchmark

https://github.com/textX/textX seems pretty promising

Seems like a good idea. It seems like textX is just a different metasyntax on top of Arpeggio, so I wonder if we should just use Arpeggio instead? Then again, textX has more stars on GitHub so maybe it's more familiar.
@ThatXliner, care to provide an implementation? There are JSON examples for both textX and Arpeggio. They just need to be adapted to follow the JSON spec more closely (particularly regarding strings) and wrapped such that they can be timed.

I can try this Saturday! IMO, I think you should put the name like textX (Arpeggio).

I can try this Saturday!

Great, thanks!

I think you should put the name like textX (Arpeggio).

That's fine if you use textX. My point is that you can apparently use Arpeggio without textX, either with a PEG-like metasyntax or with Python code (like PyParsing, in a way). Writing Python code would most certainly make it fast to instantiate a parser, but I don't think it would affect the actual parsing performance.

When you mean "top level element", do you mean like the first element? And if single values are allowed as a top-level element, do you mean
1

Should be counted as valid?

When you mean "top level element", do you mean like the first element?

Are you referring to the JSON task document? If so, then I mean that a JSON document consists of a single value, and that value may be an object ({...}), an array ([...]), a string, a number, true, false, or null. This is following the JSON specification.

And if single values are allowed as a top-level element, do you mean
1

Should be counted as valid?

Yes. This is how Python's JSON parser works, as well:
>>> import json
>>> json.loads('1')
1

Looking at the textX example, that means the top-level rule, at least, needs to be expanded:
 File:
-     Array | Object
+    Value
;

Some more work will need to be done, such as redefining STRING and BOOL and maybe FLOAT so they fit more tightly to the JSON spec. They are "primitive" patterns defined here:
https://github.com/textX/textX/blob/ac99d92da2d9a5c5d85cf3ffaacb1779b4a5a0c2/textx/lang.py#L91-L99
For instance, 01 is not a valid integer in JSON, but the INT rule in textX seems to allow it. You can check the examples in this repository for valid patterns. For instance, in Lark:
https://github.com/goodmami/python-parsing-benchmarks/blob/611cfc20ca7b61f1f489b0e56f201f6888a5c67b/bench/lark/json.py#L32-L39
Or in SLY:
https://github.com/goodmami/python-parsing-benchmarks/blob/611cfc20ca7b61f1f489b0e56f201f6888a5c67b/bench/sly/json.py#L21-L29

For the lark parser, you don't need to specify all those white spaces. You can just %ignore  it Wait. There's like a special Whitespace requirement, right?

We tweaked the Lark one to try and make it faster (see 2ddd8ce288b85a63a676c748094e55e9a27a074b and https://github.com/lark-parser/lark/issues/487#issuecomment-603866347). We're not completely sold that it's a good idea, because it makes the grammar harder to read for only a 5% speedup.
The whitespace requirement for the JSON parser is just as the spec dictates. Whitespace is allowed and ignored before and after any value and object key. Unescaped newlines are not allowed inside strings.

Now that #5 is merged and the times are included in the README, I think we can close this issue. Thanks again for the help!


N-way basic composition combinator

Closes #7
Incomplete implementation. It might be possible to lift the necessary ::Distance traits up to the Measure trait bounds, to avoid needing to introduce an EpsilonDelta struct.
Andy pushed the design on most of this! Thanks!

adjusted python to be able to construct a Vec<const AnyMeasurement*>
add FFI for multi-way composition combinator
add BasicComposition trait with binary search algorithm for iteratively finding the tightest budget

implemented on measures, and captured in the AnyMeasure via a glue function

adjusted IntoAnyMeasurementOutExt to not double-wrap the relation distances in Any
add EpsilonDelta struct, and adjust the associated type for SmoothedMaxDivergence to refer to it

not sure I like this

Closed in favor of #242.


New version: SymbolServer v1.0.1

Registering package: SymbolServer
Repository: https://github.com/julia-vscode/SymbolServer.jl
Created by: @davidanthoff
Version: v1.0.1
Commit: 6c2e923a427802d99c762e05d153dbdcd4dcd138
Reviewed by: @davidanthoff
Reference: https://github.com/julia-vscode/SymbolServer.jl/commit/6c2e923a427802d99c762e05d153dbdcd4dcd138#commitcomment-35701773

Your new version pull request met all of the guidelines for automatic merging.
I will automatically merge this pull request during the next cron job.
If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

[noblock]


TypeNode path points to incorrect type in wrong scope

The following example showcases the problem: The types of the instance variables are Array(::Bar).new and ::Bar.new. But the macro expression in ivar_types makes them Array(Bar) and Bar (not the missing :: which indicates a global path) and as a result Bar resolves in the local scope to Foo::Bar.
class Bar
end

class Foo
  class Bar
  end

  @array = Array(::Bar).new
  @bar = ::Bar.new

  def ivar_types
    {{@type.instance_vars.map(&.type) }}
  end
end

[typeof(Foo.new.@array), typeof(Foo.new.@bar)] # => [Array(Bar), Bar]
Foo.new.ivar_types                             # => [Array(Foo::Bar), Foo::Bar]

This is not related to any macro scoping issues. The macro expression mapping the ivars to their type expands to [Array(Bar), Bar], which correctly resolves Bar to Foo::Bar.
Perhaps the solution is to always use global paths when turning a TypeNode into a string?

Perhaps the solution is to always use global paths when turning a TypeNode into a string?

The problem then is that it won't work well for private types. But maybe we should not use global paths for private types...


[SCRIPT] XLNet squad finetuning scripts

Description
add XLNet squad finetuning scripts.
add corresponding results.
Checklist
Essentials

[ ] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Job PR-1130/6 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-1130/6/index.html

Job PR-1130/7 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-1130/7/index.html

Job PR-1130/8 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-1130/8/index.html

Job PR-1130/9 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-1130/9/index.html

Job PR-1130/10 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-1130/10/index.html

There seems to be a bug
[2020-02-02T20:03:05.993Z] Traceback (most recent call last):

[2020-02-02T20:03:05.993Z]   File "./scripts/language_model/run_squad.py", line 200, in <module>

[2020-02-02T20:03:05.993Z]     xlnet_base, vocab, tokenizer = model.get_model(**get_model_params)

[2020-02-02T20:03:05.993Z]   File "/var/lib/jenkins/workspace/gluon-nlp-gpu-py3/scripts/language_model/transformer/model.py", line 62, in get_model

[2020-02-02T20:03:05.993Z]     return models[name](**kwargs)

[2020-02-02T20:03:05.993Z]   File "/var/lib/jenkins/workspace/gluon-nlp-gpu-py3/scripts/language_model/transformer/model.py", line 193, in xlnet_cased_l12_h768_a12

[2020-02-02T20:03:05.993Z]     ignore_extra=not kwargs.get('use_decoder', True))

[2020-02-02T20:03:05.993Z]   File "/var/lib/jenkins/workspace/gluon-nlp-gpu-py3/src/gluonnlp/model/utils.py", line 281, in _load_pretrained_params

[2020-02-02T20:03:05.993Z]     net.load_parameters(model_file, ctx=ctx, ignore_extra=ignore_extra, allow_missing=allow_missing)

[2020-02-02T20:03:05.993Z]   File "/var/lib/jenkins/workspace/gluon-nlp-gpu-py3/conda/gpu/py3/lib/python3.5/site-packages/mxnet/gluon/block.py", line 555, in load_parameters

[2020-02-02T20:03:05.993Z]     params[name]._load_init(loaded[name], ctx, cast_dtype=cast_dtype, dtype_source=dtype_source)

[2020-02-02T20:03:05.993Z]   File "/var/lib/jenkins/workspace/gluon-nlp-gpu-py3/conda/gpu/py3/lib/python3.5/site-packages/mxnet/gluon/parameter.py", line 310, in _load_init

[2020-02-02T20:03:05.993Z]     self._init_impl(data, ctx)

[2020-02-02T20:03:05.993Z]   File "/var/lib/jenkins/workspace/gluon-nlp-gpu-py3/conda/gpu/py3/lib/python3.5/site-packages/mxnet/gluon/parameter.py", line 359, in _init_impl

[2020-02-02T20:03:05.993Z]     self._data = [data.copyto(ctx) for ctx in self._ctx_list]

[2020-02-02T20:03:05.993Z]   File "/var/lib/jenkins/workspace/gluon-nlp-gpu-py3/conda/gpu/py3/lib/python3.5/site-packages/mxnet/gluon/parameter.py", line 359, in <listcomp>

[2020-02-02T20:03:05.993Z]     self._data = [data.copyto(ctx) for ctx in self._ctx_list]

[2020-02-02T20:03:05.993Z]   File "/var/lib/jenkins/workspace/gluon-nlp-gpu-py3/conda/gpu/py3/lib/python3.5/site-packages/mxnet/ndarray/ndarray.py", line 2632, in copyto

[2020-02-02T20:03:05.993Z]     return _internal._copyto(self, out=hret)

[2020-02-02T20:03:05.993Z]   File "<string>", line 27, in _copyto

[2020-02-02T20:03:05.993Z]   File "/var/lib/jenkins/workspace/gluon-nlp-gpu-py3/conda/gpu/py3/lib/python3.5/site-packages/mxnet/_ctypes/ndarray.py", line 107, in _imperative_invoke

[2020-02-02T20:03:05.993Z]     ctypes.byref(out_stypes)))

[2020-02-02T20:03:05.993Z]   File "/var/lib/jenkins/workspace/gluon-nlp-gpu-py3/conda/gpu/py3/lib/python3.5/site-packages/mxnet/base.py", line 255, in check_call

[2020-02-02T20:03:05.993Z]     raise MXNetError(py_str(_LIB.MXGetLastError()))

[2020-02-02T20:03:05.993Z] mxnet.base.MXNetError: [20:03:01] src/engine/threaded_engine.cc:333: Check failed: exec_ctx.dev_id < device_count_ (1 vs. 1) : Invalid GPU Id: 1, Valid device id should be less than device_count: 1

Job PR-1130/11 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-1130/11/index.html


[FEATURE REQUEST] Properties derive macro shouldn't import PropertyGet

Properties imports PropertyGet into an outer scope, changing the method resolution behavior.
Recently I learned about the Properties derive macro, and when I tried to replace manual implementations with that, I got type mismatch errors in nearby code:
error[E0277]: expected a `Fn(&std::vec::Vec<std::string::String>)` closure, found `usize`
   --> xxxxxxxx.rs:99:51
    |
 99 |                                           foo.get(i)
    |                                               --- ^ expected an `Fn(&std::vec::Vec<std::string::String>)` closure, found `usize`
    |                                               |
    |                                               required by a bound introduced by this call
    |
    = help: the trait `for<'a> Fn(&'a std::vec::Vec<std::string::String>)` is not implemented for `usize`
note: required by a bound in `glib::property::PropertyGet::get`
   --> xxx/.cargo/registry/src/index.crates.io-6f17d22bba15001f/glib-0.20.2/src/property.rs:67:18
    |
67  |     fn get<R, F: Fn(&Self::Value) -> R>(&self, f: F) -> R;
    |                  ^^^^^^^^^^^^^^^^^^^^^ required by this bound in `PropertyGet::get`

Before the change, the get call was resolved to <[String]>::get through a deref of foo: &Vec<String>. With PropertyGet in scope, it gets resolved to <Vec<String> as PropertyGet>::get.

That's indeed not great. Do you want to provide a PR for fixing that?

Will do!

Thanks! If you find the same issue elsewhere in that macro (with that or another trait), feel free to take care of that at the same time :)


Enabling issue

After installation cannot able to enable the theme

Just reload the editor and type color theme inside the command palette

@equinusocio i done same way but the effect is not getting i also tried uninstalling other theme


fix: db tests path in windows container

What kind of change does this PR introduce?
Bug fix https://github.com/supabase/cli/issues/843
What is the current behavior?
filepath.Join returns back slash on windows
What is the new behavior?
Always construct path using forward slash inside container.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 62.737%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
3805

Relevant Lines:
6065

💛  - Coveralls


Dimensional Shards have no mining level

The Dimensional Shards can be mined with any level pickaxe, even wooden. Not sure if this is intentional, though.

Hmm, no. Not really. Will investigate

Fixed in next release


⚠ Bofrost.es has degraded performance

In 539d037, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1414 ms

Resolved: Bofrost.es performance has improved in fc24dfb after 6 minutes.


[terra-table] Subheader specificity

Summary
Fixes #2461 Subheader styles were being overridden by the table's reset styles on mpage theme. Increased specificity for those styles.

For curious, would like to know why the class is assigned to <td> to instead of <tr> in TableSubheader.jsx :
  <tr data-terra-table-subheader-row>
    <td {...customProps} className={cx('subheader', customProps.className)} colSpan={colSpan}>
      {content}
    </td>
  </tr>


error: ReactNativeContacts is not abstract

I was just testing out this library and got the following error:
rt2zz/reactnativecontacts/ReactNativeContacts.java:12: error: ReactNativeContacts is not abstract and does not override abstract method createJSModules() in ReactPackage
public class ReactNativeContacts implements ReactPackage {
       ^
1 error
:react-native-contacts:compileReleaseJavaWithJavac FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-contacts:compileReleaseJavaWithJavac'.

I searched around and saw someone mention that upgrading to react-native 0.47 might fix it.
I'm currently running react native 0.46.4 and avoiding ever changing it.
Any ideas on how to get around this error?
thanks.

use an older version of this project. v.40 might work https://github.com/rt2zz/react-native-contacts/releases


geonames-Importer doesn't work anymore

Until a few days ago I was able to:

create a new place on the geonames-website
In an PMB-entry create a new relation to that place
copy in the URL of the new created geonames-id
and the place was created based on the new information taken from geonames.

At least since last week this does not work anymore and when I create a relation nothing happens. I.e.
https://www.geonames.org/12535075/brennerriesensteig.html
can not be added this way as being part of
https://pmb.acdh.oeaw.ac.at/apis/entities/entity/place/91834/edit

Maybe it has something to do with newly created entries, older one seem to work

(expecting the "closed - does not work" resolution)

If older entries work, but newer ones dont, its probably related to the RDF, can you post here links to an entry that works and one that doesnt? @martinantonmueller

It appears to be an issue at geonames: The rdf of the Brennerriesensteig is empty:
https://www.geonames.org/12535075/brennerriesensteig.html
has an empty RDF:
https://sws.geonames.org/12535075/about.rdf
Maybe this will be filled in at some later moment. It used to work, but doesn't anymore. Nothing we can fix. Thank you @sennierer


Double ownerReferences problem

Operator installed with helm chart 1.0.7
Received status: Status(apiVersion=v1, code=422,
      details=StatusDetails(causes=[StatusCause(field=metadata.ownerReferences, message=Invalid
      value: []v1.OwnerReference{v1.OwnerReference{APIVersion:\"sparkoperator.k8s.io/v1beta2\",
      Kind:\"SparkApplication\", Name:\"jsonl-count\", UID:\"13efa3d6-4fee-4c2c-bc73-60d89d5d3e7d\",
      Controller:(*bool)(0xc01839a16b), BlockOwnerDeletion:(*bool)(nil)}, v1.OwnerReference{APIVersion:\"sparkoperator.k8s.io/v1beta2\",
      Kind:\"SparkApplication\", Name:\"jsonl-count\", UID:\"13efa3d6-4fee-4c2c-bc73-60d89d5d3e7d\",
      Controller:(*bool)(0xc01839a18b), BlockOwnerDeletion:(*bool)(nil)}}: Only one
      reference can have Controller set to true. Found \"true\" in references for
      jsonl-count and jsonl-count,

SOLVED: There was another spark instalation in the cluster in a different namespace.
I guess making CRD the owner of pods prevents multiple installations of spark-operator.

Solved by removing CloudFlow because it was introducing another Spart Operator.


docs: update upgrading procedures

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary
(describe what this merge request does)
Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[ ] add new test cases
[ ] all code changes are covered by unit tests
[ ] end-to-end tests

[ ] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting
[ ] streaming ingestion

[ ] with Redshift Serverless
[ ] with provisioned Redshift

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
84
< 80

Duplicated lines density
:white_check_mark: OK
5.40
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/11/2024, 15:48:47 (UTC+0)

SonarQube Code Analytics
Quality Gate passed

Additional information
The following metrics might not affect the Quality Gate status but improving them will improve your project code quality.
Issues
 0 Bugs
 0 Vulnerabilities
 0 Code Smells
Coverage and Duplications
No data Coverage
No data Duplication

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
84
< 80

Duplicated lines density
:white_check_mark: OK
5.40
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/13/2024, 03:06:40 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
84
< 80

Duplicated lines density
:white_check_mark: OK
5.40
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/13/2024, 03:09:37 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
84
< 80

Duplicated lines density
:white_check_mark: OK
5.40
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/13/2024, 03:10:25 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.50
< 80

Duplicated lines density
:white_check_mark: OK
5.60
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/15/2024, 06:22:01 (UTC+0)

Before migrating data, a step should be added to tell users that they need to set the time zone for all applications under the project.

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @amliuyong on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.40
< 80

Duplicated lines density
:white_check_mark: OK
5.60
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/15/2024, 09:58:49 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @amliuyong on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.40
< 80

Duplicated lines density
:white_check_mark: OK
5.60
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/15/2024, 10:02:11 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @amliuyong on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.50
< 80

Duplicated lines density
:white_check_mark: OK
5.60
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/15/2024, 10:03:40 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.50
< 80

Duplicated lines density
:white_check_mark: OK
5.60
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/21/2024, 07:33:44 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.50
< 80

Duplicated lines density
:white_check_mark: OK
5.60
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/21/2024, 07:40:50 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.40
< 80

Duplicated lines density
:white_check_mark: OK
5.60
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/21/2024, 10:19:13 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.60
< 80

Duplicated lines density
:white_check_mark: OK
5.60
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/21/2024, 10:22:48 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.60
< 80

Duplicated lines density
:white_check_mark: OK
5.60
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
1
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/21/2024, 10:23:03 (UTC+0)


Support terrain packets

Blocked by #31 performance issues, must reconsider whether the GUI viewer should be included in beta-v0.8.

Actually, I'm going to consider this "good enough" for now. A 3D viewer for terrain might be a bit out of scope. After all, a DataModel basepart viewer wouldn't make sense either. In the future, it might be good to have a way to serialize the terrain into dumped DataModels though.


Forward port 0.3 changes

@domenkozar can you add a bit of explanation what i can/should test to verify your PR?

We should test that windows installer works correctly. These bugfixes were in 0.2/0.3 but are not in master yet.

Ok I will boot up my windows VM and try it … btw. where can i get the latest builds?

Show all checks -> pick appveyor/branch then Artifacts tab

Without this change, Windows installer just can't work :)

Ok sorry for the delay … i just figured i cannot test windows because my Vm ware does not work anymore since i upgraded to el capitan …

@domenkozar: I can not find a build in AppVeyor. I don't have Show all checks option. I have clicked show more until I loaded all of available history and I could not find the build that I need to verify this.

There should be "Show all checks" and then you can click on appveyor build:

Once appveyor opens (it takes a while to load), go to artifacts tab.

Thanks @domenkozar. I have installed it but desktop icon installer created did not work. Here is the target from the icon: "C:\Program Files\Daedalus\cardano-launcher.exe" --node "%PROGRAMFILES%\Daedalus\cardano-node.exe" --node-log-path "%APPDATA%\Daedalus\Logs\cardano-node.log" --wallet "%PROGRAMFILES%\Daedalus\Daedalus.exe" --updater  "%APPDATA%\Daedalus\Installer.exe" --node-

@neongreen does launcher now require the updater to exist unconditionally?

    unlessM (testfile path) $ do
        echo "Running the updater"
        let args' = args ++ maybe [] (one . toText) updateArchive
        exitCode <- proc (toText path) args' mempty
        printf ("The updater has exited with "%s%"\n") (show exitCode)
        when (exitCode == ExitSuccess) $ do
            -- this will throw an exception if the file doesn't exist but
            -- hopefully if the updater has succeeded it *does* exist
            whenJust updateArchive rm

Seems to be a bug. Unfortunately, git blame didn't tell me who introduced it.

(And thus I'm not sure it's actually a bug.)

Okay, looks like it was introduced as a part of the HLint pull-request: https://github.com/input-output-hk/cardano-sl/pull/128/files#diff-9bc0ce73245ad9dfcba632fe7450ad0cR215
What would be the best way to fix it? Change unlessM to whenM in master and cherry-pick to this branch? Or to the 0.3 branch as well?

Best to cherry-pick to all branches that have this bug including this PR so we can test it again.

@neongreen was it fixed?

FYI @darko-mijic @DominikGuzei this is also why macOS installer doesn't work:
DE339:~ admin$ DISPLAY=:0.0 /Applications/Daedalus.app/Contents/MacOS/Daedalus
Running in the client scenario
Running the updater
cardano-launcher: /Users/admin/Library/Application Support/Daedalus/installer.pkg: createProcess: runInteractiveProcess: exec: invalid argument (Bad file descriptor)

@domenkozar I'm sorry, I haven't noticed your “Best to cherry-pick to all branches that have this bug including this PR so we can test it again.” message. I will fix it today and ping you.

Waiting on https://ci.appveyor.com/project/jagajaga/cardano-sl/build/0.2.3512 and then I can rebase

Blocked on a failing cardano-sl test.

@darko-mijic can you test again?

Now I get following, is this fixed in master? @DominikGuzei @darko-mijic

@DominikGuzei will fix that, I'll just merge this PR as without it the packaging for Windows isn't complete anyway.


chore: adjust license definitions for SPDX/REUSE compliance

Mostly, only the LicenseRef- prefix was missing. According to my local run of reuse lint, you should be compliant with this change. :)

Thanks a lot, @SebastianWolf-SAP ! :)


[filebeat] change default value of filebeat.extraContainers

[x] Chart version not bumped (the versions are all bumped and released at the same time)
[x] README.md updated with any new values or changes

Fixes #1636
I got this error:
template: filebeat/templates/daemonset.yaml:199:14: executing "filebeat/templates/daemonset.yaml" at <.Values.extraContainers>: wrong type for value; expected string; got []interface {}

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@jmlrt

@jmlrt please take a look.

Hi, This PR is waiting for approving review. Please review the PR.

Hi @jmlrt, Is there anything to improve?

/bump still waiting for review


Update pagination styles

Added some tailwind styles to the pagination so is more aligned with the rest of the app. Also included some Pagy defaults tweaks.
Also setup a basic basic seeds file that creates a User and some Bounties. Could be extended to create multiple users + bounties per user, but this at least enables testing of pagination, etc.

Mobile could use some clean up, paginations sticks out a bit on very small devices.


feat(UI): add pagination for detail views in process instance improves rendering time for large workflows

Motivation:
While using this Simple Monitor for some performance tests, I realized that instances with 300+ events
(let it be timers, jobs, incidents etc.) lead to trouble loading the DOM in the browsers. The reason for that is simple:
the process instance view did server-side rendering all information as HTML tables. This led to 5MB+ large HTML files,
which took ca. 10s to load the DOM in Chrome, on my MacBook Pro.
Some more extreme tests with 3000+ events also lead to server-side timeouts.
This PR tries to solve the performance issue by keeping the server-side rendering and introducing pagination
per individual detail view (timers, jobs, audit log, etc.)
This PR covers:

refactoring: move all DTOs into their own package
refactoring: split almighty ViewController into multiple ones, per each main view (see top navigation)
refactoring: split InstanceViewController into multiple smaller ones, per each detail view
refactoring: split process instance detail views into multiple pages in order to introduce pagination
refactoring: re-formatted code, using google java code style, as stated in camunda-cloud/zeebe contribution guidelines

I left the individual commits in, in case someone likes to see the intermediate refactoring steps.
Resulting from the refactorings, the behavior in the UI is now slightly different.
Each subview in the process instance view is now a standalone page. This means not all details are loaded at once anymore,
but the *ViewController makes use of Spring's Pageable methodology.
The result is significantly faster page loading and rendering.
Here's how the UI looks now... (visually the same, except we have introduced new query parameter)

Any feedback is welcome.

@saig0 without putting any pressure, I just want to "ping" the PR is now considered ready.

@nitram509 awesome :tada:
I'll review the PR as soon as I can. But currently, it is not so easy for me to find the time for my side projects :sob:

Thank you @saig0 for your support 👍


Move UFS files into a smaller number of directories

A little spring cleaning before doing some more interesting work on vnodes/inodes.
Move headers into a single ufs folder.
Also move ufs .c files into a single ufs folder.

That should be a little tidier now.


Revert "Work around the std::path reform."

This reverts commit cfd9e26258233090fae63428fbb56d70c1504236.

This change does not compile with the latest rust snapshot.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

ihavenoideawhatsgoingon.jpg

The combined cargo+rustc nightlies seem to be out-of-sync across platforms. https://github.com/rust-lang/rust-buildbot/issues/7


Chrome loses focus when i call hyperterm with a hotkey on Win10

I saw people has solutions for this issue on a Mac, but nothing on windows.

Back in June I wasn't able to reproduce it but now that I take another look at it I am so I'll have to look into this again

Steps to reproduce this:

Open Chrome.
Open Hyper overlay with a hotkey.
Close Hyper overlay with a hotkey.
Chrome is not focused, i.e. i cant just type in address bar with 1 click, i first need to return focus to chrome by clicking on it.

Yes I can reproduce it with both Chrome and Discord (which is Electron so Chromium I guess). I'll have to debug it

Discord does work just like overlay? You can hide/show it by a hotkey? Issue is in this mechanism i guess, because VSCode when minimized, not causing this bug to chrome.

Your sentence is all jumbled up there but what I meant is that Discord also doesn't gain focus back when closing and while I can't check right now if I'd have to guess I'd say no program at all does.

So you think it would be possible to fix?

I don't know. I'll have to look into it when I have time.

Update: I'm afraid I can't fix it without completely rewriting the plugin. It appears that Electron simply doesn't have a proper API to fetch the last focused window for Windows (it does for MacOS) and the reason it didn't work was because the methods used previously were simply returning null for the _lastFocus rather than the actual window.
It might be possible with something like electron-window-manager but like I said, that would require completely rewriting the plugin from scratch and I'm not looking to do that.


[YAML] Auto Release to "GitHub Release"

Both Travis and Appveory support to release back to github: https://docs.travis-ci.com/user/deployment/releases/
However, I cannot find this feature in vsts-ci, from the document.
Is this feature available ?
Although there are few github extensions said support "GitHub Releas" in market place, but I don't how to use them in yaml build.

Here is the doc for referencing tasks from a yaml file. The View Yaml link from a designer definition would be the best way to get the yaml file started.

How can I get the task name and version from a extension ?
For example, like this one: https://marketplace.visualstudio.com/items?itemName=jakobehn.jakobehn-vsts-github-tasks . There are almost no documents about how to use it.


[Feature Request]: I would like to update the about page

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Features I will be adding :

GSAP Animation
ScrollTrigger

Use Case
It will improve the User Experience
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I'm a SSOC'24 contributor
[X] I have starred the repository

@apu52 please assign me this task with gssoc-ext, level 3 label

@eshaalal u are assigned

@apu52 do assign me the level as well

@apu52 do assign me the level as well

I will add the appropriate labels as per the review of the pr


Add a new Argon.FSharp.Tests project + add tests for the FSharpListConverter + fix the converter

It seems the FSharpListConverter was no longer working with anything else than primitive values.
I fixed it by replacing writer.WriteValue(item); with serializer.Serialize(writer, item); but I don't know enough to be certain it's the correct/best fix, so please review :)
I also added an fsharp test project to make sure this does not happen again. I wasn't entirely sure how to call it or where to put it, so I used my best guess.
(I also had a hard time making the solution work with all its targets, so I only targeted net6.0 for this new test project. I think this is a good start)

Note: this is related to https://github.com/VerifyTests/Verify/pull/911: it seems an FSharp list is also a discriminated union internally — that's why I was getting a nested list of linked nodes instead of an array when I put the DiscriminatedUnionConverter first in the list of converters. It was actually correct to put it last to avoid this issue.

thanks

updating and deploying a new version of Verify now


Don't automatically update archetypes to their existing values

Travis tests have failed
Hey @silasary,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
TravisBuddy Request Identifier: b5ccd7e0-a385-11ea-9680-e709d44ff74e


Minor bugs on the newly added translated docs

Describe the bug

When you change the langauge (English to Korean) on the main page and click on the Get Started button, it takes to the original English version of the document.
When selecting different language while on the docs page, it leads to the main page.

Your environment

Tested Browser : Chrome

Steps to reproduce

Regarding Get Started button

Regarding selecting different language

Expected behaviour

Get Started button leads to the translated version of the document
when the language is changed while on the docs page, it stays on the same page but with the selected language.

Actual behaviour

Actual behaviors are as mentioned in the Describe the bug section

Thanks for the report! Fixed in #959


java.lang.RuntimeException: Can not initialize graphics device

Report from IRC (koolestest). This is similar to the crashes on Intel HD 4000 and other older hardware, but apparently the user uses a GTX 760 with proprietary Nvidia drivers which should be able to run the game just fine - plus the crash isn't silent, with the log pointing to an internal LWJGL error.
http://pastebin.com/FTkk9BH4
Relevant snippets:
13:27:09.823 [main] ERROR o.terasology.engine.TerasologyEngine - Failed to initialise Terasology
java.lang.RuntimeException: Can not initialize graphics device.
    at org.terasology.engine.subsystem.lwjgl.LwjglGraphics.initDisplay(LwjglGraphics.java:266)

...
Caused by: org.lwjgl.LWJGLException: X Error - disp: 0x7f1884a79880 serial: 87 error: BadValue (integer parameter out of range for operation) request_code: 154 minor_code: 24
    at org.lwjgl.opengl.LinuxDisplay.globalErrorHandler(LinuxDisplay.java:320)
    at org.lwjgl.opengl.LinuxContextImplementation.nCreate(Native Method)

@Cervator @emanuele3d ping!

A quick search reveals several reports with that error (some related to running Minecraft):

http://stackoverflow.com/questions/28867285/lwjgl-reports-that-opengl-is-not-supported-on-a-modern-nvidia-card
http://askubuntu.com/questions/663486/nvidia-drivers-cause-minecraft-to-crash
http://www.minecraftforum.net/forums/support/unmodified-minecraft-client/2607982-launcher-crash-report-trying-to-run-in-lubuntu-14

Interesting. The only two lines in LWJGLGraphics that can generate that error in the log are
Display.setTitle("Terasology" + " | " + "Alpha");
and
Display.setVSyncEnabled(config.isVSync());
Any other issue arising between those lines would have generated additional warnings in the log. Either ways, it seems out of our hands: the Display class is provided by LWJGL and the LWJGLexception being thrown seems to confirm this is an issue deeper than Terasology.
Hopefully skaldarnar's link provide a way out for the user.

Might be related to #2790  I had same error caused by nVidia drivers. After the last update, everything is fine.

Might be related to #2790 I had same error caused by nVidia drivers. After the last update, everything is fine.

Last update of the driver or Terasology ? :-)
Just to be sure. Yeah there was a "bad" recent nvidia driver package (#2790)

I had a similar issue on Linux. There's a bug handling multiple display outputs in lwjgl versions after 2.9.0 or 2.9.1. It is fixed in their 2.x master branch (PR: https://github.com/LWJGL/lwjgl/pull/116). I compiled lwjgl manually and replaced the lwjgl libraries in the latest Terasology release. After that the game runs perfectly.

I am currently having this issue on Linux. Can @taisph go into greater detail about how to replace the replace the lwjgl libraries?

@njbbaer Ugh. Basically you'd have to pull the master branch from https://github.com/LWJGL/lwjgl, follow their guide and build the binaries. Then you have to find the correct files in the resulting build and replace their counterparts in Terasology; in libs and natives/linux if I remember correctly. I am sorry I cannot be more specific than this but it's been awhile.
TBT, the Terasology team should consider upgrading the bundled lwjgl-2.9.x files to a working nightly or just build them manually. @skaldarnar?

Sorry for missing your earlier comment there @taisph - thanks for linking that issue :-)
I think we briefly looked at a later LWJGL quite a while back, although I think it was for some unrelated bug fix for applet support that has now been discontinued anyway. So we just put all that off to a future consideration of going LWJGL 3 or LibGDX.
But if there's a fix that tasty in the latest LWJGL nightly then we might indeed need to retry that. I wish they'd just release a 2.9.4 formally already :-)

Unfortunately this affects me as well and I can't play the game on Linux.
NVIDIA driver: 390.25 (GTX 960m)
Terasology build: http://jenkins.terasology.org/job/TerasologyStable/74/


fix(api): ensure a 409 is raised when cancelling a user with downstream objects

This ensures a 409 error is raised with the proper error to ensure the user knows why they cannot cancel the account. Beforehand it would show a 500 error because django.db.models.deletion.ProtectedError would be raised.

Current coverage is 87.76% (diff: 71.42%)

Merging #1147 into master will decrease coverage by 0.04%

@@             master      #1147   diff @@
==========================================
  Files            42         42
  Lines          3675       3679     +4
  Methods           0          0
  Messages          0          0
  Branches        632        632
==========================================
+ Hits           3227       3229     +2
- Misses          294        296     +2
  Partials        154        154

Powered by Codecov. Last update 48dc617...2e2a2fb


Upgrade aws-sdk-go-v2

What this PR does / why we need it:
Mainly:

upgraded aws-sdk-go-v2 especially aws-sdk-go-v2/service/ecs

Associated tasks:

upgraded other aws-sdk-go-v2/**/* to solve the breaking change.

cf. https://github.com/aws/aws-sdk-go-v2/issues/2370#issuecomment-1953308268

fixed compile errors caused by the breaking change.

in pkg/filestore/s3/s3.go and pkg/app/piped/platformprovider/ecs/client.go
cf. https://github.com/aws/aws-sdk-go-v2/pull/2333

fixed a test sinceRestartPolicy is added and the row number slided

in pkg/app/piped/platformprovider/ecs/diff_test.go

Which issue(s) this PR fixes:
Fixes #5144
Does this PR introduce a user-facing change?:

How are users affected by this change:
Is this breaking change:
How to migrate (if breaking change):

reopen for rerun snyk test

re:reopen for rerun snyk test


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 93 ms

Resolved: ClamAV performance has improved in a04f31d after 22 minutes.


Having ErrorException in EncryptionServiceProvider.php line 25:

I am trying to install this project to Homestead on windows 10 machine.
After installation I am having following error in all version of php 7.0, 7.1, 7.2
ErrorException in EncryptionServiceProvider.php line 25:
Even I have installed mcrypt and so on.
Please help.

FWIW, Dockerfile on develop branch lists required system dependencies.

Thanks a lot. Is there any guide to host this code in single machine without docker?

try to use PHP5.6 and follow instructions: https://github.com/SlovakNationalGallery/webumenia.sk#local-installation
it's laravel based app. so for more info, check https://laravel.com/docs/5.2/installation
regarding your exception - it seems like you are missing "mcrypt" extension. try to install it.
good luck. in case of troubles let us know.

@Ahnaf have you been able to get this up and running?

Closing this due to no response. Please feel free to re-open if you're still having issues.


Large image won't crop

Hi Helloyako,
I get a very strange result when trying to crop large images (most of the pictures I took with the phone's camera) :

In most cases the app will simply crash and but looking at the logs, it is because of an OOM error ("Failed to allocate a 63489036 byte allocation with 11027464 free bytes and 10MB until OOM" for a 2MB image).

In other cases the app wil crash because of an illegal argument exception :
java.lang.IllegalArgumentException: height must be > 0
at android.graphics.Bitmap.checkWidthHeight(Bitmap.java:446)
at android.graphics.Bitmap.createBitmap(Bitmap.java:822)
at android.graphics.Bitmap.createBitmap(Bitmap.java:791)
at com.naver.android.helloyako.imagecrop.model.CropInfo.getCroppedImage(CropInfo.java:62)
at com.naver.android.helloyako.imagecrop.model.CropInfo.getCroppedImage(CropInfo.java:36)
at com.naver.android.helloyako.imagecrop.view.ImageCropViewBase.getCroppedImage(ImageCropViewBase.java:966)
at com.example.vincent.osmtest1.CropActivity$1.onClick(CropActivity.java:120)
at android.view.View.performClick(View.java:5697)
at android.widget.TextView.performClick(TextView.java:10826)
at android.view.View$PerformClick.run(View.java:22526)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:158)
at android.app.ActivityThread.main(ActivityThread.java:7224)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)

In rare cases it wil "work" : the app won't crash but the cropped image's width will be the same as the crop rectangle's but it's height will be the same as the original one (I'm only using 1:1 ratio in order to display square images once cropped.

In VERY rare cases it will work fine but a log will still show up and tell there was an OOM error (but not fatal)

For small images the crop action works just fine =)

I know you already encountered some on these issues but since they were fixed I have absolutely no idea why this is happening.

@MasterTrollVG78
Hello, Nice to meet you :)
Is this sample app problem?

Try adding
android:largeHeap="true"

to your
<application
    android:largeHeap="true"
></application>

in AndroidManifest.xml

if issue were continue, reopen please.


Cache implementation improved

Fixes:

#56: Improperly Cached Attendee List
#49: Caching of data
#48: Opening Dashboard shows 0 tickets sold

Changes Done

Store data as it is fetch first from server into local storage.
Display UI first from cache but keep spinner loading then , after new data arrives update the UI asynchronously and stop the loading spinner.
Lint improvements. ZERO lint errors in code.

Since diffs are large for this PR, here's an APK to test out first
https://drive.google.com/file/d/0B5We_XfKpwDZSjhRNWFsb3V5Z1U/view?usp=sharing

@niranjan94 Working on it.

@niranjan94 Done.


Update CODEOWNERS

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.84%. Comparing base (f96bcf9) to head (7b94e79).
Report is 2 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #63   +/-   ##
========================================
  Coverage    99.84%   99.84%
========================================
  Files           23       23
  Lines         1301     1301
========================================
  Hits          1299     1299
  Misses           2        2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


261 - Resolve a bug with false values on dataframe create

This resolves #261.  The core issue was that creating a
dataframe from an array of hashes wasn't working properly
when some of the values were false.

Booleans are so central to data analysis.  We need to be really careful using the common Ruby idioms a || b and a ||= b when working with data values so we don't confuse false and nil.


Fix prospectus scrolling

The table is larger than the page. But it won't scroll on x-axis. This PR fixes this problem by make it scrollable on the prospectus page.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #692   +/-   ##
=======================================
  Coverage   74.36%   74.36%
=======================================
  Files          72       72
  Lines        2731     2731
=======================================
  Hits         2031     2031
  Misses        700      700

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 84c6551...ec57b07. Read the comment docs.


Odoo 17 now requires pg_trgm

As reported by @pedrobaeza in https://github.com/OCA/sale-workflow/pull/3232#issuecomment-2227842356, it seems that Odoo 17 now requires the pg_trgm extension to be installed.
This requirement was introduced recently in this commit https://github.com/odoo/odoo/commit/85b2ede4ee59bf18cdbee4ef97e9da3f023887c2
@pivi-odoo as author of that commit, maybe you can say if it was intended to add pg_trgm as a hard dependency in 17.0?
If yes, we can likely do it in oca_init_test_database.

Thanks for reporting the issue, we are aware of it, a fix is on it's way.
pg_trgm is not not required.

Thanks, please ping when the PR is done for tracking it.

Fix PR for 17.0: https://github.com/odoo/odoo/pull/173101

Thanks @pivi-odoo. Closing this as there is nothing for us to do in this project.


[iOS] Memory usage issues related to DashToHls_ReleaseHlsSegment

I don't know whether this is true of other/all STL implementations, but on iOS at least (tested on SDK 8.4 in C++98 mode), vector assignment preserves capacity if the LHS is larger than the RHS. Therefore, when an empty vector is assigned to the desired position within DashToHls_ReleaseHlsSegment(), no actual deallocation takes place. This quickly builds up to hundreds of Megabytes, and eventually iOS will kill the application for using too much memory.
Compiling in C++11 mode solves the problem (if this is a feature of C++11, it'd be nice to require C++11 compatibility); so does using std::map's erase() to remove the element.

It does appear that Apple has a bug with C++98.  I'd recommend using C++11 or higher.

Did this resolve your issue when using C++11?


Add  component

My site would benefit from a  component, that would work similarly to the already existing <client-only> component.
There is a component that relies on WebSockets (to keep the data updated at all times), which I wrap in a <client-only> tag. However I'd like search engines to render some text in its place (which won't be updated in real-time). For this, I would like my component to be able to have a <client-only> and a <server-only> part.
I haven't found an alternative way to achieve this effect.

If I understood you correctly you already be able to solve your problem with just the client-only component.
You can provide the component with an optional placeholder slot (see the second example here) which is only rendered server side.
So having a server only part should be achievable like this
<client-only>
      <!-- empty default slot -->

      <!-- only rendered on server side-->
      <service-only slot="placeholder" />
</client-only>

If I understood you correctly you already be able to solve your problem with just the client-only component.
You can provide the component with an optional placeholder slot (see the second example here) which is only rendered server side.
So having a server only part should be achievable like this
<client-only>
      <!-- empty default slot -->

      <!-- only rendered on server side-->
      <service-only slot="placeholder" />
</client-only>

Indeed, it works. That you very much for your attention and your solution. I think I should close this issue.


Made the segment border "draggable"

Click and drag on a segment border to move it. Still WIP, but feedback is welcome.
Known issues:

Scrubber always jumps to border when trying to drag it.
Missing mouse over indicator for hovering over a border.
Dragging a border "over the edge" (out of the timeline) may break border dragging.

Resolves #68.

Fixed issues mentioned in the initial comment.
There are still warnings being thrown, for which I am unsure on how to fix them (when first cutting, and when dragging a segment border out of the timeline).

A cursor like col-resize seems like a better choice:

When you cut, the scrubber overlays the segment marker but if you try dragging the scrubber, you drag the segment:
https://user-images.githubusercontent.com/1008395/121021138-597da280-c7a1-11eb-9197-1cd53554dee2.mp4

When dragging a segment over another one, the segment merges with the next one. But if you drag it over a second one, it will not merge with both, which is unexpected. I would suggest to either make the separator stop at the next segment, visually highlighting that you can only remove one segment by dragging, or allow multiple segments to be merged.
https://user-images.githubusercontent.com/1008395/121021754-ff311180-c7a1-11eb-800f-8d1a13bb8919.mp4

The UI starts jumping around when you start dragging for no apparent reason:
https://user-images.githubusercontent.com/1008395/121024788-d65e4b80-c7a4-11eb-9134-ff9e49bb078e.mp4


feat: added getPreviousSibling utility function for getting closest pa…

I added a small utility function that will recursively search for a closest sibling matching a selector.  I'm thinking this will prevent an edge case where some erroneous element will weasel its way in between the header and a panel and break a content set.
It still uses previousElementSibling but will iterate until if finds a match.

Very fancy but this validation is already being handled by this._isHeader.  The approach you proposed leaves out h-tag inclusion for pfe-content-set use-cases where they don't have the attributes present.

Oh gotcha, I didn't catch that.  Let me update it to account for that and see if it looks any better.

I'm going to close this out - _isHeader is already validating the selectors and it's a source of truth for what a "header" is in the content set


Incorrect 'host' in sg_roles_mapping.yml.

It has to be 'hosts' not 'host'. if we do not have this correctly, you may land up deleting other indices of other users.
https://github.com/khezen/docker-elasticsearch/blob/master/config/searchguard/sg_roles_mapping.yml#L12
Please see Search guard code..
https://github.com/floragunncom/search-guard/blob/master/src/main/java/com/floragunn/searchguard/configuration/PrivilegesEvaluator.java#L1068
Thanks.
Jalaja

Thank you for reporting jalaja.

https://github.com/khezen/docker-elasticsearch/commit/773317c0a07da5030f9ef419dabfa3494dcd743b


Add some new permissions to the oidc role

Adding these permissions so that we can restore an EFS AWS Backup recovery point to a temporary EFS and then use that to datasync overwrite the contents of a target EFS with the backup.
https://mojdt.slack.com/archives/C01A7QK5VM1/p1697012005045799?thread_ts=1696967339.977299&cid=C01A7QK5VM1

No description provided.
Please add a little more detail next time!

Have added a description


nixos-rebuild: use log instead of echo, always print to stderr

Introduces a log() function, similar to logVerbose(), to replace
usage of echo for logging.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

https://github.com/NixOS/nixpkgs/pull/147272

@Artturin I don’t feel like these two overlap substantially?

Like, this change isn’t really changing any policy, except for putting some more things to stderr, which can be argued was an oversight in the existing script.

I will merge this, since it should be a non-controversial change, and then https://github.com/NixOS/nixpkgs/pull/147272 can be decided separately.


Gopro Hero 9 Won't Capture Videos or Photos

Hey,
So the API has been great and easy to setup, so thanks for that.
It seems as though all the functions that I call out, except .take_photo or .take_video, work.  I can connect to the camera no problem, download media from it onto my PC, pull information from the gopro, power off, etc.  When I try to run either the .take_photo or .take_video the screen on the gopro will start strobing in and out of brightness for a few seconds then the red light will blink and the rear screen shows a capture of a picture and has a little animation of it moving down on the screen.  The problem is that the image or video never actually saves in the memory of the SD card whether I try to pull it using python or just checking manually.  Also to mention there are no errors in python or anything that indicates that anything went wrong, it will complete the script.  When I take a photo manually, pressing the red button on top, there is none of that strobing that I see when using python, it's just the little animation of the image moving down on the screen and the red LED.
The kicker is that when I connected up my gopro hero 5 session instead everything works flawlessly including taking photos and videos.  So I don't think I'm doing anything wrong....I'm wondering if my firmware version or python version isn't compatible.
I am currently using the following:
Python 3.10.1
Gopro firmware  HD<IP_ADDRESS>.00
Windows 10
I see that you mentioned this would work on the hero 9.  What firmware version was on that?
Thanks,
Joe

Hi, please downgrade to 1.21 or 1.22
https://github.com/KonradIT/goprowifihack/blob/master/HERO9/HERO9-Functionality-Compatibility-Chart.md

Great thanks for the quick reply. I will try this out Monday.
Joe

I downgraded to 1.22 and that worked like a charm.
Thanks


fix undefined variable in setgeotransform

Typo in variable name inside setgeotransform.

Coverage remained the same at 8.681% when pulling ac50d0e2b977e301395fefdb944944c96789b038 on kandread:fix-setgeotransform into 78125ba71bfd664e61d5fa7d682c971d3a1bb7f5 on wkearn:master.

LGTM, I will merge in a few days if no additional comments arrive.
Thanks for the fix.


Web - Update Interest Area Page

Update Interest Area page should be implemented in the web project. Currently we have the create IA page, it looks like this.

I'll implement the Update IA page.

I've opened a PR. I'll close this issue after merging it.


Immutable component names

Closes #581.

Should the description be changes in the docs too? In particular:
:attr:`component_names` | List of the names components on this device. Direct children only

I take that usage of "List" to be the English word not the Python data structure. I think it's probably more readable/accessible that tuple, and the distinction is not important in that context.

@danielballan then failures look like caproto bugs....

@tacaswell Good catch. Opened issue: https://github.com/NSLS-II/caproto/issues/328

OK, that's clear, thanks @danielballan. Yes, I also noticed the consistently failing tests. Great the issue is uncovered!


Change tested versions. Adjust testing workflows to qed's account

It fails because of a failed docker pull. I need to dispatch the jobs manually to build the image first.


Odd render of box drawing glyph

The ╰ box drawing character is not rendered correctly.
How it should look (e.g., in GNOME terminal):

How it actually looks (in Extraterm):

Excerpt of string to reproduce the error
   💾     ❨JSDB❩  ╰─ Loading table synchronously

Note: does not appear to be a font-dependent issue; can reproduce with all the fonts I tried including powerline and non-powerline.
Also, if you type the character and select it, displays correctly in reverse. If you select it in the output of a command, you see that the curved area is being drawn but in a dark colour.

Thanks for this very clear bug report.
The fix is in now.

Thanks so much, Simon :)

Fix released in 0.54.0


pdctl: fix region key problems in detach mode

What problem does this PR solve?
Currently, pd-ctl doesn't support using --format in detach mode and also can not decode the key which contains some escape characters, such as \n.
What is changed and how it works?
This PR fixes this two problems. After this PR, we need to wrap the key with single quotes ' in pd-ctl.
For example, we can use the below command to find the region for a given key:
./pd-ctl -d -u http://<IP_ADDRESS>:2379 region key --format=encode 't\200\000\000\000\000\000\000\377\035_r\200\000\000\000\000\377\017U\320\000\000\000\000\000 \372\n'

Check List
Tests

Manual test

Related changes

Need to cherry-pick to the release branch
Need to update the documentation
Need to be included in the release notes

/rebuild