profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/djw/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.
Dan Wilson djw Bright Network Edinburgh, Scotland https://danjwilson.co.uk VPEng at @brightnetwork. Previously: @unmadeworks, @sugru, @makielab, @timetric.

djw/core-plot 221

Unofficial core-plot mirror (official version now here: https://github.com/core-plot/core-plot)

djw/as3xls 60

Fork of as3xls with bugfixes (unmaintained)

djw/raphlot 54

Flot ported to use Raphaël APIs rather than Canvas (and therefore outputs SVG/VML)

mdales/asi-http-request 15

Easy to use CFNetwork wrapper for HTTP requests, Objective-C, Mac OS X and iPhone

mdales/ASIOAuthTest 7

A test harness for working with OAuth and ASI network frameworks

mdales/codatimetric 2

A demo of mixing CODA and Timetric data

djw/arsenalhomegames 1

Source code to http://arsenalhomegames.appspot.com/

djw/ecs 1

Experimenting with Go and ECS

teh/monmoth 1

monmoth coffee ratings

djw/AbFab3D 0

3D Printing Toolkit

delete branch brightnetwork/pr-broker

delete branch : dependabot/npm_and_yarn/types/lodash-4.14.170

delete time in 2 months

push eventbrightnetwork/pr-broker

dependabot[bot]

commit sha 72381a241e5bb1ab24824f9e88f0eb83f5933f56

chore(deps): bump @types/lodash from 4.14.169 to 4.14.170 Bumps [@types/lodash](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/lodash) from 4.14.169 to 4.14.170. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/lodash) --- updated-dependencies: - dependency-name: "@types/lodash" dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>

view details

Dan Wilson

commit sha 40c2b736f2232072bada7e42ead21fbb57566664

Merge pull request #17 from brightnetwork/dependabot/npm_and_yarn/types/lodash-4.14.170 chore(deps): bump @types/lodash from 4.14.169 to 4.14.170

view details

push time in 2 months

PR merged brightnetwork/pr-broker

chore(deps): bump @types/lodash from 4.14.169 to 4.14.170 dependencies

Bumps @types/lodash from 4.14.169 to 4.14.170. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/lodash">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

+4 -4

0 comment

2 changed files

dependabot[bot]

pr closed time in 2 months

PullRequestReviewEvent

issue commentspookylukey/django-paypal

PDT payments intermittently broken?

I've been running this branch for the last week or so without any issues, but it's a bit hacky to push upstream:

https://github.com/spookylukey/django-paypal/compare/master...djw:return-query-changes

Given that payment_date is now arriving in ISO format in the query parameters, but still in PayPalDateTimeField format in the postback response, I think the options are:

  1. Extend PayPalDateTimeField to support ISO format (perhaps requiring a dependency on python-dateutil)
  2. Use separate form classes to handle query parameters and the postback response, and probably ignore all the new parameters, including the ISO format date.

I lean towards the second option, but would like your opinion before working on a patch. :)

djw

comment created time in 2 months

push eventdjw/django-paypal

Luke Plant

commit sha 1baacb693d713d6ebcece777d2cc8f9f28c75b0e

Link to my status page

view details

Luke Plant

commit sha 24d914ba7f72c7bcab47445506f54558023c0a0b

Typo

view details

push time in 2 months

push eventdjw/django-paypal

Dan Wilson

commit sha abe58206e1833a6c736e0e80ecfdc13bbacd8346

Support query parameters present on some return url requests Delete `notify_version` since django-paypal requires it to be a decimal. Delete `payment_date` from query params because here it's an iso-formatted datetime. It'll be set from the postback as usual.

view details

push time in 2 months

startedawsdocs/amazon-ecs-developer-guide

started time in 2 months

create barnchdjw/django-paypal

branch : return-query-changes

created branch time in 2 months

issue openedspookylukey/django-paypal

PDT payments broken in v1.1

Presumably as a consequence of changing the PayPal endpoint in v1.1, the query parameters passed to the return_url have changed, in a way that's incompatible with the current implementation of PayPalPDTForm.

Specifically, I'm now receiving:

  1. notify_version=UNVERSIONED which is incompatible with the decimal type of the underlying model field
  2. payment_date=2021-05-11T12:00:00Z which is incompatible with PayPalDateTimeField

Tweaking the form like this works fine locally with Django 3.1 — when I get a moment I'll create a proper patch with a test case.

class PayPalPDTForm(PayPalStandardBaseForm):
    payment_date = DateTimeField(required=False)

    class Meta:
        model = PayPalPDT
        exclude = [
            "ipaddress",
            "flag",
            "flag_code",
            "flag_info",
            "query",
            "response",
            "created_at",
            "updated",
            "form_view",
            "notify_version",
        ]

created time in 2 months

startedasottile/pyupgrade

started time in 2 months