I'm using the ~/.docker/config.json file to store my ecr-login credentials but it keeps on getting reverted back to desktop like the following
{
"credStore": "desktop"
}
I've tried changing it to ecr-login then make the file read-only but that caused docker to crash the next time it starts up. Is there a workaround for this?
Related
I am facing weird issue, where I am unable to clear development log file contents while server web-brick up and running.
But same works fine in sublime text 2 editor ie. Clearing of development log file. This issue forcing me to restart server each and every time when I have to clear logs.
Kindly help me to avoid restarting for clearing logs. If any suggestions for workaround appreciated.
EDIT :
Observed issue with platforms windows 7 64/32 bit , windows 10 64bit(Checked on only these).
I have opened same log file with ST2 and ST3.
And tried to clear log file in ST2 and ST3, got alert message only in ST3.
For me it seems, its issue with Sublime Text 3, which is not allowing clearing of logs if used by other process.
EDIT 2 :
This is exactly the issue, I am facing right now.
I'm using electron to build a desktop application and needs to store data.
In the browser script I write
if localStorage.getItem("now") == null
localStorage.setItem("now", Date())
But this piece of code always get null for localStorage.getItem after page reload or electron application restart. The now value is always rewritten.
Disable Cache in the Network panel is not checked.
I've checked that localStorage has been written to local file /Users/user/Library/Application Support/app/Local Storage/file__0.localstorage. It appears the browser not load that file and will overwrite it on exist.
Change userData path to application directory does not help with this problem either.
I'm using electron 0.34.0 on OSX 10.11
Does someone have any suggestions to solve this?
It is possible that your app crashes when quitting or you use other ways like process.exit instead of app.quit to quit. If so, the localStorage will not be persisted by electron.
This is an extension of a question I asked here, which went unanswered. I am attempting to use the Meteor app on my iPad that I'm hosting on my own remote server. The issue is that when I run the following command, the app builds successfully:
sudo meteor run ios-device --mobile-server=XXXX:XXXX
The problem begins when I click the build button in Xcode to deploy the app to my device. It seems to build everything OK and even load the data from my remote server. But after a few seconds, it reverts back to a local database/build. When I check the Xcode log, it says "Finished load of http://meteor.local/" so it seems to be overwriting the remote data with new, local data. I'm not sure if I have something enabled that's causing Xcode to load a local database or if there's something that I have to turn off to prevent it from loading.
UPDATE:
I've resolved the issue using the suggestion from Jey DWork to apply the missing environment variables in the Meteor server startup.
The ones I added were:
Meteor.absoluteUrl.defaultOptions.rootUrl
process.env.ROOT_URL
process.env.MOBILE_ROOT_URL
process.env.MOBILE_DDP_URL
Without setting these, the ROOT_URL seemed to be getting overwritten after the initial load. As these environment variables do not seem to be documented, I'm still going to search and see if there is a different solution to this issue (as it seems strange that the app would have to re-load itself multiple times before it's usable). For now though, this is a temporary solution.
Have a look at this post :
I've understood my problem, maybe your problem is the same, all explanations here : stackoverflow.com/questions/34658956/
Your app for smartphone must be built with --server=http://IP:PORT parameters
And
Your app for server must be started with --mobile-server http://IP:PORT parameters
I'd been working on a plugin when I discovered this. I can't say for sure if this behavior happened before or not on my machine (it doesn't on our test server, a Linux box), but after attaching a file, I can't delete it until the server restarts. I can't delete through the UI or by manually navigating to the server directory and trying to delete from there.
Has anyone ever encountered this before? Could it be something environmental on my box??
Most probably it's a permission issue in that folder, which allows your JIRA user (a user under which privileges JIRA instance runs) to create files, but not to delete them (or something even more fun) :) Try deleting the temp folder (where your uploaded attachments reside) and recreate it again, adding your JIRA web user to the access list for that folder.
The workaround to delete files, when some other process is holding a lock on the file, without having to terminate that process, is to use Unlocker. But be warned, when Unlocker unlocks a file it does that in a way which does not notify the lock holder that the file has been unlocked by force. That means that the lock holder still thinks it holds the lock on the open file which it doesn't (the file handle is invalid). That means that some applications might crash due to unexpected state of the supposedly open file. Btw, I've been using Unlocker since forever and it rarely caused any crashes, but it's better to be warned.
I developed a simple plugin to bar files ending in .exe from being uploaded into my jira app. I overrode the AttachFile.doValidation() method to check for .exe in the filename. If it's there I return an error.
Now when I try to delete an attachment, 9 times out of 10 it won't work. I simply get the error "Failed to delete attachment with id {id}". Nothing in the stacktrace or logs indicated that something went wrong. Then it will suddenly delete succcessfully. I've found no rhyme or reason for this.
Again, I overrode AttachFile, not DeleteAttachment, so I don't know how my fix could be related to this problem. Could it be though??
If I remove my plugin entirely, I still get an error when I delete. The error says "The action can't be completed because the file is open in Java(TM) Platform SE binary". Somehow AttachFile() is leaving a reference to the file, but I have no clue where or how to clean up.
Permissions aren't the issue, because occasionally the delete command will work. It always works when the server first starts up, and after that only periodically.
We've come to the conclusion that this is a Windows-only problem, and Linux doesn't lock files. Our production server is Linux, so I'm not going to spend anymore time on this.