profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/AndrewDryga/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Andrew Dryga AndrewDryga Hammer Corp, Nebo #15 Kiev, Ukraine http://dryga.com CTO/Full-Stack Developer in Fintech and Blockchain domains. Elixir, DevOps, PHP, JavaScript and much more.

AndrewDryga/jQuery.DebouncedResize 5

Debounced Resize Event for jQuery with Bower support

AndrewDryga/grunt-bower-installer 2

Grunt plugin for Bower

AndrewDryga/antidote 1

A work-in-progress blazing fast Elixir json library

AndrewDryga/elixir-companies 1

A list of companies currently using Elixir in production.

AndrewDryga/font-rexbold 1

Rex Bold font repo for using with Bower. Font taken from fonts2u.com.

AndrewDryga/absinthe_plug 0

Plug support for Absinthe, the GraphQL toolkit for Elixir

AndrewDryga/api-spec 0

API Specififications

AndrewDryga/authable 0

OAuth2 Provider implementation modules and helpers using plug, ecto and postgress for any elixir application.

AndrewDryga/awesome-elixir 0

A curated list of amazingly awesome Elixir and Erlang libraries, resources and shiny things. Updates:

push eventNebo15/logger_json

Greg Mefford

commit sha 848ee0b253e3c3af8ac605bb2b059398fdc4c3fb

Fix docs for setting log level on LoggerJSON.Plug (#80)

view details

push time in 7 hours

PullRequestReviewEvent

push eventNebo15/sage

Ludovic Dem

commit sha 05775a3ba3c4b9c6c5fd937cb79b80c5d73001b3

Allow docs to lead to github source (#65) Using the bare `@version` number since that is what is used as tag names on the github repo.

view details

push time in 7 hours

PR merged Nebo15/sage

Allow docs to lead to github source

Using the bare @version number since that is what is used as tag names on the github repo.

+1 -1

0 comment

1 changed file

lud

pr closed time in 7 hours

PullRequestReviewEvent

issue commentduffelhq/paginator

Pagination does not work with joins

@bencoppock it does work with both of your use cases but I think the second one is out of scope for any pagination library.

it didn't support paginating from the end of the result set backward If I remember correctly you can add order_by: ... to your paginated query and also define cursors with direction, so pagination from the end of the list is the same for paginator as paginating from its beginning. Basically, it doesn't care about the order.

it didn't support jumping to an arbitrary point and paginating forward/backward from there And it should not do it for you, but you still can do it yourself. From your example, you can SELECT cursor_field FROM users WHERE last_name ILIKE 'J%' ORDER BY last_name LIMIT 1 and then by having cursor field on hand you can separately query a page before and after that cursor using pagination library. (Or you can UNION two queries that do that which is fancier, but writing such query in Ecto and maintaining it might not be worth the tiny speed optimization you will get out of it.)

AndrewDryga

comment created time in 18 days

issue commentNebo15/sage

Docs cannot lead to source

@lud this is just copy-pasted issue from somewhere, please go ahead and submit a PR ❤️.

lud

comment created time in 22 days

pull request commentNebo15/sage

Fix typo

Thank you ❤️

GregMefford

comment created time in 22 days

push eventNebo15/sage

Greg Mefford

commit sha 89bb9df1eeb0141e299dc985b8606c0699c86793

Fix typo (#63) I was reading through this and happened to notice this typo.

view details

push time in 22 days

PR merged Nebo15/sage

Fix typo

I was reading through the code and happened to notice this typo.

+2 -2

0 comment

1 changed file

GregMefford

pr closed time in 22 days

push eventNebo15/logger_json

Vlad Romaniuk

commit sha 3332c7cdd7a5dc57f85771809c03ff1469a2901a

bump version to 4.3.0 (#79)

view details

push time in 22 days

PR merged Nebo15/logger_json

bump version to 4.3.0

@AndrewDryga Hello, it would be nice to have a new version after including support for telemetry 1.0+ PR #78

+2 -2

1 comment

2 changed files

drEnilight

pr closed time in 22 days

push eventNebo15/ecto_trail

Vlad Romaniuk

commit sha 5f54d356b68d7d2c6599b461da690bace81d5ccf

feat: update ecto_sql and postgrex (#22)

view details

push time in 22 days

PR merged Nebo15/ecto_trail

feat: bump ecto_sql from 3.4.5 to 3.7.0 and postgrex from 0.15.5 to 0.15.10

@AndrewDryga Hello, please take a look at this PR.

+11 -11

0 comment

2 changed files

drEnilight

pr closed time in 22 days

PullRequestReviewEvent

pull request commentelixir-ecto/ecto

Add support for partial indexes

@kidbombay take a look at Ecto.Changeset.check_constraint/2.

matthewrudy

comment created time in 2 months

pull request commentNebo15/logger_json

Support telemetry v1.0

Thank you

wingyplus

comment created time in 2 months

push eventNebo15/logger_json

Thanabodee Charoenpiriyakij

commit sha b8b98642be080cf1ff06271ce96f2ea5937f7513

Support telemetry v1.0 (#78)

view details

push time in 2 months

PR merged Nebo15/logger_json

Support telemetry v1.0
+1 -1

1 comment

1 changed file

wingyplus

pr closed time in 2 months

pull request commentNebo15/logger_json

CI: add Elixir 1.12.1 and Erlang/OTP 24.0

Thank you ❤️

sgerrand

comment created time in 2 months

push eventNebo15/logger_json

Sasha Gerrand

commit sha e144b8d4c18841f83ec91ebbc505f5c8c3bc8cfd

CI: add Elixir 1.12.1 and Erlang/OTP 24.0 (#77) * Test against Elixir 1.12.1 and Erlang/OTP 24.0 * Add Elixir 1.12.1 & OTP 24.0 to build matrix

view details

push time in 2 months

PR merged Nebo15/logger_json

CI: add Elixir 1.12.1 and Erlang/OTP 24.0

💁 These changes add new versions to the Travis CI build configuration:

  • Elixir: 1.12.1; and
  • Erlang/OTP: 24.0
+7 -3

1 comment

1 changed file

sgerrand

pr closed time in 2 months

issue closedNebo15/logger_json

Dialyzer warnings: Ecto.LogEntry and DatadogLogger pattern match

I fixed some Dialyzer warnings in #75, but there are two left:

:0:unknown_type
Unknown type: Ecto.LogEntry.t/0.

Ecto.LogEntry has been removed in Ecto 3.2.0. If you want to keep this for backwards compatibility, we can tell Dialyzer to ignore this warning.

________________________________________________________________________________
lib/logger_json/formatters/datadog_logger.ex:43:pattern_match
The pattern can never match the type.

Pattern:
%{:reason => _reason}

Type:
nil | %Jason.Fragment{:encode => ({_, _} -> [any(), ...])}

I'm not using the datalog logger, but it looks like Jason.Helpers.json_map/1 (used in LoggerJSON.FormatterUtils.format_process_crash/1) returns a Jason.Fragment struct, on which you'd have to call the encode function in order to get the final map. The datadog logger matches on the encoded map though, and not on Jason.Fragment. So this looks like a bug to me.

closed time in 3 months

woylie

issue commentNebo15/logger_json

Dialyzer warnings: Ecto.LogEntry and DatadogLogger pattern match

Thank you @woylie, I fixed the bug you found via Dialyzer and removed Ecto.LogEntry struct name but kept the code for backward compatibility. ❤️

woylie

comment created time in 3 months

created tagNebo15/logger_json

tag4.2.0

JSON console backend for Elixir Logger.

created time in 3 months

push eventNebo15/logger_json

Andrew Dryga

commit sha 67d334f71f470fe6fb0f684cbe145e15545bccb1

Fix Erlang version on CI

view details

push time in 3 months

push eventNebo15/logger_json

Andrew Dryga

commit sha 9790fd0d9f17b5b8e6b1684a87a57c8545d2acc7

Deprecate Elixir version which is not supported by Ecto any more

view details

push time in 3 months

push eventNebo15/logger_json

Andrew Dryga

commit sha 4f7bdde7a7ac78332c6df8f79ff10f02b9bdf2a2

Trigger CI

view details

push time in 3 months

push eventNebo15/logger_json

Andrew Dryga

commit sha 5dba7f9ae2db3ee4a38b8d90f4f3bbe673ae733a

Update all deps

view details

Andrew Dryga

commit sha cb81f6ca2133bfb4eff1d984dc2a26b6b007d2f8

Fix a bug in datadog process match formatting

view details

Andrew Dryga

commit sha 310d6eb7ce15a5466ff054569c59c6c9872614d8

Remove Ecto.LogEntry mentions since it's removed in Ecto 3.2. Telemetry handler can be used instead as described in README.md

view details

push time in 3 months