Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 13:52
    albogdano closed #245
  • 13:52

    albogdano on master

    fixed default tag no visible in… (compare)

  • 12:52
    albogdano commented #245
  • 12:36
    b-morgenthaler commented #245
  • 12:29
    albogdano commented #245
  • 12:15
    b-morgenthaler commented #245
  • 12:01
    albogdano commented #245
  • 06:13
    b-morgenthaler opened #245
  • 04:37
    Positron010 starred Erudika/scoold
  • Apr 18 09:00
    abstraction starred Erudika/scoold
  • Apr 18 02:01
    rolal starred Erudika/scoold
  • Apr 17 15:57
    Travis Erudika/scoold (1.43.2) passed (395)
  • Apr 17 15:52

    albogdano on 1.43.2

    (compare)

  • Apr 17 15:52

    albogdano on master

    Release v1.43.2. (compare)

  • Apr 16 20:18

    albogdano on master

    added button to sort people alp… (compare)

  • Apr 16 20:09
    albogdano labeled #244
  • Apr 16 20:08
    albogdano closed #244
  • Apr 16 20:08

    albogdano on master

    fixed color of focused buttons … fixed user cannot see other use… (compare)

  • Apr 16 14:16
    b-morgenthaler opened #244
  • Apr 16 08:37
    albogdano labeled #243
Alex Bogdanovski
@albogdano
you can browse the the database and look for the rows with id app:scoold or app:para
Nick Caballero
@nickcaballero
k yeah so the secret in the jsob blob matches the value in the config
i do see that it was able to create some data in the PARA_SCOOLD schema
i was able to create a user, but i can't create questions. and if i logout, i can't log back in
Alex Bogdanovski
@albogdano
well, it really could be anything... k8s is pretty complex and something is probably modifying the requests. lots of other ppl come to me to complain their setup breaks in k8s only to find out it actually works outside of k8s
Helix
@Quant:matrix.org
[m]

:point_up: Edit: Hi, I've just setup scoold on Heroku but I've some issue registering as a user. I just don't receive a confirmation-e-mail upon my User-registration. I did configure mail_host, PW, port, username.
Log message is: [ERROR] 403 - Invalid signature for request GET /v1/_id/[ERROR] 403 - Invalid signature for request GET /v1/_id/name@mail.com coming from app scoold coming from app scoold
[ERROR] 400 - Failed to authenticate user with 'password'. Check if user is active
[ERROR] 403 - Invalid signature for request GET /v1/_id/name@mail.com coming from app scoold
[ERROR] 403 - Invalid signature for request GET /v1/_id/theme%3Acustom coming from app scoold

I get the same logs when I log-in.
do you happen to have a hint for me why this is not working?
Access to the Scoold page is possible.
para_app_name = Scoold
para_secret_key = 7 digit string
para_access_key = Scoold
para_endpoint = https://paraio.com
adding para_security_allow_unverified_emails = true didn't help to bypass user registration. I still can't post a question without login

Alex Bogdanovski
@albogdano
@Quant:matrix.org did you create your Para app first?
Helix
@Quant:matrix.org
[m]
@albogdano: no, in the Readme file I went straight to the second deploy section to deploy Scoold on Heroku. 😁
Thanks for the hint.
But now I've created the app and I do receive the e-mail. However, the URL is something like:
http://localhost:11957/signin/register?id= ...... and that doesn't work
shouldn't it give me something like appname.herokuapp.com.......... for the e-mail confirmation-link? I've tried to replace the localhost with my Heroku Domain, but it didn't help
Alex Bogdanovski
@albogdano
@Quant:matrix.org yes, you should also set para_host_url = "https://appname.herokuapp.com"
Sawyer Ward
@sawyerw-cadwell
Sorry if this is the wrong place, but I am having an error in para which is causing scoold to not work:
2021-04-01 04:26:17 [ERROR] Failed to execute INDEX operation for index 'scoold_1597348543877', document id '1288281781392379904':
Is there a way to fix this index?
Alex Bogdanovski
@albogdano
@sawyerw-cadwell you can rebuild the index
Sawyer Ward
@sawyerw-cadwell
Ah yes. para-cli rebuild-index
I just found it
Alex Bogdanovski
@albogdano
using the para-cli tool run: para-cli rebuild-index
Sawyer Ward
@sawyerw-cadwell
Thanks
When I ran the command, I get an error.
Suppressed: org.elasticsearch.client.ResponseException: method [POST], host [http://localhost:9200], URI [/_aliases?master_timeout=30s&timeout=30s], status line [HTTP/1.1 429 Too Many Requests]
{"error":{"root_cause":[{"type":"cluster_block_exception","reason":"index [scoold_1597348543877] blocked by: [TOO_MANY_REQUESTS/12/index read-only / allow delete (api)];"}],"type":"cluster_block_exception","reason":"index [scoold_1597348543877] blocked by: [TOO_MANY_REQUESTS/12/index read-only / allow delete (api)];"},"status":429}
Sawyer Ward
@sawyerw-cadwell
But then it says:
2021-04-01 15:59:45 [INFO ] rebuildIndex(): 1921 objects reindexed in 'scoold' [shared: false].
Alex Bogdanovski
@albogdano
@sawyerw-cadwell I don't know how to help here -perhaps restart Elasticsearch
Sawyer Ward
@sawyerw-cadwell
OK
Sawyer Ward
@sawyerw-cadwell
Looks like I was a bit low on disk space which was the cause for both errors.
Upped the allocation, rebuild the index, and all is well
Thanks for the quick help
Alex Bogdanovski
@albogdano
@sawyerw-cadwell ah, yes, didn't think of that. Glad it worked! :)
b-morgenthaler
@b-morgenthaler
@albogdano Hi. Can you explain briefly how the overall search in Scoold (Pro) is working or should be working? When I search for "qt" which is neither a tag nor a text phrase that has been used in any q/a, the search result seems to be two randomly chosen user (which do not have the string "qt" in their name or anything related). This is confusing for user searching for "qt" or similar. Thanks in advance
Alex Bogdanovski
@albogdano
@b-morgenthaler Ok, search may need some more fine tuning because currently Scoold will search each object on all of its data fields, meaning that if those 2 user objects have some data inside them containing "qt" then they will appear in the results.
b-morgenthaler
@b-morgenthaler
@albogdano Understood. From a user perspective, the search result should help finding answers. So maybe limiting the result to tags and q/a title, subject, text and comments would be a good starting point. It could still behave like a full text search, i. e. finding substrings anywhere in the text.
b-morgenthaler
@b-morgenthaler
@albogdano I don't know how you think about this search improvement, I am going to open an issue to track this. Let me know if you need more input on this. Thanks
Alex Bogdanovski
@albogdano
@b-morgenthaler Sorry for the late reply. I saw your issue on GitHub and will start working on it soon.
b-morgenthaler
@b-morgenthaler
@albogdano No worries. As long as we are on the same page regarding the search, it's fine :-)
Alex Bogdanovski
@albogdano
@b-morgenthaler I managed to fix the issue you described but there is still some more work to be done in fine tuning the search queries for questions and answers
b-morgenthaler
@b-morgenthaler
@albogdano Great news. As soon as a new Pro version is available, I am going to install it on our test system (next week)
Alex Bogdanovski
@albogdano
sure, the plan is to release a new version next week
mark-os
@mark-os
if I set para.host_url will that update the SSL cert for the site?
Alex Bogdanovski
@albogdano
@mark-os no, that has no effect on the SSL cert
mark-os
@mark-os
So how do we change the cert to allow HTTPS to work with custom domains?
In scoold cloud
Alex Bogdanovski
@albogdano
the process is automatic, you just need to point your new custom domain to yourinstance.cloud.scoold.com and then save the changes on Scoold Cloud
b-morgenthaler
@b-morgenthaler

@albogdano Hi. I recently updated our test system to 1.43.1 Pro (from 1.41.2 Pro) and noticed a imho changed behavior in the users tab. Just want to clarify whether this is an issue or not:

I have several user in default space, one user in a custom space and one admin user

The admin user can only see all user when "all spaces" is active, when the custom space is active the user tab is empty for the admin user. I think previously it didn't make a difference which space is active for the admin user (or maybe the users got filtered by the active space - this I'm not sure about)

The user within the custom space does not see any other - aka user tab is empty. I agree that it is not necessary to see user from other spaces, but admin user should be seen from any user in any space?

Thanks in advance for looking into this.

Alex Bogdanovski
@albogdano
@b-morgenthaler
  • admins can see all users in "All spaces" only - works as intended
  • admin in custom space can only see users in that space - works as intended
  • user in custom space can only see other users in that space - works as intended
  • user in custom space cannot see admin users - not working as intended I agree this is somewhat confusing and will be fixed
  • admins cannot leave or join spaces themselves from the "bulk edit spaces" page because they are always members of each space - works as intended
b-morgenthaler
@b-morgenthaler
@albogdano thanks for clarifying but then there's another issue:
  • admin in custom spaces can not see users in that space
Alex Bogdanovski
@albogdano
ah, ok I will check that
b-morgenthaler
@b-morgenthaler
@albogdano unfortunately another unintended issue:
  • user in one space cannot see other user in the same space (regardless if the space is a custom space or default space)
b-morgenthaler
@b-morgenthaler

@albogdano unfortunately another unintended issue:

  • user in one space cannot see other user in the same space (regardless if the space is a custom space or default space)

This could be the reason why "user in custom space cannot see admin user" from above - simply because user don't see any other user at all

b-morgenthaler
@b-morgenthaler
I opened a new issue for the observation #244
Alex Bogdanovski
@albogdano
@b-morgenthaler fixed!
Alex Bogdanovski
@albogdano
the new release is coming tomorrow
b-morgenthaler
@b-morgenthaler
@albogdano Thanks :-)