Skip to content

fix: don't require a commit hash file in dev runs #486

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 29, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions src/lib/flush-redis-cache.ts
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,13 @@ export async function flushRedisCache () {
const filePath = path.join(path.resolve(), 'data/LAST_API_COMMIT_HASH.txt');

const lastCommitHashInRedis = await persistentRedis.get(`LAST_API_COMMIT_HASH_${hostname}`);
const currentLastCommitHash = (await readFile(filePath, 'utf8')).trim();
const currentLastCommitHash = (await readFile(filePath, 'utf8').catch(() => '')).trim();

if (lastCommitHashInRedis !== currentLastCommitHash) {
if (process.env['NODE_ENV'] === 'production' && !currentLastCommitHash) {
throw new Error(`Current commit hash missing in ${filePath}`);
}

if (!currentLastCommitHash || lastCommitHashInRedis !== currentLastCommitHash) {
logger.info('Latest commit hash changed. Clearing redis cache.');
await redis.flushDb();
await persistentRedis.set(`LAST_API_COMMIT_HASH_${hostname}`, currentLastCommitHash);
Expand Down