Resolved issue with crypto global market history as the API endpoint had changed.
Expecting spelling note to be returned
RHUB Results
> rhub::last_check()
── crypto 1.1.3: OK
Build ID: crypto_1.1.3.tar.gz-b4901dd3893844898ca37fb196f382fc
Platform: Windows Server 2008 R2 SP1, R-devel, 32/64 bit
Submitted: 3h 45m 7s ago
Build time: 8m 23.8s
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
── crypto 1.1.3: OK
Build ID: crypto_1.1.3.tar.gz-ed73d97bd448496db36467f22d2c82d8
Platform: Ubuntu Linux 16.04 LTS, R-release, GCC
Submitted: 3h 45m 7s ago
Build time: 23m 11.3s
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
── crypto 1.1.3: NOTE
Build ID: crypto_1.1.3.tar.gz-0494c0cc2b774c0981d7920af82b834a
Platform: Fedora Linux, R-devel, clang, gfortran
Submitted: 3h 45m 7s ago
Build time: 28m 41.7s
❯ checking CRAN incoming feasibility ...NB: need Internet access to use CRAN incoming checks
NOTE
Maintainer: ‘Jesse Vent <cryptopackage@icloud.com>’
Possibly mis-spelled words in DESCRIPTION:
Cryptocurrency (3:8)
crypto (4:24, 4:230)
0 errors ✔ | 0 warnings ✔ | 1 note ✖
To resolve advice from CRAN around elegant handling of web service error messages I have introduced new wrapper function to handle error/warning messages and updated the references in the rest of the package to match. Also made scraper function more robust at handling the multiple tables now returned when retrieving coin history to resolve an error regarding which list index to use.
CRAN repository db overrides:
X-CRAN-Comment: Archived on 2019-11-16 as check problems were not
corrected in time.
Apologies for missing the date
Rhub results
> rhub::last_check()
── crypto 1.1.2: OK
Build ID: crypto_1.1.2.tar.gz-088621685dd54a7cbef656f197b4b335
Platform: Windows Server 2008 R2 SP1, R-devel, 32/64 bit
Submitted: 21h 34m 31.2s ago
Build time: 6m 51.3s
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
── crypto 1.1.2: OK
Build ID: crypto_1.1.2.tar.gz-a61ada3b32574e51a816ec8c7c65d80a
Platform: Ubuntu Linux 16.04 LTS, R-release, GCC
Submitted: 21h 34m 31.2s ago
Build time: 17m 37.5s
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
── crypto 1.1.2: OK
Build ID: crypto_1.1.2.tar.gz-0301f11569e64d90af1778f7b441fd8b
Platform: Fedora Linux, R-devel, clang, gfortran
Submitted: 21h 34m 31.2s ago
Build time: 20m 0.8s
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
To resolve the following crypto ERRORs and NOTEs under R-oldrelease
Thanks for letting me know
Changes
I have opted to provide message advising to install keyring package instead of prompting installation of keyring package through use of askYesNo, as my preference is for the package to work for R 3.4
Expected Note
Possibly mis-spelled words in DESCRIPTION:
crypto (4:24, 4:230)
Cryptocurrency (3:8)
Note Comments
The following words are now included in the oxford dictionary:
Winbuilder Check Results
Your package crypto_1.1.1.tar.gz has been built (if working) and checked for Windows.
Please check the log files and (if working) the binary package at:
https://win-builder.r-project.org/4axVQenM4q1a
The files will be removed after roughly 72 hours.
Installation time in seconds: 11
Check time in seconds: 194
Status: 1 NOTE
R version 3.5.2 (2018-12-20)
Rhub Check Results
> rhub::list_package_checks(howmany = 6)
package version status submitted platform
1 crypto 1.1.1 note ~2h ago fedora-clang-devel
2 crypto 1.1.1 note ~2h ago ubuntu-gcc-release
3 crypto 1.1.1 note ~2h ago windows-x86_64-devel
4 crypto 1.1.1 ok ~2h ago fedora-clang-devel
5 crypto 1.1.1 note ~2h ago ubuntu-gcc-release
6 crypto 1.1.1 note ~2h ago windows-x86_64-devel
Checks Completed On RHub Winbuilder Check Results
Your package crypto_1.2.0.tar.gz has been built (if working) and checked for Windows.
Please check the log files and (if working) the binary package at:
https://win-builder.r-project.org/N53I6FsQ14bU
The files will be removed after roughly 72 hours.
Installation time in seconds: 10
Check time in seconds: 100
Status: OK
R version 3.5.1 (2018-07-02)
Notes regard usage of doSNOW, no alternative please see previous comments below for note resolution.
crypto_history()
functionencoding.R
to not change locale for existing windows UTF-8 encodingNotes regard usage of doSNOW, no alternative please see previous comments below for note resolution.
My sincere apologies for the resubmission, wasting your time was not my intention
Added list length check into daily_market function to handle different length columns
Your package crypto_1.0.0.tar.gz has been built (if working) and checked for Windows. Please check the log files and (if working) the binary package at: https://win-builder.r-project.org/nJgAFzn14Xf3 The files will be removed after roughly 72 hours. Installation time in seconds: 13 Check time in seconds: 161 Status: 1 NOTE R Under development (unstable) (2018-05-27 r74786)
global_market()
and daily_market()
which retrieve timeseries data for charts and visualisationsreplace_encoding()
and reset_encoding()
to handle locale encoding issues which will change encoding to UTF-8, then at end of function call will reset back to users original locale setting. Github Issue: Data inconsistency #19getCoins(), listCoins(), getPrices(), getExchanges() and crypto2xts()
functions to warn about the function names changing to crypto_history(), crypto_list(), crypto_prices(), crypto_exchanges() and crypto_xts()
respectively.repair_dependencies()
to prompt user to reinstall dependant packages based on feedback from github issues Github Issue: Error when running getCoins #20Notes regard usage of doSNOW, no alternative please see previous comments below for note resolution.
Please let me know if email address change is not allowed, just trying to protect my own privacy a bit more as I have been getting a large amount of unsolicited contact through different channels and trying to consolidate public contact details.
Your package crypto_0.1.6.tar.gz has been built (if working) and checked for Windows.
Please check the log files and (if working) the binary package at:
https://win-builder.r-project.org/grYhYUjUETas
The files will be removed after roughly 72 hours.
Installation time in seconds: 8
Check time in seconds: 127
Status: 1 NOTE
R Under development (unstable) (2018-04-28 r74669)
Apologies for resubmission, but I identified a defect in one of my functions that was returning the wrong result when packaged. Change summary is below:
The reason I am using doSNOW is due to some of the lower level features included in the package that are not included in doParallel (doSNOW last updated 2017-12-14)
The main function web scrapes over 1300+ pages, and can take anywhere from 1-10 minutes to run, but while doing so the progress bar really helps to show progression.
I did attempt to swap doSNOW over to doParallel; but using doSNOW was the only way I could get real time updates to occur and inform the user.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.