I am new to Laravel. When I am in debug mode I get the following errors every time every page loads:
The payload is invalid
After pressing two times on Continue I get the error
The MAC is invalid
The error messages are located inside the encrypter.php file. After pressing "Continue" again, I can proceed with debugging with breakpoints and so on, and everything works fine. The $payload-variable is null.
The project is still very basic. Only some things like CRUD like explained on tutorials.
What is payload? And am I missing some kind of configuration? How to get rid of these error messages?
The answer is found in this post:
Can't using Visual Code to debug in Laravel project
I also:
closed VS Code Editor
cleared all history in my browser, including cookies and cache
ran the commands as mentioned in the post inside the windows cmd window (so not the integrated terminal inside VS Code Editor)
I’m having problems debugging my program. When I click on the submit button I get the Yahoo’s search engine message: Page not found message that looks like this:
The requested URL http://localhost:000000/MyController/ControllerAction/7?hsimp=yhse-001
cannot be found or is not available. Please check the spelling or try again later.
This does not leave me with any clue as to which line of code or the location of the problem.
In Chrome developer tool I find the line below
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: (-webkit-min-device-pixel-ratio: 2), (min-resolution: 192dpi) errorhandler?hsimp=yhse-001&hspart=CND&type=A75DB878ECBE148E7B6F_s_g_e&q=http://localhost:000000/Att…:2
Still confused as to how it relates to my problem. Seems to be referencing screen resolution. How can I find the offending line of code in Web Developer 2010 Express?
This isn't caused a bug in your program code, so there is no "offending line".
It's a problem with your server configuration. But why is Yahoo Search coming up for a localhost resource?
That said, localhost:000000 is not valid. Port numbers must be between 1 and 65535 and do not have leading zeros. Where is 000000 coming from?
I'm currently (trying) to develop an app with Worklight Studio 5.0.6 and Dojo (Mobile) 1.8.3. I have a really hard time to to find a proper method for debugging. After waiting 5-10 minutes for the build an deploy-process on the server, an error usually looks like this in the Chrome debugger:
How am I supposed to track down this error in MY source? The whole stack trace consists entirely of Dojo code which generates an absolutely useless error message after 20 abstraction layers.
Seriously, how do you guys handle this in real life? What methods do you use for debugging Dojo-driven apps in the browser?
spyro
For dojo.parse errors, I find it useful to pause the Chrome debugger on all exceptions (the purple icon on your screenshot, should be blue). You usally get more details about the cause of the error, the name of the DOM node being parsed, etc. in the first exception being raised.
Rémi.
Debugging dojo based application should be the same as debugging any javascript application.
Usually I will follow these steps:
add console.log() somewhere in code: this is fast and most of time this is enough.
set breakpoint in debugger: if step 1 is not enough, you can base on error information to set breakpoint before error line, then step in or step out.
comment out recently changes: for some error which is hard to find the error line, for example, parse error in your case, the good way is comment out your recently changes one by one till back to your last working version. Or, return to your last working version, then add code back one by one.
Create a simple application to reproduce the error : if your application is very complicate and it is hard for you to follow above methods, you can try to create a new application which mimics your current application but with simple logics and try to reproduce the error.
Based on experience : Some errors, for example, extra ',' in the end of array which works at chrome and firefox, will report a nonsense error information at IE. Debug these kinds of errors is very difficult, you can base on your experience or do a google search.
Did you provide isDebug: true in your dojoConfig? Also, try to see if the same occurs in other browsers.
Update: I recently discovered that there are issues with Google Chrome and Dojo debugging and I think it has to do with the asynchronous loading of files. As you can see in the provided screenshot of #spyro, the ReferenceError object is blank (which you can notice because of the empty brackets {}). If you want to solve that, reopen the console of Google Chrome, (for example by tapping F12 twice). After reopening the ReferenceError should not be empty anymore and now you can expand that object by using the arrow next to it and get a more detailed message about what failed.
Usually what I do in situations like that is to place a breakpoint inside the error callback (line 3398 in your case) and then look into the error variable ("e").
I am not sure how familiar you are with the Web Inspector, but once you hit the breakpoint open the Web Inspector 'console' and check for the error properties "e.message" and "e.stack" (just type in "e.message " in the console).
Also, during development it is better to avoid Dojo optimization / minification, which greatly improve your debug-ability.
Bottom line is to try to place the breakpoint before the error is thrown.
So there are two things going on which I have no clue and if someone can help that would be awesome.
I am doing automation using Selenium WebDriver in conjunction with VS2010 (C#) and I am using the PageObject pattern, which has really been helpful in constructed clean, organized code. Anyway, here are my two issues:
When I Debug my code the automation runs perfectly with the desired results at the end. But when I enter a breakpoint and step into the code, it gives me an error message stating "There is no source available - There is no source code available for the current location" Then the message looks like it is looking in my directory for a particular class file and it gives me a bunch of error messages and the last line says: The debugger could not locate the source file c:\Projects\WebDriver\trunk\dotnet\src\WebDriver.Support\PageObjects\WebElementProxy.cs.
Again when I run through the program with no breakpoints it's fine. But once I enter a breakpoint and step into the code, it gives me that error like it's looking for a particular class. I have all .dlls referenced to the project so I am not sure what is going on there.
When I run the code in Chrome, everything seems to work fine. But when I try to run it using FireFox, it cannot seem to locate the first button. I have my code set up as:
//Get A Quote Button Control by ID
[FindsBy(How = How.Id, Using = "bt_ContinueWelcome")]
[CacheLookup]
public IWebElement GetAQuoteButtonId;
So Chrome will read it fine but not FireFox, and I have not tried IE.
Any help for the above would be greatly appreciated. I want to start inserting validation but I need to get over these hurdles first - thank you
I keep getting this error in web hosted mode GWT, but I'm not sure what's causing it. Is there a way to make it produce a more informative output? My approach right now is to step through line by line in the debugger until the problem appears, but it's a pain.
The problem went away when I disabled Chrome's Cortex extension. Odd.