Same here, after setting a new limit in `/etc/sysctl.conf`, `sudo sysctl -p` gives `sysctl: permission denied on key 'fs.inotify.max_user_watches'`

Increasing this limit is needed for normal operation of IDEs/code editors (e.g. IntelliJ and VSCode).

jkwang, can you take a look this week? Thanks.

We have an official document that lists optimal values for 
/etc/security/limits.conf and /etc/sysctl.conf:
https://github.com/lxc/lxd/blob/master/doc/production-setup.md

You might want to take a look at these. :)

Has there been any progress on this front? Thanks

Working on a CL.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/96e8d80bde6d41c9e62061e5c8518c8e20cc5fda

commit 96e8d80bde6d41c9e62061e5c8518c8e20cc5fda
Author: Jingkui Wang <jkwang@google.com>
Date: Sat May 05 03:37:57 2018

vm_tools: setup resource limits in maitred

This patch setup the limits according to lxd suggestion.

BUG= chromium:830206 
TEST=manual

Change-Id: Ic05922a6502d3a6d9aecfc1ba526c88881042db8
Reviewed-on: https://chromium-review.googlesource.com/1041655
Commit-Ready: Jingkui Wang <jkwang@google.com>
Tested-by: Jingkui Wang <jkwang@google.com>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>

[modify] https://crrev.com/96e8d80bde6d41c9e62061e5c8518c8e20cc5fda/vm_tools/maitred/init.h
[modify] https://crrev.com/96e8d80bde6d41c9e62061e5c8518c8e20cc5fda/vm_tools/maitred/init.cc

Excellent news, thank you!

Verified on component version 10669.0.0, which is now live.