fsnotify | File system notification for Go | Notification library

Unfortunately you can't easily capture or redirect stdout and stderr for Haskell programs. Various hacks exist such as the System.Posix.Redirect or System.IO.Silently libraries, but they have a pile of caveats such as

• being POSIX-only, and
• messing with the file descriptors for your entire process, so they are not thread-safe and might interfere with other use of the handles.

In my experience the best thing to do is run your code in a MonadLogger monad. This offers a lot of control over where the log messages go: when you invoke the monad you can use runStdoutLoggingT, runChanLoggingT, etc. or an arbitrary IO function of your own to handle the messages.

If you use a logging monad transformer, you'll want to import a lifted version of bracket to use with it. I really like using Control.Exception.Safe in any place you would normally use Control.Exception (for the liftedness and other safety reasons).

So the problem lied with wrong imports.

Basically Deployments are defined in apps/v1beta2. What I was doing was importing "k8s.io/api/apps/v1beta1". I needed to change it to "k8s.io/api/apps/v1beta2"

Also for fetching that I needed to refer to clientset.AppsV1beta2() instead of clientset.ExtensionsV1beta1()

Its a bug with version inconsistency between go-micro and grpc. About a week ago I tried to follow the tutorial which you mention and got same error. If you want to fix the error above please follow the interactions below the link: https://github.com/etcd-io/etcd/issues/11563.

In additionally I recommend you just build grpc service without go-micro, due to version inconsistency.

The function that handled the matching used a different alert level for the printk function. As such, the messages were not displayed to the console at that stage in the boot process.

What was:

Some module in the transitive dependencies of github.com/onsi/ginkgo/ginkgo added a requirement on some version of gopkg.in/fsnotify.v1, which resolves to the repository hosted at github.com/fsnotify/fsnotify.

However, the go.mod file in that repository declares its canonical import path to be github.com/fsnotify/fsnotify, not gopkg.in/fsnotify.v1.

If you are using Go 1.14, the rest of the error message (which seems to be truncated) should tell you exactly which dependency is using the non-canonical path. The long-term fix is to move that dependency over to the canonical path and upgrade your other dependencies such that gopkg.in/fsnotify.v1 is no longer required.

Sounds like an issue with cabal - I think there are some packaging difficulties on Arch Linux.

As an alternative, you can manually build a Haskell project with your specific xmonad config, once you know this builds correctly, you can create a ~/.xmonad/build shell file, and in here trigger a build to your xmonad config/application.

So the contents of build might be:

You create a timer and you stop it immediately:

I understand that viper can help with live changing out of configuration without restarting your app using the OnConfigChange event, but have you tried setting the log level in your base ConfigMap and then starting up the app, just to make sure it's not an issue with the OnConfigChange event firing and your particular config in k8s (and not your local environment where you've tested it works).

Lastly, what is the difference between your local test environment (where this is working) and the other environment where this is not working?

Are there any environment variables that might be affecting this differently in the one environment?

There is nothing wrong with your code as far as I can see since fsnotify truly does trigger. So the culprit has to be in parsing. The first call to setLogLevel(c.GetLogLevel()) outside your onConfigChange callback returns an incorrect value. Change the contents of your yaml file to just