You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openmeetings.apache.org by GitBox <gi...@apache.org> on 2021/10/06 21:31:06 UTC

[GitHub] [openmeetings] sebawagner commented on pull request #159: OPENMEETINGS-2678 Update and ignore if Notificaiton API is not available

sebawagner commented on pull request #159:
URL: https://github.com/apache/openmeetings/pull/159#issuecomment-937176725


   > @sebawagner I'll update some dependencies in master Could you please cherry-pick these changes? :)))
   
   Cherry pick, why? I can just merge master to the 6-2 branch
   
   But 6.2.0 is not ready to being released yet. This Notification API fix doesn't fix https://issues.apache.org/jira/browse/OPENMEETINGS-2679. It just gets rid of some JS errors.
   
   And yeah it would be good to verify https://issues.apache.org/jira/browse/OPENMEETINGS-2679 on the altea demo server. Once you get past the dashboard and login screen. But I tested OPENMEETINGS-2679  (including this Notification API fix) the issue still exists. And it seems more to do with signalling and how streams are created.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@openmeetings.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org