Dirkjan Bussink
dbussink

195 Followers 55 Starred 6 Following

Organizations

@github @datamapper @rubinius
dbussink created repository dbussink/linux-stable
Aug 15, 2016
Aug 3, 2016
dbussink pushed to master at github/developer.github.com
@dbussink
  • @dbussink 30ec6f7
    Revert "Sync changes from upstream repository"
Jul 25, 2016
dbussink pushed to snh/benchmark-backups at github/backup-utils
@dbussink
dbussink deleted branch dbussink/fix-cluster-restore at github/backup-utils
Jul 25, 2016
Jul 25, 2016
dbussink pushed to master at github/backup-utils
@dbussink
Jul 25, 2016
dbussink opened pull request github/backup-utils#242
@dbussink
Remove restoring cluster.conf on restore
1 commit with 0 additions and 6 deletions
dbussink created branch dbussink/fix-cluster-restore at github/backup-utils
Jul 25, 2016
Jun 14, 2016
dbussink closed pull request github/backup-utils#227
@dbussink
restore host keys for cluster environment as well
Jun 14, 2016
dbussink commented on pull request github/backup-utils#227
@dbussink

We've further discussed this, but it will be necessary to make some bigger changes. For clustering setups, we want the key to be restored that is u…

May 24, 2016
dbussink commented on pull request datamapper/do#100
@dbussink

If 1.9.3 is still working, please keep it enabled.

May 23, 2016
dbussink commented on pull request datamapper/do#99
@dbussink

@tpitale Yeah, you can move 1.9.2 to the allowed failures here to get the branch green?

May 23, 2016
dbussink commented on pull request datamapper/do#99
@dbussink

Looks like MySQL's logic uses it's internal my_ulonglong type and that should be fine. There are 2 more cases of atoi though in the Postgres driver…

May 23, 2016
dbussink commented on pull request datamapper/do#99
@dbussink

This might also apply to the other drivers, so would be good to review those too.

May 23, 2016
dbussink commented on issue datamapper/do#98
@dbussink

rb_cstr_to_inum would be usable for this I think.

May 23, 2016
dbussink commented on issue datamapper/do#98
@dbussink

Looks like a real issue indeed. Best way to handle it is probably to let Ruby do the heavy lifting here and call the Ruby C-API methods to do the s…