mirror
/
tile38
mirror of https://github.com/tidwall/tile38.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
1,392 Commits 14 Branches 101 Tags 54 MiB
Commit Graph

1392 Commits

Author SHA1 Message Date
tidwall d211858db6 1.22.6 2021-02-07 18:07:24 -07:00
tidwall 72dfaaec63 Updated dependencies 2021-02-07 17:54:56 -07:00
tidwall 4f8bc0531e Updated rtree library 2021-02-04 09:50:13 -07:00
tidwall b37e7395a3 Updated rtree library 2021-02-04 08:21:08 -07:00
tidwall 3ed048242e Various updates 
- Updated all dependencies
- Updated geoindex Box api
 2021-02-03 14:30:55 -07:00
tidwall 263bbd9dcc Updated packages 2021-01-25 15:11:55 -07:00
tidwall 016f397124 Replace tinybtree 2021-01-25 14:34:40 -07:00
tidwall 6736aef801 Revert logo 2020-12-12 15:50:43 -07:00
tidwall 0a9103aaf7 Add light/dark logos 2020-12-12 15:33:57 -07:00
tidwall b8ba0e2214 Add safe border around logo 2020-12-12 15:30:34 -07:00
tidwall 5b37cb3045 Vector logo with dark mode 2020-12-12 14:52:20 -07:00
Josh Baker fe66c9189b
Update config.yml 2020-12-05 07:23:29 -07:00
Josh Baker 24b0499cf9
Create config.yml 2020-12-05 07:22:52 -07:00
Josh Baker c17959d96d
Update README.md 
Update slack link
 2020-11-30 16:05:11 -07:00
tidwall 6092f734e3 Better handle connection errors in tile38-cli 
This commit fixes an issue with the tile38-cli where it will
continually print "Could not connect to Tile38..." when it was
unable to connect to the tile38-server.

It now cleanly prints the message only once.
 2020-11-24 10:27:07 -07:00
tidwall 6c653ab268 1.22.5 2020-11-09 14:47:46 -07:00
tidwall 9ce20331e4 Fixed fields being shuffled after AOFSHRINK 2020-11-09 14:45:40 -07:00
tidwall dd53091be1 1.22.4 2020-11-07 05:30:23 -07:00
tidwall 1a7d8d6431 Added ENV var for 500 http errors 2020-11-07 05:22:11 -07:00
Josh Baker 5e03207a8a
Merge pull request #585 from tidwall/fix-fences-test 
enable fence tests
 2020-11-03 15:51:40 -07:00
tidwall 4f4954020f enable fence tests 2020-11-03 14:56:31 -07:00
tidwall 4504ea75ac Updated Github Action files 
Disabled some fence tests due to them hanging and
timing out in the Github Actions workflow, which is
something that did not happen with Travis CI.

I suspect that there's something up with Go routines
and or num of CPUs in the GH virtual environment.

Tests pass locally though
 2020-11-03 14:36:07 -07:00
Josh Baker 201d0b5821
Update go.yml 2020-11-03 13:15:08 -07:00
Josh Baker 1fae26d657
Update go.yml 2020-11-03 12:35:03 -07:00
Josh Baker c56f08b935
Update go.yml 2020-11-03 12:28:57 -07:00
Josh Baker ac67755764
Create go.yml 2020-11-03 12:27:45 -07:00
Josh Baker 927f61033f
Delete .travis.yml 2020-11-03 12:25:17 -07:00
Josh Baker 69ecc04928
Update README.md 2020-11-03 12:24:51 -07:00
tidwall 982980789b 1.22.3 2020-10-28 08:46:45 -07:00
tidwall 79bee8523b Updated btree deps 2020-10-27 15:29:50 -07:00
tidwall 9998e03f6f Optimization for non-cross geofence detection 
This commit fixes a performance issue with the algorithm that
determines with geofences are potential candidates for
notifications following a SET operation.

Details

Prior to commit b471873 (10 commits ago) there was a bug where
the "cross" detection was not firing in all cases. This happened
because when looking for candidates for "cross" due to a SET
operation, only the geofences that overlapped the previous
position of the object and the geofences that overlapped the new
position where searched. But, in fac, all of the geofences that
overlapped the union rectangle of the old and new position should
have been searched.

That commit fixed the problem by searching a union rect of the
old and new positions. While this is an accurate solution, it
caused a slowdown on systems that have big/wild position changes
that might cross a huge number of geofences, even when those
geofences did not need actually need "cross" detection.

The fix

With this commit the geofences that have a "cross" detection
are stored in a seperated tree from those that do not. This
allows for a hybrid of the functionality prior and post b471873.

Fixes #583
 2020-10-23 09:51:27 -07:00
tidwall 100be7be3c Added tests 2020-10-23 09:50:51 -07:00
tidwall 5b77c446a7 1.22.2 2020-10-07 10:12:47 -07:00
tidwall 93e3a067b7 Truncate trailing zeros from AOF at startup 
This commit addresses issue #230, where an AOF file will sometimes
not load due to the file being padded with trailing zeros. It's
uncertain what is causing this corruption, but it appears to be
coming from outside of the tile38-server process. I suspect it's
due to some block store layer in Kubernetes/Docker cloud
environments.

This fix allows for Tile38 to start up by discovering the trailing
zeros while loading the AOF and safely truncating the file as to
not include the zeros in the future.
 2020-10-07 09:52:32 -07:00
tidwall 3f87be18b4 Fixed typo 2020-09-22 16:55:31 -07:00
tidwall 8e35787e68 1.22.1 2020-09-22 16:52:03 -07:00
tidwall 9a34a378bb Updated Go version 2020-09-22 16:50:49 -07:00
tidwall b1dc463c41 Updated dependencies 2020-09-22 16:43:58 -07:00
tidwall 43cd87dc3a Merge branch 'master' of https://github.com/tidwall/tile38 2020-09-22 16:26:58 -07:00
Josh Baker 5edfccdc49
Merge pull request #563 from axvq/readme-b3q-go-client 
Update README.md (Go client)
 2020-09-22 16:24:52 -07:00
Josh Baker ad7c672a98
Merge pull request #575 from nkovacs/patch-1 
Fix typo in usage
 2020-09-22 16:24:17 -07:00
tidwall b47187349b Fix "cross" detection on firing in some cases 
Fixes #578
 2020-09-22 16:19:49 -07:00
Nikola Kovacs 8b271d1e0b
Fix typo in usage 2020-08-17 10:18:17 +02:00
tidwall bd572b0d38 1.22.0 2020-08-12 12:50:13 -07:00
tidwall d819db5f8b Added MONITOR command 
closes #571
 2020-08-12 12:38:52 -07:00
tidwall 9093926135 Limit geohash precision to 12 2020-08-12 10:58:49 -07:00
tidwall 25a954a6aa Merge branch 'superloach-master' 2020-08-12 10:57:49 -07:00
Terra Brown 9202fd0206
s/64/12/ 2020-08-11 18:11:06 -04:00
tidwall f23b46cfc0 Hotfix for previous commit 2020-07-04 10:35:07 -07:00
tidwall f3622c3756 Fixed wrong order for fields with SCAN 
This commit fixes an issue that happens when running SCAN on a
collection that has objects with fields, causing field values
to be mismatched with their respective keys.

This only occured with json output, and is a regression from #534.

Fixes #569
 2020-07-04 10:12:06 -07:00