Implement structured field and rule paths, add field and rule values to ValidationErrors

This implements the structured field and rule paths, passing the conformance test changes in https://github.com/bufbuild/protovalidate/pull/265.
In addition, it also adds the ability to get the field and rule values. These are not present in the protobuf form of the violation.
The API is still heavily centered around the protobuf form of violations, but the ValidationError type is no longer an alias to the protobuf buf.validate.Violations message. The intention is that users needing access to the error information will still use the proto violations message, only using the "native" interface methods to access in-memory data that is not feasible to transport over the wire. (e.g. protoreflect.Value pointers.)
DO NOT MERGE until the following is done:

[x] https://github.com/bufbuild/protovalidate/pull/265 is merged
[x] Dependencies updated to stable version release

Well, it took a while, but I think this is the most bang-for-our-buck possible. I think it's not the best possible code by any single measure, but I tried to balance concerns of performance, simplicity and API surface. A lot of thought was put into exactly how paths are constructed: as before, we avoid constructing paths unless a validation error is actually encountered. A careful adjustment is made to the builder code to add just enough information to be able to produce the rule paths accurately in as many edge cases as I could find, without requiring new special cases to be distributed in more places. To minimize the resulting API surface of changing the error type, the protobuf form of a Violation is still the primary way to consume a Violation, and we only need to add a utility function and an additional type to the protovalidate package.
It would be difficult to convey the number of different considerations that wound up needing to be made, but hopefully the resulting code does not make this difficulty apparent. :)

After some discussion the API was updated to use a struct for the Violation type. The exposed surface area is roughly the same and there is probably more allocs in the error case, but it is a bit simpler.

Wound up making a few more tweaks:

Provide the FieldDescriptor for each field/rule value. It's sort-of needed because it is otherwise pretty hard to do anything safely with the protoreflect.Value values, since the API is rather limited.
Some last-minute additional refactors, which should reduce allocations around rule paths, and removes the wrapper abstraction added earlier. I think the wrapper abstraction was just trying way too hard to be clever. Instead, I've tried to push the behavior down to each evaluator by having a base struct they embed. The information that needs to be propagated is put into the value. It's not pretty, but it removes the need for the skipSubscript hack that was previously present, and it passes conformance currently.


Panel component updated

Now matches govuk-frontend, and makes use of latest libs
This changes the API for the Panel component to be more standard/logical than it previously was, so it now uses children for content and title prop for the title
Checklist:

[x] Documentation
[x] Tests
[x] Ready to be merged

Deploy preview for govuk-react processing.
Building with commit 9e83910b5ec3b56c814ea2d065f15d4a9df811c3
https://app.netlify.com/sites/govuk-react/deploys/5c586340174e74000849c7ea

Codecov Report

Merging #530 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #530      +/-   ##
==========================================
- Coverage   99.77%   99.77%   -0.01%
==========================================
  Files          84       84
  Lines         453      452       -1
  Branches       29       29
==========================================
- Hits          452      451       -1
  Misses          1        1

Impacted Files
Coverage Δ

components/panel/src/index.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Skip building podio tests in CI

Should speed up the build until we have some nightlies
BEGINRELEASENOTES

Skip building podio tests in CI
ENDRELEASENOTES

Podio is included in the LCG releases now, so this is not necessarily needed.


Not able to get data in the Hygieia Widgets

Hi team,
I am currently using latest Hygieia 3.1.0
I am able to login the dashboard and configured the dashboard with the build and Jira widgets.

i am able to fetch data in widgets but not able to see data in graphs

node -v
v10.16.3
npm -v
6.9.0
npx -v
6.9.0
mvn -v
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T22:11:47+05:30)
Maven home: /opt/apache-maven-3.3.9
Java version: 1.8.0_242, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>.b08-0.el7_7.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1062.12.1.el7.x86_64", arch: "amd64", family: "unix"
any lead would be helpful

@rvema  @Sbrenthughes  need help on this issue

@shubhamk0305 just keep the collectors running for some time initially as it takes some time to initialize and populate the db. Restart them after some time and you will see they will be populated. I know its weird but that's how i also got it running.


Speed up tests

Current goals:

< 45 min on PR
< 20 concurrent jobs on PR (enterprise tier of github actions has a limit of 180 concurrent jobs)

Current state (for dd27013 in master):

~ 50 min
24 parallel jobs

Further improvements should be for:

test_series.py
test_groupby.py
test+default.py

pytest modin/pandas/test/ takes me 2.5 hours locally (the pandas test suite with --skip-slow --skip-db takes 23 minutes).
Of this, test_join_sort takes 55 minutes, test_groupby takes 37, test_series takes 18, test_indexing takes 17

@jbrockmendel that local command only runs tests with the ray. It doesn't test the dask engine at all and skips many tests in the CI. Here is an example recent successful CI run. The whole thing took 1h 17 minutes. Note that the CI benefits from parallelism across tests.
test_join_sort has way too many test cases.

In this vein, test-compat-win (engine dask, python 3.6) has been notoriously slow in CI for some time now.

One thing that we could do to make CI faster for test-compat-win is to launch parallel jobs of pytests similar to what we do for test-windows right now.

Another note: this PR https://github.com/modin-project/modin/pull/6267 seems to be a good example were testing only PandasOnPython is not enough - we should try to keep at least some tests which are bumping into Ray peculiarities. Seems that test_map_metadata.py is a good candidate.

Think more what we run regarding ASV - whether we really care about that in PRs, or maybe we can drop this from PRs and instead run this on merges to master comparing current and previous commit or something similar? cc @anmyachev

ASV tests are only run when there are changes in asv_bench folder, which is quite rare.

Add running the whole test suite on PandasOnPython backend on Windows

@vnlitvinov do you mean BaseOnPython execution? Or are we just not testing PandasOnPython at all right now, so I don’t see it?

@vnlitvinov do you mean BaseOnPython execution? Or are we just not testing PandasOnPython at all right now, so I don’t see it?

We aren't testing PandasOnPython on Windows at all, and BaseOnPython is a different thing, it cannot substitute testing for Ray or Dask because it uses different query compiler (and it's using a partitioning mechanism).


Update() destroys existing second-level relationships

Looks like Person.Save() saves only first level relationships, just like the README says. However, second-level relationships are destroyed if they already exist.
The most inmediate fix would be to avoid this behaviour, making Update() ignore second-level relationships instead of deleting them.
As, in most cases, one would want to change just the relationship itself and not the whole depending object, a plain Update() function may be appreciated.
In fact, I think the case where you want to edit an object and its relatives in the same operation is fairly common for insertions, but relatively rare for updates. So making this new "plain update" the default behaviour and delegating the current "full update" operation to a different method might be worth considering.

Thanks for reporting this! We'll look into this issue as soon as we can.
Because of the breaking changes, it could not be default behavior until 2.0, but we can add a UpdateOnly or something like this.

NOTE: Reproduction case has been merged in fix/save-relations. The bug will be fixed in that branch and then PR'd.


Allow specifying rent payer when creating NFT

The pull request is ready for your review!

@sjchmiela this is deployed to devnet + mainnet 👍


DB optimizations

We're pushing the limits of MySQL with our usage of example_utterances, and we need to be more careful if we want to survive.

Pull Request Test Coverage Report for Build 218

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.02%) to 54.48%

Totals

Change from base Build 209:
0.02%

Covered Lines:
4184

Relevant Lines:
7119

💛  - Coveralls


Multiple slave select lines on one SPI bus

I was reading through the rppal documentation and am wondering if a single Spi struct allows for multiple slave select pins. From what I can see there is only a single slave select line defined in new(). I cannot find a way to switch or change this value. Should I create a new Spi struct for each slave device? Any help would be appreciated, thanks!

Hey @willAlbertini707, apologies for the late reply. For SPI, RPPAL is just a wrapper for the underlying linux driver accessed through the available spidev character devices. Since each bus/slave select combo is accessed through a different spidev interface, you would have to create a new Spi struct for each slave device. I haven't actually experimented with this myself, but in theory that should work.
An alternative option would be to create an Spi struct for the SPI bus you want to use, and instead of using the pre-configured SS pins, use any other available GPIO pins for Slave Select and manually change those to high or low as needed.

I created a new Spi struct for each and it seemed to work, thanks!


Deal with .pbxproj file issue

May be a .gitignore fix, but the file is necessary for development, so it's hard to say.
Maybe going forward we should just avoid committing changes to it.

I think we can avoid committing changes to it by doing something like git add app/ rather than git add .


Tab do not move focus

At this dialog:

When I press Tab control is moved to Cancel.
When I press Tab again control is left on Cancel  <<< this is unexpected. Focus should be moved
When I press Tab second time it is moved to Ok

After Cancel focus moves to checkbox (Remember choice). Then to Ok, then back to Cancel.
 I am on Linux mint 18.3 Cinamon

Kazam_screencast_00000.mp4.zip
Here you can see that Cancel is still highlighted, but focus is actually on Remember choice


How to accept changes to ui tests?

I've changed an error message, and now I need ui tests updated. I know there's a command for this, but I can't find it in the docs.
I'd expect this command to be listed here: https://rust-lang.github.io/rustc-guide/tests/running.html

It's documented here: https://rust-lang.github.io/rustc-guide/tests/adding.html#editing-and-updating-the-reference-files
But yeah, it should (also?) be in the running chapter.

Great! The other page answers my question. Unfortunately, googling sent me to the running page.


Only start metrics daemons when user is on page

Right now we are always running the metrics daemons regardless of whether the user is paying attention to them. This is needlessly wasteful.

No longer the case.

How did you determine this, did you read the metrics daemon code in embassyd? I'm pretty sure this runs for the entire duration of embassyd..

I thought this was referring to the FE Metrics daemon.

Keeping daemon for new widgets metrics


prefer-conditional-expression: add option "avoid-nested"

We should try to avoid suggesting nested conditional expressions. We already avoid if-else-if-else when "check-else-if" is not enabled. However you still end up with nested conditional expressions if one of the assignments in an if-else contains a conditional expression:
if (foo) {
    bar = 0;
} else {
    bar = baz ? 1 : 2;
}

// requires you to write this:
bar = foo ? 0 : baz ? 1 : 2;

Do we want to avoid this by default and add an option to enable nested conditional expressions?
Or leave the default unchanged and add an option to avoid this behavior?

☠ TSLint's time has come! ☠
TSLint is no longer accepting most feature requests per #4534. See typescript-eslint.io for the new, shiny way to lint your TypeScript code with ESLint. ✨
It was a pleasure open sourcing with you all!


[BEAM-11456] Fix flaky table provider tests (Kafka and Pubsub)

Hopefully this will help with these tests being flaky or at least decrease flakiness rating.

Run SQL PostCommit

Run SQL PostCommit

Run SQL PostCommit

Run SQL PostCommit

Run SQL PostCommit

Run SQL PostCommit

Run SQL PostCommit

Run SQL PostCommit

R: @TheNeuralBit Could I ask you to review this small PR? You're the closest one to this part of code.
Kafka IT tests became flaky when they were running in parallel. It seems that setting 2 threads reduced the flakiness but only partially.  I also increased the timeout times, just in case.

Run SQL PostCommit

Run SQL PostCommit

@TheNeuralBit Thanks for motivating me to do something better than reducing the thread amount.
I've got rid of inheritance and replaced it with parameterized tests and added some SuppressWarnings to make the code look cleaner in IntelliJ.

Run SQL PostCommit

Is it ready to be merged? I see that it was already approved.

Is it ready to be merged? I see that it was already approved.

Nope, there was an approval but I wanted to follow up the suggestion to do it in a better way and refactored the code so the tests now are parameterized and run sequentially. So it's waiting for review atm

Sorry lost track of this! Taking a look now


Arche reports "&" instead of real "amp"

https://jupyter.scrapinghub.com/user/user-redirect/lab/tree/shared/QA/New projects/NOTHS/google.co.uk/DoD-1100_google_completion_Oleksandr.ipynb
If to download the csv format of data then the issue appeared as extra "amp" in text, but Arche reports "&" symbol exactly

That's fixed in #122 , but I noticed another issue - somehow there are more results than should be.
305 items affected - 15.2% of 'suggestions' values contain </b>, <b>: 604, 949, 239, 967, 394, 1287, 1953, 1737, 1348, 1961

1742 items affected - 87.1% of 'suggestions' values contain &amp, </b>, <b>: 1619, 339, 1481, 655, 1927, 1187, 691, 1497, 1242, 1469

1693 items affected - 84.7% of 'suggestions' values contain &amp, </b>, <b>: 1497, 806, 1589, 1769, 638, 1381, 1482, 892, 342, 1673

1607 items affected - 80.3% of 'suggestions' values contain &amp, </b>, <b>: 7, 1651, 1718, 1980, 1570, 1694, 450, 1595, 1031, 1549

1561 items affected - 78.0% of 'suggestions' values contain &amp, </b>, <b>: 369, 163, 1417, 1718, 177, 341, 1526, 1581, 1212, 1822

1494 items affected - 74.7% of 'suggestions' values contain &amp, </b>, <b>: 1656, 839, 611, 57, 24, 1417, 382, 642, 339, 1314

1434 items affected - 71.7% of 'suggestions' values contain &amp, </b>, <b>: 866, 13, 1049, 1396, 1628, 1169, 355, 1438, 979, 1381

1389 items affected - 69.5% of 'suggestions' values contain &amp, </b>, <b>: 229, 629, 296, 853, 308, 326, 693, 88, 996, 1089

1337 items affected - 66.8% of 'suggestions' values contain &amp, </b>, <b>: 1173, 857, 1870, 1036, 1446, 1627, 127, 1103, 37, 62

1299 items affected - 65.0% of 'suggestions' values contain &amp, </b>, <b>: 860, 157, 1110, 623, 1934, 1500, 112, 213, 451, 1372


Combine everything for final WOC workable Web application

Make the Contribution in front end and back end compatible with each other , using appropriate middle ware

Describe the issue clearly, avoid using terms like everything middleware etc

Also use the correct label please


[HOTFIX][#18] Add Plugins to .releaserc.json and release.yml

Refs: #11, #18

:tada: This PR is included in version 1.1.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Example path for images needs updating

I noticed the examples have the niivue image path listed as https://github.com/niivue/niivue/raw/main/demos/images/, which results in this not found error:

changing the path to path = "https://github.com/niivue/niivue/raw/main/packages/niivue/demos/images/" fixes this.

Hey @AnthonyAndroulakis! Thanks for pointing this out! PR #80 which should merge soon will simplify the use of example datasets and should fix this issue at the same time. I'll flag this issue in that PR so that we make sure it does. We should also ensure the CI runs the example notebooks when commits are done on a PR so that any future changes that break notebooks get automatically flagged and fixed before merging!


[FLINK-14843][e2e] Refactor bucketing sink test to make it more stable and comprehensible

What is the purpose of the change
Refactor bucketing sink e2e test to make it more stable and comprehensible.
Brief change log

For BucketingSinkTestProgram, set inactiveBucketCheckInterval and inactiveBucketThreshold to 2000 and 4000 respectively
only count records in part-* files to get total valid data
remove "sleep 10" between two failover to make it comprehensible

Verifying this change
Existing e2e test.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run travis

@flinkbot run azure

@flinkbot run travis

@kl0u Can you help to review this PR? Thanks

@kl0u is currently on vacation but I'm sure he'll have a look once he's back.


Error bars/whiskers on bar charts

Tried to convince chartGPT to plot error bars/whiskers on either side of a value but the result either ignored the error bars or threw back an error. Seems like it would need to recognize some standard language associated with error margins (e.g. +/- 3) or understand explicit requests (e.g. "add an error margin band of 12 on either side of the value").
I see the app users Recharts for plotting data. Recharts has an "ErrorBar" component that could accommodate this user case for bar/line/scatter plots --> https://recharts.org/en-US/api/ErrorBar

It's not a supported type, will add it soon


Get response after successful or unsuccessful payment

Hello, how can i get the response after payment is success or unsuccessful ??

You can follow the esewa's developer doc @SwikarBhattarai


Upgrade to latest version of cfpb-chart-builder for CCT release

This needs to be deployed Monday 9/24
Changes

Upgrade to latest version of CFPB Chart Builder which includes changes from v3.8.0 and v3.8.1

Testing

./setup.sh
add a chart block with inquiry data (details in testing notes on #4531)
Confirm charts match screenshots

Screenshots
Inquiry index

Credit tightness

Notes

The charts aren't loading on IE9 and IE10 with the latest version of chart-builder. I've done visual QA in other supported browsers and confirmed it's working in those, so we'll go forward with this version to launch and follow up with thoroughly QAed fixes to IE9/10 after launch.

Todos

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the development playbook
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Visually tested in supported browsers and devices (see checklist below :point_down:)
[ ] Project documentation has been updated
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist
Browsers

[x] Chrome
[x] Firefox
[x] Safari
[x] Internet Explorer 8, 9, 10, and 11
[x] Edge
[x] iOS Safari
[x] Chrome for Android

Accessibility

[x] Keyboard friendly
[x] Screen reader friendly

Other

[x] Is useable without CSS
[x] Is useable without JS
[x] Flexible from small to large screens
[x] No linting errors or warnings
[x] JavaScript tests are passing

IE11
Inquiry index

Credit tightness


The access rate limitation (ask)

Question
Did the google limit the access for this mechanism ?
For example, I deploy this feature in server nodejs. Then there are 50-100 users simultaneously access this feature to get the search results. I worry google will block the access like a spam bot.
Thank you.
Other details
No response
Checklist

[X] I am running the latest version.
[X] I checked the documentation and found no answer.
[X] I have searched the existing issues and made sure this is not a duplicate.
[X] I have provided sufficient information.

I use this for a few projects and never faced a 429, but it might happen and honestly the only way to bypass it would be using proxies (ex: #29) or add some sort of delay between requests.

I see. Thank you for your hard work. I will try to use that way.

I use this for a few projects and never faced a 429, but it might happen and honestly the only way to bypass it would be using proxies (ex: #29) or add some sort of delay between requests.

I'm getting error 429 after few search (without spamming) using boolean operators


Specify in which Queue a completion block should be executed

What
Right now we are executing completion blocks in a background thread, this could be a potential problem for future uses (like UnsplashKit)
Proposal
When executing a request, specify in which Queue the completion block should be called. If not specified, the Main queue should be used by default.

Fixed here https://github.com/carambalabs/CarambaKit/commit/dc693353774bf20ba5a6d3c2c3e02929a1c6f51d


CI failing

Description
The CI failing is caused by go version in gitea/test-env image. This PR to gitea/test-env should address the issue.
Gitea Version
main
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
N/A
Database
None

Solved


Fixes #204 - actually parse the correct property & fix the unit tests

Fixes #204

accidentally pushed my local vendor/knative.dev/test-infra changes (so I could run them on OS X)  - should be good now

sigh commit -a trouble lol

/assign @mattmoor

@mattmoor I'm not an approver ;)

/approve
Do you want to be? 😉

Do you want to be? 😉

gotta earn it 🤣


Remove or change Menu Item 3

Describe the bug
Menu Three appears in the header. This can be removed until the compare functionality is implemented.
To Reproduce
Steps to reproduce the behavior:

Go to any page on the site
See error

Expected behavior
Menu Three doesn't appear
Screenshots

Additional context
This is likely where the Compare function goes in the future.

This is the link to the About page now.


ApprArmor denies sigkill signal on Ubuntu 22.04.5 LTS, docker 24.0.5 (latest/stable)

I observe the behavior on Ubuntu 22.04.5 LTS, using snap package 24.0.5 (latest/stable).
It used to work fine previously, but likely stopped working with some updates in the last few months.
Upon doing a simple "docker container stop #containername#", three log entries will appear in dmesg:

[992750.699273] audit: type=1400 audit(1730648846.097:83): apparmor="DENIED" operation="signal" profile="docker-default" pid=3479255 comm="runc" requested_mask="receive" denied_mask="receive" signal=term peer="snap.docker.dockerd
[992752.754437] audit: type=1400 audit(1730648848.153:84): apparmor="DENIED" operation="signal" profile="docker-default" pid=3479261 comm="runc" requested_mask="receive" denied_mask="receive" signal=kill peer="snap.docker.dockerd"
[992762.756895] audit: type=1400 audit(1730648858.156:85): apparmor="DENIED" operation="signal" profile="docker-default" pid=1676 comm="dockerd" requested_mask="receive" denied_mask="receive" signal=kill peer="snap.docker.dockerd"

The error received at the command line is simply:
Error response from daemon: cannot stop container: #contername#: permission denied
User initiating the command is a member of docker group, and the issue still occurs leveraging sudo privileges.
The workaround is simply sudo kill #pid the container process, and the container stops as expected.

Hello, thank you for reporting this issue, we appreciate that.
This is a known issue already reported on: https://github.com/canonical/docker-snap/issues/36
We are working to solve this. But in the meantime, you may want to try this workaround solution.

This workaround didn't work for me.
I deleted the file as instructed and issued a "service docker restart" to restart the docker service.
I observed no change of behavior, including on a container I restarted
Reading a bit more about the issue, it appears like there was a regression already fixed by the official package. https://github.com/moby/moby/pull/47749
However, it hasn't been backported to 24.x because that branch is not maintained anymore.

@Vlurk Thank you for the additional information!
The current version available on the latest/stable channel for the Docker snap is version 24.0.5, as shown by running:
$ snap info docker
...
...
channels:
  latest/stable:    24.0.5   2024-09-03 (2932) 138MB -
  latest/candidate: 24.0.5   2024-09-03 (2932) 138MB -
  latest/beta:      27.2.0   2024-09-19 (2963) 146MB -
  latest/edge:      27.2.0   2024-09-20 (2969) 146MB -
  core18/stable:    20.10.17 2023-03-13 (2746) 146MB -
  core18/candidate: ↑
  core18/beta:      ↑
  core18/edge:      ↑
installed:          24.0.5              (2932) 138MB -

However, version 27.2.0 is currently available on the beta channel.
We are currently testing the Docker snap on beta to ensure it runs smoothly without any regressions, and once these tests are complete, this version will be promoted to stable.
In the meantime, you may consider switching to the beta channel:
sudo snap refresh docker --beta

Once version 27.2.0 is promoted to stable, you can switch back to the stable channel:
sudo snap refresh docker --stable

Version 27.2.0 is now on latest/stable. This version includes the aforementioned fix: https://github.com/moby/moby/blob/v27.2.0/profiles/apparmor/template.go#L28-L31


tetrio-plus-desktop: init at 0.23.13

Things done

Built on platform(s)

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 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

[x] Fits CONTRIBUTING.md.

I've packaged tetrio plus as an option for tetrio-desktop, is this PR still relevant?

Nah, PR is no longer relevant


fix: Deprecate UnsetBorderTopBackgroundColor in favor of UnsetBorderTopBackground

This looks like a looong standing typo :)
This is the only one method ending by "Color". To avoid breaking changes, i've just copy/paste to a new one, directly call this new one, and add a deprecation notice.

Wow, indeed it was. @aymanbagabas, heads up for v2.


purejavacomm support in JDK 1.7 32 bit

Does purejavacomm APIs support with JDK 32 bit?

On 20 Jul 2015, at 15:03, VipinMca<EMAIL_ADDRESS>wrote:
Does purejavacomm APIs support with JDK 32 bit build?
—
Reply to this email directly or view it on GitHub.

On which platform?
Regardless, I think PJC is mostly 32/64 bit agnostic so it
should "just work”.
br Kusti


Add gcompris educational package

Motivation for this change
Add gcompris, which is a mandatory educational package for kids.
Things done

[ X] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X ] Tested execution of all binary files (usually in ./result/bin/)
[ X] Fits CONTRIBUTING.md.

I've got this error:
 /nix/store/c90qjb1n7p7gkj4xf29rj8lx84jbm92h-gcompris-0.90/bin/gcompris-qt
QCursor: Cannot create bitmap cursor; invalid bitmap(s)
exeCount set to:  1
QQmlApplicationEngine failed to load component
qrc:/gcompris/src/core/main.qml:22 module "QtQuick.Controls" is not installed
qrc:/gcompris/src/core/main.qml:23 module "QtQuick.Window" is not installed
qrc:/gcompris/src/core/main.qml:21 module "QtQuick" is not installed
qrc:/gcompris/src/core/main.qml:22 module "QtQuick.Controls" is not installed
qrc:/gcompris/src/core/main.qml:23 module "QtQuick.Window" is not installed
qrc:/gcompris/src/core/main.qml:21 module "QtQuick" is not installed
qrc:/gcompris/src/core/main.qml:22 module "QtQuick.Controls" is not installed
qrc:/gcompris/src/core/main.qml:23 module "QtQuick.Window" is not installed
qrc:/gcompris/src/core/main.qml:21 module "QtQuick" is not installed

Cannot mix incompatible Qt library (version 0x50901) with this library (version 0x50903)
Aborted

Any idea about what is happening?

@nlewo try to install the package in your env : nix-env -i /nix/store/c90qjb1n7p7gkj4xf29rj8lx84jbm92h-gcompris-0.90/. The nixpkgs manual told so, I don't know why...

@guibou ok, it work with nix-env.

I fixed the enableParallelBuilding as requested by @jtojnar  and added a .desktop file entry. However this PR does not see the changes, I wonder why. I will let a few time to github to see if it refreshs itself and if not, I'll open a new PR.

@guibou looks like the PR has now been updated.
@GrahamcOfBorg build gcompris

Failure on aarch64-linux (full log)
Attempted: gcompris
Partial log (click to expand)
   Compiling backtrace v0.3.4
   Compiling rustc_const_math v0.0.0 (file:///build/rustc-1.24.0-src/src/librustc_const_math)
   Compiling proc_macro v0.0.0 (file:///build/rustc-1.24.0-src/src/libproc_macro)
   Compiling syntax_ext v0.0.0 (file:///build/rustc-1.24.0-src/src/libsyntax_ext)
building of '/nix/store/whsyh46wr0zfkw420xcc8ffgahszsd80-rustc-1.24.0.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/nfjkyviyyy9ly6hq1pj5wzy6qxmd491n-cargo-0.24.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/bbqaq71xj30lggbbbf6calm3g7g56c02-librsvg-2.42.2.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/z97wv2682mjz6bvgffwa3994ryav1vgs-gst-plugins-bad-1.12.3.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/npjyjxy73wzazv90r7gkhwj643v4g67b-gcompris-0.90.drv': 1 dependencies couldn't be built
error: build of '/nix/store/npjyjxy73wzazv90r7gkhwj643v4g67b-gcompris-0.90.drv' failed

@guibou could you either fix the aarch64 build or restrict the platforms to x86 only?

@nlewo
Done, set to [ "i686-linux" "x86_64-linux" ].

@GrahamcOfBorg build qmlbox2d

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: qmlbox2d
Partial log (click to expand)
Cannot nix-instantiate `qmlbox2d' because:
error: attribute 'qmlbox2d' in selection path 'qmlbox2d' not found

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: qmlbox2d
Partial log (click to expand)
Cannot nix-instantiate `qmlbox2d' because:
error: attribute 'qmlbox2d' in selection path 'qmlbox2d' not found

Thanks... from my child:)


Gpaste needs update for gnome3.18

The gpaste derivation version is ${gnome3.version}.3 but 3.18.3 does not exist yet. The most recent 3.18 version of gpaste is <IP_ADDRESS> (https://github.com/Keruspe/GPaste/releases). I can't submit a pull request yet because my computer needs to build gnome3.18 first.

/cc @lethalman

There's no hurry, you can package it when gnome 3.18 will be in the unstable channel.

but won't the 3.18.3 version number break the build? This release does not exist.

@DamienCassou yes it will, I believe there are also some other programs that will break. No worries :)

This has been fixed a long time ago.


[Feature] Make "main-server-url" a persistant and changeable value.

In the case of GDPSes, they can't use main.globed.dev, so they create their own server and instruct people to add said server.
However, a better solution would be to put the GDPS server url as the default without having to build it by yourself (which will get overwritten as soon as you update globed)
A way that could be done would be with a file that will not change regardless of updates, which will contain the main server url.

where would the said file be?
i'm not familiar with GDPS, would it be fine if Globed tried reading a file called globed-server.txt from the game directory, and if it was found, use the server URL from there?

If it stays persistent through globed updates, yeah.

it won't be touched by globed itself, Globed would simply check if a file called "globed-server.txt" exists in the game directory, and read the server URL from there if it does.
This means, if you include the file together with your gdps installation, it will always work across different globed updates
If you have better suggestions, please tell

I don't believe there's a better solution, this already suits well!

i was suggesting putting it in the game directory, near the GeometryDash.exe file, but if you have other suggestions then i'n open to ideas

i was suggesting putting it in the game directory, near the GeometryDash.exe file, but if you have other suggestions then i'n open to ideas

Either mod's folder or inside Resources

any updates?

already implemented in the code and will be added in the next update.
to find the URL, the mod will go through all of these in order until one of them is found:

The GLOBED_MAIN_SERVER_URL variable
globed-server-url.txt file in the game folder
globed-server-url.txt file in the mod's config folder
globed-server-url.txt file in the mod's save directory
The default value, `https://main.globed.dev

added in v1.7.1!


BUG:Add FavIcon in the blogPage and scrollbar is not styled

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
when we redirect to the blog page favIcon is not there also the scrollbar is not styled.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hello sir @Suchitra-Sahoo
I'm a GSSOC'24 contributor...i want to work on this issue please assign this task to me..i will complete this task with in one day


Maybe from multiple

Ebert has finished reviewing this Pull Request and has found:

7 possible new issues (including those that may have been commented here).
5 fixed issues! 🎉

You can see more details about this review at https://ebertapp.io/github/D3MNetworks/ronad/pulls/15.


Update the version of Alpine in governmentpaas/curl-ssl

The current Alpine version, 3.3, has DNS problems with Kubernetes. Is it possible to update it to 3.8?
A related issue gliderlabs/docker-alpine#255.

Hi @vadimeisenbergibm - thanks for this issue. We'll have a look at updating to 3.8.
I'd caution against using this image for anything production-like though - it's maintained for internal use cases, and we don't provide any guarantees of stability, security or fitness for purpose.

Hi @richardTowers, thank you! I do not intend to use this image for production, only for testing and demos of istio.io


how to test nan

I have nan in an array and for instance data[7772, 4465] is nan
If I do:
snuggs.eval("(== d a)", d=data[7772, 4465], a=data[7772, 4465])
I get
False
How do I to the test nan in data?

nan == nan always evaluates to False in Python. That's the way it is. You will need to replace or mask out the nans in your data.


control+o can't work

control+o should return last page ,but it doesn't work

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/22181810-control-o-can-t-work?utm_campaign=plugin&utm_content=tracker%2F252770&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F252770&utm_medium=issues&utm_source=github).

Duplicate #774

Yea, we should close this out if at all possible. I would suggest all further discussions occur in #774

Thank you very much!


New Station: Behemoth (autofailed PR attempt because I can't read)

kinda want a better name but this works for now
large station with sections of maints inside asteroid bits
to me this station is already completely done, may need to rework maints a bit. I've tried and tried again to start a round with it but I do not know what I am doing wrong as I cannot roundstart any map, it just gets stuck at "round starting now" for all maps. Help would be greatly appreciated so I can full
I just copied the kettle prototype file, job counts will probably need to be adjusted
(looks a bit empty in spot as spawns are hidden)

holy shit how did I not see a post about this until this

~holy shit how did I not see a post about this until this~ nevermind I remember seeing it like once in discord lol

yeah, I've been showing it around to a lot of people and live streaming building it in VCs to get ideas and suggestions. Probably should've made a draft PR aswell


Include preprocess_image from the model for drive.py to work.

Use student's pre-processing method
Fix for the problem of car not moving in autonomous mode even when trained model.h5 file is supplied as argument.
The drive.py script should use the student's preprocess_image method because it was how the model was trained in the first place. This should perhaps be documented in the course instruction so that the name remains the same.
About throttle/speed
Also, the current throttle and speed seems to be too slow. Perhaps something like: throttle = (17.0 - speed) * 0.5 would be better?

This looks like it's your project submission. You don't need to send a PR for that just submit your repo in when you submit your project.


Twitter: Failed to load rate_limit_status.json?resources=statuses

Ripme version: 1.7.95
Java version: openjdk version "16.0.2" 2021-07-20
Operating system: Win10
Exact URL you were trying to rip when the problem occurred: a Twitter profile

Expected Behavior
RipMe should start crawling the Twitter user's post history for things to download.
Actual Behavior
Crawling immediately fails with the error:

"Failed to load https://api.twitter.com/1.1/application/rate_limit_status.json?resources=statuses after 1 attempts"

There were news recently that Twitter will start enforcing stricter rate limits on the API, so this is probably that. fxtwitter managed to get around this problem somehow, so this might be solvable.

Update - having retried it every hour or so, it finally succeeded in scraping without an error. Will keep trying with other Twitter profiles to see if there's consistency to it.
I also just remembered that I've had unusual API rate limit problems before, but those threw an 'API limit exceeded' error instead of the one above, and weren't as persistent(usually going away after a few minutes instead of hours). This could be the same issue, but with RipMe not recognizing it as such due to API changes.


Process Accept header MIME types in case-insensitive way

The Accept header is processed case sensitively when user requests for manifest. So the following is not matching to manifest v2.
Accept: Application/vnd.docker.distribution.manifest.v2+json
But according to spec, media type should be case insensitive:
Both top-level type and  subtype names are case-insensitive.
https://tools.ietf.org/html/rfc6838

@yuwaMSFT2 Care to make a PR?

@manishtomar Sure. Will prepare a PR.


How to train in LoveDA

Hi~The implementation of LoveDA datasets is located in dataset/dataset.py.
You only need to change the potsdam dataset to LoveDA dataset in the main training file.
Thanks~

Closed as long periods of inactivity, feel free to reopen if there is any problem.


Issue 2: Adding personal page

Description
In this PR:

I've added my personal page, with my ENS, and some social links

Additional Information

[x] I have read the contributing docs (if this is your first contribution)
[x] This is not a duplicate of any existing pull request

Related Issues
_Closes #9
Note: If your changes are small and straightforward, you may skip the creation of an issue beforehand and remove this section. However, for medium-to-large changes, it is recommended to have an open issue for discussion and approval prior to submitting a pull request.
Your ENS/address:0xcefb233406133224AE9b19444d836F6a33593F13

Oh no! @danitome24 linked to "#21 in his PR, which accidentally closed this PR when his personal page got merged. I just re-opened this one so we can get your personal page in, @guidoPeirano

Merged!


Added strip_headers conifguration option to remove SWIFT header data before parsing

some MT940 files come with additional header information. Currently parsing failes when these headers are present. This options tries to clean up the file and remove the headers before parsing as mostly this information is not needed.
By default this option is disabled and should only be enabled when these header files are present.
As a further improvement we should support parsing of the header data aswell.

related: #9

This would be a really useful feature for us! Any chance we can get this merged?

@hmac thanks for the bump.
@Uepsilon what do you think can we merge this? It is not changing the current behaviour and simply adds the option to strip any line that does NOT start with : at the beginning and the end of the file.
parsing those somehow would be nicer but in most cases those are not needed.

@bumi code looks fine to me. yet this feature is something i'd rather see in the code utilising our gem. this parser should not be responsible for finding what to parse but parse what is provided and throw an error if it's not parseable.

hmm... I see your point.
but I can see how it is useful... some banks have that header and in my code I just want to pass whatever the bank provides to the parser without any pre-parsing of the data.

It sure is useful. Go ahead, do it. Let's just be careful not to overload this gem with features not necessarily aligned with the core task

yep, I totally agree and I am not sure about this... so I hesitate and appreciate your opinion!
@hmac what do you think?

I think in the long run, it'd definitely be nicer if we properly parsed these headers. However in the absence of that, I'd rather that they get stripped out here, close to the rest of the parsing logic, than in surrounding downstream code. Catching cmxl errors and trying to work out if they're caused by the presence of swift headers or by an actual parsing issue doesn't sound like a very robust approach.
@Uepsilon I appreciate that you don't want to overload the gem - I think that's a really valid concern. Would you be happier if we instead attempted to parse these headers?

The swift headers have nothing to do with MT940. The data should always be included in the {4:...}-block. At best dumping the headers into this parser should produce a non-parsable error.
Since the primary usage of this gem is related to SWIFT, I could agree to adding the stripping of said headers. But at best the stripping would happen within a separate gem which parses the swift message and utilises this gem if it detects MT940 blocks in the SWIFT text block.

but for convenience sake i'd say merge it, since the change aren't really that big and it's fully downward-compatible and should not have side effects unless explicitly activated


DxList height property not working

I ran into an issue today where the height property on my DxList component was not working. The issue was occurring on Chrome v52.
This was happening because the DxList element needs to be display: block for the height property to work. However, when you create a non-standard HTML element tag (e.g. <dx-list></dx-list>), the browser was setting it's display property by default to inline. This was preventing the height styles from taking effect.
I was able to override this by manually setting the display: block style on the dx-list element. Another workaround would be to declare the component as such: <div dx-list></div> although this is not encourage per the style guide.

Maybe similar to #61 ?

Yes, you are right. This issue is a duplicate of #61


Indexes on language func does not work with aliased cols

discovered at https://github.com/src-d/empathy-sessions/issues/37#issuecomment-470041061
time srcd sql "SELECT file_path, language(file_path, blob_content)
FROM files
WHERE language(file_path, blob_content)='JSX';"
+------------------------------------+--------------------------------+
|             FILE PATH              |   LANGUAGE(FILES FILE PATH,    |
|                                    |      FILES BLOB CONTENT)       |
+------------------------------------+--------------------------------+
| src/js/components/posts.jsx        | JSX                            |
| src/js/components/repositories.jsx | JSX                            |
+------------------------------------+--------------------------------+
real	0m12.926s

Then I created an index, following your example to create an index on language expresion
$ time srcd sql "CREATE INDEX files_lang_idx ON files USING pilosa (language(file_path, blob_content));
+
+

real	0m0.236s

And queried again, and the time processing was reduded from ~15s to ~.3s what is nice.
But then I queried using an aliased column... and ~15s again.
$ time srcd sql "SELECT file_path, language(file_path, blob_content) as lang
FROM files
WHERE lang='JSX';"

...

real	0m12.147s

I think this is more of a bug than a feature request, WDYT @ajnavarro?


EvaluateFunctionOnNewDocumentAsync isn't working in firefox

When I try to execute a script for a new document via EvaluateFunctionOnNewDocumentAsync, nothing happens in Firefox, unlike Chromium browsers, everything works there. EvaluateFunctionAsync works in firefox for me, but i need to run scripts in each frame. That's why I even tried to subscribe to the FrameNavigated event, but it doesn't work in FireFox.
var options = new LaunchOptions()
{
    ExecutablePath = @"C:\Program Files\Mozilla Firefox\firefox.exe",
    Headless = false,
    IgnoreDefaultArgs = false,
    DefaultViewport = null,
    Browser = PuppeteerSharp.SupportedBrowser.Firefox,
};

IBrowser browser = await Puppeteer.LaunchAsync(options);

browser.TargetCreated += async (_, e1) =>
{
    try
    {
        if (e1.TargetInfo.Type == TargetType.Page)
        {
            IPage page = await e1.Target.PageAsync();

            if (page != null)
            {
                await page.EvaluateFunctionOnNewDocumentAsync("() => { alert(1); }");
            }
        }
    }
    catch (Exception ex) { }
};

await Task.Delay(20000000);

Hey @mortinlojen3030, unfortunately, Firefox doesn't support Page. EvaluateFunctionOnNewDocumentAsync :(

Hi @kblok, thanks for the answer. Can you give me any advice on how to do this in firefox?

@mortinlojen3030 On thing you would do is listen to the FrameNavigated event, and inject the code there. It's not the perfect solution but I think it's a decent workaround.

@kblok maybe FrameNavigated is not supported either? Because this code works for Chromium but not for Firefox
var options = new LaunchOptions()
{
    ExecutablePath = @"C:\Program Files\Mozilla Firefox\firefox.exe",
    Headless = false,
    IgnoreDefaultArgs = false,
    DefaultViewport = null,
    Browser = PuppeteerSharp.SupportedBrowser.Firefox,
};

IBrowser browser = await Puppeteer.LaunchAsync(options);

browser.TargetCreated += async (_, e1) =>
{
    try
    {
        if (e1.TargetInfo.Type == TargetType.Page)
        {
            IPage page = await e1.Target.PageAsync();

            if (page != null)
            {
                 page.FrameNavigated += async (sender, e2) =>
                 {
                     try
                     {
                         Console.WriteLine(e2.Frame.Url);
                     }
                     catch (Exception) { }
                 };
            }
        }
    }
    catch (Exception ex) { }
};

await Task.Delay(20000000);


Feature Request: Download to sub folders

I don't know if this is an option or not already but i would like to have different shows download into sub folders with the shows title.
Example:
anidl.exe --service "funi" -s 1174282 -e "all" --nosubs
anidl.exe --service "funi" -s 119587 -e "all" --nosubs
1174282 would download to ./videos/Yashahime: Princess Half-Demon/
119587 would download to ./videos/Yu Yu Hakusho/
Instead of all episodes of both shows downloading to ./videos/
Thank You in advance whether this is possible or not.
I appreciate all the work everyone has put into this program

nvm, i read the cli functions a little closer and figured it out

For anyone who's searching for this feature: Look at --fileName. By adding a path separator (/ or \\) you can create subfolders


Next.js 13.2 Upgrade

Upgrades playground and next-template to Next 13.2

[x] Migrate to Metadata API
[x] Enable Typescript plugin
[x] Remove display: swap as it is now built in

Note
Upgrading www currently blocked by https://github.com/contentlayerdev/contentlayer/issues/386

Build Stats: next-template
Before
Route (pages)                              Size     First Load JS
┌ ○ /                                      34.6 kB         113 kB
├   /_app                                  0 B            78.2 kB
└ ○ /404                                   181 B          78.4 kB
+ First Load JS shared by all              85.5 kB
  ├ chunks/framework-2647c7e378e02044.js   45.2 kB
  ├ chunks/main-9fee79d2c98001b5.js        26.8 kB
  ├ chunks/pages/_app-a38f8853e697b35d.js  5.13 kB
  ├ chunks/webpack-880e48e2fc817058.js     1 kB
  └ css/41aa8a2b2b181921.css               7.29 kB

After
Route (pages)                              Size     First Load JS
┌ ○ /                                      34.6 kB         113 kB
├   /_app                                  0 B            78.3 kB
└ ○ /404                                   182 B          78.5 kB
+ First Load JS shared by all              85.6 kB
  ├ chunks/framework-2647c7e378e02044.js   45.2 kB
  ├ chunks/main-1cd0f54cc68f94aa.js        27 kB
  ├ chunks/pages/_app-68b552c48a55f428.js  5.13 kB
  ├ chunks/webpack-880e48e2fc817058.js     1 kB
  └ css/a04992481059eb80.css               7.3 kB

Build Stats: playground
Before
Route (app)                                Size     First Load JS
┌ ○ /                                      0 B                0 B
├ ○ /login                                 0 B                0 B
└ ○ /signup                                0 B                0 B
+ First Load JS shared by all              82.8 kB
  ├ chunks/837-6030326ca5f785ef.js         80.4 kB
  ├ chunks/main-app-b990bd463c1682a5.js    217 B
  └ chunks/webpack-967f29203e361fcc.js     2.16 kB

Route (pages)                              Size     First Load JS
─ ○ /404                                   178 B          81.3 kB
+ First Load JS shared by all              81.1 kB
  ├ chunks/main-829f724b2c2d74e7.js        78.8 kB
  ├ chunks/pages/_app-ee185f83cd769c40.js  192 B
  └ chunks/webpack-967f29203e361fcc.js     2.16 kB

After
Route (app)                                Size     First Load JS
┌ ○ /                                      0 B                0 B
├ ○ /login                                 0 B                0 B
└ ○ /signup                                0 B                0 B
+ First Load JS shared by all              75.8 kB
  ├ chunks/757-9c2a460bb02e0f4f.js         65.5 kB
  ├ chunks/901-21bd003a0bcd078c.js         7.93 kB
  ├ chunks/main-app-07558ef4ed89c5b4.js    204 B
  └ chunks/webpack-6a948f17753cea2e.js     2.16 kB

Route (pages)                              Size     First Load JS
─ ○ /404                                   179 B          90.9 kB
+ First Load JS shared by all              90.7 kB
  ├ chunks/main-32a87a4adb794685.js        88.4 kB
  ├ chunks/pages/_app-5c5d79c30c1fd3df.js  192 B
  └ chunks/webpack-6a948f17753cea2e.js     2.16 kB

Woah! This is a big effort. Thank you.
Let me know when ready I'll review.

@shadcn ready for review

Closed by #180
Thanks @shadcn for all your work!


Bootstrap Menu hiding behind ActiveX object

Hi,
When I click on Menu item, it opens up, but hides behind ActiveX Object.
Please help.
Thanks,
Shakti

If you found soulation give me


More context in IApiResponseMetadataProvider or extension points to DefaultApiDescriptionProvider

At the moment the DefaultApiDescriptionProvider is able to auto-generate an ApiResponseType having a 200 status code whose type is the runtime return type (see here), but this kind of functionality cannot be attained by the developer unless a specific ProducesResponseTypeAttribute is used on every action, passing the defined return type explicitly.
It would be nice if such runtime return type (or a more informative context) could be somehow accessed while providing the response type metadata, so that it would be possible to declare 'global' filters.
An example could better explain the purpose: let's say my Api will always return 400 and 500 providing an Error result, and 200 with the return type defined on the action unless a more specific 2xx is already specified for the action. I would like to avoid to decorate every action/controller with such information and would prefer to register filters to define this default behavior globally:
services.AddMvc(o =>
                {
                    o.Filters.Add(new ProducesResponseTypeAttribute(typeof(Error), StatusCodes.Status400BadRequest)); // Error during model validation
                    o.Filters.Add(new ProducesResponseTypeAttribute(typeof(Error), StatusCodes.Status500InternalServerError)); // Error during execution (exception)
                    o.Filters.Add(new ProducesSuccessResponseTypeAttribute(StatusCodes.Status200OK)); // Default status code associated to the actual runtime return type of the action
                })

The ProducesSuccessResponseTypeAttribute could implement a more informative interface to determine if the action already has a specific success response type defined and append 200 if not.
The current return type metadata resolution strategy would play nicely with this approach, since filters declared on leaves will override the default behavior.
Another possible approach would be to have a new extension point that allows the developer to resolve/manipulate the api response types programmatically, something like
public interface IApiResponseTypesMetadataProvider
{
     IReadOnlyList<ApiResponseType> GetApiResponseTypes(ActionDescription description, IEnumerable<IApiResponseMetadataProvider> providers);
}

Ultimately, this behavior could be achieved replacing the DefaultApiDescriptionProvider, but since it lacks virtual methods or other extension points, we need to re-implement it copying and pasting the existing code...

Thanks for contacting us, @BladeWise.
@rynowak, @pranavkm any thoughts?

Hi @BladeWise - sorry for the delay, it just dropped off my radar.
We intended for the providers to be composable, but I think we got some things wrong by not separating our computation into phases. You could probably simplify that code a great deal by just hardcoding content types if you don't actually do content negotiation.

I still think it could be worth to have a better extension point to plug-in a bit of logic used to determine the actual result types of an action.

This kind of request is something we've tracking for a while now. https://github.com/aspnet/Mvc/pull/6936
Currently "attribute soup" is only want to configure this in MVC. You might have a better experience trying to use Swashbuckle or NSwag's extensibility directly.

Thanks @rynowak, I suppose you are right, but I preferred to try playing nicely with ApiExplorer, instead of brute-forcing the swagger code generation.
In the end I could achieve what I needed and was not a painful expreience, so even provider composition is not so bad.
Unfortunately, a well described API does not play nicely with client auto-generation in this case, at least with AutoREST, since you lose strong-typed clients by declaring different response types for each status code... but that's another story... :(

Thanks for your feedback, @BladeWise.
I'm closing this issue as we already track the main concerns raised here in different issues. Hopefully we'll be able to address those quite soon.


Display full contract address in cast run (with -v flag)

Component
Cast
Describe the feature you would like
I like that cast makes the output so pretty, but sometimes it's easier to understand what's going on with the full address on-hand.
I propose adding a -v or --verbose option to cast run to have cast spit the full address.
Additional context
No response

I think we should add this :
    #[clap(long, short = 'v', help = "Prints full address")]     verbose: bool,
at the end of in this struct :
https://github.com/foundry-rs/foundry/blob/8b33ded5a6193c4cba76beb1729477f0395b185d/cli/src/cmd/cast/run.rs#L28-L46
and then check for the bool in run_tx(self) but don't get how the tracing system works, if someone could explain it that would be cool.

You guys rock!


auto.fish changes to system ruby when no .ruby-version is present

Whether or not one has a ~/.ruby-version to defined with a default, when I have the following in my ~/.config/fish/config.fish:
source /usr/local/share/chruby/chruby.fish
source /usr/local/share/chruby/auto.fish
chruby 3.0.2

then I correctly have 3.0.2 in my home directory, and get whatever version is specified in a project directory with a .ruby-version. However, if I change to a directory without a .ruby-version chruby_auto just sets me back to the system ruby. For example:
# new shell; expected behavior
~> chruby
   jruby-<IP_ADDRESS>
   ruby-2.7.2
   ruby-3.0.0
   ruby-3.0.1
 * ruby-3.0.2

~> printenv | egrep '(CH)?RUBY_'
<EMAIL_ADDRESS>CHRUBY_VERSION=0.3.9
CHRUBY_FISH_VERSION=0.8.2
RUBY_VERSION=3.0.2
RUBY_ROOT=/Users/tjacobs/.rubies/ruby-3.0.2
RUBY_AUTO_VERSION=3.0.2
RUBY_ENGINE=ruby

# directory without .ruby-version; unexpected behavior
~> cd /tmp

~> printenv | egrep '(CH)?RUBY_'
<EMAIL_ADDRESS>CHRUBY_FISH_VERSION=0.8.2
CHRUBY_VERSION=0.3.9
RUBY_AUTO_VERSION=

~> chruby
   jruby-<IP_ADDRESS>
   ruby-2.7.2
   ruby-3.0.0
   ruby-3.0.1
   ruby-3.0.2

If you try cd /tmp; and printenv | egrep '(CH)?RUBY_' it looks like it works, but it's transient success because fish appears to be reporting the environment variables before the Ruby change is completed. If you cd and then check, the Ruby has definitely been reset to the system Ruby.
From a user point of view, it looks like when auto.fish unsets RUBY_AUTO_VERSION, it loses track of whatever the default was supposed to be. When I set a default using chruby or a .ruby-version in my home directory, my expectation is that Ruby will be my default unless overridden by a project .ruby-version.
Looking at the source, auto.fish and chruby.fish use set -gx rather than set -lx for a lot of things, which may be part of the problem since -g affects all shells rather than just the current one. That aside, though, it seems that there's nothing that resets chruby to the initial value of chruby use or checks the ~/.ruby-version when leaving a project directory. This may be by design, but it feels like a bug.
A potential solution might be to have a set -Ux RUBY_AUTO_VERSION_DEFAULT (or maybe just a CHRUBY_DEFAULT_RUBY) set by the first use of chruby use or an encounter with ~/.ruby-version, and then fall back to that when needed. Alternatively, if the user has a .ruby-version in the home directory, then the following makes more sense to me (and is probably less complicated). For example:
set -q RUBY_AUTO_VERSION; or set -lx RUBY_AUTO_VERSION=(cat ~/.ruby-version)

There may be problems with these particular approaches that I haven't thought of; I'm simply offering them as possible solutions if there isn't a better one. The issue may not even be fish-specific (it seems to exhibit the same behavior with Bash on my system, too), but I still find the behavior surprising.

Yeah I should probably introduce another variable for the "default ruby" (defaults to system) and have chruby_auto reset back to the default ruby as opposed to system ruby.

I most definitely prefer the first option. If you're open to the idea, I would be willing to take a stab at a PR for the feature if you don't get to it first. I'm unfamiliar with the code base, though, and would like to know how to ensure I don't introduce any regressions.

Before we brainstorm how this feature should work, I'm curious what's wrong with just installing the desired default ruby version into /usr/local as the new system ruby? Installing gems might be a problem as the default gem home is /usr/local/share/gems/... which requires sudo access. What if chruby could use system ruby, but also set GEM_HOME so that gem install wouldn't require sudo access to write into /usr/local/share/gems/... and instead install into ~/.gem/? See issue #421 where I brainstormed mixing system ruby but with a default GEM_HOME for non-root users.
If we do go the default ruby route, i'd imagine setting the default ruby would be done in the chruby.sh config via a chruby --default <ruby> command. This would set an internal variable DEFAULT_RUBY. chruby_auto would then use DEFAULT_RUBY when resetting the ruby version (would fallback to system if not set, or maybe just call chruby_reset directly).

Before we brainstorm how this feature should work, I'm curious what's wrong with just installing the desired default ruby version into /usr/local as the new system ruby?

The use case here is that I work on a lot of projects with varying Ruby versions set via .ruby-version. The problem I'm experiencing is the surprise of not having my default Ruby when I cd to /tmp or some other system directory, and the cognitive load of having to remember that I need to manually chruby "$some_non_system_ruby" whenever I move to a non-project directory.
I'm not looking to change the system Ruby, because that sometimes breaks things. I'm just experiencing a constant stream of "Oh, right; I need to chruby again!" when I switch to /tmp or ~/bin or whatever from a project directory to test something or run a one-liner. In Bash (I'm not sure about Fish) I could certainly leverage PROMPT_COMMAND or similar to roll my own, but it seemed like something that was bound to surprise other people too, whether or not they take the trouble to report it. Users often don't, in my personal experience, unless it's a show-stopper for them.
So, for me it's less about GEM_HOME than it is about resetting the current Ruby version in a way that is unexpected when I'm hopping around the filesystem. Does that add some useful context?

I'm not looking to change the system Ruby, because that sometimes breaks things.

That is a valid concern. Any script or package that uses #!/usr/bin/env ruby could potentially break if you installed ruby 3.x into /usr/local and the scripts/packages expected ruby 2.x. I do know that Debian and RedHat based Linux distros are very careful about their packages relying on an explicit ruby via #!/usr/bin/ruby to prevent this from happening.

I do know that Debian and RedHat based Linux distros are very careful about their packages relying on an explicit ruby via #!/usr/bin/ruby to prevent this from happening.

This is yet another reason to never set GEM_HOME btw. Otherwise such scripts would be broken if they use any gem.

I forgot that there is already a branch where I experimented with adding chruby --default ... and chruby default. Checkout 9682bfaf72b79bf434fb36b7d84443b4b8f087ee. Still needs some tests, but it seems to satisfy the requirements. Will probably end up merging it into the 0.4.0 branch.

Added some tests, but ran into an interesting edge-case. @todd-a-jacobs what do you think chruby --default with no argument should do? Error? Print the current default ruby? Unset the default ruby?

@postmodern said:

Added some tests, but ran into an interesting edge-case. @todd-a-jacobs what do you think chruby --default with no argument should do? Print an error? Print the current default ruby? Unset the default ruby?

That really is an interesting edge case. My initial thought is that a flag with no argument should probably be a request for information, e.g. almost the same as calling chruby with no arguments, except perhaps with a different sigil to mark the current and  default rubies. While it's got its own issues, rvm does something similar by using:
# => - current
# =* - current && default
#  * - default

While I think the chruby approach is generally superior, and should keep * to mark the current Ruby, the reason I think we might want to differentiate here rather than taking an action or treating it as an error. What we're really asking when we discuss an argument-less --default flag is the following pair of questions:

What's the user's likely intent?
What is least likely to create unexpected or surprising behavior for the user?

Keeping the principle of least surprise in mind, here are my thoughts:

If we treat --default with no argument as a duplicate of -h, it doesn't really add anything to the user's knowledge of chruby state. It just makes them re-run the command, and possibly other commands beforehand to see what the current and default rubies are.
If we treat it as a request to set the current Ruby as the default Ruby, that could lead to unexpected surprises if the user has lost track of where they are, or what the current Ruby is (esp. if it's been unintentionally unset or auto-set to the system Ruby).
Treating it as a request to switch from the current Ruby to the default Ruby is definitely a legitimate choice, but I think it could lead to the same set of surprises as #1 and #2.

In summary, I think treating it as a call to chruby that lists the current and default rubies (assuming chruby itself doesn't yet make that distinction when listing rubies) is sane, safe, and relatively unsurprising. If you think it useful to append the usage instructions for the flag as well then that might add informational value, but I think the central notion of making the flag informational if not passed an argument is probably the best overall solution.
Thoughts?

I've decided that chruby --default "" should probably print an error, otherwise if someone put chruby --default $var in their ~/.bashrc and var is not set, that would be confusing and should be caught.
As for printing the rubies, the default ruby could be indicated by simply appending  (default) after the ruby name.


README: Avoid macOS crash in suggested ipykernel inline backend config snippet

What error do you otherwise get?

I'm getting random segmentation faults, somewhere in the compiled code. (Apologies for the lack of details, but this seems like the macOS issue already pointed out in the readme.)

Sounds fair.


Bootstrap and wake nodes in a single script tag

Even better would be a single LAB script.
This is ugly, and inefficient:

This was closed by #288.


【feat】Support dependency coverage stats collection

in some cases, our business logic would write in our custom lib

source load path /home/build/elixir/lib/logger need to can be specific.


Use GTK on window

In theory this would be as simple as:

Link GTK on windows (Somehow, ideally add the source in /extern/ and link it with cmake, probably add a .cmake file in /extern/ for it and add it to the main cmake extern file, then maybe add some things in /src/CMakeLists.txt)
Include the file in arch_default.h for windows
Make LoadingWindowGTK.h try GTK for windows

Then, practically, this might require:

Make the loading window use the new layout (full-window image)
There might be non cross-platform code in the stepmania gtk window code. Make it portable.

This would allow us to nuke the windows loading window and the thing itself would probably be faster/ more efficient than our raw implementation.

Superseded by https://github.com/etternagame/etterna/pull/1073


lineapy python extension is not loaded in VSC notebooks

Open any test notebook in VSC (i.e. https://github.com/LineaLabs/lineapy/blob/03cf685383ad55b22594684a6fce743d1f84a1ce/tests/notebook/test_is_executing.ipynb)
Run with the default kernel

Expected:
VSC uses IPYTHONDIR=$PWD/.ipython to load the extension

using %load_ext lineapy should work in a runtime that has lineapy installed. closing until a compelling use case is encountered.


Fix for e2e setup

Did you see the same thing?

Yeah, same issue from my side. Still investigating and guess something related to the fast slot hack?


[msal-core] Fix ID Token in browser history bug

This PR fixes a bug in msal v1 where the ID Token portion of the hash was being left in the browser history entry after authentication (for both reidrect and popup). Fixes #3367 .

Coverage increased (+0.007%) to 83.813% when pulling 13a4706a93d6cd98a9eb5eb2ea09ed1780f27e60 on fix-idtoken-in-history into b4cda68b9c2708976e2b794c71344a8b9dfdd627 on dev.


Support serde w/o std and update base64 dependency

By using base64’s encode_slice and decode_slice it’s possible to
implement serde serialisation without std or alloc.  Take advantage of
that and allow enabling serde support separate from std.  This is
gated by a new serde feature which.
To maintain backwards-compatibility make std feature enables serde
feature.  Ideally, it should be possible to enable std without
bringing in serde support.  We're still in 0.x releases so there’s
technically no semver issue in breaking builds, but for now it’s
probably nicer to keep std enabling serde support.  It probably
makes sense to remove that in 0.8.
With all that, make serde and base64 dependencies optional.
Previously, they were always included even though they were only used
if std feature was enabled.  Now, they are enabled only if
explicitly requested.
While at it, update base64 dependency to the newest 0.21.2 release.

@sorpaas, @alvicsam, friendly ping


Validation

Should verify specimen type values with accepted codelist values.
Should verify that submitter specimen id and specimen sample id values are all distinct (never the same value in both columns).
Should warn if required jars not found

Is there a specification somewhere of the accepted format of the metadata.tsv file / accepted codelist values? (beyond the implicit specification of "what the spinnaker client has been implemented to accept")?

This issue was intended for the dcc-spinnaker-client repo, but much of the validation mentioned could be implemented serverside too. For more detailed discussion, see dcc-spinnaker-client/issues/5

This issue was intended for the dcc-spinnaker-client repo

Ah, okay.
The server will absolutely doing validation of some sort; it's an open question from my perspective which validations should be server-side? client-side? both?

For user convenience, the client should do as much validation as possible; uploads shouldn't proceed if an invalid metadata.json was produced by spinnaker-client because that would waste a lot of time.
We trust users enough to give them an access token, so we probably don't need to worry about users hacking around the client to send malicious data to redwood/spinnaker. Some validation that files were transferred correctly is one thing that could go server-side. Not sure about others.

Another consideration: data-processing-heavy validation (eg, doing QC on the data files) should be done server-side to ease burden on user hardware requirements & upload time.


support @rendition

We need to support @rendition out of the box.

[x] support @rendition in main text
[x] support @rendition in apparatus
[x] template to generate CSS styles from <tagsDecl>
[x] regression tests

mentioned in commit 13d2fcba50c9b210d5471009e777afc14ff151ef

marked the checklist item template to generate CSS styles from <tagsDecl> as completed

mentioned in commit 1c2dd57fcf5062dd695918b0cc6c77cf4083571d

marked the checklist item support @rendition in apparatus as completed

added 4h of time spent

marked the checklist item support @rendition in main text as completed

mentioned in commit a6fbb0322e1b1438f3189ad722612534e87a2186

mentioned in commit 584e09a4c3d7c57d161cbb743c6f1bf93fbb7516

added 2h 30m of time spent

marked the checklist item regression tests as completed


feat!: ErrorType as enum, add ErrorMessage string

Codecov Report

Merging #72 (7a64766) into main (1f7e4cb) will decrease coverage by 0.31%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #72      +/-   ##
==========================================
- Coverage   94.44%   94.13%   -0.32%
==========================================
  Files          18       18
  Lines         432      426       -6
  Branches       36       36
==========================================
- Hits          408      401       -7
  Misses         13       13
- Partials       11       12       +1

Impacted Files
Coverage Δ

...c/OpenFeatureSDK/Error/FeatureProviderException.cs
100.00% <100.00%> (ø)

...eatureSDK/Extension/ResolutionDetailsExtensions.cs
100.00% <100.00%> (ø)

src/OpenFeatureSDK/Model/FlagEvaluationDetails.cs
100.00% <100.00%> (ø)

src/OpenFeatureSDK/Model/ResolutionDetails.cs
100.00% <100.00%> (ø)

src/OpenFeatureSDK/OpenFeatureClient.cs
99.21% <100.00%> (ø)

src/OpenFeatureSDK/Extension/EnumExtensions.cs
80.00% <0.00%> (-20.00%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


NPE in GoogleAuthenticatorAuthenticationHandler

CAS Version: 5.1.0-RC2-SNAPSHOT
CAS Commit Id: ed48739a3a97d4ceaeabef13fb14355a3ddeacf3
CAS Build Date/Time: 2017-01-18T07:44:14.101Z
Spring Boot Version: 1.5.0.RC1
Apache Tomcat Version: Apache Tomcat/8.5.5
After providing either a valid or an invalid GAuth token I get an NPE in GoogleAuthenticatorAuthenticationHandler.
Log file
Nb. I get the NPE error as a dialog error instead of as an error page (probably because of #2304)

Give it another shot please. I should have fixed this. Ran through the set up a few times and I believe it should be gone now.


Accept a custom base uri for the go binaries

In my experience, many organisations have restrictions on downloading binaries from the internet, particularly from build servers.  Instead, they often require binaries to be downloaded from an internal repository.
This PR adds a property to the plugin that allows you to specify where you'd like the go binaries downloaded from.
Note, I was unable to get all the tests to run - gradlew check produces a lot of failures like the below when I run it (I assume I've missed something):
org.mockito.exceptions.base.MockitoException:
Mockito cannot mock this class: class com.github.blindpirate.gogradle.GolangPluginSetting.

Mockito can only mock non-private & non-final classes.
If you're not sure why you're getting this error, please report to the mailing list.

Java               : 1.8
JVM vendor name    : Oracle Corporation
JVM vendor version : 25.11-b03
JVM name           : Java HotSpot(TM) 64-Bit Server VM
JVM version        : 1.8.0_11-b12
JVM info           : mixed mode
OS name            : Linux
OS version         : 3.19.0-32-generic

Underlying exception : java.lang.IllegalArgumentException: java.lang.ClassCastException@210ea9c6
	at com.github.blindpirate.gogradle.GogradleRunner.createTest(GogradleRunner.groovy:63)
...

Thanks for your PR. Your advice is valuable.
It seems that the Mockito issues you encountered are due to some bugs in early JDK8, according to this and this.
However, there're at least a typo and a checkstyle violation in the PR, please see my comments in your commits.
Please let me know if there're any other questions.

Sorry for the slightly half-baked initial PR.  You were right on the money regarding my version of the JDK.
I've run the tests and fixed up all the issues that came out, including those you mentioned.

PR merged, thanks!


feat: Allow getting the size of a source

Hi,
First of all, I want to thank you for making such a wonderful library! This is exactly what I've been waiting for, and it's making multiplatform games much easier to write.
Onto the issue: I don't know how easy this is, but it would be very nice to see how much memory was being taken up by a given AudioSource. If I could see how much memory was being used, I could more easily cache sources, and dispose of them when the size of the cache exceded a given limit.
Is this possible?
Thanks again.

Hi @chrisnorman7,
I don't see an easy way to do this at this moment. But you can try to use something like system_info2  package to get the physical memory before and after loading a sound.
FYI when loading a sound file, methods like SoLoud.loadAsset have the mode parameter. When using the default value LoadMode.memory the sound is decompressed and stored in memory. But if you don't need to use the seek functionality as you could do with a slider, you can use LoadMode.disk which reads the audio while playing it, doing so not much memory is needed.

Hi,
Thank you for your response. That's great info, thank you.


oci: Support containers with identical ID prefixes

Starting 2 containers with the same ID prefixes is a valid use case.
Docker CLI supports shortened container IDs but always call the runtime
with the full and complete ID.
Fixes #699
Signed-off-by: Samuel Ortiz<EMAIL_ADDRESS>

LGTM

lgtm


Scheduler algorithm rename breaks backwards compatibility

1.0.0 shipped with ServiceSpreadingPriority (https://github.com/GoogleCloudPlatform/kubernetes/blob/release-1.0/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go#L70). The rename at https://github.com/GoogleCloudPlatform/kubernetes/pull/10667/files#r36776577 breaks backwards compatibility with serialized scheduler config files.
We should:

Add a test for backwards compatibility with the serialized version of the priorities/algorithms
Alias or revert the rename to that priority algorithm

Looks like it was more than just a rename, but a change in function as well...

cc @abhgupta

Pasting my comment from https://github.com/openshift/origin/issues/4112#issuecomment-129996433
The previous priority function (ServiceSpreadingPriority) ONLY considered services and the new priority function (SelectorSpreadPriority) considers both services and replication controllers for spreading.
Do we need to ensure backward compatibility in functionality as well? As in, do we create a ServiceSpreadingPriority that uses the new priority function but ignores the replication controllers (perhaps by passing an empty lister for RCs)?

cc @davidopp

Opened #12544 with deserialize test and empty ControllerLister implementation, per @abhgupta's suggestion

Sorry for the trouble.
Yeah, the reason we changed the name was because we changed the behavior.
My proposal wold be that we take what we have now and add back ServiceSpreadingPriority with the same behavior as the old ServiceSpreadingPriority. (That is, SelectorSpreadPriority would be strictly an addition.)
WDYT?

works for me. I think that's what my PR does, eyes welcome


Add giganto migration option

Add -m options to send giganto raw event from giganto export file.

Codecov Report
Base: 19.37% // Head: 15.38% // Decreases project coverage by -3.99% :warning:

Coverage data is based on head (5b24c21) compared to base (452ec52).
Patch coverage: 0.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #232      +/-   ##
==========================================
- Coverage   19.37%   15.38%   -3.99%
==========================================
  Files          10       11       +1
  Lines        2952     3717     +765
==========================================
  Hits          572      572
- Misses       2380     3145     +765

Impacted Files
Coverage Δ

src/config.rs
0.00% <0.00%> (ø)

src/controller.rs
0.00% <0.00%> (ø)

src/lib.rs
5.97% <ø> (+<0.01%)
:arrow_up:

src/main.rs
0.00% <0.00%> (ø)

src/migration.rs
0.00% <0.00%> (ø)

src/producer.rs
2.30% <0.00%> (-0.64%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Input message typo

In line 29, "Enter choice(1/2/3): " -> "Enter choice(1/2/3/4): "

Thank you for your Issue.
I edited it.


fix: align session error message with core terminology as "session_missing"

Task linked: CU-86975vemc Poor grammar in logs of the phone app


center align items on vertical axis

Description
Align text and arrow-down icon at the center of the vertical axis.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)

Well done @kofiarkoh!


Heuristic Evaluation of APINF Dashboard

Link for Heuristic Evaluation Report
https://github.com/apinf/docs/blob/master/docs/research/DashboardHeuristicsEvaluation.md


Split IsortItem into Item and File implementations

This fixes support for pytest 7.0 and is the recommended approach to implement collectors and items.
Close https://github.com/pytest-dev/pytest/issues/9487

Note: we can simplify the code a bit if you are willing to drop support for pytest 4.

Some tests failed due to missing "isort" and in support for pytest 4.
(I unfortunately can't tox locally because the tox configuration is no Windows friendly, that's why I missed that case).

Note: we can simplify the code a bit if you are willing to drop support for pytest 4.

Yes that's fine. I'll to a major release then.

Yes that's fine. I'll to a major release then.

That's good, but better do that in a follow up.


Gifs being destroyed when resized

Hi,
Firstly thanks for the great work – I've used it for a few projects now and it's always worked really well. The problem I've got this time round is that the client wants to use GIFs, at the moment when the GIF is resized the animation is destroyed and only the first frame is shown.
Any help you could give would be greatly appreciated!

Great, I'll see what I can do over the weekend!


Next

Hello @foreign-sub! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file custom_components/hacs/__init__.py:

Line 85:80: E501 line too long (90 > 79 characters)

In the file custom_components/hacs/aiogithub.py:

Line 2:80: E501 line too long (88 > 79 characters)
Line 42:80: E501 line too long (88 > 79 characters)
Line 57:80: E501 line too long (85 > 79 characters)
Line 69:80: E501 line too long (88 > 79 characters)
Line 85:80: E501 line too long (85 > 79 characters)
Line 104:80: E501 line too long (88 > 79 characters)
Line 118:80: E501 line too long (85 > 79 characters)
Line 178:80: E501 line too long (88 > 79 characters)
Line 193:80: E501 line too long (85 > 79 characters)
Line 217:80: E501 line too long (88 > 79 characters)
Line 230:80: E501 line too long (85 > 79 characters)
Line 251:80: E501 line too long (88 > 79 characters)
Line 262:80: E501 line too long (85 > 79 characters)

In the file custom_components/hacs/const.py:

Line 32:80: E501 line too long (224 > 79 characters)

In the file custom_components/hacs/frontend/views/api.py:

Line 80:9: E266 too many leading '#' for block comment
Line 87:80: E501 line too long (85 > 79 characters)
Line 90:9: E266 too many leading '#' for block comment
Line 97:80: E501 line too long (85 > 79 characters)
Line 166:80: E501 line too long (155 > 79 characters)
Line 171:80: E501 line too long (86 > 79 characters)
Line 177:80: E501 line too long (96 > 79 characters)
Line 181:80: E501 line too long (86 > 79 characters)

In the file custom_components/hacs/frontend/views/error.py:

Line 75:80: E501 line too long (125 > 79 characters)

In the file custom_components/hacs/frontend/views/overview.py:

Line 36:80: E501 line too long (105 > 79 characters)
Line 44:80: E501 line too long (102 > 79 characters)
Line 48:80: E501 line too long (109 > 79 characters)
Line 54:80: E501 line too long (84 > 79 characters)
Line 55:80: E501 line too long (84 > 79 characters)
Line 59:80: E501 line too long (80 > 79 characters)

In the file custom_components/hacs/frontend/views/repository.py:

Line 57:80: E501 line too long (92 > 79 characters)
Line 63:13: E303 too many blank lines (2)
Line 79:80: E501 line too long (91 > 79 characters)
Line 120:80: E501 line too long (96 > 79 characters)
Line 130:80: E501 line too long (93 > 79 characters)
Line 134:80: E501 line too long (90 > 79 characters)
Line 157:80: E501 line too long (130 > 79 characters)
Line 163:80: E501 line too long (126 > 79 characters)
Line 170:80: E501 line too long (133 > 79 characters)
Line 233:80: E501 line too long (99 > 79 characters)
Line 234:80: E501 line too long (175 > 79 characters)
Line 240:80: E501 line too long (80 > 79 characters)
Line 241:80: E501 line too long (196 > 79 characters)
Line 249:80: E501 line too long (81 > 79 characters)
Line 251:80: E501 line too long (88 > 79 characters)
Line 252:80: E501 line too long (96 > 79 characters)
Line 253:80: E501 line too long (88 > 79 characters)
Line 266:80: E501 line too long (92 > 79 characters)
Line 273:9: E115 expected an indented block (comment)
Line 273:9: E265 block comment should start with '# '

In the file custom_components/hacs/frontend/views/settings.py:

Line 32:80: E501 line too long (85 > 79 characters)
Line 39:80: E501 line too long (108 > 79 characters)
Line 77:80: E501 line too long (83 > 79 characters)
Line 78:80: E501 line too long (85 > 79 characters)
Line 81:80: E501 line too long (108 > 79 characters)
Line 81:109: W291 trailing whitespace
Line 98:80: E501 line too long (92 > 79 characters)
Line 98:93: W291 trailing whitespace
Line 108:80: E501 line too long (146 > 79 characters)
Line 114:80: E501 line too long (148 > 79 characters)
Line 115:80: E501 line too long (80 > 79 characters)
Line 147:80: E501 line too long (135 > 79 characters)
Line 148:80: E501 line too long (88 > 79 characters)
Line 149:80: E501 line too long (84 > 79 characters)
Line 179:80: E501 line too long (93 > 79 characters)
Line 180:80: E501 line too long (100 > 79 characters)
Line 184:80: E501 line too long (201 > 79 characters)
Line 199:80: E501 line too long (216 > 79 characters)
Line 208:80: E501 line too long (136 > 79 characters)
Line 215:80: E501 line too long (159 > 79 characters)
Line 235:80: E501 line too long (91 > 79 characters)
Line 253:80: E501 line too long (149 > 79 characters)

In the file custom_components/hacs/frontend/views/store.py:

Line 42:80: E501 line too long (105 > 79 characters)
Line 51:80: E501 line too long (102 > 79 characters)
Line 52:80: E501 line too long (119 > 79 characters)
Line 55:80: E501 line too long (123 > 79 characters)
Line 57:80: E501 line too long (109 > 79 characters)
Line 60:80: E501 line too long (122 > 79 characters)
Line 64:80: E501 line too long (84 > 79 characters)
Line 65:80: E501 line too long (84 > 79 characters)
Line 72:80: E501 line too long (88 > 79 characters)
Line 73:80: E501 line too long (80 > 79 characters)
Line 78:17: E303 too many blank lines (2)
Line 90:80: E501 line too long (93 > 79 characters)
Line 91:80: E501 line too long (93 > 79 characters)

In the file custom_components/hacs/hacsbase.py:

Line 71:80: E501 line too long (80 > 79 characters)
Line 102:80: E501 line too long (83 > 79 characters)
Line 129:80: E501 line too long (90 > 79 characters)
Line 146:80: E501 line too long (94 > 79 characters)
Line 166:80: E501 line too long (94 > 79 characters)
Line 196:80: E501 line too long (98 > 79 characters)
Line 225:80: E501 line too long (87 > 79 characters)
Line 229:80: E501 line too long (85 > 79 characters)
Line 265:80: E501 line too long (90 > 79 characters)

In the file custom_components/hacs/hacsdatastore.py:

Line 6:80: E501 line too long (147 > 79 characters)
Line 8:1: E302 expected 2 blank lines, found 1
Line 30:80: E501 line too long (92 > 79 characters)
Line 74:13: E303 too many blank lines (2)
Line 77:80: E501 line too long (92 > 79 characters)
Line 105:80: E501 line too long (102 > 79 characters)
Line 108:80: E501 line too long (104 > 79 characters)
Line 111:80: E501 line too long (99 > 79 characters)
Line 114:80: E501 line too long (106 > 79 characters)
Line 117:80: E501 line too long (99 > 79 characters)
Line 122:80: E501 line too long (89 > 79 characters)
Line 124:80: E501 line too long (89 > 79 characters)
Line 130:80: E501 line too long (97 > 79 characters)
Line 131:80: E501 line too long (95 > 79 characters)
Line 132:80: E501 line too long (95 > 79 characters)

In the file custom_components/hacs/hacslogger.py:

Line 3:1: E302 expected 2 blank lines, found 1

In the file custom_components/hacs/hacsrepositoryappdaemon.py:

Line 51:80: E501 line too long (88 > 79 characters)

In the file custom_components/hacs/hacsrepositorybase.py:

Line 83:80: E501 line too long (82 > 79 characters)
Line 160:80: E501 line too long (81 > 79 characters)
Line 166:80: E501 line too long (85 > 79 characters)
Line 229:80: E501 line too long (84 > 79 characters)
Line 235:80: E501 line too long (80 > 79 characters)
Line 255:80: E501 line too long (86 > 79 characters)
Line 295:80: E501 line too long (86 > 79 characters)
Line 355:80: E501 line too long (85 > 79 characters)
Line 448:1: W391 blank line at end of file

In the file custom_components/hacs/hacsrepositorypythonscript.py:

Line 48:80: E501 line too long (88 > 79 characters)

In the file custom_components/hacs/hacsrepositorytheme.py:

Line 48:80: E501 line too long (88 > 79 characters)

In the file custom_components/hacs/hacsviewbase.py:

Line 13:80: E501 line too long (105 > 79 characters)

In the file custom_components/hacs/repositoryinformation.py:

Line 4:1: E302 expected 2 blank lines, found 1
Line 13:80: E501 line too long (87 > 79 characters)

In the file custom_components/hacs/repositoryinformationview.py:

Line 5:1: E302 expected 2 blank lines, found 1
Line 24:5: E303 too many blank lines (2)
Line 32:80: E501 line too long (184 > 79 characters)

In the file tests/test_aiogithub.py:

Line 16:80: E501 line too long (83 > 79 characters)
Line 23:80: E501 line too long (83 > 79 characters)


Move period inside quotation marks in setting-repository-visibility#making-a-repository-public

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility#making-a-repository-public
This issue is intended for newcomers to the OS Docs repo! 💛
If you are veteran of the OS Docs repo and are looking for issues to work on, take a look at our help wanted section ✨
What part(s) of the article would you like to see updated?

For more information on how to remove workflow runs and artifacts see "Managing workflow runs and deployments" and "REST API endpoints for workflow runs".

Move period inside quotation marks to align with our style guide
Additional information
No response

@sumedhakoranga Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏


Grant the authority to manage to the "post" host

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

Describe the solution you'd like
*I use Google Translate because I can't understand English correctly
I'm sorry if the location of the discussion was wrong
Function request

To my post
I want you to add a posting option that gives the permissions that can be deleted by selecting the contents of "Reply", "Repost", "Like".
(If it is difficult to delete "repost", additional settings such as "repost" approval system and ban)

I want a function that allows you to delete followers individually

I want a function to display the number of views that only I can see

In relation to the above three
It is necessary to erase traces from "malicious users" and protect my "Bluesky"

Describe alternatives you've considered
About the reason
I use "Bluesky" and post it because I want to be involved with people with the same hobbies and emotions.
However, from the unrelated "malicious users", they receive "reply", "repost", "Like", "follow".
Therefore, it is possible to block "malicious users"
However, with the block alone, scars remain in the important "post" I posted.
Every time I see the traces, I recall the discomfort
If "1" is possible, you can self -defense by erasing those traces.
The same is true for "2"
Regarding "3", it will be an index to know if you are a "malicious user" target.
Of course, I don't want to show the number of browsing to other users.
As a problem of "1", I think that the host can operate the information and twist the impression.
Therefore, by clarifying whether it is a post with a authority as a posting option or a post that is not given.
I think people can judge
Also, I think that "malicious users" will spread by "reply", "repost", "like", "follow".
I feel that it is impossible to entrust all "malicious users" processing to "Bluesky management"
It is impossible to rely on a specific user by "Modelity List" and manage it.
Therefore, I thought it was best to provide additional means of self -defense.

Additional context
As a personal emotion
I don't know what the situation in the world,
At least as far as I can view, "post" is contaminated by "spam" and "publicity".
And it makes that person's heart very uncomfortable
As a result, the tools for enjoying have created the opposite effect.
And it leads to quitting the post itself or quitting the relationship with others.
With "X", these are very very overwhelmingly severe
It wasn't that bad at the time of "Twitter"
And some people who escaped from "X"
Even in "Bluesky", there are some "spam" and "publicity", which abandon their hope.
The malice brought by "X", which was operated for a long time
The above request is a function that I felt that it was necessary when I learned from there.
I hope my feelings will be conveyed.

I'd suggest splitting multiple feature requests as separate issues.