add handling unsupported nans in stringifying_unsupported

[asledz]

Before submitting checklist

• Did you update the CHANGELOG? (not for test updates, internal changes/refactors or CI/CD setup)
• Did you ask the docs owner to review all the user-facing changes?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Files	Coverage Δ
src/neptune/common/warnings.py	96.87% <100.00%> (+0.20%)	⬆️
src/neptune/internal/types/stringify_value.py	86.20% <100.00%> (+5.25%)	⬆️

... and 56 files with indirect coverage changes

📢 Thoughts on this report? Let us know!.

[antoinebrl]

Hello, I'm wondering how the system reacts when the logging a float series that contains NaN and inf.

run["value"] = 0.1
run["value"] = np.nan
run["value"] = 1

[normandy7]

Hello, I'm wondering how the system reacts when the logging a float series that contains NaN and inf.

run["value"] = 0.1
run["value"] = np.nan
run["value"] = 1

Hey @antoinebrl! Neptune will skip unsupported values when logging a series (see related docs).

Sidenote: In your snippet, each new value would overwrite the one previously assigned to that field. Use the append() method to create a series:

run["series"].append(value)

For more, see Logging series of values or files.