Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update engines to v2.26.0-13.a9966aa784861dee7e6b2a90950874cbaf7b4984 #7796

Merged
merged 2 commits into from Jun 23, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 21, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@​prisma/engines 2.26.0-7.473f96e8dcb29039719059f8e9ac32c14a63a9f6 -> 2.26.0-13.a9966aa784861dee7e6b2a90950874cbaf7b4984 age adoption passing confidence
@​prisma/engines-version 2.26.0-7.473f96e8dcb29039719059f8e9ac32c14a63a9f6 -> 2.26.0-13.a9966aa784861dee7e6b2a90950874cbaf7b4984 age adoption passing confidence

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@Jolg42
Copy link
Member

Jolg42 commented Jun 22, 2021

Result of prisma/prisma-engines#1945

Integration will be done with #7620

@renovate renovate bot changed the title fix(deps): update engines to v2.26.0-7.473f96e8dcb29039719059f8e9ac32c14a63a9f6 fix(deps): update engines to v2.26.0-8.a06ab528db16c04bc97ae9edf08d6dcbfa7ce889 Jun 22, 2021
@renovate renovate bot force-pushed the renovate/engines branch 2 times, most recently from fe88cfd to 771261f Compare June 22, 2021 17:10
@renovate renovate bot changed the title fix(deps): update engines to v2.26.0-8.a06ab528db16c04bc97ae9edf08d6dcbfa7ce889 fix(deps): update engines to v2.26.0-10.4778706e0163559cd391ce644ab95c9a48b369ea Jun 22, 2021
@renovate renovate bot changed the title fix(deps): update engines to v2.26.0-10.4778706e0163559cd391ce644ab95c9a48b369ea fix(deps): update engines to v2.26.0-11.c1fcbb503125a193f54f46920f59da1b6c6b859e Jun 22, 2021
@@ -3765,7 +3765,7 @@ Object {
"authorId",
],
"relationName": "PostToUser",
"relationOnDelete": "NONE",
"relationOnDelete": "Cascade",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be related to prisma/prisma-engines#1947 (comment)

Not sure about the other changes, could you check @williamluke4 @millsp ?

Copy link
Member

@janpio janpio Jun 23, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to double check why the relationOnDelete changed even when the preview feature is not enabled. This will affect users potentially now.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pimeys gave me context that this is not used in Prisma anywhere.

I just checked the community generators, none use relationOnDelete in code as well.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

0: sql_migration_connector::flavour::postgres::create_database
with self=PostgresFlavour { url: \\"<REDACTED>\\" }
at migration-engine/connectors/sql-migration-connector/src/flavour/postgres.rs:117"
Please make sure your database server is running at \`doesnotexist\`:\`5432\`."
Copy link
Member

@Jolg42 Jolg42 Jun 23, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These 2 changes are expected ✅

Comment on lines +27902 to +27904
exports[`getDMMF chinook introspected schema 1`] = `842348`;

exports[`getDMMF chinook introspected schema connectOrCreate 1`] = `842601`;
exports[`getDMMF chinook introspected schema connectOrCreate 1`] = `842348`;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's this?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The size/length of a JSON stringified dmmf...

Not super useful like this to know what changed...!

test('chinook introspected schema', async () => {
const file = fs.readFileSync(
path.join(__dirname, '../../fixtures/chinook.prisma'),
'utf-8',
)
const dmmf = await getDMMF({
datamodel: file,
})
const str = JSON.stringify(dmmf)
expect(str.length).toMatchSnapshot()
})
test('chinook introspected schema connectOrCreate', async () => {
const file = fs.readFileSync(
path.join(__dirname, '../../fixtures/chinook.prisma'),
'utf-8',
)
const dmmf = await getDMMF({
datamodel: file,
})
const str = JSON.stringify(dmmf)
expect(str.length).toMatchSnapshot()
})

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The length of the stringify dmmf 😕

Copy link
Member

@janpio janpio Jun 23, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can give toMatchSnapshot() a string as single param, then it uses that to name the snapshot. But 🤷

Comment on lines -28495 to -28512
Object {
"inputTypes": Array [
Object {
"isList": false,
"location": "scalar",
"type": "Int",
},
Object {
"isList": false,
"location": "inputObjectTypes",
"namespace": "prisma",
"type": "IntFieldUpdateOperationsInput",
},
],
"isNullable": false,
"isRequired": false,
"name": "id",
},
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is causing this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are currently investigating

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are expected changes as this test does not have a datasource. Meaning that these operations are not supported. cc @dpetrick

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, the gh ui is a bit screwed up here. Probably due to the large size of the file. Basically, the snapshot indicated is incorrect. It is not getDMMF model with autoincrement should fail if mysql but actually getDMMF simple model

Copy link
Member

@janpio janpio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good generally, the removals from the snapshots make me nervous though (see comments).

@renovate renovate bot changed the title fix(deps): update engines to v2.26.0-11.c1fcbb503125a193f54f46920f59da1b6c6b859e fix(deps): update engines to v2.26.0-13.a9966aa784861dee7e6b2a90950874cbaf7b4984 Jun 23, 2021
Copy link
Member

@Jolg42 Jolg42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want to make the snapshot file smaller in a separate PR because it got over +30k lines 😓
#7829

@Jolg42 Jolg42 merged commit 9062fa3 into master Jun 23, 2021
@Jolg42 Jolg42 deleted the renovate/engines branch June 23, 2021 14:53
Andrew-Colman pushed a commit to Andrew-Colman/prisma that referenced this pull request Aug 7, 2021
…4cbaf7b4984 (prisma#7796)

Co-authored-by: William Luke <william@ordino.ai>
Co-authored-by: Joël Galeran <galeran@prisma.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants