# Confuse on changelog v1.2 on loadContents

**URL:** <https://cwl.discourse.group/t/confuse-on-changelog-v1-2-on-loadcontents/796>\
**Category:** CWL Questions\
**Created:** [May 10, 2023, 5:31pm UTC](https://cwl.discourse.group/t/confuse-on-changelog-v1-2-on-loadcontents/796 "2023-05-10T17:31:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![green555](https://yyz2.discourse-cdn.com/free1/user_avatar/cwl.discourse.group/green555/32/460_2.png) [@green555](https://cwl.discourse.group/u/green555)\
**Post date:** [May 10, 2023, 5:31pm UTC](https://cwl.discourse.group/t/confuse-on-changelog-v1-2-on-loadcontents/796/1 "2023-05-10T17:31:32Z")

</div>

Greetings!

According to CommandLineTool v1.2 ChangeLog:

- When using `loadContents` it now must fail when attempting to load a file greater than 64 KiB instead of silently truncating the data.

However it looks like v1.0 or v1.1 also fail when loadContents for large files instead of silently truncating. Am I missing something? I am using cwl-runner 3.0.20201203173111 for testing.

Thank you for your time in advance. I am trying to decide whether to revisit my previous v1.0 tools since they are written without concerning file size.

---

<div class="post-metadata">

**Author:** ![alexiswl](https://yyz2.discourse-cdn.com/free1/user_avatar/cwl.discourse.group/alexiswl/32/93_2.png) [@alexiswl](https://cwl.discourse.group/u/alexiswl)\
**Post date:** [September 21, 2023, 11:08pm UTC](https://cwl.discourse.group/t/confuse-on-changelog-v1-2-on-loadcontents/796/2 "2023-09-21T23:08:21Z")

</div>

Hi @green555,

Can you provide a reproducible example that shows the error that you’re seeing?

Alexis

---

<div class="post-metadata">

**Author:** ![mrc](https://yyz2.discourse-cdn.com/free1/user_avatar/cwl.discourse.group/mrc/32/3_2.png) [@mrc](https://cwl.discourse.group/u/mrc)\
**Post date:** [September 22, 2023, 11:18am UTC](https://cwl.discourse.group/t/confuse-on-changelog-v1-2-on-loadcontents/796/3 "2023-09-22T11:18:20Z")

</div>

Hello @green555

We decided to make cwltool more conservative even for CWL v1.0 and v1.1, as an exception was decided to be better than silently truncating too-large files.
