bug(starters): starter pages are not created for some starter repos

[muescha]

Description

for some starters in the starters.yml there are no starters pages created and creating a 404. with the gatsbyjs starter there is a page with blurred preview but with fore reload there is an error page.

this starters are affected:

• gatsby-starter-stripe
  • https://www.gatsbyjs.org/starters/brxck/gatsby-starter-stripe/
  • https://github.com/brxck/gatsby-starter-stripe

Steps to reproduce

open starter page

Expected result

should be an page

Actual result

404 page

Related Issues

• Update docs/processing-payments-with-stripe #22431 Update docs/processing-payments-with-stripe
• bug(starters): starter pages are not created for some starter repos #19849 bug(starters): starter pages are not created for some starter repos
• Add link checker for Gatsby Docs #19267 Add link checker for Gatsby Docs

[pieh]

At every build there is percentage of sites/starters that fail to take screenshot of sites. To not fail .org builds completely we skip them. It's not always same demo sites also - the screenshot service is pretty flaky. For now we skip those in builds, but maybe instead we could show them with some placeholder image/screenshot

[muescha]

yes - a placeholder would be better instead of skipping the starter

[muescha]

note for changing this:

• the field hasScreenshot is used in more places and not only at the reporter.warn lines: search for hasScreenshot

[pieh]

Right, this is how we skip displaying full entries right now. We could instead opt into removing those filters from queries and in right components fallback to some placeholder images (or just don't show anything, depending on layout? https://www.gatsbyjs.org/starters?v=2 will need some image to keep grid layout, but details page - https://www.gatsbyjs.org/starters/gatsbyjs/gatsby-starter-blog/ could just skip the screenshot I think )

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[github-actions]

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community! 💪💜

[muescha]

it is still a bug (#23383)

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[LekoArts]

Since the starters are now sourced from WordPress this issue was resolved.