[folarinmartins]

Problem

Data updates published to a scoped client through POST /scopes/{scope_id}/data/update are silently dropped by the client. The scoped client only receives its data through the initial load and the periodic refresh, so real-time push and broadcast never take effect for scopes.

Why:

• The scoped client subscribes to <scope_id>:data:<topic> (DataUpdater.__init__, "Namespacing the data topics for the specific scope").
• The scope's data sources config entries are expected in that same form, which is why the initial load works.
• The scope update endpoint (opal_server/scopes/api.py) rewrites entry.topics = [f"data:{topic}" ...] and publishes through ScopedServerSideTopicPublisher, which prefixes the scope on the published topic only (<scope_id>:data:<topic>).
• The client therefore receives the event, but the entry inside it carries data:<topic>. DataUpdater._update_policy_data skips it because set(entry.topics).isdisjoint(set(self._data_topics)).

Observed (opal-server and opal-client 0.9.9; the same code is on master):

• The server logs Publishing to topics: ['document-access:data:documents'] for an update whose entry has 'topics': ['data:documents'].
• The scoped client (OPAL_SCOPE_ID=document-access, OPAL_DATA_TOPICS=documents) never applies it.
• The same data appears only at the next periodic refresh.

Fix

The topic check moves into a small DataUpdater._entry_matches_data_topics(). For a non-default scope, it normalises an entry topic without the scope prefix to <scope_id>:<topic> before comparing.

• Scoped config entries (<scope_id>:data:<topic>): unchanged.
• Scoped push entries (data:<topic>): now match.
• Another scope's topic (other:data:<topic>): still doesn't match.
• Clients in the default scope: unchanged; no rewriting.

This is the smallest change that keeps both the config-entry form and the push-entry form valid. A server-side alternative would rewrite the entries' topics in the scope endpoint to the full scoped form. That needs the publisher to stop prefixing the scope again, and it changes the wire format for any other subscriber, so I kept the fix on the client side. Happy to move it if you prefer.

Tests

The new packages/opal-client/opal_client/tests/data_updater_scoped_topics_test.py covers:

• scoped/scoped-config match;
• scoped/pushed match;
• other-scope rejection;
• unsubscribed-topic rejection;
• default-scope behaviour unchanged.

8 cases, all passing locally.

[netlify]

✅ Deploy Preview for opal-docs canceled.

Name	Link
🔨 Latest commit	8c50250
🔍 Latest deploy log	https://app.netlify.com/projects/opal-docs/deploys/6adfcbde6912dd3fb60f75f8

[zeevmoney]

Thank you for the clear write-up and the fix.

We're fixing this on the server side in #949. With it, the entries carry the scoped topic that clients already match. That works for every client, older ones included, without a client change.

Closing in favour of #949. Thanks again.