Skip to content

Commit

Permalink
Automated deployment to update contributors 2020-12-29 (#135)
Browse files Browse the repository at this point in the history
Co-authored-by: github-actions <github-actions@users.noreply.github.com>
  • Loading branch information
github-actions[bot] and github-actions committed Dec 29, 2020
1 parent 1600e6b commit f3a9167
Show file tree
Hide file tree
Showing 4 changed files with 62 additions and 0 deletions.
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
event_type: IssuesEvent
avatar: "https://avatars.githubusercontent.com/u/814322?"
user: vsoch
date: 2020-12-28
repo_name: panoptes-organization/panoptes
html_url: https://github.com/panoptes-organization/panoptes/issues/142
repo_url: https://github.com/panoptes-organization/panoptes
---

<a href='https://github.com/vsoch' target='_blank'>vsoch</a> open issue <a href='https://github.com/panoptes-organization/panoptes/issues/142' target='_blank'>panoptes-organization/panoptes#142</a>.

<p>Discussion: handled async tasks</p><small>Given that a snakemake workflow is launched from panoptes, how would it be best to handle waiting for it? E.g., you could add some kind of queue with redis or celery, but on the other hand, we don't want to make the tool too bulky to use. Are you planning to add another service to Docker compose for this, or some strategy to just make the user wait in the interface while it's running the job?...</small><a href='https://github.com/panoptes-organization/panoptes/issues/142' target='_blank'>View Comment</a>
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
event_type: IssueCommentEvent
avatar: "https://avatars.githubusercontent.com/u/814322?"
user: vsoch
date: 2020-12-28
repo_name: snakemake/snakemake
html_url: https://github.com/snakemake/snakemake/issues/799
repo_url: https://github.com/snakemake/snakemake
---

<a href='https://github.com/vsoch' target='_blank'>vsoch</a> commented on issue <a href='https://github.com/snakemake/snakemake/issues/799' target='_blank'>snakemake/snakemake#799</a>.

<small>I was thinking the minimal like the command (so the user can recognize it easily), the snakefile, and working directory....</small>

<a href='https://github.com/snakemake/snakemake/issues/799' target='_blank'>View Comment</a>
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
event_type: PushEvent
avatar: "https://avatars.githubusercontent.com/u/814322?"
user: vsoch
date: 2020-12-28
repo_name: vsoch/opensource-heartbeat
html_url: https://github.com/vsoch/opensource-heartbeat/commit/1600e6b07dbee66e327ae6ce62e331dfe46b8ae1
repo_url: https://github.com/vsoch/opensource-heartbeat
---

<a href='https://github.com/vsoch' target='_blank'>vsoch</a> pushed to <a href='https://github.com/vsoch/opensource-heartbeat' target='_blank'>vsoch/opensource-heartbeat</a>

<small>Automated deployment to update contributors 2020-12-28 (#134)

Co-authored-by: github-actions <github-actions@users.noreply.github.com></small>

<a href='https://github.com/vsoch/opensource-heartbeat/commit/1600e6b07dbee66e327ae6ce62e331dfe46b8ae1' target='_blank'>View Commit</a>
17 changes: 17 additions & 0 deletions docs/_events/2020-12-28-vsoch-snakemake-PushEvent-14659541312.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
event_type: PushEvent
avatar: "https://avatars.githubusercontent.com/u/814322?"
user: vsoch
date: 2020-12-28
repo_name: vsoch/snakemake
html_url: https://github.com/vsoch/snakemake/commit/fda56e096bb8921257bd601e9af4e4c093b305fc
repo_url: https://github.com/vsoch/snakemake
---

<a href='https://github.com/vsoch' target='_blank'>vsoch</a> pushed to <a href='https://github.com/vsoch/snakemake' target='_blank'>vsoch/snakemake</a>

<small>ensuring we send additional data to server on workflow creation

Signed-off-by: vsoch <vsochat@stanford.edu></small>

<a href='https://github.com/vsoch/snakemake/commit/fda56e096bb8921257bd601e9af4e4c093b305fc' target='_blank'>View Commit</a>

0 comments on commit f3a9167

Please sign in to comment.