I totally meant the code block & Failed to connect to event stream wasn’t really pointing to the issue. That was a ‘red herring’, meaning I don’t see it as being the cause of not being able to get your repo to build and launch. Sorry for the misunderstanding.
To make it clear. Hiccups that come up sometimes don’t end up being clear about what is going on. Often you’ll get the Failed to connect to event and later it will work just fine, after some time. And unless something changed in your apt.txt, the issue concerning bionic-security part isn’t in your hands. In other words, unless you changed something in the configuration file and then you got errors, it is probably something that will sort itself out if you try again later or get a different federation member to launch from. Similar to the API stuff you saw in your other post.