ncbi issueshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues2021-11-15T15:56:01Zhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/630Not receiving kafka notifications cause components to get stuck in "convertin...2021-11-15T15:56:01ZDione Mentisdione@coko.foundationNot receiving kafka notifications cause components to get stuck in "converting" and "loading preview"@lathrops1 @Kireev @deniskar @John.kopanas @yannis @danjela @lathrops1 @andynicholson
There is a known problem of book components getting 'stuck' in the Converting or Loading preview status. This problem occurs because BCMS does not re...@lathrops1 @Kireev @deniskar @John.kopanas @yannis @danjela @lathrops1 @andynicholson
There is a known problem of book components getting 'stuck' in the Converting or Loading preview status. This problem occurs because BCMS does not receive the kafka notification (for an error or successful preview).
The BCMS doesn't receive the kafka notifications because the connection to the kafka server is lost. This might be because we're connected to one kafka server at `https://test.ncbi.nlm.nih.gov/books/kafka` for all three instance: coko testing site; ncbi testing site; dev (locally run apps). Having one kafka server per instance would help us debug other possible reasons for the "stuck" problem but this would requires NCBI to set up the three kafka servers.
We're not sure why the kafka server goes down so frequently in the first place. It could be because we're connecting via a proxy server (due to NCBI's security requirements) and additionally the library NCBI uses is deprecated (see #203).
At the moment all we can do is keep trying to reconnect (every 80 seconds) until a connection is established but any notifications sent while there is no connection are lost. This isn't a sufficient solution.
We need to debug the issue asap as it's slowing down our development and testing on both sides. I suggest that whenever anyone in the team experiences this problem, comment here for @deniskar's attention with the time you noticed it and a link to the book component. NCBI will need to share the logs and help debug. -- Does that work for you @deniskar?
Assuming the lost connect issue is resolved, this alone won't move a book component out of Converting or Loading preview status. We should scope out the use cases for when a book component should be placed in a "failed" state so that the user can "submit" again or "reload preview". One suggestion was to fail after a certain amount of kafka connection attempts however it would be better for this failed action to relate to specific jobs instead of a general BCMS/Kafka problem. So for example we could say, if BCMS does not receive a notification for `chapter 1` in `x amount of time` then put the book component into a failed state.Aug 01.Giannis Kopanasjkopanas@gmail.comEvgenyGiannis Kopanasjkopanas@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/649Kafka can fail to start (and restart)2021-10-12T16:23:02ZDenis KaramyshevKafka can fail to start (and restart)Looks like kafka gives up reconnecting and fails to start.
Attached is the log where kafka did not connect and is not retrying[kafka_failed_to_connect.txt](/uploads/d68a6e1da811370236e7f5e1a89cc14b/kafka_failed_to_connect.txt)Looks like kafka gives up reconnecting and fails to start.
Attached is the log where kafka did not connect and is not retrying[kafka_failed_to_connect.txt](/uploads/d68a6e1da811370236e7f5e1a89cc14b/kafka_failed_to_connect.txt)Aug 01.Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/648Updates to Org level settings2021-08-31T17:57:17ZDione Mentisdione@coko.foundationUpdates to Org level settings@danjela
Here is an updated UI for the Org setting tab:
![org-settings-20210819](/uploads/5cb92526330011ec0df1a22dd9c51c97/org-settings-20210819.png)
Changes here:
1. [x] remove email field (#585)
2. [x] categorise collections in...@danjela
Here is an updated UI for the Org setting tab:
![org-settings-20210819](/uploads/5cb92526330011ec0df1a22dd9c51c97/org-settings-20210819.png)
Changes here:
1. [x] remove email field (#585)
2. [x] categorise collections into two types: Book Series collection and Funded collection
3. [x] Organization type should be toggles to allow more than one typeAug 01.Danjela Shehidanjelashehi@gmail.comDanjela Shehidanjelashehi@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/653Change domain name creation rule2021-08-31T17:55:12ZDione Mentisdione@coko.foundationChange domain name creation rule*(Updated 30 Aug)*
create domain rule:
* For books: match BCMSID e.g. `BCMS1234`
* For collection: match BCMSID + add suffix collect e.g. `BCMS1234collect`
---
[original issue]
@Kireev @deniskar
As raised in #616, we need to cha...*(Updated 30 Aug)*
create domain rule:
* For books: match BCMSID e.g. `BCMS1234`
* For collection: match BCMSID + add suffix collect e.g. `BCMS1234collect`
---
[original issue]
@Kireev @deniskar
As raised in #616, we need to change the domain name creation rule.
The domain name limitations are:
* Must match `[a-z][a-z0-9_]+$` (start with a letter and only contains alphanumeric chars plus underscore))
* is 20 chars or less
Currently we create a domain name with rule: the first 5 characters of the organization abbreviation and an autoincrement number ex. `abbre_10`.
Additionally, if we are creating a collection domain we should add `collect` at the end (see #652)
I think the publisher abbreviation limitations are the same as the domain name -- is that correct?
Before I suggest an alternative, can you confirm if the character limit for either domain name or publisher abbreviation can be changed?Aug. 02Giannis Kopanasjkopanas@gmail.comGiannis Kopanasjkopanas@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/585Remove email requirement when creating publisher2021-08-31T15:31:02ZDenis KaramyshevRemove email requirement when creating publisherBCMS Publisher organization will not have a communications email address. Communication will primarily be directed at individual users. Need to make org email either optional or remove it altogether.BCMS Publisher organization will not have a communications email address. Communication will primarily be directed at individual users. Need to make org email either optional or remove it altogether.Aug 01.Danjela Shehidanjelashehi@gmail.comDanjela Shehidanjelashehi@gmail.com