Add a checkbox to the Talk submission page

It would be nice to add a checkbox to the talk submission page similar to what we have when a user logs in.
The talk submission page can be found this way:

Login into epstage
Go to https://epstage.europython.eu/events/call-for-proposals/
Click on "Submit a proposal" (which send you to https://epstage.europython.eu/cfp/submit-proposal/)

The checkbox (see example image) should

Be positioned just above the "Submit Proposal" button
Have the following text next to it: "I agree to the EuroPython Speaker Release Agreement*"
"EuroPython Speaker Release Agreement" should be a link to https://epstage.europython.eu/events/speaker-release-agreement/
Submitting the form without checking the checkbox should result in a validation error.

Tips:

The current code for the identical checkbox and the desired functionality is in conference/accounts.py
The necessary code should probably end up in conference/forms/forms.py

Example (to be adapted for the talk submission page)

I will give this one a shot :-)


Export ClosedTerm, POpaque, and popaque from Prelude

Added a couple more exports to Prelude as discussed on Discord.

Warnings on the tests @blamario

Yes, but it's fixed now.


Extract the code for the ranged requests into a set of methods in the BaseArtifactController and make the implementation generic enough to be able to serve all layout provider controllers

At the moment, the logic for this exists only in the MavenArtifactController. The code for this needs to be extracted into the BaseArtifactController and made more re-usable. The respective layout provider implementations of the controllers should then use these methods as required, to avoid duplication.
This task is similar to #446.

@carlspring  I will check this out.

Okay, thanks! :)

@carlspring I think this has already been resolved. All artifact controllers now call the provideArtifactDownloadResponse() in BaseArtifactController. So they all should be supporting ranged requests.

@sanket407 : You are right! Thanks for checking! :)


Number starting with 6 series indian mobile is not accepted

Number starting with 6 series indian mobile is not accepted

Did you find any solution?


No snap-ins have been registered for Windows PowerShell version 4

Other than changing the net addresses etc. I am running the exchange quick start mostly right out of the box. I had it working fine the other day and then when I went to the various GitHub sites to grab the latest scripts so that they would launch from my S3 instead of hitting the microsoftquickstart S3 bucket I run into this:
16:26:05 UTC-0600	CREATE_FAILED	AWS::CloudFormation::WaitCondition	ExchangeNode2WaitCondition	WaitCondition received failed message: 'Command failure in C:\cfn\scripts\Configure-ExchangeDAG.ps1 on line 91 Exception: System.Management.Automation.RemoteException: No snap-ins have been registered for Windows PowerShell version 4.' for uniqueId: i-0110313f7d7d8080c
Do I have a mismatched AMI maybe? or a script error not yet rolled out? This maybe an easy fix as my Exchange and PowerShell mojo is still weak. I come from a linux aws world afterall.
Thanks,
Robert

It's not an AMI mismatch from my latest round of testing.

Are you getting the error just on ExchangeNode2? Can you check whether Exchange gets installed successfully? Check the logs under C:\ExchangeInstall.
The error likely fails due to the Exchange snappin not being there, e.g. likely this

just did a full clean of my stacks and figured lets try to run this with 3 nodes to see if the order/timing changes results. Node 2 still fails Node1 Node3 both come up nicely. Of course it is Node2 that has the extra logic to establish the DAG configuration. Error message was simular but different this time:
14:52:43 UTC-0600	CREATE_FAILED	AWS::CloudFormation::WaitCondition	ExchangeNode2WaitCondition	WaitCondition received failed message: 'Command failure in C:\cfn\scripts\Configure-ExchangeDAG.ps1 on line 91 Exception: System.Management.Automation.RemoteException: The Microsoft Exchange Replication service does not appear to be running on exchangenode1. Make sure that the server is op...'

My guese would be the issue and the difference has to do with this:
$ConfigDAG={
$ErrorActionPreference = "Stop"
    Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn
    New-DatabaseAvailabilityGroup -Name $Using:DAGName -WitnessServer $Using:FileServerNetBIOSName -WitnessDirectory C:\$Using:DAGName -DatabaseAvailabilityGroupIpAddresses '<IP_ADDRESS>'

    Start-Sleep -s 60

    Add-DatabaseAvailabilityGroupServer -Identity $Using:DAGName -MailboxServer $Using:ExchangeNode1NetBIOSName
    Add-DatabaseAvailabilityGroupServer -Identity $Using:DAGName -MailboxServer $Using:ExchangeNode2NetBIOSName

    # Manuall run
    #Add-MailboxDatabaseCopy -Identity DB1 -MailboxServer $Using:ExchangeNode2NetBIOSName -ActivationPreference 2
    #Add-MailboxDatabaseCopy -Identity DB2 -MailboxServer $Using:ExchangeNode1NetBIOSName -ActivationPreference 2

    #There should also be a restart of the IS service (restart-service MSExchangeIS on each node)
    #Get-MailboxDatabaseCopyStatus * | where {$_.ContentIndexState -eq "Failed"} | Update-MailboxDatabaseCopy -CatalogOnly

}
if ($ExchangeNode3NetBIOSName) {
    $ConfigDAG={
        $ErrorActionPreference = "Stop"

        Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn
        New-DatabaseAvailabilityGroup -Name $Using:DAGName -WitnessServer $Using:ExchangeNode3NetBIOSName -WitnessDirectory C:\$Using:DAGName

        Start-Sleep -s 60

        Add-DatabaseAvailabilityGroupServer -Identity $Using:DAGName -MailboxServer $Using:ExchangeNode1NetBIOSName
        Add-DatabaseAvailabilityGroupServer -Identity $Using:DAGName -MailboxServer $Using:ExchangeNode2NetBIOSName
    }
}

Hi @Robert-M-Green , are you still seeing this come up? I've not seen this issue in our CI tests for a while now.


parametrize doesn't work as expected with multiple Python versions

Given the following:
@nox.session(python=["3.8", "3.9"])
def test(...

I can run nox -s test and Nox will run test-3.8 and test-3.9.
However, given the following:
@nox.session(python=["3.8", "3.9"])
@nox.parametrize("foo", ["bar", "baz"])
def test(...

I cannot then run nox -s "test(foo='bar')" and have Nox run test-3.8(foo='bar') and test-3.9(foo='bar').

This is expected behavior. You can explicit ask nox to just run with one of
the interpreters.
On Fri, Mar 5, 2021, 3:45 PM smithfred<EMAIL_ADDRESS>wrote:

Given the following:
@nox.session(python=["3.8", "3.9"])def test(...
I can run nox -s test and Nox will run test-3.8 and test-3.9.
However, given the following:
@nox.session(python=["3.8", "3.9"])@nox.parametrize("foo", ["bar", "baz"])def test(...
I cannot then run nox -s "test(foo='bar')" and have Nox run
test-3.8(foo='bar') and test-3.9(foo='bar').
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/theacodes/nox/issues/395, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB5I43QPCGWEXOXPQ3EGHTTCE7HVANCNFSM4YV3UUWQ
.

I don't understand.
What I mean is, I would expect that if I run nox -s "test(foo='bar')", then it would run both test-3.8(foo='bar') and test-3.9(foo='bar'), but this doesn't work.

As a workaround @smithfred , the following should work:
@nox.session
@nox.parametrize("python", ["3.8", "3.9"])
@nox.parametrize("foo", ["bar", "baz"])


Fix server termination in tests

We currently skip this test because it hangs (after passing).

It seems that this issue is gone.


Upgrade test_api dependency

On the current beta channel, the flutter_test and flutter_driver sdk dependency pins test_api to 0.4.8. There is a never version 0.4.9 that is a requirement for test 1.20.0+. Some packages already depends on this, especially analyzer 3.0.0+. I'm working on a builder that is hitting a bug in the analyzer package that is fixed in 3.0.0.
I would like to urge you to update the pinned version of test_api in beta before the next release. Otherwise users will need to do a dependecy_override on test_api, which is not ideal

It has already been updated
It's general best to check master before filling issues about dependency versions; they are updated regularly.

@stuartmorgan this was not a request for master; it was a request to get this updated in beta (i.e. essentially a cherry-pick request).

@nielsenko - thanks for the report! A few questions:

test 1.20.0+. Some packages already depends on this, especially analyzer 3.0.0+

How is the analyzer dep on test visible to people who depend on analyzer? Analyzer depends on test via a dev dependency.

I'm working on a builder that is hitting a bug in the analyzer package that is fixed in 3.0.0.

Do you have a link to the bug? I'm wondering how widespread the issue is - how many people would be impacted by this analyzer bug. In addition, when you say builder, do you mean you're doing some code gen?
Thanks!

No, I don't have a link to an issue on analyzer. I just tried updating to version 3.0.0 (from 2.8.0) and noticed it was resolved.
Yes, I'm doing codegen. I have this somewhat unusual requirement that makes the builder a normal dependency, not a dev_dependency. Hence, it drags in the analyzer as a transitive dependency for our users. Since analyzer 3.0.0 depends on test ^1.20.0 which depends on test_api ^0.4.9 we end up forcing the user to use a never test_api than currently supported by flutter. It is true, it works on master, but I wondered if it could be cherry-picked to beta as well, as it is closer to be released.
Anyway, I'm also investigating what it will take to work around the issue we see with analyzer 2.8.0.

@stuartmorgan this was not a request for master; it was a request to get this updated in beta (i.e. essentially a cherry-pick request).

Many (most?) Flutter bugs are filed against stable or beta; this isn't distinguishable from them. And in particular we have bugs like this (please update pinned dependency X) filed on a regular basis. We've never treated them any differently from other bugs filed against non-master channels--which is to consider them fixed once they are fixed on master.
Cherry pick requests should be clearly identified as such in order to be triaged correctly.

Hi @stuartmorgan
I'm sorry if I made a mistake raising the issue. I should have mentioned that I was aware of the fix on master. You are of course entitled to close as you did - I was just hoping that it would be a minor thing on your end.
Br, Kasper

We have found a work-around. Sorry for the inconvenience.


fix: Data Resource Group block and update tests

Description

Update to remove the data block requirement for resource group
Associated Readmes updated
Testing update
Please specifically review diagnostic settings as I believe this did not work previously
Update default testing to minimum inputs

Type of Change

[x] Non-module change (e.g. CI/CD, documentation, etc.)
[x] Azure Verified Module updates:

[ ] Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in locals.version.tf.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in locals.version.tf.json.
[x] Breaking changes and I have bumped the MAJOR version in locals.version.tf.json.
[x] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[x] My corresponding pipelines / checks run clean and green without any errors or warnings
[x] I did run all  pre-commit checks

@Azure/avm-core-team-technical-terraform I believe this repository may not have the approvals correctly setup

@chinthakaru can you please review?


Allow block systems to be solved with SuperLU

This adds the ability for form a monolithic system from a block operator when SuperLU is requested for block systems. In other words, direct solvers can now be used for block systems.

Codecov Report

Merging #933 (3d2acab) into develop (ef06132) will decrease coverage by 0.12%.
The diff coverage is 25.00%.

@@             Coverage Diff             @@
##           develop     #933      +/-   ##
===========================================
- Coverage    90.46%   90.35%   -0.12%
===========================================
  Files          129      129
  Lines         9428     9443      +15
===========================================
+ Hits          8529     8532       +3
- Misses         899      911      +12

Impacted Files
Coverage Δ

src/serac/numerics/equation_solver.cpp
62.68% <25.00%> (-3.45%)
:arrow_down:

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


[Refactor] Open the event base compaction framework

What type of PR is this：

[ ] bug
[ ] feature
[ ] enhancement
[x] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_be_unittest

run starrocks_admit_test

https://github.com/Mergifyio backport branch-2.4


Bug: ArgumentNullException: Value cannot be null.

Describe the bug
I'm currently trying to get an overlay running in Unity using Twitchmata. While doing so I noticed an error in the Unity Console:
ArgumentNullException: Value cannot be null.
Parameter name: key
System.Collections.Generic.Dictionary`2[TKey,TValue].FindEntry (TKey key) (at <27586baf39bf4babbfd8a2caabe8e228>:0)
System.Collections.Generic.Dictionary`2[TKey,TValue].ContainsKey (TKey key) (at <27586baf39bf4babbfd8a2caabe8e228>:0)
Twitchmata.UserManager.UserWithID (System.String userID) (at Assets/External/Twitchmata/UserManager.cs:28)
Twitchmata.UserManager.ExistingOrNewUser (System.String userID, System.String userName, System.String displayName) (at Assets/External/Twitchmata/UserManager.cs:98)
Twitchmata.UserManager.UserForSubscriptionNotification (TwitchLib.PubSub.Models.Responses.Messages.ChannelSubscription subscriptionNotification) (at Assets/External/Twitchmata/UserManager.cs:135)
Twitchmata.SubscriberManager.PubSub_OnChannelSubscription (System.Object sender, TwitchLib.PubSub.Events.OnChannelSubscriptionArgs arg) (at Assets/External/Twitchmata/FeatureManagers/SubscriberManager.cs:153)
TwitchLib.Unity.PubSub+<>c__DisplayClass111_21.<.ctor>b__58 () (at <5a6d6e98208f4e00995c90390ef1878d>:0)
TwitchLib.Unity.ThreadDispatcher.Update () (at <5a6d6e98208f4e00995c90390ef1878d>:0)

Time-wise, this happened at the moment a viewer was gifted a subscription. My code for handling the new subscriber is this:
	public override void UserSubscribed(Twitchmata.Models.User subscriber)
	{
		if (subscriber.Subscription.IsGift == true)
		{
			Debug.Log($"{subscriber.DisplayName} received gift sub from {subscriber.Subscription.Gifter.DisplayName}");
		}
		else
		{
			Debug.Log($"{subscriber.DisplayName} subscribed. They have subscribed for {subscriber.Subscription.SubscribedMonthCount}");
		}
		_twitchTracker.AddSubscription();
		this.Manager.Utilities.FetchAvatarForUserAsTexture(subscriber, (texture) => {
			Debug.Log("Trying to get user image");
			userProfilePic.texture = texture;
			//Save_Texture2D(texture, @"D:\" + subscriber.DisplayName.ToString() + ".png");
		});
	}

The Debug.Log($"{subscriber.DisplayName} received gift sub from {subscriber.Subscription.Gifter.DisplayName}"); isn't showing up in the log, so I suppose it's the event itself causing the issue. _twitchTracker.AddSubscription(); wasn't called either.
I've only seen this issue once so far. So I don't have any steps to reproduce. But I can tell you that subs / gift subs before and after the error were working just fine.
Expected behavior
No exception would be great :D
Screenshots
Desktop (please complete the following information):

OS: Windows 10 Pro 21H2
Unity Version 2022.2.12f1 (DX11)
Twitchmata 1.05b5

Update: Over the course of 4.5 hours of stream today, I've seen the same error 6 times. And from what I could see from the logs, all the errors happened for gifted subs.

@tryallthethings As I suspected, this was to do with anonymous gifters. It should be fixed in the main branch

Great, thank you! Will "test" it in the next stream. How do you test these kinds of things? Just ask someone to gift a sub to you, or is there a way to emulate them?

I've added a debug method to emulate an anonymous gift sub


chore(docs): fix wording in setup.md

Nittest of the nits after #322.

Superseded by #336. Whoops, did not notice 😅


Document won't build due to "Too many unprocessed floats."

It's because all the H's were changed to p's. I'll try inserting \clearpage calls, and hopefully this will work.

Okay, I'll try to build after master Chris' viola...


Remove custom browser config from package.json

What's the purpose of this pull request?
This PR takes the great idea of @igorbrasileiro and removes the "browser" field in store-ui. Also, this PR makes it possible to remove the custom requires in gatsby-(browser|ssr).
How it works?
Tell us the role of the new feature, or component, in its context.
How to test it?
https://github.com/vtex-sites/carrefourbrfood.store/pull/445
https://github.com/vtex-sites/btglobal.store/pull/476
https://github.com/vtex-sites/marinbrasil.store/pull/478
https://github.com/vtex-sites/storecomponents.store/pull/823
References
Spread the knowledge: is there any content you used to create this PR that is worth sharing?
Extra tip: adding references to related issues or mentioning people important to this PR may be good for the documentation and reviewing process

Maybe you have created this branch from another one that's not master, maybe this fix/seo.

Maybe you have created this branch from another one that's not master, maybe this fix/seo.

It's because it was in draft. Now it's ready for review :)


Uncaught Error: Unknown header type: 10532

Attempting the simple visualization example:
Keen.ready(function(){
    var count = new Keen.Query("count", {
      eventCollection: "views",
      groupBy: "event.id",
      interval: "daily",
      timeframe: "this_21_days"
    });

    keen.draw(count, document.getElementById("chart-wrapper"));
  });

with "views" collection event data like:
{
    "keen": {
        "timestamp": "2016-02-12T21:30:09.456Z",
        "created_at": "2016-02-12T21:30:09.456Z",
        "id": "56be4ee190e4bd6cbed434c0"
    },
    "event": {
        "id": 12798,
        "parent_id": 12797,
        "status": "published",
        "starttime": "2016-03-05T14:00:00.000Z",
        "tags": [
            "Performance"
        ],
        "name": "The Sea Voyage by John Fletcher and Phillip Massigner ",
    }
}

results in a JS runtime error Uncaught Error: Unknown header type: 10532 (Note: 10532 is probably one of the event.id's).
It works fine if you use groupBy: "event.name". Perhaps a bug due to event.id being numeric?

I just re-created this same query in the Keen explorer and was able to get the visualization.
The embed code there looks pretty much the same (although groupBy is an array, which should also work).
Can you confirm what version of keen-js you are usings?

  var query = new Keen.Query("count", {
    eventCollection: "views",
    groupBy: [
    "event.id"
],
    timeframe: "this_21_days",
    timezone: "UTC"
  });

  client.draw(query, document.getElementById("my_chart"), {
  });```

Meekohi provided a fiddle where this issue is present:
https://jsfiddle.net/u2k5wnnn/

keen-js is able to query & render this as a pie chart, but it breaks as soon as you add an interval to turn into a line chart or bar chart.
For some reason this issue is not present in the keen-explorer, perhaps the explorer is using a newer version of keen-js (keen_viz.js?)?
Here is the version of keen-js the customer is using in the Fiddle:
"https://d26b395fwzu5fz.cloudfront.net/3.4.0-rc/keen.min.js"

@wetzler @Meekohi this sounds consistent with issues we've worked through in latter -rc# distros. Please give v3.4.0-rc4 a try :+1:

I just swapped that latest version in and it appears to be working just fine. Closing this issue for now, but please ping me if I should re-open.

I can confirm issue is fixed in -rc4. :+1:


ci(dependabot): fix dependabot prs failing due to missing token

Slightly simpler solution than #169 (in my opinion).
Short summary:

I feel that there's a fair amount of noise in the CI step descriptions (at the bottom of a PR). To make them easier to parse I've:

Removed the dhis2 prefix (this didn't communicate anything extra to me, but maybe I'm missing the reason for this prefix).
Removed the app suffix (I can see how it's necessary to distinguish between the different types of workflows when managing multiple workflow types on an org. level, but from the context of this app, I thought it would be clear enough that the workflow running should be for an app).

Split up the verify task in a verify trusted and verify external workflow. verify external only runs tasks that don't need credentials (and runs for PRs from forks and dependabot PRs). We distinguish between PRs from forks and local PRs by checking a github supplied fork boolean. We use a github supplied actor to identify dependabot PRs. You can verify that this works correctly by checking the tasks that ran in the commit where I reversed the checks: https://github.com/dhis2/scheduler-app/pull/171/commits/c04c86bb00b30c27caf127b3e39388013d796759. We'll need to check that the dependabot identification works by rebasing the dependabot PRs after merging this.
Abstracted the publish and release steps to a separate publish workflow. Felt like they shouldn't be under verify to me, since we're not verifying but publishing. The publish workflow only runs after the verify trusted workflow has completed (and jobs are only executed if the verify trusted workflow exited successfully)
manual skip ci check is no longer necessary, so I removed it
Unfortunately cypress needs a secret, so this can't run in the verify external context
Note that the publish step won't trigger now. It'll only start triggering once that workflow has been merged to the default branch of this repo.

FYI: I'll squash this to the PR title before merging

Closed as I've moved the core fixes from this PR to https://github.com/dhis2/workflows/pull/10


Good hosting solution for an FTP server with ftp-srv

This one is more of a question than an issue.
We've created a custom FTP server that talks to Google Cloud Storage. Currently, we're running it inside of a Docker container on a Google Compute instance, which works alright, but it's a hassle to implement proper Continuous Deployment.
I've been looking for alternatives that offer a better CD experience but it seems like most of them don't offer opening up the ports required to run an FTP server. I've been looking at Heroku, Fly, Render, and Sloppy so far, but neither of them seem to work for what I'm trying to do.
Do you have any recommendations on where to host a project like this?
Thanks in advance!

Yea, this is actually a harder problem than it seems on the surface given FTP and its port requirements, as you have discovered.
We currently use Packer  to create an (AWS) AMI and manage our FTP server outside of our containerized environment - this gives us far more control over the networking conditions and dynamic port assignment, etc.
We build the AMI alongside our other container builds and then use Terraform with an input variable for the AMI build (written to the input file after the tests pass and the container is built) to provision and version the server. This allows us to correctly manage the code within our mono-repo alongside the containerized services and lambda functions and follow the same QA as the rest of the containers.
I'm going to transfer this to the discussions, because that is the appropriate place for this!


fallback if vundle fails

So, this is experimental and I haven't tested it but I hope it explains a potential vundle fallback.

so this works for me on.
I tested by ~yadr/vim/bundle/vundle && git reset --hard b571067 which is before the vundle#begin method then running rake update.  This captured the error and recovered (although I am worried that stdin might not work for this command so if vim requires input for some reason this might not work).

This has been sitting too long and I don't think the current vundle is really bothering anybody, I'd rather not have a crazy migration to deal with. thanks for your efforts


memory corrupt

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

To my experience, problems like these can be avoided if you do not access an instance of ndarray from different threads or tasks. If it is still necessary, try copying ndarray to float[], pass it to your method and then copy to new ndarray.
Cheers!

I'm single-threaded, so I shouldn't have any problems with multithreading

To my understanding it - AccessViolationException usually occurs if you somehow lost reference to your NDArray.
NDArray only frees allocated memory when IDisposable is triggered by the garbage collector when there are no longer any references to it.
In addition, zero-copied NDArrays from any operation still hold a reference to base memory which should prevent deallocation.
Please provide here a reproducing unit test/piece of code and I'll gladly investigate.

这个是我测试的时候异常的内容,

当我对一个数组执行批处理操作时，我看到的结果是这个问题.


Simplified mesh intersection logic

Change the mesh intersection code to rely on epsilon checks and point insertion to construct the final intersected mesh.

I know there are merge conflicts but I don;t know if we want to merge to master or to a different branch. So I await further instructions.

I know there are merge conflicts but I don;t know if we want to merge to master or to a different branch. So I await further instructions.

@Makogan Yes, we want to merge to master.

Merged to master and made sure the current code passes the CI checks

Other than the conversations marked as unresolved, I think I addressed all comments.

Thank you, I took care of the last few details.


✨ Contribution Opportunity: Convert Echinda tests to Forge invariants

What is a Contribution Opportunity?
A Contribution Opportunity is a concrete task that you can work on to contribute to the Optimism Collective.

Summary
The smart contracts for Optimism’s upcoming Bedrock launch includes a suite of Echidna tests which use Echidna for property testing. These contracts also have a suite of Forge invariant tests. In order to standardize tooling, OP Labs is looking for contributors to help convert the Echidna tests into to Forge invariant tests.
Please refer to the corresponding GitHub issue for more information.
Impact
Standardization is important to making sure that we’re covering every possible case with our invariant test suite and that we’re not missing anything because tests are split between two different frameworks.
Resources

Bedrock
Echidna

Hello! I want to express my interest in contributing this task and ask a clarifying question:

Is it possible if I want to implement new invariants? In that case do you have contract to get more information?

You can reach me here or:
email<EMAIL_ADDRESS>Kind Regards,
Rati

Hi @Ratimon, I'm glad you're interested in this task! Adding new invariants is also always useful. I will ask the OP Labs smart contracts team for more information about the list of invariants that are not currently being tested.

@smartcontracts Hi, I note that this issue (https://github.com/ethereum-optimism/optimism/issues/4980) is now resolved : ).


Original event details not present in emitted event

Fixed in https://github.com/artfuldev/cycle-keyboard/commit/1fbaec6157c93b45d6d43121dfc18ea1722d98ed


Closes #41: Make tagged items view class-based

The current function-based view is broken since commit
8c5496f0eafe7d3ec8cb52847de44d3336b18c2d.

This branch has conflicts that must be resolved

@apollo13 is this issue already addressed? or needs rework?

No idea, I am not maintaining taggit anymore.


Live Server

live server not working in vs code, when I click it showing the port 4405

Can you able to access from http://localhost:4405?


Legacy App issue

Good to fix/address this if it's quick since we're still using the legacy app for demonstration purposes.
Index of Datasets
README doc
New spreadsheet I am trying to add
It looks to me like Google changed the format of it's links - I can't get the new spreadsheet ID in a format where it starts with 2PACX also where it used to say "/spreadsheets/d/e/" the URL is now just "/spreadsheets/d/"
I think that's why I am getting a "No Links" error.

@hazelshapiro the sheet is published, correct?

Yes, this is the published url https://docs.google.com/spreadsheets/d/1envoTaQE59sGkgnZJU8L6KMICrjHZAOGsh6f998JGbI/pubhtml

Thanks! It's not the first time they've done this. How inconsiderate.
We should be saving the full URL in our index sheet, and updating the code to use that full URL instead of templating based on the old URL structure. The change sounds minor, but it's been some time since we deployed this app, and we may have taken shortcuts because we only expected to deploy it once, so there may be additional minor challenges there. What do you think @rmarow ? We have that deployment set up in this private repo, but I don't remember if you worked on it or not: https://github.com/nsidc/usaon-vta-webapp-legacy

@MattF-NSIDC I don't recall doing any deploying of the legacy app during my time on this project besides reviewing it for work on the new app. Very frustrating that google changes the URL!


update to redux 4

redux 4 is coming! https://github.com/reactjs/redux/releases/tag/v4.0.0-beta.1
it seems not to introduce many breaking changes, so it should work with saga as well, but saga has currently a dependency on redux 3.x, so that at least needs to be updated

Redux 4 it out btw https://github.com/reactjs/redux/releases/tag/v4.0.0

As discussed - we should update the dependency range to >=0.10 <5. Anyone up for creating a PR? :)


fix(frame): set execution context null if it's not created

Fixes: https://github.com/GoogleChrome/puppeteer/issues/2709
In mixed-content page like this one, frame stops loading before execution context is created.
This behavior causes exposeFunction to be stuck indefinitely because contextPromise will never be never resolved.
There is no way setting proper context if it's not created yet, so I think it's better to set null.

Interesting. Ideally, Puppeteer should force the creation of an execution context. We already do this for pages like about:blank that normally wouldn't have an execution context.
It looks like DevTools has the same bug on the page. No execution context is shown for the iframe. But I can force an execution context to be created by evaluating document.querySelector('iframe').contentWindow. I'll look into this a bit more and then possibly file an upstream bug on Chromium.

@JoelEinbinder
Thanks! If it can be fixed upstream, that would be perfect!

Closing in favor of upstream fix: https://chromium-review.googlesource.com/c/chromium/src/+/1102154


Handle not existing or invalid secrets file

Fix this unhandled exception: http://paste2.org/KAKAN6Kf

@gazpachoking what do you mean by 'config validation'? I thought the config validation just validates against the json schema?? Which would mean @antivirtel changes are valid?

No, they are not, it's still WIP!

@antivirtel this PR is still WIP?? It's been over 8month so i assumed it was forgotten .. heh

Sorry, I'd no time to work on this. I'll have in this month finally!

@antivirtel no problems... I changed the title to [WIP]

File does not exist:
$ flexget check
2015-07-11 16:00 INFO     check                         Checking config file `~/.flexget/config.yml`
2015-07-11 16:00 WARNING  check                         Config line 4 is likely missing ':' at the end
2015-07-11 16:00 WARNING  check                         Config line 7 is likely missing ':' at the end
2015-07-11 16:00 WARNING  check                         Config line 10 is likely missing ':' at the end
2015-07-11 16:00 CRITICAL secrets                       Secrets' config file '/home/roland/.flexget/secrets.yml' does not exist or you have no read permission!
Could not initialize manager: ~/.flexget/secrets.yml

Invalid secrets config file:
$ flexget check
2015-07-11 14:59 INFO     check                         Checking config file `~/.flexget/config.yml`
2015-07-11 14:59 WARNING  check                         Config line 4 is likely missing ':' at the end
2015-07-11 14:59 WARNING  check                         Config line 7 is likely missing ':' at the end
2015-07-11 14:59 WARNING  check                         Config line 10 is likely missing ':' at the end
2015-07-11 14:59 CRITICAL secrets                       Invalid secrets file: '/home/roland/.flexget/secrets.yml'.
2015-07-11 14:59 CRITICAL manager                       Failed to load config file: Invalid secrets file: '~/.flexget/secrets.yml'.
Could not initialize manager: Invalid secrets file: '~/.flexget/secrets.yml'.

@antivirtel Sorry I didn't see this when you updated. Can you update and make sure it still works?

Is this relevant?

@gazpachoking I'll try to test it this weekend, I hope I'll have time.
@liiight how you mean that?

I'm just going over all prs, pinging the openers. If you're on it it's great

Reopen if relevant


Makes test pass on Windows

Using the basename function I get  "test.php"
Using Str::afterLast($str, '/') gets this: "one_missing_key\en\test.php"
That's because the directory separator is different on Windows.
Which is also the reason none of the test pass for me, I assume.

@LarsWiegers the last commit makes all test pass on Windows.

Awesome thx!


Unable to use automation on

First of all a big thank you for the plug in!
I am able to see an control the valve from homekit, but unable to add an automatic switch (eg switch valve off when last person leaves home). The sensors can be used as inputs for another automation. Any idea how this can be resolved?
I am running 1.4.2 on ios 14.
1.5.0 does not show the switch at all as some people suggested while 1.5.1 shows as not supported.

I am aware of this problem, and it happen because I am bundling multiple HomeKit characteristics inside each device. Im working on a branch which separate out characteristics, and this may fix the issue you are seeing.


update otel-collector to 0.77.0 and golang 1.20.4

Description
Changes proposed in this pull request:

update otel-collector to 0.77.0 and golang 1.20.4
...
...

Related issue(s)

otel-collector-contrib was not released yet with 0.77.0, we will need to wait a tiny bit


Material Design Expansion Panels with animation effect in Angular 4

Feature request/Proposal:
Multiple expansion panels in a single card.(Accordion in Material design with ripple effect).
What is the expected behavior?
Drops down multiple cards with animation style, and minimizes with animation.

The Expansion Panel is already implemented:
https://material.angular.io/components/expansion/overview

Closing as the Material Expansion Panel and Accordion are already released.


[Bug]: openssl fatal error: openssl/opensslconf.h: No such file or directory

What happened?
Added openssl as the dependency, but including <openssl/bn.h> fails with
external/openssl+/include/openssl/macros.h:14:10: fatal error: openssl/opensslconf.h: No such file or directory
14 | #include <openssl/opensslconf.h>
|          ^~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Version
Development (host) and target OS/architectures:
Output of bazel --version:
bazel 8.0.0
Version of relevant rules from the WORKSPACE or MODULE.bazel file:
bazel_dep(name = "openssl", version = "3.3.1.bcr.0")
Language(s) and/or frameworks involved:
c++
How to reproduce
MODULE.bazel
bazel_dep(name = "openssl", version = "3.3.1.bcr.0")
test.cpp
#include <openssl/bn.h>
run bazel build test
boringssl works:
cc_library(
	name = "test",
	srcs = ["test.cpp"],
	deps = ["@boringssl//:ssl"],
)

openssl doesn't:
cc_library(
	name = "test",
	srcs = ["test.cpp"],
	deps = ["@openssl//:ssl"],
)

external/openssl+/include/openssl/macros.h:14:10: fatal error: openssl/opensslconf.h: No such file or directory
14 | #include <openssl/opensslconf.h>
|          ^~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Any other information?
No response

@illicitonion

Thanks for flagging this - it was fixed in https://github.com/raccoons-build/bazel-openssl-cc/commit/878a12f1b55cd8b16d2482ee8f79b42884d6dbd7 and released in https://github.com/bazelbuild/bazel-central-registry/pull/3400


Sliders are not available

We'd like to use sliders to our project. But Semantic UI does offer that feature.
Would you put it on the new version of the project ?

Like a range slider?


HTML Compliance - Form Select - Empty

Misses some corner cases such as boolean false and all white space.

This improvement was included in #2316 so I believe this PR can be closed.


Max size of graph

The maximum width or height of a chart is hard code to 1000. The total number of pixels is also hard code to 300000.
Is there any technical issue that justifies these limits? It seems indeed that these values are never used in the code beside in AbstractGChart.setSize(...) ?

Welll, it seems that it is related to the hart.apis.google.com API. No way to relax this thus...


item can't  following if inside div scrolling element

drag item can't following scrolling element div, how to fix this issue  ?

                                        @foreach ($sub_menu_list->display_product as $product)

category_id }}-{{ $product->category_product_id }}"
                                                wire:key="productList-{{ $product->category_product_id }}">

                                                    image }}"
                                                        class="card-img-top" style="object-fit:cover" alt="..."
                                                        height="250" width="100">

                                                            {{ $product->title }}

                                                            <button type="button" style="margin-right:10px;"
                                                                class="btn btn-outline-danger px-3"
                                                                wire:click.prevent="removeAdditional({{ $list->category_id }}, {{ $sub_menu_list->category_id }},{{ $product->category_product_id }})">

                                                                Remove
                                                            </button>

                                        @endforeach

I'm not sure what you mean 🤔 Is it a visual issue? If that's the case, I think it is probably an issue in the Sortablejs package itself.

As this is an old issue and there have been multiple new package releases since this issue was created, I'm closing this issue for now. If you still have this bug or issue, tag me in a new comment on this issue and I will reopen it again.


updated resources

Updated design resources and added my profile to contributors.md

@mayukhsil good one

Thanks!🙏🏽


Check $this->record->canCreate() so that the button is removed if user is not to be able to create new items.

https://github.com/silverstripe/silverstripe-framework/blob/4a0f62fafd13bfc90a1498a632a6fec9ea27d039/src/Forms/GridField/GridFieldDetailForm_ItemRequest.php#L326

Would you like to make a pull request to add that check in?

Done (:
https://github.com/silverstripe/silverstripe-framework/pull/9018

Done @robbieaverill
https://github.com/silverstripe/silverstripe-framework/pull/9019

Thanks @rafaeldsousa


License updates for yarn-handle-malformed-json

This PR was auto generated by the licensed-ci GitHub Action.
It contains updates to cached github/licensed dependency metadata to be merged into yarn-handle-malformed-json: (branch, PR).
The licensed-ci action will add comments to this PR with the status of license checks.  Please make any changes needed to fix any status failures on this branch, then merge license updates into your branch.
If updates are unexpected, please check the github/licensed changelog for recent updates.

The licensed-ci GitHub Action updated cached license metadata based on changes to yarn-handle-malformed-json: (branch, PR).
licensed status result: SUCCEEDED
All status checks succeeded, please merge when ready.
Checking cached dependency records for licensed
.............................
29 dependencies checked, 0 errors found.

/cc @jonabc


Fixing #66 bug related to override the params default values

Fixed #66

Codecov Report

Merging #70 into master will decrease coverage by 0.04%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master      #70      +/-   ##
==========================================
- Coverage   55.77%   55.72%   -0.05%
==========================================
  Files          25       25
  Lines        2123     2121       -2
  Branches      217      217
==========================================
- Hits         1184     1182       -2
  Misses        924      924
  Partials       15       15

Impacted Files
Coverage Δ

marvin_python_toolbox/management/engine.py
53.57% <100%> (ø)
:arrow_up:

...n_python_toolbox/engine_base/engine_base_action.py
61.42% <25%> (-0.55%)
:arrow_down:

Continue to review full report at Codecov.

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

Tests done, from engine-dryrun to creating new engine with custom params_file running all actions.


Improves editor overview example with min height and border

Summary
Improves editor overview example providing a code sample that sets the editor's min height and border, as well as focuses the editor when clicking the editor area.
Test Plan
Copy and paste example into CodeSandbox
https://codesandbox.io/s/9y5162ryj4
Fixes #1880

Thanks @niveditc 😊


Website: Make the home page quick download link larger and more visible

On large screens, the home page quick download link now encompasses the logo
immediately above it, making the click target much larger.  In addition, the
quick download link now mimics the nav links at the top of the stage in
hover/focus/active highlight behavior.
On all screens, the quick download link now appears underlined, and the
spacing has been subtly adjusted.

This change is currently staged at http://nicksay.github.io/spfjs/

LGTM


EPERM: operation not permitted, unlink '...node_modules\prisma\query_engine-windows.dll.node'

Bug description
Following the Getting Started guide, when it gets to the point of running the "migrate dev" command, the script tries to install some packages through npm (don't know which ones) and this causes the error in title.
How to reproduce

Follow the Getting started prisma guide up to and included the "npx prisma migrate dev --name init" command.
Get the following error:

Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db": PostgreSQL database "testprisma", schema "public" at "localhost:5432"

PostgreSQL database testprisma created at localhost:5432

The following migration(s) have been created and applied from new schema changes:

migrations/
  └─<PHONE_NUMBER>0511_init/
    └─ migration.sql

Your database is now in sync with your schema.

Running generate... (Use --skip-generate to skip the generators)
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

npm ERR! code EPERM
npm ERR! syscall unlink
npm ERR! path C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, unlink 'C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node'
npm ERR!  [OperationalError: EPERM: operation not permitted, unlink 'C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node'] {
npm ERR!   cause: [Error: EPERM: operation not permitted, unlink 'C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node'] {
npm ERR!     errno: -4048,
npm ERR!     code: 'EPERM',
npm ERR!     syscall: 'unlink',
npm ERR!     path: 'C:\\Users\\mbelletti\\Documents\\Projects\\hello-prisma\\node_modules\\prisma\\query_engine-windows.dll.node'
npm ERR!   },
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'unlink',
npm ERR!   path: 'C:\\Users\\mbelletti\\Documents\\Projects\\hello-prisma\\node_modules\\prisma\\query_engine-windows.dll.node',
npm ERR!   parent: 'hello-prisma'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR!      C:\Users\mbelletti\AppData\Roaming\npm-cache\_logs\2021-09-09T08_05_23_557Z-debug.log
Error: Command failed with exit code<PHONE_NUMBER>: npm install -D<EMAIL_ADDRESS>The batch file cannot be found.

The log file is the following:
2021-09-09T08_05_23_557Z-debug.log
After this, the node_modules.bin directory no longer has the prisma executable, and the node_modules/prisma folder only contains the file that npm wasn't able to remove (query_engine-windows.dll.node).
Expected behavior
The script finishes correctly.
Prisma information
All the prisma configurations are the ones taken from the guide.
Environment & setup

OS: Windows 10
Database: PostgreSQL 13
Node.js version: 14.17.1 (using nvm)

Prisma Version
Environment variables loaded from .env
prisma                  : 3.0.1
@prisma/client          : Not found
Current platform        : windows
Query Engine (Node-API) : libquery-engine 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Default Engines Hash    : 2452cc6313d52b8b9a96999ac0e974d0aedf88db
Studio                  : 0.423.0

(I had to relaunch npm install to get prisma back)

The script tries to install @prisma/client and prisma` if they doesn't exists on your package.json file.
I wasn't really able to reproduce this. Looks like the system you were using didn't give the migrate command the permission to save the Node API library that we download and use.
Can you consistently reproduce this on your machine?

The script tries to install @prisma/client and prisma if they doesn't exists on your package.json file.

This is interesting, because prisma is already present in my package.json, but from what I see the script is trying to re-install prisma too (I guess so because the package getting disrupted is prisma itself). Could be a version problem?

Can you consistently reproduce this on your machine?
Yes, on this machine it happens consistently, and yesterday evening I had the same problem on another machine (but I should check it today, I tried just once).

As an additional information, after the script breaks, the node_modules/prisma directory only contains  query_engine-windows.dll.node. Could it be that the file is opened for some reason while the install script is running, and because of this it cannot be removed?

Could it be that the file is opened for some reason while the install script is running, and because of this it cannot be removed?

Might be possible. Did you try completely removing node_modules once and trying to reproduce this again?

I've tried right now by removing the node_modules directory, re-installing the packages with npm install and re-running npx prisma migrate dev --name init, and got the same result:
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db": PostgreSQL database "testprisma", schema "public" at "localhost:5432"

Already in sync, no schema change or pending migration was found.

Running generate... (Use --skip-generate to skip the generators)
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

npm ERR! code EPERM
npm ERR! syscall unlink
npm ERR! path C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, unlink 'C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node'
npm ERR!  [OperationalError: EPERM: operation not permitted, unlink 'C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node'] {
npm ERR!   cause: [Error: EPERM: operation not permitted, unlink 'C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node'] {
npm ERR!     errno: -4048,
npm ERR!     code: 'EPERM',
npm ERR!     syscall: 'unlink',
npm ERR!     path: 'C:\\Users\\mbelletti\\Documents\\Projects\\hello-prisma\\node_modules\\prisma\\query_engine-windows.dll.node'
npm ERR!   },
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'unlink',
npm ERR!   path: 'C:\\Users\\mbelletti\\Documents\\Projects\\hello-prisma\\node_modules\\prisma\\query_engine-windows.dll.node',
npm ERR!   parent: 'hello-prisma'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR!      C:\Users\mbelletti\AppData\Roaming\npm-cache\_logs\2021-09-10T07_27_58_812Z-debug.log
Error: Command failed with exit code<PHONE_NUMBER>: npm install -D<EMAIL_ADDRESS>The batch file cannot be found.

I can confirm this problem:
C:\Users\Jan\Documents\throwaway\sethRepro>npx prisma migrate dev
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db": SQLite database "fancy.db" at "file:./fancy.db"

SQLite database fancy.db created at file:./fancy.db

√ Enter a name for the new migration: ... init
The following migration(s) have been created and applied from new schema changes:

migrations/
  └─<PHONE_NUMBER>3934_init/
    └─ migration.sql

Your database is now in sync with your schema.

Running generate... (Use --skip-generate to skip the generators)
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

npm ERR! code EPERM
npm ERR! syscall unlink
npm ERR! path C:\Users\Jan\Documents\throwaway\sethRepro\node_modules\prisma\query_engine-windows.dll.node
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, unlink 'C:\Users\Jan\Documents\throwaway\sethRepro\node_modules\prisma\query_engine-windows.dll.node'
npm ERR!  [OperationalError: EPERM: operation not permitted, unlink 'C:\Users\Jan\Documents\throwaway\sethRepro\node_modules\prisma\query_engine-windows.dll.node'] {
npm ERR!   cause: [Error: EPERM: operation not permitted, unlink 'C:\Users\Jan\Documents\throwaway\sethRepro\node_modules\prisma\query_engine-windows.dll.node'] {
npm ERR!     errno: -4048,
npm ERR!     code: 'EPERM',
npm ERR!     syscall: 'unlink',
npm ERR!     path: 'C:\\Users\\Jan\\Documents\\throwaway\\sethRepro\\node_modules\\prisma\\query_engine-windows.dll.node'
npm ERR!   },
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'unlink',
npm ERR!   path: 'C:\\Users\\Jan\\Documents\\throwaway\\sethRepro\\node_modules\\prisma\\query_engine-windows.dll.node',
npm ERR!   parent: 'sethRepro'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR!      C:\Users\Jan\AppData\Roaming\npm-cache\_logs\2021-09-10T20_39_44_431Z-debug.log
Error: Command failed with exit code<PHONE_NUMBER>: npm install -D<EMAIL_ADDRESS>The batch file cannot be found.

Here are my versions:
C:\Users\Jan\Documents\throwaway\sethRepro\prisma
λ node -v
v14.17.5

C:\Users\Jan\Documents\throwaway\sethRepro\prisma
λ npm -v
6.14.14

Interesting is what happened on npx prisma -v:
C:\Users\Jan\Documents\throwaway\sethRepro\prisma
λ npx prisma -v
Environment variables loaded from ..\.env
prisma                  : 3.0.2
@prisma/client          : Not found
Current platform        : windows
Query Engine (Node-API) : libquery-engine 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Default Engines Hash    : 2452cc6313d52b8b9a96999ac0e974d0aedf88db
Studio                  : 0.423.0
Error: EPERM: operation not permitted, unlink<EMAIL_ADDRESS>    at Object.unlinkSync (fs.js:1251:3)
    at fixWinEPERMSync (C:\ProgramData\nvm\v14.17.5\node_modules\npm\node_modules\rimraf\rimraf.js:219:13)
    at rimrafSync (C:\ProgramData\nvm\v14.17.5\node_modules\npm\node_modules\rimraf\rimraf.js:319:28)
    at C:\ProgramData\nvm\v14.17.5\node_modules\npm\node_modules\rimraf\rimraf.js:350:5
    at Array.forEach (<anonymous>)
    at rmkidsSync (C:\ProgramData\nvm\v14.17.5\node_modules\npm\node_modules\rimraf\rimraf.js:349:26)
    at rmdirSync (C:\ProgramData\nvm\v14.17.5\node_modules\npm\node_modules\rimraf\rimraf.js:342:7)
    at fixWinEPERMSync (C:\ProgramData\nvm\v14.17.5\node_modules\npm\node_modules\rimraf\rimraf.js:217:5)
    at rimrafSync (C:\ProgramData\nvm\v14.17.5\node_modules\npm\node_modules\rimraf\rimraf.js:319:28)
    at C:\ProgramData\nvm\v14.17.5\node_modules\npm\node_modules\rimraf\rimraf.js:350:5

When running npx prisma -v it downloaded/installed something on the spot I think, so it might indeed be that the prisma installation somehow got corrupted. I have that sometimes but never could reproduce or understand it.
That my engine is located in<EMAIL_ADDRESS>is also an indication that something is weird and this is not the actual prisma in my project, but a temporary one from npx.

(This seems to happen on the in-the-background npm install @prisma/client and then corrupts the local prisma installation in the project, causing it to use an instant one via npx)

Can confirm, just had the same error.
Tried installing @prisma/client manually, it seems to help. So here is a possible workaround until the problem is fixed.

Delete node_modules
Run npm install
Run npm install @prisma/client
Run npx prisma generate

Can you shared your node and npm version and how you installed it? I do not really think this is anything wrong with Prisma itself, but just a weird combination of different things in the setup leading to some broken behavior.

Can you shared your node and npm version and how you installed it? I do not really think this is anything wrong with Prisma itself, but just a weird combination of different things in the setup leading to some broken behavior.

Sure. I was losing my mind over this, so I even reinstalled node. The versions are node: v14.17.6, npm: 6.14.15 on Windows 10.0.19043.
I can get the error simply by creating empy folder, running npm init and npm install prisma, then adding a simple model and running npx prisma generate.
Btw, I just tried doing the same with the older prisma version (2.20.3) and I didn't get the error.

Hello, updating my npm to the latest solve this error for me.
"In my situation this helped:
Before proceeding to execute these commands close all VS Code instances.
clean cache with
npm cache clean --force
install the latest version of npm globally as admin:
npm install -g npm@latest --force
clean cache with
npm cache clean --force
Try to install your component once again.
I hope this fix your issue. If not, you may temporarily disable your antivirus program and try again."
source : https://stackoverflow.com/questions/39293636/npm-err-error-eperm-operation-not-permitted-rename

Can replicate with yarn:

The fix provided by @NordicBeaver works perfectly and can bypass the issue.

Just to confirm, with that you mean a manual npm install @prisma/client before you first run npx prisma generate, correct?

The fix provided by @NordicBeaver works perfectly and can bypass the issue.

Just to confirm, with that you mean a manual npm install @prisma/client before you first run npx prisma generate, correct?

Correct. Installing the client manually bypasses the issue.

I just noticed that at the end of the error message, it gives a quite explicit error message what is failing:
Error: Command failed with exit code<PHONE_NUMBER>: npm install -D<EMAIL_ADDRESS>
Why is Prisma even running npm install -D prisma, when Prisma CLI is clearly already installed!?

Internal note:
This seems to be related to the Node-API library for Windows query_engine-windows.dll.node. When using the escape hatch to return to the binary engine,
PRISMA_CLI_QUERY_ENGINE_TYPE=binary
PRISMA_CLIENT_ENGINE_TYPE=binary

(for example in your .env file), the error does not occur like it does described above. Instead you get this one:
C:\Users\Jan\Documents\throwaway\9184>npx prisma generate
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma

><EMAIL_ADDRESS>preinstall C:\Users\Jan\Documents\throwaway\9184\node_modules\prisma
> node scripts/preinstall-entry.js

><EMAIL_ADDRESS>install C:\Users\Jan\Documents\throwaway\9184\node_modules\prisma
> node scripts/install-entry.js

npm notice save prisma is being moved from dependencies to devDependencies
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>updated 1 package and audited 2 packages in 1.474s
found 0 vulnerabilities

npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

npm ERR! code ENOENT
npm ERR! syscall rename
npm ERR! path C:\Users\Jan\Documents\throwaway\9184\node_modules\@prisma\client
npm ERR! dest<EMAIL_ADDRESS>npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, rename 'C:\Users\Jan\Documents\throwaway\9184\node_modules\@prisma\client' -><EMAIL_ADDRESS>npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR!      C:\Users\Jan\AppData\Roaming\npm-cache\_logs\2021-09-20T19_03_16_214Z-debug.log
Error: Command failed with exit code<PHONE_NUMBER>: npm install<EMAIL_ADDRESS>

The script tries to install @prisma/client and prisma if they doesn't exists on your package.json file.

This is interesting, because prisma is already present in my package.json, but from what I see the script is trying to re-install prisma too (I guess so because the package getting disrupted is prisma itself).

I can confirm Prisma is always trying to install prisma and @prisma/client, and lets npm/yarn deal with it already being installed:
https://github.com/prisma/prisma/blob/d75d71e6e31eefbc77f211466ab75a8dfd27b4b6/packages/sdk/src/predefinedGeneratorResolvers.ts#L108-L109
This is the reason why you are experiencing a failure in the prisma installation while already having prisma installed and actually using it right at that time.
Theory why this only now started failing: The Node-API engine file is "kept in use" (whatever that might mean in this context), while the binary engine file was not before.

Happened to another user in public Slack with 3.1.1
https://prisma.slack.com/archives/CBFFY3066/p1632645964035500

🤔 I'm trying to think why that file might have a lock now but it didn't before. Is there anything that uses that file now during the generation of the client?

@LewisTehMinerz The Node-API library engine file was only introduced generally with 3.x - so this makes sense. The code behind that (internally known as LibraryEngine) is new and different from the old one (BinaryEngine). (In https://github.com/prisma/prisma/issues/9184#issuecomment-923204553 I describe how to switch back to that implementation, and then not have this error any more).
We will need to understand why there is a file lock on Windows on that file and then find a way to fix that. (And also create a test for CI that triggers this behavior along the way - so we can confirm the fix)

New minimal reproduction:

git clone https://github.com/janpio/prisma-issue-9184
cd prisma-issue-9184
npm install
npx prisma generate
Boom.

And here is an isolated reproduction of what is happening: https://github.com/janpio/prisma-9184-minimal-repro
If you are on Windows:

git clone https://github.com/janpio/prisma-9184-minimal-repro
cd prisma-9184-minimal-repro
npm install
npx ts-node script.ts

This shows that a require keeps a file open on Windows and then does not let any process, like npm install, delete that file.

This problem also affects usage of npx prisma without a package.json: https://github.com/prisma/prisma/issues/9517 That reproduction is even more minimal.

Try to install prisma client with: yarn add @prisma/client later try again with: yarn prisma migrate dev

Thanks, it works. I think the problem occured because I didn't had @prisma/client and when first run yarn prisma migrate dev it automatically installed, but somehow failed in the fourth step

I had the same issues when trying to install a library (yarn add node-cron).. I tried @NordicBeaver solution (https://github.com/prisma/prisma/issues/9184#issuecomment-917396506) but just went to step 3 (yarn add @prisma/client). But I got the same result. Then I realized I had my server running so after I stoped it everything went to normal

Current plan:

Don't install the Prisma CLI when it is already present in package.json. This fixes the issue with npm 6.
Yarn still removes the DLL library in Prisma CLI even when @prisma/client (or any other unrelated package) is installed. If we detect that @prisma/client is missing and the project is using Yarn, prisma generate will abort and ask the user to install @prisma/client manually, since that's the only safe option with Yarn.

Possible addition to the plan: Split out Prisma CLI installation completely from the "Prisma Client" is missing condition, as that can also be useful when Prisma Client is already there.

I want to note that I accidentially ran into the same issue while prisma studio was running in the background

Hi @pfried, if this still happens with the latest version of Prisma could you open a new issue with as many details you can? So we can try to reproduce.

@Jolg42 I do not think this is an error, because if you have a file in use by another process (the node dll) this is just the normal behaviour.
Just wanted to leave the comment because it could be helpful to others if they have the same issue

As @pfried mentioned, this only happened to me while I was running prisma studio in a background process.
I stopped prisma studio and installed the dependency I needed and it worked normally.
I don't know why this happens but it would be great if they fixed it

I fixed by killing prisma studio process

I stumbled across this just now. I do not have a Prisma studio running. I have tried with and without my nest.js app running in the background.
Deleting node_modules magically fixed it for me. I'll come back if I experience this again.

Can confirm, just had the same error. Tried installing @prisma/client manually, it seems to help. So here is a possible workaround until the problem is fixed.

Delete node_modules
Run npm install
Run npm install @prisma/client
Run npx prisma generate / npm prisma migrate dev

This has just worked for me. Thanks

Can confirm, just had the same error. Tried installing @prisma/client manually, it seems to help. So here is a possible workaround until the problem is fixed.

Delete node_modules
Run npm install
Run npm install @prisma/client
Run npx prisma generate / npm prisma migrate dev

Shockingly this worked for me. To be clear I had to distinct, yet connected errors:

even as an admin, I wasn't able to delete a file generated by the prisma client within my node_modules folder
after painfully figuring out how to delete that folder, and doing an npm i, "npx prisma generate" failed due to a permissions issue.

Only after deleting the file, node_modules folder, re-installing from my package.json (which already includes prisma and @prisma/client), and then "npm i @prisma/client" explicitly after my npm -i, was I able to get "npx prisma generate" to work.
To be clear the offical prisma docs state the following: "Note also that prisma generate is automatically invoked when you're installing the @prisma/client npm package. So, when you're initially setting up Prisma Client, you can typically save the third step from the list above."

Hy!
I have a same error but not the begining.
I want install class-validator and class-transformer
After that i reinstall prisma and @prisma/client , and that i install class-validator and class-transformer.

The problem with this can be if you try building projects etc npm run build, and you started your Prisma, etc npx Prisma studio. The project throws this error because it cannot build a project if Prisma is running.

Thank you both @StrahinjaWebDev & @ishaqyusuf for reporting this in comments here, I randomly found them.
Could you actually create a new bug issue, so we can look at it again with fresh eyes on a fresh version of Prisma?
Note: creating a new bug issue (and mentioning this one) is the best way to have us look at it, comments in closed issues are very likely to be unseen.

Fixed the issue on my end. Turns out my server was still running and that was blocking access to specific files. Stopped the server, and did npx prisma migrate dev and it worked.

May help some, if your application is running while trying to migrate then prisma can't unlink. If that's the case just kill your node process and try again. I've done many times and forgotten that I still have my server running.

i was running prisma studio in background kill your all  open terminals and then try

getting the same error- I cannot prisma:generate if the client is already being used in an app which is running

I dont know if anyone is having this issue anymore, but what helped me in my case is that first I stopped the server, then ran npx commands and it worked perfectly fine.

I dont know if anyone is having this issue anymore, but what helped me in my case is that first I stopped the server, then ran npx commands and it worked perfectly fine.

That's it! That's working for me, I'm using pm2, so after running npx pm2 stop all and re-running npx prisma db push it's working fine. Thanks @lumgashi

Just remove node modules folder.

I dont know if anyone is having this issue anymore, but what helped me in my case is that first I stopped the server, then ran npx commands and it worked perfectly fine.

As simple as that, thanks

For anyone still experiencing this issue, and using next.js... It would appear the next build can get corrupted sometimes. With the dev server not running, delete the .next build folder, then try npx prisma generate. Worked for me.

This bug popped up for me again, and seemed to coincide with me placing the first entry for a new model that I hadn't used yet.

same problem for me when I updated prisma

I go this problem, and I noticed that .dll file were running due to my current terminal was running "npm dev run"
I stopped the run and then the command was working nicely again.
TRY STOPPING ACTIVE "npm run dev" or "npm start"

lumgashi

I can see that this works, but honestly it is a pretty terrible DX.
Is anyone working on a fix for this??

I dont know if anyone is having this issue anymore, but what helped me in my case is that first I stopped the server, then ran npx commands and it worked perfectly fine.

I can see that this works, but honestly it is a pretty terrible DX.
Is anyone working on a fix for this??

Windows does not let us delete a file during the command you are trying to run. I don't think there is much we, Prisma, can do about that - or is there? Suggestions welcome.

I think prisma is trying to delete the file "query_engine-windows.dll.node" while at the same time the node.js environment is using it. So the easiest solution I found is to stop the server you are using and run the command that was previously causing this error.

Can confirm, just had the same error. Tried installing @prisma/client manually, it seems to help. So here is a possible workaround until the problem is fixed.

Delete node_modules
Run npm install
Run npm install @prisma/client
Run npx prisma generate / npm prisma migrate dev

Thanks, it work for me !

I go this problem, and I noticed that .dll file were running due to my current terminal was running "npm dev run" I stopped the run and then the command was working nicely again. TRY STOPPING ACTIVE "npm run dev" or "npm start"

Yeah stopping the dev server worked for me

In my case, i have to delete node_module and yarn install all package again, and i found reason lead to this error, because prisma use nodejs version > 14 or 15, but when i npx prisma generate to migrate i use nodejs version 14.17.3. It's lead to that error. ( because to run my project i must use nodejs version 14, and when i migrate i have to delete node_module )
To resolve that error, i found two ways to fix:
1)
Tried re-installing @prisma/client manually, it seems to help. So here is a possible workaround until the problem is fixed.
Delete node_modules
Run npm install
Run npm install @prisma/client
Run npx prisma generate / npm prisma migrate dev

Use nodejs version >= 15 ( or in my case found what package use nodejs <15 and remove it to run completedly perfect project )

Stopping the dev server worked for me too, but is there really no way to circumvent this? It's an annoying thing to do.

Suggestions welcome @filipjnc, we see the problem but have no idea what to do about it.

@filipjnc I did the same and it worked.

Попробуйте остановить runtime приложение, которое у вас запущено в данный момент, после остановки приложения, yarn prisma generate

If you're using typescript try this
ctrl+p
Write this
>TypeScript: Restart TS Server
That's all

Must stop server before running command.

Prisma 5 has a --no-engine flag for this. As far as i can tell ( without doing actual research :) ) this on works with npx prisma generate
Otherwise stop the dev server before generating as advised earlier in this issue

I have error : "EPERM: operation not permitted, unlink<EMAIL_ADDRESS>i tried to delete node_modules and manually reinstall prisma and @prisma/client but not work. Help me pls

Can confirm, just had the same error. Tried installing @prisma/client manually, it seems to help. So here is a possible workaround until the problem is fixed.

Delete node_modules
Run npm install
Run npm install @prisma/client
Run npx prisma generate / npm prisma migrate dev

I have error : "EPERM: operation not permitted, unlink<EMAIL_ADDRESS>i tried to delete node_modules and manually reinstall prisma and @prisma/client but not work. Help me pls

Can confirm, just had the same error. Tried installing @prisma/client manually, it seems to help. So here is a possible workaround until the problem is fixed.

Delete node_modules
Run npm install
Run npm install @prisma/client
Run npx prisma generate / npm prisma migrate dev

I have error : "EPERM: operation not permitted, unlink<EMAIL_ADDRESS>i tried to delete node_modules and manually reinstall prisma and @prisma/client but not work. Help me pls

You have to stop the server and then run npx prisma generate.

 I stopped the server, deleted my previous migration folder because I was trying to map, then ran npx prisma migrate dev and npx prisma studio and it worked.

4. npx prisma generate

This works for me, thanks

Can confirm, just had the same error. Tried installing @prisma/client manually, it seems to help. So here is a possible workaround until the problem is fixed.

Delete node_modules
Run npm install
Run npm install @prisma/client
Run npx prisma generate / npm prisma migrate dev

This works for me. Thanks

Stopping the dev server has worked for me.

i received this error when tried to generate when the code still running on it

No need to uninstall node or prisma you just need stop the dev server

Can confirm, just had the same error. Tried installing @prisma/client manually, it seems to help. So here is a possible workaround until the problem is fixed.

Delete node_modules
Run npm install
Run npm install @prisma/client
Run npx prisma generate / npm prisma migrate dev

Can confirm faced this error and this method resolved it.

Can confirm, just had the same error. Tried installing @prisma/client manually, it seems to help. So here is a possible workaround until the problem is fixed.

Delete node_modules
Run npm install
Run npm install @prisma/client
Run npx prisma generate / npm prisma migrate dev

Worked for me. But when I ran this npx prisma db push after that, it threw this error in terminal:
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db": MongoDB database "nextauth" at "cluster0.pecwetf.mongodb.net"
Error: MongoDB error
Kind: SCRAM failure: bad auth : authentication failed, labels: {}
   0: schema_core::commands::schema_push::Calculate `from`
             at schema-engine\core\src\commands\schema_push.rs:29
   1: schema_core::state::SchemaPush
             at schema-engine\core\src\state.rs:436

2023 - Same bug

Can confirm, just had the same error. Tried installing @prisma/client manually, it seems to help. So here is a possible workaround until the problem is fixed.

Delete node_modules
Run npm install
Run npm install @prisma/client
Run npx prisma generate / npm prisma migrate dev

Manually install @prisma/client , then npm install worked for me. It's wired 😥 .

all the above solutions didn't work for me, so, I searched for a hanging NodeJS process in my task manager, I found a process and killed it. and then, it is resolved.

Just had this one, I found that the problem was that there was a nodejs instance still running that had imported prisma. Resolved by closing node. Recommend this be closed with a hotfix to better catch and label this error.

NordicBeaver's fix was only temporary for me. I found that running powershell in administrator rights did the trick in my case. However, it's obviously not an ideal solution.

Just had this issue - in my case I think the cause was that I used a different NodeJS version since the last time I ran npm install, removing node_modules then npm install fixed the issue.

Stop the dev server and run the npm prisma migrate dev command. It should work

removing the node modules entirely worked for me

if you are working with nextjs stop the server and then run npx prisma generate this worked for me :)

stop your npm server before running prisma generate

Can confirm, just had the same error. Tried installing @prisma/client manually, it seems to help. So here is a possible workaround until the problem is fixed.

Delete node_modules
Run npm install
Run npm install @prisma/client
Run npx prisma generate / npm prisma migrate dev

I have error : "EPERM: operation not permitted, unlink<EMAIL_ADDRESS>i tried to delete node_modules and manually reinstall prisma and @prisma/client but not work. Help me pls

You have to stop the server and then run npx prisma generate.

This worked for me

If there is another node instance running, then stop it and try again.

If you're using typescript try this ctrl+p Write this >TypeScript: Restart TS Server That's all
(Remember stop server before running npx prisma generate)

I can confirm, this works for me too.

This usually happens because you are trying to do this and the development mode is working
Turn off development mode and try again. I think this will solve the problem

Bug description
Following the Getting Started guide, when it gets to the point of running the "migrate dev" command, the script tries to install some packages through npm (don't know which ones) and this causes the error in title.
How to reproduce

Follow the Getting started prisma guide up to and included the "npx prisma migrate dev --name init" command.
Get the following error:

Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db": PostgreSQL database "testprisma", schema "public" at "localhost:5432"

PostgreSQL database testprisma created at localhost:5432

The following migration(s) have been created and applied from new schema changes:

migrations/
  └─<PHONE_NUMBER>0511_init/
    └─ migration.sql

Your database is now in sync with your schema.

Running generate... (Use --skip-generate to skip the generators)
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

npm ERR! code EPERM
npm ERR! syscall unlink
npm ERR! path C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, unlink 'C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node'
npm ERR!  [OperationalError: EPERM: operation not permitted, unlink 'C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node'] {
npm ERR!   cause: [Error: EPERM: operation not permitted, unlink 'C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node'] {
npm ERR!     errno: -4048,
npm ERR!     code: 'EPERM',
npm ERR!     syscall: 'unlink',
npm ERR!     path: 'C:\\Users\\mbelletti\\Documents\\Projects\\hello-prisma\\node_modules\\prisma\\query_engine-windows.dll.node'
npm ERR!   },
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'unlink',
npm ERR!   path: 'C:\\Users\\mbelletti\\Documents\\Projects\\hello-prisma\\node_modules\\prisma\\query_engine-windows.dll.node',
npm ERR!   parent: 'hello-prisma'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR!      C:\Users\mbelletti\AppData\Roaming\npm-cache\_logs\2021-09-09T08_05_23_557Z-debug.log
Error: Command failed with exit code<PHONE_NUMBER>: npm install -D<EMAIL_ADDRESS>The batch file cannot be found.

The log file is the following: 2021-09-09T08_05_23_557Z-debug.log
After this, the node_modules.bin directory no longer has the prisma executable, and the node_modules/prisma folder only contains the file that npm wasn't able to remove (query_engine-windows.dll.node).
Expected behavior
The script finishes correctly.
Prisma information
All the prisma configurations are the ones taken from the guide.
Environment & setup

OS: Windows 10
Database: PostgreSQL 13
Node.js version: 14.17.1 (using nvm)

Prisma Version
Environment variables loaded from .env
prisma                  : 3.0.1
@prisma/client          : Not found
Current platform        : windows
Query Engine (Node-API) : libquery-engine 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Default Engines Hash    : 2452cc6313d52b8b9a96999ac0e974d0aedf88db
Studio                  : 0.423.0

(I had to relaunch npm install to get prisma back)

Problem: your node server is running somewhere and using the prisma client, even if you have closed the terminal sometimes it keeps running, thats why the error is saying to first stop the prisma client and then execute the command
Solution: Just restart your computer and it will be solved!

Update the @prisma/cliente. And just delete the query_engine-windows.dll.node file and run npx prisma generate or npx prisma migrate again.
It worked for me

Stop the dev server and run the npx prisma migrate dev command. It should work

This Worked Thanks!!🤝

While deleting the node_modules folder, I found that  query_engine-windows.dll.node is open in node, and closing the dev server and prisma studio might also be a fix, instead of removing the node_modules folder

Try closing any development servers you have that uses the prisma client and then try running the command again. That's how I got mine to work.

Al eliminar la node_modulescarpeta, descubrí que query_engine-windows.dll.nodeestá abierta en el nodo, y cerrar el servidor de desarrollo y prisma studio también podría ser una solución, en lugar de eliminar la node_modulescarpeta.

Confirm solution, thanks you

for me  , deleting node_modules and running npm i solves the issue .

hey, you can try this :

First try to delete node_modules/@prisma/client
Now run command - npx prisma generate
this will install new client

Bug description
Following the Getting Started guide, when it gets to the point of running the "migrate dev" command, the script tries to install some packages through npm (don't know which ones) and this causes the error in title.
How to reproduce

Follow the Getting started prisma guide up to and included the "npx prisma migrate dev --name init" command.
Get the following error:

Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db": PostgreSQL database "testprisma", schema "public" at "localhost:5432"

PostgreSQL database testprisma created at localhost:5432

The following migration(s) have been created and applied from new schema changes:

migrations/
  └─<PHONE_NUMBER>0511_init/
    └─ migration.sql

Your database is now in sync with your schema.

Running generate... (Use --skip-generate to skip the generators)
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

npm ERR! code EPERM
npm ERR! syscall unlink
npm ERR! path C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, unlink 'C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node'
npm ERR!  [OperationalError: EPERM: operation not permitted, unlink 'C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node'] {
npm ERR!   cause: [Error: EPERM: operation not permitted, unlink 'C:\Users\mbelletti\Documents\Projects\hello-prisma\node_modules\prisma\query_engine-windows.dll.node'] {
npm ERR!     errno: -4048,
npm ERR!     code: 'EPERM',
npm ERR!     syscall: 'unlink',
npm ERR!     path: 'C:\\Users\\mbelletti\\Documents\\Projects\\hello-prisma\\node_modules\\prisma\\query_engine-windows.dll.node'
npm ERR!   },
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'unlink',
npm ERR!   path: 'C:\\Users\\mbelletti\\Documents\\Projects\\hello-prisma\\node_modules\\prisma\\query_engine-windows.dll.node',
npm ERR!   parent: 'hello-prisma'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR!      C:\Users\mbelletti\AppData\Roaming\npm-cache\_logs\2021-09-09T08_05_23_557Z-debug.log
Error: Command failed with exit code<PHONE_NUMBER>: npm install -D<EMAIL_ADDRESS>The batch file cannot be found.

The log file is the following: 2021-09-09T08_05_23_557Z-debug.log
After this, the node_modules.bin directory no longer has the prisma executable, and the node_modules/prisma folder only contains the file that npm wasn't able to remove (query_engine-windows.dll.node).
Expected behavior
The script finishes correctly.
Prisma information
All the prisma configurations are the ones taken from the guide.
Environment & setup

OS: Windows 10
Database: PostgreSQL 13
Node.js version: 14.17.1 (using nvm)

Prisma Version
Environment variables loaded from .env
prisma                  : 3.0.1
@prisma/client          : Not found
Current platform        : windows
Query Engine (Node-API) : libquery-engine 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt 2452cc6313d52b8b9a96999ac0e974d0aedf88db (at<EMAIL_ADDRESS>Default Engines Hash    : 2452cc6313d52b8b9a96999ac0e974d0aedf88db
Studio                  : 0.423.0

(I had to relaunch npm install to get prisma back)
If you are running nextjs server. Close the server and try running the command again.

$ npx prisma generate

If you are running nextjs server. Close the server and try running the command again.
$ npx prisma generate

Even I was facing this problem, then I have deleted the .prisma folder in node_modules, then I tried to generate and it was successful.

Notice that if I had my backend server running, I constantly got this error.
Once I stop the server, the error gone. My hunch is that the running server prevents deleting query_engine-windows.dll.node

Simple solution is stopping the server and then executing this command.

This is a prisma bug, stopping the server, restarting the pc, deleting the node_modules, are poor and inconvenient workarounds at best. For security reasons you cannot change an .exe file while you're running it, nor delete any .dll files it has loaded. This is for security and stability reasons. Prisma shouldn't do this.  There are windows APIs for doing this correctly and securely - prisma should use those APIs.

Simple solution is stopping the server and then executing this command.

Maybe nice to tell the user that the the server is running and it could cause problems if you want to migrate? Looking trough a lot of stuff until I saw your comment, bit waste of time.

@thebjorn Can you tell us how? Optimally of course via a PR fixing this, but if you just explain it to us we would certainly consider changing the behavior so no one has to find this issue again in the future. Thanks!

Maybe this would work?: https://serverfault.com/a/503769/96844 In any case you'll need cooperation from the process holding the file open, otherwise you'll have to use the MOVEFILE_DELAY_UNTIL_REBOOT flag to MoveFileEx.

While deleting the node_modules folder, I found that query_engine-windows.dll.node is open in node, and closing the dev server and prisma studio might also be a fix, instead of removing the node_modules folder

This works for me, and after deleting it I just ran the migration command again and it's done. Been stuck on this error. Thanks, man!
OBS: Update the prisma version and prisma client version seens to be important too.

It is because of the running next server. It is not able to mutate files as they are under usage, the OS is rejecting the request. CLose the server and editor then open the editor again and then try executing the same command. It will work. This worked for me.

This worked for me!

This usually happens because you are trying to do this and the development mode is working Turn off development mode and try again. I think this will solve the problem

THANK YOU

4. npm prisma migrate dev

incase npm prisma migrate dev doesn't work here you can try
npx prisma migrate dev this is probablly because you don't have prisma installed globally
you can install it globally and use npm prisma migrate dev

Hey everyone, I found a workaround. You have to use the binary engine for development and kill "query-engine-windows.exe" process each time there's HMR event for prisma schema, then run prisma generate.
I implemented it as a vite plugin, you can check it out here (code).

just run this script in your terminal, works like a charm:
Identify the process using the file
$process = Get-Process | Where-Object {
$.Modules -match 'query_engine-windows.dll.node'
} | Select-Object Id, ProcessName, @{Name="Module";Expression={
$.Modules | Where-Object { $_.FileName -match 'query_engine-windows.dll.node' }
}}
Display the process details (optional, for verification)
$process
Terminate the process by its ID
if ($process) {
Stop-Process -Id $process.Id -Force
Write-Output "Process $($process.ProcessName) with PID $($process.Id) terminated."
} else {
Write-Output "No process found using query_engine-windows.dll.node"
}
Run prisma generate again after terminating the process
npx prisma generate

This usually happens because you are trying to do this and the development mode is working Turn off development mode and try again. I think this will solve the problem

Thank you it worked !

 This works. After turning off dev mode, it works fine.

I have the same issue and I fixed it using these steps ps. it only works if you are using pnpm

remove the prisma client in node modules.
pnpm remove @prisma/client

add it back.
pnpm add @prisma/client

It will works now.

Try to Shut Down Your Currently running server and then migrate
Thank you so much for the suggestion to shut down the currently running server before migrating. It worked perfectly for me! I was having issues with migrations, and this simple step resolved the problem. I appreciate your help!

@janpio
Im running the generate command as part of my build process.
It's not about "dev servers" I have production servers running, I won't just stop and re-start them.
It worked perfectly at<EMAIL_ADDRESS>which was the version I used just before upgrading now to 5.17.
I'm thinking I'll have to downgrade because of it.
Please help?
I wanted to upgrade not stay at the same place

@omerman
If you shutting down nextjs server, you can generate prisma with no error and restart nextjs server so now it working

stop all instances of node.js running on your pc and run prisma generate
taskkill /f /im node.exe

I dont understand these comments. I dont want to stop all the instances of node.js..
If I stop them, my server will be down.

@omerman
I know but this is the only way to reset this but don't worry you can restart your server after you generate prisma in just the few second

@QTNAandPie Im aware.. But I have multiple nextjs apps using prisma. I dont like the idea I have to do it.
Especially because I didn't have to do it in previous versions. It's a new issue. It should be fixed by Prisma. It's not a good solution to simply kill my prod nextjs instances in order to run a script that simply generates a typescript file 🤷
I actually downgraded to Prisma v4.11 in order to keep working as usual..

I ran into this while running tests on Windows CI runners. To ensure the tests reset their state, some of them delete node_modules/.prisma (due to what the tests are testing).
There is no server to kill, so I fixed this by calling await prismaClient.$disconnect() at the end of each test that constructed a PrismaClient instance.

for me , deleting node_modules and running npm i solves the issue .

Yeah this worked for me too.

I

I ran into this while running tests on Windows CI runners. To ensure the tests reset their state, some of them delete node_modules/.prisma (due to what the tests are testing).
There is no server to kill, so I fixed this by calling await prismaClient.$disconnect() at the end of each test that constructed a PrismaClient instance.

I understand what you are saying.. but the thing is.. Im not running tests, Im not willing to disconnect prisma or kill the server.. I dont think there should be any locking of files while performing a basic operation such as generating types. I can't understand the need to lock a file while doing so 🤷

如果您运行的是 nextjs 服务器。关闭服务器，然后再次尝试运行该命令。
$ npx prisma generate

感谢，你的建议解决了我的问题

如果您运行的是 nextjs 服务器。关闭服务器，然后再次尝试运行该命令。
$ npx prisma generate

感谢，你的建议解决了我的问题

Workaround: The following generate task in package.json works for me, when I have dev server with Prisma running:
rm -rf .prisma.tmp && mv -f ../node_modules/.prisma/client .prisma.tmp; prisma generate

That cleans up .prisma.tmp and moves Prisma client, which works OK on contrary to removing Prisma client directly, which fails with EPERM.
Note, that I'm in monorepo, so I have Prisma client in ../node_modules. On single repo just use node_modules in current directory.

In dev mode it doesnt really matter. because you can simply stop your running code.
The issue here is in prod environments. I also have a monorepo that unfortunately runs on windows machine.
Prisma's engine file is locked as long as the process using it is running.(in windows) I dont think it is an actual "must" by Prisma.
I dont understand why this issue is not dealt with.

@omerman It matters for me in dev mode. I have a monorepo with running dev servers for API (Prisma/Apollo) and Web (Next.js) and the Web generate task (GraphQL codegen) depends on API generate task (Nexus GraphQL codegen) in Turborepo orchestration, as well as the build tasks do.
So I need the above workaround to make prisma generate run smoothly even when dev server with Prisma is running. Works ok on Windows/Mac/Linux.

hey, i have the same problem
this was happening because my backend was on in the another terminal
first close it then do npx prisma migrate dev/npx prisma generate

Me funciono hacer lo que dice
@ankur0999
hey, i was having the same problem
this was happening because my backend was on in the another terminal
first close it then do npx prisma migrate dev/npx prisma generate

All you have to do is just update the npm package using command
npm install -g npm@latest
and then delete node_modules and install again all the dependencies using
npm install

Looks like mine was a permissions error. I needed to run as sudo or give the folders read/write perms.

It worked when I terminated all open terminals and ran npx prisma migrate dev --name <name> & npx prisma create.

It is because of the running next server. It is not able to mutate files as they are under usage, the OS is rejecting the request. CLose the server and editor then open the editor again and then try executing the same command. It will work. This worked for me.

This is helped me. If you are using Nextjs ,close the server and then run the generate command.


Centralize strings in prep of private-repo move.

All repo url strings are now attributes. Will also need to change some occurrences over in scala/scala:
README.md:100:> set resolvers += "pr" at "http://private-repo.typesafe.com/typesafe/scala-pr-validation-snapshots/"
build.xml:474:    <property name="sbt.interface.url"     value="http://private-repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/interface/${sbt.latest.version}/jars/interface.jar"/>
build.xml:476:    <property name="sbt.interface.src.url" value="http://private-repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/compiler-interface/${sbt.latest.version}/jars/compiler-interface-src.jar"/>
scripts/jobs/integrate/bootstrap:21:# - ~/.credentials-private-repo for private-repo.typesafe.com, as follows:
scripts/jobs/integrate/bootstrap:23:    # host=private-repo.typesafe.com
scripts/jobs/integrate/bootstrap:112:privateRepo="http://private-repo.typesafe.com/typesafe/scala-release-temp/"
scripts/repositories-scala-release:3:  private-repo: http://private-repo.typesafe.com/typesafe/scala-release-temp/
scripts/repositories-scala-release:4:  typesafe-ivy-releases: http://repo.typesafe.com/typesafe/ivy-releases/, [organization]/[module]/[revision]/[type]s/[artifact](-[classifier]).[ext], bootOnly
tools/binary-repo-lib.sh:5:remote_urlget="http://repo.typesafe.com/typesafe/scala-sha-bootstrap/org/scala-lang/bootstrap"
tools/binary-repo-lib.sh:6:remote_urlpush="http://private-repo.typesafe.com/typesafe/scala-sha-bootstrap/org/scala-lang/bootstrap"

LGTM!