Build #196929 2019-11-07T15:46:15.215306+00:00
# rustc version
rustc 1.40.0-nightly (38048763e 2019-11-06)
# docs.rs version
docsrs 0.6.0 (2cc016f 2019-11-06)
# build log
[INFO] running `"docker" "create" "-v" "/home/cratesfyi/workspace/builds/ynab-api-3.0.0/target:/opt/rustwide/target:rw,Z" "-v" "/home/cratesfyi/workspace/builds/ynab-api-3.0.0/source:/opt/rustwide/workdir:ro,Z" "-v" "/home/cratesfyi/workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/home/cratesfyi/workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=1001" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "RUSTFLAGS=" "-e" "RUSTDOCFLAGS=-Z unstable-options --resource-suffix -20191106-1.40.0-nightly-38048763e --static-root-path / --disable-per-crate-search --extern-html-root-url serde=https://docs.rs/serde/1.0.102 --extern-html-root-url serde_json=https://docs.rs/serde_json/1.0.41 --extern-html-root-url reqwest=https://docs.rs/reqwest/0.9.22 --extern-html-root-url url=https://docs.rs/url/1.7.2 --extern-html-root-url serde_derive=https://docs.rs/serde_derive/1.0.102" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "3221225472" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "doc" "--lib" "--no-deps" "--target" "x86_64-unknown-linux-gnu"`
[INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
[INFO] [stdout] eae7bbbb1b7d2fc73b0d4ac2248d2cfc558fea0c649c7a02da66357084d05b34
[INFO] running `"docker" "start" "-a" "eae7bbbb1b7d2fc73b0d4ac2248d2cfc558fea0c649c7a02da66357084d05b34"`
[INFO] [stderr] Compiling libc v0.2.65
[INFO] [stderr] Checking cfg-if v0.1.10
[INFO] [stderr] Compiling autocfg v0.1.7
[INFO] [stderr] Compiling semver-parser v0.7.0
[INFO] [stderr] Checking lazy_static v1.4.0
[INFO] [stderr] Compiling maybe-uninit v2.0.0
[INFO] [stderr] Compiling cc v1.0.47
[INFO] [stderr] Checking futures v0.1.29
[INFO] [stderr] Compiling byteorder v1.3.2
[INFO] [stderr] Compiling log v0.4.8
[INFO] [stderr] Compiling version_check v0.1.5
[INFO] [stderr] Compiling proc-macro2 v1.0.6
[INFO] [stderr] Checking either v1.5.3
[INFO] [stderr] Compiling unicode-xid v0.2.0
[INFO] [stderr] Checking rand_core v0.4.2
[INFO] [stderr] Checking scopeguard v1.0.0
[INFO] [stderr] Compiling syn v1.0.7
[INFO] [stderr] Checking matches v0.1.8
[INFO] [stderr] Checking slab v0.4.2
[INFO] [stderr] Checking fnv v1.0.6
[INFO] [stderr] Compiling pkg-config v0.3.17
[INFO] [stderr] Checking itoa v0.4.4
[INFO] [stderr] Compiling memchr v2.2.1
[INFO] [stderr] Compiling serde v1.0.102
[INFO] [stderr] Checking rustc-demangle v0.1.16
[INFO] [stderr] Compiling bitflags v1.2.1
[INFO] [stderr] Compiling ryu v1.0.2
[INFO] [stderr] Checking foreign-types-shared v0.1.1
[INFO] [stderr] Compiling failure_derive v0.1.6
[INFO] [stderr] Checking percent-encoding v1.0.1
[INFO] [stderr] Compiling openssl v0.10.25
[INFO] [stderr] Compiling httparse v1.3.4
[INFO] [stderr] Compiling crc32fast v1.2.0
[INFO] [stderr] Compiling native-tls v0.2.3
[INFO] [stderr] Checking percent-encoding v2.1.0
[INFO] [stderr] Checking try-lock v0.2.2
[INFO] [stderr] Checking regex-syntax v0.6.12
[INFO] [stderr] Checking openssl-probe v0.1.2
[INFO] [stderr] Checking adler32 v1.0.4
[INFO] [stderr] Compiling encoding_rs v0.8.20
[INFO] [stderr] Checking mime v0.3.14
[INFO] [stderr] Checking dtoa v0.4.4
[INFO] [stderr] Checking try_from v0.3.2
[INFO] [stderr] Checking crossbeam-utils v0.6.6
[INFO] [stderr] Checking thread_local v0.3.6
[INFO] [stderr] Compiling semver v0.9.0
[INFO] [stderr] Compiling crossbeam-utils v0.7.0
[INFO] [stderr] Compiling crossbeam-epoch v0.8.0
[INFO] [stderr] Compiling indexmap v1.3.0
[INFO] [stderr] Compiling rand_chacha v0.1.1
[INFO] [stderr] Compiling rand_pcg v0.1.2
[INFO] [stderr] Compiling rand v0.6.5
[INFO] [stderr] Compiling unicase v2.5.1
[INFO] [stderr] Compiling error-chain v0.12.1
[INFO] [stderr] Checking lock_api v0.3.1
[INFO] [stderr] Checking rand_core v0.3.1
[INFO] [stderr] Checking rand_jitter v0.1.4
[INFO] [stderr] Checking unicode-bidi v0.3.4
[INFO] [stderr] Checking tokio-sync v0.1.7
[INFO] [stderr] Compiling backtrace-sys v0.1.32
[INFO] [stderr] Checking foreign-types v0.3.2
[INFO] [stderr] Compiling openssl-sys v0.9.52
[INFO] [stderr] Checking miniz_oxide v0.3.5
[INFO] [stderr] Checking tokio-executor v0.1.8
[INFO] [stderr] Checking crossbeam-queue v0.1.2
[INFO] [stderr] Compiling rustc_version v0.2.3
[INFO] [stderr] Checking rand_isaac v0.1.1
[INFO] [stderr] Checking rand_xorshift v0.1.1
[INFO] [stderr] Checking rand_hc v0.1.0
[INFO] [stderr] Checking smallvec v0.6.13
[INFO] [stderr] Checking tokio-current-thread v0.1.6
[INFO] [stderr] Checking tokio-timer v0.2.11
[INFO] [stderr] Checking iovec v0.1.4
[INFO] [stderr] Checking num_cpus v1.11.0
[INFO] [stderr] Checking net2 v0.2.33
[INFO] [stderr] Checking time v0.1.42
[INFO] [stderr] Checking rand_os v0.1.3
[INFO] [stderr] Checking want v0.2.0
[INFO] [stderr] Compiling parking_lot_core v0.6.2
[INFO] [stderr] Compiling memoffset v0.5.2
[INFO] [stderr] Compiling parking_lot v0.9.0
[INFO] [stderr] Compiling hyper v0.12.35
[INFO] [stderr] Checking base64 v0.10.1
[INFO] [stderr] Compiling quote v1.0.2
[INFO] [stderr] Checking aho-corasick v0.7.6
[INFO] [stderr] Checking flate2 v1.0.12
[INFO] [stderr] Checking unicode-normalization v0.1.9
[INFO] [stderr] Checking bytes v0.4.12
[INFO] [stderr] Checking futures-cpupool v0.1.8
[INFO] [stderr] Checking mio v0.6.19
[INFO] [stderr] Compiling mime_guess v2.0.1
[INFO] [stderr] Checking backtrace v0.3.40
[INFO] [stderr] Checking regex v1.3.1
[INFO] [stderr] Checking idna v0.1.5
[INFO] [stderr] Checking idna v0.2.0
[INFO] [stderr] Checking tokio-io v0.1.12
[INFO] [stderr] Checking http v0.1.19
[INFO] [stderr] Checking tokio-buf v0.1.1
[INFO] [stderr] Checking string v0.2.1
[INFO] [stderr] Checking uuid v0.7.4
[INFO] [stderr] Checking url v1.7.2
[INFO] [stderr] Checking url v2.1.0
[INFO] [stderr] Compiling synstructure v0.12.2
[INFO] [stderr] Checking cookie v0.12.0
[INFO] [stderr] Checking publicsuffix v1.5.3
[INFO] [stderr] Checking tokio-reactor v0.1.10
[INFO] [stderr] Checking http-body v0.1.0
[INFO] [stderr] Checking h2 v0.1.26
[INFO] [stderr] Checking crossbeam-deque v0.7.2
[INFO] [stderr] Checking tokio-tcp v0.1.3
[INFO] [stderr] Checking tokio-threadpool v0.1.16
[INFO] [stderr] Checking tokio v0.1.22
[INFO] [stderr] Compiling serde_derive v1.0.102
[INFO] [stderr] Checking failure v0.1.6
[INFO] [stderr] Checking hyper-tls v0.3.2
[INFO] [stderr] Checking serde_json v1.0.41
[INFO] [stderr] Checking serde_urlencoded v0.5.5
[INFO] [stderr] Checking cookie_store v0.7.0
[INFO] [stderr] Checking reqwest v0.9.22
[INFO] [stderr] Documenting ynab-api v3.0.0 (/opt/rustwide/workdir)
[INFO] [stderr] warning: `[milliunit_amount]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/hybrid_transaction.rs:50:242
[INFO] [stderr] |
[INFO] [stderr] 50 | /// If the Transaction was imported, this field is a unique (by account) import identifier. If this transaction was imported through File Based Import or Direct Import and not through the API, the import_id will have the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.
[INFO] [stderr] | ^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = note: `#[warn(intra_doc_link_resolution_failure)]` on by default
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[iso_date]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/hybrid_transaction.rs:50:261
[INFO] [stderr] |
[INFO] [stderr] 50 | /// If the Transaction was imported, this field is a unique (by account) import identifier. If this transaction was imported through File Based Import or Direct Import and not through the API, the import_id will have the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.
[INFO] [stderr] | ^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[occurrence]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/hybrid_transaction.rs:50:272
[INFO] [stderr] |
[INFO] [stderr] 50 | /// If the Transaction was imported, this field is a unique (by account) import identifier. If this transaction was imported through File Based Import or Direct Import and not through the API, the import_id will have the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.
[INFO] [stderr] | ^^^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[milliunit_amount]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/save_transaction.rs:44:452
[INFO] [stderr] |
[INFO] [stderr] 44 | /// If specified, the new transaction will be assigned this import_id and considered \"imported\". We will also attempt to match this imported transaction to an existing \"user-entered\" transation on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).
[INFO] [stderr] | ^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[iso_date]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/save_transaction.rs:44:471
[INFO] [stderr] |
[INFO] [stderr] 44 | /// If specified, the new transaction will be assigned this import_id and considered \"imported\". We will also attempt to match this imported transaction to an existing \"user-entered\" transation on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).
[INFO] [stderr] | ^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[occurrence]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/save_transaction.rs:44:482
[INFO] [stderr] |
[INFO] [stderr] 44 | /// If specified, the new transaction will be assigned this import_id and considered \"imported\". We will also attempt to match this imported transaction to an existing \"user-entered\" transation on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).
[INFO] [stderr] | ^^^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[milliunit_amount]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/transaction_detail.rs:50:242
[INFO] [stderr] |
[INFO] [stderr] 50 | /// If the Transaction was imported, this field is a unique (by account) import identifier. If this transaction was imported through File Based Import or Direct Import and not through the API, the import_id will have the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.
[INFO] [stderr] | ^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[iso_date]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/transaction_detail.rs:50:261
[INFO] [stderr] |
[INFO] [stderr] 50 | /// If the Transaction was imported, this field is a unique (by account) import identifier. If this transaction was imported through File Based Import or Direct Import and not through the API, the import_id will have the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.
[INFO] [stderr] | ^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[occurrence]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/transaction_detail.rs:50:272
[INFO] [stderr] |
[INFO] [stderr] 50 | /// If the Transaction was imported, this field is a unique (by account) import identifier. If this transaction was imported through File Based Import or Direct Import and not through the API, the import_id will have the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.
[INFO] [stderr] | ^^^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[milliunit_amount]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/transaction_summary.rs:50:242
[INFO] [stderr] |
[INFO] [stderr] 50 | /// If the Transaction was imported, this field is a unique (by account) import identifier. If this transaction was imported through File Based Import or Direct Import and not through the API, the import_id will have the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.
[INFO] [stderr] | ^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[iso_date]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/transaction_summary.rs:50:261
[INFO] [stderr] |
[INFO] [stderr] 50 | /// If the Transaction was imported, this field is a unique (by account) import identifier. If this transaction was imported through File Based Import or Direct Import and not through the API, the import_id will have the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.
[INFO] [stderr] | ^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[occurrence]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/transaction_summary.rs:50:272
[INFO] [stderr] |
[INFO] [stderr] 50 | /// If the Transaction was imported, this field is a unique (by account) import identifier. If this transaction was imported through File Based Import or Direct Import and not through the API, the import_id will have the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.
[INFO] [stderr] | ^^^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[milliunit_amount]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/update_transaction.rs:46:452
[INFO] [stderr] |
[INFO] [stderr] 46 | /// If specified, the new transaction will be assigned this import_id and considered \"imported\". We will also attempt to match this imported transaction to an existing \"user-entered\" transation on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).
[INFO] [stderr] | ^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[iso_date]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/update_transaction.rs:46:471
[INFO] [stderr] |
[INFO] [stderr] 46 | /// If specified, the new transaction will be assigned this import_id and considered \"imported\". We will also attempt to match this imported transaction to an existing \"user-entered\" transation on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).
[INFO] [stderr] | ^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `[occurrence]` cannot be resolved, ignoring it...
[INFO] [stderr] --> src/models/update_transaction.rs:46:482
[INFO] [stderr] |
[INFO] [stderr] 46 | /// If specified, the new transaction will be assigned this import_id and considered \"imported\". We will also attempt to match this imported transaction to an existing \"user-entered\" transation on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).
[INFO] [stderr] | ^^^^^^^^^^ cannot be resolved, ignoring
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1m 03s
[INFO] running `"docker" "inspect" "eae7bbbb1b7d2fc73b0d4ac2248d2cfc558fea0c649c7a02da66357084d05b34"`
[INFO] running `"docker" "rm" "-f" "eae7bbbb1b7d2fc73b0d4ac2248d2cfc558fea0c649c7a02da66357084d05b34"`
[INFO] [stdout] eae7bbbb1b7d2fc73b0d4ac2248d2cfc558fea0c649c7a02da66357084d05b34