New warning message using latest dev version of the package

I installed the latest dev version by running devtools::install_bitbucket( 'QuantTools/QuantTools' ). But I got some new warning messages (or some messages that previous not exposed?). I believe it's related to the "trade_conditions", sometimes it just "01", "02", etc, but it can be "8E" or other values occasionally. Could you please make sure it's always parsed as character because this is field is a hex number in two-character string, implicitly convert a hex number like "11", "12", etc. to an integer would not be right.

QCLU17C5000 <- get_iqfeed_data('QCLU17C5000', from='2017-03-08', to='2017-08-09', period='tick') Warning messages: 1: In fread(message_chunk$complete, sep = ",") : Bumped column 10 to type character on data row 4662, field contains '8E'. Coercing previously read values in this column from logical, integer or numeric back to character which may not be lossless; e.g., if '00' and '000' occurred before they will now be just '0', and there may be inconsistencies with treatment of ',,' and ',NA,' too (if they occurred in this column before the bump). If this matters please rerun and set 'colClasses' to 'character' for this column. Please note that column type detection uses a sample of 1,000 rows (100 rows at 10 points) so hopefully this message should be very rare. If reporting to datatable-help, please rerun and include the output from verbose=TRUE. 2: In fread(message_chunk$complete, sep = ",") : Bumped column 10 to type character on data row 2422, field contains '8E'. Coercing previously read values in this column from logical, integer or numeric back to character which may not be lossless; e.g., if '00' and '000' occurred before they will now be just '0', and there may be inconsistencies with treatment of ',,' and ',NA,' too (if they occurred in this column before the bump). If this matters please rerun and set 'colClasses' to 'character' for this column. Please note that column type detection uses a sample of 1,000 rows (100 rows at 10 points) so hopefully this message should be very rare. If reporting to datatable-help, please rerun and include the output from verbose=TRUE.

Comments (4)