Summary of error notifications from console - r

I am running a long R script. Is there a way to give me an overview of all the errors that occured after the script has run. (e.g. a function that I could enter after the script has finished running and that extracts me the error notifications from the console)

Related

gmailr credentials randomly (?) need re-authentication

I'm using gmailr in an automatic R script to send out some emails. It's been working fine for about a month and a half, but recently it failed with the following error:
Error: Can't get Google credentials.
Are you running gmailr in a non-interactive session? Consider:
* Call `gm_auth()` directly with all necessary specifics.
Execution halted
My code, which hasn't changed, is
library(gmailr)
options(gargle_oauth_email = TRUE)
gm_auth_configure(path ="data/credentials.json")
gm_auth(email = TRUE, cache = ".secret")
and is run non-interactively. (there is only one token in the .secrets folder) When I now ran it interactively, it "did the dance" and opened up the authentication thingy in the browser, which I confirmed and now everything is running fine again.
The problem is that I don't understand why the credentials suddenly required re-authentication or how I could prevent the script failing like this in the future.
You can try to clean cache in gargle folder and then create new one.
It worked for me, when i had similar problem
gm_auth function with gargle_oauth_cache stop working

Command to read .rout file if encountered error sending email

Goodnight,
Currently I have some processes scheduled in the windows scheduler by bat.
I would like to improve my process and I thought of 2 ways:
A -> in the execution of the code if you find an error, run some command to send an alert email.
B -> It would be possible to read a .rout file if it finds an error send an email informing that the processing failed.
Has anyone tried any of these ways?

Appium with WD and Mocha testing - Element is not currently interactable and may not be manipulated (status: 12)

The Problem:
Android Emulator
Tests work perfectly.
iOS Emulator
The test in question is verifying form validations on an ionic hybrid application. After initial form interaction on the emulator the following tests all fail as they are unable to utilize clear() or sendKeys() commands; the below error is thrown.
Error: [element.sendKeys("firstName")] Error response status: 13, UnknownError - An unknown server-side error occurred while processing the command. Selenium error: An unknown server-side error occurred while processing the command. Original error: Error while executing atom: Element is not currently inter-actable and may not be manipulated (status: 12)
Adding delay times between tests has no effect, changing the order of the tests results in the first one passing and the rest failing. Putting the tests in different test files results in them all passing. Any suggestions much appreciated!!
Manually
Interfacing with the app manually in the emulator the form inputs are all active after responding to an input validation and I am able to submit the form a second time.
Environment
Appium version: 1.72
Desktop OS/version : MAC OS High Sierra 10.13.3
Node.js version: 6.10.3
platform/version under test: iOS 10.3
My Code
Test Code
Appium Logs
Was able to get it working through the use of the retries method provided by the Mocha framework, not sure this is the most effective solution though.
https://github.com/appium/appium/issues/10256
describe('XYZ SCREEN: xyz.test.js', function() {
this.retries(30);
it('Should do something', async function() {
await test code ...
});
});

Where are errors logged when a DeployR script is called remotely?

I am trying to debug my deployR script which gives a generic error "HTTP 400 Error" / "Bad Request" at the Web application end when it fails.
Is there a way to get DeployR to pass a more informative error to the web application. i.e. Typically whatever error message the underlying R program has thrown at Deployr?
If I do a local execution then DeployR does log these messages to the Console pane. But if the script is called Remotely where does it log these errors? Even if I have a deployr Session open simultaneously the Console does not seem to show anything.
Any ideas or Workarounds?
There is an API to retrieve console output. See https://deployr.revolutionanalytics.com/documents/dev/api-doc/guide/workingprojects.html#projectexecuteconsole

Rstudio How to suppress console messages until end of script

When running a script with a large number of lines RStudio always lags and freezes due to the output/echo that appears in the console. Is there any way to suppress the console messages entirely or at least suppress the repetition of the input that occurs when a script is run?

Resources