Replies: 2 comments 2 replies
-
More debugging that I did: When I run following command from the container shell for new changeset, it prints the file correctly:
But when I run same command for old changeset (around 2 years old), I get error:
But this file exists at that changeset. |
Beta Was this translation helpful? Give feedback.
-
Documenting all the details here... to open a feature request or request for contribution from p4 experts. When a user clicks on History link of a file, it runs following command on backend and based on output it displays the result:
Above commands returns historical data which UI formats to display on UI. However, UI ignores some field from above output such as:
These are the point where the file was moved from one branch to other branch. So instead of ignoring this, if we can keep this value in some variable and while getting the content of file with old branch, if we can use it then it can display the result. So, instead of running, [/usr/bin/p4 print -q $'example.h@8018060'] in directory '/opengrok/src/project_name/' run [/usr/bin/p4 print -q '<full_depot_path>' ] based on the above info, then it can give the file content. (full depot path available from above history info) Changing branch is very common in perforce and so this can solve a big issue for user. Although I'm not familiar with Java, I will attempt to explore the code to see if I can implement these modifications on my local machine. In the meantime, I welcome any Perforce experts to provide their insights. |
Beta Was this translation helpful? Give feedback.
-
Its regarding the Perforce repository, where it seems to be an issue occurring with most of the files. This problem could be related to a configuration error or something that I think can be resolved. I am currently using a Docker version of OpenGrok, where the source code is mounted on a container.
Let's consider the file "example.h" as an example. When I open this file in OpenGrok and click on "history," I can view all the available historical data for the file. I can even select specific changesets, which takes me to the file at that particular changeset. However, for some older changesets (more than two years old), the page appears blank.
Interestingly, there are no error messages in the log, and it returns an exit code of 0.
Any idea what could be going wrong or any debugging tips?
Beta Was this translation helpful? Give feedback.
All reactions