Skip to content

Bugfix: new pads not in listAllPads data if padList cache already created.#1971

Closed
ldidry wants to merge 1 commit intoether:developfrom
ldidry:fix-new-pads-not-in-padList-cache
Closed

Bugfix: new pads not in listAllPads data if padList cache already created.#1971
ldidry wants to merge 1 commit intoether:developfrom
ldidry:fix-new-pads-not-in-padList-cache

Conversation

@ldidry
Copy link
Copy Markdown
Contributor

@ldidry ldidry commented Oct 28, 2013

Since commit 200f250, the new pads
aren't listed in listAllPads data.
They appears only if we don't have called listAllPads before creating
the new pad (because we read the db at first listAllPads call).

…ated

Since commit 200f250, the new pads
aren't listed in listAllPads data.
They appears only if we don't have called listAllPads before creating
the new pad (because we read the db at first listAllPads call).
marcelklehr added a commit that referenced this pull request Nov 1, 2013
@aaronpk
Copy link
Copy Markdown

aaronpk commented Jan 2, 2014

Any idea when this will make it into a release version?

@ldidry ldidry deleted the fix-new-pads-not-in-padList-cache branch January 2, 2014 19:58
@JohnMcLear
Copy link
Copy Markdown
Member

Peep the release procedure, if you can do any of those bits its whenever you do them, it only needs an admin to merge two pull requests and publish a blog post.

Aaron Parecki notifications@github.com wrote:

@aaronpk
Copy link
Copy Markdown

aaronpk commented Jan 2, 2014

Oh, didn't realize that! Will check it out, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants