The bare /.well-known/jwks form is only answered by the hanzo.id-worker
shim, which is being retired; IAM's discovery document advertises
/v1/iam/.well-known/jwks on both the public host and in-cluster.
The embedded UI in tasksd is now the @hanzo/gui Tamagui build from
~/work/hanzo/gui/code/admin-tasks/. v1 React/shadcn deleted.
What's still here:
ui/embed.go — Go //go:embed wrapper (handler unchanged)
ui/dist/ — synced from admin-tasks build output
ui/README.md — explains the bundle is built externally
scripts/sync-admin-ui.sh — copies admin-tasks/dist → ui/dist + stamp
Makefile — `ui` target now calls the sync script
Dockerfile — drops the node ui-build stage; expects pre-built
dist/ in the repo or built upstream via CI
What's deleted (62 files):
ui/{src,public,node_modules}/ entire trees
ui/{package.json, vite.config.ts, tailwind.config.js, postcss.config.js,
tsconfig.json, index.html, PERF.md, .gitignore, pnpm-lock.yaml,
vite.perf2.config.ts, tsconfig.tsbuildinfo}
UI-TAMAGUI-MOVED.md (no longer accurate)
Live bundle (verified curl http://127.0.0.1:7243/):
/_/tasks/ → 200
/_/tasks/assets/index-BKuZ1al1.js → 200, 674,748 bytes
/_/tasks/assets/index-DTXHKKx4.css → 200, 9,104 bytes
/v1/tasks/namespaces → 200
Bundle: 339 KB → 675 KB raw / 104 KB → 199 KB gzip. Larger because
Tamagui ships react-native-web + Tamagui core + theme primitives
that shadcn doesn't. Trade: design-system consistency across all
Hanzo admin UIs (kms, commerce, console, etc.) vs 95 KB gzip.
CI note: .github/workflows/build.yml's docker build needs a pre-step
that checks out hanzo/gui and builds admin-tasks, OR commits ui/dist/
to this repo. Dockerfile fails fast with a clear message until then.
Tag v3.0.0 because this is a meaningful UI architecture change.
Change all cadence references to temporal references throughout
source code and documentation.
Change docker entry point to tctl as we renamed it from temporal
to tctl.
Update mysql user login info.
* Buildkite integration to run integration tests with code coverage
* update docker-compose plugin version to v3.1.0
* remove SSH_AUTH_SOCK volume mapping
* remove git config remap to use https again
* comment out cover files for XDC tests
* Rename IDL files to move then under temporalio/temporal
* Rename ProjectRoot in makefile represent new repository
* Update go.mod to represent new repository
* Update all imports to temporalio/temporal package
* Fix tests to work after renaming
* increase test timeout to 40 minutes in makefile
* parallelize travis builds
* fix condition to start tests
* Parallelize travis builds for Cadence
Split Cadence build into three separate parts.
1) Unit: This runs unit test for all packages
2) Integration: This runs integration tests under host
3) XDC: This runs cross dc specific integration tests under hostxdc
Also split test initialization to only setup sql for unit tests and
Kafka for xdc tests.
* Retry timer task incase of continuous update failures.
* Add schema to store next_event_id and state in the mutable state.
* Update MS state to get Next Event ID/State.
* Update History Engine API to do mutable state check
* Update TimerQ Processor to user Mutable state check
* Update workflow execution context to set next event ID and state.
* CR Comments.
* TimerProcessor Test: Split Activity timeouts into multiple tests.
* Turn the verbose -> Debug log in TimerQ Processor.
* Updating scripts to point to cadence_staging_dca1a
* Data Layer: Merge mutable state in to execution state
* Change decision start-to-close timeout to int32.
* Mutable state: Flatten decision info into execution info.
* CR Comments: remove the test code in timerQ processor.
* Remove decision_pending from schema.
* CR Comments Schema Naming: Remove last_ from decision, start_to_close from decision timeout
* Creating workflow to set decision start request ID to empty.
* Thrift changes for cancel timer.
* Scripts to refer to local cassandra.
* Add CancelTimer to RespondDecisionTaskComplete
* Update integration test to run setup once.
* CR comments.
Summary:
ShardController implementation as a daemon started for each history
service host. Basic implementation of shard controller relies entirely
on ring pop for shard distribution.
Added mocks for HistoryEngine, HistoryEngineFactory, ShardManager and
ServiceResolver for unit testing of shard controller.
Reviewers: sivakk, tamer, maxim
Reviewed By: tamer, maxim
Subscribers: jenkins, aravindv, venkat
Differential Revision: https://code.uberinternal.com/D716912
Summary:
Add support for running tests on jenkins
Added more reselient setup scripts which also allow us to run test on
jenkins.
Added .jenkins folder to allow running test on jenkins for every
check-in.
Reviewers: tamer
Reviewed By: tamer
Subscribers: aravindv, venkat
Differential Revision: https://code.uberinternal.com/D697074
zeekay
