Every time that I do a code review in Kiln, the first time I go to add a comment, approve/reject the review, or close the review, it pops up a dialog box saying,
Your session has expired
You are no longer logged in. Please log in and try your request again.
The words "log in" are hyperlinked, so I click it and type my comment again. Half the time, I forget to re-mark the code. This is the biggest bug in my usage of Kiln.
Is there a way to make this stop happening?
We are on version 2.7.29 of Kiln.
This problem is known on kiln.stackexchange.com, but my account is limited over there. Here is the question.
Can someone from FogCreek please provide a status update? This is a bug that we can repeat at will.
I think you could get rid of this problem by upgrading
check this link
We will be performing an account upgrade to Kiln 2.9 on Sunday June 24th at 02:00 UTC
...
Countless bug fixes and stability improvements, such as:
Fix spurious "your session has expired" errors.
Related
That is the case as of last night. Does not work for CPU or GPU "compute type"
Basically, after pressing the "Start runtime" button, it says "Preparing project runtime..." for about ten minutes and then stops. It shows the following error, "There was a problem when starting the project runtime. This should be resolved shortly. Please try again later."
I have now tried it about five times over last night and this morning.
There is no way to even access the work that is saved there. The "project" will not boot up.
Basically it is a dud at this point.
Is anyone else experiencing similar issues? What does one do?
The issues/questions and answers that I have learned since (because I was asked to clarify):
(1) The environment on Sagemaker Studio Lab is supposed to be persistent. I.e., any time one starts it, the environment, files uploaded, etc. are where it was left last. However, I was not able to start the environment any longer. Before it locked out, it would start fine. Consequently, I was not able to get to my saved work in any way shape or form. I was wondering if anyone has had this issue
Answer: Thus far not too many people are approved for Sagemaker Studio Lab. So, I may have been the first or one of the first to encounter this issue. As of this writing there does not exist a way to access ones data if one cannot spin up a virtual machine that would have access to the data using their "Start runtime" button.
(2) It is not clear where one is supposed to report issues with Sagemaker Studio Lab. On one's home page in Studio Lab, it has a link to StackOverflow under "Get answers and help others". That is how I ended up here. Though, I should have included the following hashtag (#amazon-sagemaker pointing to https://stackoverflow.com/questions/tagged/amazon-sagemaker).
Answer: I eventually found where people are submitting bug reports. And I reported the issue there (see issue 56). https://github.com/aws/studio-lab-examples/issues
(3) It was not clear to me if I was to delete my account and request a new one if I would be put on a waitlist (which supposedly is presently long). I.e., this would be the manual factory reboot option where one still loses all of ones work, but, at least has an opportunity to start again with the environment.
Answer: Once one is approved, one does not go to the waitlist. Deleting my account, requesting a new one, and setting it up to the initial state took a couple of minutes for me. And yes, I lost all my work that was on there. So, back stuff up as it was your computer in the `80s. I.e., back up externally to that environment.
I signed up for ASMSL about 2 weeks ago. As of this evening (Feb 15) I'm able to log into my runtime without any trouble at all.
Some of our reports suddenly produce the following error message when trying to open them (from https://datastudio.google.com/)
We're sorry! Data Studio isn't available at the moment. Please try again later.
We are getting this message for more than 24h now. Any idea what the reason might be, and how to regain access to the reports?
While I still don't know what the root cause was, it's very likely something outside our sphere of influence. Looks like someone on Google's side pushed the wrong button, as it affected more users than just us (see, e.g., here and here).
So to fix this, have a look at the Google support forums, and then sit back, relax, and hope that Google is quick to do their thing.
Ok Not sure what is going on here. I have runaway queries that won't cancel. I have one query to select all rows from a table that only has 250 rows and is 1.5KB in size. It's been running for 30 minutes right now and it should only take a few ms.
I've tried canceling by hitting the abort button on the worksheet, going into history and selecting the query and hitting abort, aborting based on the query ID via SQL, and aborting based on the session ID via SQL.
Ironically whenever I try to abort via SQL it shows that the queries have been terminated and then they still show as running, I wait a few minutes and re run the query and it again shows as terminated but they still are running.
I also tried loggin out and logging back in again and am seeing all kinds of weird errors:
Internal Error: Unable to retrieve the current roles.
Error
Problem with your MFA Enrollment: There was an issue with your enrollment
process. Please try again.
Worksheet Not Loaded
I have no idea what is going on but it seems like everywhere I turn there is an issue. Any assistance would be greatly appreciated.
Try logging completely out, close the browser, reboot your machine, and start from there. Here my guess:
Sometimes the query history (which I assume is where you were seeing things still running), needs a browser refresh, but based on MFA errors, refreshing your browser appears to have you logged out of your SAML/MFA process.
Once you successfully login, you'll likely see that the query had completed already before you even tried to cancel it.
If that isn't the case, and you are still seeing issues, then we'd probably need more information, or a quick call to Snowflake Support will walk you through things. My guess is this is all a display issue on your browser/UI, rather than something going wonky with Snowflake.
I am not an IT person but I have to play one at work sometimes. I was about to run diagnostics on our EHR which I do weekly, I always stop the ADS and restart it before running the diagnostics. When I went to stop it this time I got an error box that said operation complete which I've gotten before but the box to restart it never came back, I tried to close it and it said not responding. After waiting 10-15 minutes I used the task manager to end ADS. Now when I try to restart it it says it can't because there is another instance running. When I look in the task manager under service the ADS says stopping and has said that for at least 30 minutes now.
Any help would be greatly appreciated!
Thank you
Quite suddenly, after years of running and developing this application, the log-file shown at Google developers console is filling up with entries marked with the double exclamation mark error, but with no error description when expanded. It has been going on for days now, and is making the logging absolutely useless. Everything else is drowning in these seemingly false error messages.
What can I do, except pay $150 for the right to send them an email?
tl:dr Don't have print statements in your request handler!
With the help of a friendly google person looking at my issue report, I found the trigger for the empty errors in the log file:
Print statements in the request handler was the cause. I had forgotten to remove them after a quick local test. Updating a version with those removed stopped the errors immediately, so it seems pretty clear.