[Bug 198727] [PATCH] lang/mono FileSystemWatcher (kevent) deadlock problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198727 w.schwarzenf...@utanet.at changed: What|Removed |Added CC||w.schwarzenf...@utanet.at --- Comment #13 from w.schwarzenf...@utanet.at --- Mono version is at 4.8.1.0. I don't think this is relevant anymore. Please close it. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
[Bug 198727] [PATCH] lang/mono FileSystemWatcher (kevent) deadlock problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198727 Romain Tartière changed: What|Removed |Added Status|In Progress |Closed Resolution|--- |Overcome By Events -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
[Bug 198727] [PATCH] lang/mono FileSystemWatcher (kevent) deadlock problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198727 --- Comment #14 from joshrueh...@gmail.com --- I believe the patch still applies properly. I actually still use it to enable realtime media scanning for the Emby plugin that I package for the FreeNAS community. It would be great if we could get this accepted upstream, or if this got reviewed. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
[Bug 198727] [PATCH] lang/mono FileSystemWatcher (kevent) deadlock problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198727 Romain Tartière changed: What|Removed |Added Status|Closed |Open Resolution|Overcome By Events |--- --- Comment #15 from Romain Tartière --- Ooops! I understood that this change was included upstream… Is there a PR upstream ? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
[Bug 198727] [PATCH] lang/mono FileSystemWatcher (kevent) deadlock problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198727 --- Comment #16 from joshrueh...@gmail.com --- Sorry, I confused this with https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206593. I believe both solve the same problem, but #206593 is the patch I have been including with the Emby plugin for FreeNAS. I does not look like there is an upstream (mono) merge request for either of these patches. I do see this github compare for #206593. https://github.com/mono/mono/compare/mono-4.2.2.10...razzfazz:mono-4.2.2.10-freebsd_port_patch I think it is fine to close/change the status for both of these bug reports. When I have time I could submit a new one, reference both of these bugs, CC everyone involved, and make sure the implemented changes apply to the latest mono version. I can also submit a merge request upstream which I think is the ideal solution. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
[Bug 206593] lang/mono: fix kevent-based file system monitor on FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206593 --- Comment #11 from Daniel Becker --- I did submit pull requests for these changes upstream; let me check whether all of them have been merged by now. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
[Bug 198727] [PATCH] lang/mono FileSystemWatcher (kevent) deadlock problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198727 --- Comment #17 from Ivan Radovanovic --- This was actually the most recent work I did with this watcher https://github.com/radovanovic/monobsd/commit/27141786e3db3e5e381be812ff698d479550e678 That was when we were trying to make mono run better on FreeBSD. I am not sure if guys from .Net foundation took these patches for their watcher implementation or they did it from scratch (or they didn't do it at all). In the meantime I mostly moved away from mono, so I didn't really have time to look at this issue anymore. At point when I wrote it it passed all tests and it was able to apply cleanly to upstream. Later I realized that for my use case for .Net it was much better to have completely broken watcher implementation, so I stopped using and maintaining it... -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
[Bug 198727] [PATCH] lang/mono FileSystemWatcher (kevent) deadlock problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198727 Russell Haley changed: What|Removed |Added CC||russ.ha...@gmail.com --- Comment #18 from Russell Haley --- My understanding is that waiting on upstream for these kinds of patches is fruitless. I just tested the patch to move mono to 5.2. I am willing to test if someone puts an appropriate patch on reviews.freebsd.org and provides test cases (e.g. name a program to test and loosely describe some test cases I can run). FYI there will be an exp-run done for mono 5.2 once the D13752 is approved (soonish?). https://reviews.freebsd.org/D13752 If nobody has time please say so now and I will do my best but I'm still trying to catch up with other projects. Once the filesystemwatcher is tested, I can update the mono port and ask dbn@ to commit? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
