How can I make a MongoDB setup reproducible?
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
ReadMeFeed / Community knowledge
Models, data engineering, retrieval, analytics and databases.
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
I am trying to add a generated column to an existing table with this script. alter table Asset_Store add column md5_hash VARCHAR(100) GENERATED ALWAYS AS (CAST(UPPER( case when OR_ID is not null then MD5(cast(OR_ID as varchar(100))) when Asset_ID is not null then MD5(Asset_ID) else null end ) as VARCHAR(100))) STORED ; but I am getting an error: SQL Error [4
I want to call my Python module from the Matlab. I received the error: Error using numpy_ops>init thinc.backends.numpy_ops Python Error: ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject. The Python script is as follows import spacy def text_recognizer(model_path, text): try: # Load
The new pip dependency resolver that was released with version 20.3 takes an inappropriately long time to install a package. On our CI pipeline yesterday, a docker build that used to take ~10 minutes timed out after 1h of pip installation messages like this (almost for every library that is installed by any dependency there is a similar log output): INFO: pi
I am trying to run a Django project with Postgres database. I use Postgres 13.4 installed via postgressapp (UNIVERSAL with all currently supported versions) and python 3.9 (in venv). I work on Mac with Apple M1 chip, macOS Big Sur. I faced the following well-known problem: django.core.exceptions.ImproperlyConfigured: Error loading psycopg2 module: dlopen(/Us
As we all know, the pythonic way to swap the values of two items a and b is a, b = b, a and it should be equivalent to b, a = a, b However, today when I was working on some code, I accidentally found that the following two swaps give different results: nums = [1, 2, 4, 3] i = 2 nums[i], nums[nums[i]-1] = nums[nums[i]-1], nums[i] print(nums) # [1, 2, 4, 3] nu
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
Upon rebuilding my Postgresql database from a dump file using pg_restore , my schema file db/schema.rb is now prefixing the gen_random_uuid() function with public . create_table "cars", id: :uuid, default: -> { "public.gen_random_uuid()" } How can I prevent from the schema file from prefixing method calls with public ?
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
answered · 26 Jan 2025, 00:43 UTC