dir/dircache: disable access checks for now

1) Because of connection caching, our attempts to access the store
both cached and uncached did not work. I have currently disabled
the checks until I can figure out how to make it work. This will
be necessary to make writeback work.

2) Fix the lock in proxied.go:handleEvent. It was too late in the
routine. The following scenario was possible (even probable) when
doing a large git clone:

	Delete file
	seq = Put(file)
			seq = Watch event for delete file
			if event seq > file.seq remember delete
	file.seq = seq

Thus we end up thinking the file we just put has been deleted.

Change-Id: I0475aa6cc0ff853ddbba23b55ad0424cf157de05
Reviewed-on: https://upspin-review.googlesource.com/18440
Reviewed-by: Andrew Gerrand <adg@golang.org>
2 files changed
tree: 0ddd57628049b0708729f8e359a4e58d0ed59d9b
  1. .travis.yml
  3. CONDUCT.md
  6. Gopkg.lock
  7. Gopkg.toml
  10. README.binary
  11. README.md
  12. access/
  13. bind/
  14. cache/
  15. client/
  16. cloud/
  17. cmd/
  18. config/
  19. dir/
  20. doc/
  21. errors/
  22. factotum/
  23. flags/
  24. key/
  25. log/
  26. metric/
  27. pack/
  28. path/
  29. rpc/
  30. serverutil/
  31. shutdown/
  32. store/
  33. subcmd/
  34. test/
  35. transports/
  36. upbox/
  37. upspin/
  38. user/
  39. valid/
  40. vendor/
  41. version/



Documentation: upspin.io

About the project

Upspin is an experimental project to build a framework for naming and sharing files and other data securely, uniformly, and globally: a global name system of sorts.

It is not a file system, but a set of protocols and reference implementations that can be used to join things like file systems and other storage services to the name space.

Performance is not a primary goal. Uniformity and security are.

Upspin is not an official Google product.


Upspin has rough edges, and is not yet suitable for non-technical users.

Build Status


The code repository lives at upspin.googlesource.com and is mirrored to GitHub.

Note that the Upspin project does not use GitHub pull requests, and that we use the issue tracker for bug reports and proposals only.

See the Contribution Guidelines for more information on contributing to the project.

Reporting issues

Please report issues through our issue tracker.


All Upspin users should subscribe to the Upspin Announcements mailing list to receive critical information about the project.

Use the Upspin mailing list for discussion about Upspin use and development.

Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

The Upspin mascot is Copyright 2017 Renee French. All Rights Reserved.