@bloodbare is that the right URL I always get confused with Plone and Guillotina on Docker Hub :)
sorry, I screwed up, working too fast and accidentally committed directly to master my cherry pick: https://travis-ci.org/plone/guillotina/builds/653628955?utm_medium=notification&utm_source=email
I'll fix
Cloning into '.'...
Warning: Permanently added the RSA host key for IP address '192.30.253.112' to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
please ensure the correct public key is added to the list of trusted keys for this repository (128)
Warning: Permanently added the RSA host key for IP address '192.30.253.112' to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
please ensure the correct public key is added to the list of trusted keys for this repository (128)
BaseView (grange/views/base.ts) as I can see in the constructor is limited only to authenticated users. What is the reason for this?
Since it is an object exposed on the public api it should be used for creating custom views, isn't it?
Do you think that makes sense to opensource the way we managed it?
It's something more or less equivalent at setting up pyramid with postgres and traversal.
It's a guillotina (with permission system, traversal, zca, ....)
On another side, guillotina has evolved from a company project, to a project used on some companies (4 or 5) if I'm not wrong, and also we built some projects around it (in our case 2)... This makes me thing that right now we have to be super careful on braking changes... Something like (no braking changes)..
Later, if we want to brake something, I think the path should be to not brake it (just provide something else, and keep both things.. )
What do you think? @all
BTW, yesterday @masipcat_gitlab deployed G6 to production :)
haha
@jordic I definitely agree. Major versions it should be somewhat okay to break some things though.
The elasticsearch changes will I think be the final breaking changes for g6 right?
@masipcat_gitlab can I make you owner on pypi of guillotina_elasticsearch?
what is your pypi handle?
I'm
@masipcat
The elasticsearch changes will I think be the final breaking changes for g6 right?
No
Yes *
@masipcat_gitlab done!
Hi,
I’m helping @eikichi18 to develop an application using guillotina_amqp, but we found a problem trying to connect the “task” created by the worker and a simple web socket. We’ve created an object using the guillotina_amqp worker, notified the event to a subscriber, which put it on an utility queue, and tried to sent on a web socket, as shown during the training. The problem is that the worker do not allowed us to open the socket directly so we are force to open a second service on an other port that manages it. So we have the worker service opened with the “g amqp-worker” command, on the local port 5672, and the socket service open with the simple “g -c config.yaml” o “g” command, on the 8080. At this point we find the problem: the worker does not see the list of opened sockets and the socket does not read the events notified by the worker when an object is created in the database, as if we are managing two different instance. We think it could be a solution to save the socket’s list in the context using a new behavior, but first we are glad to hear a more expert opinion, maybe there is an easier way to connect the socket and the worker and we are doing something wrong.
I’m helping @eikichi18 to develop an application using guillotina_amqp, but we found a problem trying to connect the “task” created by the worker and a simple web socket. We’ve created an object using the guillotina_amqp worker, notified the event to a subscriber, which put it on an utility queue, and tried to sent on a web socket, as shown during the training. The problem is that the worker do not allowed us to open the socket directly so we are force to open a second service on an other port that manages it. So we have the worker service opened with the “g amqp-worker” command, on the local port 5672, and the socket service open with the simple “g -c config.yaml” o “g” command, on the 8080. At this point we find the problem: the worker does not see the list of opened sockets and the socket does not read the events notified by the worker when an object is created in the database, as if we are managing two different instance. We think it could be a solution to save the socket’s list in the context using a new behavior, but first we are glad to hear a more expert opinion, maybe there is an easier way to connect the socket and the worker and we are doing something wrong.
