-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Messages to inbox are not forwarded to followers #40
Comments
I believe this is the relevant message:
This could well be something in the proxy config. |
On the test server, it doesn't work as well:
|
If you use without SSL, it seems to work, right? |
Nope, when using http-only, the server sends a 301 redirect to the https version:
|
Interesting. Use the "-L" with curl and it seems to work, no? |
Uh, right: "POST has been converted to GET and no more data is forwarded." , so this is a different thing. |
Ok. Got it:
Fixed this by freeing disk space. Restarted ES.
Manipulating the data to POST to: "@context" :{
"id" : "https://w3id.org/kim/lrmi-profile/draft/context.jsonld"
},
... the document is created. To not happen 1. again I will put free space observated by Nagios which warns us by email. |
fyi, index was set to "read only" because of the low watermark of disk space since 2020-10-03. |
As discussed offline with @acka47 we delete the ES index. A new indexed document would then determine the ES settings field structure to be ok with what is used atm. |
@acka47 confirmed to change the schema at https://github.com/dini-ag-kim/lrmi-profile to comply to elasticsearch's "Arrays with a mixture of data types are not supported". |
|
In JSON-LD an '@context' is used to define semantics of JSON fields. These definitions can consist of an array with mixed data types. This is invalid when tried to be indexed into elasticsearch. As a mapping of the index can be defined to ignore the '@context' field for indexing such an JSON-LD document can then be loaded into elasticsearch. The mapping must be set when initializing the index. This is done in the start script provided by skohub-pubsub. See #40.
In JSON-LD an '@context' is used to define semantics of JSON fields. These definitions can consist of an array with mixed data types. This is invalid when tried to be indexed into elasticsearch. As a mapping of the index can be defined to ignore the '@context' field for indexing such an JSON-LD document can then be loaded into elasticsearch. The mapping must be set when initializing the index. This is done in the start script provided by skohub-pubsub. See #40.
Deployed to test. Please test it @acka47, use the 'test.skohub.io' URL to do so. |
It does work better than before but the messages won't get trough to Mastodon anyway. I created a new build at https://test.skohub.io/build/?id=e06c1fe4-a93f-4a92-bed7-61e70a7eabd1. I followed n271, see the followers list. I posted with curl like this:
However, the message is not forwarded to the followers it seems as I don't get a message in Mastodon. One strange thing in this context: the concept is not listed in my "following" list on Mastodon (but others are): |
However, as the original problem seems to be fixed, we can already deploy the changes to production and then look into the remaining issue. |
Deployed to production. Please test it @acka47 . |
Comparing the logs of production (it's just empty) and the one I got on test.skohub:
|
@literarymachine, does this maybe ring a bell? If not, we can leave this for now nbecause it works on production where it is most important... |
It could be that the message's signature cannot be verified, you might want to compare the configurations on test and prod starting here: https://github.com/skohub-io/skohub-vocabs/blob/master/.env.example#L6 Unfortunately I don't really have the time right now to wrap my head back around those authentication issues... |
|
Whether I use the editor or curl, I can post to the inbox but it won't be forwarded to the followers' inboxes.
Curl example:
The command will stop at this point for quite some time and after a while this is added:
Result: the message is in the inbox but I do not get it via Mastodon although I am a follower of the respective concept.
Using the editor or the extension it is very similar:
@dr0i, there must be something wrong on the server side, I guess. It did function before, though. Maybe @literarymachine has an idea...
The text was updated successfully, but these errors were encountered: