Can no longer use time lapse view in the epic licensee perforce endpoint (too many rows scanned)

Development Pipeline & Plugins
, ,
1

This used to be possible but within the last couple of months starting spewing out an error message. It was a really useful way to be able to find more information about why a certain change was done in the engine in order to learn more how to work around issues, when to use features, integrate bug fixes from upstream, etc.

Is it intentional that this stopped working, is there a recommended way to do this instead for licensees?

2

Steps to Reproduce

  1. Log in to the licensee perforce endpoint in p4v
  2. navigate to //UE5/Main/Engine/Source/Runtime/Engine/Private/Animation/AnimSequence.cpp
  3. Right click and choose “Time lapse view”
  4. Notice that a message with “Too many rows scanned (over 50000000); see ‘p4 help maxscanrows’” pops up.
3

Hey there,

I just tried this internally against our p4 server, and had no issue with this specific file (but configs could be different between servers of course). Let me chat with the team internally regarding the licensee endpoint. In the interim, you could probably try p4 annotate and p4 filelog to achieve similar results.

Julian

4

Hey there,

One of our internal users has also tried this against the licensee p4 via command line:

p4 fstat -OL -L //UE5/Main/Engine/Source/Runtime/Engine/Private/Animation/AnimSequence.cpp#0 p4 filelog -1 -l //UE5/Main/Engine/Source/Runtime/Engine/Private/Animation/AnimSequence.cpp p4 annotate -a -q -t -c -dl //UE5/Main/Engine/Source/Runtime/Engine/Private/Animation/AnimSequence.cppand no maxscanrows issue. Can you give this a try from command line perhaps? Another hypothesis is that this could be occurring when run from within a workspace in p4v (as some fstat commands can behave differently within this context).

Kind regards,

Julian

5

Hey Julian,

Thank you for the quick reply!

I’ve tried running those commands and they all run successfully (the first one says no such file). In p4v I am trying to open the time lapse view in a context without having any workspace selected. I am not aware of having made any changes there, so I’m curious why this started failing on my end. I just tried and it appears to fail when connecting from port 1666 as well as 1667.

Alright after further investigation I found that I may have changed this setting locally to “Originating changelist history”. When changing it to “Direct history” here everything works as before again. Apologies for the confusion.

[Image Removed]