"byte index [number] is not a char boundary; it is inside '[string]' ..."

[jpmckinney]

I occasionally see messages like:

thread 'tokio-runtime-worker' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rust_xlsxwriter-0.79.0/src/xmlwriter.rs:291:20:
byte index 67 is not a char boundary; it is inside '”' (bytes 66..69) of `paquetes_de_bolsas_rojas_plásticas_de_alta_densidad_de_18”_x_24”_1`
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Other examples of the middle message:

byte index 19 is not a char boundary; it is inside '½' (bytes 18..20) of `tubos_de_1_½_x_1_½_chapa_16_1`
byte index 39 is not a char boundary; it is inside '’' (bytes 38..41) of `manguera_traslucida_de_colores_½_x_75’_1`
byte index 16 is not a char boundary; it is inside '°' (bytes 15..17) of `codo_de_2"_x_90°_1`
byte index 23 is not a char boundary; it is inside '´' (bytes 22..24) of `codo_pvc_liso_1/2_x_90´_1`
byte index 29 is not a char boundary; it is inside '´' (bytes 28..30) of `tuberia_conduit_emt_3/4_x_10´ul__05501ul_1`
byte index 15 is not a char boundary; it is inside '°' (bytes 14..16) of `codo_1/2"_x_90°_1`
byte index 264 is not a char boundary; it is inside '¼' (bytes 263..265) of `sistema_de_sonido_portátil:_______________________________________________________sistema_de_sonido_portátil_de_300_watts_de_potencia,_2_parlantes_y_una_mezcladora:
-_sistema_de_altavoces_de_dos_vías_con_woofer_de_10_pulgadas.
-_7_canales
-_6_combinaci`[...]

[kindly]

Do you have an example JSON file I could use where this happened. I suspect it's due to new rust xlsx writer having unicode issues but it's hard to tell from the above.

[kindly]

@jpmckinney This is an issue in the xlsxwriter library. Have submitted pull request jmcnamara/rust_xlsxwriter#142 to fix it.

[jpmckinney]

Awesome, thank you!

[kindly]

@jpmckinney The latest release has the fixed version of rust_xlsxwriter so these issues should be fixed.

[jmcnamara]

This was fixed in rust_xlsxwriter v0.84.2 but I would recommend upgrading to v0.85.0 which has come out in the meantime.

[kindly]

@jmcnamara thanks. I will use the new tmpdir feature too when I upgrade as it makes more sense in this library to set the tmp directory to the same place the xlsx is written.