Recently perforce started complaining with:
Invalid changelist number 'default <other-user>#<workspace>'
when a user, other than <other-user>, switches to that <workspace>, unshelves stuff into that <workspace> etc.
Acknowledging the error one may proceed, but it would be nice to know how to get rid of this warning.
Related
I have a process which zips a file and emails it on. The process works most of the time. However, every so often I get an error message similar to the below.
ERROR: System Exception : Could not execute code stage because exception thrown by code stage: Could not find a part of the path 'T:\Path\Folder\File.zip'.
This is strange as it is able to find the original excel file, then zip it.
If I use the location from the error message I am able to find the file.
Is there an issue with the time it takes for the machine to find the file? Is this a bug?
It may happen that the file is getting zipped and you are trying to pick it up for sending mail, So solution Can be
Give some wait of 1 or 2 sec after zipping (as it may require some time for finishing work Not sure.)
While sending mail please ensure the file exists at location
If Point 2 is true, send the email with attachment
If point 2 is false, Raise the error to main process: "Zipped file not found"
After the zipping the files, if not created/zipped retry for 3 time or you can raise the error "Error: while zipping the files".
Ensure that zip file name should not contain any special character like ` , :
By doing so, we can able to find where the exact error is, whether is is on zipping code or file existence.
On Linux, after a review has been completed on a CL(changelist), the
p4 submit
fails validation indicating a file has changed after the review. Example:
Submit validation failed – fix problems then use 'p submit -c 123456'.
'changeContent' validation failed: This file has been changed between the time it was reviewed and the time it was committed, starting on line 2:
But, the file hasn't changed. This doesn't happen all the time, just some times. When it happens, it doesn't matter how many reviews get completed on the CL, it will never submit. We're forced to move the changes over to Windows and review/submit them from there. Is there any solution to it?
The short answer is that your changeContent trigger is rejecting the submit. Fixing or disabling this trigger should allow the submit to proceed.
As far as speculating about what about this trigger could be broken, Bryan's suggestion about line endings is a good one. Maybe your Linux client is using share and one of your Windows clients is using unix? That's a recipe for a bad time for the Linux client.
I'm running tomcat 6, and I get a warning ONCE, follow with that note,
Note: further occurrences of Parameter errors will be logged at DEBUG level,
But they aren't logged anywhere, or at least I can't find them. But what I really want is for all the occurences to keep showing in my log, because when I try to recreate the warning, well, they aren't showing anymore.
I have in my loggging.properties the next line:
1catalina.org.apache.juli.FileHandler.level = FINE
which is supposed to log everything, and I have also tried ALL and I still get the warning only ONCE.
What do I need to change so the warning shows everytime?
I'm running p4 interchanges -b my_branch, and I get a ton of results, the first one being a changelist that we integrated a long time ago.
So I try to integrate again, but p4 integrate -b my_branch //...#changelist,#changelist just returns "All revision(s) already integrated".
The only way to unblock this is to do a forced integration (-f in the integrate command) and then simply accept target (-at when resolving), and that works - p4 interchanges then no longer lists this changelist.
But how can Perforce get into this state to begin with? This happened after we've done a bunch of integrating across multiple branches, but I nothing that I'd think would cause a changelist to become "unintegrated" somehow.
This is on a 2014.1 server.
Thank you for specifying your server version.
The 'p4 interchanges' command can give the "All revision(s) already integrated" message with misleading results when cherry-picking is involved.
There is a command line example here:
http://answers.perforce.com/articles/KB_Article/Cherry-Picking-Integrations
You could also be affected by a bug that was patched in 2014.1 listed here in the server release notes:
http://www.perforce.com/perforce/doc.current/user/relnotes.txt
Bugs fixed in 2014.1 PATCH5
#880506 (Bug #71725) **
The istat.mimic.ichanges configurable controls the reporting
of revisions between stream and parent. If set, istat will
not report cherry-picked revisions already present in the target.
The default behavior will report any changes not credited, even
when the content may already be in the target.
If you would like, you can pull the most recent build of the server P4D for your OS from our ftp site: http://ftp.perforce.com/perforce/r14.1/
REFERENCE
http://answers.perforce.com/articles/KB_Article/Integration-Changes-Reporting
I want to create a p4 branch based on branch mvs_1211_hf at this label CC2P4_MVS_1211_HF_PILOT1, but the p4 command response is not my expectation. Anyone can help on this? Or is there any ways to create branch in p4? Thanks in advance!
Here is the p4 command i run:
p4 integ //depot/MVS_IMPORT/mvs_1211_hf/tms_dev/...#CC2P4_MVS_1211_HF_PILOT1 //deport/1211_hf/...
Here is the p4 complains:
//deport/1211_hf/... - must refer to client 'ruilong_mvs_1211_hf_pilot1'.
Best regards,
Ruilong
Typical errors include the ones previously mentioned, plus:
//depot1/... - must refer to client 'clientname'.
Check the client workspace view by running:
p4 client -o clientname
Check the "View" lines in the client workspace specification to confirm that the file specification used in your Perforce command (or appearing in the error message) falls within your workspace view.
If needed, change the client workspace by running:
p4 client clientname
Find more at: http://answers.perforce.com/articles/KB_Article/Common-Permissions-and-File-Access-Problems
Thanks
I received this error, when the path simply did not exists... had a typo :/
The must refer to client <client> error is the generic error given when an absolute path is neither a valid depot path nor a valid client path within the context of the current client. In this case, the cause of the error is that you typed //deport instead of //depot.
It would be more accurate for the error to say must be a depot path or a client path referring to current client <client>, but Perforce error messages tend to err on the side of brevity.