When I run arc diff, it asks Autoland after builds pass and reviewers approve (Default Y)? [Y/n].
Can we change the setting to disable the autoland by default and avoid getting this question?
I learned that there is a tag/flag for it. We can disable it by
arc diff --noautoland
Related
I'm trying to switch to Latex Workshop for VSCode, however I cannot get it to build after change.
I have it enabled in the settings, however it does not autobuild. After building manually the log says
Auto Build Run is temporarily disabled during a second.
at some point. I also made sure that Polling is active.
What is that supposed to mean and what is the fix?
I tried to set up Latex Workshop to autobuild, but it does not.
I think this is a bug. The way that I got auto build working was to enable autosave, because the "build on change" setting does seem to work and so the auto save triggers an auto build. Some instructions to enable autosave can be found e.g. in an answer here (in conjunction with the settings you mention).
I'm not entirely sure how I get into this situation, but fastlane_tmp_keychain-db becomes my default keychain after a build, and I can't figure out how to un-set it.
There are no options here to change the defaults. Why did fastlane do this and how do I undo it?
It's definitely the default; I get "Spotlight wants to use fastlane_tmp_keychain-db" on login.
Took me longer to figure out than I care to admit, so I'm documenting this here also for my own reference...
Open up Keychain Access, select the fastlane_tmp_keychain-db keychain on the left and then select Edit > Delete.
In the following dialog choose "Delete Keychain File" to permanently delete it.
This should fix it.
The fastlane_tmp_keychain-db shouldn't be there in the first place. It's temporary and supposed to be deleted automatically after the lane is executed. However, judging by the number of reports and questions on this topic lately, it seems to have broken recently. Deleting it should fix any issues you might have with your Mac and shouldn't affect your Fastlane project in any way.
It happened for me as well and I found this thread. But the solution of André does not work for me, Delete action is grayed out and disabled in Edit menu.
But I found another solution to delete the keychain:
fastlane run delete_keychain name:fastlane_tmp_keychain-db
and set login keychain as default again:
security default-keychain -s ~/Library/Keychains/login.keychain-db
you may have to restart 'Keychain Access' to show changed default keychain
Finally managed to get rid of if using the following. Add this to your fastlane file;
desc "delete created keychain"
lane :delete_chain do
delete_keychain(name: "fastlane_tmp_keychain-db")
end
Then run sudo fastlane delete_chain. Note: This will (likely) destroy anything that has been saved into the keychain while it was considered the default. Therefore consider backing it up first.
I'd like to configure VS code to work the same as pretty much every editor I've ever used which is to save only when I tell it to and to ask to save modified files if I try to quit.
I've set Auto Save to "off"
I've set Hot Exit to "off"
As it is if I have modified files and I choose quit it just exits immediately, losing all my changes. I could have sworn this used to work.
version 1.41.1
At least, VSCode 1.51 (Oct. 2020) mitigates that situation with:
Prevent accidental close
A new setting window.confirmBeforeClose was added to show a confirmation dialog before closing or leaving the workbench.
Possible values are:
keyboardOnly: The confirmation will only be shown when you use a keybinding to close (for example Ctrl+W or Cmd+W). (default)
always: The confirmation dialog will always be shown, even if you close from a mouse gesture.
never: The confirmation will never be shown.
But, that was only for Web.
VSCode 1.66 (Apr. 2022) will propose the same for the desktop app.
See issue 14710 and PR 147242
The issue was if you're in extension develop mode it just exits. If I pass in --extensionDevelopmentPath some/path then the save options are ignored. Without that it works as it's supposed to.
Apparently that's by design
https://github.com/microsoft/vscode/issues/71405
I am used to the focus follows mouse option for years.
In the VSCode editor I want to switch between the integrated terminal and the code writer by simply focusing the cursor on them.
For example in Geany editor:
Does anyone know how to enable focus follows mouse from settings or using any simple hack while trying to move between the code writer and terminal?
The simple answer is it's not possible at the moment. There have been numerous issues raised in the past (#25685, #44214) and they have been closed because "the number of votes ... and duplicate issues" are not high enough. Go out and raise an issue and get others to vote on that issue.
There was a pull request made a couple of years ago that would introduce a focusOnHover setting. This appears to resolve the issue but it has not been accepted and is now a bit stale and needs some work. So you could for VSCode (for yourself), apply the pull request and then build it.
I am keen on this feature as well.
It is now a candidate for the backlog, see https://github.com/microsoft/vscode/issues/93772 (Provide a "focus-follow-mouse" setting)
So upvote it if you want this. It needs 20 votes to move to the backlog.
I'm using Eclipse with Perforce version control. In P4V I check out the files I want to modify, making them readonly, but when I open a file I didn't check out in Eclipse it prompts me if I'd like to make it writable and defaults the anser to 'Yes.' If I'm not paying attention and just typing I unintentionally make files writable and then have to reconcile with P4V.
Is there any way to force Eclipse to just disallow changing the read-only flag on files?
I do not know the answer to your actual question, but you may be able to work around this issue by using Perforce's Eclipse plugin. That way, if you unintentionally modify a file, it will be in your pending CL where you can review the change and revert if it necessary.
http://www.perforce.com/perforce/products/p4eclipse.html
In Eclipse , click on Window-> preferences->Team->{selct ur source, in your case it should be P4V } . In there you have some default settings done. You can apply them as per your need. I had the same issue with MKS and me going there resolved the issue.
MAKE SURE YOU REFRESH AND RESTART ECLIPSE TO SEE THE CHANGES. SOMETIMES ECLIPSE DOES NOT RECOGNIZE THE CHANGES MADE IN PREFERENCES.
I hope this helps you too.
Setting perforce_auto_checkout property to false in Eclipse will give you the desired behaviour.