In a test, I click a link (SSL Cert) link that does not actually load the expected URL page. It hangs and as far as I can tell no issues when I look at network or console. Is there a known issue with TestCafe and clicking certain kinds of links. Clicking the same link with Selenium and Robot Framework successfully takes you to the expected URL.
This information is not sufficient to reproduce the problem. Please create a separate issue in the TestCafe Github repository using the following form
I would appreciate it if you provide us with your project or url to your site and your test code. It will help us determine the cause of the issue efficiently.
Related
I've been using Jira recently and I came across a problem that I don't know how to fix it.
I have to Jira instances. when I try to link an issue to one on the other instance it doesn't link. It used to work but now it won't.
every time I try to link it I will get this even though for other projects it wasn't needed :
and when press authenticate I get this page:
afterward, when I press the link nothing changes.
Please if you are familiar with this problem help me.
afterward, when I press the link nothing changes.
I tried to link the other way and it's working but I still can't identify where the problem is.
Please if you are familiar with this problem help me.
It's all about Application Links.
Some server changes (like reverse proxy, update in web.xml, etc.) or changes in the admin user account may break the links.
You need the check Application Links between two instances; if there is a problem, try to solve that first.
If not, remove the application link from both instances and add it again.
By the way, if the users in the two Jira instances are same, enable the "OAuth" in the application links (and also be sure that the admin account is same on these two instances.)
Sources:
Linking issues
Application Links
We tried to load scripts but something went wrong.
Please make sure that your network settings allow you to download scripts from the following domain:
https://aid-frontend.prod.atl-paas.net/atlassian-id/front-end/4.5.0
Tried Google Chrome, Firefox, Internet explorer also tried with different PC.
Not able to login into bitbucket
I'm using Chrome Version 77.0.3865.120 (Official Build) (64-bit). I got the same error trying to log in to my group's Atlassian site, and I was able to fix it by specifically allowing JavaScript from Atlassian:
Open Chrome settings
Click on Advanced
Click on Privacy and Security
Click on Site Settings
Click on JavaScript
Make sure JavaScript is set to allowed
Next to Allow, click Add
Paste the URL from the error message in and click Add
I've faced a similar problem recently while traveling and trying to work from a new location.
First I've tried the steps from the previous answer which unfortunately didn't help me (but they definitely may be useful in a different case scenario).
I'm renting a house with an existing pre-configured WIFI router which I could get an access to manage it over the web UI.
I'm not sure which of the following helped me. I did the following changes to the router configuration:
Added the 8.8.8.8 as a primary DNS Server
Enabled IPV6
Disabled the built-in firewall (this one is the more likely one which fixed the issue)
With Eclipse Che, I've recently been able to deploy the docker container without any issue as provided in the instructions.
I'm at the point where am trying to learn a bit more about extension development for Che, and I'm going through the small introduction on "developing your first plugin" located on the following page:
https://www.eclipse.org/che/docs/che-in-che-quickstart.html
I'm stuck at the point where I can successfully build and deploy the sample project by executing the Traefik Start, Tomcat8-IDE Start, Deploy IDE and Deploy Workspace Agent commands.
But when it comes time to navigate to the newly created 2nd workspace by clicking on the link provided in the IDE to go to the newly created 2nd workplace instance...:
... I end up getting redirected to the following error page:
I suspect that there may be some kind of configuration problem with the sample plugin project, or configuration problem with keycloak, but I'm at the point where I don't really know how to proceed in terms of troubleshooting.
(Update: 2018/07/31)
At request of #kalrsson for more information, below is a screenshot of the che-public client configuration in my Keycloak instance.
(SOLUTION Update: 2018/08/01)
Thanks to #kalrsson for pointing me in the right direction.
At first I tried only adding the needed URL to the "Valid Redirect URIs" list. Doing so allowed me to get past the issue were I was receiving the error "Invalid parameter: redirect_uri". However, this only presented me with a blank page. On this blank page, when I inspect the web browser console, I noticed the following error:
From there, I also tried to add the needed URL to WebOrigins in KeyCloak as seen below.
Doing this finally allowed me to fully load and render the secondary workspace
Can you go to keycloak_ip:5050/auth, login as admin/admin, clients, che-public, and the IP you use to redirect urls and webOrigins?
So, you need to previewURL:port both to redirectURIs and webOrigins
I am trying to integrate Gitlab EE with JIRA as documented at http://doc.gitlab.com/ce/project_services/jira.html.
I created a JIRA-ticket ABC-1234, and when I commit with the message ABC-1234: Blabla I get the ABC-1234 part underlined and a link offered in gitlab. But when I click on this link, I get directed to ...[jira]/browse/ABC instead of ...[jira]/browse/ABC-1234.
My settings are:
Project url: hxttp://[jira]/issues/?jql=project=ABC
Issues url: htxtp://[jira]/browse/:id
(The x is there because I cannot post links yet) When I try the links in my browser, they all work fine. Also the issue overview works. Does anybody have an idea what I am doing wrong?
It is as easy as changing the service template!
There is this one action that is requested using javascript during the loading of a page, it takes over 25 seconds to resolve. Looking at the code makes me think there is a scaling issue, but I am wondering if there is any way I can step through the code during the request so I can see what is happening. I try clicking 'debug/start debugging' but it won't launch the proper URL (access to the site is subdomain based), and it will also not find certain dependencies. I am able to browse the site directly via URL locally after mapping a URL via my hosts file to localhost (127...) but the default url that pops up (localhost...) from debug does not work because it is not formatted properly.
Any ideas?
You can attach the debugger to your browser by selecting "Attach to process" under "Debug" menu.
In the past, at least with ASP.NET we have used tracing to debug issues. You will just need to enable it in the webconfig. If you use warn, the messages will show in red and be easier to spot.