Interactive console for Crystal programming language
JWT implementation in Crystal
greyblake/blogo 102
Mountable blog engine for Ruby on Rails
Simple and flexible HTTP client for Crystal with middleware and test support.
Watches changes in a rust project, runs test and shows friendly notification
A unified Crystal interface for key-value stores.
Crystal binding for LevelDB
crystal-community/bloom_filter 30
Bloom filter implementation in Crystal lang
greyblake/crystal-google_translate 12
Google Translate client for Crystal
greyblake/awesome-programming-books 11
List of good programming books for beginners and professionals
push eventgreyblake/dot-nvim
commit sha 2d053f6d06016c571eab76cb4561e6cc5f7ba396
Add support for LSP
commit sha 11509f8bfb18eae1fd732205e0b875d98cf3f95c
Setup skim for fuzzy search
push time in 4 hours
startedphil-opp/blog_os
started time in 6 hours
startedEmbarkStudios/rust-gpu
started time in a day
startedLemmyNet/lemmy
started time in 3 days
issue openedyujinakayama/guard-rubocop
Compatiblity with rubocop 1.0.0
Rubocop 1.0.0 was released today: https://metaredux.com/posts/2020/10/21/rubocop-1-0.html Are the any plans to update dependencies? Currently it's not possible to use rubocop 1.0.0, because guard-rubocop depends on 0.x versions for rubocop.
Thanks!
created time in 3 days
pull request commentgreyblake/ta-rs
Fix error in StandardDeviation
@edwardycl The fix is out in version 0.3.1
comment created time in 3 days
push eventgreyblake/ta-rs
commit sha e2b6c67e52d4b9b584decc68be665ecc0a3fa195
Prepare v0.3.1
push time in 3 days
push eventgreyblake/ta-rs
commit sha fa0d04c4a175624dc6019e2629cb3251adaaf704
Fix error in StandardDeviation
commit sha 6b312543837143b88def4134981bc2e131c56c4e
Merge pull request #32 from edwardycl/master Fix error in StandardDeviation
push time in 3 days
PR merged greyblake/ta-rs
let mut sd = StandardDeviation::new(6).unwrap();
assert_eq!(sd.next(1.872), 0.0);
assert_eq!(round(sd.next(1.0)), 0.436);
assert_eq!(round(sd.next(1.0)), 0.411);
assert_eq!(round(sd.next(1.0)), 0.378);
assert_eq!(round(sd.next(1.0)), 0.349);
assert_eq!(round(sd.next(1.0)), 0.325);
assert_eq!(round(sd.next(1.0)), 0.0);
Before the fix, this test failed at the last line because sd.next(1.0) would return NaN
The StandardDeviation calculation ends with (self.m2 / self.count as f64).sqrt(), and clearly self.m2 should be zero when six 1.0s are given.
But a floating-point error occurs, and self.m2 becomes -0.0000000000000000000000002757268708510092 - which is a negative number, and sqrt() of a negative number is NaN.
To prevent this, self.m2 must be set to zero if it's negative.
self.m2 can't be negative mathematically, so if it is, then it must be zero (+floating-point error).
pr closed time in 3 days
pull request commentgreyblake/ta-rs
Fix error in StandardDeviation
@edwardycl Interesting bug! Thank you for the report and fix!
comment created time in 3 days
startedgoogle/vimscript-language-server
started time in 6 days
startedlaunchbadge/sqlx
started time in 6 days
issue closedgreyblake/envconfig-rs
Automatically figure out the env var name from the field name
Hi,
when I have something like this:
#[derive(Envconfig)]
pub struct Config {
pub database_url: String
}
I would expect to be the same as:
#[derive(Envconfig)]
pub struct Config {
#[envconfig(from = "DATABASE_URL")]
pub database_url: String
}
Any reason why it doesn't convert that automatically ?
closed time in 9 days
vasilakisfil
issue commentgreyblake/envconfig-rs
Automatically figure out the env var name from the field name
@vasilakisfil FYI, I just merged PR enabling automatically deriving environment variable from field names: https://github.com/greyblake/envconfig-rs/pull/34
comment created time in 9 days
push eventgreyblake/envconfig-rs
commit sha fd5f915f62195eb631c7c61c910831f0979fbcb6
Derive env var names aumatically from a field name
commit sha 26a0776c583a8a912639189691930bec5f8e1ee2
Rework nested config structs
commit sha ab5694e7c9ccc3f02c3bb37515c9cadf473db89c
Rename test nesting.rs -> nested.rs
commit sha 087df487ee02052bfeb846b87386500b0e70b178
Fix formatting
commit sha 1dc3c5452c62d8946b16622a76d171018150e9a3
Address clippy warnings
commit sha 2db3346fe83a2b14d0688c32dbd027f7c4fcc7fd
Update CHANGELOG
commit sha 6ba0ddeebcb99a4c14949136ad71b2369841c896
Merge pull request #34 from greyblake/default-env-name Default env name
push time in 9 days
push eventgreyblake/envconfig-rs
commit sha 087df487ee02052bfeb846b87386500b0e70b178
Fix formatting
commit sha 1dc3c5452c62d8946b16622a76d171018150e9a3
Address clippy warnings
commit sha 2db3346fe83a2b14d0688c32dbd027f7c4fcc7fd
Update CHANGELOG
push time in 9 days
push eventgreyblake/envconfig-rs
commit sha 98f700fbbed23ecfcf4a299fae757382822d8037
Rename neasting -> nesting
push time in 13 days
created taggreyblake/envconfig-rs
Build a config structure from environment variables in Rust without boilerplate
created time in 14 days
push eventgreyblake/envconfig-rs
commit sha f97fe3a5194177df97a7667d75dec61b866f096c
Get rid of thiserror #32
commit sha 1e3b91f6e1bced90bb0346e148450d80a1b305fa
Merge pull request #33 from greyblake/get-rid-of-thiserror Get rid of thiserror #32
push time in 14 days
startedhecrj/iced
started time in 14 days
pull request commenth3poteto/logist
Add flat_json option for formatter
@h3poteto Thank you!
comment created time in 16 days
pull request commentgreyblake/ta-rs
Refactor: unify indicators behaviour
@tirz Thank you, looks pretty good! I have thoughts about replacing u32 with usize, but was not sure. In your changes I see, that avoiding the casting u32 -> usize justifies this.
Could pls explain Box<[f64]> thing to me and I'm ready to merge.
comment created time in 17 days
Pull request review commentgreyblake/ta-rs
Refactor: unify indicators behaviour
use serde::{Deserialize, Serialize}; #[cfg_attr(feature = "serde", derive(Serialize, Deserialize))] #[derive(Debug, Clone)] pub struct Maximum {- n: usize,- vec: Vec<f64>,+ period: usize, max_index: usize, cur_index: usize,+ deque: Box<[f64]>,
Could you please explain this change Vec<f64> VS Box<[f64]> ?
comment created time in 17 days
issue closedgreyblake/ta-rs
Any interest in serde support?
A while back I forked this repo for a summer project and one of the things I added to my fork was serde support before I got busy with school and work. If I opened a PR for that would it be welcome? In its present state it may be a bit disruptive to the API since if I recall correctly I had to adjust one of the traits.
closed time in 18 days
dgunay
startedh3poteto/logist
started time in 18 days
pull request commentgreyblake/ta-rs
refactor: rename _n_ and _length_ by _period_, replace Vec<f64> by Box<[f64]>, etc...
@tirz Sorry, I haven't taken a look at this yet. Will try to do it soon.
comment created time in 18 days
push eventgreyblake/ta-rs
commit sha ff2b78c193efbd1f96db42c72409a4d0657e1405
dep: bump csv to ~1.1.0
commit sha c117a2adbfc5e1408890c003c0dbbf4521e3d3c6
Merge pull request #30 from tirz/dependencies-update_csv dep: bump csv to ~1.1.0
push time in 18 days
pull request commentgreyblake/ta-rs
Add serde support to all indicators
@dgunay I just released a new version 0.3.0 with your change.
comment created time in 18 days
push eventgreyblake/ta-rs
commit sha 5046d600924e7402007018aa6d781420cde69679
prepare version 0.3.0
push time in 18 days
push eventgreyblake/ta-rs
commit sha e3e4ac6d609c4d0d27338b1fb5847fb11a62c66b
change travis to run on nightly/stable
commit sha 2dbdf73354303b48c607cc97a5e80bc72cf73c37
add .vscode to gitignore
commit sha 4a9df02292bf29a68e9a831588744dde67ee0d77
Merge branch 'macd-output'
commit sha 0a4d3243b8a6ebd772eda8c07609d7731e978e17
run cargo fmt
commit sha 3b816677baaac4f9d61dece228675536ecc793d2
don't run cargo --check on travis
commit sha be76735ca9e8c72d01f028fbd3e3f20ca9847c40
Add derived serde capability to all indicators
commit sha 602ec1aa7683ca828bc68b35a328353552f6e662
Merge commit 'be76735ca9' into serde-support
commit sha d70e291fe87cc23edd5d202177567361e65d9b7d
add serde to kc and ppo, add smoke test for serde
commit sha b116be3eb5f0c756e425acbc9066395690f69914
remove references to dgunay repo/CI
commit sha a2a7f18082c8d57e55994456b1627a7327cf88ba
cache deps when running CI
commit sha 453dff7c87f92ba76c1f50300927cacd05f0cd24
put serde behind a feature flag
commit sha 2ae71b0e0f7c26d7a02df54b37b9e6fca2987809
fix warning when not compiling w/ serde
commit sha d3868e27a024f5746803637d4057c44917eab828
revert changes to .travis.yml
commit sha 85bc708cc36756db8a6e3a1ec2b667bfc06cf940
Merge branch 'serde-support' of github.com:dgunay/ta-rs into serde-support
commit sha d1a2cfd94b4d307a03d649ff1b11a693f5605b35
Rename feature serde_support to serde
commit sha 6117c972f51f9c3ca48cbce29c4d8c15c82bffe3
remove unnecessary lifetimes
commit sha 80837f5c6abec717a7d501ebff039f7951403165
revert link to BB on wikipedia
commit sha 71417c2b67ebfc8b38cde04ca29352e71f0e4128
dont make serde a requirement to implement Next
commit sha 96efa738d8faa080f55dc9aecc31152f03159985
remove unnecessary lifetimes
commit sha bbb70283a22597e40d59426efc1e5aa71d46bddd
test with serde feature enabled
push time in 18 days
PR merged greyblake/ta-rs
Figured I'd just go ahead and open the PR. Adds serde support to all indicators using serde_derive.
Perhaps most importantly I changed the Next trait to require the implementation of Serialize and Deserialize:
pub trait Next<'a, T>: Serialize + Deserialize<'a>
There's only a test for one indicator but perhaps it's not even really necessary (since I imagine it would be unlikely to compile if it were broken given how serde_derive works).
If you would rather not bloat compilation times and maybe have it behind a feature flag or something that is totally fine, it's up to you. Thanks for maintaining this repo by the way, it was a big help for one of my projects.
pr closed time in 18 days
pull request commentgreyblake/ta-rs
Add serde support to all indicators
@dgunay Thanks for the great work!
comment created time in 18 days
push eventgreyblake/envconfig-rs
commit sha c5bb137e4cd0bea54c2eaba56f5d6ec9a0c69d19
Update README
push time in 18 days
push eventgreyblake/envconfig-rs
commit sha 02fbe5cc262acdd012ad62178f55690cfee92b45
Center badges on README page
push time in 18 days
push eventgreyblake/envconfig-rs
commit sha fd3cf7a9938bbf8a3680d617eb8dbc9653064ee1
Resize logo
push time in 18 days
push eventgreyblake/envconfig-rs
commit sha f2307bdc6b8747558e0dadd68f650ee0670902a2
Resize logo
push time in 18 days
push eventgreyblake/envconfig-rs
commit sha f56476dc21f196d713a73519805b7047315bfa16
Add logo to README
push time in 18 days
push eventgreyblake/envconfig-rs
commit sha 112644123742fb1b73512c05a78afe65583d4a33
Add logo
push time in 18 days
push eventgreyblake/envconfig-rs
commit sha 514c307d380dd4be0f622ac4410b5ba1c57b6764
Update README
push time in 18 days
push eventgreyblake/envconfig-rs
commit sha b60f1ef101da79c335e77f82f3994d98868813e2
Migrate to rust-2018 edition
commit sha 52ac50551acff77f0f9ed036e171638db460ca7f
Export derive macros
commit sha 73b14dc05c20b75945e281a998c68b22d54124cd
Use reexported Envconfig in tests without explicit usage of envconfig_derive
commit sha 48a01f5a34138557f352376624c666e3da00a13e
Update changelog
commit sha cc81745db0c516b7e9303804df5fa06f6eeca5b3
Deprecate init() function
commit sha ee40865ed1f89a1a01c2d4acef1368c5183d0dc9
Prepare for v0.9.0
commit sha 90179d33a6d342df8ab7a2cb6a7257d7f6a59260
version in depdency
commit sha 36d621f05e155c3ef377923a0cc08711609116aa
Merge pull request #31 from greyblake/rust-2018 Rust 2018
push time in 18 days
push eventgreyblake/envconfig-rs
commit sha 90179d33a6d342df8ab7a2cb6a7257d7f6a59260
version in depdency
push time in 18 days
issue commentgreyblake/envconfig-rs
Automatically figure out the env var name from the field name
Thanks for the idea. It must be possible to implement.
comment created time in 18 days
push eventgreyblake/envconfig-rs
commit sha cc81745db0c516b7e9303804df5fa06f6eeca5b3
Deprecate init() function
commit sha ee40865ed1f89a1a01c2d4acef1368c5183d0dc9
Prepare for v0.9.0
push time in 18 days
push eventgreyblake/logist
commit sha e5768eb46dbc3c7b9d2e4a8ccc05d75693df1380
Add flat_json option for formatter
push time in 18 days
PR opened h3poteto/logist
This PR addresses issue https://github.com/h3poteto/logist/issues/16
It adds flat_json boolean option, when it's set to true and message is a hash, the hash will be merged with the main hash (this way nested hash is avoided).
flat_json=false by default for backward compatibility.
If you merge this PR, please consider publish a new version to rubygems.
Thanks again. Sergey.
pr created time in 18 days
push eventgreyblake/logist
commit sha 0d2801a30ed840ad5b8649c93303496afdd908e4
Add flat_json option for formatter
push time in 18 days
push eventgreyblake/logist
commit sha 06dfe44643e04bb1c4fc486dfc8df8e1f444a3de
Set flat_json property
push time in 18 days
issue openedh3poteto/logist
Hi, we're using logist, thanks for this library.
We'd like to be able to log hashes like this:
Rails.logger(foo: 'bar', xyz: 'abc')
Currently the resulted output is a nested JSON:
{"level": "INFO", "message": {"foo": "bar", "xyz":"abc" }}
What is reasonable.
However to be able parse and index the logs properly we need all this logged attributes to be on top level (not a nested JSON), like:
{"level": "INFO", "foo": "bar", "xyz":"abc" }
I'd like to open PR to add flat_json (boolean) configuration option for Logger and Formatter.
Would you be possibly to accept and merge such PR?
Thanks in advance.
created time in 18 days
pull request commentgreyblake/ta-rs
Add serde support to all indicators
@dgunay Thanks for your update. One last thing (I hope).. could you please remove all the liftimes that were added in this PR, including those with indicators?
comment created time in 20 days
startedcurlpipe/ox
started time in 20 days
Pull request review commentgreyblake/ta-rs
Add serde support to all indicators
include = [ "README.md" ] +[features]+serde_support = ["serde"]
Could you please rename feature name serder_support -> serde?
comment created time in 20 days
Pull request review commentgreyblake/ta-rs
Add serde support to all indicators
pub trait Reset { /// [MACD](indicators/struct.MovingAverageConvergenceDivergence.html) it is `(f64, f64, f64)` since /// MACD returns 3 values. ///+#[cfg(feature = "serde_support")]+pub trait Next<T>: Serialize + DeserializeOwned {
Please revert changes in Next trait. Sorry for not mentioning this earlier.
The trait should not depend on other traits. If caller/client needs an indicator to be serializable they have to declare requirement for Serialize + Deserialize traits explicitly.
As you noticed the traits in this library (Next, Reset) are pretty much thin. It's done so by design with respect to Interface segregation principle
It could be that someone wants to implement own indicator and Next trait for it, but we should not force them to implement serialization if they don't need it.
comment created time in 20 days
Pull request review commentgreyblake/ta-rs
Add serde support to all indicators
use crate::{Close, Next, Reset}; /// /// # Links ///-/// * [Bollinger Bands, Wikipedia](https://en.wikipedia.org/wiki/Bollinger_Bands)+/// 
Please revert back this line
comment created time in 20 days
Pull request review commentgreyblake/ta-rs
Add serde support to all indicators
impl AverageTrueRange { } } -impl Next<f64> for AverageTrueRange {+impl<'a> Next<f64> for AverageTrueRange {
Please remove unnecessary liftimes here and in the other places. (they were removed on purpose a while ago: https://github.com/greyblake/ta-rs/pull/26)
comment created time in 20 days
Pull request review commentgreyblake/ta-rs
Add serde support to all indicators
language: rust+cache: cargo # cache dependencies to reduce compilation times rust: - stable install: - rustup component add rustfmt - rustup component add clippy script:- - cargo fmt -- --check+ # - cargo fmt -- --check # - cargo clippy -- -D warnings - cargo test - cargo package+jobs:+ allow_failures:+ - rust: nightly
Could you please remove back this new jobs section?
comment created time in 20 days
Pull request review commentgreyblake/ta-rs
Add serde support to all indicators
language: rust+cache: cargo # cache dependencies to reduce compilation times rust: - stable install: - rustup component add rustfmt - rustup component add clippy script:- - cargo fmt -- --check+ # - cargo fmt -- --check
Could you please revert this change?
comment created time in 20 days
pull request commentgreyblake/ta-rs
Add serde support to all indicators
@dgunay thanks for the PR.
If we add serde support, serde depedency must be optional and depend on serde feature flag (false by default) like it's done in other crates (see chrono for examlpe)
comment created time in 21 days
issue commentgreyblake/ta-rs
Any interest in serde support?
Hi @dgunay, ta is not involved in any kind of data serialization. Could you please clarify what do exactly mean by serde support?
comment created time in 22 days
startedllogiq/mutagen
started time in a month
push eventgreyblake/ta-rs
commit sha 4345862c064693b981d8a792bbb0922ebdf19cfd
refactor: remove declared but not mandatory lifetime
commit sha ed0ffb2eac3cb93aaa4b41131601507b6b5cc332
Merge pull request #26 from tirz/refactor-bound_lifetime refactor: remove declared but not mandatories lifetime parameters
push time in a month
push eventgreyblake/ta-rs
commit sha c382f9543494e14ca7fe2806361f55387b7e4b44
opti: remove usage of modulo
commit sha 2b2d644d2acd1469aa6c1de77e0d0e4ca12d1b5d
Merge branch 'master' into feature-opti_min_max_sd
commit sha 30574f5dad7d8f90bf91c07f3b04d8976fca04ee
Merge pull request #25 from tirz/feature-opti_min_max_sd opti: remove usage of modulo
push time in a month
PR merged greyblake/ta-rs
Remove usage of modulo to find the index of the next poped value for Minimum, Maximum and StandardDeviation.
Here is the benchmark with my i7 6500u: before:
test Maximum ... bench: 75,284 ns/iter (+/- 4,688)
test Minimum ... bench: 77,725 ns/iter (+/- 10,071)
test StandardDeviation ... bench: 68,862 ns/iter (+/- 5,893)
test BollingerBands ... bench: 86,684 ns/iter (+/- 7,133)
test FastStochastic ... bench: 163,767 ns/iter (+/- 22,085)
test SlowStochastic ... bench: 178,034 ns/iter (+/- 12,981)
after:
test Maximum ... bench: 32,359 ns/iter (+/- 1,353)
test Minimum ... bench: 32,091 ns/iter (+/- 1,369)
test StandardDeviation ... bench: 36,202 ns/iter (+/- 1,989)
test BollingerBands ... bench: 41,592 ns/iter (+/- 1,635)
test FastStochastic ... bench: 72,559 ns/iter (+/- 1,773)
test SlowStochastic ... bench: 92,549 ns/iter (+/- 2,997)
pr closed time in a month
pull request commentgreyblake/ta-rs
refactor: remove declared but not mandatories lifetime parameters
I almost sure the liftimes were mandatory in some older versions of rust. Thanks for the cleanup!
comment created time in a month
push eventtirz/ta-rs
commit sha 54888c6d6afa51961003ccc90f545023963a4cf1
doc: update ta-rs version
commit sha f798fd59d2ba37634366426ca18c265e4609f0c5
feat: add length() for SMA and remove usage of modulo
commit sha 62a40b24311ed7562a2084b5327c4e1cdf2511cf
Merge pull request #23 from tirz/doc-readme_dependency_version doc: update ta-rs version
commit sha a5b37989131ea5e2b4ef1038cc025688d61bf5e8
Merge pull request #24 from tirz/feature-sma_length feat: add length() for SMA
commit sha 2b2d644d2acd1469aa6c1de77e0d0e4ca12d1b5d
Merge branch 'master' into feature-opti_min_max_sd
push time in a month
push eventgreyblake/ta-rs
commit sha f798fd59d2ba37634366426ca18c265e4609f0c5
feat: add length() for SMA and remove usage of modulo
commit sha a5b37989131ea5e2b4ef1038cc025688d61bf5e8
Merge pull request #24 from tirz/feature-sma_length feat: add length() for SMA
push time in a month
PR merged greyblake/ta-rs
This PR may be usefull to implement others indicators like CCI.
It also remove the usage of the modulo used to find the index of the next poped value. As the result, SMA is almost three time faster on my compter (i7 6500u).
from:
test SimpleMovingAverage ... bench: 62,249 ns/iter (+/- 3,553)
to:
test SimpleMovingAverage ... bench: 22,371 ns/iter (+/- 610)
pr closed time in a month
pull request commentgreyblake/ta-rs
On my machine it dropped from 40,787 ns/iter -> 18,495 ns/iter.
Still very impressive, I did not know that using modulo could be that much expensive.
Thank you!
comment created time in a month
push eventgreyblake/ta-rs
commit sha 54888c6d6afa51961003ccc90f545023963a4cf1
doc: update ta-rs version
commit sha 62a40b24311ed7562a2084b5327c4e1cdf2511cf
Merge pull request #23 from tirz/doc-readme_dependency_version doc: update ta-rs version
push time in a month
push eventgreyblake/dot-nvim
commit sha d1990fbbf2f4a428b25da3c7ad07ed34e5586224
Add new deps
push time in a month
push eventgreyblake/vim-preview
commit sha 20817879d70c2473ef89092466aeb1fc80b09f26
Add support to Windows Chrome browser
commit sha d8f994db3ea7089cad158d851c6f6b21a3249f43
Merge pull request #47 from Ae-Mc/master Add support to Windows Chrome browser
push time in a month
pull request commentgreyblake/vim-preview
Add support to Windows Chrome browser
Thanks!
comment created time in a month
starteddropbox/pb-jelly
started time in a month
pull request commentgreyblake/ta-rs
feat: implement Percentage Price Oscillator (PPO)
@tirz Thank you!
comment created time in a month
push eventgreyblake/ta-rs
commit sha 2c0ff2df866ce1e3b3dbbddcf88c83f1af8bd1f3
feat: implement Percentage Price Oscillator (PPO)
commit sha 6daf73d5c6395acf5a3567e3b0137f04ae17e031
Merge pull request #22 from tirz/feature-ppo feat: implement Percentage Price Oscillator (PPO)
push time in a month
PR merged greyblake/ta-rs
PPO is a comparable MACD. The formula is a simple copy past from https://school.stockcharts.com/doku.php?id=technical_indicators:price_oscillators_ppo
pr closed time in a month