SPAM in the branches

Dearest.
We have noise in our repositories.

Hey @ajsb85
what are the names of the repositories?

Hi, @Realtin
I already deleted the branches.
https://github.com/flyve-mdm/glpi-plugin

Hi, @btry
Could you describe the behaviour?
Thanks

Hey @ajsb85
This happened because conventional-changelog-cli release multiple versions (all of them in your version range) in a short amount of time and at least one of that versions broke your ci build.
Then greenkeeper creates an issue informing you of this problem and created some branches in order to give you the option to pin this dependency to a version that does not break things anymore. A bit later conventional-changelog-cli released the version that fixed their faulty version and the ci build was passing again. but since the greenkeeper issue was still open greenkeeper will only delete these branches when the issue is closed. That is why you had quite a few branches for that dependency.
So it really is a feature and not a bug ;)

Hi @Realtin
I disagree : conventional-changelog-cli is used only when we create an archive of our project, and for now this is done only manually. the CI does not handles this yet.
If I read the log of a failed build, the failure is related to unit  tests for PHP only, and conventional-changelog-cli is not related to the failure.
For example, look this issue
https://github.com/flyve-mdm/glpi-plugin/issues/323
and the first job of the branch created by greenkeeper
https://travis-ci.org/flyve-mdm/glpi-plugin/jobs/340541346
The failure in this job is related to a fine tuning of a composer package for our unit tests. All jobs suffered the same issue for this build.
I think the context is the following :

we did domething which broke our unit tests
in the mean  time an update was  released for conventional-changelog-cli and detected by greenkeeper
greenkeeper tries to build the project with the updated package
the build still fails because we did not fixed our unit tests yet
greenkeeper sees the failure and reports that conventional-changelog-cli update breaks our project (but thisis false, because it was broken before this build)

True!  Greenkeeper just assumed it was conventional-changelog-clis fault!

Do you think you could enhance the analysis ability of greenkeeper to no longer be wrong with such scenario ?

Greenkeeper only reads the ci status on github so it only knows if it was a success or a failure and nothing more. For an enhanced analysis we would probably need access to CI logs which is out of scope for greenkeeper.

I understand that reading build logs would be complex to handle, and/or out of scope of the greenkeeper.
However, maybe the following could be in the scope of Greenkeeper :
If Greenkeeper creates a branch and a commit to try a newer version of a package, maybe it would be sufficient to read the build status of the parent commit. This way, the bot can detect that a failure on his build may not be related to an update of a package.
It might be even better to not try to build with updated packages if the base branch is already broken.


Contractor can request changes to the contract

Additional context
This is a sub-issue of the meta https://github.com/OpenTechFund/apply-app/issues/2
User story

As a contractor, I want to request changes to the contract provided to me, so that I can sign a contract that reflects the conditions agreed.

I'm picking up this issue 😄

I remember from some user testing re. e-signing that most applicants don't actually need changes at the contract signing point because of the amount of conversation and back and forth that happens pre-contract signing. Specifically from one user saying the 'concept note' and probably, the PAF.
This being said I think this issue is about taking those conversations that were previously had across channels (email etc.) and making sure they happen in hypha app and outside of an email 1-2-1 exchange with the PM of the project.
I do still think there will be users that want to request changes at this stage but. think that process (changes to the contract) and previous stages where there are changes to concept note and PAF happening need to be the same type of process e.g. comment boxes in hypha etc.

From OTF finance stand up on Feb 2nd:
The PAF (and back and forth between project lead/OTF staff and the applicant) solidifies the contract, any edits/changes a contractor might have beyond spelling errors, address corrections etc. post the PAF stage (e.g. in the contract phase) is difficult.
Designing for a simple changes user case is easy - comms between contractor and OTF staff re. address spelling etc. simple.
It was also discussed that if in the edge case that a contractor has big critical changes to the contract at the contract stage then the contract should not be edited but the cycle of PAF should bre revisited/restarted inorder for the PAF to generate the contract with the new edits.
@ei8fdb has some concerns if this matches what he understands from the finance direct POV. Me and Bernard will sync on this this week and attend the Thursday 3rd Feb stand up to clarify.

@Erioldoesdesign you asked all the right questions and recored our conversation perfectly. However, I have to defer to @ei8fdb because he:

conducted user research and discovery with each role within this process so he has a richer understanding of their responsibilities at each juncture. I can recall information that was convey during these meetings and has my own POV as a 'user/program manager,' but BT synthesized every piece of information into technical steps.

knows the full workflow or big picture of the entire process.

My responses are correct in isolation, but are inaccurate when we take into account 1 + 2

Designing for a simple changes user case is easy - comms between contractor and OTF staff re. address spelling etc. simple.

In the past, a spelling error or incorrect contract required OTF to cancel the contract and resend the vendor an amended contract.

It was also discussed that if in the edge case that a contractor has big critical changes to the contract at the contract stage then the contract should not be edited but the cycle of PAF should be revisited/restarted in order for the PAF to generate the contract with the new edits.

What happens during the PAF stage?

[ ] Prior to drafting the PAF, the Program Manager/Staff has negotiated terms and conditions of the deliverables during the application stage. This communication with the vendor/contractor takes place prior to drafting the PAF.
[ ] When drafting the PAF, many elements of the PAF like 'vendor name' will be automated to minimize human error.
[ ] PM submits PAF to Compliance
[ ] If the Associated General Counsel/Compliance or Finance has questions about the PAF, modifications need to take place on the PAF between the Program Manager/Staff and Compliance/Finance. Revisions on the PAF will impact pre-populated text on the contract and scope of work (SOW).
[ ] Associated General Counsel/Compliance drafts a contract and sends to the PM.

Design located here: https://miro.com/app/board/o9J_l6AaDhM=/?moveToWidget=3458764519190819004&cot=14
As screenshots from balsamiq which can be viewed in higher res here: https://balsamiq.cloud/so3r3ka/p9tuu7g/r5EA3
scroll on the left hand panel to the mockup that is labelled 'otf#33 info & links - Contractor can request changes to the contract

'

Assigning Bernard & Di for review first pass before showing devs and added 'question' label as a sort of 'needs design reviewed' label

Eriol to set up a quick 30 min catch up with @sks444 (and other dev's he may think are relevant) and run through designs for technical feasibility.
Sk - any time this week or early next week to chat? 😄

I've reviewed the designs. They're based on the manually signing route. (I'll change the title of this issue as that's not clear!)

For the "contractor has no amendments" route: you've replicated the current manual (download, read, sign, upload) workflow right? No problem there.

For the "contractor has 'simple' amendments" route: it relies on it being clear to the contractor they are required to communicate via the communications tab. As long as that happens (i.e. they communicate via the communications tab) that seems sensible to me.

@fourthletter: I know currently contractors request changes to contracts often happens via email/signal/etc, but what is the current advice/guidance for contractors to request changes?

@Erioldoesdesign the "corrections or amendments to your contract" text link - I think that's fine, but should it go inside the Actions to take border?

@Erioldoesdesign I didn't understand the non-trivial changes scenario where contractor. It looked the same as the simple changes scenario. Am I missing something?

@fourthletter over to you and the @OpenTechFund/devs.

@Erioldoesdesign thank you for this design + workflow!

The user research related to e-signing could help inform this issue #33

Open Questions (we may need further user research/discovery to answer these questions)

Notifications

[ ] Which activities or tasks should appear in the Activity Feed? Example: Staff sends email to Contractor, Contractor signs contract, etc.
[ ] How is Staff, Approver notify when a contract is ready for review or still waiting for signature via Hypha?
[ ] Are instructions regarding how Contractors could communicate with Staff a) implementable and b) align with operational needs? The design shows a pop-up box and a red bar on top of the page. These are prompts we haven't traditionally used in Hypha to guide applicants/external users because we've mostly relied on external communication.

Contract Changes

[ ] When a Contractor submits a change directly on the contract a) copy & paste, b) highlighting -- will they also need to write a comment to explain this request for change?
[ ] What is the best approach for the Contractor to communicate with Staff regarding a change request or edit?
[ ] Is it necessary for multiple contracts appear on the UI?

General

[ ] What triggers the email to the Contractor?
[ ] 'amendments' is a term of art that only applies to certain scenarios, not every change request.
[ ] In regards to pop-up box with instructions on types of change, i.e., spelling error, update address, and other types of change, etc. Could we simplify instructions to "Please contact your Project Lead if you have inquiries related to your contract. We will respond to your inquiry as quickly as possible."

BT: I didn't understand the non-trivial changes scenario where contractor. It looked the same as the simple changes scenario. Am I missing something?

[ ] It looks to me as if the first workflow is for no change and the second workflow is for a change request. Is this accurate?

Gonna take a look at this again this week :)

https://helpx.adobe.com/content/dam/help/en/document-cloud/Adobe_DC_eSign_Best_Practices_Digital_Signatures.PDF
Some Adobe esign docs

Updated designs here: https://miro.com/app/board/o9J_l6AaDhM=/?moveToWidget=3458764519190819004&cot=14

This issue is no longer needed right now because the contract will not be signed in Hypha. The contractor will sign the contract outside of Hypha.


[Feature-16300][registry] Added Consul-based Register implementation

Purpose of the pull request
Implemented Register based on Consul.
Brief change log

Added a new module: /dolphinscheduler-registry/dolphinscheduler-plugins/dolphinscheduler-registry-consul/
Added com.orbitz.consul.consul-client dependency in dolphinscheduler-bom/pom.xml
Added dolphinscheduler-registry-consul dependency in dolphinscheduler-registry/dolphinscheduler-registry-all/pom.xml

Verify this pull request
Inherited RegistryTestCase in /dolphinscheduler-registry/dolphinscheduler-plugins/dolphinscheduler-registry-consul/src/test/java, which can be directly run for verification.

You need to create a DSIP firstly.


allow / in apiDocsPath

Sometimes I like to have a slash in my api docs path. Currently something like override val apiDocsPath = "v1/api-docs" gets converted to v1%252Fapi-docs, which is nasty

Current coverage is 94.91% (diff: 100%)

Merging #5 into master will increase coverage by 0.08%

@@             master         #5   diff @@
==========================================
  Files             2          2
  Lines            58         59     +1
  Methods          52         49     -3
  Messages          0          0
  Branches          6         10     +4
==========================================
+ Hits             55         56     +1
  Misses            3          3
  Partials          0          0

Powered by Codecov. Last update d9e8c12...d7df021

Published an 0.7.4 release for Scala 2.11.


Using absolute imports for wagtailadmin scss.

This is to facilitate overriding of default styles via staticfiles.
I wanted to change some variables in the admin scss. I was unable achieve this without doing nasty things with copy-pasting all of wagtailadmin static. This change allows me to just override static/wagtailadmin/scss/variables.scss.

Hi @m-sanders,
It looks like this commit has somehow got mixed up with 8fe8c5bc134fd78817b9450ce6e525b39461ceb9 - perhaps you ran git rebase to squash multiple commits into one, and inadvertently included this older one. Please can you re-apply this on top of current master?

I have no idea how I managed that, usually use mercurial all day and rarely touch git. I am on it!


acme.sh: command not found

Hi All,
I'm using the latest version of docker-letsencrypt-nginx-proxy-companion from Dockerhub and have the follwing error when starting up:
calling acme.sh --register-account with the following parameters : --log /dev/null --debug 2 --server https://acme-v02.api.letsencrypt.org/directory --config-home<EMAIL_ADDRESS>--accountemail<EMAIL_ADDRESS>/app/letsencrypt_service: line 265: acme.sh: command not found
grep<EMAIL_ADDRESS>No such file or directory

Everything worked fine when I used a previous version which didn't use acme. When I bash into the container I see that /app/acme.sh is there and executable.
What could be wrong?
Best regards,
Oliver

Docker image has this command:
ENV COMPANION_VERSION=v2.0.1-6-ga717c35 DOCKER_HOST=unix:///var/run/docker.sock PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/app
But $PATH outputs this:
bash-5.0# $PATH bash: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin: No such file or directory

Duplicate of #732

@sparx82 @XanderStrike any idea why the $PATH might not work inside your containers ? The fact that the CI is still passing means it's working properly in some cases and not in others.

I use Portainer as a docker management system. The ENV Path was defined like this:

And when I add /app, everything works:

I also use Portainer, interesting! Did you update it using Portainer? That's what I did, I wonder if it clobbered the changes to PATH.
I resolved my issue by starting over from scratch (deleting everything including the volume, reinstalling from the readme in this repo) and letting it generate all new certs. This only resulted in a few minutes downtime for my ~50 sites which isn't too bad at all.

From #732:

Based on the other issue I suspect this was a PATH problem caused by Portainer's upgrade feature that keeps environment variables while changing the container image.

@XanderStrike that seems likely. Is there a way to set a custom PATH in a Docker image that won't interfere with this feature of Portainer ?

Did you update it using Portainer?

Yes, I used "Recreate" and switched on the "Pull latest image". And I was on "latest", it pulled that one. I guess it did not update the PATH using this method.

Well that settles it then!

Is there a way to set a custom PATH in a Docker image that won't interfere with this feature of Portainer ?

I've done some experimenting and Portainer seems to pull all environment variables out of the Dockerfile and sets them in stone forever.
I don't think there's anything for this project to do, definitely seems like a bug or at least bad behavior with Portainer. I've created an issue to get their thoughts here: https://github.com/portainer/portainer/issues/4665

Given the answer received by @XanderStrike in https://github.com/portainer/portainer/issues/4665, I'm going to remove the bug label and close this issue. If Portainer isn't disposed to discriminate between image's default environment variable and user set environment variable, I'm not disposed to accommodate Portainer non standard way of creating containers either.

Given the answer received by @XanderStrike in https://github.com/portainer/portainer/issues/4665, I'm going to remove the bug label and close this issue. If Portainer isn't disposed to discriminate between image's default environment variable and user set environment variable, I'm not disposed to accommodate Portainer non standard way of creating containers either.


Cannot create the index

Using 2.0
I'm creating new DB with indexes on application startup.
12 of 19 indexes gets create successfully. Then I get exception
com.orientechnologies.orient.core.index.OIndexException: Cannot create the index 'Exchange.order'
at com.orientechnologies.orient.core.index.OIndexAbstract.create(OIndexAbstract.java:240)
at com.orientechnologies.orient.core.index.OIndexOneValue.create(OIndexOneValue.java:108)
at com.orientechnologies.orient.core.index.OIndexOneValue.create(OIndexOneValue.java:45)
at com.orientechnologies.orient.core.index.OIndexManagerShared.createIndex(OIndexManagerShared.java:169)
at com.orientechnologies.orient.core.index.OIndexManagerProxy.createIndex(OIndexManagerProxy.java:79)
at com.orientechnologies.orient.core.metadata.schema.OClassImpl.createIndex(OClassImpl.java:1434)
at com.orientechnologies.orient.core.sql.OCommandExecutorSQLCreateIndex.execute(OCommandExecutorSQLCreateIndex.java:252)
at com.orientechnologies.orient.core.sql.OCommandExecutorSQLDelegate.execute(OCommandExecutorSQLDelegate.java:64)
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.executeCommand(OAbstractPaginatedStorage.java:1176)
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.command(OAbstractPaginatedStorage.java:1165)
at com.orientechnologies.orient.core.command.OCommandRequestTextAbstract.execute(OCommandRequestTextAbstract.java:63)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.command(ONetworkProtocolBinary.java:1180)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.executeRequest(ONetworkProtocolBinary.java:385)
at com.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstract.execute(OBinaryNetworkProtocolAbstract.java:216)
at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:65)
Same happens in studio. The command is
create index Exchange.order on Exchange (order) UNIQUE_HASH_INDEX
and it worked fine with 1.7.*
Maybe the problem is that schema was not created correctly. When I look at it in studio->schema I dont see Type and LinkedClass set on order property
When I try to set it manually
I get
java.lang.IllegalArgumentException: Cannot change property type from CUSTOM to LINK [ONetworkProtocolHttpDb]
2015-01-23 11:02:06:201 SEVERE Internal server error:
com.orientechnologies.orient.core.exception.OSchemaException: Linked class is not supported for type: CUSTOM [ONetworkProtocolHttpDb]
btw. how can I print schema for given class (so I can paste it here?)
I managed to export whole schema. Exchange object looks like this:
{
"name": "Exchange",
"default-cluster-id": 20,
"cluster-ids": [20],
"super-class": "ObservablePojoWithId",
"cluster-selection": "round-robin",
"properties": [
{
"name": "addressTransaction",
"type": "CUSTOM",
"collate": "default"
},
{
"name": "bankTransaction",
"type": "CUSTOM",
"collate": "default"
},
{
"name": "customer",
"type": "CUSTOM",
"collate": "default"
},
{
"name": "order",
"type": "CUSTOM",
"collate": "default"
},
{
"name": "warnings",
"type": "EMBEDDEDLIST",
"linked-type": "STRING",
"collate": "default"
}
]
},
"type": "CUSTOM" is likely the problem
Which brings question: When I do:
db.getEntityManager().registerEntityClasses("first");
db.getEntityManager().registerEntityClasses("second");
Can objects from first have links to second ?

Hi @PavelNiedoba
I'm afraid you are right, it seems that the schema was not created correctly.
Could you try to drop and re-create the properties (http://orientdb.com/docs/last/SQL-Drop-Property.html) ? It will not affect your data.
Luigi

Closed because of no reply.


Ability to pin version

It would be great to have the ability to pin the Chromium version. I know it's possible to say PUPPETEER_SKIP_CHROMIUM_DOWNLOAD, but I'd like to maintain the auto-download functionality while also pinning the version.

We pin the version since it is updated as new features are added/fixed that the new versions use. If you'd like to pin a specific version, then specify an exact puppeteer version since that will give you the build of this module with the Chromium package known to work with it.

Oh, didn't realize the version is pinned in package.json. Pinning the puppeteer version is a perfect solution for us, thanks!


Adds a cat and then a gat

The Calico M900 is an auto-fire carbine with a 100 round cylindrical magazine.
https://en.wikipedia.org/wiki/Calico_M960
The Calico Cat is a domestic feline with a distinctive fur pattern consisting of white, black and orange splotches.
https://en.wikipedia.org/wiki/Calico_cat

Address the reviews and it's ready to merge.

Reviews addressed, merge me Dad.


Support for type hints

Add support for type hints. This makes it easier to work with the library in an IDE.
If this is a desired extension, I would provide the implementation for it.

Hi @Pevtrick, the library could use some cleanup, so PRs would def be appreciated

Addressed in https://github.com/sqids/sqids-python/pull/7


Fix CI failure due to missing files when installed

https://github.com/numba/numba/pull/5174 failed internal CI because some files needed by testing is not included in the installation.
This patch adds two __init__.py so that find_packages() in setup.py will automatically pick up the needed directories.

@sklam thanks for the fix.

Will queue this for internal CI

Running as numba_107

@sklam do you know why this only appears on OSX?

Also windows and some of the aarch stuff.

It's whether the test is running is the source root and whether numba is setup.py installed. The new nested module test are not installed.


Input field connected to disclaimer checkbox on swap screen

The input field won't let me provide a RDN amount unless i tick the disclaimer checkbox first and if I were to deselect the disclaimer checkbox the input field won't let me remove an already provided RDN value.
Feels more natural if the checkbox affects the state of the button only and not the input field.

obselete with the new design


UI State not available on print job

Google Cloud Print provides a UI State that includes a summary, progress of a job, and a cause for display use.  Parsing that information into the print_job would help us display errors correctly with the same terminology as Google's UI.

I created a pull request for this.  I'm probably going to publish another gem of my fork since there hasn't been a commit on this repo in a while and I need the functionality.
https://github.com/thegengen/cloudprint/pull/28


Receiving "Invalid command run" when running "probot run"

Bug Report
Current Behavior
When running probot run the probot command prints "Invalid command run" message, yet runs the bot anyway. Seems like the message is printed by mistake.
Expected behavior/code
Probot should simply run, when issuing probot run.
Environment

Probot version(s): v9.8.0
Node/npm version: Node 12/npm 6.13.4
OS: OSX 10.15.2

Additional context/Screenshots
$ ./node_modules/.bin/probot run

Invalid command run

Usage: probot <command> [options]

Options:
  -V, --version  output the version number
  -h, --help     output usage information

Commands:
  run            run the bot
  receive        Receive a single event and payload
  help [cmd]     display help for [cmd]
08:43:34.130Z  INFO probot: Forwarding https://smee.io/<obfuscated> to http://localhost:3000/
08:43:34.132Z  INFO probot: Listening on http://localhost:3000
08:43:34.776Z  INFO probot: Connected https://smee.io/<obfuscated>

This looks like a bug introduced with #1097. For the time being, you can ignore the messages or pin your Probot dependency to v9.6.6.
Pinging @jamesgeorge007, could you take a look at this?


Guide: JBatch with Helidon

Let's check with Dmitry re: the location of the sample code currently located here:  https://github.com/dalexandrov/helidon-jbatch
Should examples be moved to Helidon repo?

See #3895


Roll Flutter Engine from a8e9ac63fd95 to ad382c1692d4 (1 revision)

https://github.com/flutter/engine/compare/a8e9ac63fd95...ad382c1692d4
2023-05-08<EMAIL_ADDRESS>Roll Skia from 5f7e572995b1 to 64ba57381c94 (1 revision) (flutter/engine#41814)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jimgraham@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Deleting an entire line in a long text inside an input makes scroll to the top on iOS

Describe the bug
When I delete an entire line of a long text it makes the scroll view scroll to the top. It happend on Android on 1.11.6 as well but has been fixed between 1.11.6 and the current version (1.12.6)
Code snippet
      <KeyboardAwareScrollView>         <Input.Area           autoFocus           scrollEnabled={false}           value={editText}           minHeight={55}           onChangeText={setEditText}         />       </KeyboardAwareScrollView>
Expected behavior
The view shouldn't scroll if the line is not hidden
Screenshots
https://github.com/user-attachments/assets/fcf71eba-a64b-46ac-bfc8-bb1db930b522
Smartphone (please complete the following information):

Device: iPhone SE 2020 (but we tested with different iphones)
OS:17.5.1
RN version: 0.73.6
RN architecture: new
JS engine: Hermes
Library version: [e.g. 1.2.0]

@ticketapp do you have a big single TextInput (multiline, but with disabled scroll) on the page?
Does it makes sense to use the KeyboardAwareScrollView or maybe it would be better to use KeyboardAvoidingView in this case? 🤔

@kirillzyusko yes I have a big single TextInput (multiline with disabled scoll) on this page, but I have an other page with other elements of undetermined height where I need a KeyboardAwareScrollView

@ticketapp in your case the problem happens, because KeyboardAwareScrollView detects text changes inside inputs and tries to assure, that input is located within visible area and is not obscured by header or keyboard:
https://github.com/kirillzyusko/react-native-keyboard-controller/blob/dce5a5741d701789fb97d852439b83f9ab1c2d7d/src/components/KeyboardAwareScrollView/index.tsx#L244
Since you have a big input which is simultaneously obscured by keyboard and header - whenever you modify the text it will scroll down.
A straightforward approach would be to add a new property to KeyboardAwareScrollView and allow to run this handler (onChangeText) conditionally.
A more sophisticated approach would be to track cursor position (onSelectionChange from useFocusedInputHandler) and assure it's always in visible area but it would require more code changes😅
I think temporarily you can patch-package this library and comment out onChangeText handler - and in a meantime I'll try to invent a solution that will cover all the cases 👍

Thank you very much for your response

Many thanks @kirillzyusko 🙏🏽


Rebase bladedisc 20220830

TensorFlow mainly update:

Extract StreamExecutors into OpenXLA
Extract StableHLO
Update new DenseArray attribute https://discourse.llvm.org/t/rfc-introduce-a-new-dense-array-attribute/63279

Mark https://github.com/alibaba/BladeDISC/pull/602


Improve auto updates

Improves upon the automated update PRs introduced in #12 to resolve issues brought up in the first automated PR #14

Give more information about the updates, not much, but at least the output of npins update
Update all npins sources, not just Nixpkgs.
Also run a cargo update
Make it trigger CI by using an unprivileged separate machine account (welcome, @infinixbot!)
Set committer and author of the commits to the machine account

Now that I configured the repo secret correctly, it works: https://github.com/NixOS/nixpkgs-check-by-name/pull/17 :D


Hide "Load More" labs button when all labs are loaded

"Within the Labs menu - if you reach the end of the Labs and click "Load More Labs", the button stays looking selected/on but never switches off or gives a message saying the end of the list was reached"

Tested it out, and on dev at least, there's 457 labs. Two big problems to implementing this right now:

1: The server doesn't implement pagination, and it doesn't distinguish if you've asked for all the available data. Any request made for more than the available labs, the server just returns as many as it can give you in the requested size. If I ask for 500, the server will send all 457.
2: Because there's no pagination, every request sends all the data. So the initial request for 9 labs is fine. Click "Load More" and it will ask for 18 labs, and it will receive the data of the first 9 labs again. Click "Load More" again, get sent more duplicated data.

I think the right move here is to address this with the server refactor, and implement pagination properly in the new backend. Then we can implement a response that tells the frontend "End of data", and can hide "Load More" in response. Pagination will also have the benefit of reducing responses with duplicate data.

The server does actually implement pagination. The API supports a skip parameter, and the API call does return a total count (the app just currently throws it away)

Yeah, it was implemented in the old frontend, but got stuck in a WIP PR in the new frontend: https://github.com/eternagame/eternagame.org/pull/215


Extend prismaWhere generated Input

How can I change the type of the generated input when I use builder.prismaWhere, for example if I want to change (remove or add) a field in the input? Currently I have types issues if I do this, and I have to use exactly the same input type as Prisma.

The prisma-utils package is still pretty early in it's development.  If you need to customize the fields beyond what's currently possible, you will likely need to create your own input types manually.

Ok, thanks, I don't need to look any further then! I'll create my own!

Just ran into this same issue.
  const ThingWhere = t.builder.prismaWhere("Thing", {
    fields: {
      tags: t.builder.prismaFilter(["String"], {
        ops: ["hasSome"],
        name: "TagsFilter",
      }),
      category: GraphQLStringFilter,
      authorId: t.builder.prismaFilter("String", {
        ops: [GraphQLFilterOp.equals],
        name: "AuthorFilter",
      }),
      privacy: t.builder.prismaFilter(Privacy, {
        ops: [GraphQLFilterOp.equals],
        name: "PrivacyFilter",
      }),
      favorited: t.builder.prismaFilter("Boolean", {
        ops: [GraphQLFilterOp.equals],
        name: "FavoritedFilter",
      }),
    },
  });

The favorited field is calculated based on the relationship being present; there is favorites relationship it looks at, using directly made the GraphQL calls a bit awkward.

Yeah, this makes sense, and I think it could make sense to support additional fields.  It's a little tricky because a big part of these helpers is to ensure that the types are compatible with prisma.
Additional fields can be pulled out, but if you want to add a field that matches an existing prisma field (but use a custom type)  there are 2 options which both seem bad:
Either allow you to define any field name as being any type (this would mean losing all type-safety from the prisma schema) or just don't allow you to  create custom fields that match properties in your prisma types.
The alternative I've been considering is to create a new method that allows you to extend or modify input types after definition.  I don't have any API in mind yet for exactly how this would work.
There are a couple of other ideas I've been considering that might also help:

Adding the ability to alias/rename input fields (the plugin would automatically map the alias field to the right prisma property
Adding the ability to flatten filters

// this would likely not be the actual API, but roughly shows the ideas from above
 const ThingWhere = t.builder.prismaWhere("Thing", {
    fields: {
      favorites: {
        alias: 'favorite',
        type: t.builder.prismaFlatFilter("Boolean", {
          op: GraphQLFilterOp.equals,
          name: "FavoritedFilter",
        }),
      }
    },
  });

I'd be interested in what your ideal API would be:

What do the GraphQL types look like (GraphQL sdl)
What would the arguments/input values look like in the resolver
How would you want to define those types with the builder

Another question:
If you are customizing the input types already to not match exactly the shape that prisma expects, what benefit are you hoping for from using prismaWhere over just using a normal input type. The main one I can think of is converting nulls to undefined, but interested to hear if there are other benefits you are looking for

I might also just be attempting to misuse this API. And I am glad they keep compatibility with Prisma, has been helpful on the client side when trying to implement filtering as I was used to with Hasura.
In order to mix and match as needed I suppose I should just create use builder.inputType and then call implement?
ThingWhere.implement("Thing", {
    fields: (t) => ({
      otherField: t.string({ required: true }),
      favorited: {
        type: t.builder.prismaWhereField("Boolean", {
          op: GraphQLFilterOp.equals,
          name: "FavoritedFilter",
        }),
      }
    }),
  });

Again I just might be going about this all the wrong way. I am mainly looking for a way to keep the filters strict to a Prisma objects field where I need it and then allow custom inputs along side.


XInput (Xbox One Controller Emulation) compatibility improvements

Keeping notes and track of ideas regarding XInput mode problems and brainstorming about what could be done to improve compatibility up to a level where it - hopefully - could totally replace the need for Xbox 360 device emulation (which requires additional drivers and software due to restrictions of user-mode drivers).
See #114

Testing with Hollow Knight
XINPUT compatible HID device

Changed Device ID to HID\VID_045E&PID_02FF&IG_00
Changed Hardware IDs to HID\VID_045E&PID_02FF&IG_00
Changed Class to HIDClass
Changed used INF from dshidmini.inf to xinputhid.inf
Changed HIDD_ATTRIBUTES.VendorID to 0x045E
Changed HIDD_ATTRIBUTES.ProductID to 0x02FF

Not yet enough to make the game detect the controller.

Testing with Hollow Knight
Changing the product string HidD_GetProductString returns to
#define DSHIDMINI_PRODUCT_STRING         L"Controller (Xbox One For Windows)"

made the controller appear in HK!

Changing the device class to HIDClass made DSHM devices appear in the HidHide config tools!

Next subject: why is the device not recognized by Gamepad Tester.

Funny enough it works just fine on Windows 10 Chromium Edge:

Firefox also happy:

Doesn't get detected by Brave on Windows 11...

Oh well...
According to the Chromium source code these devices should be enumerated using XInput so I wonder where these inconsistencies come from.

Research notes dump


#158138248 A logged in user can modify their requests

What does this PR do?
Allows a logged in user to modify their previously made request.
Description of Task to be completed?

User view modify request.
Ensuring token is passed to the header.
Ensure user can only edit their own request.

How should this be manually tested?
$ git clone https://github.com/dalaineme/m-tracker.git

$ cd m-tracker

Create a virtual environment
$ python3.6 -m venv venv

Activate a virtual environment
$ source venv/bin/activate

Install project dependencies
$ pip install -r requirements.txt

Run the server
$ python run.py

Using postman, send a PUT request to the URL http://<IP_ADDRESS>:5000/api/v1/users/requests/
Refer to the screenshots below.
Any background context you want to provide?
Authorization header MUST be provided
What are the relevant pivotal tracker stories?
https://www.pivotaltracker.com/story/show/157931429
Screenshots
Validation errors.

Request doesn't exist.

Successful Request update.

.

Pull Request Test Coverage Report for Build 171

27 of 29 (93.1%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 95.254%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

api/server/request/views.py
19
21
90.48%

Totals

Change from base Build 169:
-0.3%

Covered Lines:
281

Relevant Lines:
295

💛  - Coveralls


Adjust and Fix Snapshot Timings

This is meant to be a master ticket to help track the state of snapshot timing fixes across all characters. This is meant to align with the findings being made in the KQM #snapshot-timings channel, as well as adjust some of the current snapshot implementations for dynamic attacks (e.g., NAs and CAs) that occur before the actual hit lands, which can lead to timings being off on buffs.

[ ] Jean
[ ] Kaedehara Kazuha
[ ] Sayu
[ ] Sucrose
[ ] Traveler (Anemo)
[ ] Venti
[ ] Xiao
[ ] Aloy
[ ] Chongyun
[ ] Diona
[ ] Eula
[ ] Ganyu
[ ] Kaeya
[ ] Kamisato Ayaka
[ ] Qiqi
[ ] Rosaria
[ ] Beidou
[ ] Fischl
[ ] Keqing
[ ] Kujou Sara
[ ] Lisa
[x] Raiden Shogun
[ ] Razor
[ ] Traveler (Electro)
[ ] Albedo
[ ] Ningguang
[ ] Noelle
[ ] Traveler (Geo)
[ ] Zhongli
[ ] Barbara
[ ] Mona
[ ] Sangonomiya Kokomi
[ ] Tartaglia
[x] Xingqiu
[ ] Amber
[ ] Bennett
[ ] Diluc
[ ] Hu Tao
[ ] Klee
[ ] Xiangling
[ ] Xinyan
[ ] Yanfei
[ ] Yoimiya

With the new AttackEvent refactor done, this needs to be rechecked for all characters effectively.

relevant sheet: https://docs.google.com/spreadsheets/d/1M2nTLogzYd2o4ZLkYEkzfovwiTznQOB5ujWuMlQbE0k/edit?usp=sharing


W-15805907: assign_permission_set_licenses accepts the api_names in either developerName or the PermissionSetLicenseKey

To handle the compatibility issues and ensure smooth functionality for both get_available_permission_set_licenses and assign_permission_set_licenses, you can make the following adjustments:

Revert get_available_permission_set_licenses to Return PermissionSetLicenseKey:

This will maintain backward compatibility.

Update assign_permission_set_licenses to Accept Both DeveloperName and PermissionSetLicenseKey:

Modify the function to handle input as either DeveloperName or PermissionSetLicenseKey, ensuring it can correctly interpret and process both formats. This adjustment will resolve issues with names like alpha.beta where the DeveloperName is alpha_beta.  Accepts api_name as  alpha_beta or  alpha.beta and assigns them correctly

Hi @jkasturi-sf @jstvz @vsbharath
Please review the PR
Thank you

Hi @jstvz
Combined the queries into one, updated the task docs.
Please review the PR
Thank you


[Additional Parameter Request]  publisher OnBeforeDeleteSalesLines Table 36-"Sales Header"

Could we please have the "Rec" as parameter in publisher OnBeforeDeleteSalesLines  of table 36-"Sales Header".
We pass some global variables of our table extension through this event and needs also the GetHideValidationDialog procedure.
table 36 "Sales Header"
{
...
    local procedure DeleteSalesLines()
    var
        ReservMgt: Codeunit "Reservation Management";
        IsHandled: Boolean;
    begin
        // >>>>>>>>>>>>>>>>>
        //OnBeforeDeleteSalesLines(SalesLine, IsHandled);
        OnBeforeDeleteSalesLines(Rec, SalesLine, IsHandled);
        // <<<<<<<<<<<<<<<<<
        if IsHandled then
            exit;

        if SalesLine.FindSet then begin
            ReservMgt.DeleteDocumentReservation(DATABASE::"Sales Line", "Document Type", "No.", GetHideValidationDialog);
            repeat
                SalesLine.SuspendStatusCheck(true);
                SalesLine.Delete(true);
            until SalesLine.Next = 0;
        end;
    end;

local procedure OnBeforeDeleteSalesLines(>>>>var SalesHeader: Record "Sales Header";<<<< var SalesLine: Record "Sales Line"; var IsHandled: Boolean);
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


[Bug] sheet.insertRows/insertRowsAfter is not a function

Before you submit this issue, have you checked the following

[X] Is this really a problem?
[X] I have searched the Github Issues for similar issues, but did not find anything.

Affected packages and versions
0.2.15
Reproduction link
https://codesandbox.io/p/devbox/rt9vcq
Expected behavior
The API can be used normally. I'm not sure if there's a problem with the UMD citation, but the official website Playground also has this issue.
Actual behavior
is not a function
System information
No response

Please provide an accessible minimization reproduction.

Please provide an accessible minimization reproduction.

@jikkai  https://codesandbox.io/p/devbox/rt9vcq

Please provide an accessible minimization reproduction.

it's a public sandbox now

Please use the latest version.

Please use the latest version.

Thanks a lot~~~ I copied this version from https://univer.ai/zh-CN/playground?title=UMD, the officail Univer website. And there is a spelling error about div id=app.  Could you please update the examples in the official website playground when you have time


swift run danger-swift ci --> [!] Unknown command: ci

Hello,
I am trying to convert this SwiftPM package to danger-swift from danger-ruby (the latter relied on generating an XcodeProject throush swift pacakge manager and then use fastlane scan to run the tests and Danger's xcov and junit plugins to do the rest, like we do for our apps), but I am running into some trouble.
First it was adding Danger itself and the two main plugins (discovering later that danger-swiftlint had been merged into Danger-Swift itself, but again not clear for the README here perhaps), but then after resolving all the dependencies and adding the .git folder to the repo (who is now 1.4 GB, unless I did that pre-commit hooks in Tower/SourceTree would bail out at some point), but after sorting those out the last problem is the more puzzling one:
Running this in the test script:
[...]

Test Suite 'NativeCorePackagePackageTests.xctest' passed at 2020-05-24 23:35:25.034.
	 Executed 41 tests, with 0 failures (0 unexpected) in 0.266 (0.268) seconds
Test Suite 'All tests' passed at 2020-05-24 23:35:25.034.
	 Executed 41 tests, with 0 failures (0 unexpected) in 0.266 (0.268) seconds

[...]

    swift test | XCPRETTY_JSON_FILE_OUTPUT=result.json xcpretty -f `xcpretty-json-formatter`
    swift run danger-swift --fail-on-errors=true

Result on the CI agent (which has danger-js installed too)
[!] Unknown command: `ci`
Did you mean: pr?

which is now what I would want to run (I need something that will post to the PR) considering the documentation of the pr command:
Usage:

    $ danger pr

      Run the Dangerfile locally against Pull Requests (works with forks, too). Does
      not post to the PR. Usage: danger pr <URL>

As a reference...
Dangerfile.swift
import Danger
import DangerSwiftCoverage
import DangerXCodeSummary

let danger = Danger()
checkChangelog()

if danger.git.createdFiles.count + danger.git.modifiedFiles.count - danger.git.deletedFiles.count > 300 {
    warn("Big PR, try to keep changes smaller if you can")
}

SwiftLint.lint(.modifiedAndCreatedFiles(directory: "Modules"),
               inline: true)

let summary = XCodeSummary(filePath: "result.json")
// let summary = XCodeSummary(json: JSONFile.jsonObject(fromString: reportTestJSON), dsl: dsl, resultsFilter: { result in
//     return result.category != .warning
// })
summary.report()

Coverage.spmCoverage(minimumCoverage: 0.001)

// Support running via `danger local`
if danger.github != nil {
    // These checks only happen on a PR
    if danger.github.pullRequest.title.contains("WIP") {
        warn("PR is classed as Work in Progress")
    }

    // TODO: We're still figuring this out
    _ = danger.github.api.me { response in
        print("OK")
        switch response {
            case let .success(user):
                message(user.name ?? "")
            case .failure:
                break
        }
    }
}

Package.swift
// swift-tools-version:5.2
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

extension Target {
    static func target(name: String,
                       sources: [String],
                       dependencies: [Target.Dependency] = [])
        -> Target {
        .target(name: name,
                dependencies: dependencies,
                path: "Sources",
                exclude: [],
                sources: sources,
                publicHeadersPath: nil,
                cSettings: nil,
                cxxSettings: nil,
                swiftSettings: nil,
                linkerSettings: nil)
    }
}

let package = Package(name: "NativeCorePackage",
                      products: [.library(name: "NativeCorePackage", targets: ["NativeCorePackage"]),
                                 .library(name: "DangerDeps", type: .dynamic, targets: ["DangerDependencies"]) // dev
                      ],
                      dependencies: [.package(path: "Modules/NativeCurrencyFormatter"),
                                     // .package(path: "Modules/NativeHelpersModule"),
                                     // .package(path: "Modules/"),

                                     .package(url: "https://github.com/shibapm/Rocket", from: "1.0.1"),
                                     .package(url: "https://github.com/Quick/Quick.git", from: "2.2.0"), // dev
                                     .package(url: "https://github.com/Quick/Nimble.git", from: "8.0.7"), // dev
                                     .package(url: "https://github.com/shibapm/PackageConfig.git", from: "0.12.2"),
                                     .package(url: "https://github.com/f-meloni/TestSpy", from: "0.4.1"), // dev
                                     .package(url: "https://github.com/realm/SwiftLint.git", .exact("0.39.2")), // dev
                                     .package(url: "https://github.com/nicklockwood/SwiftFormat.git", .exact("0.44.11")), // dev

                                     .package(name: "danger-swift", url: "https://github.com/danger/swift.git", from: "3.0.0"), // dev
                                     .package(name: "DangerXCodeSummary", url: "https://github.com/f-meloni/danger-swift-xcodesummary", from: "1.2.1"), // dev
                                     .package(name: "DangerSwiftCoverage", url: "https://github.com/f-meloni/danger-swift-coverage", from: "1.1.0") // dev
                      ],
                      targets: [.target(name: "NativeCorePackage",
                                        dependencies: ["NativeCurrencyFormatter"],
                                        exclude: ["Pods",
                                                  "output_dir",
                                                  "test_output",
                                                  "Modules/NewModules"]),
                                .testTarget(name: "NativeCorePackageTests",
                                            dependencies: ["NativeCorePackage",
                                                           "Quick",
                                                           "Nimble"],
                                            exclude: ["Pods",
                                                      "output_dir",
                                                      "test_output",
                                                      "Modules/NewModules"]),
                                .target(name: "DangerDependencies", dependencies: ["danger-swift", "DangerXCodeSummary", "DangerSwiftCoverage"]) // dev
                        ])

I think it's calling to Danger ruby on your CI, and not to Danger JS /cc @f-meloni

Hello @orta thanks for the reply I will try completely removing the ruby danger locally and on CI and try again, did not expect it to do that when calling:
swift run danger-swift —fail-on-errors=true

:/
P.S:
Once this is sorted, I will be making a PR for the README as currently (is it just Swift 5.2 version of SPM maybe?) the Package.swift integration of Danger you find in the README does not work (hence the changes in my original message here).
If I install danger-swift through brew, can I still use plugins @f-meloni  wrote for Danger-Swift and would I do that using SwiftPM or would they be on bee too?

Both danger-js and danger ruby are called danger, this means that when Danger-Swift tries to find the path for the bin danger it could get the wrong one if you have both installed.

This worked, thanks @f-meloni  @orta . Went and checked all projects to make sure they were using locally bundled danger (through bundler) and removed all globally installed danger tools (beside the danger-js installed through npm, maybe we should be advising people to install it locally through npm?)


AttributeError: 'ConfigDict' object has no attribute 'gpu_ids'

when we use mmdetv2 to do detection task, the error occured, can you tell me how to do it?
the error is as follows:
Traceback (most recent call last):
File "/home/lgl/PycharmProjects/DetectoRS-mmdetv2/train_crossing.py", line 148, in
main()
File "/home/lgl/PycharmProjects/DetectoRS-mmdetv2/train_crossing.py", line 144, in main
meta=meta)
File "/home/lgl/PycharmProjects/DetectoRS-mmdetv2/mmdet/apis/train.py", line 116, in train_detector
seed=cfg.seed) for ds in dataset
File "/home/lgl/PycharmProjects/DetectoRS-mmdetv2/mmdet/apis/train.py", line 116, in
seed=cfg.seed) for ds in dataset
File "/home/lgl/anaconda3/envs/DetectoRS/lib/python3.6/site-packages/mmcv/utils/config.py", line 324, in getattr
return getattr(self._cfg_dict, name)
File "/home/lgl/anaconda3/envs/DetectoRS/lib/python3.6/site-packages/mmcv/utils/config.py", line 36, in getattr
raise ex
AttributeError: 'ConfigDict' object has no attribute 'gpu_ids'

This looks like a mmdetection problem. Sorry, but I have no idea how it happened.


spotify: add libglvnd

Description of changes
Fixes error spam:
ERR: Display.cpp:1066 (initialize): ANGLE Display::initialize error 12289: Could not dlopen libGL.so.1: libGL.so.1: cannot open shared object file: No such file or directory
ERR: Display.cpp:1066 (initialize): ANGLE Display::initialize error 12289: Could not dlopen libGL.so.1: libGL.so.1: cannot open shared object file: No such file or directory
ERR: Display.cpp:1066 (initialize): ANGLE Display::initialize error 12289: Could not dlopen libGL.so.1: libGL.so.1: cannot open shared object file: No such file or directory
ERR: Display.cpp:1066 (initialize): ANGLE Display::initialize error 12289: Could not dlopen libGL.so.1: libGL.so.1: cannot open shared object file: No such file or directory

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[x] 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/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[x] (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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

typo

I believe we should add libGL instead of libglvnd, maybe the respective maintainers can also provide some opinions. cc @primeos @vcunat


[!] CocoaPods could not find compatible versions for pod "sound_generator":

Not sure what error I am making when importing the package.

same issues here
any idea to fix it?

same issues here
any idea to fix it?

Nope I just started using android instead.

I have this issues in a M1 Mac Mini
And I build few projects using sound generator normally.
However, this time I try to make my previous project as packages to import.
I encounter this error when I trying to do so.
On android it works perfectly.

Did you tried to put " pod 'AudioKit', '4.11.2' " in the pod file?
However I failed to pod update it

I fixed this issue by create another project and move my code to it～

I tried creating a new project and copying the code over. It didn't work. What exactly did you change?

`# Uncomment this line to define a global platform for your project
platform :ios, '12.0'
CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'
project 'Runner', {
'Debug' => :debug,
'Profile' => :release,
'Release' => :release,
}
def flutter_root
generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), FILE)
unless File.exist?(generated_xcode_build_settings_path)
raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
end
File.foreach(generated_xcode_build_settings_path) do |line|
matches = line.match(/FLUTTER_ROOT=(.*)/)
return matches[1].strip if matches
end
raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end
require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)
flutter_ios_podfile_setup
target 'Runner' do
use_frameworks!
use_modular_headers!
flutter_install_all_ios_pods File.dirname(File.realpath(FILE))
end
post_install do |installer|
installer.pods_project.targets.each do |target|
flutter_additional_ios_build_settings(target)
end
end
pod 'AudioKit', '4.11.2'`
above is my Podfile used

Did you try my solution from issue #11 ?

fiexed with v0.0.9


Toggling comment fails in unsupported filetypes

Version
f7c2817 (at least)
Maybe, all commits which supports toggling comment function.
Vim Vesrion
all version
Details
When opening files of unsupported filetype, error message is shown like following:
Error detected while processing function Toggle_Comment[1]..Toggle_Comment_Pre:
line    8:
E121: Undefined variable: b:comment_str
E116: Invalid arguments for function strlen(b:comment_str)
Press ENTER or type command to continue

For example, b:commet_str variable is not defined in filetype text, but when pressing Ctrl + /, vim script tries to refer b:comment_str.
Frequency
every time

Fixed in b03474fac7f97d65d1a9801b58ec0527e2662c7a


Add support for comments

Comments are an important part of many formats serde supports. However, serde does not expose a comment type, so in current crates there is no way to add them.
Here are some people in the community asking for comment support:

https://github.com/alexcrichton/toml-rs/issues/274
https://github.com/dtolnay/serde-yaml/issues/145
https://github.com/dtolnay/serde-yaml/issues/219
https://github.com/dtolnay/serde-yaml/issues/100
https://github.com/serde-rs/json/issues/168

In addition, HJSON could be serializable instead of just deserializable
Comments are usually tied to fields. Perhaps serde could parse doc strings and expose them. For instance, if we had
struct Tester {
   /// use this for reason xyz
   a_field: u32
}

and used serde-yaml, we could generate
# use this for a reason xyz
a_field: 123

from
Tester { a_field: 123 }

However, this has disadvantages. It doesn't allow for dynamic comments. It might be better to have a Comment type, but I am not sure this would be as clean. At least it would be better in terms of backward compatibility. We could also have a custom comment property on fields. Thoughts?

You can see my responses in many of the issues you linked. I would prefer not to build this into this crate.


Add support for response compression

Component(s)
router
Is your feature request related to a problem? Please describe.
As a user, I'd like to be able to compress data between the client <-> router to save bandwidth and improve performance.
Describe the solution you'd like
Response compression is done transparently. The user of the router doesn't need to configure anything. The exchange is done through HTTP headers Accept-Encoding. The implementation should support Gzip, Deflate and Brotli as compression methods.
We need to extend the router to compress responses. A very reasonable choice for gzip could be https://github.com/klauspost/compress/tree/master/gzhttp which also serve as good inspiration for the other methods.
Requirements:

No CGO.
Functionality must be provided in separate Go modules with unit tests and  integration test. See test suite.
Use compression defaults that favor a good mix between compute time and space savings.

Describe alternatives you've considered
No response
Additional context
We use gin as http framework. The router engine transport can be found here https://github.com/wundergraph/cosmo/blob/main/router/core/transport.go
Previous issue #153

/bounty $200

/bounty $200

/attempt #602

/attempt  #602

@StarpTech do we need prehandler and posthandler to decode and encode the request body?

/attempt #602

Hi @StarpTech I have raised the draft PR. I would appreciate your help with further development. I need to know where I should use compression and decompression functions to achieve the desired results.

Hi @StarpTech I need you help in architectural understanding in know in I have to add it as prehandler and posthandler. But I am unable to understand where other prehandler and posthandler is added.

@Rutik7066 take a look at the referenced issue https://github.com/wundergraph/cosmo/issues/153 Wwe want to support client response compression. This means, a middleware needs to be implemented that overwrites responseWriter to support the compression algorithm. You can use https://github.com/go-chi/chi/blob/master/middleware/compress.go

@Rutik7066 take a look at the referenced issue https://github.com/wundergraph/cosmo/issues/153 We want to support client response compression. This means, a middleware needs to be implemented that overwrites responseWriter to support the compression algorithm. You can use https://github.com/go-chi/chi/blob/master/middleware/compress.go
This is already almost the full story. If I assistant you more, I could the address the bounty myself 😄

Got it 🫡

Hi @StarpTech work is completed. Could you please review PR

I'm interested in taking a shot at this, adding my name to the queue!

I'm interested in taking a shot at this, adding my name to the queue!

PR submitted already everything is done. I am waiting for @StarpTech to review the PR

Hi @StarpTech could you please review the PR

Hi @StarpTech, there is a lot going on right now. I promise to review it at the beginning of next week. Thank you for your patience.

I have decreased the scope of the ticket and therefore also the reward. Thanks for the contribution @Rutik7066

@StarpTech  what?

@StarpTech I think you know I worked because of 200$ bounty price right. If anything from my side needs to be corrected or completed then you should tell me instead of this thing.

Hi @Rutik7066,
I appreciate the effort you put into the project. However, it's important to note that the requirements were clearly outlined from the start. We've provided significant guidance throughout this process, which wasn't the intent of the bounty. You have completed response compression, which is only half of the requirement, and therefore received $100 as a reward.
The issue is closed.
Thank you for your understanding and contribution.

@StarpTech just because of some guidance on project code ? You are cutting half of the bounty.

Okay No problem I guess I have wasted you time as well.


[Event Request] codeunit 90 "Purch.-Post".PostDistributeItemCharge - OnAfterCalcFactorOnPostDistributeItemCharge

Please add a new event OnAfterCalcFactorOnPostDistributeItemCharge:
local procedure PostDistributeItemCharge(...)
begin
    if TempItemLedgEntry.FindSet() then begin
        repeat
            Factor := TempItemLedgEntry.Quantity / NonDistrQuantity;
            QtyToAssign := NonDistrQtyToAssign * Factor;
            AmountToAssign := Round(NonDistrAmountToAssign * Factor, GLSetup."Amount Rounding Precision");
            //***************************
            OnAfterCalcFactorOnPostDistributeItemCharge(PurchLine, TempItemLedgEntry, QtyToAssign, AmountToAssign, Sign, Factor);
            //***************************
            if Factor < 1 then begin
    ...
end;

[IntegrationEvent(false, false)]
local procedure OnAfterCalcFactorOnPostDistributeItemCharge(var PurchLine: Record "Purchase Line"; TempItemLedgEntry: Record "Item Ledger Entry";QtyToAssign: Decimal; AmountToAssign: Decimal; Sign: Decimal; Factor: Decimal)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


[Fix] Geometry editor scale mode issue

Description
This PR fixes Create and edit geometries in Maps category.
Linked Issue(s)

swift/issues/4794

How To Test
Create a geometry with uniform mode. Create another geometry with the toggle checked. It should still preserve the aspect ratio.

Thanks all!


State Handling Performance Speedup

Group all state updates in a given render cycle together
module React
  class State
    def self.set_state(object, name, value, delay=true)
      states[object][name] = value
      if delay || @bulk_update_flag
        @delayed_updates ||= Hash.new { |h, k| h[k] = {} }
        @delayed_updates[object][name] = [value, Set.new]
        @delayed_updater ||= after(0.0) do
          delayed_updates = @delayed_updates
          @delayed_updates = Hash.new { |h, k| h[k] = {} } # could this be nil???
          @delayed_updater = nil
          updates = Hash.new { |hash, key| hash[key] = Array.new }
          delayed_updates.each do |object, name_hash|
            name_hash.each do |name, value_and_set|
              set_state2(object, name, value_and_set[0], updates, value_and_set[1])
            end
          end
          updates.each { |observer, args| observer.update_react_js_state(*args) }
        end
      elsif @rendering_level == 0
        updates = Hash.new { |hash, key| hash[key] = Array.new }
        set_state2(object, name, value, updates)
        updates.each { |observer, args| observer.update_react_js_state(*args) }
      end
      value
    end
  end
end

Is this already on master? https://github.com/ruby-hyperloop/hyper-react/blob/master/lib/react/state.rb#L84

Might be!  I couldn't find the issue.  Note that the default on the second parameter is now true.  That makes a huge difference

Ok, I see. The change is actually introduced by https://github.com/ruby-hyperloop/hyper-react/issues/178

this doesnt work as expected with react, react seems unable to group setState calls outside of a render cycle. Preact can do this, maybe react 16 will improve this during its dot releases.
However, this can be achieved in React with: ReactDOM.unstable_batchedUpdates(), which, as the name suggests, is kinda unstable. Needs watching and adoption. If this a performance issue for somebody, i recommend to try with Preact.
As of lap20 state handling improved anyway, setting state synchronously where allowed.


Bicep parameters with default values are always passed as null

[ ] Make sure you've installed the latest version using instructions in the wiki

Output from azd version
azd version 1.9.5 (commit cd2b7af9995d358aab33c782614f801ac1997dde)
Describe the bug
Bicep parameters with default values are always passed as null, regardless of config.json
To Reproduce
Steps to reproduce the behavior...
Expected behavior
Define a parameter with a default value in main.bicep
param clientTags string = '{}'
azd provision doesn't prompt for it, which is expected, but the deployment behaves as though the param is null, regardless of what the default value is actually set to.
Crucially, supplying a value in config.json for the current environment makes no difference, the parameter is still null.
Environment
Information on your environment:
* Language name and version
* IDE and version : [e.g. Visual Studio 16.3]
Additional context
Add any other context about the problem here.

@jongio @vhvb1989 don't think azd passes/translates such default empty string params as null for deployment? any tips/tricks to handle it in bicep itself?


"host_module_id" in OS_module_prop_t might be too small on 64-bit machines

The OS_module_prop_t structure (output by OS_ModuleInfo) contains a field "host_module_id" which is a uint32 type.  This is possibly too small for some machines and can cause a warning, notably on 64-bit builds where the host module is tracked natively as a void*.
Suggest to either use a cpuaddr type instead, or to remove this field altogether as it is really a crutch that shouldn't be needed (a good abstraction means that the app shouldn't ever need to know this, and if the app actually does use it, then the app isn't portable).

Imported from trac issue 224.  Created by jphickey on 2019-06-11T19:44:03, last modified: 2019-07-26T15:13:27

Trac comment by jphickey on 2019-06-11 19:47:24:
Commit [changeset:3c2a4f6] on branch trac-224-fix-host-module-id ready for review.  (one-liner)

Trac comment by jhageman on 2019-06-24 12:38:58:
Milestone - would only be an API change on a 64 bit machine (really a bug fix) so targeting minor milestone vs a true API update which requires major version update.

Trac comment by jhageman on 2019-06-26 17:07:09:
Marked for CCB code review (for 7/3/19)

Trac comment by jhageman on 2019-07-17 16:51:41:
CCB 7/17/2019 - approved for merge to dev.

Trac comment by jphickey on 2019-07-11 11:19:52:
Merged into branch ic-ccb-2019-07-10 for integration test

Trac comment by jhageman on 2019-07-10 13:26:31:
CCB 7/10/2019 - code reviewed and approved for test

Trac comment by jphickey on 2019-07-17 18:52:55:
Merged to "development" branch

Trac comment by jhageman on 2019-07-26 15:13:27:
Milestone renamed


Remove unused Msg

I tried to search for usages of ChangedRoute and found none.

Thanks @mksmtn!

Fixed in https://github.com/rtfeldman/elm-spa-example/commit/30d19ec220634abd3f7a567bdf921df7192f4013 which resolves the merge conflict here.
Thanks again!


"BPF doesn't have JIT enabled" reported incorrectly when using docker

Describe the bug
Even if JIT is enabled for BPF, both falcosecurity/falco and facosecurity/falco-driver-loader are reporting the following message when run with -e FALCO_BPF_PROBE="":
******************************************************************
** BPF doesn't have JIT enabled, performance might be degraded. **
** Please ensure to run on a kernel with CONFIG_BPF_JIT on.
Screenshots
Environment

Falco version: 0.23.0
System info:

Cloud provider or hardware configuration:
OS:

Kernel: Linux ubuntu-xenial 4.15.0-101-generic #102~16.04.1-Ubuntu SMP Mon May 11 11:38:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Installation method: docker

Additional context
Because the view of /proc inside the container is different, this check is not working as expected when it runs inside a container. Note that prefixing the path with ${HOST} will not solve the issue anyway.

/help

@leodido:
This request has been marked as needing help from a contributor.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

/remove-lifecycle stale
/remove-lifecycle rotten
/milestone 1.0.0

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

IIRC, we suppressed the banner. https://github.com/falcosecurity/falco/pull/1811 attempted to re-introduce it, but I had some concern :point_down:
https://github.com/falcosecurity/falco/pull/1811#pullrequestreview-837474605
cc @LucaGuerra @FedeDP

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

/remove-lifecycle stale
/remove-lifecycle rotten
/milestone 1.0.0

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

/remove-lifecycle rotten

cc @therealbobo @LucaGuerra

A way to solve this issue is to use the --net=host flag but this is a terrible idea from a security standpoint: by giving the container access to the host network stack, it effectively eliminates any network isolation provided by Docker.
The only other way I can think of is to load dynamically a small bpf program and benchmark it: this comes with no guarantee of correctness (given that we have no actual baseline) and it isn't a clean approach.
Otherwise if the falco-driver-loader doesn't find the /proc/sys/net/core/bpf_jit_enable file we could assume that falco is running inside a container and alert the user to check outside of it.
I'll continue investigating.

After some more digging I discovered that it's possible to check if the jit is enabled using bpftool or writing a small program that essentially does the same of bpftool. I know that this solution is suboptimal but, at the moment, I think it's the only one.

After some more digging I discovered that it's possible to check if the jit is enabled using bpftool or writing a small program that essentially does the same of bpftool. I know that this solution is suboptimal but, at the moment, I think it's the only one.

If we directly do that in the eBPF probe, then Falco will be able to emit the warning (rather than falco-driver-loader), which is a superior solution.
cc @Andreagit97 @FedeDP
@therealbobo why do you think it is suboptimal? :thinking:

After some more digging I think there is a way to determine if the JIT is enabled without relying on /proc/sys/net/core/bpf_jit_enable (which is not visible inside the container unless the --net=nost flag is specified). At runtime if we check /proc/falco_pid/fdinfo/* (filled by https://github.com/torvalds/linux/blob/5f63595ebd82f56a2dd36ca013dd7f5ff2e2416a/kernel/bpf/syscall.c#L2170) we'll found some useful info about each ebpf probe. One of these info is prog_jited which is actually what we are looking for (it indicates if an ebpf prog is jited or not). I've already tested and I think it's a perfect source of truth: if all probes have the prog_jited = 0 we can assume that the JIT is disabled.
If all of you agree I can work on integrating this into falco. 😄

first of all, thank you for the investigation! Just some random thoughts:

As far as I know the bpf jit is now a sort of default so I expect it to be enabled unless some real corner cases. At the time the issue was opened probably it was a notable issue but 3 years are passed. WDYT?
I like the proposed solution, but just out of curiosity how does bpftool detect the jit enabled?

As far as I know it's a VERY corner case: I didn't find any distro that permits to disable the JIT... the only way to test my assumptions was to recompile the kernel 🤣 I totally agree that it isn't essential. The only problem, in my opinion, is the misleading error that shows up.
All the other tools, that I can think of and that I found, only check the value in /proc/sys/net/core/bpf_jit_enable

As far as I know it's a VERY corner case: I didn't find any distro that permits to disable the JIT... the only way to test my assumptions was to recompile the kernel, I totally agree that it isn't essential.

Uhm so if this is the situation probably I would simply close the issue, keeping in mind that we have a solution in the case.

The only problem, in my opinion, is the misleading error that shows up.

Please note that this log is no more present, this is a quite old issue

All the other tools, that I can think of and that I found, only check the value in /proc/sys/net/core/bpf_jit_enable

Thank you for the research!


add ability to set current user outside of login

I have created custom authentication outside of what azure mobile services provides following this guide:
http://azure.microsoft.com/en-us/documentation/articles/mobile-services-dotnet-backend-get-started-custom-authentication/
It would be nice to be able to set the currentUser manually, with the token returned from my custom authentication.

I think that this would be a great addition.  Correct me if I'm wrong but it sounds like you just need a method to set the current user object.  Is that correct?

Thats correct. I can see the method setting the current user then adding it to session storage.

@jmiazga I added some code that I think will allow what you are looking for.  However I recently switched jobs and currently dont have access to Azure to test it.  Do you mind testing and letting me know if that works for you before I tag it and release the update to bower/cdn?  Thanks.

Tested it out and it works for me. Thanks for the update. On a side note any chance of including the Azure Mobile Services client with this in bower?

Awesome.  I will update bower and cdn.
Also I searched bower for the MS client and I couldn't find it.  Is there another way to add the MS Client as a dependency?


Website Logo not appearing

Describe the bug
On clicking the Go button for number of posts on the home page, the page which appears does not show the Logo of the website
Expected behavior
I will remove this bug and Logo will start appearing on every page.
Screenshots

I would like to work on this issue as a part of GSSoC'21.
Note:

Do mention if your are working under GSSoC'21.
If you want to work on an issue, you should check if it has already been assigned to anyone. If the issue is free you can comment /assign to get the issue assigned to you.
If you are raising a new issue and want to work on it then also you should comment /assign under the issue to get it auto assigned.
Please refrain from adding labels to your issue/pull-request on your own. It is the job of the Project Admin and the Mentors to review your issue/pull-request and add labels accordingly.
According to the level of the issue, respective time will be allotted under which the task needs to be completed/resolved by the assigned person. If the issue is not resolved within the given time, it will be assigned to the next person. In case of any discrepancies, the decision of the maintainer will be final.

level - 0: 2 days
level - 1: 3 days
level - 2: 4 days
level - 3: 5 days

/assign


VLANBPFBypass: the data filed in ConfigMap not able to take array of int

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
the data filed in ConfigMap is map[string]string. Passing VLANBPFBypass values as an array of integers is not possible in ConfigMap. A validation error will happen. got "array", expected "string"
Cilium Version
1.11.1 9ce9549ce6 2022-02-10T18:14:35-08:00 go version go1.17.6 linux/amd64
Kernel Version
5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.6", GitCommit:"ad3338546da947756e8a88aa6822e9c11e7eac22", GitTreeState:"clean", BuildDate:"2022-04-14T08:49:13Z", GoVersion:"go1.17.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.8-gke.200", GitCommit:"87bd5277f85536686030dd1fd7d6e39776dd44d1", GitTreeState:"clean", BuildDate:"2022-03-17T20:36:33Z", GoVersion:"go1.16.14b7", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

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

Hi @shen-cloud , can you provide exact examples of CLI flags that you used and/or the content of this field in the ConfigMap?
Do you observe this when configuring the option as documented in https://docs.cilium.io/en/stable/configuration/vlan-802.1q/#vlan-802-1q ?
cc @kvaster

ConfigMap can't accept array. This setting should be a string of numbers separated by comma.


Use pip instead of setup.py

@tlvu Work for you? ;)

@tlvu Work for you? ;)

Perfectly :D

Note each time you force push, the PR will track it, see "Zeitsperre force-pushed the use_pip_docker branch from 0cdf250 to 7c363a1 8 minutes ago" so you can technically go back if you screw up as well.

Being able to revert is nice as well. KK, I'll work on these ingrained behaviours in the future.

Being able to revert is nice as well. KK, I'll work on these ingrained behaviours in the future.

Yeah, leaving trace of "why" you make a change not only save other people that was not in the "initial" review process but can also save your own future self because in french there is a saying "la mémoire est une faculté qui oublie".


Bug

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.01.29. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[ ] I've verified and I assure that I'm running youtube-dl 2017.01.29

Before submitting an issue make sure you have:

[ ] At least skimmed through README and most notably FAQ and BUGS sections
[ ] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl -v youtube-dl -x --audio-format mp3 https://www.youtube.com/playlist?list=PL8EE0ADDCF2C7D753
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'youtube-dl', '-x', '--audio-format', 'mp3', 'https://www.youtube.com/playlist?list=PL8EE0ADDCF2C7D753']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.01.29
[debug] Python version 3.6.0 - Linux-4.9.6-1-ARCH-x86_64-with-arch
[debug] exe versions: ffmpeg 3.2.2, ffprobe 3.2.2, rtmpdump 2.4
[debug] Proxy map: {}

...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
Explanation of your issue in arbitrary form goes here. Please make sure the description is worded well enough to be understood. Provide as much context and examples as possible.
If work on your issue requires account credentials please provide them or explain how one can obtain them.

$ youtube-dl -x --audio-format mp3 https://www.youtube.com/playlist?list=PL8EE0ADDCF2C7D753
[youtube:playlist] PL8EE0ADDCF2C7D753: Downloading webpage
[download] Downloading playlist: Iron man Soundtrack
[youtube:playlist] playlist Iron man Soundtrack: Downloading 19 videos
[download] Downloading video 1 of 19
[youtube] TwEl8NBx1VM: Downloading webpage
[youtube] TwEl8NBx1VM: Downloading video info webpage
[youtube] TwEl8NBx1VM: Extracting video information
[youtube] TwEl8NBx1VM: Downloading js player en_US-vflV3n15C
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1057, in _decrypt_signature
video_id, player_url, s
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 971, in _extract_signature_function
errnote='Download of %s failed' % player_url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 529, in _download_webpage
res = self._download_webpage_handle(url_or_request, video_id, note, errnote, fatal, encoding=encoding, data=data, headers=headers, query=query)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 436, in _download_webpage_handle
urlh = self._request_webpage(url_or_request, video_id, note, errnote, fatal, data=data, headers=headers, query=query)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 416, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2000, in urlopen
req = sanitized_Request(req)
File "/usr/local/bin/youtube-dl/youtube_dl/utils.py", line 525, in sanitized_Request
return compat_urllib_request.Request(sanitize_url(url), *args, **kwargs)
File "/usr/lib/python3.6/urllib/request.py", line 329, in init
self.full_url = url
File "/usr/lib/python3.6/urllib/request.py", line 355, in full_url
self._parse()
File "/usr/lib/python3.6/urllib/request.py", line 384, in _parse
raise ValueError("unknown url type: %r" % self.full_url)
ValueError: unknown url type: '/yts/jsbin/player-en_US-vflV3n15C/base.js'
(caused by ValueError("unknown url type: '/yts/jsbin/player-en_US-vflV3n15C/base.js'",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Duplicate of #11890


sql: don't try to add index in ALTER...ADD FK

PR: https://github.com/cockroachdb/cockroach/pull/16175

Duplicate of #1519


Failing Reference Tests

The following reference tests need to be repaired to begin interoperability testing with other clients:

[ ] ssz_generic tests need to be implemented

[ ] sanity -> blocks (super broken) needs BLS points don't match because it is not a valid key

[ ] sanity -> slots (super broken) needs BLS points don't match because it is not a valid key

[ ] shuffle setup method sanityProcessSlot needs to be renamed

[ ] ssz_static (super broken)

[ ] genesis -> validity (super broken)

[ ] one last pass for minimal configurations

I am working genesis -> validity

I'm on the BLS issues with sanity/*


Add -y to npx command for cspell

#83  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @acco and the rest of your teammates on  Graphite


Should it raise an exception when VA exceed the max range of the VA  when mmu off? what kind of the that exception?

Should it raise an exception when VA exceed the max range of the VA  when mmu off? and what kind of the that exception?
Let's think about a PAW(PA width) = 40, when it is in M mode and mstatus.mprv=0 (MMU off)
1） Can the software use a VA that exceed 40-bits, like VA0=0xAAAA_BBBB_CCCC？ Here the VA0 width is 48bits， exceed the max PA width(40bits).
2) if The answer is NO, then an exception should be raised, the what kind shold we use? access fault, selfdefined fault, or any other determined kind? The RV spec is better to make this clear.

The same case when pte.ppn[55:40] is not full-0, when the PAW=40, should an exception be raised? access fault or any other exception?

for SV48, a VA can be any address such that A[63:47] == either all1s, or
all 0s (so, sign extended from the VA MSB.
the PAW is completely independent from that; it can be larger or smaller.
if A[63:PAW] !=0, then you should get an illegal access fault.
(I don't recall if there are any weird cases that some other cause would be
reported offhand, and I'm too lazy to look)
It is the responsibility of the OS to ensure that the VA->PA mapping
defined by the page table never exceeds that PAW limit.
On Thu, Dec 5, 2024 at 11:17 PM rock-ifly @.***> wrote:

The same case when pte.ppn[55:40] is not full-0, when the PAW=40, should
an exception be raised? access fault or any other exception?
—
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-isa-manual/issues/1754#issuecomment-2522299633,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPXVJQOTUZD5DORDLT7MTD2EFFQFAVCNFSM6AAAAABTEAWWOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRSGI4TSNRTGM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

for SV48, a VA can be any address such that A[63:47] == either all1s, or all 0s (so, sign extended from the VA MSB. the PAW is completely independent from that; it can be larger or smaller. if A[63:PAW] !=0, then you should get an illegal access fault. (I don't recall if there are any weird cases that some other cause would be reported offhand, and I'm too lazy to look) It is the responsibility of the OS to ensure that the VA->PA mapping defined by the page table never exceeds that PAW limit.
…
On Thu, Dec 5, 2024 at 11:17 PM rock-ifly @.> wrote: The same case when pte.ppn[55:40] is not full-0, when the PAW=40, should an exception be raised? access fault or any other exception? — Reply to this email directly, view it on GitHub <#1754 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHPXVJQOTUZD5DORDLT7MTD2EFFQFAVCNFSM6AAAAABTEAWWOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRSGI4TSNRTGM . You are receiving this because you are subscribed to this thread.Message ID: @.>

OK， I see.

mmu on, for a Sv39/Sv48/Sv57, sign extenstoin is checked for VA
mmu on, OS should ensure the pte.ppn(PA) not exceed the PAW during the PTW process.
mmu off, OS should ensure the PA=VA not exceed the PAW

Why not make it clear in Ch12.3.2 vritual address translation prcess in the  RV spec, since the PAW is different for every implementation.


RDS Auth Token

SEP: /seps/accepted/shared/rds-sdk-1574/
internal id: 174915587

Changing priority based on feature matrix, this sep is marked as "may" for GA importance for new SDKs .

Is there somewhere I could track the progress of this? Currently building out an internal tool at my company where this is needed. I tried to look at SOTO but it does not seem like they have the feature either.

Moved to internal ticket 2173.


Roll Engine from 1424dfbe4d57 to f392053b1f2a (11 revisions)

https://github.com/flutter/engine/compare/1424dfbe4d57...f392053b1f2a
2021-01-16<EMAIL_ADDRESS>Unconditionaly enable some tracing on startup (flutter/engine#23729)
2021-01-16<EMAIL_ADDRESS>[fuchsia] Add missing static binding check. (flutter/engine#23731)
2021-01-16<EMAIL_ADDRESS>Roll Dart SDK from 0554c17398ef to 93a7e1189a8a (3 revisions) (flutter/engine#23735)
2021-01-16<EMAIL_ADDRESS>Roll Skia from d414e600b24b to 05e5446145a6 (4 revisions) (flutter/engine#23732)
2021-01-16<EMAIL_ADDRESS>Revert "Roll buildroot to 92a8d2eb7aad592068f808e39b8330fd2bce25e3, Clang to 12.0.0 (#23698)" (flutter/engine#23734)
2021-01-16<EMAIL_ADDRESS>Roll buildroot to 92a8d2eb7aad592068f808e39b8330fd2bce25e3, Clang to 12.0.0 (flutter/engine#23698)
2021-01-16<EMAIL_ADDRESS>Roll Skia from bfd330d08195 to d414e600b24b (5 revisions) (flutter/engine#23725)
2021-01-15<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from 058reL2R_... to -f95YWvck... (flutter/engine#23722)
2021-01-15<EMAIL_ADDRESS>Roll Skia from 9f079f7c0d16 to bfd330d08195 (2 revisions) (flutter/engine#23721)
2021-01-15<EMAIL_ADDRESS>Roll FreeType to 2.10.4 (flutter/engine#23666)
2021-01-15<EMAIL_ADDRESS>Skia can now build with 10.11 as the min deployment version (flutter/engine#23717)
Also rolling transitive DEPS:
fuchsia/sdk/core/mac-amd64 from 058reL2R_Ecn to -f95YWvckuWQ
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Gold has detected about 1 untriaged digest(s) on patchset 11.
View them at https://flutter-gold.skia.org/cl/github/74126

Gold has detected about 1 untriaged digest(s) on patchset 11.
View them at https://flutter-gold.skia.org/cl/github/74126


Modularization Question

For a basic app that would provide a set of tools to end users I am attempting to modularize a ui.navset_pill_list / ui.nav_panel layout. Essentially a sidbar with listed tools that provide informatics functionality.
When I attempt to modularize (using expressify) it seems the reactivity based on inputs defined is lost - I may not be understanding the expressify decorator 100%.
Without Modularization
The below does seem to work if I keep the tool1 function in the app module
Modularization attempt

I found Shiny Modules and the module decorator works perfectly for what I needed. I either missed it or it wasn't yet in the docs when I was looking for a solution.
https://shiny.posit.co/py/docs/modules.html


Spoon report and screenshots

Hi! nice test application, but what's about the Spoon report? Is it generated? Thanks

No, the Spoon library here is only used to take screenshots, not to run or generate test reports.
Cheers.

Do You know if is it possible to have spoon reports with cucumber?

I don't think so out of the box, because both cucumber and Spoon take control of how the tests batch is divided and executed


Remove monitor op from stonith-sbd

I removed    op monitor interval="15" timeout="15" from stonith-sbd.
With multiple SBD disks, in case one disk failed, the monitor operation will detect a failure and pacemaker will try to restart stonith-sbd resource on all node and the start will fail and stonith-sbd become inactive.
stonith-sbd    (stonith:external/sbd): Stopped
Removing above monitor operation, the system will log failure messages in logs but resource will not restart.
Oct 25 11:42:38 ora1 sbd[3034]:  warning: inquisitor_child: Servant /dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2019-11.sbd.local:ora1-sbd-2-lun-1 is outdated (age: 4)
Oct 25 11:42:38 ora1 sbd[3035]: /dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2019-11.sbd.local:ora1-sbd-2-lun-1:    error: header_get: Unable to read header from device 5
Oct 25 11:42:38 ora1 sbd[3035]: /dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2019-11.sbd.local:ora1-sbd-2-lun-1:    error: servant_md: No longer found a valid header on /dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2019-11.sbd.local:ora1-sbd-2-lun-1
Also, in our HAE documentation we don't advice customer to us op monitor for stonith-sbd resource:
https://documentation.suse.com/sle-ha/15-SP3/single-html/SLE-HA-administration/#book-administration
Thanks

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to review your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close


organicmaps: 2022.06.18-2 -> 2022.06.29-3

Description of changes

https://github.com/organicmaps/organicmaps/releases/tag/2022.06.29-3-android
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

[x] 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.

The hash changed after rebasing. Weird!

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1018


fix: typos

fix: typos

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