R Shiny: saving full session with settings for log/debug purposes
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am developing a shiny app, and as always, it is possible that something may crash or return unexpected results from the database, etc. For this the idea is to implement a simple bug report in the app.
The basic idea here is a button with shinyBS:::bsModal
popup, that gives the ability to write down the problem and log it/send it as an email.
However, it would be useful to also store the full session at the time of the submit for an easier debug. For example, so it could be possible to load it up and see the error.
Is this possible from a shiny app? Are there tools/functions made for specifically this purpose? Since debugging shiny apps, in my experience, is quite more difficult than usual R code.
r shiny
add a comment |
I am developing a shiny app, and as always, it is possible that something may crash or return unexpected results from the database, etc. For this the idea is to implement a simple bug report in the app.
The basic idea here is a button with shinyBS:::bsModal
popup, that gives the ability to write down the problem and log it/send it as an email.
However, it would be useful to also store the full session at the time of the submit for an easier debug. For example, so it could be possible to load it up and see the error.
Is this possible from a shiny app? Are there tools/functions made for specifically this purpose? Since debugging shiny apps, in my experience, is quite more difficult than usual R code.
r shiny
You can save the state of the app, including Input Parameters with: shiny.rstudio.com/articles/bookmarking-state.html.
– BigDataScientist
Nov 16 '18 at 12:51
@BigDataScientist worth looking into, thanks.
– Nutle
Nov 16 '18 at 13:12
Are there maybe any functions to dump the whole stdout of the previous console history to a file? One way would be to capture and discard (when not needed) stdout for every session, but it would be better if it's possible to do this retrospectivelly?
– Nutle
Nov 16 '18 at 13:13
@BigDataScientist Although, I'm not sure this will work as intended when not on RStudio Server, as I'm running through dockerized simplerunApp()
.
– Nutle
Nov 16 '18 at 13:17
add a comment |
I am developing a shiny app, and as always, it is possible that something may crash or return unexpected results from the database, etc. For this the idea is to implement a simple bug report in the app.
The basic idea here is a button with shinyBS:::bsModal
popup, that gives the ability to write down the problem and log it/send it as an email.
However, it would be useful to also store the full session at the time of the submit for an easier debug. For example, so it could be possible to load it up and see the error.
Is this possible from a shiny app? Are there tools/functions made for specifically this purpose? Since debugging shiny apps, in my experience, is quite more difficult than usual R code.
r shiny
I am developing a shiny app, and as always, it is possible that something may crash or return unexpected results from the database, etc. For this the idea is to implement a simple bug report in the app.
The basic idea here is a button with shinyBS:::bsModal
popup, that gives the ability to write down the problem and log it/send it as an email.
However, it would be useful to also store the full session at the time of the submit for an easier debug. For example, so it could be possible to load it up and see the error.
Is this possible from a shiny app? Are there tools/functions made for specifically this purpose? Since debugging shiny apps, in my experience, is quite more difficult than usual R code.
r shiny
r shiny
asked Nov 16 '18 at 12:29
NutleNutle
318217
318217
You can save the state of the app, including Input Parameters with: shiny.rstudio.com/articles/bookmarking-state.html.
– BigDataScientist
Nov 16 '18 at 12:51
@BigDataScientist worth looking into, thanks.
– Nutle
Nov 16 '18 at 13:12
Are there maybe any functions to dump the whole stdout of the previous console history to a file? One way would be to capture and discard (when not needed) stdout for every session, but it would be better if it's possible to do this retrospectivelly?
– Nutle
Nov 16 '18 at 13:13
@BigDataScientist Although, I'm not sure this will work as intended when not on RStudio Server, as I'm running through dockerized simplerunApp()
.
– Nutle
Nov 16 '18 at 13:17
add a comment |
You can save the state of the app, including Input Parameters with: shiny.rstudio.com/articles/bookmarking-state.html.
– BigDataScientist
Nov 16 '18 at 12:51
@BigDataScientist worth looking into, thanks.
– Nutle
Nov 16 '18 at 13:12
Are there maybe any functions to dump the whole stdout of the previous console history to a file? One way would be to capture and discard (when not needed) stdout for every session, but it would be better if it's possible to do this retrospectivelly?
– Nutle
Nov 16 '18 at 13:13
@BigDataScientist Although, I'm not sure this will work as intended when not on RStudio Server, as I'm running through dockerized simplerunApp()
.
– Nutle
Nov 16 '18 at 13:17
You can save the state of the app, including Input Parameters with: shiny.rstudio.com/articles/bookmarking-state.html.
– BigDataScientist
Nov 16 '18 at 12:51
You can save the state of the app, including Input Parameters with: shiny.rstudio.com/articles/bookmarking-state.html.
– BigDataScientist
Nov 16 '18 at 12:51
@BigDataScientist worth looking into, thanks.
– Nutle
Nov 16 '18 at 13:12
@BigDataScientist worth looking into, thanks.
– Nutle
Nov 16 '18 at 13:12
Are there maybe any functions to dump the whole stdout of the previous console history to a file? One way would be to capture and discard (when not needed) stdout for every session, but it would be better if it's possible to do this retrospectivelly?
– Nutle
Nov 16 '18 at 13:13
Are there maybe any functions to dump the whole stdout of the previous console history to a file? One way would be to capture and discard (when not needed) stdout for every session, but it would be better if it's possible to do this retrospectivelly?
– Nutle
Nov 16 '18 at 13:13
@BigDataScientist Although, I'm not sure this will work as intended when not on RStudio Server, as I'm running through dockerized simple
runApp()
.– Nutle
Nov 16 '18 at 13:17
@BigDataScientist Although, I'm not sure this will work as intended when not on RStudio Server, as I'm running through dockerized simple
runApp()
.– Nutle
Nov 16 '18 at 13:17
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53337949%2fr-shiny-saving-full-session-with-settings-for-log-debug-purposes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53337949%2fr-shiny-saving-full-session-with-settings-for-log-debug-purposes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You can save the state of the app, including Input Parameters with: shiny.rstudio.com/articles/bookmarking-state.html.
– BigDataScientist
Nov 16 '18 at 12:51
@BigDataScientist worth looking into, thanks.
– Nutle
Nov 16 '18 at 13:12
Are there maybe any functions to dump the whole stdout of the previous console history to a file? One way would be to capture and discard (when not needed) stdout for every session, but it would be better if it's possible to do this retrospectivelly?
– Nutle
Nov 16 '18 at 13:13
@BigDataScientist Although, I'm not sure this will work as intended when not on RStudio Server, as I'm running through dockerized simple
runApp()
.– Nutle
Nov 16 '18 at 13:17