Skip to content
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

Default data backend #2062

Open
fnikolai opened this issue May 17, 2024 · 3 comments
Open

Default data backend #2062

fnikolai opened this issue May 17, 2024 · 3 comments
Labels
🐛 bug Something isn't working

Comments

@fnikolai
Copy link
Collaborator

I 'm trying to run superduper without any configuration, but it fails:

2024-May-17 00:16:19.96| ERROR    | 8caba5037a98| superduperdb.base.build:72   | Error initializing to DataBackend Client: localhost:27017: [Errno 111] Connection refused (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms), Timeout: 5.0s, Topology Description: <TopologyDescription id: 6646a1ceb8de3de22757623b, topology_type: Unknown, servers: [<ServerDescription ('localhost', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('localhost:27017: [Errno 111] Connection refused (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>]>

The problem is that is trying to connect to a local mongo database. Why don't we have the mongomock as default ?

@jieguangzhou
Copy link
Collaborator

I think we can use mongomock as the default, and print a warning message to the user

@blythed
Copy link
Collaborator

blythed commented May 17, 2024

@fnikolai traceback please.

@fnikolai
Copy link
Collaborator Author

>> cat testme.py 
from superduperdb import superduper
db = superduper()

fnikol@moumia  ( ~/Workspace/projects/superduper/superduperdb )[Mon May 20 17:37:20]  
>> python testme.py 
2024-May-20 17:38:03.36| ERROR    | moumia  | superduperdb.base.build:72   | Error initializing to DataBackend Client: localhost:27017: [Errno 
111] Connection refused (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms), Timeout: 5.0s, Topology Description: <T
opologyDescription id: 664b60461c878e393021f50e, topology_type: Unknown, servers: [<ServerDescription ('localhost', 27017) server_type: Unknown
, rtt: None, error=AutoReconnect('localhost:27017: [Errno 111] Connection refused (configured timeouts: socketTimeoutMS: 20000.0ms, connectTime
outMS: 20000.0ms)')>]>

@fnikolai fnikolai changed the title [BUG] Default data backend [BUGS-0.2.0] Default data backend May 21, 2024
@fnikolai fnikolai mentioned this issue May 21, 2024
14 tasks
@fnikolai fnikolai added the 🐛 bug Something isn't working label May 21, 2024
@blythed blythed changed the title [BUGS-0.2.0] Default data backend Default data backend May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants