Skip to content

Refactor Queues to Temporal#203

Merged
vimscientist69 merged 17 commits intodevelopfrom
william/refactor-queues-to-temporal
Feb 11, 2026
Merged

Refactor Queues to Temporal#203
vimscientist69 merged 17 commits intodevelopfrom
william/refactor-queues-to-temporal

Conversation

@vimscientist69
Copy link
Contributor

@vimscientist69 vimscientist69 commented Feb 11, 2026

Reason

Tech Details List

  1. Refactor vapor-queues commands to temporal workflows
  2. init temporal worker and client, helper to use temporal worker and client

Tasks:

Un-important tasks:

Links:

ISSUE-ISSUEID
closes/resolves #ISSUEID

Testing

Steps:

  1. Run required commands to test all the code modified by this PR
# unit tests
# integration tests
# procs / testing logic
  1. Further testing can be done by following the notes in TESTING-QA

Output:

Testing QA

… container, updated job usage to use temporal workflow

Code will not work currently. I'm going to build application, and fix all errors.
…temporal activities & workflows

Currently fixing sendable errors
it currently executes, but temporal ui doesn't work
…vice in docker-compose

It almost works, just need to fix out of memory issue when setting volume for temporal service
…istent database

using a volume for database leads to database readonly errors
…up worker as separate process, use worker host to initialize worker client and temporal client, small code enhancements
…and temporary debug code to get symbolicated stack trace in production fly.io
… steps and temporary debug code to get symbolicated stack trace in production fly.io
…x runtime + unsymbolicated stacktrace errors
@vimscientist69 vimscientist69 self-assigned this Feb 11, 2026
@vimscientist69 vimscientist69 merged commit b055014 into develop Feb 11, 2026
0 of 5 checks passed
@vimscientist69 vimscientist69 deleted the william/refactor-queues-to-temporal branch February 11, 2026 11:21
vimscientist69 added a commit that referenced this pull request Feb 11, 2026
* fix(Package): update swift tools version to v6.2, temporal as backend dependency package

* feat(docker-compose.yaml): added temporal services in docker-compose, along with configurations

* refactor(ProfilePictureAsyncJob): refactored to temporal activity and container, updated job usage to use temporal workflow

Code will not work currently. I'm going to build application, and fix all errors.

* refactor: in process of fixing all errors when refactoring queues to temporal activities & workflows

Currently fixing sendable errors

* fix: fixed all sendable errors

* fix: in process of debugging why send message temporal workflow doens't execute

* fix: fixed temporal workflows not executing

it currently executes, but temporal ui doesn't work

* fix(DebugMenu,AuthenticationServiceHelper): use new dev-port, run workflows asynchronously

* fix(docker-compose): using temporal cli to startup dev-server, as service in docker-compose

It almost works, just need to fix out of memory issue when setting volume for temporal service

* fix(docker-compose): don't use data dir, it's fine to not have a persistent database

using a volume for database leads to database readonly errors

* fix(configure.swift): refactor code, temporal worker command to startup worker as separate process, use worker host to initialize worker client and temporal client, small code enhancements

* feat: deploy temporal service, temporal worker refactor, debug steps and temporary debug code to get symbolicated stack trace in production fly.io

* fix(ApplicationExtensions): use hostname, not static string for instrumentation hostname temporal client

* fixup! feat: deploy temporal service, temporal worker refactor, debug steps and temporary debug code to get symbolicated stack trace in production fly.io

* fix(Dockerfile): use old develop dockerfile

* fix(Package.swift): update temporal-swift-sdk, new verions fixes linux runtime + unsymbolicated stacktrace errors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant