Repeated terminal restes causing lost work. Issues with Object/NS mismatchs, leading to work not being properly counted.
Very frustrainting experience with this mock exam series. Too bad because the content is good, but not executed well and/or fully baked.
How often are you seeing this? There used to be (and may still be) an issue where the terminal resets after about an hour; I believe this is/was caused by an upstream CDN timing out. But not much more often than that. This is annoying, but it’s predictable enough that you can learn to get around it. Things to know:
Is this what’s going on for you, or is something else going on?
Yes, terminal resets as you describe, seems like 2-3 every session. can be editing a manifest and then boom, it’s all gone, time to start over. same with aliases and such.
I’ve also experienced a deployment populated in dev-001 NS when it was supposed to be in the default. To name but one of these occurrences. I seem to notice, after going through a few of the mocks, that to pass, you might need to create the manifest by specifically defining the NS, even if you’ve switched over to that particular context/namespace whilst creating imperatively. So i’m now calling out NS in all my imperative/declarative workflows.
If it’s in a specific exam and question, tell us about it with that info, and someone will check it out and notify engineering if needed.
As for the restarting terminal – you should be able to get back most of your edits from vim by using the “recover” feature. Vim keeps a swap file, and you can get at it by asking for it to restore it. If you’re in vim when the terminal resets, just start up vim with “vi FILENAME” and vim will give you the option to restart with the swap.
I’m not sure if this problem is universal, location dependent, or just like to pick on us “special people”. It’s certainly annoying, but it’s in my experience somewhat predictable down to which minute during the exam it hits you. If that’s the case, you sort of just learn to roll with it.
appreciate the responses and tips and tricks. not certain if the mock labs are a free tier option or paid only. but if the latter, it should simply work w/o having to be concerned about the periodic terminal resets. my 2 cents.
i’ve submitted an incident for a deployment that was not being accurately counted.
