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.
Related
When opening Azure Data Factory Studio, our datasets do not appear (couple of 100). If I open the solution in Azure Repos, I can see that they are there. If I open the solution in Visual Studio, again, the datasets are there. Sometimes if we refresh our browser several times over, they appear. If I clear all browser history, cookies, etc, and restart my computer, they 'sometimes' reappear.
If I accidentally close the browser (like I did now), it can take me hours to get the datasets to appear again. Sometimes they just pop back up.
Anyone else experience something similar? I have done a whole load of searches and cannot seem to find any posts with a similar issue (could be my wording?).
This is unexpected behavior in Azure Data Factory. As there is no error message, it is difficult to understand reason of problem and difficult to resolve issue.
Providing a link to raise ticket.
Just for anyone else experiencing the same issue.... turns out it was related to the proxy server. Apparently it was intermittently stripping out the datasets from the header (possibly because there were so many of them - and as they grew in number, so did the frequency in which they were being stripped from the header). Whitelisting ADF apparently solved the issue.
When running my code in debug mode, I keep getting 2 error messages:
Could not delete [path_to]\productiondb.log. May be locked by another process
I don't know what process might be locking it. It comes when I make changes to the code while my Pivotal tc Server is running in debug mode, but it dosent seem to create a lot's of trouble. Sometimes however, I get this warning:
Also due to some changes. I usally just restart the server and move on. This isen't the real problem, the real problem is that I get these messages when I havent doen any changes. Somethimes it accures when I run a certen part of the code, other times i occurs when I open certen codes in sts, however, it doen't seem to stop at the same place twice.
I am suspecting that this has something to do with git. I am using git to change between versions and doing tests. So I am thinking that STS has some of the code in memory from before I changed branche with git, and isen't updating it before I run or open the file with that code. But I am rather new to both sts and git, and can't be certan that it would work that way. If it is, does anyone know how to update sts after I have changed branch? If it is not, does anyone know what might causing it?
If you run an app in debug mode, the Eclipse Debugger tells the application when code gets changed and tries to use the debug API to swap in the new code into the running application. This is especially useful if you debug your code, hit a breakpoint, step through the code, fit the issue, change the code, and press save. At that moment, the Eclipse compiler updates the class file and tells the running JVM to swap in the new code. If that succeeds, the debugger will jump back to the last stack frame and the execution of your app will continue with the beginning of the method that you entered. This allows you to directly continue to debug and step through the updated code without restarting the app.
While this is a great feature of the JVM, it is very limited in terms of what scope of changes to the classes the JVM can deal with while doing this hot-swap. It is usually limited to method implementations. So adding new methods, adding or deleting members of the class, etc, are not supported. As a result, the above screenshot will appear. It means that the JVM wasn't able to hot-swap the changed code and will continue to run with the previously loaded code instead of the changed one.
Locally, in single play mode, any PointsService:AwardPoints() just fails silently. Even wrapping it inside pcall() does not give me anything, success nor error. Lines after that one are just not executed and function returns.
I'm guessing it will not work locally? But behavior is weird and I don't know how to develop/test it. I've been banging my head with this for hours, maybe too long and I'm missing something obvious?
EDIT: after more testing, to avoid adding more comments, I realized expected error is returned (Processing PointsService:AwardPoints error: HTTP 0 (HTTP 403 (HTTP/1.1 403 Forbidden))) but only after I restart Studio and during first local run (Play). As soon as I hit Stop and then Play again, errors are no more returned and behavior is back to described.
Also, it appears to work in Test mode. I'm guessing that "Cleanup" button helps, while "Stop" in single play mode doesn't.
Still, quick testing with Single Play mode is not possible and it slows down development a lot
This could be happening for two reasons:
You're trying to award PlayerPoints while in Play Solo, which is restricted.
- OR -
You're trying to award points from a LocalScript, which is also restricted. Points can only be awarded from the ServerSide to prevent exploiters from ruining the leaderboards.
I have a very weird situation. Since a few days, the following actions will crash my Windows 10 PC (using Notes R9.01FP8):
I open my Prefs page in the Domino Designer
click on the Source tab
move to a specific location in a table
then I add a Repeat control
I then open the Properties of the Repeat control
to set the data to JavaScript...
and nothing happens, until after a few seconds: BSOD - Unexpected Kernel Mode Trap in either win32kfull.sys or ntoskrnl.exe.
Sometimes, the JavaScipt box is displayed, so I can paste my code, but a short while later the PC still crashes.
I have to say that my PC crashed a lot lately, so I reinstalled Windows and all drivers, so there might be a rotten one that causes all this. According to DriverEasy, all drivers are now up to date. The Event viewer displays a BugCheck event, but nothing relevant (to me anyway).
What I did for further analysis:
I removed Cache.ndk, it didn't help (of course)
in a copy of the XPage, the system crashes when I add the Repeat
ditto, in a different XPage
it seems to work in a different Notes database, on a different XPage
so I created a new database, copied all elements from the original database over, and still the system crashes when I add the Repeat
I'll be doing so more tests, e.g. with an empty database and just one XPage, then adding my Prefs page, or with the same database but then on a server. Actually, one could say I'm kind of lost, and stumbling around in the dark.
My questions to the XPages/Eclipse gurus:
could it be the workspace, and is there any way to reset it?
do you have any suggestions how to get this solved?
Thanks!
The Windows Creator update that MS posted does not seem to fix the Designer crash.
https://grahamacres.wordpress.com/2017/07/10/domino-designer-still-crashes-after-windows-10-creators-update/
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.