Why is Cypress Duplicating Selectors and Shifting Elements On Screen When Running Local Tests? - dom

When running tests locally, in both Cypress 9 and 10, the program will shift elements around on the page and seemingly duplicate selectors or adjust the DOM. The best way to describe it is that it looks like what you would see if a movie froze between two film cells, with the top of the page either duplicating itself or replicating the bottom of the page. The tests will find duplicate selectors (there aren't duplicates, I have checked) and I am unable to progress. Sometimes, I am able to restart a number of times and it will almost work, but I have been brought to a bit of a stand still with this.[example 1][example 2]
I have tried using both Cypress 9 and 10, and the issue persists across both version. I attempted a global uninstall and reinstall and that didn't help. There has been no change.

Related

How do I get transformers' .from_pretrained("model") to consistently show download progress in a Jupyter Notebook?

I'm running a Jupyter Lab instance on a remote server which I access through my browser
I'm working with a notebook from a venv kernel that imports the AutoTokenizer and AutoModelForCausalLM classes from transformers, then downloads the elements for each from a model we'll call "model", using each class' .from_pretrained method.
the actual importing and downloading works fine; however, the first time I ran the cells containing AutoTokenizer.from_pretrained("model") and AutoModelForCausalLM.from_pretrained("model"), a text-based download progress bar appeared in the output text. this went through each file download until the kernel crashed (for reasons that I am yet to troubleshoot, but I suspect are related to storage allocations).
when I ran the code again, everything worked the same, but the progress bars never reappeared. the same thing happened a few weeks ago when I tried this the first time with a different model and slightly different environment
What I've tried:
I've tried creating a new kernel from a new venv. I've tried restarting jupyter. neither made a difference
there was a warning that appeared underneath the transformers import that suggested I should install ipywidgets. this was there the first time when the progress bar did appear, and again when it didn't, but somewhere online suggested that ipywidgets and progress bars could be linked, so I imported it to the venv anyway. this unsurprisingly did not help
I've tested whether I get output at all: I do. if I enter 1+1, "2" outputs. I also still got the ipywidgets a warning a few times before I installed it
I made sure that the output is not just being collapsed. View -> Menu -> Collapse/Expand all Outputs does not make anything new appear, besides some ellipses.
I tried doing pip install --upgrade jupyter_client, but it basically said there's nothing further to upgrade.
I tried a browser based on a different engine (chromium instead of ff). I tried with my adblocker on and off
if I download a different model, that does seem to work, once, but then as soon as the kernel crashes a single time trying to download that model, it will never show them again, even when it's clearly actually downloading them

Selenium IDE: controlKeyDown and the likes not working

I'm still studying for my computer science degree and have mostly focused on the mathematics side of things for now. However, in my current job I am working with Selenium IDE (specifically because it doesn't require coding knowledge) and I'm having a bit of trouble:
I need to test a Shift + click as well as a cherry-pick (Control + click) command on the web-based software we are creating, but it's not working. Manually pressing control and then clicking different elements on the screen works fine, however.
Like I said, I'm using Selenium IDE 2.9.1, and I'm using it on Firefox 50.0.2 on a Windows 10 install. My commands on that section are as follows:
Screenshot of the IDE command
The idea, obviously, being to select the object named Field1, depressing the Ctrl key, selecting the object named Field2 and then releasing the Ctrl key. This should, theoretically anyway (and does work when done manually outside of the IDE), select Field1 and then cherry-pick Field2 from the list as well.
This, however, is not the case, and it doesn't work.
Can anyone, please, advise me on how to proceed here? Should the commands be structured differently? Am I using the incorrect commands? Is there something else I can try?
As a PS: The same issue persists with the shiftKeyDown command as well.
I have searched for this issue online and found no help that actually works for me yet, hence this post.
I am looking forward to your replies, in the hope that I can find success... :)
I think that it is a Selenium IDE original command problem.
When you tried to simulate pressing Ctrl key and used "controlKeyDown/Up" command, it just changed the boolean value and did not fired a real key down/up event. Also Shift and Alt key could not work.
Maybe you should try to add a "keyDown/Up" command after "controlKeyDown/Up" command and the target could be //body .
And, if you need, please try to use the tool, SideeX, the extended version of Selenium IDE. Maybe this problem will be solve in the future and make the test case flexible. Here is the link to SideeX and there are more details about the tool.
OK, I found the solution.
When compiling the tests I test them by running through them step by step to ensure that everything is working like it should, before saving it to a test suite and letting it run on it's own. Now, this involves me double-clicking every command in the Table one by one, in sequence, and keeping and eye on the screen to ensure that it executes and behaves exactly like I want it to. Simple, understandable, logical, correct?
Well, it seems like the controlKeyDown and controlKeyUp commands DO NOT WORK in this way.
I built a bare-minimum test case using only the 4 commands: click the element, controlKeyDown, click the next element, controlKeyUp. I ran through the test a hundred times with no success, but then I started thinking - what if the controlKeyDown command is never released? That would cause issues outside of the test (on the rest of the environment, obviously), since the Ctrl key would be permanently depressed. So I figured that the Selenium IDE either 1. Releases the key in a short amount of time automatically (faster than I can execute the command to click the next element manually) or 2. It simple ignores the controlKeyDown command if it's not run in a complete test case/suite.
So I took the 4-line test case, built up a test screen with test grid elements and ran the test case - and it works. Perfectly, actually.
So, in case anyone has similar issues in the future, try to RUN the test case instead of clicking through it or executing commands manually.

Protractor test fails when launch directly on Windows Server 2012

I use Protractor 3.0.0 to measure UI performances of a web app.
I need to launch my test suites on a virtual machine running on Windows Server 2012. They run perfectly on my personal computer, but on the VM the tests go crazy:
My tests don't always properly click on dropdown menus (e.g. my debug messages indicate that the click on the logout link in a dropdown menu was successful but nothing happens)
When filling text fields A and B with values "valueA" and "valueB" in a form, the tests sometimes sends "valueAvalueB" in the field B
I tried launching tests with PhantomJS, and I still have the same problem with dropdown menus (I didn't check the values of text fields yet). In addition, the performance measurements seem to be too optimistic.
Does anyone encountered the same problem? I couldn't find anything describing that kind of problem...
I launch my tests directly from the VM (not using remote WebDriver or something).
Ok Link Pham this is what I feared... Headless browsers could fix the issues, but we want to measure times spent displaying items and refreshing them. Headless browsers could give too optimistic results (as I observed with PhantomJS when I gave it a try). I will try with headless Chrome.
I guess I will have a bunch of other questions, but your answer properly covers the scope of this specific question so I will close it. Thank you again .

MonoDevelop: Autocomplete not showing all members?

Linux Mint 17.2 64x
MonoDevelop 5.9.5, writing a D application with D language binding
I've been having a problem with Monodevelop for a long time where it'll just stop showing relevant autocomplete entires. I'll write a class or have one from from a library and sometimes I'll get what's in the class and sometimes I'll only gent entries like sizeof (which I think apply to everything). Occasionally I'll get nothing at all.
Like this.
I've tried uninstalling and reinstalling, I've tried deleting project files, and these solutions work in some cases until I start adding more code and then at some point they break again and I get nothing relevant in my autocomplete pop-ups. I've even tried deleting Monodevelop folders in .local .cache and .config on my system, but the problem persists.
I've been trying to ignore it, and when I had a duel monitor setup it wasn't so bad because I could have references to what I'm working on in another window... but right now I'm this close to having zero monitors from getting so frustrated with having to tab around back and forth every 2.5 seconds, I'm just going to lose it and embed my mouse in the screen.
I'd switch to another IDE but I haven't been able to get most of my other options working with D/Dub...

how to suppress the enoying dialog boxes when developing xPages?

Anyone know how to remove or supress the enoying dialog boxes when developing xPages
If you are just making small xpages application you might not see these very often, but the more complex your xPages get you see these all the time. specially when you navigate your xpage using the outline view or during build
I click the x several times every day to get rid of it, Not sure if the operation quits when I click the x or if it continues in the background.
I would like a setting to get rid of it once and for all
Well, in your designer, you should disable Build automatically in the Project menu. This will remove the constant build, but also means that you have to build manually, when needed.
You could also take a look at Nathan T. Freeman's post on the matter # Making Domino Designer work like you want
Are you using any java libraries added to the webinf/lib dir in your nsf? I noticed that when adding any jar files to the lib dir rebuilding your application can take ages..
I had 2 external jar files used in my project (contained within the database). It used to take around 5-10 minutes to compile the project. Any changes to the XPages/Custom Control/Java files needs a recompile. And you can imagine the frustration I had with the compilation time. Later I detached the jar files and put under the jvm\lib\ext folder. The compilation time drastically reduced to 1 minute. Still not happy.
As a next step, took a local replica of the database and started making the changes and recompilation on the local replica. Once done, replicated the databases and always previewed the changes on the server version. The compilation time is hardly 10 seconds. So 10 minutes to 10 seconds :)
Switch off build automatically, it will solve most of these.
There is also a known issue SPR SODY8Q9KNA where Java Design elements (new feature in 8.5.3) keep getting rebuilt on designer start up. That brings up the same pop-up.
There should be a fix for that in 8.5.3FP1 but I am not in an official position to say it will be in FP1 until it actually ships. You can check in the release notes as they are updated.
http://www-10.lotus.com/ldd/r5fixlist.nsf/(Progress)/853%20FP1