===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
r-cran-promises-1.1.1+dfsg/vignettes/overview.Rmd-64-
r-cran-promises-1.1.1+dfsg/vignettes/overview.Rmd:65:You might guess that you could call a function or method on a promise to extract the value, like `value(promise)` or `promise$value()`. But that isn't how promises work. Instead, everything is based on a function called `then`.
r-cran-promises-1.1.1+dfsg/vignettes/overview.Rmd-66-
##############################################
r-cran-promises-1.1.1+dfsg/vignettes/intro.Rmd-253-
r-cran-promises-1.1.1+dfsg/vignettes/intro.Rmd:254:When `output$table` executes the `renderTable` code block, it will notice that
r-cran-promises-1.1.1+dfsg/vignettes/intro.Rmd-255-the result is a promise, and wait for it to complete before continuing with the
##############################################
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd-119-
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd:120:* `data` (`eventReactive`): Whenever `input$date` changes, the `data` reactive downloads the full log for that day from http://cran-logs.rstudio.com, and parses it.
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd:121:* `whales` (`reactive`): Reads from `data()`, tallies the number of downloads performed by each unique IP, and returns a data frame of the top `input$count` most prolific downloaders, along with their download counts.
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd-122-* `whale_downloads` (`reactive`): Joins the `data()` and `whales()` data frames, to return all of the details of the cetacean downloads.
##############################################
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd-240-
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd:241:The `whales` reactive takes the data frame from `data`, and uses dplyr to find the top `input$count` most prolific downloaders.
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd-242-
##############################################
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd-274-
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd:275:One last thing before we move on. In the last section, I emphasized that reactive values cannot be read from inside a future. Here, we're using `head(input$count)` inside a promise-pipeline; since `data()` is written using a future, doesn't that mean… well… isn't this wrong?
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd-276-
##############################################
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd-545-
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd:546:Note that neither the R6 call `p$set(message = ...)` nor the second `future()` call are tidy, so they use curly-brace blocks, as discussed in the above section about `biggest_whales`.
r-cran-promises-1.1.1+dfsg/vignettes/casestudy.Rmd-547-
##############################################
r-cran-promises-1.1.1+dfsg/R/is_something.R-9- identical(pipe, quote(`%<>%`)) ||
r-cran-promises-1.1.1+dfsg/R/is_something.R:10: identical(pipe, quote(`%$%`))
r-cran-promises-1.1.1+dfsg/R/is_something.R-11-}
##############################################
r-cran-promises-1.1.1+dfsg/R/is_something.R-36-{
r-cran-promises-1.1.1+dfsg/R/is_something.R:37: identical(pipe, quote(`%$%`))
r-cran-promises-1.1.1+dfsg/R/is_something.R-38-}
##############################################
r-cran-promises-1.1.1+dfsg/inst/doc/overview.Rmd-64-
r-cran-promises-1.1.1+dfsg/inst/doc/overview.Rmd:65:You might guess that you could call a function or method on a promise to extract the value, like `value(promise)` or `promise$value()`. But that isn't how promises work. Instead, everything is based on a function called `then`.
r-cran-promises-1.1.1+dfsg/inst/doc/overview.Rmd-66-
##############################################
r-cran-promises-1.1.1+dfsg/inst/doc/intro.Rmd-253-
r-cran-promises-1.1.1+dfsg/inst/doc/intro.Rmd:254:When `output$table` executes the `renderTable` code block, it will notice that
r-cran-promises-1.1.1+dfsg/inst/doc/intro.Rmd-255-the result is a promise, and wait for it to complete before continuing with the
##############################################
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd-119-
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd:120:* `data` (`eventReactive`): Whenever `input$date` changes, the `data` reactive downloads the full log for that day from http://cran-logs.rstudio.com, and parses it.
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd:121:* `whales` (`reactive`): Reads from `data()`, tallies the number of downloads performed by each unique IP, and returns a data frame of the top `input$count` most prolific downloaders, along with their download counts.
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd-122-* `whale_downloads` (`reactive`): Joins the `data()` and `whales()` data frames, to return all of the details of the cetacean downloads.
##############################################
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd-240-
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd:241:The `whales` reactive takes the data frame from `data`, and uses dplyr to find the top `input$count` most prolific downloaders.
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd-242-
##############################################
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd-274-
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd:275:One last thing before we move on. In the last section, I emphasized that reactive values cannot be read from inside a future. Here, we're using `head(input$count)` inside a promise-pipeline; since `data()` is written using a future, doesn't that mean… well… isn't this wrong?
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd-276-
##############################################
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd-545-
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd:546:Note that neither the R6 call `p$set(message = ...)` nor the second `future()` call are tidy, so they use curly-brace blocks, as discussed in the above section about `biggest_whales`.
r-cran-promises-1.1.1+dfsg/inst/doc/casestudy.Rmd-547-
##############################################
r-cran-promises-1.1.1+dfsg/debian/tests/run-unit-test-6-if [ "$AUTOPKGTEST_TMP" = "" ] ; then
r-cran-promises-1.1.1+dfsg/debian/tests/run-unit-test:7: AUTOPKGTEST_TMP=`mktemp -d /tmp/${debname}-test.XXXXXX`
r-cran-promises-1.1.1+dfsg/debian/tests/run-unit-test-8- trap "rm -rf $AUTOPKGTEST_TMP" 0 INT QUIT ABRT PIPE TERM