Vadim

Results 14 issues of Vadim

Use [js-joda](https://github.com/js-joda/js-joda/) as the javascript impl.

enhancement
help wanted

`java-time.repl` provides a `show-path` function which provides a way to peek into the conversion graph. It's nice when one already knows the types used for the conversion, but doesn't help...

Includes support for * Tooltips * Multiple Y axes as well as a few other minor API additions. Missing: * Dial and Radar charts

Not sure what's exactly causing the issue, but once I nest templates deep enough the following happens upon trying to call the `cista::offset::to_vec(std::vector)` macro: ``` my.cpp: In function `cista::basic_vector::basic_vector()': /usr/local/cista/include/cista/containers/vector.h:21:...

Not sure if this is supposed to fail. Probably not, as the year isn't known. ``` java new Period(new Partial(DateTimeFieldType.dayOfYear(), 200), new Partial(DateTimeFieldType.dayOfYear(), 366)); // IllegalFieldValueException Value 366 for dayOfYear...

Bug
Hard

Currently there's no mechanism to propagate errors which happen in the stream transforming functions. The only option currently is to log the error and close the output stream. I often...

feature request

Would it make sense to add an `manifold.stream/upstream` analogous to already existing `manifold.stream/downstream`? I don't think it would be needed for any functionality currently, but would be great for graph...

feature request

I like the ideas behind `with-timestamps` and `with-counters` macros. However, their usage is harmed by having to manually assemble the composite collector maps of e.g. ```clojure (with-timestamps {:last-run (registry :app/last-run),...

question
need-investigation
design-change

Commons FileUpload allows limiting uploaded file/request size (throwing exception when the size is exceeded) by counting the bytes received over the wire. `ring.middleware.multipart-params` now accepts two more options: - max-request-size...

enhancement

Currently the `InfluxDbClientConfiguration` fails on empty username/password. It's possible to have InfluxDB instances unprotected, so the validation shouldn't be as strict. I propose removing the validation for the username/password fields.