dev  

Messages by Thread

• (unomi) branch UNOMI-1014-aggregate-tenant-filter updated (6872c08c7 -> 985649f2f) shuber
• [jira] [Commented] (UNOMI-1014) Aggregate queries with a condition return nothing Serge Huber (Jira)
• [PR] UNOMI-1014: Return aggregate results and keep them in the current tenant [unomi] via GitHub
• (unomi) branch UNOMI-1014-aggregate-tenant-filter created (now 6872c08c7) shuber
  • (unomi) 01/01: UNOMI-1014: Return aggregate results and keep them in the current tenant shuber
• [jira] [Commented] (UNOMI-1013) Let each tenant list the websites that can use its tracker Serge Huber (Jira)
• [jira] [Updated] (UNOMI-1016) Public API key lookup reads every tenant on each request Serge Huber (Jira)
  • [jira] [Updated] (UNOMI-1016) Public API key lookup reads every tenant on each request Serge Huber (Jira)
• (unomi) branch UNOMI-1013-tenant-cors-origins deleted (was a22fd07cb) shuber
• (unomi) branch UNOMI-1013-tenant-cors-origins updated (7c6fdf17d -> a22fd07cb) shuber
• (unomi) branch UNOMI-1013-tenant-cors-origins updated (323dc4461 -> 7c6fdf17d) shuber
• [jira] [Updated] (UNOMI-1013) Let each tenant list the websites that can use its tracker Serge Huber (Jira)
• [jira] [Created] (UNOMI-1016) Speed up looking up a tenant by its API key Serge Huber (Jira)
• [PR] UNOMI-1013: Let each tenant list the websites that can use its tracker [unomi] via GitHub
  • Re: [PR] UNOMI-1013: Let each tenant list the websites that can use its tracker [unomi] via GitHub
• (unomi) branch UNOMI-1013-tenant-cors-origins created (now 323dc4461) shuber
  • (unomi) 01/01: UNOMI-1013: Let each tenant list the websites that can use its tracker shuber
• (unomi) branch UNOMI-1005-tracker-cookie-origins deleted (was 9ea9e2298) shuber
• (unomi) branch UNOMI-1005-tracker-cookie-origins updated (210fe6c14 -> d877cc087) shuber
• (unomi) branch UNOMI-1005-tracker-cookie-origins updated (8034af39e -> 51a2a8678) shuber
• (unomi) branch UNOMI-1005-tracker-cookie-origins updated (d877cc087 -> 9ea9e2298) shuber
• (unomi) branch UNOMI-1005-tracker-cookie-origins updated (51a2a8678 -> 210fe6c14) shuber
• (unomi) branch UNOMI-1005-tracker-cookie-origins updated (f405c5844 -> 8034af39e) shuber
• (unomi) branch UNOMI-1005-tracker-cookie-origins updated (357c291e6 -> f405c5844) shuber
• (unomi) branch UNOMI-1005-tracker-cookie-origins updated (ac3a686f3 -> 357c291e6) shuber
• (unomi) branch UNOMI-1005-tracker-cookie-origins updated (3da34b6ad -> ac3a686f3) shuber
• [jira] [Assigned] (UNOMI-1005) The web tracker and the server disagree on cookies across sites Serge Huber (Jira)
• [PR] UNOMI-1005: Allow visitor cookies only for listed website origins [unomi] via GitHub
  • Re: [PR] UNOMI-1005: Allow visitor cookies only for listed website origins [unomi] via GitHub
• (unomi) branch UNOMI-1005-tracker-cookie-origins created (now 3da34b6ad) shuber
  • (unomi) 01/01: UNOMI-1005: Allow visitor cookies only for listed website origins shuber
• [PR] UNOMI-1005: Add an option to send tracker requests without cookies [unomi-tracker] via GitHub
• (unomi) branch UNOMI-1004-hover-condition-optional-or deleted (was 8b88d353d) shuber
• (unomi) branch master updated: UNOMI-1004: Omit unset optional branches from boolean OR (#919) shuber
• (unomi) branch UNOMI-1004-hover-condition-optional-or updated (e83f13bc6 -> 8b88d353d) shuber
• [jira] [Created] (UNOMI-1015) Empty boolean condition does not match the same items in rules and in searches Serge Huber (Jira)
• (unomi) branch UNOMI-1004-hover-condition-optional-or updated (3bd8f8897 -> e83f13bc6) shuber
• (unomi) branch UNOMI-1004-hover-condition-optional-or updated (6a14294b7 -> 3bd8f8897) shuber
• (unomi) branch UNOMI-1004-hover-condition-optional-or updated (585e58f60 -> 6a14294b7) shuber
• (unomi) branch UNOMI-1004-hover-condition-optional-or updated (9c11ebf01 -> 585e58f60) shuber
• [jira] [Commented] (UNOMI-1004) A hover condition with only a target id matches every hover event Serge Huber (Jira)
• (unomi) branch UNOMI-1004-hover-condition-optional-or created (now 9c11ebf01) shuber
• [PR] UNOMI-1004: Omit unset optional branches from boolean OR [unomi] via GitHub
  • Re: [PR] UNOMI-1004: Omit unset optional branches from boolean OR [unomi] via GitHub
• (unomi) branch UNOMI-1003-segment-scoring-list-sort deleted (was 8692a44fa) shuber
• [jira] [Assigned] (UNOMI-1004) A hover condition with only a target id matches every hover event Serge Huber (Jira)
• (unomi) branch master updated: UNOMI-1003: Sort merged segment/scoring lists and fix missing limit (#917) shuber
• (unomi) branch UNOMI-1003-segment-scoring-list-sort updated (f6de8939d -> 8692a44fa) shuber
• (unomi) branch unomi-3.0.x updated: Bound the MVEL expression cache (unomi-3.0.x) (#918) jsinovassinnaik
• (unomi) branch backport/bound-mvel-caches-3.0.x-reland deleted (was 06fd017f4) jsinovassinnaik
• (unomi) branch backport/bound-mvel-caches-3.0.x-reland created (now 06fd017f4) jsinovassinnaik
  • (unomi) 01/01: Bound the MVEL expression cache (unomi-3.0.x) (#891) jsinovassinnaik
• [jira] [Commented] (UNOMI-1003) Segment and scoring lists ignore the sort, and fail with no limit Serge Huber (Jira)
• [PR] UNOMI-1003: Sort merged segment/scoring lists and fix missing limit [unomi] via GitHub
  • Re: [PR] UNOMI-1003: Sort merged segment/scoring lists and fix missing limit [unomi] via GitHub
• (unomi) branch UNOMI-1003-segment-scoring-list-sort created (now f6de8939d) shuber
  • (unomi) 01/01: UNOMI-1003: Sort merged segment/scoring lists and fix missing limit shuber
• [jira] [Assigned] (UNOMI-1003) Segment and scoring lists ignore the sort, and fail with no limit Serge Huber (Jira)
• (unomi) branch master updated: UNOMI-1006: Generate a node id per node and run the heartbeat on every node (#916) shuber
• (unomi) branch UNOMI-1006-scheduler-cluster-node-id deleted (was bf956b264) shuber
• (unomi) branch backport/deny-public-mvel-eval-3.0.x updated: Bound the MVEL expression cache (unomi-3.0.x) (#891) jsinovassinnaik
• (unomi) branch unomi-3.0.x updated: Write filtered personalization contents back onto the request (unomi-3.0.x) (#890) jsinovassinnaik
• (unomi) branch unomi-3.0.x updated: Deny public MVEL eval APIs from the scripting class loader (unomi-3.0.x) (#892) jsinovassinnaik
• (unomi) branch UNOMI-1006-scheduler-cluster-node-id updated (22923d2ea -> bf956b264) shuber
• (unomi) branch UNOMI-1006-scheduler-cluster-node-id updated (6cffe0a7e -> 22923d2ea) shuber
• (unomi) branch UNOMI-1006-scheduler-cluster-node-id updated (574381b0f -> 6cffe0a7e) shuber
• (unomi) branch UNOMI-1006-scheduler-cluster-node-id updated (6f49fc8b4 -> 574381b0f) shuber
• [jira] [Commented] (UNOMI-1006) All Unomi nodes share the same scheduler node id by default Serge Huber (Jira)
• [PR] UNOMI-1006: Default scheduler node id to the cluster node id [unomi] via GitHub
  • Re: [PR] UNOMI-1006: Generate a node id per node and run the heartbeat on every node [unomi] via GitHub
• (unomi) branch UNOMI-1006-scheduler-cluster-node-id created (now 6f49fc8b4) shuber
• [jira] [Assigned] (UNOMI-1006) All Unomi nodes share the same scheduler node id by default Serge Huber (Jira)
• (unomi) branch UNOMI-1002-compat-tenant-cache deleted (was 03e5e8210) shuber
• (unomi) branch master updated: UNOMI-1002: Stop serializing public requests in compatibility mode (#915) shuber
• (unomi) branch UNOMI-1002-compat-tenant-cache updated (a783f024e -> cfb549f92) shuber
• (unomi) branch UNOMI-1002-compat-tenant-cache updated (cfb549f92 -> 03e5e8210) shuber
• [jira] [Commented] (UNOMI-1002) In compatibility mode, all public requests wait on each other Serge Huber (Jira)
• (unomi) branch UNOMI-1002-compat-tenant-cache created (now a783f024e) shuber
• [PR] UNOMI-1002: Stop serializing public requests in compatibility mode [unomi] via GitHub
  • Re: [PR] UNOMI-1002: Stop serializing public requests in compatibility mode [unomi] via GitHub
• [jira] [Assigned] (UNOMI-1002) In compatibility mode, all public requests wait on each other Serge Huber (Jira)
• (unomi) branch master updated: UNOMI-1001: Restore 3.0 peer abilities in compatibility mode (#914) shuber
• (unomi) branch UNOMI-1001-compat-peer-abilities updated (b0cdf9735 -> 8cabe44de) shuber
• (unomi) branch UNOMI-1001-compat-peer-abilities updated (8cabe44de -> de3a16c41) shuber
• (unomi) branch UNOMI-1000-background-tasks-tenants deleted (was 4e5ba0c7c) shuber
• (unomi) branch UNOMI-1001-compat-peer-abilities updated (06e2b04e4 -> b0cdf9735) shuber
• (unomi) branch UNOMI-1001-compat-peer-abilities created (now 06e2b04e4) shuber
  • (unomi) 01/01: UNOMI-1001: Restore 3.0 peer abilities in compatibility mode shuber
• [PR] UNOMI-1001: Restore 3.0 peer abilities in compatibility mode [unomi] via GitHub
  • Re: [PR] UNOMI-1001: Restore 3.0 peer abilities in compatibility mode [unomi] via GitHub
• [jira] [Assigned] (UNOMI-1001) In compatibility mode, 3.0 third-party servers lose features Serge Huber (Jira)
• (unomi) branch UNOMI-1000-background-tasks-tenants updated (8f10aad3f -> 4e5ba0c7c) shuber
• (unomi) branch UNOMI-1000-background-tasks-tenants updated (16c17bbcf -> 8f10aad3f) shuber
• (unomi) branch UNOMI-1000-background-tasks-tenants updated (2fdd99954 -> 16c17bbcf) shuber
• (unomi) branch UNOMI-1000-background-tasks-tenants updated (e55fd88ea -> 2fdd99954) shuber
• (unomi) branch UNOMI-1000-background-tasks-tenants updated (b8fa761c1 -> e55fd88ea) shuber
• (unomi) branch UNOMI-1000-background-tasks-tenants updated (d1af55fc1 -> b8fa761c1) shuber
• Unomi October Monthly Meeting Minutes Serge Huber
• (unomi) branch UNOMI-998-migrate-from-30 updated (f520ecf27 -> 3b387b9a4) shuber
• (unomi) branch master updated: UNOMI-998: Cover a 3.0 to 4.0 migration in the integration tests (#910) shuber
• (unomi) branch UNOMI-998-migrate-from-30 deleted (was 3b387b9a4) shuber
• (unomi) branch UNOMI-998-migrate-from-30 updated (648d6dad7 -> d67ac7e19) shuber
• (unomi) branch master updated: UNOMI-985: Update the Develocity Maven extension to 2.6.0 for Maven 3.10 (#912) shuber
• (unomi) branch unomi-3.0.x updated: UNOMI-985: Build unomi-3.0.x with Maven 3.10 (#913) shuber
• (unomi) branch UNOMI-998-migrate-from-30 updated (d67ac7e19 -> f520ecf27) shuber
• [PR] UNOMI-985: Build unomi-3.0.x with Maven 3.10 [unomi] via GitHub
  • Re: [PR] UNOMI-985: Build unomi-3.0.x with Maven 3.10 [unomi] via GitHub
  • Re: [PR] UNOMI-985: Build unomi-3.0.x with Maven 3.10 [unomi] via GitHub
• [PR] UNOMI-985: Update the Develocity Maven extension to 2.6.0 for Maven 3.10 [unomi] via GitHub
  • Re: [PR] UNOMI-985: Update the Develocity Maven extension to 2.6.0 for Maven 3.10 [unomi] via GitHub
  • Re: [PR] UNOMI-985: Update the Develocity Maven extension to 2.6.0 for Maven 3.10 [unomi] via GitHub
• (unomi) branch UNOMI-998-migrate-from-30 updated (1e48f5b1e -> 648d6dad7) shuber
• (unomi) branch UNOMI-998-migrate-from-30 updated (fbaff8fde -> 1e48f5b1e) shuber
• (unomi) branch UNOMI-998-migrate-from-30 updated (d15802ebc -> fbaff8fde) shuber
• (unomi) branch UNOMI-997-migration-tenants deleted (was 026c6502a) shuber
• [jira] [Assigned] (UNOMI-998) Migration tests do not cover an upgrade from Unomi 3.0 Serge Huber (Jira)
• [PR] UNOMI-998: Cover a 3.0 to 4.0 migration in the integration tests [unomi] via GitHub
  • Re: [PR] UNOMI-998: Cover a 3.0 to 4.0 migration in the integration tests [unomi] via GitHub
  • Re: [PR] UNOMI-998: Cover a 3.0 to 4.0 migration in the integration tests [unomi] via GitHub
• (unomi) branch UNOMI-998-migrate-from-30 created (now d15802ebc) shuber
• [jira] [Commented] (UNOMI-1000) Background tasks only process the internal "system" tenant Serge Huber (Jira)
• [jira] [Commented] (UNOMI-998) Migration tests do not cover an upgrade from Unomi 3.0 Serge Huber (Jira)
• (unomi) branch UNOMI-1000-background-tasks-tenants created (now d1af55fc1) shuber
• [PR] UNOMI-1000: Run background tasks for every tenant [unomi] via GitHub
  • Re: [PR] UNOMI-1000: Run background tasks for every tenant [unomi] via GitHub
• (unomi) branch master updated: UNOMI-997: Put migrated items in the right tenant (#909) shuber
• (unomi) branch UNOMI-997-migration-tenants updated: UNOMI-997: Address review findings on tenant assignment shuber
• (unomi) branch UNOMI-997-migration-tenants updated: UNOMI-997: Keep create audit when redeploying migrated defs shuber
• (unomi) branch UNOMI-997-migration-tenants updated: UNOMI-997: Drop duplicate CXF jaxrs dependency in rest POM shuber
• [PR] UNOMI-997: Put migrated items in the right tenant [unomi] via GitHub
  • Re: [PR] UNOMI-997: Put migrated items in the right tenant [unomi] via GitHub
• (unomi) branch UNOMI-997-migration-tenants created (now d59bd02b4) shuber
  • (unomi) 01/01: UNOMI-997: Put migrated items in the right tenant shuber
  • (unomi) branch UNOMI-997-migration-tenants created (now d59bd02b4) shuber
  • (unomi) 01/01: UNOMI-997: Put migrated items in the right tenant shuber
• (unomi) branch master updated: UNOMI-996: Let the 3.0 to 4.0 migration finish (#908) shuber
• (unomi) branch UNOMI-996-migration-mappings deleted (was 7812c092b) shuber
• (unomi) branch UNOMI-996-migration-mappings updated: UNOMI-996: ship migration mappings in the bundle and fail on missing ones shuber
• [PR] UNOMI-996: Let the 3.0 to 4.0 migration finish [unomi] via GitHub
  • Re: [PR] UNOMI-996: Let the 3.0 to 4.0 migration finish [unomi] via GitHub
• (unomi) branch UNOMI-996-migration-mappings updated: UNOMI-996: Use Jackson in the mapping IT and assert the real item type shuber
  • (unomi) branch UNOMI-996-migration-mappings updated: UNOMI-996: Use Jackson in the mapping IT and assert the real item type shuber
• [jira] [Assigned] (UNOMI-996) Migration from Unomi 3.0 stops before it finishes Serge Huber (Jira)
• (unomi) branch UNOMI-973-tenant-file-endpoints created (now ada2ddcb9) shuber
  • (unomi) 01/01: Merge remote-tracking branch 'github/master' into UNOMI-973-tenant-file-endpoints shuber
• (unomi) branch UNOMI-996-migration-mappings created (now dd5d4954a) shuber
  • (unomi) 01/01: UNOMI-996: harden 4.0 tenant document-id migration and mapping IT shuber
• (unomi) branch backport/graphql-websocket-auth-3.0.x created (now 1cbb18234) shuber
  • (unomi) 01/01: Merge remote-tracking branch 'origin/unomi-3.0.x' into backport/graphql-websocket-auth-3.0.x shuber
• (unomi) branch UNOMI-999-scope-purge deleted (was fbb3295b0) shuber
• (unomi) branch master updated: UNOMI-999: Keep scope purge limited to one scope (#907) shuber
• (unomi) branch UNOMI-999-scope-purge updated: UNOMI-999: Purge whole scopes and match folded scope names shuber
• (unomi) branch UNOMI-999-scope-purge created (now 4ae92b426) shuber
  • (unomi) 01/01: UNOMI-999: Keep scope purge limited to one scope shuber
• [PR] Bump org.jsoup:jsoup from 1.23.1 to 1.23.2 in /samples/groovy-actions [unomi] via GitHub
• [PR] UNOMI-999: Keep scope purge limited to one scope [unomi] via GitHub
  • Re: [PR] UNOMI-999: Keep scope purge limited to one scope [unomi] via GitHub
• (unomi) branch dependabot/npm_and_yarn/graphql/graphql-ui/source-map-js-1.2.2 created (now b210a706a) github-bot
• (unomi) branch dependabot/maven/samples/groovy-actions/org.jsoup-jsoup-1.23.2 created (now 76bf877e0) github-bot
• [PR] Bump source-map-js from 1.2.0 to 1.2.2 in /graphql/graphql-ui [unomi] via GitHub
• (unomi) branch master updated: chore: restore 4.0.0-SNAPSHOT after cancelled RC1 shuber
• (unomi) tag unomi-root-4.0.0-rc1 created (now e54cbaebf) shuber
• (unomi) annotated tag unomi-root-4.0.0 deleted (was d06e0cf3e) shuber
• [jira] [Updated] (UNOMI-1014) Aggregate queries with a condition return nothing Serge Huber (Jira)
• [jira] [Created] (UNOMI-1014) Aggregate queries with a condition return nothing on Elasticsearch Serge Huber (Jira)
• [jira] [Created] (UNOMI-999) Deleting the data of one scope deletes all the data of the tenant Serge Huber (Jira)
• [jira] [Created] (UNOMI-997) After migration from 3.0, some data ends up in the wrong tenant Serge Huber (Jira)
• [jira] [Created] (UNOMI-1013) Let each tenant list the websites that can use its tracker Serge Huber (Jira)
• [jira] [Created] (UNOMI-1007) Health check environment variables no longer have any effect Serge Huber (Jira)
• [jira] [Updated] (UNOMI-1002) In compatibility mode, all public requests wait on each other Serge Huber (Jira)
• [jira] [Commented] (UNOMI-1005) The web tracker and the server disagree on cookies across sites Serge Huber (Jira)
  • [jira] [Commented] (UNOMI-1005) The web tracker and the server disagree on cookies across sites Serge Huber (Jira)
  • [jira] [Commented] (UNOMI-1005) The web tracker and the server disagree on cookies across sites Serge Huber (Jira)
  • [jira] [Commented] (UNOMI-1005) The web tracker and the server disagree on cookies across sites Serge Huber (Jira)
  • [jira] [Commented] (UNOMI-1005) The web tracker and the server disagree on cookies across sites Serge Huber (Jira)
• [jira] [Commented] (UNOMI-1007) Health check environment variables no longer have any effect Serge Huber (Jira)
• [jira] [Commented] (UNOMI-1008) Admin requests without a tenant header do not see migrated data Serge Huber (Jira)
• [jira] [Commented] (UNOMI-1009) The 3.0 to 4.0 migration guide misses several breaking changes Serge Huber (Jira)
• [jira] [Commented] (UNOMI-1001) In compatibility mode, 3.0 third-party servers lose features Serge Huber (Jira)
  • [jira] [Commented] (UNOMI-1001) In compatibility mode, 3.0 third-party servers lose features Serge Huber (Jira)
• [jira] [Created] (UNOMI-1012) Present the compatibility mode as working for Unomi 2 and Unomi 3 clients Serge Huber (Jira)
• [jira] [Updated] (UNOMI-1000) Background tasks only process the internal "system" tenant Serge Huber (Jira)
• [jira] [Created] (UNOMI-1011) The release publishes an extra build cache artifact Serge Huber (Jira)
• [jira] [Created] (UNOMI-1008) Admin requests without a tenant header do not see migrated data Serge Huber (Jira)
• [jira] [Updated] (UNOMI-1008) Admin requests without a tenant header do not see migrated data Serge Huber (Jira)
  • [jira] [Updated] (UNOMI-1008) Admin requests without a tenant header do not see migrated data Serge Huber (Jira)
• [jira] [Updated] (UNOMI-1009) The 3.0 to 4.0 migration guide misses several breaking changes Serge Huber (Jira)
• [jira] [Updated] (UNOMI-1006) All Unomi nodes share the same scheduler node id by default Serge Huber (Jira)
• [jira] [Updated] (UNOMI-1011) The release publishes an extra build cache artifact Serge Huber (Jira)
• [jira] [Updated] (UNOMI-1010) Some manual pages still describe Unomi 3.0 behaviour Serge Huber (Jira)
• [jira] [Updated] (UNOMI-1007) Health check environment variables no longer have any effect Serge Huber (Jira)
  • [jira] [Updated] (UNOMI-1007) Health check environment variables no longer have any effect Serge Huber (Jira)
• [jira] [Updated] (UNOMI-998) Migration tests do not cover an upgrade from Unomi 3.0 Serge Huber (Jira)
• [jira] [Updated] (UNOMI-1004) A hover condition with only a target id matches every hover event Serge Huber (Jira)
• [jira] [Updated] (UNOMI-1005) The web tracker and the server disagree on cookies across sites Serge Huber (Jira)
  • [jira] [Updated] (UNOMI-1005) The web tracker and the server disagree on cookies across sites Serge Huber (Jira)
• [jira] [Updated] (UNOMI-997) After migration from 3.0, some data ends up in the wrong tenant Serge Huber (Jira)
• [jira] [Updated] (UNOMI-1003) Segment and scoring lists ignore the sort, and fail with no limit Serge Huber (Jira)
• [jira] [Updated] (UNOMI-996) Migration from Unomi 3.0 stops before it finishes Serge Huber (Jira)
• [jira] [Created] (UNOMI-1010) Some manual pages still describe Unomi 3.0 behaviour Serge Huber (Jira)

• Earlier messages