Assembla Perforce wont submit a large number of files - version-control

I have 1000+ files marked for add that I would like to submit using perforce. During the submit everything seems to work fine but after an hour or so into the submit, using the p4v client, I get an error saying "unable to connect to server...as user... try reconnecting"
This seems to happen every time I the p4v client to submit. Also tried using the commandline and get this message after a while into the submit saying "ssl send failed", "cannot find file specified WSAECONNABORT"
I suspect it has to do with SSL: I am currently hosting my perforce server on assembla.com as they wont give me the option to disable SSL. Is this an SSL problem?
How can I go about solving this?
Pretty desperate and grateful for help.
I've tried the following to no avail:
uninstalling and reinstalling
downgrading p4v client versions,
x86 and x64 bit versions of the p4v client
Ethernet instead of WiFi
During the submit everything is fine:
After about an hour I get this error:
If I press the "close p4v" button, this pops up:
Since p4v is giving me all these errors, I try to submit vi
commandline but still get error about an hour into the submit saying:

SOLVED IT! instead of trying to submit all the files marked for adds in one big chunk, I submitting it in small portions at a time like 300 or so instead of submitting all 1000+ files at a time.
so to recap the solution to this problem is submit in small portions instead of submitting them all at once.
I hope this helps anybody!

Sounds like the Perforce server is running out of resources. In Perforce, submits are atomic; It either totally works or totally fails. With such a large submit, if the server ran out of memory, or temporary disk space or something, and choked, the submit would fail. As you found, submitting in more manageable chunks doesn't trigger it.

Related

Thunderbird: Keeps asking me to add security exception

I've been using Thunderbird for ages without any (real) problems. A few days ago, Thunderbird updated to version 78.5.0. Shortly thereafter the problems started. I can't remember if it started immediately after the update so I'm not sure if the update was the direct cause.
Anyway, every time I try to retrieve my mail (by clicking "Get Messages") a pop-up appears:
This pop-up isn't new to me since I'm using my own mail server with a self-signed certificate. So every time I update the certificate, I get this popup. It is new however the pop-up appears while nothing has changed (other than Thunderbird updating).
If I click "Confirm Security Exception", the popup disappears but no mail is retrieved. If I click "Get Messages" again, the pop-up reappears. Oddly enough, If I go to Thunderbird's Certificate Manager, I see the certificate was actually added.
So that's one strange thing. It isn't the strangest thing however. What's even stranger is that the location (email.glasshouse.nl:995) isn't the address of my mail server. If I look under Thunderbird's "Server Settings", I see the correct address. Even if I change the server address to something else (the IP address for instance), the pop-up still displays email.glasshouse.nl as location. I'm not worried this is some kind of hack or virus or malware since I recognize the address - it's the mail server I used well over ten years ago (in Thunderbird).
So what is actually going on here? And more important, how can I solve this so I can get to my email again?
Thanks in advance!
Had some time this morning and did a bit of digging.
There is a cert_override.txt file in your thunderbird profiles directory, stop thunderbird, open it and change the wrong/invalid hostname to the correct one, save and start thunderbird.
On the file itself it says:
# This is a generated file! Do not edit.
So editing it may not help!
My problem is really similar, every time i reboot Windows 10, Thunderbird asks again for adding the exception; please note that i had also verified at ThunderBird start that the exception it will add is already present there, so after the window where you tell it to store it permanently nothing is changed in the configuration of certificates exceptions.
I my case is Avast the one that cause the problem, since deactivating eMail scan the problem does not show until i reactivate Avast mail shield.
The weird thing id that in old versions of Thunderbird / Avast / Windows 10 that problem (re-ask for exception after windows reboot) never appeared.
Hope a fix is found soon, it is getting mad a lot of people.

pgAdmin-4 does not open; throws a 'Can't reach this page' error in the browser

Disclaimer: I'm answering my own question.
I've just installed Postgres(version does not matter, I checked) and pgAdmin-4;
However, when I try to launch pgAdmin-4, it says 'Can't reach this page'.
I looked it up, tried everything, including pg_hba.conf, pg_dba.conf modifications.
The solution sounds really simple: Change your default browser to Chrome/IE(tried these). It does not open on the MS Edge browser.
I had it as default, since I was working on other html files, and didn't want them to interfere with Chrome tabs that were already open on opening those files.
Wasted a whole day on this, especially none of the signs pointed to a browser issue. Hope you aren't stuck on this!
If this does not work, you might want to look here: pgadmin4 : postgresql application server could not be contacted.
the error message on Edge

Flash not running debugger any more. Possible socket issue in Windows-10?

Bounty Update
I am leaving the question essentially the same, but I just want to point out at the beginning here that I'm most interested in help trying to get the socket between flash (Adobe Animate) and the native debugger working again, as I believe that is the issue I'm having. Or is it a socket between flash and Windows?
Original Question
I've apparently turned something off? Even when I write really bad code (like trying to call a function that isn't there or divide an integer into a fraction), the flash player boots, shows a background color and stops there. No messages in the output window or compiler errors window. If I fix my code, it all runs fine, but for about 30 minutes (ever since I started trying to work with bitmaps for a sprite sheet) I get no runtime errors no matter what kind of mistake I type in my code. Anyone know how to turn it back on?
I've checked my actionscript settings and I have both warning mode and strict mode checked on.
Could it be a socket issue? I admit I have little to no experience working with sockets and only a surface understanding of what that even means. I've added the socket tag. If someone can see that this is clearly nothing to do with sockets, by all means, I'll remove the tag.
UPDATE: 6/22/16
I just reinstalled Adobe Animate CC 2015.2 and no change. I'll try compiling it in flash builder when I get a chance to help pigeon hole the problem. (Edit 6/24: flash builder worked! But my trial version expired the next day so is no longer a viable option).
And I just tried something in the command prompt in Windows 10 as an administrator:
netsh winsock reset catalog
netsh int ip reset reset.log hit
which I found another user on flashdevelop.org used to fix a similar issue, but no change.
And I just tried debugging in Flash Builder. It worked fine (debugger caught bugs) but my trial version expired the next day.
update 6/24
I've tried launching debugger for AIR from within the Adobe Animate CC IDE and it works fine if there are no bugs; it fails to do anything visible (no Iphone emulator, no swf window) if I put a typo or error in the code.
I also just deleted winsock and winsock2, rebooted Windows, then reinstalled winsock and winsock2. No change.
update 6/25
Just tried a system restore in Windows to set all my files and settings and drivers etc. to the way it was a week and a half ago... Also completely uninstalled all Adobe products and reinstalled. No change. I can only imagine that wiping my hard drive and reinstalling Windows would do the trick, but come on, it hasn't come to that has it?
As VC.One suggested, I checked the compile error window (cannot believe I didn't check before! Maybe when I checked before there were no compile errors... Only runtime errors?) and the errors are showing up there. Does this mean that it's catching compile errors but just not runtime errors?
When you force/test a runtime error... make sure you check
Compiler Errors (ALT+F2) and also Output (F2). By Output I mean the window that shows traces (and runtime issues). One of those two should have some feedback for you.
A possible solution is to save a new Workspace. So with those windows for Compiler Errors and Output both open (or tabbed, I tab them next to my Timeline) go to Window (in top options like File/Edit/Debug etc) and choose Workspace, then into that you choose New Workspace. Give it a name in the pop-up and okay everything.
Flash should always load that current workspace (next time, go to Workspace option again, check that your specified workspace [by name] has a tick next to it...).
Possible pitfalls:
1 - Use the debug player
2 - Make sure there isn't somewhere a try/catch enclosing the portion of code that triggers the event that may lead to an error
3 - Socket issue: may be exported in debug mode but swf cannot connect to debugger (it waits in a blank state for 60 seconds I guess)
4 - Does it compile ok? If there are compilation errors you may get an SWF anyway but then it will not start
...

Unable to save or load my code in the IBM Swift Sandbox

Whenever I attempt to Save Code of mine, the Sandbox gets stuck on "Saving Snapshot" with the little dots jiggling below.
Also, when I attempt to Load Code that is something other than the sample code tab, it just says "Loading".
I've tried various browsers, and disabling any adblock or Ghostery-type utilities, without any success.
It does seem to 'Autosave' what I am working on, but that's about it and I can't even give the code a save name.
Are you others experiencing this situation also, with the IBM Swift Sandbox?
https://swiftlang.ng.bluemix.net/
It appears that our database server has gone down, since we can't ping it. We don't have the appropriate error checking in place at the moment, but we're going to be updating the code so that we handle these situations a bit more gracefully, instead of just hanging forever on a load/save dialogue. Thanks for bringing this to our attention!
EDIT: our database server is back up, and we've also pushed a code change so those database requests will time out and fail more gracefully.

Changes in Umbraco CMS does not update at front-end instantly

I have an issue in updating contents in Umbraco. Whenever I update something in Umbraco, I have to wait at least one hour, sometimes 12 hours to see the changes at front-end.
The only way to see the changes immediately at front-end is "empty the connection string value umbracoDbDSN and refresh the page, then put the connection string back and refresh the page". I have to do everything I update something in CMS.
Do you guys have any idea what is happening here? Thanks.
The problem was. Umbraco was configured to run on load balanced servers on our old servers. I had to turn it off on the new server.
<distributedCall enable="false"> in umbracoSettings.config
What version are you running? When v5 first came out, I had a big problem with that (and solved it like you by touching the web.config to force a reset. Hopefully you are not using v5 (as its been discontinued and has extreme performance issues).
I have not had that problem in any v4.x versions that I can remember; changes should show up instantly after you republish.
Are you running in a standard configuration? Using a webfarm by anyt chance?
Is the ~/App_Data/umbraco.config file being written to on publish? This is the XML cache file that is used in displaying you website.
When you publish a node, the data is serialized into XML, stored in a database table and then written out to the umbraco.config cache.
This could be some kind of permissions issue, if umbraco doesn't have rights to read/write the file. Or you could have a corrupt dll that just isn't writing to it correctly. Or perhaps it's writing it out just fine, but your server is caching you pages in a weird way. Either way, I'd take a look first at the umbraco.config and make sure the data is being written to it on publish.