Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / pharo-nosql/voyage issues and pull requests
#51 - Remove unqlite from the baseline as wellThe unqlite support has bee…
Pull Request -
State: closed - Opened by zecke over 8 years ago
- 1 comment
#51 - Remove unqlite from the baseline as wellThe unqlite support has bee…
Pull Request -
State: closed - Opened by zecke over 8 years ago
- 1 comment
#50 - ciclic references cause duplicated objects when save
Issue -
State: closed - Opened by estebanlm over 8 years ago
- 3 comments
Labels: bug
#50 - ciclic references cause duplicated objects when save
Issue -
State: closed - Opened by estebanlm over 8 years ago
- 3 comments
Labels: bug
#49 - How do VORepository>>commit: and VORepository>>root:commit: differ from VORepository>>save:?
Issue -
State: closed - Opened by dalehenrich over 8 years ago
- 4 comments
Labels: question
#49 - How do VORepository>>commit: and VORepository>>root:commit: differ from VORepository>>save:?
Issue -
State: closed - Opened by dalehenrich over 8 years ago
- 4 comments
Labels: question
#48 - >>#selectAny: and difference of VOMemoryRepository and VOMongoRepository
Issue -
State: closed - Opened by zecke over 8 years ago
- 8 comments
Labels: question
#48 - >>#selectAny: and difference of VOMemoryRepository and VOMongoRepository
Issue -
State: closed - Opened by zecke over 8 years ago
- 8 comments
Labels: question
#47 - Introduce VOMongoExecuteStrategy
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
- 9 comments
#47 - Introduce VOMongoExecuteStrategy
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
- 9 comments
#46 - Removing forceEager option (VOMongoRepository)
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
- 3 comments
#46 - Removing forceEager option (VOMongoRepository)
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
- 3 comments
#45 - Replica set support (version 2)
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
- 10 comments
#45 - Replica set support (version 2)
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
- 10 comments
#44 - move #testSelectManyWithAllKeyword to VOMongoTest
Issue -
State: closed - Opened by estebanlm over 8 years ago
- 3 comments
#44 - move #testSelectManyWithAllKeyword to VOMongoTest
Issue -
State: closed - Opened by estebanlm over 8 years ago
- 3 comments
#43 - `github://pharo-nosql/mongotalk:1.?/mc` cannot be used in older versions of Pharo without updating Metacello
Issue -
State: closed - Opened by dalehenrich over 8 years ago
- 3 comments
#43 - `github://pharo-nosql/mongotalk:1.?/mc` cannot be used in older versions of Pharo without updating Metacello
Issue -
State: closed - Opened by dalehenrich over 8 years ago
- 3 comments
#42 - Rename BaselineOfVoyageMongo to BaselineOfVoyage
Issue -
State: closed - Opened by estebanlm over 8 years ago
- 5 comments
Labels: enhancement
#42 - Rename BaselineOfVoyageMongo to BaselineOfVoyage
Issue -
State: closed - Opened by estebanlm over 8 years ago
- 5 comments
Labels: enhancement
#41 - changed dependency of Magritte3 to load only Core group
Pull Request -
State: closed - Opened by noha over 8 years ago
#41 - changed dependency of Magritte3 to load only Core group
Pull Request -
State: closed - Opened by noha over 8 years ago
#40 - changed dependency of Magritte3 to load only Core group
Pull Request -
State: closed - Opened by noha over 8 years ago
#40 - changed dependency of Magritte3 to load only Core group
Pull Request -
State: closed - Opened by noha over 8 years ago
#39 - BaselineOf should only load Magritte3 Core
Issue -
State: closed - Opened by noha over 8 years ago
- 1 comment
#39 - BaselineOf should only load Magritte3 Core
Issue -
State: closed - Opened by noha over 8 years ago
- 1 comment
#38 - Replica set support
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
#38 - Replica set support
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
#37 - Improvement in VOMongoRepository>>printOn:
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
#37 - Improvement in VOMongoRepository>>printOn:
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
#36 - Improve printOn: (e.g. to ease debugging)
Issue -
State: closed - Opened by tinchodias over 8 years ago
- 1 comment
#36 - Improve printOn: (e.g. to ease debugging)
Issue -
State: closed - Opened by tinchodias over 8 years ago
- 1 comment
#35 - Fix instance creation method in VOMongoRepository
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
#35 - Fix instance creation method in VOMongoRepository
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
#34 - Do not catch all errors in VOMongoSessionPool since it causes infine loop with resolver
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
- 1 comment
#34 - Do not catch all errors in VOMongoSessionPool since it causes infine loop with resolver
Pull Request -
State: closed - Opened by tinchodias over 8 years ago
- 1 comment
#33 - Can't instantiate a VOMongoRepository with custom port
Issue -
State: closed - Opened by tinchodias over 8 years ago
- 1 comment
#33 - Can't instantiate a VOMongoRepository with custom port
Issue -
State: closed - Opened by tinchodias over 8 years ago
- 1 comment
#32 - Issue #30: invert VORepositoryTest/VOMongoTest hierarcy
Pull Request -
State: closed - Opened by dalehenrich almost 9 years ago
- 1 comment
#32 - Issue #30: invert VORepositoryTest/VOMongoTest hierarcy
Pull Request -
State: closed - Opened by dalehenrich almost 9 years ago
- 1 comment
#31 - Infinite VOMongoConnectionError resignal loop
Issue -
State: closed - Opened by dalehenrich almost 9 years ago
- 2 comments
#31 - Infinite VOMongoConnectionError resignal loop
Issue -
State: closed - Opened by dalehenrich almost 9 years ago
- 2 comments
#30 - Inverted class hierarchy? VOMongoTest is superclass of VORepositoryTest
Issue -
State: closed - Opened by dalehenrich almost 9 years ago
- 5 comments
#30 - Inverted class hierarchy? VOMongoTest is superclass of VORepositoryTest
Issue -
State: closed - Opened by dalehenrich almost 9 years ago
- 5 comments
#29 - convert to use smalltalkCI
Pull Request -
State: closed - Opened by dalehenrich almost 9 years ago
#29 - convert to use smalltalkCI
Pull Request -
State: closed - Opened by dalehenrich almost 9 years ago
#28 - Add replication support
Issue -
State: closed - Opened by tinchodias almost 9 years ago
- 7 comments
#27 - backport to 1.3.1 fix to #removeValue:
Issue -
State: closed - Opened by estebanlm almost 9 years ago
- 1 comment
#26 - VOMongoCache compaction occurs too late
Issue -
State: closed - Opened by zecke almost 9 years ago
- 4 comments
#25 - Concurrency issue with cached MongoCollections
Issue -
State: closed - Opened by zecke almost 9 years ago
- 6 comments
#24 - Merged with Holger's commits at Smalltalkhub, which uses strategy design pattern
Pull Request -
State: closed - Opened by tinchodias almost 9 years ago
- 3 comments
#23 - Now it's possible to specify a version generator.
Pull Request -
State: closed - Opened by tinchodias almost 9 years ago
- 3 comments
#22 - Run Mongo tests in Voyage travis
Issue -
State: closed - Opened by tinchodias almost 9 years ago
- 12 comments
#21 - Added VOMongoRepository>>onlyUpdateIfCurrent: option
Pull Request -
State: closed - Opened by tinchodias almost 9 years ago
- 52 comments
#20 - Improve workaround in VOMongoTest>>tearDown
Pull Request -
State: closed - Opened by tinchodias almost 9 years ago
#19 - Workaround in VOMongoTest>>tearDown is slow and leaks open sockets
Issue -
State: closed - Opened by tinchodias almost 9 years ago
- 1 comment
#18 - In collectionAt:inDatabase:, replace addCollection: by getCollection:
Pull Request -
State: closed - Opened by tinchodias almost 9 years ago
- 5 comments
#17 - forceEager has no effect
Issue -
State: closed - Opened by tinchodias almost 9 years ago
- 1 comment
Labels: enhancement
#16 - Optimize VOMongoRepositoryResolver>>newVersion
Issue -
State: closed - Opened by tinchodias almost 9 years ago
- 6 comments
#15 - Update if current
Issue -
State: closed - Opened by tinchodias almost 9 years ago
- 4 comments
Labels: enhancement
#14 - Test Runner on VORepositoryTest hangs with MongoTalk 1.9.1 (released some days ago)
Issue -
State: closed - Opened by tinchodias almost 9 years ago
- 16 comments
#13 - Indirectly referenced objects are not automatically updated
Issue -
State: closed - Opened by tinchodias almost 9 years ago
- 8 comments
#12 - Workaround to randomly failing tests: dropDatabase after each test run
Pull Request -
State: closed - Opened by tinchodias almost 9 years ago
- 7 comments
#11 - Extension methods in TimeStamp raise warnings when loading in Pharo 5.0
Issue -
State: closed - Opened by tinchodias almost 9 years ago
- 8 comments
Labels: bug
#10 - Circular dependency between Voyage-Mongo-Core and Voyage-Mongo-Magritte
Issue -
State: closed - Opened by tinchodias almost 9 years ago
- 1 comment
#9 - Unit tests don't release or close open connections.
Issue -
State: closed - Opened by ironirc almost 9 years ago
- 4 comments
#8 - Tests randomly fail when they are not run in isolation
Issue -
State: closed - Opened by tinchodias almost 9 years ago
- 4 comments
Labels: bug
#7 - Update README.md
Pull Request -
State: closed - Opened by tinchodias almost 9 years ago
#6 - OID does not create correct ids
Issue -
State: closed - Opened by estebanlm over 9 years ago
- 13 comments
Labels: bug
#5 - Infinite loop when VOMongoConnectionError
Issue -
State: closed - Opened by estebanlm over 9 years ago
- 11 comments
Labels: bug
#4 - WeakKeyDictionary in cache (for reversedObjects) might be buggy
Issue -
State: closed - Opened by estebanlm over 9 years ago
- 2 comments
Labels: bug
#3 - Creation of Repository failed
Issue -
State: closed - Opened by mkemper over 9 years ago
- 6 comments
#2 - MemoryRepository does not save voyageRoots contained in another voyageRoot
Issue -
State: closed - Opened by demarey over 9 years ago
- 1 comment
Labels: bug
#1 - save not nesting roots correctly?
Issue -
State: closed - Opened by estebanlm almost 10 years ago
- 2 comments
Labels: bug