profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/mhfs/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.
Marcelo Silveira mhfs Trusted Health Brazil mhfs.net Full Stack Software Engineer. Ruby, Rails, Go, JavaScript, React.

mhfs/devise-async 575

Send Devise's emails in background. Supports Resque, Sidekiq, Delayed::Job and QueueClassic.

mhfs/dotfiles 4

My dotfiles

mhfs/codereport 2

Command line utility to generate a beautiful PDF/HTML of your source code

mhfs/firebot 2

Extensible Campfire bot to integrate with other applications/services

mhfs/ix 2

Issues Explorer - CLI tool to explore GitHub issues

mhfs/applicator 1

Embarrassing set of Thor tasks to make a bare ubuntu VPS capable of hosting a jekyll site and/or a rake app.

mhfs/bigtuna 1

Continuous Integration software written on top of Ruby on Rails 3 and DelayedJob.

mhfs/brcobranca 1

Gem para emissão de bloquetos de cobrança para bancos brasileiros

mhfs/cpfcnpj 1

Sinatra App to generate CPF/CNPJ for test purposes

mhfs/devise 1

Flexible authentication solution for Rails with Warden.

push eventtrusted/heroku-buildpack-private-npm-registries

Marcelo Silveira

commit sha 73d0a290bd4ae1a810d336c9dc2b4234d90a7b26

fix env var escaping

view details

push time in 7 hours

push eventtrusted/heroku-buildpack-private-npm-registries

Marcelo Silveira

commit sha c19e0bcb76adb6859dafee97576014532811d159

and done?

view details

push time in a day

push eventtrusted/heroku-buildpack-private-npm-registries

Marcelo Silveira

commit sha 67f0b7e84e521cb3ccb4bf79ed3b365131818bbd

more

view details

push time in a day

push eventtrusted/heroku-buildpack-private-npm-registries

Marcelo Silveira

commit sha e9a02021c02079ea4a4b4ff27519379f604ddc0d

debugging env dir

view details

push time in a day

push eventtrusted/heroku-buildpack-trusted-registry

Marcelo Silveira

commit sha b439fbd34c6990742584fd46925c626825ff36f4

readme

view details

push time in a day

push eventtrusted/heroku-buildpack-trusted-registry

Marcelo Silveira

commit sha 35b55c539dbeccc29310979fc98d4869c86c6425

polish the script

view details

push time in a day

push eventtrusted/heroku-buildpack-trusted-registry

Marcelo Silveira

commit sha 2929edac3ae5e28282b83e141e041b7d9f351c09

again

view details

push time in a day

push eventtrusted/heroku-buildpack-trusted-registry

Marcelo Silveira

commit sha fb55cafef5f4b11ca30f52a6e740f498a3608537

oopsie

view details

push time in a day

push eventtrusted/heroku-buildpack-trusted-registry

Marcelo Silveira

commit sha b622cfc12eae02318fb0a961273b028a5c43afb4

avoid using yarn

view details

push time in a day

push eventtrusted/heroku-buildpack-trusted-registry

Marcelo Silveira

commit sha 48f6e8da5978416ba6bbc36f84d3d77033b8c176

name the buildpack

view details

push time in 2 days

push eventtrusted/heroku-buildpack-trusted-registry

Marcelo Silveira

commit sha 64208548068d790de81ca7770e5f5ba9b90ecd29

initial version

view details

push time in 2 days

created repositorytrusted/heroku-buildpack-trusted-registry

created time in 2 days

create barnchtrusted/heroku-buildpack-trusted-registry

branch : main

created branch time in 2 days

pull request commentadamniedzielski/tiddle

Add ability to track additional info in tokens

awesome, @adamniedzielski. thanks for your comments and consideration, we really appreciate it.

I made the keywords args change you suggested.

From my perspective, this is good to go. Anything else I can help with before the merge?

mhfs

comment created time in 9 days

Pull request review commentadamniedzielski/tiddle

Add ability to track additional info in tokens

 def authentication_token_class(resource)       end     end -    def token_attributes(token_body, request, expires_in)+    def token_attributes(token_body, request, expires_in, metadata: {})

:+1: done!

mhfs

comment created time in 9 days

PullRequestReviewEvent

push eventmhfs/tiddle

Adam Niedzielski

commit sha 4b195053e031e132a9c4a6a9b0a58540b230dc2a

Drop support for Ruby 2.5 (#77) * Drop support for Ruby 2.5 * Fix small Rubocop offence * Check if comment is still relevant Co-authored-by: Adam <adam@Liefery-MacBook-Pro.local>

view details

Marcelo Silveira

commit sha 7f526844cdfd39f6cd72b2844b9582e1c13235d8

make token_attributes params keyword args

view details

Marcelo Silveira

commit sha 629ddc8c6465a441ad4a05fae3300b29dd5ada9b

Merge remote-tracking branch 'upstream/main' into mhfs/metadata * upstream/main: Drop support for Ruby 2.5 (#77)

view details

push time in 9 days

pull request commentadamniedzielski/tiddle

Add ability to track additional info in tokens

hey @adamniedzielski, wonder if you had the chance of looking into my previous comment here. :)

mhfs

comment created time in 14 days

pull request commentadamniedzielski/tiddle

Add ability to track additional info in tokens

hey @adamniedzielski, thanks for the reply and I totally understand the desire to keep the library small.

However, I explored your suggestion, and Tiddle.create_and_return_token returns a string and not the ActiveRecord object.

Also, by splitting the process into two steps, I'd lose the ability to do model validations on my custom attributes as they'd fail on the create! call Tiddle makes internally.

Any other ideas? :D

mhfs

comment created time in a month

pull request commentgoldstar/newrelic-elasticsearch

Make gem compatible with elasticsearch v7

@stephenprater for insisting, but I was hoping you could provide some guidance on what we could do to help get this released. Thank you.

rzaharenkov

comment created time in 2 months

pull request commentadamniedzielski/tiddle

Add ability to track additional info in tokens

@adamniedzielski anything else I can do to help this move along?

mhfs

comment created time in 2 months

issue openedsunny/graph_attack

graph_attack 1.2.0 rubygem release?

Hey there, thanks for your work on this library, great stuff.

Any plans on releasing 1.2.0 version to rubygems?

Thank you

created time in 2 months

startedslatedocs/slate

started time in 2 months

pull request commentadamniedzielski/tiddle

Add ability to track additional info in tokens

@adamniedzielski it seems appraisal has an unresolved issue with ruby 3. I believe that's why some checks failed.

https://github.com/thoughtbot/appraisal/issues/186

mhfs

comment created time in 2 months

PR opened adamniedzielski/tiddle

Add ability to track additional info in tokens

Hey Adam!

First of all, thanks for all your work on Tiddle.

In our product, we have the need of tracking some additional context information when issuing authentication tokens.

This PR adds the ability to pass a metadata hash to create_and_return_token so that arbitrary data can be stored in the token.

I don't expect it to cause any backward compatibility issues.

Looking forward to your thoughts!

+11 -4

0 comment

4 changed files

pr created time in 2 months

create barnchmhfs/tiddle

branch : mhfs/metadata

created branch time in 2 months

issue closedmirego/activerecord_json_validator

Issue with error messages after 2.0.0 release

Prior to 2.0.0 a schema failure in a model would result in something like this:

model_instance.errors.full_messages
"Data The property '#/something/Status' value \"Wrong\" did not match the regex '^(Closed|Open)$' in schema file:///Users/.....json"

Now it returns this:

["Data {\"data\"=>\"Wrong\", \"data_pointer\"=>\"/something/Status\", \"schema\"=>{\"type\"=>\"string\", \"pattern\"=>\"^(Closed|On Hold)$\"}...

Was that expected? Regression?

closed time in 3 months

mhfs

issue commentmirego/activerecord_json_validator

Issue with error messages after 2.0.0 release

Thanks @remi.

mhfs

comment created time in 3 months

issue openedmirego/activerecord_json_validator

Issue with error messages after 2.0.0 release

Prior to 2.0.0 a schema failure in a model would result in something like this:

model_instance.errors.full_messages
"Data The property '#/something/Status' value \"Wrong\" did not match the regex '^(Closed|Open)$' in schema file:///Users/.....json"

Now it returns this:

["Data {\"data\"=>\"Wrong\", \"data_pointer\"=>\"/something/Status\", \"schema\"=>{\"type\"=>\"string\", \"pattern\"=>\"^(Closed|On Hold)$\"}...

Was that expected? Regression?

created time in 3 months