A light Elixir wrapper around exometer.
pinterest/riffed 289
Provides idiomatic Elixir bindings for Apache Thrift
A Pure Elixir Thrift Implementation
Fast memcached protocol client in pure Erlang
Consistent hashing ring for Distributed Hash Tables (DHT)
A mongoDB configuration and resilience framework
Configuration reload manager for Erlang applications
Bcrypt password hashing for Elixir
ClickHouse Python Driver with native interface support
An Elixir database driver for Clickhouse
push eventdiscord/jiffy
commit sha 0b2f2e5db61cf4e5d7d7073fb610b52a96f4485b
dont try to enable lto at all This is causing some issues for some developers where they can compile files with LTO, but linking fails. Our usage of JSON is small enough tha the small optimization loss isn't a big deal.
commit sha 39d3207f1c1d65b594c2c3188e99ea10f9029667
Merge pull request #8 from discord/no_lto dont try to enable lto at all
push time in 3 days
PR merged discord/jiffy
This is causing some issues for some developers where they can compile files with LTO, but linking fails. Our usage of JSON is small enough that the small optimization loss isn't a big deal.
pr closed time in 3 days
PR opened discord/jiffy
This is causing some issues for some developers where they can compile files with LTO, but linking fails. Our usage of JSON is small enough that the small optimization loss isn't a big deal.
pr created time in 3 days
push eventdiscord/jiffy
commit sha 0b2f2e5db61cf4e5d7d7073fb610b52a96f4485b
dont try to enable lto at all This is causing some issues for some developers where they can compile files with LTO, but linking fails. Our usage of JSON is small enough tha the small optimization loss isn't a big deal.
push time in 3 days
push eventdiscord/jiffy
commit sha f31f2866a63bcac643e23ab30d3dfa8b388dacb2
more options for encode()
commit sha a71845ce42f5e4f4609a019979919a0b3a7674f9
Merge pull request #7 from discord/bugfix/jiffy_encode_option_typespec more options for encode()
commit sha 55447cde29b58c6f505bae0824b9c9510526ea7a
dont try to enable lto at all
push time in 3 days
push eventdiscord/jiffy
commit sha c46dc7515f1a62a3e82e42cf2872397036ee50bc
dont try to enable lto at all
push time in 3 days
delete branch discord/jiffy
delete branch : bugfix/jiffy_encode_option_typespec
delete time in 4 days
push eventdiscord/jiffy
commit sha f31f2866a63bcac643e23ab30d3dfa8b388dacb2
more options for encode()
commit sha a71845ce42f5e4f4609a019979919a0b3a7674f9
Merge pull request #7 from discord/bugfix/jiffy_encode_option_typespec more options for encode()
push time in 4 days
create barnchdiscord/jiffy
branch : bugfix/jiffy_encode_option_typespec
created branch time in 7 days
delete branch pinterest/elixometer
delete branch : dependabot/hex/excoveralls-0.14.1
delete time in 10 days
push eventpinterest/elixometer
commit sha 699f84b7b7eb7d45399d05998f8ebaf269d3dea4
Bump excoveralls from 0.14.0 to 0.14.1 Bumps [excoveralls](https://github.com/parroty/excoveralls) from 0.14.0 to 0.14.1. - [Release notes](https://github.com/parroty/excoveralls/releases) - [Changelog](https://github.com/parroty/excoveralls/blob/master/CHANGELOG.md) - [Commits](https://github.com/parroty/excoveralls/compare/v0.14.0...v0.14.1) --- updated-dependencies: - dependency-name: excoveralls dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
commit sha 1e16953ddcf63764f20804970967b8036b4a3abe
Merge pull request #203 from pinterest/dependabot/hex/excoveralls-0.14.1
push time in 10 days
PR merged pinterest/elixometer
Bumps excoveralls from 0.14.0 to 0.14.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/parroty/excoveralls/releases">excoveralls's releases</a>.</em></p> <blockquote> <h2>v0.14.1</h2> <h4>Changes</h4> <ul> <li>Fix HTML tag typo (<a href="https://github-redirect.dependabot.com/parroty/excoveralls/issues/259">#259</a>).</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/parroty/excoveralls/blob/master/CHANGELOG.md">excoveralls's changelog</a>.</em></p> <blockquote> <h2>0.14.1</h2> <h4>Changes</h4> <ul> <li>Fix HTML tag typo (<a href="https://github-redirect.dependabot.com/parroty/excoveralls/issues/259">#259</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/parroty/excoveralls/commit/04acabcabe24315bd399ab12b488f9b0ae5468fd"><code>04acabc</code></a> Update version</li> <li><a href="https://github.com/parroty/excoveralls/commit/5720baf979b6ee4fe056995a98c8411b68b4cfe2"><code>5720baf</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/parroty/excoveralls/issues/259">#259</a> from roehst/bugfix-html-tag</li> <li><a href="https://github.com/parroty/excoveralls/commit/b54a3c126ab0fa494234702414c09c09f618d60b"><code>b54a3c1</code></a> Fix small HTML error</li> <li><a href="https://github.com/parroty/excoveralls/commit/825c24abedd11d1d0b54b059e77cc54df57b53d7"><code>825c24a</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/parroty/excoveralls/issues/256">#256</a> from zentetsukenz/update-setup-elixir-action</li> <li><a href="https://github.com/parroty/excoveralls/commit/6820e88da534af6167e39edb2addee90c1c35d04"><code>6820e88</code></a> Use the latest setup beam for github action</li> <li><a href="https://github.com/parroty/excoveralls/commit/9f48f290db3c1787ed019d5106f774c65f019677"><code>9f48f29</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/parroty/excoveralls/issues/251">#251</a> from sgerrand/patch-1</li> <li><a href="https://github.com/parroty/excoveralls/commit/95db8d1ddd185d42cbe09fac4056fd24cf7ba7fc"><code>95db8d1</code></a> Update license URL</li> <li>See full diff in <a href="https://github.com/parroty/excoveralls/compare/v0.14.0...v0.14.1">compare view</a></li> </ul> </details> <br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
pr closed time in 10 days
create barnchpinterest/elixometer
branch : dependabot/hex/excoveralls-0.14.1
created branch time in 10 days
PR opened pinterest/elixometer
Bumps excoveralls from 0.14.0 to 0.14.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/parroty/excoveralls/releases">excoveralls's releases</a>.</em></p> <blockquote> <h2>v0.14.1</h2> <h4>Changes</h4> <ul> <li>Fix HTML tag typo (<a href="https://github-redirect.dependabot.com/parroty/excoveralls/issues/259">#259</a>).</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/parroty/excoveralls/blob/master/CHANGELOG.md">excoveralls's changelog</a>.</em></p> <blockquote> <h2>0.14.1</h2> <h4>Changes</h4> <ul> <li>Fix HTML tag typo (<a href="https://github-redirect.dependabot.com/parroty/excoveralls/issues/259">#259</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/parroty/excoveralls/commit/04acabcabe24315bd399ab12b488f9b0ae5468fd"><code>04acabc</code></a> Update version</li> <li><a href="https://github.com/parroty/excoveralls/commit/5720baf979b6ee4fe056995a98c8411b68b4cfe2"><code>5720baf</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/parroty/excoveralls/issues/259">#259</a> from roehst/bugfix-html-tag</li> <li><a href="https://github.com/parroty/excoveralls/commit/b54a3c126ab0fa494234702414c09c09f618d60b"><code>b54a3c1</code></a> Fix small HTML error</li> <li><a href="https://github.com/parroty/excoveralls/commit/825c24abedd11d1d0b54b059e77cc54df57b53d7"><code>825c24a</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/parroty/excoveralls/issues/256">#256</a> from zentetsukenz/update-setup-elixir-action</li> <li><a href="https://github.com/parroty/excoveralls/commit/6820e88da534af6167e39edb2addee90c1c35d04"><code>6820e88</code></a> Use the latest setup beam for github action</li> <li><a href="https://github.com/parroty/excoveralls/commit/9f48f290db3c1787ed019d5106f774c65f019677"><code>9f48f29</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/parroty/excoveralls/issues/251">#251</a> from sgerrand/patch-1</li> <li><a href="https://github.com/parroty/excoveralls/commit/95db8d1ddd185d42cbe09fac4056fd24cf7ba7fc"><code>95db8d1</code></a> Update license URL</li> <li>See full diff in <a href="https://github.com/parroty/excoveralls/compare/v0.14.0...v0.14.1">compare view</a></li> </ul> </details> <br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
pr created time in 10 days
PR closed discord/jiffy
This catches this repo up to upstream's 1.0.8 tag (around 4 years worth of changes/fixes). It maintains the patches that existed from before. I'm not convinced a merge commit is the best way to do this, but open to ideas.
pr closed time in 21 days
pull request commentdiscord/jiffy
Ended up manually rebasing the old master on top of upstream's 1.0.8
comment created time in 21 days
push eventdiscord/jiffy
commit sha 79f1dd17259b71e3af2263d602099d8b1be2eba1
Add compile option no_native
commit sha 5337135b8313293927349fea0b14433f8337c0e8
update README.md fixing typo in maps example
commit sha 5d5cfe4f9b6cfd4e6d0ea429bf8eb62110a21145
Merge pull request #86 from clonejo/patch-1 update README.md fixing typo in maps example
commit sha 587f143e279ff586d90df31ea5e1c934cdde2e99
Changed pos to unsigned int to prevent warning from happening.
commit sha 446e284bd51013fe2899803b9dcbd162d8b8efb3
Merge pull request #92 from emfa/master Changed pos to unsigned int to prevent warning from happening.
commit sha cd1b2632083c3724b246c8e8107845d9903bc578
Add an option to control null value decoding atom This is pretty much a generalisation of the use_nil option to support an arbitrary atom.
commit sha 1784ca2ab567a3b52b8916565bb41db716c2b9ca
Add an option to escape forward slashes This brings back escaping forward slashes as an option during encoding. Default is still not to escape.
commit sha b403e4ab5b8f64ee1b62a9e23453e3ad522d6ba2
Merge pull request #93 from ratelle/master Add replace_undefined and escape_forward_slashes
commit sha a1418434b275183aae3bb4e853c44c8e91b7b0a6
Fix typo in README.md Thanks to @dvliman and @kxepal for noticing.
commit sha 5d6b2651c9ebdccf04ab99083cbf24919ebf25b9
Update double-conversion to latest master
commit sha 3458b79cac9fa612cd004bbcc4e46ca67463c08b
Document new encoding and decoding options
commit sha 43d9516bfcb54919cfd3eb89360448bdcc1c583f
Squash to new double-conversion
commit sha e371ec1075266240ec88a744cda036e8fddefd1c
Add Dialyzer types and specs Thanks to @joedevivo for the contribution. Fixes #85
commit sha 2c394028691ad6cd60cf5bd7faa14c645ff27381
Merge pull request #65 from lpgauth/no_native Add compile option no_native
commit sha 238c653ded399076a7f65ee3414996cd6ca66986
Ignore test XML files
commit sha 6d2278e90694bb484845ad149d484d0a3cae10ec
Add new return_trailer option Previously Jiffy would throw an error about trailing data if there is any non-whitespace character encounter after the first term had been decoded. This patch adds a decoder option `return_trailer` that will instead return a sub-binary starting at the first non-whitespace character. This allows users to be able to decode multiple terms from a single iodata() term. Thanks to @vlm for the original patch.
commit sha 454928ff3435721a5e4bbda5e80df9f3931cb6ff
Revamp yields back to Erlang In the original PR for `return_trailer` @vlm pointed out that I wasn't using enif_consume_timeslice correctly. This fixes that by changing out its called. Previously we attempted to define the total number of bytes to decode or encode in a single NIF call and then would consume as much of the timeslice as we processed. This is wrong because we may start the NIF call with less than an entire timeslice left. The new approach is to define the number of bytes to encode or decode per reduction and then iteratively call enif_consume_timeslice until it indicates that we should return.
commit sha a32a12f8b5262a975084ccf918390c650b0b4aff
Fix dialyzer type specs
commit sha f284a1b2b0799441665209a86ce14c1f0921d6ca
Strings can be atoms or binaries
commit sha e132b633f586281cfce7d4f1e71a41c96555e963
Add map typespec for dialyzer This obviously only exists on VMs that support it.
push time in a month
push eventdiscord/jiffy
commit sha 7b7a9f91c47da9ef423055376e3c81b1fdcd746f
add support for incoding int64 as string
commit sha 66c3b6c6dda92813271446e7d389f5258792bdc8
check bounds
commit sha 7a3ab2903d9a5f6d8fc4b525ae408aacd28e0ba8
add stripping of elixir struct
commit sha 02e282ce413e2b578a4d5447fd77746af65fb8d4
Changed pos to unsigned int to prevent warning from happening. Snagged from upstream at https://github.com/davisp/jiffy/pull/92
commit sha a08c584f84303d4d72a61e4bac5e58fb5cd645b8
Merge local changes with upstream 1.0.8 Some bits in encoder.c in particular were manually merged
commit sha 4c2009a54e840eeac823eecf902e52bf38bd0ec4
Merge pull request #6 from discord/merge-1.0.8 Merge 1.0.8 with old local commits
push time in a month
PR merged discord/jiffy
This is https://github.com/discord/jiffy/pull/5 just in the other direction. I had a few manual merge bits (enc_long is the most interesting of those).
pr closed time in a month
pull request commentdiscord/jiffy
https://github.com/discord/jiffy/pull/6 for the other direction. Regardless it's the same commit being pushed to master.
comment created time in a month
PR opened discord/jiffy
This is https://github.com/discord/jiffy/pull/5 just in the other direction. I had a few manual merge bits (enc_long is the most interesting of those).
pr created time in a month
pull request commentdiscord/jiffy
I usually like merging for this type of catch-up, but I think in this case it may make it hard to find our changes in the noise later.
If it's not too much work (i.e. if you didn't have many code conflicts when creating this) we can:
- create a new
discord-1.0.8branch that's starting at upstream's1.0.8tag - rebase all of our commits on top of that
- make a PR to review merging those changes into
discord-1.0.8
comment created time in a month
pull request commentdiscord/jiffy
This is hard to read in this direction. https://gist.github.com/ypisetsky/149fdc93afcf971894a4691bb796abcd shows the patch as compared to upstream's 1.0.8 tag.
comment created time in a month