As weird as it might seem i am having a sandbox violation on the same domain:
*** Security Sandbox Violation ***
SecurityDomain 'http://192.168.1.165/52589a87aab101a25e0000de#/' tried to access incompatible context 'http://192.168.1.165/52589a87aab101a25e0000de#/'
Does anyone have a clue what this might be? everything works.. but i get this warning 100x times and then the log just won't display any more errors.
It's the first time i ever see this kind of sandbox error, especially with everything working properly.
I'm not the code owner, but i still did a find all for Loader( and i got only 2 loaders who are not responsible for this error.
thank you in advance.
I've noticed there was a weird onEnterFrame that was constantly trying to talk to a javascript, i took this away and it fixed the issue.. but i never seen crossdomain errors on this kind of communication before.
Related
I don't understand why I am getting a "run build" and "build failed" error when I have not added or deleted any code.
I tried the "invalidate cache/restart" as well as "rebuild project" but the error still occurs.
The first is below:
Unable to resolve dependency for
':app#debugAndroidTest/compileClasspath': Could not resolve
androidx.test.espresso:espresso-core:3.2.0.9
The second error is
Unable to resolve dependency for
':app#debugAndroidTest/compileClasspath': Could not resolve
androidx.test:monitor:1.2.0
.
These errors are occurring in the initial build as I am attempting to do my 1st class assignment. My accountability partner and I attempted to figure it out but he has a Mac (Maybe that's why he couldn't reproduce the errors) I cleared the cache, restarted the build several times. Updated Gradle. Doubled checked settings. etc.
I am at a loss for a resolution.
The problem was traced back to my machine not having enough RAM.
Meh, I'm a coding newbie this is all apart of the learning process as well as changing career fields.
I have posted this on google-apps-script-issues (https://code.google.com/p/google-apps-script-issues/issues/detail?id=4723&can=4&colspec=Stars%20Opened%20ID%20Type%20Status%20Summary%20Component%20Owner) but with no response I am getting desperate as all my sheets and scripts are breaking down. So I hope someone here might have encountered this and have some idea for me how to handle this.
Some of my exiting scripts (including some in spreadsheets) suddenly started throwing the exception 'Library with identifier LabelServices is missing (perhaps it was deleted?)'.
I tried deleting the library reference in some of the scripts that were throwing this error and re-adding it but the same error comes up. I even defined a new library with the same name and try to use it instead. Still the same error.
Most likely a related error, when trying to open project properties to these scripts I see the message 'Something went wrong. Please reload.' and the hourglass never stops. This happens at both standalone scripts and ones embeded in spreadsheets.
Please note that if I add the same library to a new script then there is no problem and the library works perfectly.
I would like to add that even if I remove the library and also any calls or references to the library the problem still persists.
Link to a script where this happens is available at https://script.google.com/d/1ptevXwu25z9Vo88zX0XOyaQk5pE5MmzwDbb-lMglNY1lzz1HBBiAeJxn/edit?usp=drive_web
You can copy it and play with it. You should get the same problem.
Appreciate any help!!!
Andrew. First of all thank you as you triggered something in my mind. I went all the way bottom up and checked each script and a library it was calling. There were obviously dependencies, however nothing that should have been a problem. a couple of libraries even though in development mode seem to cause a problem. I had to create a new version but it was not enough just to update their version in other scripts. In the calling scripts I had to remove all libraries and re-add them one by one while testing whether the project properties shows up or not. I just wish Google would have a utility to clearly highlight what was wrong because I can't figure it out though I went twice through their documentation in regard to libraries and development mode. Since I have about 30 libraries or so, not to mention spreadsheets and apps it took me nearly a whole day... Thanks again!
To all, it seems that there is a problem where sometimes libraries get out of sync (at least that's the best way I can describe it). You may need to create new versions for the libraries (even though these are in development mode. And in each problematic script remove and re-add the libraries (in at lease a couple of transactions - first remove and confirm then add - and better one at the time while checking that your project properties opens properly). This solved the problem for me.
I've been experiencing a strange error while working on my Play Framework project. While my project is running, I will sometimes receive a ClassCastException, but the error is this:
ClassCastException occured : models.Person cannot be cast to models.Person
This occurs usually when I'm calling a find method such as:
Person p = Person.find("name=?","Joe").first();
If I restart the project, the problem goes away, but only temporarily. It makes testing my project a major pain. How do I fix this?
I've experienced this error while in Dev mode in Play, in two scenarios (as far as I can remember):
Modify an entity and try to recover values from cache that are objects of that entity class.
A compilation error while reloading the code of the page/application
In both scenarios fixing compilation errors or cleaning the cache solved the issue.
Not saying that those are the only possibilities, it may be that you are having some other issue.
This most likely occurs because you've somehow loaded the Person class under two different class loaders. When a class is loaded twice in two different class loaders it's effectively two distinct classes.
(Unfortunately, I can't tell you where/how you might have done this.)
(And it is a bit curious to have the problem pop up on the statement you list. Are you certain that's where it's occurring? Perhaps you should show the exception traceback.)
In my case, this is related to applying evolutions from the web interface. Someone raised a bug for this, but so far it hasn't received any attention from the dev team. There is a patch attached to the ticket, but I haven't tried it, so YMMV.
When I am debugging broken code, after a while the browser announces that the Flash plugin has crashed, and I can't continue debugging my code. Can I prevent the browser from killing Flash?
I am using Firefox.
Going to the debugger on a breakpoint makes the plugin "freeze". This is intentional, it's a breakpoint after all!
However, from the browsers perspective, the plugin seems to be stuck in some kind of infinite loop. The timeout value varies, my Firefox installation is set to 45 seconds.
To change the timeout value go enter about:config in the url field and look for the setting dom.ipc.plugins.timeoutSecs increase this or set it to -1 to disable the timeout altogether.
When the plugin crashes, it does in fact not so, because the browser is "killing" it, but rather the plugin terminates itself when a fatal error occurs. This is necessary to prevent the browser, or even your entire machine from crashing - there is no way to tell what is going to happen after an error like that. And besides: After the first uncaught error, your program will likely not be able to perform even correct code the way you intended, so you won't do any good by continuing a broken debugging session. So it is not a flaw, it is actually a good thing this happens!
However, you can do some things in order to work more effectively (and make your programs better). The most important I can think of right now are:
Learn to use good object-oriented programming techniques and get acquainted with design patterns, if you haven't already done so.
Take extra care to prevent error conditions from happening (e.g. test if an object is null before accessing its properties, give default values to variables when possible, etc.)
Use proper error handling to gracefully catch errors at runtime.
Use unit tests to thoroughly test your code for errors one piece at a time, before debugging in the browser. Getting to know FlexUnit is a good place to start.
EDIT
I should also have said this: A Debugger is a useful tool for stepping through your code to find the source of an error, such as a variable not being properly initialized, or unexpected return values. It is not helpful when trying to find out what's happening after a fatal error has occurred - which will also not help you to fix the code.
I am following example by José F. Romaniello on session management with NHibernate. It's a very good article, however I'm struggling with it having very little experience with NHibernate, Windsor and MVC.
I am trying to re-create NHibernateInstaller, however encountering the following error: Component Castle.TypedFactory.DefaultInterfaceFactoryComponentSelector could not be resolved. Make sure you didn't misspell the name, and that component is registered.
In the sample project provided this error does not crop up, even though the installer is identical and Google does not come up with any results (which is very unusual). What causes this and how can it be avoided?
it seems a problem with the TypedFactoryFacility... are you doing this?
kernel.AddFacility<TypedFactoryFacility>();
before running all the installers?
uncomment the following code in Bootstrapper.cs file.
container.AddFacility();
This happened to me when I created my own implementation of ITypedFactoryComponentSelector, but forgot to register the selector itself.
There was no indication this was the actual problem (and the kernel debug information assured me the components can be resolved) - but registering it fixed the issue.
Hope this helps someone :-)