So I'm trying to finish up some ClearCase work. I'm extremely new to Clearcase, keep that in mind - I've basically been stumbling through this somehow making it work until this point.
I'm using Clearcase Remote Client, and am trying to remove one of my views, but am getting the following error:
CRVAP0087E CCRC command 'rmview' failed: View path/to/int/view has a UCM deliver or rebase operation in progress.
Please complete or cancel the UCM operation before removing this view.
I tried ignoring this, but then when I try delivering the other view that I made after encountering errors with this one, I get this error:
Unable to prepare the integration view "bluhman_iOSTablet_6.4.2_int" for deliver: error detected by ClearCase subsystem
ClearCase CM Server: Error: View "bluhman_iOSTablet_6.4.2_int" is set activity to activity
"deliver.bluhman_iOSTablet_6.4.2_2.20150929.122347" which is currently involved in an
active deliver or rebase operation. The set activity of this view may not be
changed until the operation has completed.
ClearCase CM Server: Error: Resume, complete or cancel the operation in progress in view "bluhman_iOSTablet_6.4.2_int".
View "bluhman_iOSTablet_6.4.2_int" cannot be used in the current deliver operation.
ClearCase CM Server: Error: Unable to prepare view common.
Unable to prepare the integration view "bluhman_iOSTablet_6.4.2_int" for deliver: error detected by ClearCase subsystem
ClearCase CM Server: Error: View "bluhman_iOSTablet_6.4.2_int" is set activity to activity
"deliver.bluhman_iOSTablet_6.4.2_2.20150929.122347" which is currently involved in an
active deliver or rebase operation. The set activity of this view may not be
changed until the operation has completed.
ClearCase CM Server: Error: Resume, complete or cancel the operation in progress in view "bluhman_iOSTablet_6.4.2_int".
View "bluhman_iOSTablet_6.4.2_int" cannot be used in the current deliver operation.
ClearCase CM Server: Error: Unable to prepare view common.
So it seems that when I was running into all these delivery errors prior to starting this delivery, it really messed something up. But, I'm not sure what got messed up or how to remedy this situation, as I said, I'm extremely new to Clearcase and have been just barely stumbling through this.
I'm not using any sort of console to do this, and I'm very limited in what I can actually use -- I think the remote client is all I'm given access to in order to do all this, so it would be great if I could fix this in the remote client somehow.
Some details are missing from your question, but here's my interpretation:
The first problem is you're trying to remove a view (path/to/int/view) which is involved in a deliver or rebase. You ignored the error and made a different view (presumably source view) and tried another deliver, which is also returning the error:
Unable to prepare the integration view "bluhman_iOSTablet_6.4.2_int"
for deliver: error detected by ClearCase subsystem
ClearCase CM Server: Error: View "bluhman_iOSTablet_6.4.2_int" is set to activity
deliver.bluhman_iOSTablet_6.4.2_2.20150929.122347"
which is currently involved in an active deliver or rebase operation.
My guess is you are using the same target view as the original deliver. The best recourse seeing as the existing deliver is still in progress from the first view is to resume that deliver op from that view to the same target, or undo it.
If using GUI, it should detect the deliver in progress and prompt you to resume/cancel (Undo). If using the command line,
cleartool deliver -cancel -stream .... You can also use clear deliver -status -stream ... to get the status.
Once the deliver has been canceled or completed you will be able to remove the view.
Related
so I just downloaded plastic scm for my unity project today and whenever I try to checkin my changes (I have made a lot of progress on the game, so my guess is that the mass checkin is the problem) I get this error saying: "this is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server" for completely no reason, if you know how to stop this from happening, please answer my question
1- Plastic SCM error whenever I try to checkin
2- Full Window screenshot
Most of the time that error is related with network issues (Slow, unstable, high latency), you might want to consider a distributed workflow in that case: https://www.plasticscm.com/book/index.html#_centralized_distributed
A workaround is to checkin smaller chunks at a time until everything gets uploaded.
I have enabled a couple of different code scanning tools in my GitHub Actions workflow that each upload their results to the GitHub Security tab (via upload-sarif).
One of these scans produces a lot of alerts that are not relevant for my project, as it scans the built container image and produces alerts for all of the packages and utilities included in the base (Linux) image regardless of whether they are used by my application. So I have reviewed all of the alerts on the GitHub Security tab and dismissed (as "Won't Fix") the alerts that are not relevant.
Subsequent executions of the GitHub Actions workflow on the default branch work fine - the code scanning tool still generates all of the alerts, but GitHub sees that the alerts have already been dismissed and doesn't add or re-open them on the Security tab.
However, I also want to run the scan on PRs targeting my default branch in order to catch any new alerts before they are merged. But here GitHub doesn't appear to be checking that the alerts have already been dismissed on the default branch, so the code scanning check fails on every PR. Worse, if I ignore the check and merge the PR anyway, the alerts are transferred over to the default branch and need to be manually dismissed again.
Is there a workaround for this, or should I be approaching this in a different way?
I have discovered that the code scanning tool in question (Trivy) does not include fingerprints in its SARIF output, which is what confuses GitHub. I've made a feature request for Trivy here: https://github.com/aquasecurity/trivy/issues/1840
As a workaround, I've discovered that keeping the container image name static for code scanning allows GitHub's fallback deduplication logic to correctly identify duplicate alerts.
My understanding is if the bug was in Activity, the new code will be used since Activity does not have the concept of version. But what if there is a bug in Workflow code and causing some workflows to fail (or even worse, not fail but stuck), we fixed the bug and deployed the new version, but those failing workflows are stuck on old versions. Is there a way to automatically move those failed / stuck workflows to new version and re-run them?
This happening a lot to us because we just started to learn to use Cadence/Temporal
Thank you in advance!
It depends on the bug.
For bugs that cause workflow to get stuck (in Go a nil pointer dereferencing causes panic which blocks the workflow progress by default) deploying the new version of the code is usually enough to unblock them.
If the bugfix requires backwards incompatible change then the best option would be to reset workflow to the point before the bug. This way workflow will be rolled back and continue through the new code.
For situation when the breakage of workflow code is caused by a new bad build you can rollback the workers to the previous build and mark that build as broken and all workflows going to roll back their state to before that build automatically. See "Recovery from bad deployment" section of the Temporal documentation.
If you are using ElasticSearch integration then you can also perform batch reset of multiple workflows using a predicate to select workflows that match some criteria. See "Signal, cancel, terminate workflows as a batch job" section. Besides the name of the section the batch jobs apply to reset operations as well.
No matter what I do, I cannot seem to get Mylyn to stop inserting a commit message based on a Task even though that task is no longer active and closed. I've tried restarting the app, I've tried activating and inactivating tasks (which seems to simply change the commit message, although this is not consistent).
Switching to different perspectives also does not resolve the problem.
There must be some switch somewhere that I am neglecting to turn off. Please help me fix it!
Summary: Mylyn automatically creates meaningful commit messages based on the tasks you've worked on. To disable them see the Disabling section below.
Disabling: To disable Mylyn's commit messages go to Preferences -> Tasks -> Team and remove all content from the Commit Comment Template.
Details: Mylyn commit messages are automatically generated by using your context to determine which tasks where active when you changed the set of files you are about to commit. Thus, if you had the task implement the submit button active when you changed the file Submit.java then when you commit Submit.java the commit message will automatically be filled in with implement the submit button and a link to that task. Here's an example of a filled in commit message for the task improve upon associations prototype:
Many people find this more convenient than having to copy and paste from your task or type in a commit message yourself. Additionally, there are several advantages to having the commit message filled in by Mylyn, such as having traceability back to the task and having correct annotations. Here's an example of the traceability that having Mylyn-generated commit messages allows. You can see that the code annotations have links directly back to the tasks.
See this article for further details and advantages: Mastering Change-Sets
David Shepherd, Tasktop Technologies http://www.twitter.com/davidcshepherd
Go to Preferences -> Tasks -> Team : clear the Commit Comment Template
i have implement a ResourceChangeListener and catch the save event. Now i want to add some code to the File. How i can do that?? I try to use BufferedReader/BufferedWriter but than the i must refresh the file. If i try it with IFile.refreshlocal() i got an error that the file is lock?
May be the article "How You've Changed! Responding to resource changes in the Eclipse workspace"
You need to access a resource in a workspace in a thread safe manner. (From this post)
If you are making resource changes outside of a IWorkspaceRunnable (old) or WorkspaceJob (new), that could be the cause of your "is locked" message: the workspace could be
modified at anytime.
Placing your resource changes inside a WorkspaceJob ensures you will not have lock issues with other threads.
You will not need to update the resource view tree or run a refreshLocal(). WorkspaceJob, if all goes well, will handle that for you.
See also article "On the Job: The Eclipse Jobs API" for more on the WorkspaceJob.
[...] our job will not run if a scheduling rule is held by another thread for the workspace root itself or for any of the resources contained in the workspace.
Once this job is running, no other threads will be able to obtain a rule for the above-mentioned resources until the job in our example completes.