ink-api issueshttps://gitlab.coko.foundation/INK/ink-api/-/issues2018-03-08T22:31:09Zhttps://gitlab.coko.foundation/INK/ink-api/-/issues/66Missing `RAILS_ENV` in shell causes Docker to fail2018-03-08T22:31:09ZAlex ThegMissing `RAILS_ENV` in shell causes Docker to failIn following the docker installation steps for INK, `docker volume create --name=gems` succeeds but `docker-compose up` fails. I get the following error, which stops the process:
```bash
ink_1 | wait-for-it: seed_db:1234 is availa...In following the docker installation steps for INK, `docker volume create --name=gems` succeeds but `docker-compose up` fails. I get the following error, which stops the process:
```bash
ink_1 | wait-for-it: seed_db:1234 is available after 8 seconds
ink_1 | + ./bin/bundle exec puma -b tcp://0.0.0.0:3000
ink_1 | Folding contents of StepGemfile into Gemfile
ink_1 | bundler: failed to load command: puma (/gems/bin/puma)
ink_1 | Bundler::GitError: https://gitlab.coko.foundation/INK/ink-step.git (at master@016222c) is not yet checked out. Run `bundle install` first.
```
The issue was that `RAILS_ENV` was not set in my shell's environment (`RAILS_ENV` wasn't there at all) on a Mac. Setting it with `export RAILS_ENV='development'` fixed the issue and the following worked:
* `docker system prune`
* `docker volume rm gems`
* `docker-compose down -v`
* `docker volume create --name=gems`
* `docker-compose up`
`RAILS_ENV='development'` is specified in the `.env.sample`, and the missing `RAILS_ENV` in my shell environment was overriding this. This value should come from `.env.sample`:
https://gitlab.coko.foundation/INK/ink-api/blob/master/.env.sample#L28
Full log:
[master_ink_docker.log](/uploads/596c252e8b791eea204123e6d62523b9/master_ink_docker.log)https://gitlab.coko.foundation/INK/ink-api/-/issues/65Nondeterministic error in ci2018-01-31T10:48:03ZSam GalsonNondeterministic error in cihttps://gitlab.coko.foundation/INK/ink-api/-/jobs/7820
UPDATE! It turns out the error occurs consistently when using the shared runner. And it has never occurred using the private runner.https://gitlab.coko.foundation/INK/ink-api/-/jobs/7820
UPDATE! It turns out the error occurs consistently when using the shared runner. And it has never occurred using the private runner.https://gitlab.coko.foundation/INK/ink-api/-/issues/64Document how ink is supposed to be set up to run with multiple workers2018-01-30T23:58:54ZSam GalsonDocument how ink is supposed to be set up to run with multiple workers@blahah do you know?@blahah do you know?https://gitlab.coko.foundation/INK/ink-api/-/issues/63Decouple ink and sideqik2018-01-30T23:04:45ZSam GalsonDecouple ink and sideqikCurrently ink and sideqik need to share a volume. While I'm not sure what the thinking was behind how ink would scale up for multiple workers it seems like a shared volume might inhibit this. The classic pattern would be to use something...Currently ink and sideqik need to share a volume. While I'm not sure what the thinking was behind how ink would scale up for multiple workers it seems like a shared volume might inhibit this. The classic pattern would be to use something like s3 for file storage and share references to files stored on s3.
Until this is fixed ink and sideqik will need to be run in the same pod or use AWS EFS. This is not natively supported by kubernetes but an [addon is here](https://github.com/kubernetes-incubator/external-storage/tree/master/aws/efs).https://gitlab.coko.foundation/INK/ink-api/-/issues/62Clarify seeding strategy2018-01-22T16:50:03ZSam GalsonClarify seeding strategySeeds are defined in two places...`lib/tasks/setup.rake` and `db/seed.rb`. Maybe we should standardise on a single source? Which one?Seeds are defined in two places...`lib/tasks/setup.rake` and `db/seed.rb`. Maybe we should standardise on a single source? Which one?https://gitlab.coko.foundation/INK/ink-api/-/issues/61Set up continuous deployment2018-01-22T11:23:41ZTamlyn RhodesSet up continuous deploymentSam GalsonSam Galsonhttps://gitlab.coko.foundation/INK/ink-api/-/issues/58Step instead of chain execution granularity2017-12-14T09:09:09ZcharlieStep instead of chain execution granularitycharliecharliehttps://gitlab.coko.foundation/INK/ink-api/-/issues/57Add CREDITS file2017-08-28T04:43:00ZAdam Hydeadam@coko.foundationAdd CREDITS filelets start a CREDITS file telling the story, in brief, of who has been involved in INKlets start a CREDITS file telling the story, in brief, of who has been involved in INKhttps://gitlab.coko.foundation/INK/ink-api/-/issues/56Add LICENCE file2017-08-28T04:42:57ZAdam Hydeadam@coko.foundationAdd LICENCE fileAdd MIT default with (c) Adam HydeAdd MIT default with (c) Adam Hydehttps://gitlab.coko.foundation/INK/ink-api/-/issues/55Use docker containers when executing steps with third-party dependencies2017-12-21T11:46:01ZcharlieUse docker containers when executing steps with third-party dependenciescharliecharliehttps://gitlab.coko.foundation/INK/ink-api/-/issues/54Parameter presets for steps2017-11-08T09:25:43ZcharlieParameter presets for stepscharliecharliehttps://gitlab.coko.foundation/INK/ink-api/-/issues/53Steps have human readable name as a method2017-08-17T11:53:16ZcharlieSteps have human readable name as a methodcharliecharliehttps://gitlab.coko.foundation/INK/ink-api/-/issues/52Cumulative manifest2017-08-13T10:18:53ZcharlieCumulative manifestcharliecharliehttps://gitlab.coko.foundation/INK/ink-api/-/issues/51Admin can install gem from UI2017-08-08T02:52:32ZcharlieAdmin can install gem from UIcharliecharliehttps://gitlab.coko.foundation/INK/ink-api/-/issues/50User can see favourite recipes2017-09-06T04:10:05ZcharlieUser can see favourite recipescharliecharliehttps://gitlab.coko.foundation/INK/ink-api/-/issues/49Account can add a recipe to "favourites"2017-09-02T08:15:24ZcharlieAccount can add a recipe to "favourites"charliecharliehttps://gitlab.coko.foundation/INK/ink-api/-/issues/48Pagination2017-11-08T09:25:43ZcharliePaginationcharliecharliehttps://gitlab.coko.foundation/INK/ink-api/-/issues/47Some files consistently fail when converting multiple documents.2017-08-23T11:39:09ZYannis BarlasSome files consistently fail when converting multiple documents.What I do is just send the same 12 files (again and again, as I'm trying some things out) in 12 consecutive api calls to the editoria typescript recipe.
So what's interesting is that I noticed the same three files failed every time (w...What I do is just send the same 12 files (again and again, as I'm trying some things out) in 12 consecutive api calls to the editoria typescript recipe.
So what's interesting is that I noticed the same three files failed every time (with an empty response error).
Even more interesting is that I tried one of the files on its own and it worked just fine. From then on, it doesn't fail in the batch api calls either.
I'm using ink through the pubsweet components btw.https://gitlab.coko.foundation/INK/ink-api/-/issues/45Generic steps2017-08-28T12:02:34ZcharlieGeneric stepscharliecharliehttps://gitlab.coko.foundation/INK/ink-api/-/issues/43INK client auto-update all current process chains2017-08-24T09:42:03ZcharlieINK client auto-update all current process chainscharliecharlie