jR]@dZddlmZdddddZd dZd dZdd d d Zy)u The EVENT configuration → feed meta overlay, in one place. The competition's own presentation — which venue and which WORLD (photoreal vs the stylised water plane), the boat class, the fleet's hull livery, whether there are RC vessels, the start-sequence length — is `event_config` data, and the renderer reads it off the feed meta. Two producers derive that meta: the store-backed one (`serve_v3_live.apply_event_config`, reading the config out of the database) and the REST one (`rest_source`, reading it over `/v3/manage/events/{id}/config`), and they must land on the SAME meta or the same race looks like two different productions depending on where the producer happens to run. It did. The REST path built its meta from scratch and never applied the event config at all, so a producer run with `--follow --read-base` — the deployment the whole live operation is built on, render PC or cloud — rendered a bare stylised sea on an event whose config asks for the photoreal venue. Verified on the field-practice broadcast 2026-08-01: `meta.world` was absent and the scene came up as flat water with no buildings. `integrations` (secret refs) are NEVER copied into meta — they are server-side only. ) annotationsstartfinish) start_port start_stbd finish_port finish_stbdc t|tsydt|jddi} t dt dt |jdd|d<t dt d t|jd d |d <i}d D]v}t|jd tr$|jd xsij|nd}t|tsZt|jddj}|dvrd|i}|jd}|rt||d<dD]m\}} |j|} t| ttfs.t| | k(s= | D cgc] } t | } } td| Dsi| ||<o d|vr%t dt dt |d|d<d|vr%t dt dt|d|d<|||<y|sy||d <|S#ttf$rYywxYwcc} w#ttf$rYwxYw#ttf$rYwxYw)a~Sanitize the event's visual line-detector controls before they reach browser clients. Camera calibration is event data, while detector profiles are a closed renderer capability. Keeping that boundary here prevents an arbitrary stored document from expanding the detector's work area, cadence or hold time beyond the limits the on-air browser source was tested for. NenabledFg?g@ sampleFpsri maxHoldMsi^)rrrolesdetector>redbluegreenyellow checkered darklight redorange targetRole))anchor)searchr ) targetBoxr ) targetSizerc3<K|]}d|cxkxrdkncyw)rN).0items =/srv/vr/releases/25f455cc4e75/v3/broadcast/live/event_meta.py z,_line_camera_overlay_meta..Fs7$qD~A~~7s minConfidenceg?g\(\? minPixelsi ) isinstancedictboolgetmaxminfloatint TypeError ValueErrorstrlowerlisttuplelenall) rawoutrnamevaluerroletargetkeylengthdeclaredr#numss r$_line_camera_overlay_metarC"se c4  d3779e45 6CsCU377;3J-K$LMKq#c3sww{C/H+I"JKK E#6@AQSW6X!'R,,T2^b%& uyyR01779 ) ) H%<( !$VD / %KCyy~H(T5M2s8}7N4<=DE$K=D=7$77 $DI % %'(+BCu_?U9V0W(X_%e#$'3sCk8J4K+L$M[!d ;< CL JI z "(>!:.:&   sIA$HH6 H1H68AI H.-H.1H66I I  IIc|siS|xsijdxsijdxsi}i}|jD]*\}}tj|}|s|s!|d|||<,|S)u`{"start"|"finish": slot}` for the line ends this event puts a phone on. The slot is built rather than looked up, and it is built from the account NAME the QR was minted with (`trwc2026:buoy:A`) — never from an owner id. The two spellings are one of this codebase's standing traps: every owner column in the database is a `users.id`, while a slot prefix is the username, and comparing one to the other matches nothing without failing. No owner, or an event that declares no vessels ⇒ `{}`. A club Saturday whose line runs between two buoys simply has no vessel cameras, which is absence rather than a camera that is off. devicesvesselsz:buoy:)r,itemsVESSEL_CAMERA_NAMES)cfgownerrFr:r=bidr;s r$vessel_camera_slotsrLVs   ry)/R44Y?E2G C]]_. c"&&t, C 'u-CI. JN)rJc |s|St|}t||}|r||d<|jdxsijdxsi}t|tr<|j Dcgc]\}}|t vr |r t |}}}|r||d<|jdrt |d|d< ddlm} | |} | | |d <|jd xsi} | r$t|jd xsi} | jdrt | d| d<| jd rt | d | d <| jd rt | d | d <dD]Y} t| j| ttfs)t| j| trIt| | | | <[| jdt| d| d<| jdrt | d| d<| jdrt| d| d<| jdr| d| d<| jdrt | d| d<| jdrt| d| d<| jdrt| d| d<ddlm}|jdxsijdxsijd}|| |\}}|r|| d<|r|| d<| |d <|jdrt |d|d<|jdr|d|d<|jdxsi}|jdt|d|d<|jd t|d |d <|jd!t|d!|d!<|jd"t|d"|d"<|jd#rt|d#|d#<|jd$rt |d$|d$<t|jd%trL|d%j Dcic]*\}}t|trt |t|,c}}|d%<t|jd&trW|d&j Dcic]5\}}t |t|tr t|n t |7c}}|d&<t|jd'trXi}|d'j D]9\}} t|}|d(zd(zd(z}|d)kDr|d(z}|d*vs,||t |<;|r||d'<t#|jd+}|r||d+<|jd,t|d,|d,<|jd-|d-|d-<|jd.rt|d.|d.<t|jd/tr]|d/j Dcic];\}}t|tr&|jd0rt |t|=c}}|d/<t|jd1tr]|d1j Dcic];\}}t|tr&|jd0rt |t|=c}}|d1<t|jd2trU|d2j Dcic]3\}}t |j%rt |t |5c}}|d2<|jd3}|d)}|t|}|dkDrt'd4||d3<|jd5rt |d5|d6<|jdrt|d|d<|jd7t|d7|d7<|jd8rt|d8|d8<|jd9rt |d9|d9<|jd:d;vrt |d:|d:<|jd<rt|d<|d<<|jd=rt|d=|d=<|jd>rt|d>|d><|jd?rt|d?|d?<|jd@rt|d@|d@<|Scc}}w#tttf$rd } YpwxYwcc}}wcc}}w#ttf$rYwxYwcc}}wcc}}wcc}}w)AuOverlay an event-configuration document onto derived feed meta and return the result. Applied BEFORE any per-instance broadcast config, so instance keys win: engine-derived defaults < event config < instance broadcast config. An empty/None config leaves the meta untouched (full backwards compatibility). `owner` is the account NAME the devices registered under, and it is needed for one thing: turning the event's declared vessel buoy ids into slot refs the picture can ask for clips by. Callers derive it from a boat ref they already hold rather than from an owner column, because a slot prefix is the username and every owner column is a `users.id` — the two spellings that match nothing when compared and fail silently when they do. vesselCamerasrErF vesselRolesr; eventNamer)course_line_length_mN courseLineMvenuetimeZonedisplayTimeZoneLabel) centreLat centreLoncityBearingDegworld waterSurfacenavMarks speechLang speechNames speechIpa)venue_place_lists presentationcruisetourCategories) categories landmarks tourSites boatClassteamBibs neuralTtsOnlyneuralTtsFallbacknoDownwindSails rcVessels markColors hullLivery hullProfileshullSubstitutionscameraDisplayRotationDegByRefih)iLirZrrlineCameraOverlayshowJibNumberssailPlan sailFlagByBibidentityStreamersassetsailIdentityStreamersmastheadIdentityLabelByBibwaitingCoursePresentationEveryS<modepresentationModecrew signalFlags penaltyRegimeobservedGeometryGuard)rieoff sanctionMark partnerMarkseventWaterMark waitingMusic startSequence)r*rLr,r)rGrHr3 event_configrR ImportErrorr1r2r0r/r+r5r`rCstripr-) metarIrJr:rF vessel_rolesr=buoy_iddeclared_rolesrR_line_mrTv_kr`_cats _landmarks _tour_sitespreshullprofileslot replacement rotationsrefr<degline_camera_overlaycodespeclabelwaiting_course_ss r$overlay_event_configrlsx   t*C"#u-G&OWWY'-2229=CL,%9E9K9K9MF g!%88Wd)FF !/C  wwvs6{+K5&s+$M GGG  "E !'R ( 99V E&M*AfI 99Z  j 12AjM 99+ ,),E2H,I(JA$ %- )B%))B-#u6z%))TV-Y]?^eBi(" ) 99% & 2"'.>(?"@A  99W U7^,AgJ 99^ $ !%U>%: ;An  99Z !*-AjM 99\ ""% "56AlO 99] ##E-$89Am  99[ !!% "45AkN 3''.)/R44X>D"IIJZ["3Ee"L K 'AkN (AkNG  ww{s;/0K wwzj/J 77> " (bD xx , $D$9:O xx#$0#'-@(A#B   xx!".!%d+<&=!>  xx ([ 12K xx  !l!34L xx \ 23L$((>*D1594H4N4N4P=#04",Wd"; #4y$w-7=N$((./6 &**=%>%D%D%F$ !k IJ{D,ItK(sS^O_ _$   $((:;TB  >?EEG *JC %j#I$+CSys --&) #c(# * 3rs;&#H 1h,OSPrM