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

Version comparison crashes in a new clean installation #10673

Open
joanvf opened this issue Jan 19, 2025 · 3 comments
Open

Version comparison crashes in a new clean installation #10673

joanvf opened this issue Jan 19, 2025 · 3 comments
Assignees
Labels
status: cant-reproduce If an issue cannot be reproduced

Comments

@joanvf
Copy link

joanvf commented Jan 19, 2025

Describe the Bug

Version comparison crashes in the latest version after a new clean installation. See screenshot in the reproduction steps

Link to the code that reproduces this issue

https://github.com/joanvf/payload-version-bug

Reproduction Steps

  1. Create a clean installation with npx create-payload-app

  2. Create a new collection with versioning and drafting enabled on a regular text field:

export const Pages: CollectionConfig = {
  slug: 'pages',
  versions: {
    drafts: true,
  },
  fields: [
    {
      name: 'title',
      type: 'text',
    },
  ],
}
  1. Import the new collection in payload.config.ts
    collections: [Users, Media, Pages]

  2. Go to admin, create a few versions and try to compare. You will see the crash both in the console and on the screen.
    [11:56:51] ERROR: invalid input syntax for type integer: "NaN"

Image

Which area(s) are affected? (Select all that apply)

area: core

Environment Info

Node: 23.4.0
payload: 3.17.1
next: 15.1.5
@joanvf joanvf added status: needs-triage Possible bug which hasn't been reproduced yet validate-reproduction labels Jan 19, 2025
Copy link
Contributor

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@beta -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

@paulpopus paulpopus self-assigned this Jan 20, 2025
@github-actions github-actions bot removed the status: needs-triage Possible bug which hasn't been reproduced yet label Jan 20, 2025
@paulpopus paulpopus added the status: cant-reproduce If an issue cannot be reproduced label Jan 20, 2025
@paulpopus
Copy link
Contributor

Hi I'm failing to reproduce this, can you confirm for me which database are you using?

@joanvf
Copy link
Author

joanvf commented Jan 21, 2025

Postgres. I tested with:

  • Postgre 17
  • Vercel Postgre

Let me know if you can reproduce with this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: cant-reproduce If an issue cannot be reproduced
Projects
None yet
Development

No branches or pull requests

2 participants