Small /tmp Partition Can Silently Derail GBase 8s Database Installation

·1 views

A GBase 8s database installation can fail with a 'disk full' error even when the target directory has ample free space, because the installer uses the /tmp filesystem for temporary file extraction. The misleading error occurs because /tmp is often backed by a small or tmpfs-limited partition separate from the main disk. Inode exhaustion on /tmp can trigger the same error even when disk capacity appears available, making it a less obvious culprit. To work around insufficient /tmp space, administrators can redirect the temporary directory by setting the TMPDIR environment variable to a larger partition before running the installer. Running pre-installation checks on /tmp disk space, inode availability, and required dependencies can help catch these issues before deployment begins.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Flutter Developer Builds Stutter-Free 1080p Google Drive Video Player for Budget Android TVs

A developer has built a Flutter-based Android TV app called Cloud Dock TV that streams 1080p Google Drive video smoothly on low-end hardware. To avoid the cumbersome D-pad keyboard login, authentication is handled on a paired mobile device via Google Sign-In, with a 6-digit PIN used to hand off read-only stream tokens to the TV through Firebase in under 3.2 seconds. Micro-stutters caused by widget rebuilds were eliminated by keeping the native video surface static and isolating UI overlay redraws using Flutter's RepaintBoundary. Video is standardised to H.264/AAC MP4 at 1080p 30 FPS with a 5–8 Mbps bitrate cap, keeping CPU load below 12% on budget devices. The app is currently available for closed testing on the Google Play Store.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

OpenAI Responses API Does Not Persist Instructions Across Chained Turns

OpenAI's Responses API allows developers to chain conversation turns using a previous_response_id field, but this mechanism carries forward only conversation state, not top-level instructions. This means output format rules, tool constraints, or safety policies set in an earlier turn are silently absent in follow-up requests unless explicitly repeated. A developer writing for DEV Community highlighted this counterintuitive boundary and demonstrated how accidental omission can cause an application to respond outside its expected policy contract. To address this, the author built a request constructor that enforces non-empty instructions on every policy-bound turn and rejects conflicting state fields at the application level. The approach treats instruction repetition as an application invariant rather than an API requirement, making policy enforcement explicit and deliberate across all turns.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Get Your Content Cited by ChatGPT, Perplexity, and Gemini

A digital content strategist outlines how AI-powered search tools like ChatGPT, Perplexity, and Gemini are reshaping web visibility by replacing traditional clicks with in-answer citations. Businesses with strong Google rankings are seeing traffic decline because users increasingly get answers directly from AI without visiting any website. All four major AI search systems follow a similar process: fetching candidate pages, extracting directly answerable content, and citing the most relevant source. To be cited, content must be easily crawlable, authored by a named individual, and structured so that key answers appear near the top of the page in standalone sentences. Each platform has distinct preferences — ChatGPT favors server-rendered pages with visible bylines, while Perplexity prioritises freshness and evidence-style writing.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Snowflake Cortex Runs Generative AI Directly Inside SQL Queries

Snowflake Cortex allows developers to run generative AI models as native SQL functions, executing once per row within standard SELECT statements alongside WHERE, JOIN, and GROUP BY clauses. Key functions include AI_COMPLETE for general text generation, AI_CLASSIFY for categorizing free text into custom labels, AI_FILTER for natural-language row filtering, and AI_AGG for summarizing entire columns without context-window chunking. Access requires granting the SNOWFLAKE.CORTEX_USER database role to a purpose-built role via ACCOUNTADMIN, and AI workloads should run on a dedicated warehouse to keep credit consumption visible and controllable. Costs accrue on two dimensions: warehouse credits for query execution and token-based billing for each model call, making row-level testing with LIMIT essential before scaling to large tables. Developers should note that older syntax such as SNOWFLAKE.CORTEX.COMPLETE and CLASSIFY_TEXT has been superseded by updated equivalents like AI_COMPLETE and AI_CLASSIFY in current Snowflake releases.

0 comments Read more at DEV Community