force-static broken for catch all routes

[alexanderhorner]

Link to the code that reproduces this issue

CodeSandbox

To Reproduce

1. Build the application npm run build
2. Start the application npm run start
3. Refresh the root page a few times

Current vs. Expected behavior

Current behaviour: The time changes every second

Expected behaviour: Just like can be observed on the sub directories, the page should be generated on the first visit and then statically served on every subsequent visit (time stays the same).

Provide environment information

codesandbox.io:

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.1.1-canary.72 // There is a newer canary version (14.1.1-canary.73) available, please upgrade! 
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A

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

App Router, Data fetching (gS(S)P, getInitialProps)

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

next build (local), next start (local)

Additional context

No response

_NEXT-2622

[coffeecupjapan]

@alexanderhorner
I opened a PR for this issue.

I think I fix this issue. However, maybe there are lacks of consideration for some edge cases, and therefore should investigate for this issue more.

#62757

[alexanderhorner]

Thank you. I agree it should be investigated further. I've also noticed some weird behavior with dynamicParams, wich doesn't seem to be consistent with the documentation.