inotify | Swift wrapper around the CInotify library | Notification library

Note I am using a singleton class.

There are no errors in this code. But you may be using it incorrectly. To avoid accidental usage errors, I advise you to change the implementation:

Finally found a solution here

Just add CHOKIDAR_USEPOLLING=true npm start to a local .env file

I'm not really sure what happened and why but I tried doing this on my rails container and I was no longer receiving the said error.

1. docker-compose run --rm bash
2. cd to project directory
3. bundle install

You don't need inotify for this.

If you open a named pipe for writing, the open system call will block until some process opens the named pipe for reading. That's basically what you want. When the open returns, you know there's a client waiting to read.

Similarly, if you open the pipe for reading, the open will block until some process opens the pipe for writing. Furthermore, a read will block until the writer actually writes data. So the named pipe basically takes care of synchronisation.

That makes for a very simple client-server architecture, but it only works if you never have two concurrent clients. For a more general approach, use Unix domain sockets.

Set DEBIAN_FRONTEND=noninteractive before running apt-get install:

This issue is caused by the overriding of parent class. The code in Caliber class generated by nswwag override the PropertyChanged event and RaisePropertyChanged method, which causes hide RaisePropertyChanged method inherited from base class.

You can delete these overriding in Caliber class to solve error. But you said these code genetated automatically, and it can’t change.

As you said, you can add the Typename property to the sub class. Or you can directly declare the object of the parent class and bind dropDownBase.TypeName.

Yesterday I tried to install Ejabberd first through souce code

Just curiosity: what problems did you find, that prefered to use the Ubuntu package?

Did you install from source code? If so, did you later uninstall it? Maybe uninstallation left some files there (there was some bug related to that in make uninstall)... it will help if you can take a look at the installation paths and remove the remaining ejabberd files and directories, specially the file ejabberdctl.

and then with Ubuntu specific packages

Well, it could be that both installations get mixed... or maybe the Ubuntu package has some problem unrelated to your previous installation. Keep all investigation lines open :)

{"init terminating in [do_boot",{undef,[{ejabberd_ctl,start,[],

This error message says that erlang cannot find the file ejabberd_ctl.beam, or that the file doesn't define the function start.

Just a wild idea: maybe you are running the "ejabberdctl" script from source installation (pointing to the old ejabberd beam files), but now you have the ejabberd beam files installed in a different location (by the Ubuntu package).

If you do a standard git gc in a repository with no changes, this is expected. Git names its packfiles by a hash of their contents. Because Git doesn't recompute deltas for existing packs, when you git gc and there's only one pack and no loose objects, it's very likely that it will pack all the data into one pack that's the same as the old one.

When this happens, Git still has a file descriptor to the old pack open because it doesn't close packs immediately. This is because often it's necessary to access them again, so it will try to leave them open a little while. The old pack, which is still open, is renamed to the old name, and the new pack is renamed into place; the old pack is then deleted. On a Unix system, it's completely possible to delete a file for which you have the file descriptor open; when the last process closes its file descriptor, the storage is freed.

So this all seems completely normal for the scenario you're describing. Usually git gc is not a no-op, since additional objects are added to or removed from the pack or multiple packs are combined into one. But, if you do run a git gc immediately after running one with no intermediate changes, this is expected.

From your ruby -v, I see that you are in an Intel x86 Mac, but the gem that your trying to build (nokogiri-1.11.3-arm64-darwin) is for new Mac ARM M1 chips. If this is the cause, it means your are using precompiled gems.

Try uninstalling the gem, specify that you don't want to use precompiled gems, and reinstall.