Want to use venv but it's stored in .gitignore as a file not directory?

Prerequisites

[x] Did you read FAQ section in readme.md?
[x] Did you test with the latest releases or commit ?
[x] Did you search for existing issues in Issues?

Description
I'm doing a fresh install of my operating system on a new drive and wanted to utilize Python3's venv to run PixivUtil2. While I could put the virtual environment anywhere, I noticed this:
https://github.com/Nandaka/PixivUtil2/blob/9faed1dd428b816b3ecac30b8806b638a6c2410b/.gitignore#L5
venv is in the ignore list as a file and not a directory? If that's the case, could I have clarification on what this ignore file actually is?
Steps to Reproduce
N/A
Expected behavior:
N/A
Actual behavior:
N/A
Log file:
N/A
Versions
N/A

Would docker be a preferred over venv in this case? :thinking:

hmm, I'm also not sure as it was added in https://github.com/Nandaka/PixivUtil2/pull/1015/files#diff-bc37d034bad564583790a46f19d807abfe519c5671395fd494d8cce506c42947 by @BassOfBass and I don't use virtual environment

.gitignore is only used to determine files/folders that should not be added when submitting a commit to the git repository.  If you are wanting to use venv for running PixivUtil2 locally you can ignore that file as it won't apply in that case.
With that said....  I have not tried to do that (yet).  I run this on Windows and use the exe builds (and make my own when testing code).

.gitignore is only used to determine files/folders that should not be added when submitting a commit to the git repository.

I am assuming when migrating from demjson to demjson3, python3's venv came in handy to make sure things worked right. What I would not understand is a file created named venv, but perhaps a folder where dependencies were installed named venv existed that they did not want uploaded, however that's not what the .gitignore is set up for in that case.

hmm, then it should be changed to venv/* instead?

Perhaps it should be removed altogether, because in probably the only circumstance it was needed was in the use case by BassOfBass, in which anyone could create a venv outside the PixivUtil2 folder and use the scripts in it just fine. I was merely confused as it was set up as a folder.

not really, the venv folder should not be included into the main repo, right? If you remove it, the venv folder might accidentally added if someone use git add .. It should not affect your local repo.

Yeah, virtual environments should not be committed and it's a good practice to have some safeguards against it. It's why the GitHub Python .gitignore includes it.

With that in mind the venv entry should probably be replaced with this (taken from the previously mentioned link) in order to try and avoid venv from being committed in error.
# Environments
.env
.venv
env/
venv/
ENV/
env.bak/
venv.bak/

not really, the venv folder should not be included into the main repo, right? If you remove it, the venv folder might accidentally added if someone use git add .. It should not affect your local repo.

The way it's currently setup, the .gitignore would only ignore venv if it was a file. As others are now pointing out, other .gitignores are properly safeguarding against these folders. I'd like to point out it has been lingering there for over a year without anyone noticing however, so I am doubting we, collectively as PixivUtil2 devs, are using venvs like this, lol.

Done and done.


SQL statement syntax

Creating new tags always results in the following error (both per web interface and REST API):
Error 1054 (42S22): Unknown column '$1' in 'field list'

Further investigation lead me to the following line:
https://github.com/ClusterCockpit/cc-backend/blob/280b16c11c1760e66f053fe24751712b69907b8e/internal/repository/tags.go#L62C25-L62C25
INSERT INTO tag (tag_type, tag_name) VALUES ($1, $2)

The sqlx package documentation says:
    MySQL uses the ? variant shown above
    PostgreSQL uses an enumerated $1, $2, etc bindvar syntax
    SQLite accepts both ? and $1 syntax
    Oracle uses a :name syntax

We are running cc-backend with MySQL (mariadb) and it seems the "$1" is passed verbatim to the server without inserting the value.
Grepping through the code shows, that all three syntaxes are used in the code.
I found the ":name" syntax in internal/repository/job.go, but still need to figure out if these statements are also problematic on our instance.

I used the squirrel query builder which automatically uses the correct syntax for placeholders. In my tests with a MariaDB test database this works now.
The :name Syntax is used in NamedJobInsert, this is used for example in the init-db job import. I tested it against MariaDB and it didn't cause any issues.

We will convert raw SQL statements into query builder on the go from now on.

One more thing. There was a Bug in the initial database initialization.
For the tags table the autoincrement was missing. I just added this now, but this is of course not the right way to do it. I have to add a new migration.
Question: How was your table initilalized?


Need standard development environment

As a developer
I need a standardized development environment for containerized microservice development
So that I can be sure that development work is being undertaken in consistent circumstances to avoid unnecessary troubleshooting
Details and assumptions

Environment should be set up to use Docker containers
Developers may be using a variety of host OSs
Regardless of OS, all developers will use VS Code as their IDE
Need a standardized list of dependencies as part of this environment

Acceptance criteria
Given [some initial state]
When [some event]
Then [some measurable outcome]

Per Professor Rofrano's note on Slack, we may consider this "done" in the form of the starter code / dockerfile provided with the initial repo


Increase text element padding in rectangle

As of now, the text padding inside the rectangle is way too small, so it's often necessary to manually add the spaces to achieve a more pleasant look.
Instead, we shall increase the padding, so that no manual "alignment" is not necessary.
Things to keep in mind:

it might be a regression -> double-check
do not create a breaking change for existing diagrams (after a manual redraw, like entering wysiwyg, it's likely fine)
don't forget about padding while editing (wysiwyg)
test different sizes & zoom levels

I will start looking into it. Thanks

I think this is related to https://github.com/excalidraw/excalidraw/issues/6179 or https://github.com/excalidraw/excalidraw/issues/4498 , not sure if it requires discussion or not but I guess we will have to revert some changes made there or maybe add a few that would compromise the ones made here. Not sure but these feel related.


New data science project with plagiarism free code and good accuracy

Create a new folder for new data science project then create your own named folder then upload your whole code data set used and all with one mark down file explaining everything

can I'll do this

I am interested to do this. Please assign it to me.

Go for it.

Could you pls assign this to me too? Or should I create a new issue with the specific project name that I want to work on?

@KartikeySharma either is fine

Hey @Jayshah6699 can you please assign me this issue ?

@Ashishkumarpanda kindly explain what you are going to do:)

I am removing everyone from this issue for now.
Do one thing instead,
make a separate issue or issues based on what do you want to contribute then I will assign the levels and other tags based on that particular issue and according to pull request.
It is for my convenience.
Thank you, everyone, who is interested in this project:)
@vaishnavi-1
@yashasvimisra2798
@KartikeySharma
@keshav340
@Ashishkumarpanda


get homeserver of a mxid

Is your feature request related to a problem? Please describe.
For example: You can host a simple matrix server and nothing else on "example.org". Then creds.homeserver == "https://example.org" and matrix IDs are like @user:example.org.
You might have a bigger setup and host lots of things on several servers all on your domain and, for easy management of a whole lot of servers, its subdomains, for example website at "example.edu" and email on "mail.example.edu". In this case you can host Matrix at "matrix.example.edu" but configure the server to still use usernames of the base domain. Then creds.homeserver == "https://matrix.example.edu" (since afaik nio can't resolve delegation?) but matrix IDs are still like @user:example.org.
Describe the solution you'd like
getHomeserver(@user:example.org) == 'example.org'
Additional context
https://github.com/KrazyKirby99999/simple-matrix-bot-lib/pull/93#discussion_r768139580

related: getHomeserver() should get the bot's own hs.
related: would be nice to have an easy method of adding everyone from a hs to the allow/block/admin/etc list.
To do that properly, one would need to bot.config.add_allowlist(f"@.*:{getHomeserver(mxid).replace('.', '\.')}"). Imo especially the regex part is easily overlooked and there might be more characters that should get escaped. Thus there could be helper methods for this? On the other hand I wouldn't want to overload the config class with a million presets.


feat: Add support for omitting empty and zero values in validation (including nil pointer and empty content of pointer)

Fixes Or Enhances
Add the omitzero Tag:

It allows you to ignore the subsequent validations if the value of a field is empty
If the field is a pointer and the pointer is nil, ignore the subsequent validations
If the field is a pointer and the pointer is not nil, but the content value of the pointer is zero, the subsequent validations will be ignored

Make sure that you've checked the boxes below before you submit PR:

[x] Tests exist or have been written that cover this particular change.

@go-playground/validator-maintainers

coverage: 74.319% (+0.03%) from 74.291%
when pulling 835464d2710f195c6f642025bbe5b30c47a29a3b on zeewell:feature/omitzero
into a947377040f8ebaee09f20d09a745ec369396793 on go-playground:master.

Fixes #249 #485 #698 #849


Combine several existing pages into a new account management page

Currently, we have many different pages about signing up/deleting / and changing your account plan, and resetting username and password:

https://sendgrid.com/docs/Classroom/Basics/Account/how_do_i_add_more_emails_to_my_account.html
https://sendgrid.com/docs/Classroom/Basics/Account/account_sign_up_faq.html
https://sendgrid.com/docs/Classroom/Basics/Account/how_can_i_cancel_my_account.html
https://sendgrid.com/docs/Classroom/Troubleshooting/dont_know_your_username.html
https://sendgrid.com/docs/Classroom/Troubleshooting/Account_Administration/dont_know_your_username.html
https://sendgrid.com/docs/Classroom/Troubleshooting/Account_Administration/recovering_your_username.html
https://sendgrid.com/docs/Classroom/Basics/Account/resetting_your_password_without_breaking_current_integrations.html
https://sendgrid.com/docs/Classroom/Basics/Account/resetting_your_password_as_a_teammate.html

The to do:
Create a new page that has no less than these tasks:

Creating a SendGrid account
Deleting your SendGrid account
Changing your SendGrid account plan
Resetting your account username
Resetting your account password
Additional resources - these should include a link to whitelabeling and 2fa

delete the pages listed above and redirect them to your new page, which should be in User Guide>Settings

I'm gonna take a stab!

Got this one!

you da best @hmbrown64  :)

After discussion on #2709, I have an additional to do to add onto this item - since we updated password resets to happen through SendGrid instead of letting integrations handle it, these integrations pages also need to redirect to this new page with a note at the bottom of the password reset section, something like:
{% info %}
You can also reset your password here if you're using SendGrid through an integration like AWS, Azure, IBM Cloud Marketplace, OpenShift, Heroku, AppDirect, or SoftLayer.
{% endinfo %}
The files that need deleted and redirected here are these:

Heroku Users - Find your SendGrid Credentials
How to change password when integrated via AppDirect
How to change the password for your SendGrid account via SoftLayer
How to change the password for your SendGrid add-on via Azure
How to change the password for your SendGrid add-on via OpenShift
How to change the password for your SendGrid add-on via the IBM Cloud Marketplace

I would like to do this. Is this available?

@hmbrown64 are you still planning to work on this?

@ksigler7 Yes I am!

Creating a new issue that captures the current state of this documentation and the additional updates that need to be made.


FIX error "Cannot find name 'HTMLStencilElement'"

Pull request checklist
Please check if your PR fulfills the following requirements:

[X] Tests for the changes have been added (for bug fixes / features)
[X] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[X] Build (npm run build) was run locally and any changes were pushed
[X] Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

(This fixes an issue)
Please check the type of change your PR introduces:

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
When you are building a Typescript project in Vue it shows the following message: "Cannot find name 'HTMLStencilElement'"
This fixes the issue
Issue Number: N/A
What is the new behavior?
Two imports has been added

Does this introduce a breaking change?

[ ] Yes
[X] No

Other information
<!-- Any other information that is important to this PR such as screenshots of how the component looks

![ISSUE](https://user-images.githubusercontent.com/27731047/60743403-ce0d8e00-9f47-11e9-85dc-2d4e9180b4a2.png)

I think #18701 does the same as in these changes. out of curiousity, didn't you have ionicons issues?

Yes, but I fixed it by downloading an earlier version of Ionic Icons; forcing its use. I also had problems with Ionic PWA Elements https://github.com/ionic-team/pwa-elements/pull/32

Closing in favor of #18701


package.json dependencies and devDependencies

Your question.

Can we split dependencies into dependencies and devDependencies?

The codebase on this repo has been moved to the main Apache Superset repo, and consequently the repo is in the process of being archived. See the Superset Improvement Proposal for details: https://github.com/apache/superset/issues/13013 . While all currently open issues and PRs will be closed, we encourage you to reopen this issue on the main repo if it is still relevant.


add hover effect to cursor pointer

updated the hover effect on download button

Website deploy preview link - https://deploy-preview-207--drifty.netlify.app/

@RyanRaushan I am out of station for a week. After I return home, I shall be a bit busy but once I get free, I shall review it.


[Tables] Release prep

Removes a debug logging statement
Cleans up some Py27 unicode references from the samples

/azp run python - tables - tests


Split CLI: fowld and fowl

Start with some README / documentation changes -- ultimately this will split the CLI into two programs, fowld and fowl.

Thank you for pinging me. Like I wrote, I will unfortunately probably not have much time to participate too actively in the near future, but I will be happy if you will be so kind and keep me in the loop if possible. Either way, it's great to see some progress again!

Yeah, trying it out for Pear-On -- do you know if there's a migration script etc?

I found this [1], it doesn't seem to be actively maintained nowadays but
the author is one of Soucehut staff which is why I think it might be a
good candidate for trying out. And also maybe this [2], which however
also doesn't seem to get much attention now. You can find a third
similar project mentioned at the bottom of the latter's README.

(Don't have a lot of PRs or Issues on this repo, but would love to give this a go as a test-migration....)

Yes, that's exactly why I thought that if you were ever to move it, now
would be the best time.
[1] https://sr.ht/~emersion/gh2srht/
[2] https://git.sr.ht/~jman/github-migrate-tool

Great, thanks!
Maybe I'll wait until DDoS is "definitely over" before I bug any srht staff ;) but I would like to move e.g. https://github.com/meejah/txtorcon "somewhere else" too (but it has enough ticket / PR history that I'd like to properly migrate it ideally).

but I would like to move e.g. https://github.com/meejah/txtorcon "somewhere else" too (but it has enough ticket / PR history that I'd like to properly migrate it ideally).

Well, that's why it's a good practice to use commit messages properly
;-) (although of course those will not hold the discussion/PR history
either).
I'm actually not sure how old PRs would be migrated -- other than
re-posting them all as patch series' on the mailing list. However, it
seems that the only ones that are currently open are authored by
yourself so you can just push them into respective branches on the new
remote without having to worry about write priviliges or asking the
authors to send further versions via email as series'. Well, actually,
you could probably also handle such PRs as "native" git PRs.

Would be great to hear any feedback (things that don't work, documentation that's still wrong ;) as tickets or whatever is appropriate.
Thanks!

Are you keeping the outdated protocol.rst for reference or can it be
removed?

How about this
diff --git a/src/fowl/cli.py b/src/fowl/cli.py
index ece5ad5..08ea908 100644
--- a/src/fowl/cli.py
+++ b/src/fowl/cli.py
@@ -92,7 +92,7 @@ def fowld(ctx, ip_privacy, mailbox, debug):
     "--local", "-L",
     multiple=True,
     help="Listen locally, connect remotely (accepted multiple times)",
-    metavar="listen-port[:connect-port]",
+    metavar="listen-port[:remote-port]",
 )
 @click.option(
     "--remote", "-R",

or maybe even better this
diff --git a/src/fowl/cli.py b/src/fowl/cli.py
index ece5ad5..9c50d3c 100644
--- a/src/fowl/cli.py
+++ b/src/fowl/cli.py
@@ -98,7 +98,7 @@ def fowld(ctx, ip_privacy, mailbox, debug):
     "--remote", "-R",
     multiple=True,
     help="Listen remotely, connect locally (accepted multiple times)",
-    metavar="listen-port[:local-port]",
+    metavar="listen-port[:connect-port]",
 )
 @click.option(
     "--allow",

? I find the current wording a bit confusing/inconsistent.

want to state that as a PR?

Pushed a commit to the typos PR. Also changed it for --allow.


Update Many Models documentation

This PR adds the documentation for following Many Models items:

model registration
model naming and tags
deployment
inference

@ssalgadodev
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Cargo-watch reacts to IsFile event, while it should not.

Hi, I'm using cargo-watch 8.1.1 (because 8.3.0 does not work for me). Recently, our build script, which uses cargo-watch under the hood, started looping indefinitely. After debugging it turned out, that when using std::fs::copy("a.txt", "b.txt") on macOS, a file system event IsFile is sometimes emitted on the source file ("a.txt"). The term "sometimes" is better explained here. Our build script is copying some files to target directory, which causes the sources to emit this event, which causes cargo-watch to re-run the whole operation again.
System: macOS Monterey (12.0.1), M1 pro

IsFile is a bit in the event mask, not an event type per se, similar to the IS_DIR bit in Linux. The event itself is probably a new possibly-undocumented one, so it doesn't appear in the fswatch handling, and passes through fsevents and notify to us.
This makes this bug platform version specific: it doesn't appear on Linux, and it doesn't appear on the old macbook air I have, which can't get upgraded to macOS 12.x
Fixing the issue is probably best done upstream in notify as by the time it gets handled here, it's already reduced to one of only five categories. However, cargo-watch 8.x uses watchexec 1.17, which uses notify 4.x... but it might be possible to have a patch release made for that release branch. Ask there.
In the meantime, you can likely work around the issue by using --watch-when-idle.

@passcod thanks for the explanation. I created an issue in the notify repo.
Regarding --watch-when-idle, unfortunately, it does not help. It still loops forever. Here are the logs with --why option. Please note that logs are interleaved with out build script logs:
out-2.txt
Is there anything I can do to help debugging it further?

Wow I hadn't realised you were embedding cargo watch in your program. That's... not supported. I can't stop you, but this is not something that I would ever recommend doing. Use the libraries directly if you need to.
Regardless:

if you use watchexec with --print-events (like --why) and -p -1 (hidden testing flag, will stop at first event), and fswatch, you should be able to catch this new event, and see what watchexec interprets it as.
notify from your latest log displays it as Some((none)), which we should be able to catch and ignore in here. That's probably a good workaround until the event is properly caught.

@passcod we are not embedding it. We have a build script which basically downloads fonts to a folder, then compiles some C binaries, etc., end then runs cargo-watch to watch for changes. Every time a change happens, we are just running cargo and also npm to build our JS app. I believe that this is just a normal usage of cargo-watch, wich does not stands in opposite to how this library is meant to be used. Am I correct?
Regarding the points that you mentioned:

That's a very handy info, thank you! I'll try to dig deeper and check how watch exec interprets it.
It would be amazing to ignore it and check out if it fixes things - do you think you'd be able to implement it?

Not really interested in debating what exactly counts as embedding. This isn't a gotcha or invalidating a support contract or whatever. Interactive use is the intended use. If your setup works for you, fine.

Sure. Can't guarantee when, though. Probably sometime next month? If you or anyone's interested in patching earlier, then start looking here.

Hi @passcod, did you find time to take a look into this issue? :)

No. Again, if you want it earlier, a PR is welcome.

@passcod I totally understand it. Unfortunately, I don't have enough of time to contribute here, as it requires pretty in-depth debugging. While I find cargo-watch to be the right solution in long-term, as it's written purely in Rust, until it works properly on modern MacOS and covers all .gitignore syntax, we made another project that is a in-place replacement for cargo-watch - we made it just in 1 evening, as it uses well-tested JS libs under the hood – for anyone facing this issue, you can find it here: https://github.com/enso-org/cargo-watch-plus (it works well on all Mac, Linux, and Windows, and supports all .gitignore syntax).

I'd say please don't use the name cargo-watch, but otherwise, best of luck

I'm using cargo- prefix because this way it registers as cargo command. I was trying to be very explicit that cargo-watch is the go to tool when it will work fine on MacOS. TBH, I hope I'd be able to delete this project sooner than later, as soon as cargo-watch will again work on my system.


kotlin version issue in Android side please fix it.

The Android Gradle plugin supports only Kotlin Gradle plugin version 1.3.0 and higher.
The following dependencies do not satisfy the required version:
project ':web_vuw' -> org.jetbrains.kotlin:kotlin-gradle-plugin:1.2.71

i am also facing same issue

i am also facing this can someone fix it


Request Money- Unable to cature image with camera button

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

Version Number: 1.3.91-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Launch the app and login
Tap the green fab > Request money > Scan
Tap the camera button to capture image

Expected Result:
Image captured by tapping the green camera button
Actual Result:
Button non functional and Camera error message displayed on native apps
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

https://github.com/Expensify/App/assets/78819774/e728f555-29d1-4c6c-8995-336457dc93e1

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

@ishpaul777 it's intentional to use new forwardRef pattern introduced in https://github.com/Expensify/App/pull/28411.
This should be correct change:

Ah, I see that option 1 is what I suggested

Thanks for the RCA @ishpaul777! @roryabraham do you have a preference whether we revert https://github.com/Expensify/App/pull/28813, or cherry pick a fix? (Either from @ikevin127 if available, or @ishpaul777). cc @mananjadhav as well

Indeed I introduced this regression and I am creating a PR  to fix it as we speak.

Thanks!

Created PR https://github.com/Expensify/App/pull/30397

This should be resolved now.

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@amyevans / @roryabraham] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@amyevans / @roryabraham] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@amyevans / @roryabraham] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[x] [@ikevin127] Determine if we should create a regression test for this bug.
[x] [@ikevin127] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ] [@NicMendonca] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

No need for any regression tests here.

Oh, whoops I spoke too soon, this was a regression so no separate payment should be issued for the fix


Can you add a license, please?

Thank you for your fantastic effort in developing and sharing your BM4D code on GitHub.
Could you kindly consider adding a license to your work? Doing so would significantly enhance the accessibility of your code, allowing more people to use it.
You may find this webpage informative on licenses: Choose a License. It offers detailed explanations and guidance on the subject.
Once again, thank you for your exceptional work and for considering this request.

I added a license.


Add 'OCaml from the very beginning' book & OCaml playground

What does this PR do?
This PR fixes EbookFoundation#7070 and adds another free OCaml book, 'OCaml from the very beginning' by John Whitington, also fixes #7073 and adds OCaml.org's playground.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Thanks, and welcome to free-programming-books!


BytesSpec is a flakey test

[info] BytesSpec:
[info] - requires non-null arrays
[info] - has a sane equals function
[info] - has a sane hashCode function *** FAILED ***
[info]   NoSuchElementException was thrown during property evaluation.
[info]     Message: next on empty iterator
[info]     Occurred when passed generated values (
[info]       wordLength = 0
[info]     )

this calls head but does not check it if is empty:
https://github.com/twitter/algebird/blob/develop/algebird-test/src/test/scala/com/twitter/algebird/BytesSpec.scala#L81
@jnievelt is that part of the change you added?

Not sure if you're thinking of my change in scalding.  Looks like this one hasn't changed in over a year.

Oh maybe you're thinking of #510

Ah I did break it!  Must have missed that it's head outside of any length check.


Update dependencies; Dart SDK version to 3.0.0.

Many packages that depends on cli_pkg can't be updated without update these dependencies and Dart SDK to 3.0.0+.

FYI: @nex3

Note that it's entirely possible to use cli_pkg with packages that require Dart 3 (as Dart Sass does); Dart 3 interprets an upper SDK bound of < 3.0.0 as allowing 3.x.

It's not possible to upgrade to http: ^1.1.0 (Dart 3) if your package is not updated

Packages that need this update:
https://pub.dev/packages/sass
https://pub.dev/packages/sass_builder
Eventually you will need this update, it's better for other packages to be soon.
Best regards

If we're going to require 3.0.0, I'd prefer to go all in and update the codebase to use Dart 3 features. Otherwise, I'd rather just update the dependency versions (and maybe explicitly expand the SDK constraint).

The current update passes dart analyze and dart format. I currently don't see any code that really needs to be migrated for specific Dart 3 feature, since it's already a null-safe package. The other main features introduced by Dart 3 are records and enhanced switch and if-case statements.
If you need any help migrating it, just ask.

Note that the only way to use sass and sass_builder now, for a Dart 3 project with the last version of common packages is to point to a patches fork:
https://github.com/gmpassos/sass_builder

I don't think your information is correct. I can locally update the http package to 1.0.0 without touching the SDK constraint and it works fine. Similarly, sass currently requires Dart 3 and is able to install its dependency on cli_pkg just fine. All its CI tests are passing.

Well, I made a simple dart web test here and I'm getting a dependencies resolution error:
dart create -t web test_sass

pubspec.yaml:
name: test_sass
description: Testing sass_builder dependencies.
version: 1.0.0

environment:
  sdk: '>=3.0.0 <4.0.0'

dependencies:
  path: ^1.8.0
  http: ^1.1.0

dev_dependencies:
  build_runner: ^2.4.2
  build_web_compilers: ^4.0.3
  sass_builder: ^2.2.1
  lints: ^2.1.1

dart pub get

Resolving dependencies... (1.3s)
Because sass_builder >=2.1.5 depends on sass ^1.55.0 which depends on http ^0.13.3, sass_builder >=2.1.5 requires http ^0.13.3.
So, because test_sass depends on both http ^1.1.0 and sass_builder ^2.2.1, version solving failed.

Same thing if testing only cli_pkg:
dart create -t web test_cli_pkg

pubspec.yaml
name: test_cli_pkg
description: Testing cli_pkg dependencies.
version: 1.0.0
# repository: https://github.com/my_org/my_repo

environment:
  sdk: '>=3.0.0 <4.0.0'

# Add regular dependencies here.
dependencies:
  path: ^1.8.0
  http: ^1.1.0

dev_dependencies:
  build_runner: ^2.4.2
  build_web_compilers: ^4.0.3
  cli_pkg: ^2.4.7
  lints: ^2.1.1

dart pub get

Resolving dependencies... (1.1s)
Because cli_pkg 2.4.7 depends on http ^0.13.0 and no versions of cli_pkg match >2.4.7 <3.0.0, cli_pkg ^2.4.7 requires http ^0.13.0.
So, because test_cli_pkg depends on both http ^1.1.0 and cli_pkg ^2.4.7, version solving failed.

Dart SDK version: 3.0.6 (stable) (Tue Jul 11 18:49:07 2023 +0000) on "macos_x64"

http: ^1.0.0

Min Dart SDK: 3.0

Those failures are only caused by incompatible http dependencies, not by the SDK constraint. Again, Dart 3 treats an SDK constraint with an upper bound of <3.0.0 as though its upper bound were <4.0.0. We can fix the issue you describe just by expanding the upper bound on the http constraint.

Those failures are only caused by incompatible http dependencies, not by the SDK constraint.

Yes, I agree.
The point is: do you wish to update the http dependency, which requires Dart 3+, without upgrading your own package to require Dart 3? I know that it's possible, but I don't know if this is the ideal.
Best regards.


Empty S&M_Cyclactions.ini and cycle action editor after "Apply change" function

It happened once in the past, and it happened again. Just after "apply change" in the cycle action editor, all cycle actions disappear from the cycle action editor (instantaneous disapearance), and S&M_Cyclactions.ini is mostly empty : there still is one or two actions, but all the rest has vanished. Quite a horror story scenario if you don't have backups (hopefully I have one) ^^.
Thank you

Here is the Cyclaction.ini. If you try to apply change to this file, all cycle action are deleted.
https://gofile.io/d/8suAjC

So I went thru the the txt file, trying to see if I have an action that goes beyond 8192 characters, but no, max is around 7500 characters.

Which action are you changing and what is the change? Given the symptoms it's probably a duplicate of #1439 (I don't have a fix for that ready yet).

Never mind, I found the issue. There is an additional limit on Windows: an entire section cannot reliably contain more than 65,535 bytes in the .ini. This second ceiling doesn't apply on macOS and Linux.
( The Main_Cyclactions section in the .ini above has 1,053,598 bytes.)

Argh... So what can be done at the user level ? Transform some actions in script with the template you posted earlier ? Is there any chance that this problem could have a solution ?

Is there any chance that this problem could have a solution?

I'm fixing the data loss issue. I'll also explore a few possible ways to avoid being hit by the limit, but I can't give a guarantee on that right now.

Thanks :) !!! I'll have to adapt for the time being.

I've seen your edit : Ok so if the limit is one million that would explain why the bug appears just now, not long before. This limit explains (I think) most of the issues I've been reporting here lately. I might have to rely on scripts more for now on, and try to reduce the cycle action count.
Thanks for your help, have a nice day ! :)

Any update on a possible lift of the 1 million bytes ceiling for the .ini file ? I regularly hit the limit, it has become very difficult to get anyhting done in a quick & safe way. I have to convert cycle actions into scripts, making them hard to tweak in the future, in order to implement anything. It's a really difficult situation in Reaper now. If there is any way to lift the ceiling I'd be very glad !

I removed the limit in the PR linked above. It won't be included in the next release (<IP_ADDRESS>) though, but the one after (probably 2.13).

Oh wow that's an amazing news :) ! Thanks Cfillion for this, big time !

Downloaded, and now problem totally solved :). I will avoid any SWS update until it's officially implemented then. thank you very very much Cfillion. I'll give a bit of money at the end of the month !
xxxxxxxx

Well... Actually I still end up with some Cycle action into parenthesis, actions that are fine otherwise, again it's the latest ID in the list (around 850). I have weird behaviors where, script or custom actions are not registered completely (ID = 0, or script not found in the action list), then with a Close and reopen Reaper, the script/custom/cycle action appear. But then, other cycle actions are put into parenthesis. It seems that new scripts put older cycle actions into parenthesis ? There seems to be a threshold that I'm crossing there ?Could be also that I'm above the global number of action that Reaper can scan ? I can't really count the global number, so cannot tell.

That's #1436, a separate issue where you're reaching REAPER's maximum action limit. Next update (not <IP_ADDRESS>) will show a warning message when cycle actions fails to be added when clicking on Apply. The limit itself is not on SWS side so I can't remove that one.
https://forum.cockos.com/showthread.php?t=243459

^^ Yes I got the two topics mixed up, sorry. Clear explanation, I'll have to clean the action list then !

& I'm so fucked, Reapack was installing everything, always, and I was not paying attention. facepalm

Disable "Install new packages when synchronizing" in Extensions > ReaPack > Manage repositories > Options. Then uninstall anything packages you're not using in Browse packages. That should free up a few hundred slots...

I'd just like to mention, after using this special version for a few weeks, that it works, but I get random crash when registering new actions. I'm above the 1 million w10 limit. and sometimes "apply change" in the cycle action editor bugs, resulting in a total reaper crash. It disapears, poof ^^. When I open a new session, all datas are fine, even the new one I was trying to save (the crash seems to wait until the very end of the "apply change" calculation). I think you could reproduce the crash by simply trying several "apply change" in a row with a very big Cycle (for one Cyclaction.ini  that goes above the 1 mo limit) action list (I'm at ID 880 and some cycle actions are super big).

Please send a "Dump file" of reaper.exe taken using the Windows task manager when it crashes.

will do

Sorry but I don't know how to do that : Reaper is not in the processes when it crashes.

Sorry but I don't know how to do that : Reaper is not in the processes when it crashes.

Does it show the "REAPER has stopped working" dialog? reaper.exe should still be in the process list while that dialog is still open.
Sometimes the crash dialogs may are disabled in Windows 10. Here's how to enable them: https://superuser.com/a/1349113.

Does it show the "REAPER has stopped working" dialog? reaper.exe should still be in the process list while that dialog is still open.
Sometimes the crash dialogs may are disabled in Windows 10. Here's how to enable them: https://superuser.com/a/1349113.

No Reaper disapears. Pouf. No dialog. Ok I'll follow the instructions on this page, and next time the Reaper bug happens & it crashes, I'll be READY :p.
xxxxxxxxxxx

No Reaper disapears. Pouf. No dialog. Ok I'll follow the instructions on this page, and next time the Reaper bug happens & it crashes, I'll be READY :p.
xxxxxxxxxxx


Cannot calculate spectra purity with msconvert 3.0.20059

Hi,
We recently noticed that our Philosopher pipeline is not able to calculate spectra purity for data sets labeled with TMT. We apply a method that is very similar to what P.D. does, but they call it Isolation Interference. The issue seems to only happen when the Thermo raw file is converted using msconvert 3.0.20059, the problem cannot be reproduced with previous versions. What we expect from the method is to have a score that goes from 0 to 100% purity for each PSM (or isolation interference), but with the latest msconvert version every spectra is either 0 or 1. I inspected the mzML files and I don't see any major differences with one exception, see below:

Apparently the latest version has an extra <userParam> tag inside the MS2 scans, right below the <precursor> tag. I don't know if that is the issue because my parser was able to read the spectra.
Regarding the purity score issue, everything else seems to be OK, including our TMT quantification, the values from the newest and the previous version seem to match.
I would appreciate if you could help us figuring out this.
Thanks

I can't help much without knowing what metadata the Philosopher purity calculation is using in its input. You can give me 2 mzML files, one working, one not, and I can tell you the differences between them. If the userParam ms level is the only difference then that's clearly a bug in Philosopher. (Although I suspect precursor intensity might have changed too because not too long ago we changed the way we were calculating that.)
But if you're the developer of that algorithm (or at least can debug the source code), you're in the best position to understand why it's only producing 0 or 1. Let me know if you notice something wrong/different with the mzML output which I could fix/explain.

The pipeline does not convert the files, we convert them manually and I did so using the Windows GUI. For each PSM we look at the MS1 scan where the precursor peak is and we then calculate the purity by looking around that peak for other peaks.
We are using the same version for comparing things, same processing steps, same database and same parameters, the only difference is the mzML file created by msconvert GUI 3.0.19 and 3.0.2.
I uploaded the files here for you to take a look.

For the most part, the userParam ms level and pwiz version are the only differences. However, the index on the newer file is corrupt after index 4121 because 4121 is missing the userParam ms level. I'd guess that's because the file was edited manually to remove it. Perhaps you did that while trying to test it? But if you didn't edit the file, I'll need the RAW file to try to reproduce this weird artifact.
Having a partially corrupt index actually led me to some other index handling bugs in pwiz, so that was a good thing to catch in any case. :)

Yes you are right, I removed to test, sorry for not noticing before sending to you.

Actually, let me clarify, I only removed that <userParam> that I highlighted above

OK in that case it's probably a bug in Philospher's mzML reader. It should just ignore those userParams and not let it affect the calculation.

To be clear, the binary data is identical between the two files.

Yes, that's why I was suspecting that the difference could be on the meta data or file structure

But if that's a bug on our reader, how come the previous versions of msconvert work without any issue? That tag is not present when converting using 3.0.19

BTW, we also tested on the same file but converted with version 3.0.7 and it also works fine but we can't find that version to download.

The previous versions didn't have that userParam. Zero or more userParams are allowed in that element. It should not affect your reader, but it's pretty clear that it is, right?

I'm not sure what versions you're quoting. The versions for those files are 3.0.20059 (newer) and 3.0.19127.

The file that can be found here says the following:
      <software id="pwiz" version="3.0.7680">
        <cvParam cvRef="MS" accession="MS:1000615" name="ProteoWizard software" value=""/>
      </software>

That's a pre-git version. But I'm not sure how that's related to the fact that the userParams are there in the mzML now, and they do not make the mzML invalid. Is it hard to fix your mzML reader so it ignores it?

not at all, I'm working on something now but at the same time wanted to confirm with you that this was the only difference. I'll try that and I'll let you know. Thanks for replying


direct-syscall feature doesn't report errors correctly

Linux syscalls do not set errno directly - libc is responsible for taking negative return values from the syscall return value and populating errno.
This means that anything depending on errno (like std::io::Error::last_os_error()) will not work if you're not using libc.
When using direct-syscall, libc is not used in the sys module - so any call to sys::* followed by a last_os_error will not report errors correctly. One example of this is when calling io_uring_setup https://github.com/tokio-rs/io-uring/blob/6c535d2ce8d05f7a5eb33a82d948e6eb7e19c6f7/src/lib.rs#L175-L182
Cargo.toml
[package]
name = "ringer"
version = "0.1.0"
edition = "2021"
[dependencies]
io-uring = { version = "0.5", features = ["direct-syscall"] }

src/main.rs
fn main() {
    io_uring::IoUring::new(u32::MAX).unwrap();
}

Output from cargo run:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 0, kind: Uncategorized, message: "Success" }', src/main.rs:2:38
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

If you remove the direct-syscall feature you instead get:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 22, kind: InvalidInput, message: "Invalid argument" }', src/main.rs:2:38
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

You can fix this by handling the conversion yourself, but an alternative is to move from sc to https://crates.io/crates/rustix which already does this conversion into its own io::Result type - e.g. https://docs.rs/rustix/latest/rustix/io_uring/fn.io_uring_enter.html returns a rustix::io::Result (which you can convert this into a std::io::Result with res.map_err(std::io::Error::from))

I see three places where this is handled incorrectly:
https://github.com/tokio-rs/io-uring/blob/6c535d2ce8d05f7a5eb33a82d948e6eb7e19c6f7/src/lib.rs#L175-L182
https://github.com/tokio-rs/io-uring/blob/6c535d2ce8d05f7a5eb33a82d948e6eb7e19c6f7/src/register.rs#L15-L20
https://github.com/tokio-rs/io-uring/blob/6c535d2ce8d05f7a5eb33a82d948e6eb7e19c6f7/src/submit.rs#L96-L110
The last one is interesting because it is trying to do the right thing, but I think it's subtly wrong - if a syscall returns EPERM (mapped to -1) then this code will incorrectly believe it's a libc return value and call last_os_error and probably get nonsense.
(fortunately io_uring_enter isn't documented to return EPERM so this is more a theoretical problem in this case)

You are right, I am actually known this problem. rustix is a pretty big dependency and I would rather avoid it. Also direct-syscall doesn't seem to be really used by anyone and I've been considering remove it in next release.

Ah! I'm currently starting to use it, and in fact looking at building on it to allow no_std - but if it's a maintenance burden then it's fair to remove.

If you use it, I would be happy to accept a PR for the fix. :D


Added new icons

Associated Issue: #
Summary of Changes

change 1
change 2

Pull Request Test Coverage Report for Build 992

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.143%

Totals

Change from base Build 937:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls


Add 'managedBy' label to rook-ceph-exporter metrics

Currently we add the 'managedBy' label to ceph metrics, similarly we need to add 'managedBy' label to ceph exporter metrics.

Tested the change on our daily cluster and relabelings details are added to the rook-ceph-exporter ServiceMonitor's endpoints spec (by rook).

/cherry-pick release-4.15


Capstone project: set up the kanban board

Hi :wave:
In this project we are a group of three people:

Team member 1: @mirouhml
Team member 2: @NasKhalil
Team member 3: @Sboursen

Please find a below-attached link to our project:
:point_right: Project link
Cheers,

Hi team👋,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉 🎉 🎉 🎉 🎉
Cheers and Happy coding!👏👏👏

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


games.com

hope everyone enjoys your games

Description of change

Pre-Merge Checklist

[x] Tests and/or benchmarks are included
[ ] Documentation is changed or added
[ ] Lint process passed (npm run lint)
[ ] Tests passed (npm run test)

hope you enjoy this game i been working really hard!!!


[Bug] --empty flag causes syntax errors when source CTE uses ref name as prefix

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
I am looking to use the --empty flag to do basic syntax/schema testing of DBT models in our project but I am running into an issue where references to the model name (i.e. as a column prefix) are broken due to the way in which the limit 0 is applied in a subquery without an alias.
Expected Behavior
I would expect that when the --empty flag is used, a table alias of the original model name is supplied after the empty subquery to preserve references to the model name. For example of desired behavior see example below in Steps To Reproduce
Steps To Reproduce
Running with DBT in any environment (Redshift for us) with package versions below
dbt-core==1.9.0
dbt-redshift==1.9.0

Given a DBT SQL model below (test_model.sql)
with previous_cte as (

    select 1 as col1, 2 as col2

),

my_cte as (

    select
          source_model.col1
        , previous_cte.col2
    from {{ ref('source_model') }}
    inner join previous_cte
        on source_model.col1 = previous_cte.col1

)

select *
from my_cte

Running dbt compile --select test_model --empty yields the following sql
with previous_cte as (

    select 1 as col1, 2 as col2

),

my_cte as (

    select
          source_model.col1
        , previous_cte.col2
    from (select * from "my_db"."my_schema"."source_model" where false limit 0)
    inner join previous_cte
        on source_model.col1 = previous_cte.col1

)

select *
from my_cte

When executed this SQL returns a syntax error:
ERROR: relation "source_model" does not exist

I would like for the --empty flag to also include a table alias after the subquery to preserve references. Example compiled SQL below:
with previous_cte as (

    select 1 as col1, 2 as col2

),

my_cte as (

    select
          source_model.col1
        , previous_cte.col2
    from (select * from "my_db"."my_schema"."source_model" where false limit 0) as source_model
    inner join previous_cte
        on source_model.col1 = previous_cte.col1

)

select *
from my_cte

Relevant log output
No response
Environment
- OS: macOS Sonoma 14.6
- Python: 3.11.10
- dbt: 1.9.0

Which database adapter are you using with dbt?
redshift
Additional Context
No response

Thanks for reaching out @sfangman !
I see what you are saying -- thanks you for such a nice write-up 🤩

I would like for the --empty flag to also include a table alias after the subquery to preserve references.

This is a totally reasonable ask!
But we'd also need to figure out how to handle the opposite case if someone does supply aliases like this:
    select
          source_model.col1
        , previous_cte.col2
    from {{ ref('source_model') }} as source_model
    inner join previous_cte
        on source_model.col1 = previous_cte.col1

In that case, we wouldn't want to double alias like this:
    select
          source_model.col1
        , previous_cte.col2
    from (select * from "my_db"."my_schema"."source_model" where false limit 0) as source_model as source_model
    inner join previous_cte
        on source_model.col1 = previous_cte.col1

Current known limitations
Similar to https://github.com/dbt-labs/dbt-snowflake/issues/1251, it is known current limitation of dbt unit tests that relation names within dbt models must be aliased if aliases are used within the join logic.
We have a small call-out within our "Before you begin" section of our documentation, and we'd be open to suggestions of how to word this better:

Table names must be aliased in order to unit test join logic.

Workaround in the meantime
Our recommendation in the meantime is to add aliases like this whenever the join logic needs them:
    select
          source_model.col1
        , previous_cte.col2
    from {{ ref('source_model') }} as source_model
    inner join previous_cte
        on source_model.col1 = previous_cte.col1

Hi @dbeatty10 - thanks for the quick response! This makes a ton of sense to me, we can go about updating aliases as a part of our project upgrade process.


Update release notes for NBUI

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

The version is already released, we just need to update RN


Changes pulled in from upstream pytorch

This change is done as part of the bigger activity to - move pytorch to use hipify-torch module.
It will involve to parts

PR into pytorch to update into hipify-torch
PR into hipify-torch, adding any changes from pytorch hipify script. And PR address this.


Successful manual runs from a branch can result in lots of failed error messages

Awaiting a clear way to reproduce, but:
After starting a run an a development branch:

The run completes successfully and shows a success message
Several (10+) "Deployment finished with errors" messages all show below

We believe this may have been fixed as of significant changes to run logs / UI storage code. @lewish to check with affected customer.


Fix the usage of a virtual clock in backoff handler

backoff.NewExponentialBackOff() initializes an ExponentialBackOff, including grabbing
the current time from the system clock.  During tests when we override the clock, this
effectively puts us back in time to 1970.
Eventually all this adhoc retry logic will be centralized when the Transport system
is completed (which handles it properly already)

I know, right?


dlib

face_recognition version:
Python version:
Operating System:

Description
run the program,and tell me can't find dlib.
so,i run the commond pip install dlib,but installed failed
What I Did
pip install dlib
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

Building wheels for collected packages: dlib
Building wheel for dlib (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for dlib (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [78 lines of output]
running bdist_wheel
running build
running build_ext
:125: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.

face_recognition version:

Python version:

Operating System:

Description
run the program,and tell me can't find dlib. so,i run the commond pip install dlib,but installed failed
What I Did
pip install dlib
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

Building wheels for collected packages: dlib Building wheel for dlib (pyproject.toml) ... error error: subprocess-exited-with-error
× Building wheel for dlib (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [78 lines of output] running bdist_wheel running build running build_ext :125: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.

Check and see if you have a cxx compiler and cmake on your computer, since dlib must be compiled.

PS C:\Users\SHAIK  SHABEENA> pip install cmake
Requirement already satisfied: cmake in c:\users\shaik  shabeena\appdata\local\programs\python\python311\lib\site-packages (3.29.2)
PS C:\Users\SHAIK  SHABEENA>
PS C:\Users\SHAIK  SHABEENA> pip install dlib
Collecting dlib
Using cached dlib-19.24.4.tar.gz (3.3 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: dlib
Building wheel for dlib (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for dlib (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [11 lines of output]
running bdist_wheel
running build
running build_ext
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in run_code
File "C:\Users\SHAIK  SHABEENA\AppData\Local\Programs\Python\Python311\Scripts\cmake.exe_main.py", line 4, in
ModuleNotFoundError: No module named 'cmake'
  ERROR: CMake must be installed to build dlib

  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for dlib
Failed to build dlib
ERROR: Could not build wheels for dlib, which is required to install pyproject.toml-based projects
PS C:\Users\SHAIK  SHABEENA>
i am getting this error how to fix this could you please help me in this regard its very urgent

Simply download the whl file and install it manually


[Question] Is delta table partition column serialization format mandatory?

I found the partition column serialization format is recommended in delta protocol. I'm trying to understand if the format is mandatory for delta table? For example, if I serialized a Date partition column with format "MM/dd/yyyy" rahter than the recommended "yyyy-MM-dd", would it be considered as an invalid delta table (for now and in future)?

Hi @dandandanliu915 - where does it say in the protocol that this partition value serialization format is recommended? My interpretation is that the protocol states pretty clearly that partition date values must be serialized in the format "yyyy-MM-dd".
https://github.com/delta-io/delta/blob/master/PROTOCOL.md#partition-value-serialization
Let me know! Thanks!


readme.md link to youtube is broken

Refers to https://cortx.link/XGVHVq which doesn't work.
Should refer to https://www.youtube.com/playlist?list=PLOLUar3XSz2M_w5OxQLNDBTpSrsGbjDWr

Thanks @kaplanlior for fixing this.
@novium258 could you fix that on your end?
@kaplanlior I love the feedback on the documentation. If you see anything that needs improvements don't hesitate to let us know. + @johnbent as an FYI.

Thanks!  @Saumya-Sunder fixed this!


Movement Speed in 1.3.6 is faster than it should be

Describe the bug
Party moves a lot faster than they should. Compared speeds with a new game started with 1.3.6 installed and one new game without toybox installed. In 1.3.6 movement is a lot faster than it should be. Did not have this problem in <IP_ADDRESS>
To Reproduce
Steps to reproduce the behavior:

Install Toybox 1.3.6
Load any save or create a new game.
Observe the characters speed, compare it to the speed in vanilla WOTR
See error

Settings
Please attach your settings.xml file from the mod folder
Version Info:

ToyBox Version: 1.3.6
OS: Windows 10
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Can you attach your settings file in which you see this problem please?


Remove em() Sass mixin

What
Remove em() Sass mixin
Why
This was deprecated for a while now and it's no longer used in GOV.UK applications.
Fixes https://github.com/alphagov/govuk_publishing_components/issues/2035
Visual Changes
No visual changes

Looks good. If this isn't in use anymore does this still count as a breaking change?

It is technically a breaking change and I haven't looked anywhere outside our core frontend apps so I thought we could bundle it with others in the pipeline.

It is technically a breaking change and I haven't looked anywhere outside our core frontend apps so I thought we could bundle it with others in the pipeline.

Good shout. I've just noticed it's also a breaking change because static explicitly imports this file: https://github.com/alphagov/static/blob/main/app/assets/stylesheets/header-footer-only.scss#L6

Looks good. If this isn't in use anymore does this still count as a breaking change?
(also need to update the changelog)

It oddly imports it without using it.. 🤷
Will remove it from static beforehand to make dependabot happy.


Reply on merge command parse failure

Makes hoff give feedback when an invalid command is issued.

Thanks for all the feedback! :)

@OpsBotPrime merge

Pull request approved for merge by @RileyApeldoorn, rebasing now.

Rebased as 0bd569a825edea47cd4c076a67db26f8881e132a, waiting for CI …


update svd parser

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

Converted to draft

Problems (updatable):
1.
[ERROR svd2rust] In device nrf51
Caused by:
    0: In peripheral `WDT`
    1: In register `RR[%s]`
    2: Parsing field #0
    3: In field `RR`
    4: Value<PHONE_NUMBER> out of range 0..0

@burrbull I updated the svd file for Espressif/ESP32, so now should be ok. (I tested it with branch svd_new, but it also passed before the updates, so I might have done something wrong.)

I still see empty <registers /> in the file. Just remove them.

cc @therealprof

Why are we removing the Spansion tests again?

Why are we removing the Spansion tests again?

Spansion SVDs are same as Fujitsu's ones, but more old versions of them with lot of bugs, that are fixed in newer.
So I've left only not doubled files.


Windows portability fixes

This is an umbrella issue for "make scopehal compile and work under Windows".

@nshcat Please close this issue once you believe the Windows build has reached feature parity with the Linux build.

libscopehal builds in windows, and has feature-parity with the linux build. Any bugs or differences in behaviour between the different platforms will be tracked in separate issues.


Upgrade parboiled dependency to 2.1.1

This allows us to get away from the version hacks in the build surrounding shapelss 2.2.5

We're about to have eviction problems again, because 2.3.0 is in its fourth RC.  But this should put the cross versioning mismatch behind us for good, and hooray for that.


Finesse resolution of coincident insertions / edits.

          It is apparent (and this has been the case before work was started on this ticket) that coincident insertions and edits that are move destinations haven't been resolved taking the source of the move into account for trivial edit resolution - instead just the left and right contributions are used. That two-way resolution is fine when coincident insertions and edits are standalone, but is lacking when they are coincident move destinations.

          Regarding that last point about coincident entries being represented in unresolved form, perhaps we could represent then as insertion versus insertion conflicts or edit versus edit conflicts in the implementation of `MergeResultDetectingMotion`?

          If so, that would allow three-way resolution to be done in [`evaluateSpeculativeSourcesAndDestinations.evaluateSpeculativeSourcesAndDestinations`](https://github.com/sageserpent-open/kineticMerge/blob/d1973bb25fbbea61ba6f8359f04a7ad42b74ec55/src/main/scala/com/sageserpent/kineticmerge/core/MoveDestinationsReport.scala#L124).

          I'm not sure whether to add a pair of substitutions for the left- and right-side contribution to the three-way resolution there, and then to add additional pairs of substitutions referring to the two-way resolution for all the speculative coincident merge destinations that didn't turn out to be moves after all?

Originally posted by @sageserpent-open in https://github.com/sageserpent-open/kineticMerge/issues/90#issuecomment-2466247827

In short, when a coincident insertion or edit is standalone, resolution should be two-way (and it is in the existing code).
When a coincident insertion or edit is a move destination, resolution should be three-way.

Commit b35273138e885f7989a7bad19b952956b318c87a delivers most of what was proposed in the previous comment; what is missing is the revised approach to resolution.
Nevertheless, CodeMotionAnalysisExtensionTest.coincidences passes now, so this approach has paid off.

Merged to main in Git commit SHA: f79df93eed13c8e80d345f8ef820abfab96ff1af.

This went out tin Release 1.4.0.


RESTEASY-2161 remove @NoJackson annotation

remove @NoJackson annotation (because jettison is removed)
clean Jettison related tests
update documents

Hey @liweinan,
Good job. I just have a couple of comments.
-Ron

@ronsigal Thanks for reviewing Ron! I'll remove the outdated parts of doc after coming back from holiday :D

Thanks, @liweinan. Have a good holiday.

@ronsigal This branch needs rebase, and I have created a new PR for it(in case I mass things up): https://github.com/resteasy/Resteasy/pull/1878


Rely on jackson.version from common pom

This was already setup on earlier release branches, not sure what happened in the merge that it didn't make it into 4.1.x and master...


fix: resolve badge hydration error

Fix React hydration error in badge display by:

Replace table layout with flex container
Add explicit image dimensions
Configure Next.js image optimization
Maintain side-by-side badge display

Changes have been tested in both development and production environments, with no hydration errors present.
Link to Devin run: https://app.devin.ai/sessions/c169347707424fc5a1af9e33c3c78438

📝 Changed routes:

/

(view full size)

Commit 08b843a6acd259b5fd1542e27dff601436df778d (https://mdxe-js-285bkyldb.dev.driv.ly).


💡 [FEATURE] -

Idea Contribution

[X] I have read all the feature request issues.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Explain feature request
I would like to add cheatsheets for DSA
Explain your solution
No response
Any alternative approaches/features
No response
Additional Context
No response

i would like to work on this project, please assign this to me

I assigned it to you. You can start working on it


EC-144: Add peers limit

as previously
I have issue with connecting to peers because app is considering peers from list that are not yet conneted as working connections and even if I am connected to only 1 peer and limit is set to 5 I am getting
19:19:19.483 i.i.e.network.PeerManagerActor - Maximum number of connected peers reached. Not connecting to enode:

for 4 peers out of 9 on the list from application.conf


Fresh Install | UI is a Mess

I just stumbled on your amazing software and installed it within a subfolder of my website. As I navigated to it, I found the Dashboard to be a mess. I searched around for similar problems, but found none. Any ideas or a link to point me in the right direction?

It looks like something wasn't loaded correctly. Please check your browser's console for errors. It might be necessary to use a local server to make it work.

Just FYI, I noticed I originally downloaded AdminLTE2.zip from https://almsaeedstudio.com/themes/AdminLTE/documentation/index.html https://almsaeedstudio.com/themes/AdminLTE/documentation/index.html
I went back and looked around some more and decided to redownload from https://almsaeedstudio.com https://almsaeedstudio.com/ and found that it was version AdminLTE-2.0.4.zip
I uploaded the zip to my server, uncompressed it…went to the subfolder and still the same result. Refreshed, cleared cookies, etc…still a mess. I decided to test it in Firefox…WORKS PERFECT! Chrome? PERFECT!!! It’s just Safari Version 8.0.5 (10600.5.17) that is giving me fits. My computer model is iMac (27-inch, Late 2013), 3.5 GHz Intel Core i7, 32 GB 1600 MHz DDR3
If I can help debug this, please let me know.
The errors being reported are:
Failed to load resource: the server responded with a status of 404 (Not Found)
/dash/bootstrap/js/bootstrap.min.js (I looked and it IS there)
Failed to load resource: the server responded with a status of 404 (Not Found)
/dash/bootstrap/css/bootstrap.min.css (I looked and it IS there)
The warnings being reported are:
Unexpected CSS token: : font-awesome.min.css:4
Unexpected CSS token: : 10AdminLTE.min.css:7
Invalid CSS property declaration at: * blue.css:6
Invalid CSS property declaration at: / jquery-jvectormap-1.2.2.css:22
Invalid CSS property declaration at: * datepicker3.css:780
Invalid CSS property declaration at: * datepicker3.css:781
On Apr 22, 2015, at 12:40 PM, Abdullah Almsaeed<EMAIL_ADDRESS>wrote:
It looks like something wasn't loaded correctly. Please check your browser's console for errors. It might be necessary to use a local server to make it work.
—
Reply to this email directly or view it on GitHub https://github.com/almasaeed2010/AdminLTE/issues/359#issuecomment-95279763.

This is odd. I downloaded the version you are using and it worked fine on Safari 8.0.5 (10600.5.17). Are you using MAMP, Vagarant or a different server? It should've worked out of the box simply by opening the index.html file. Try opening the starter.html file by double-clicking it. If it works fine on Safari, then the server you are using is somehow preventing these resources from loading. I'd appreciate it if you get back to me with the results.

Hi,
Thanks for this really awsome theme !
I have the same problem here, on a local install in Laravel5 (runing with artisan serve). Got the same errors in Firefox but not in Chrome.

@jadubbz any updates?
@tiipiik I am using the template with Laravel 5 and Homestead and at first I faced a few problems. Here is how I solved them:

Make sure that all of the AdminLTE assets are available and accessible by placing them in the public directory and checking that all file permissions are set properly.
Check your html (or blade) and make sure that all the resources are linked to correctly. Some servers require that files are case sensitive, so app.js does not equal App.js.

I am not sure why firefox would give such an error. "dead object"? What do you think that means?

@almasaeed2010 Don't really know. I just find this => https://blog.mozilla.org/addons/2012/09/12/what-does-cant-access-dead-object-mean/
So maybe your code is not responsible of this issue, but a Firefox extension is (or maybe is) !
I'll try to deactivate estensions one after the other and tell you if it changes something.

I tested FF again just to make sure if any errors show up on my end but I didn't get anything. I then installed it on homestead but it also worked fine there. No errors at all. Please let me know if you find the issue that's causing this in your end so we address it here in case it is an error from our end.

Well, this is quite strange.
After I deactivate all extensions and then reactivate all one by one, errors just "disappear". I also renamed dist/css/AdminLTE.min.css to dist/css/admin-lte.min.css, but it seems not to change anything, as I rename files like originals and errors are still not here.
If other people who have the same issue can try to deactivate all extensions and tell if it make the same as for me it would be interesting !

I apologize…my email at work is not working correctly. Just checking this at home and found these messages. I’ll look at these when I get a chance this evening and get back with you. I apologize.
Jacob
On Apr 23, 2015, at 9:43 AM, Yohann Decharraud<EMAIL_ADDRESS>wrote:
Well, this is quite strange.
After I deactivate all extensions and then reactivate all one by one, errors just "disappear". I also renamed dist/css/AdminLTE.min.css to dist/css/admin-lte.min.css, but it seems not to change anything, as I rename files like originals and errors are still not here.
If other people who have the same issue can try to deactivate all extensions and tell if it make the same as for me it would be interesting !
—
Reply to this email directly or view it on GitHub https://github.com/almasaeed2010/AdminLTE/issues/359#issuecomment-95609308.

I apologize…my email at work is not working correctly. Just checking this at home and found these messages. I’ll look at these when I get a chance this evening and get back with you. I apologize.
Jacob
On Apr 23, 2015, at 4:47 AM, Yohann Decharraud<EMAIL_ADDRESS>wrote:
Hi,
Thanks for this really awsome theme !
I have the same problem here, on a local install in Laravel5 (runing with artisan serve). Got the same errors in Firefox but not in Chrome.
https://cloud.githubusercontent.com/assets/3844253/7294513/591a78ae-e9ae-11e4-9295-f1d2527ef34b.png
—
Reply to this email directly or view it on GitHub https://github.com/almasaeed2010/AdminLTE/issues/359#issuecomment-95514957.

Tested on all browsers but couldn't replicate the issue yet. If there is no progress on this, I will have to close the post. Thank you.


NullPointerException when reading file from sftp

I'm trying to read a csv file from sftp server and convert to dataframe.
The file is in /ppreports/outgoing/MY.CSV. I can see it when logging in with a GUI.
val df = spark.read
            .format("com.springml.spark.sftp")
            .option("host", HOST)
            .option("username", USER)
            .option("password", PASSWORD)
            .option("fileType", "csv")
            .option("inferSchema", "false")
            .option("createDF", "false")
            .load("/ppreports/outgoing/MY.CSV")

I get
java.lang.NullPointerException
	at org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:453)
	at org.apache.spark.sql.DataFrameReader.loadV1Source(DataFrameReader.scala:291)
	at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:277)
	at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:212)

If I try to read non-existing file:
val df = spark.read
            .format("com.springml.spark.sftp")
            .option("host", HOST)
            .option("username", USER)
            .option("password", PASSWORD)
            .option("fileType", "csv")
            .option("inferSchema", "false")
            .option("createDF", "false")
            .load("/ppreports/outgoing/non-existing.CSV")

Then I'll predictable get file not found:
2: No such file or directory
	at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2833)
	at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2185)
	at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2202)
	at com.jcraft.jsch.ChannelSftp.get(ChannelSftp.java:914)
	at com.jcraft.jsch.ChannelSftp.get(ChannelSftp.java:874)
	at com.springml.sftp.client.SFTPClient.copyInternal(SFTPClient.java:168)
	at com.springml.sftp.client.SFTPClient.copy(SFTPClient.java:74)
	at com.springml.spark.sftp.DefaultSource.copy(DefaultSource.scala:212)
	at com.springml.spark.sftp.DefaultSource.createRelation(DefaultSource.scala:80)
	at com.springml.spark.sftp.DefaultSource.createRelation(DefaultSource.scala:41)
	at org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:346)
	at org.apache.spark.sql.DataFrameReader.loadV1Source(DataFrameReader.scala:291)
	at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:277)
	at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:212)

Thus, I conclude that file is there and spark-sftp finds it, but fails to download.
What should I do?

@sslavian812 - What content is present in the file? Can you check whether it is valid CSV file?
Also try to use the latest spark-sftp connector as we solved similar issue like this

whether it is valid CSV file?
It's a text file, a regular csv. I can download it with curl and open on local machine.

latest spark-sftp
Upgraded from 1.3 to  com.springml:spark-sftp_2.11:1.1.5, didn't help.

Yes this is a issue, Even i'm facing it too..
java.lang.NullPointerException --> When reading a exsisting fie and even upgrading - com.springml:spark-sftp_2.11:1.1.5 didnt helped
Let me know if any other option can be implemented

Can you provide a sample of the file to be tested?

You can use any file either csv or txt. How it does perform is It is trying to perform two things at a same time

Copy the file from sftp to temp location in dbfs
Reading from dbfs

thats why it is failing which is a bug.
If u do a try catch block
try(read the file but do not create dataframe){
copy the data in the dbfs
}catch(once its copied u can load the file to dataframe)
this is a temprory solution but this is a bug

@AJAnujsharma Can you please provide the code snippet that you used to sftp from databricks. Not sure I get what you are doing in your catch block. Thanks in advance.

@AJAnujsharma Can you please provide the code snippet that you used to sftp from databricks. Not sure I get what you are doing in your catch block. Thanks in advance.
This is working for me. sftp server

try/except is the workaround
try:
df = (spark
.read
.format("com.springml.spark.sftp")
.option("host", "test.rebex.net")
.option("username", sftp_user)
.option("password", sftp_password)
.option("fileType", "txt")
.option("tempLocation", "/dbfs/tmp/")
.load("/pub/example/readme.txt"))
except:
df = (spark
.read
.format("com.springml.spark.sftp")
.option("host", "test.rebex.net")
.option("username", sftp_user)
.option("password", sftp_password)
.option("fileType", "txt")
.option("tempLocation", "/tmp/")
.load("/pub/example/readme.txt"))

@sauerch91  were you able to write to a sftp server? If so can you give me the snippet please.. seems like the library cannot ready from the temporary dbfs location..

I am with @yuvapraveen . Does someone have a working example ? Struggling to write to SFTP server and get NPE with newest version 1.0.3.


Image zoom: now possible to pinch zoom into entire window

Testing: #42130
I now seem to be able to pinch zoom into the entire workbench:

Possible fixed by 0d97fab352b0c70e50aecf03268a18bcd8fadd33


Patched VE images torn down even though no-teardown flag is given to pytest

@zancas
Issues: Issue #53
Problem: When running a functional test for patching a VE image, a user
can provide the '--no-teardown-glance-images' to prevent the removal of
those patched VE images once the test completes. This was not working,
and it was due to a bad setting of the config option.
Analysis: Fixed the config option setting by making the default action
as store true, and the default value of this option as store false.
Tests: Ran the tests both with and without this setting. It works as
expected. Added back in the apt-cache proxy url.

Is this the PR we need to test?

To run these tests, currently, you may to modify the inputs to the heat stack in the test file.
https://github.com/F5Networks/f5-openstack-heat/blob/develop/test/functional/ve/images/test_patch_upload_ve_image.py
In your openstack cloud, you need two networks of names: 'data1_net' and 'data2_net'. A mangement network named 'mgmt_net'. A key named 'testlab'. An ubuntu image named 'ubuntu_14.04_lts'. A security group named 'open'. These inputs will be provided through our automation runner via JSON blob, most likely, but for now they are hard-coded.

add:
-e git+git://github.com/F5Networks/f5-openstack-test.git#egg=f5-openstack-test
to requirements.func.test.txt.
Also add:
hacking to setup.py in f5-openstack-test::setup.py


Key repeat broken in macOS Sierra

Currently your script...
defaults write NSGlobalDomain KeyRepeat -int 0
...does not work in macOS Sierra. I've found that if I set things up here they work great:

Maybe they changed the preference file location or something.

I've played with that a bit. I think 0 is no longer allowed as a value, but you could use 1, 2 etc. It makes it awfully fast then though. So they might have changed the scale. If you set it to the fastest Key Repeat and shortest initial delay and then read the values on the command line you get 2 and 15.

Tried doing this:
defaults write NSGlobalDomain KeyRepeat -int 1
And here's what I get:
2016-07-14 13:51:07.168 defaults[8647:1323339] Could not write domain Apple Global Domain; exiting

Use diff to compare before and after the changes (quickly). I can't imagine Apple changed this to no longer use NSUserDefaults. Maybe it's not in NSGlobalDomain anymore.

@hkdobrev If it was just a matter of forbidden value, replacing -int 0 with -float 0.001 would have done the trick and been a better way than -int 1 [except if -float was forbidden too]. ;)

@kvpb Yeah, using float seems to work:
defaults write NSGlobalDomain KeyRepeat -float 0.000000000001; defaults read-type NSGlobalDomain KeyRepeat; defaults read NSGlobalDomain KeyRepeat
Type is float
1e-12

@mathiasbynens That didn't seem to work.

@jdsimcoe It does for me on OS X El Capitan 10.11.6 (15G31).

@jdsimcoe It does for me on OS X El Capitan 10.11.6 (15G31) when rebooting afterwards.

@mathiasbynens I'm on macOS Sierra and that setting has changed or something because neither works at all... they must have changed the value.

@jdsimcoe Could you do this please?

defaults read > a
Open system preferences and change the setting to some other value than the default.
defaults read > b
Post diff a b here.

when I do this defaults read NSGlobalDomain KeyRepeat... I get 1e-12. When I do defaults read-type NSGlobalDomain KeyRepeat I get Type is float.

When I change it in the Preferences slider to the fastest value I do defaults read NSGlobalDomain KeyRepeat and get 2. And the type is integer.

@mathiasbynens defaults write NSGlobalDomain KeyRepeat -int 1 is the best I can do on macOS Sierra. The float just doesn't work.

I tried to take a wild guess, I don't have any Mac running macOS Sierra DP. If I get what @mathiasbynens and you @jdsimcoe say, my trick works for OS X 10.11.6 El Capitan but not macOS 10.12 DP4 Sierra. Maybe it actually is a matter of forbidden values.
If -int works, -float maybe works too. Have you tried to defaults read NSGlobalDomain KeyRepeat with the slider put at different random values [not just the extremes and middle but some points here and there on the slider as well]? Right now, the question I'm asking myself is: did Apple reverse how it works [eg a bigger value means a higher rate] or just lock the values to a certain range?

Im on DP 5 and cannot seem to get the float to increase to speeds I was experiencing prior. also, you may need to tweak the InitialKeyRepeat value if you're getting no key repeat at all.

On macOS build 16a294a, after setting values through the prefs panel (and verifying that it works in the terminal), these are the values I see:
% defaults read NSGlobalDomain ApplePressAndHoldEnabled
0
% defaults read NSGlobalDomain KeyRepeat
6
% defaults read NSGlobalDomain InitialKeyRepeat
25

@wprater InitialKeyRepeat's value is actually the time it takes for key repeat to initialize, that is how long you have to stay pressing the key before it automatically repeats. Maybe it needs to be set to a shorter value along KeyRepeat in macOS Sierra?
Also, I highly discommend setting InitialKeyRepeat lower than [ 7 ; 10 ]: hardly will you press a key that 2 or 3 characters will have been input. See my .osxmavericks for more.

I can't find any command that works for macOS Sierra. Something must have changed ...

Same here. I just ugpraded to Sierra and I had to use... the GUI. And even then key repeat wasn't as fast as it was in El Capitan.

@knpwrs I've experiencing the same thing. They key repeat set from CLI appears to have no affect.

For keyboards and mouse fine-tuning I'm exploring the use of https://pqrs.org/osx/karabiner/ . Only thing is a rewrite of the app is in progress for macOS Sierra support at: https://github.com/tekezo/Karabiner-Elements

@anhkind @knpwrs @danemacmillan @kdeldycke If you want to close to 0 try this:
 defaults write NSGlobalDomain KeyRepeat -int 1
It is as close as you can get on macOS Sierra.

For me:
defaults write NSGlobalDomain KeyRepeat -int 1
defaults write NSGlobalDomain InitialKeyRepeat -int 10
makes it blazing fast. Even a bit too much, maybe.

This is sad, I really liked having blazing fast key repeat. Has anyone found anything better than
defaults write NSGlobalDomain KeyRepeat -int 1
defaults write NSGlobalDomain InitialKeyRepeat -int 10

?

Nothing i've tried has been as fast as keyrepeat 1 and initialkeyrepeat 10 =/ I miss lightning fast, but I imagine i'll get used to this speed shortly.

Just have in mind that you need to restart to apply the changes.

Logging  in and out is enough, don't need a full restart.

I found that locking and unlocking my macbook was enough to apply the changes.
defaults write NSGlobalDomain KeyRepeat -int 1
defaults write NSGlobalDomain InitialKeyRepeat -int 10

Seems as fast as before for me once I locked and unlocked my computer.

To be clear:

the UI sliders within System Preferences > Keyboard do not reflect changes made to defaults (or at least do not update if the value is outside a particular range). Previously, setting keyrepeat 0 and initialkeyrepeat 10 would min/max the sliders.
Setting KeyRepeat to a float or zero value actually disables key repeat (e.g. holding a hey does nothing). So seems like 1 is the best we can do for now.

Guys it works pretty awesome and it will be much to fast, I was not even able to type. How I got it working (also in iTerm). By default the min. value for KeyRepeat seems to be 1 and for InitialKeyRepeat 15. I used the following:
defaults write NSGlobalDomain KeyRepeat -int 1
defaults write NSGlobalDomain InitialKeyRepeat -int 10

after it I closed all applications and explicit called the "Logout". Maybe you should also try to keep the System Preferences closed or at least not pointing to the keyboard configuration.
PS: I guess the that float values are also working since the KeyRepeat value could be set on previous Mac OS X versions to float value.

Regarding settings not being applied, I proposed some days ago to kill any instance of System Preferences to keep it from interfering. My PR is ready to merge at: https://github.com/mathiasbynens/dotfiles/pull/706

I have come to this thread looking for a solution to my big issue with the macos Sierra update I've recently done, to find a dismal scene.  It appears Apple has altered the scaling factors of keyboard repeat rate and wait-times, in a way that has implications for power users everywhere: If you rely on your keyboard as a principle means of interfacing with your computer, your system will now feel slower, no matter what you do.
Just in case anyone at Apple GIAF's, this nonsense with the key repeat rate has the (intended/un-?) impact of making Apple computers feel slower, for those of us who use keyboard-based applications (apparently there are still a few..)  For example, I feel that through todays usage of vim, as opposed to yesterdays pre-Sierra update, my computer is about 3x slower than it was.  In actuality, it is not - but it certainly is not sending keys to my apps as fast as it used to, so my apps spend a lot more time just sitting around .. waiting for keypress.
It really seems like a systematic failure on Apple's part to not understand this.  I guess in the leap for features (sticky-/hot-keys are a feature now?) and the desire to push Siri everywhere, Apple is preparing us to have the courage required to .. get rid of the keyboard, too?

@seclorum Apple stopped supporting developers like us aeons ago. Look at Swift Playgrounds on the App store.

This seems to work for me sort of as fast as in El Capitan:
defaults write NSGlobalDomain KeyRepeat -int 2
defaults write NSGlobalDomain InitialKeyRepeat -int 15

Can't make it go any faster than this unfortunately.

@davidkuridza defaults write NSGlobalDomain KeyRepeat -int 1 is faster.

@jdsimcoe not in my case for some reason :)

For posterities sake, the following are the macOS 10.12.1 step values for the keyRepeat and InitialKeyRepeat when you set them using the GUI. Lower values are faster.
keyRepeat: 120, 90, 60, 30, 12, 6, 2
InitialKeyRepeat: 120, 94, 68, 35, 25, 15

Ive had different behaviour on different devices: my MBPro updated and appeared to have either disabled key repeat or set it to repeat after 30 seconds.
My Mac Mini has updated and all appears to be as before:  at least in that it works:
Values are currently:
    - InitialKeyRepeat: 15
    - KeyRepeat: 2

Hey everybody.
I just got off the phone with Apple Support about this issue. Rubber ducking the problem with a very helpful agent named Zach, I resolved this problem for my computer on OS X Sierra.
The trick was:
defaults write -g KeyRepeat -int 1
followed by a reboot.
Does that fix it for anyone else? I think the reboot step is critical.

Good but I hate rebooting.

It is frustrating that the preferences pane doesn't need to reboot the machine. Wonder what command/API it is using to trigger the update realtime...

@jakeonrails Thanks for that! Worked like a charm on a Mac Pro.
Here's what I ended up with to correct the problem, using your suggestion.
# Set a blazingly fast keyboard repeat rate.
defaults write NSGlobalDomain ApplePressAndHoldEnabled -bool false;
defaults write -g InitialKeyRepeat -int 15; # Anything lower than 15 seems too fast.
defaults write -g KeyRepeat -int 2; # You can go as low as 1, but that's too darn fast for me.

I had a slightly different problem, I had fast repeat on my MBP keyboard but no key repeat on my DAS keyboard (I'm using a new 2016 MBP - switching from Ubuntu to OSX, oh the joy, the daily struggles FFS).
Initially my KeyRepeat was set to 0.9 which, after reading through this thread and others, appears to be an invalid value. In any case, setting KeyRepeat to 1 as follows didn't fix the issue after a reboot.
defaults write -g ApplePressAndHoldEnabled -bool false;
defaults write -g InitialKeyRepeat -int 10;
defaults write -g KeyRepeat -int 1;

This did at least make the key repeat on my DAS keyboard work, but it made both my DAS and the MPB keyboard repeat way too slow. It was taking at least 500ms for each repeat which is useless.
What did work was to disable 'Slow Keys' in Accessibility Preferences and then adjust the sliders in Preferences so that they were both the highest values.
Adjusting the sliders to the highest values caused the following;
⇒  defaults read -g KeyRepeat
2
⇒  defaults read -g InitialKeyRepeat
15

KeyRepeat now working on both the MPB keyboard and my DAS keyboard. It's not super fast, but it's at least working...

@alexhayes here are my settings:
$ defaults read -g ApplePressAndHoldEnabled
2016-12-19 14:40:44.933 defaults[20505:13529518]
The domain/default pair of (kCFPreferencesAnyApplication, ApplePressAndHoldEnabled) does not exist
$ defaults read -g InitialKeyRepeat
15
$ defaults read -g KeyRepeat
1

I definitely noticed the difference between 1 and 2 - 1 is 50% of the time as 2, about 15ms. Maybe try your initial key repeat at 15 like mine - maybe one is a multiplier for the other? And reboot :D  Good luck sir, I hope this fixes it for you.

FOUND THE SOLUTION
After being desperate myself, I tried out every single solution which was posted here, but nothing helped. Afterwards, I made a single last try:
Deactivate "PressAndHoldEnabled"
in the GUI of System-Settings>"Input-Help"

I also used
$ defaults read -g InitialKeyRepeat
15
$ defaults read -g KeyRepeat
1
Those 2 adjustments only worked after disabling the checkbox in my first step.

@lobster-jack Thanks! I haven’t been able to confirm this myself yet (since everything is already working on my end), but here’s some more info:

in the GUI of System-Settings>"Input-Help"

For those running macOS in English, that’s System Preferences → Accessibility.

(then choose keyboard, and uncheck the checkbox at the bottom)

This is the checkbox that says “Enable Slow Keys”.

It baffles me that everyone in this thread ignores the fact that defaults read -g InitialKeyRepeat -int 10 returns an error: The domain/default pair of (kCFPreferencesAnyApplication, InitialKeyRepeat) does not exist.

@prewk I believe you mean write? It should be defaults read -g InitialKeyRepeat and defaults write -g InitialKeyRepeat -int 10

..and suddenly - the error disappeared. I think I interpreted an answer in this thread wrong and made an incorrect assumption. Thanks, and sorry :)

Doesn't seem anyone mentioned this yet, but when doing  defaults write -g KeyRepeat -int N and N is 0 or 1, then the slider in System Preferences shows up in the middle, but the actual tested key repeat is indeed blazing fast. And I got that working after just a Log Out, which is faster than a full reboot, so if you are like me and wanted to test different values out, you don't have to wait for a full reboot.

Finally found a solution! 🎉
defaults write NSGlobalDomain KeyRepeat -int 1
defaults write NSGlobalDomain InitialKeyRepeat -int 10
defaults write NSGlobalDomain ApplePressAndHoldEnabled -bool false

Then, close the app and re-open it.

@lucascaton That’s what .macos contains right now…

@mathiasbynens not really, ApplePressAndHoldEnabled is commented out and won't work out of the box 😁

@lucascaton What makes you say that? It’s not commented out: https://github.com/mathiasbynens/dotfiles/blob/d6ca39a907123c0a7f874c500ba16cabb3156a63/.macos#L181-L186

Ahh, sorry - I was looking at the link mentioned by someone above:
https://github.com/gcallaghan/dotfiles/blob/master/.macos#L182
My bad.

I'm running macOS Sierra 10.12.3, and I concur with @lucascaton. The solution to get the fastest keypress speeds all around is to run the following in your terminal (you can copy-paste the below directly, but note it will restart your computer):
defaults write NSGlobalDomain ApplePressAndHoldEnabled -bool false && \
defaults write NSGlobalDomain KeyRepeat -int 1 && \
defaults write NSGlobalDomain InitialKeyRepeat -int 10 && \
sudo reboot

When I attempted lower int values for either KeyRepeat or InitialKeyRepeat, I kept running into issues where my Mac Pro's 4k display literally wouldn't work at all and/or I had to physically reboot my comp (sidenote: potentially an odd/interesting bug? how/why would keypress settings affect display function?)

If I'm not mistaken, .macos already seems to be doing that (minus the reboot), @PaulCapestany

@hassankhan ah, yup, nice catch.

In Sierra you can unplug and replug your external keyboard in for the new values to take effect, no reboot required.

You can also use float like defaults write -g KeyRepeat -float 8.5

along time ago, in https://github.com/mathiasbynens/dotfiles/issues/687#issuecomment-236710547 , @mathiasbynens wanted a diff a b on defaults after changing some settings. I did that just now, and here's my diff:
103c103,104
<         KeyRepeat = 0;
---
>         InitialKeyRepeat = 15;
>         KeyRepeat = 2;
10086,10087c10087,10088
<         SPLoggingWindowHideCount = 6719;
<         SPLoggingWindowShowCount = 6720;
---
>         SPLoggingWindowHideCount = 6720;
>         SPLoggingWindowShowCount = 6721;
10091c10092
<         lastWindowPosition = "{{600, 316}, {680, 430}}";
---
>         lastWindowPosition = "{{600, 690}, {680, 56}}";
19897c19898
<                 Age = "8296.247732316";
---
>                 Age = "8402.392134855001";
20007a20009,20011
>                         56,
>                         1076,
>                         1077,
20010d20013
<                         56,
20897c20900
<         "NSWindow Frame Main Window Frame SystemPreferencesApp 8.0" = "1002 257 668 560 0 0 1920 1057 ";
---
>         "NSWindow Frame Main Window Frame SystemPreferencesApp 8.0" = "1002 274 668 543 0 0 1920 1057 ";

@mathiasbynens thanks for your dotfiles, they've continue to be helpful to me for years and years.

Leaving an update here. Using macOS Sierra 10.12.5 and it seems like
defaults write -g KeyRepeat -int 0 + logout + login now works, albeit too fast.
The scales have changed drastically, as @hkdobrev has previously stated. I've documented this behavior here:

Take note that while the GIF is indeed skipping frames, it does skip some frames until I stop holding the repeating key.
This behavior "works" on both my 11-inch Mac Book Air (2014) and my 13-inch Mac Book Air (2017). I've since set it to 1, but it 2 can be comfortable as well since the new 1 might be a little bit too fast.

Three-liner:
defaults write com.apple.universalaccess slowKey -int 0 # Disable Slow Keys.
defaults write NSGlobalDomain ApplePressAndHoldEnabled -bool FALSE # Disable Press-and-hold for keys.
defaults write NSGlobalDomain InitialKeyRepeat -int 10 # Set key repeat triggering delay to even shorter.
defaults write NSGlobalDomain KeyRepeat -int 3 # Set key repeat rate to even faster. [i] Enables key repeat.

4-liner:
defaults write com.apple.universalaccess slowKey -int 0 # Disable Slow Keys.
defaults write NSGlobalDomain ApplePressAndHoldEnabled -bool FALSE # Disable Press-and-hold for keys.
defaults write NSGlobalDomain InitialKeyRepeat -int 10 # Set key repeat triggering delay to even shorter.
defaults write NSGlobalDomain KeyRepeat -int 3 # Set key repeat rate to even faster. [i] Enables key repeat.

@mathiasbynens You could disable Slow Keys before setting key repeat, like so:
defaults write com.apple.universalaccess slowKey -int 0 # Disable Slow Keys.
defaults write NSGlobalDomain ApplePressAndHoldEnabled -bool FALSE # Disable Press-And-Hold for keys.
defaults write NSGlobalDomain InitialKeyRepeat -int 10 # Set key repeat triggering delay to even shorter.
defaults write NSGlobalDomain KeyRepeat -int 3 # Set key repeat rate to even faster.

In case you guys found default ./.macos setting is too fast. Here is good setting:
defaults write NSGlobalDomain KeyRepeat -int 3
defaults write NSGlobalDomain InitialKeyRepeat -int 20

It works for me:
sudo defaults write NSGlobalDomain KeyRepeat -float 0.000000000001
W/o sudo it does not work

wouldn't've thought to try sudo. Does it work for other broken commands?

wouldn't've thought to try sudo. Does it work for other broken commands?


Add issue templates(Proposal and Documentation)

Issue that this pull request solves
Closes: #394
Proposed changes
Add documentation and proposal issue templates
Types of changes
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Put an x in the boxes that apply

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Screenshots
Please attach the screenshots of the changes made in case of change in user interface
Other information
Any other information that is important to this pull request

@Akash20x Maybe I will handle this Template thing. I have already added new template which is given by github only. So there is no need of these. :)

OK


publish<EMAIL_ADDRESS>

Requested by: @szokeasaurusrex
Merge target: (default)
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave a comment containing #retract under this issue to retract the release (original issuer only).
Targets

[ ] gcs
[ ] npm[@sentry/cli-darwin]
[ ] npm[@sentry/cli-linux-arm]
[ ] npm[@sentry/cli-linux-arm64]
[ ] npm[@sentry/cli-linux-i686]
[ ] npm[@sentry/cli-linux-x64]
[ ] npm[@sentry/cli-win32-i686]
[ ] npm[@sentry/cli-win32-x64]
[ ] npm[@sentry/cli]
[ ] brew
[ ] github
[ ] registry
[ ] pypi
[ ] sentry-pypi

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

#retract