Help Needed, My Piccolo Isn’t Working

[Monsoon-Song]

Description

Help Needed, My Piccolo Isn’t Working

System Environment: Ubuntu 22.04.5

Issue:
I’ve followed the steps in the README.md for setting up Piccolo, but it’s not working. The symptoms are:

Browser Displays a Blank White Screen with a “Not Secure” Warning
When I access the application through the browser, I see a blank white screen and a message indicating that the connection is “Not Secure.”
Docker Error: django.db.migrations.exceptions.NodeNotFoundError
The Docker logs show the following error:
django.db.migrations.exceptions.NodeNotFoundError
sensiml.databse.initalize-1 | Loading ENV from /home/sml-app/install/config/env/.env.docker
sensiml.databse.initalize-1 | DOCKER HOST SML DATAT DIR
sensiml.databse.initalize-1 | [‘*’]
sensiml.databse.initalize-1 | 2025-02-08 08:41:17.638972: E tensorflow/stream_executor/cuda/cuda_blas.cc:2981] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
sensiml.databse.initalize-1 | Traceback (most recent call last):
sensiml.databse.initalize-1 | File “/home/sml-app/install/server/manage.py”, line 30, in
sensiml.databse.initalize-1 | execute_from_command_line(sys.argv)
sensiml.databse.initalize-1 | File “/usr/local/lib/python3.10/site-packages/django/core/management/init.py”, line 419, in execute_from_command_line
sensiml.databse.initalize-1 | utility.execute()
sensiml.databse.initalize-1 | File “/usr/local/lib/python3.10/site-packages/django/core/management/init.py”, line 413, in execute
sensiml.databse.initalize-1 | self.fetch_command(subcommand).run_from_argv(self.argv)
sensiml.databse.initalize-1 | File “/usr/local/lib/python3.10/site-packages/django/core/management/base.py”, line 354, in run_from_argv
sensiml.databse.initalize-1 | self.execute(*args, **cmd_options)
sensiml.databse.initalize-1 | File “/usr/local/lib/python3.10/site-packages/django/core/management/base.py”, line 398, in execute
sensiml.databse.initalize-1 | output = self.handle(*args, **options)
sensiml.databse.initalize-1 | File “/usr/local/lib/python3.10/site-packages/django/core/management/base.py”, line 89, in wrapped
sensiml.databse.initalize-1 | res = handle_func(*args, **kwargs)
sensiml.databse.initalize-1 | File “/usr/local/lib/python3.10/site-packages/django/core/management/commands/migrate.py”, line 92, in handle
sensiml.databse.initalize-1 | executor = MigrationExecutor(connection, self.migration_progress_callback)
sensiml.databse.initalize-1 | File “/usr/local/lib/python3.10/site-packages/django/db/migrations/executor.py”, line 18, in init
sensiml.databse.initalize-1 | self.loader = MigrationLoader(self.connection)
sensiml.databse.initalize-1 | File “/usr/local/lib/python3.10/site-packages/django/db/migrations/loader.py”, line 53, in init
sensiml.databse.initalize-1 | self.build_graph()
sensiml.databse.initalize-1 | File “/usr/local/lib/python3.10/site-packages/django/db/migrations/loader.py”, line 259, in build_graph
sensiml.databse.initalize-1 | self.graph.validate_consistency()
sensiml.databse.initalize-1 | File “/usr/local/lib/python3.10/site-packages/django/db/migrations/graph.py”, line 195, in validate_consistency
sensiml.databse.initalize-1 | [n.raise_error() for n in self.node_map.values() if isinstance(n, DummyNode)]
sensiml.databse.initalize-1 | File “/usr/local/lib/python3.10/site-packages/django/db/migrations/graph.py”, line 195, in
sensiml.databse.initalize-1 | [n.raise_error() for n in self.node_map.values() if isinstance(n, DummyNode)]
sensiml.databse.initalize-1 | File “/usr/local/lib/python3.10/site-packages/django/db/migrations/graph.py”, line 58, in raise_error
sensiml.databse.initalize-1 | raise NodeNotFoundError(self.error_message, self.key, origin=self.origin)
sensiml.databse.initalize-1 | django.db.migrations.exceptions.NodeNotFoundError: Migration datamanager.0005_lock_schema dependencies reference nonexistent parent node (‘datamanager’, ‘0004_label_info’)

sudo docker info

Client: Docker Engine - Community
Version: 27.5.1
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.20.0
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.32.4
Path: /usr/libexec/docker/cli-plugins/docker-compose

Server:
Containers: 8
Running: 6
Paused: 0
Stopped: 2
Images: 7
Server Version: 27.5.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
runc version: v1.2.4-0-g6c52b3f
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.8.0-52-generic
Operating System: Ubuntu 22.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 27.29GiB
Name: mn-AMD
ID: 4d83298a-cab3-415b-8d80-36b038eb27bf
Docker Root Dir: /home/mn/working/docker-utu
Debug Mode: false
HTTP Proxy: http://10.10.10.23:7890/
HTTPS Proxy: http://10.10.10.23:7890/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

Reproduction steps

Following the project README steps, but an error occurs when running docker-compose up

Current behavior

Cannot open the Piccolo page, and Docker outputs the following error message: django.db.migrations.exceptions.NodeNotFoundError: Migration datamanager.0005_lock_schema dependencies reference nonexistent parent node ('datamanager', '0004_label_info')

Expected behavior

Can log in and use Piccolo normally.

Additional context and Screenshots

No response

[Monsoon-Song]

After reviewing the code, I found that the file is indeed missing.

ls src/server/datamanager/migrations/
0001_initial.py 0002_alter_knowledgepack_options.py 0003_add_crosstab_tablefunc.py 0005_lock_schema.py init.py pycache

[mkaliberda]

Hi @Monsoon-Song
Thank you for reporting this issue!
I'll take a look