Skip to content

Releases: cognitedata/dotnet-extractor-utils

Release v1.40.0

23 Mar 10:52
f156431

Choose a tag to compare

Add option for changing ignoreBadDataPoints in GetExtractedRanges (#646)

* Add option for changing ignoreBadDataPoints in GetExtractedRanges

* remove false change

Release v1.39.1

12 Feb 13:57
1d96642

Choose a tag to compare

Fix handling of mismatched datapoints against CDM (#630)

This was causing issues, because the code assumed that if there was no identity with `Id` in the datapoints request, it must be there using `ExternalId`. Now that we can use `InstanceId` instead, that was no longer correct.

I've fixed the issue, and also made it so that we throw an explicit exception if this should ever happen again.

There's an implicit ordering here. _Technically_ a caller could reference a timeseries in multiple ways in the same request, but I think it's fair to call that outside of what we want to support. None of our extractors currently do this, and I think it would fail against the timeseries API at another time.

Release v1.39.0

17 Dec 11:56
f75ff1a

Choose a tag to compare

Update dependencies and release (#623)

* update dependencies and release

* fix breaking change

Release v1.38.0

20 Nov 08:19
81ccf00

Choose a tag to compare

[SEC-4668] Fix Nuget package signing by updating code sign github act…

Release v1.37.1

29 Oct 08:16
b9751e4

Choose a tag to compare

Backstop for logging secrets in ConfigToString (#600)

We really do want to avoid ever logging these. There is a workaround to
force it, but you have to explicitly opt-in which seems reasonable.

Release v1.37.0

22 Oct 09:01
34ae5b7

Choose a tag to compare

Update datapoint string limits to align with api changes and fix sequ…

Release v1.36.0

13 Aug 07:48
17730c7

Choose a tag to compare

Bump version (#570)

Release v1.35.0

27 Jun 06:11
4ee0842

Choose a tag to compare

make base class to enable writing as JSON to timeseries (#556)

Release v1.34.0

05 May 10:35
09ba90a

Choose a tag to compare

Add field to extractor to set the scheduler timeout (#543)

There's currently no way to pass this to the base extractor, so the timeout feature isn't very helpful...

Release v1.33.0

30 Apr 05:19
458c8d5

Choose a tag to compare

Add an optional timeout to the periodic scheduler (#539)

This can cause extractor shutdown to hang forever if there's an issue with shutting down a task, so we should allow setting a timeout.

Should we set a default? It would technically be a breaking change, but hanging forever seems unlikely to be desirable behavior.