nxtgauge-backend-rust

History

Ashwin Kumar Sivakumar 1af10420ce Some checks failed build-and-release / build (cron) (push) Successful in 57s Details build-and-release / build (customers) (push) Successful in 1m54s Details build-and-release / build (employees) (push) Successful in 2m11s Details build-and-release / build (companies) (push) Successful in 2m27s Details build-and-release / build (catering-services) (push) Successful in 2m28s Details build-and-release / build (gateway) (push) Successful in 48s Details build-and-release / build (developers) (push) Successful in 3m3s Details build-and-release / build (jobs) (push) Successful in 43s Details build-and-release / build (fitness-trainers) (push) Successful in 2m36s Details build-and-release / build (makeup-artists) (push) Successful in 1m45s Details build-and-release / build (graphic-designers) (push) Successful in 2m38s Details build-and-release / build (job-seekers) (push) Successful in 2m28s Details build-and-release / build (photographers) (push) Successful in 2m34s Details build-and-release / build (social-media-managers) (push) Successful in 2m34s Details build-and-release / build (payments) (push) Successful in 3m20s Details backend-integration-tests / ai-credits (push) Failing after 44s Details build-and-release / build (tutors) (push) Successful in 2m41s Details build-and-release / build (video-editors) (push) Has been cancelled Details build-and-release / build (users) (push) Has been cancelled Details build-and-release / build (ugc-content-creators) (push) Successful in 2m41s Details fix(db): convert ai_credits timestamp columns to TIMESTAMPTZ 9 columns across ai_plans/user_ai_subscriptions/ai_feature_costs/ ai_usage_logs were TIMESTAMP (no timezone), left over from whatever pre-20260703210000 mechanism originally created these 4 tables, but crates/db/src/models/ai_credits.rs maps all of them to DateTime<Utc>, which sqlx requires TIMESTAMPTZ for. This is a live bug, not just a test-setup gap - discovered via crates/db/tests/ai_credits.rs failing with ColumnDecode errors, but any production code path selecting these columns (e.g. current_period_start/end on every wallet read) would hit the same failure. ALTER COLUMN ... USING col AT TIME ZONE 'UTC' is lossless here since every write path uses NOW()/DEFAULT NOW() with no other timezone handling anywhere in the codebase. Applied to both nxtgauge_test and the live nxtgauge database directly; verified all 9 columns converted and the 3 existing user_ai_subscriptions + 4 ai_plans rows' values are intact and correctly interpreted as UTC afterward. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>		2026-08-13 21:44:30 +05:30
..
auth	fix payments runtime and jwt backend	2026-06-09 22:52:30 +02:00
cache	Fix security audit findings: admin authz, captcha, secret leak, CORS	2026-07-23 17:31:48 +05:30
contracts	fix: security, wallet holds, printpdf upgrade	2026-08-12 13:38:17 +02:00
db	fix(db): convert ai_credits timestamp columns to TIMESTAMPTZ	2026-08-13 21:44:30 +05:30
db-migrate	feat(db): update service handlers and models for new schema	2026-04-13 00:29:44 +02:00
email	Update backend services: catering_services, companies, developers, gateway, job_seekers, photographers, social_media_managers, tutors, ugc_content_creators, users; update cache (otp, token), contracts (profession_shared, profession_state), db (job_seeker, verification), email; add revision-requested email template; update init-db.sql and start-services.sh	2026-05-08 15:34:29 +02:00
invoice	feat: generate a GST invoice automatically after a successful Tracecoin/PayU purchase	2026-07-21 03:02:47 +05:30
storage	Add presigned document URLs to stop leaking permanent Backblaze links	2026-07-27 18:07:15 +05:30
wallet	feat: profile photo upload, PDF resume generation, AI auto-apply, schema fixes	2026-07-02 13:31:06 +02:00