3bot / 3bot Goto Github PK

We should activate the „Error Stream“-Tab by default if a task has failed and the STDERR is not empty, so the user sees the reason right away.

both list and detail view(s)

before replaying a workflow log we should try to render the scripts, as we do in the template.

Traceback (most recent call last):
  File "***background_task/tasks.py", line 160, in run_task
    tasks.run_task(task.task_name, args, kwargs)
  File "***background_task/tasks.py", line 45, in run_task
    task.task_function(*args, **kwargs)
  File "***threebot/tasks.py", line 56, in run_workflow
    template = render_template(workflow_log, workflow_task)
  File "***threebot/utils.py", line 234, in render_template
    inputs = workflow_log.inputs[str(workflow_task.id)]
KeyError: '333'

Can't remember - is theToken required for the default 3bot installation or is it only required if https://github.com/3bot/3bot-hook is used?

Generate a link, for example https://my.3bot.io/w/S0rtUr1, for each workflow. This link should never change, even if the title of the workflow was modified.
This would be great when sending the link of the workflow by email or adding it to documentation.

https://my.sentry.arteria.ch/arteria/my3botio/issues/1750/

IOError: write error

IOError: write error

@kennethreitz has an API Implementation (https://github.com/kennethreitz/gistapi.py/tree/develop/gistapi) for this.

Afterwards, post a comment here https://gist.github.com/defunkt/370230

• Change django-background-task to django-background-tasks
• Django

WorkflowPresets should be unique for workflow and user to prevent MultipleObjectsReturned Exceptions

https://github.com/Kickball/awesome-selfhosted/blob/master/README.md#continuous-integration

• ERRORS: threebot.Worker.ip: (fields.E900) IPAddressField has been removed except for support in historical migrations. HINT: Use GenericIPAddressField instead.

you must apt-get install python-dev on Debian/Ubuntu.

By now we just save the starting time for a workflow log.
It would be an improvement if be log both, the start- and endtime. So we can display the average time the workflow takes.

using a random string

This would be helpful if a Worker should be reachable by multiple 3bots.

show the rendered script per task and in a tab, not modal.

Copy-Paste error

https://github.com/3bot/3bot/blob/master/threebot/templates/threebot/preferences/organization/activity.html#L9

To give users/developers a better starting point we could add an Example Project (as seen here: https://github.com/justquick/django-human-datetime#example-project).

No workflows should be started on not available workers