** Notice: all internal pipelines have been restricted to 30 minute timeouts, if your CI/CD runs take longer, either use your own runners or read below **
We would remind everyone that the CI/CD services provided by the university Gitlab servers are intended for CI/CD use only (ie. delivering new versions of your software to your production servers, etc).They are not intended for data analysis or -production use, or creating, building and running servers to do heavy data calculation or visualization.
As a general guideline; if your jobs take more than 15 minutes, you might be running something that is better suited for a dedicated system or a virtual server - in this case, please contact the helpdesk for a solution to your needs.
* Allow certain channels to be restricted to prevent change in response frames.
* Allow certain channels to be restricted to prevent change in response frames.
* Do not allow `FrameCreator` objects for sources that are not owned (except via `response()`)
* Do not allow `FrameCreator` objects for sources that are not owned (except via `response()`)
Another approach to the above is to use the existing frame info on `foreign` vs `local` vs `completed` frames. This same status information can determine of the frame is a response frame or a primary frame, response frames arrive without the `foreign` tag where as primary frames have the flag. The flag should be renamed to `response` vs `primary`.
It should be possible to merge multiple sources into a single frameset, currently this occurs inside the `Stream` objects through a multiplexing/demultiplexing process.
It should be possible to merge multiple sources into a single frameset, currently this occurs inside the `Stream` objects through a multiplexing/demultiplexing process.
