This used to work, but at some point in the last year it stopped working and we just found out today from a customer. It keeps on saying that you failed even if you type it right.
Also, if you press the voice button, it says a different number/word than the number/word it's displaying.
Here is a live link.
Figured it out. For anyone else that has this problem the solution was...
The page had multiple tables. In an update, the end of the form got outside of the main table, breaking the captcha. Once the was moved back inside the proper it worked again!
Related
been trying to create a table in sandbox and i'm getting an "Unexpected error
Tracking number: c904462681469709". sometimes the table gets created, sometimes it doesn't.
any wizards that can help me with this?
cheers,
I ran into the same issue today, I do not know what causes the error, but I found that BigQuery has loaded my table. The steps I used are as follows:
Click the three dot drop down to create the table.
Fill out the source, destination, schema for the table.
After clicking 'create table' receive the error and close out the error window.
Close out of the create table window.
Refresh your BigQuery page.
Check the dataset you created the table under and it should be there.
I hope this method works for you as it did for me!
That happened to me too. So strange but yes I did the same thing Devin did. Took me forever trying to figure it out but it is what it is. Just refresh and keep going.
I am using VB.Net is Visual Studio v16.6.3
I started getting this problem a few days ago on an application I developed two years ago and have been improving on and off. This error appeared out of now where. My DataGridView is OK at design time. when I launch the application, all forms that contain a DataGridView, it will appear all blacked out - as per image below.
If I minimize the form and return to it, the datagridview is fine, as per image below:
I get the same problem, in design mode or on a compiled executable. I have not tried this on some elses computer yet to see if it is graphics-card related or application related. Anyone has any idea how to resolve it? I did notice that if I move the datagrid binding and display from the "new" contructor to the "shown" event, it sometimes fixes the problem - but not always. Very weird and random.
I finally found it. I have to call the Refresh for my datagridview... I don't know why. Did not have to do that before but it works.
If someone can explain the reason behind this behavior, please tell me.
I ran to the issue and I cannot get my head around how to solve this. I have four views, each with elements inside has its constraints, you can see the full list in the picture below.
When I run the app, and click on the any one of the text fields, nothing happens and works just fine. However, when I click on the other text field I get this not very pleasant error message.
Well, I followed the steps, and added a symbolic breakpoint, but it did not give any useful information, as you can see below,
I have been stuck on this for a while, and tried many things, including changing the priorities of both views and textfields, as well as deleting some of the constraints that might have caused the problem. Unfortunately, nothing works :( Any help is very appreciated!
You're not doing anything wrong. The TUISystemInputAssistantView mentioned by the console message is not your view. Ignore the message (and file a bug report with Apple). It's not your problem.
We have a customized mail template where we can set values of a parameter in mail preference.
After getting upgraded to Notes 9, when the parameter is set to Automatic it's working fine, but when another value is selected below thing happens (It was working fine in previous versions of Notes..):
After opening any external email, after double clicking on the mail body to edit.. notes is getting crashed.
I have two questions :
I see for external emails the control is going from querymodechange to queryclose while editing. Does it always happen?
I debugged the whole thing. Surprisingly it works in debug mode..no notes crash!!
Any help would be much appreciated !!!
This is why customizing the mail template is rarely recommended. There are interactions and dependencies between the code in the template and the Notes client, and it's very hard to debug. Since you haven't shown any of your customized code, I don't think anybody is going to be able to help you. I would recommend removing your customization code one piece at a time until it no longer crashes. Then you'll have an idea of what's triggering it, and you can try a different approach.
When Notes crashes, it dumps some diagnostics in the data/IBM_TECHNICAL_SUPPORT directory, notably the file console.log
You could review it and post here the lines pertaining to the crash.
Also, what was the previous version of Notes ?
To target the offending code line, you can use that old, dirty and tedious trick : add the folling line at the top of the QueryClose event, and move it down until you no longer see the result. Then post the context.
print now & "so far so good"
I was working at the forms designer and yesterday the designer literally only showed the form. Tried copying the .designer.vb to another new form and the same thing happened. Also when built it just shows what the designer shows. Compare the two versions:
(Had to use pastebin as the code is too long for a post, and it rejects my post if more than two links are used.)
Current code: pastebin.com/SsgR7YWD
Current form view:
Previous code: pastebin.com/bXCL3jhH
Previous screenshot:
Why it is not showing the controls? I know it is a long piece of designer code but I can't find where the error comes from.
I've just run your code through this site that compares to blocks of text and shows the differences - there's a lot - you might want to do the same and have a look at the differences. It may be easier to delete the form and start again to be honest. Having said that, you might be able to spot what went wrong
You should just delete the form and start again. A few tips to having a better UI ---
Use layout grids for the button-checkboxes and let the buttons occupy the whole horizontal space.
And remember to backup your code often so that things like this won't happen again - use something like GitHub and commit your files whenever your day is finished.
Happy coding!