evince: respect global dbusSupport flag

This commit allows to compile evince without dbus (-Ddbus=false) if
the dbusSupport attribute is set to false.  This can be done globally
in nixpkgs.conf, and is understood by other packages.  See also PR
For reasons which remain unclear, the process of building the
development documentation (devdocs) fails when -Ddbus=false is passed
to meson.  Let's simply not build the devdocs in this case.
Evince is currently the only PDF viewer with form-filling support that
doesn't depend on QT.  Nowadays a lot of unavoidable things like tax
forms require a form-filling PDF viewer.  Since people don't get much
of a choice anymore about having to use a piece of software with this
feature, let's at least allow them to do the job with the smallest
possible set of dependencies.
Checked with nixpkgs-hammer, which did not report any new warnings
introduced by this commit.
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I do not really see the benefit. Each extra option makes the expression more cluttered and less maintainable, and dbus is a pretty tiny dependency anyway. There would need to be a stronger argument to justify the extra noise. The explanation of devdocs disabling is unsatisfactory too.

and dbus is a pretty tiny dependency anyway.

Perhaps, but it has attack surface implications.

The explanation of devdocs disabling is unsatisfactory too.

I agree.
Digging through the evince build machinery to figure out exactly what causes this spooky-action-at-a-distance would require significant effort.  I would expend that effort if the devdocs problem were the only obstacle to this being merged.

Perhaps, but it has attack surface implications.

Looking at the source code, I really would not worry about that. The attack surface of the D-Bus API is also trivial. Especially compared to the many C libraries that parse various file formats, all without any sandboxing.

Digging through the evince build machinery to figure out exactly what causes this spooky-action-at-a-distance would require significant effort. I would expend that effort if the devdocs problem were the only obstacle to this being merged.

Could you share the error message?

Looking at the source code, I really would not worry about that.

https://github.com/freedesktop/dbus/blob/master/dbus/dbus-sysdeps-unix.c#L235

The project used dbus implementation from glib’s gio-unix-2.0 library (gdbus), not libdbus.

evince-scan.c:(.text.startup+0x50): undefined reference to ev_media_player_keys_get_type'`

Yeah, that is another evidence that the configuration without dbus support is untested, this line should be conditional:
https://gitlab.gnome.org/GNOME/evince/-/blob/41.4/help/reference/shell/evince.types#L4
However, the upcoming GNOME 42 will use a different documentation generator that is not affected by this.

I'm marking this as draft while I reconsider my approach to the whole dbusSupport thing.
If I can get a stub-headers package to work, then an overlay with { dbus = dbus-stub-headers; } instead of { dbusSupport = false; } would have the same benefits without adding an extra parameter to so many packages.

As mentioned, dbus package is only used for the pkg-config file to find the .service file instalation path. Most GLib based apps have long since switched from libdbus to GDBus (which is part of Glib’s Gio library).

And there are many more independent D-Bus client libraries (e.g. Rust programs started switching to a native zbus library).

And there are many more independent D-Bus client libraries

Ugh, I thought most of those were wrappers around libdbus.  Surprisingly many of them are not.


plexdrive does not show all files

hi there
I successfully built the project from source with 'go'
and was able to mount my team drive
but it does not show all files
there are missing folders and alot of folders shown as empty
is there a limit for amout of files somewhere?
I've recreated the auth token and it showed: Processed 7886 items / deleted 268 items / updated 7618 items
so I guess plexdrive gets 7886 files from my drive?
but rclone size shows that there are 9119 files at the drive
any help is appreciated
thanks
structure is like this
/mounted/drive/
------>RootSubFolderOne (visible)
------------>Sub1 (not visible)
------------>Sub2 (no visible)
------------>Sub3 (visible)
------------------>a lot of missing and empty folders
------->RootSubFolderTwo (visible)
------------>Every Folder and File visible

You could try removing cache.bolt from ~/.plexdrive and restart plexdrive to force a complete resync of the file system.

@felixbuenemann looks like deleting cache.bolt fixed this
thanks


fix(testing): support for Node16 TypeScript module resolution

Similar to #2454, adds support for Node16 module resolution in TypeScript for the testing package.
Tested:

Still works with "moduleResolution": "node"
Works with "moduleResolution": "node16"

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Fixed in https://github.com/open-wc/open-wc/pull/2507


Boot Error

Firmware version
v2.4.1
What happened? What did you expect to happen?
After flashing few types of binaries in few types of controllers (WeAct esp32-c3, WROOM32 - same one shown in the "simple" wiki page),
Or the board get stuck, do not want to boot (ESP32-C3), or get stuck in a boot loop with the following message:
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
invalid header: 0x25207325
invalid header: 0x25207325
invalid header: 0x25207325
invalid header: 0x25207325
invalid header: 0x25207325
invalid header: 0x25207325
invalid header: 0x25207325
invalid header: 0x25207325
I have tried to flash via Flash Tool, and ESPHOME, with the cc1101 connected and disconnected, always the same error.
Please advice.

Invalid header means you did not flash (onboard) with a binary that is valid for your chip.  So if your board is an ESP32-C3 then you need to download the .zip file SomfyController.onboard.esp32c3.bin.zip but if this is a WROOM32 then you need to download SomfyController.onboard.esp32.bin.zip.   It cannot be both a WROOM32 and a C3
After you download the correct file specified above you must extract the zip to get the .bin file located inside.   Then use web.esphome.io to flash the file.  For more in-depth instructions see this wiki.
https://github.com/rstrouse/ESPSomfy-RTS/wiki/Installing-the-Firmware

My bad, downloaded the bin files instead of the ZIPs.
Thank you so much, great software.

Glad you got it working!


For integration with Kitty, how can another process get its yabai-compatible window numbers?

Background, I'm running yabai with kitty, and kitty has several windows in the same process. I want to be able to have my editor (running in several Kitty windows), figure out where it is on the screen, relative to other editor windows.
Kitty has window numbers, but they start at 1 and increase monotonically.  I looked at the yabai code and found the use of the private API _AXUIElementGetWindow(ref, &wid).
I'm not sure how, in Kitty, to get a AXUIElementRef from a window (the ref isn't the window itself, is it?), or whether I can use this private API without requiring the user to agree to accessibility permissions.  I see that NSWindow has windowNumber, but the documentation says this is not the same as the global window server number.
Thoughts?
kovidgoyal/kitty#2552

NSWindow windowNumber is the same thing, whatever documentation says otherwise is wrong. AXUIElementRefs are only necessary for external software that wants to interact with windows of some other application.

On 23 Jul 2020, at 21:43, Jason Felice<EMAIL_ADDRESS>wrote:
Background, I'm running yabai with kitty, and kitty has several windows in the same process. I want to be able to have my editor (running in several Kitty windows), figure out where it is on the screen, relative to other editor windows.
Kitty has window numbers, but they start at 1 and increase monotonically. I looked at the yabai code and found the use of the private API _AXUIElementGetWindow(ref, &wid).
I'm not sure how, in Kitty, to get a AXUIElementRef from a window (the ref isn't the window itself, is it?), or whether I can use this private API without requiring the user to agree to accessibility permissions. I see that NSWindow has windowNumber, but the documentation says this is not the same as the global window server number.
Thoughts?
kovidgoyal/kitty#2552 https://github.com/kovidgoyal/kitty/issues/2552
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/koekeishiya/yabai/issues/625, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABPDZV22OOJLPHVM6FAG6STR5CHGNANCNFSM4PGBTVFA.

Thank you!  This got merged to kitty and is working nicely.


35.0.0 Build-Tools not Recognized

Description
The default build-tools version installed by Android Studio is 35.0.0, but Tophat requires 33.0.0 to launch an Android app successfully. Since Tophat currently doesn’t clarify this, Android appears marked as "completed" on the onboarding despite the mismatch.
When users attempt to launch an Android app, the process fails as it doesn’t recognize the 35.0.0 build-tools version.
While attempting to roll out this tool to employees, we must reduce the complexity of the installation steps, and ideally remove the need to manually download an older build-tools version.
Expo Orbit automatically detects available build-tools versions, so a similar behavior in Tophat would be nice.
Steps to reproduce

Download Android Studio
See build-tools installed as 35.0.0 by default
Open Tophat
Attempt to Launch an Android App
See it failed to launch, as AAPT was not recognized

Expected behavior

Download Android Studio
See build-tools installed as 35.0.0 by default
Open Tophat
Attempt to Launch an Android App
See it succeeding, as build-tools 35.0.0 gets find.

Screenshots
Without build-tools 35.0.0 and not 33.0.0 (default behavior):

With build-tools 33.0.0 installed:
![Image](https://github.com/user-attachments/assets/86bfc247-63c3-4c6e-a350-24083e9ed8b5
System

Device: MacBook Pro
OS: macOS 15.1
Platform: Apple Silicon M3

Other details

Also working on it 👆


Browser / Transparent Window Wording Improvements

Felt that the documentation for BrowserWindow and TransparentWindow were a little poorly worded, especially some of the missing connectives hampering the flow of the sentences. I've also made the code commented as to literally point out what's going on, for those people who may find themselves confused.

Thanks for the edits, @Crowes. However the source content lives in a different repository: https://github.com/electron/electron/tree/master/docs -- I'm going to close this PR, but please feel free to open a new PR on that repo.
I've also created an issue to help prevent confusion about this in the future: https://github.com/electron/electron.atom.io/issues/682


How to reset/retrieve the token for API usage?

Can't find log, I an using runpod, is there a easy to get it?

If you want to reset the token and the password, delete the file ./login/PASSWORD.
If you want to see the token, it's in the terminal when the server starts. (maybe search for For direct API calls, use token=)


Loads of errors after opening cs file

Hi, these are my settings
let g:OmniSharp_server_stdio = 1
let g:OmniSharp_selector_ui = 'fzf'
let g:OmniSharp_server_use_mono = 1
let g:OmniSharp_highlight_types = 3
let g:OmniSharp_start_without_solution = 1
let g:OmniSharp_server_stdio_quickload = 1

let g:ale_fix_on_save = 1
let g:ale_completion_enabled = 1
let g:ale_sign_error = '●'
let g:ale_sign_warning = '.'
let g:ale_linters = {
\ 'cs': ['OmniSharp']
\}

The behaviour is there when you open a single file and with errors that are most basic ones. e.g. The namespace "Web" doesn't exists in the namespace "System"
This has been bugging me for quite some time. Any help will be appreciated.
The project is opened side by side in my vscode and it runs there fine without any problems

I suspect your server isn't properly loaded. Try removing the line let g:OmniSharp_server_stdio_quickload = 1 which will hopefully let the server finish loading before sending requests.
If that doesn't resolve the issue, please post your server log (:OmniSharpOpenLog from a .cs file)

Well thanks for the quick reply (a big fan here btw). So let g:OmniSharp_server_stdio_quickload = 1 did not work and as I did : OmniSharpOpenLog from the cs file, I got this as output

You're presumably trying to use :OmniSharpOpenLog from a modified buffer, without :set hidden?
You can also just open the file yourself, it's in your OmniSharp-vim plugin directory, at log/stdio.log, so something like ~/.vim/plugged/omnisharp-vim/log/stdio.log

Here it is
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Stdio.Host","Message":"Starting OmniSharp on MacOS 10.14.6 (x64)"},"Seq":1,"Type":"event"}
process 28055 run  JSON error: Vim(let):E474: Invalid argument
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Services.DotNetCliService","Message":"DotNetPath set to dotnet"},"Seq":2,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.Discovery.MSBuildLocator","Message":"Located 2 MSBuild instance(s)\n            1: Mono 16.4 - \"/Library/Frameworks/Mono.framework/Versions/6.4.0/lib/mono/msbuild/Current/bin\"\n            2: StandAlone 16.4 - \"/Users/apple/.cache/omnisharp-vim/omnisharp-roslyn/.msbuild/Current/Bin\""},"Seq":3,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.Discovery.MSBuildLocator","Message":"Registered MSBuild instance: Mono 16.4 - \"/Library/Frameworks/Mono.framework/Versions/6.4.0/lib/mono/msbuild/Current/bin\"\n            CscToolExe = csc.exe\n            CscToolPath = /Users/apple/.cache/omnisharp-vim/omnisharp-roslyn/.msbuild/Current/Bin/Roslyn"},"Seq":4,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Cake.CakeProjectSystem","Message":"Detecting Cake files in '/Users/apple/Documents/codidact/authentication'."},"Seq":5,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Cake.CakeProjectSystem","Message":"Could not find any Cake files"},"Seq":6,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectSystem","Message":"Detecting projects in '/Users/apple/Documents/codidact/authentication/Codidact.Authentication.sln'."},"Seq":7,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Queue project update for '/Users/apple/Documents/codidact/authentication/src/Application/Application.csproj'"},"Seq":8,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Queue project update for '/Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj'"},"Seq":9,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Queue project update for '/Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj'"},"Seq":10,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Queue project update for '/Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj'"},"Seq":11,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Queue project update for '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'"},"Seq":12,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Script.ScriptProjectSystem","Message":"Detecting CSX files in '/Users/apple/Documents/codidact/authentication'."},"Seq":13,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Script.ScriptProjectSystem","Message":"Could not find any CSX files"},"Seq":14,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.WorkspaceInitializer","Message":"Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0"},"Seq":15,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Loading project: /Users/apple/Documents/codidact/authentication/src/Application/Application.csproj"},"Seq":16,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.WorkspaceInitializer","Message":"Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100"},"Seq":17,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.WorkspaceInitializer","Message":"Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.ImplementTypeWorkspaceOptionsProvider, Order: 110"},"Seq":18,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.WorkspaceInitializer","Message":"Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.EditorConfigWorkspaceOptionsProvider, Order: 200"},"Seq":19,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.WorkspaceInitializer","Message":"Configuration finished."},"Seq":20,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Stdio.Host","Message":"Omnisharp server running using Stdio at location '/Users/apple/Documents/codidact/authentication' on host -1."},"Seq":21,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Successfully loaded project file '/Users/apple/Documents/codidact/authentication/src/Application/Application.csproj'."},"Seq":23,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Adding project '/Users/apple/Documents/codidact/authentication/src/Application/Application.csproj'"},"Seq":25,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Loading project: /Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj"},"Seq":26,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Successfully loaded project file '/Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj'."},"Seq":27,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Adding project '/Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj'"},"Seq":29,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Loading project: /Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj"},"Seq":30,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Successfully loaded project file '/Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj'."},"Seq":31,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Adding project '/Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj'"},"Seq":33,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Loading project: /Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj"},"Seq":34,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Successfully loaded project file '/Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj'."},"Seq":37,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Adding project '/Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj'"},"Seq":39,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Loading project: /Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj"},"Seq":40,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Successfully loaded project file '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'."},"Seq":49,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Adding project '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'"},"Seq":51,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Update project: Application"},"Seq":52,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Update project: Domain"},"Seq":54,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Update project: Infrastructure"},"Seq":56,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Update project: WebApp"},"Seq":58,"Type":"event"}
process 28055 run  {"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectManager","Message":"Update project: WebApp.Tests"},"Seq":60,"Type":"event"}

Ok that looks good,, OmniSharp-roslyn seems to be loading up well. What is the "Server loaded" message echoed to Vim? If you miss it, you can see it in :messages. Something along the lines of "Loaded server for ...", or "Failed to load ..."

It says https://imgur.com/a/2IUVxOa

Ok. That message indicates that OmniSharp-vim didn't wait for OmniSharp-roslyn to load up fully before starting to send messages. I've had similar errors to yours when that happens. Try increasing the server load timeout: set g:OmniSharp_server_loading_timeout = 60

Well this time it says
Loaded server for /Users/apple/Documents/codidact/authentication/Codidact.Authentication.sln but there are still errors on the screen like before so nothing changed

Hmm. No "... after 10.6s"? Are you using the latest versions of OmniSharp-vim and OmniSharp-roslyn?

Yes, I updated them with :PlugInstall and did :OmniSharpInstall.

The the message should say "Loaded server for /Users/apple/Documents/codidact/authentication/Codidact.Authentication.sln in 00.0s", right?

I'm a bit stuck sorry. Things to try:

Remove let g:OmniSharp_server_use_mono = 1, then restart Vim and re-install the server with :OmniSharpInstall (I don't know if this is necessary on macs still, I don't have one to test on)
Compare vim's omnisharp-roslyn log (which you posted earlier) with the vscode log. Are they using the same MSBuild?

Well, it doesn't say "in 00.0s", I have tried removing mono and then reinstalling but no luck :/. I'll try comparing with vscode log

Then you're not using the latest version of OmniSharp-vim. :PlugUpdate is the vim-plug command to update plugins - :PlugInstall just installs plugins you don't already have.

(Not that I expect the latest version of OmniSharp-vim to help, necessarily, I think you're experiencing some kind of msbuild/omnisharp-roslyn issue. Interesting that vscode is working properly though!)

Well after that, it says Loaded server for /Users/apple/Documents/codidact/authentication/Codidact.Authentication.sln in 11.5s  but no change! so by seeing vscode's log, I saw that it is using a Omnisharp that is latest, so I did let g:OmniSharp_server_path in my .vmrc and still nothing :/

Can you post the vscode OmniSharp log? It should look reasonably similar to the vim one you posted earlier

It says
Starting OmniSharp server at 4/3/2020, 10:08:21 PM
    Target: /Users/apple/Documents/codidact/authentication/Codidact.Authentication.sln

OmniSharp server started with Mono 6.4.0.
    Path: /Users/apple/.vscode/extensions/ms-dotnettools.csharp-1.21.16/.omnisharp/1.34.15/omnisharp/OmniSharp.exe
    PID: 15544

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on MacOS 10.14.6 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 2 MSBuild instance(s)
            1: Mono 16.4 - "/Library/Frameworks/Mono.framework/Versions/6.4.0/lib/mono/msbuild/Current/bin"
            2: StandAlone 16.4 - "/Users/apple/.vscode/extensions/ms-dotnettools.csharp-1.21.16/.omnisharp/1.34.15/omnisharp/.msbuild/Current/Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: Mono 16.4 - "/Library/Frameworks/Mono.framework/Versions/6.4.0/lib/mono/msbuild/Current/bin"
            CscToolExe = csc.exe
            CscToolPath = /Users/apple/.vscode/extensions/ms-dotnettools.csharp-1.21.16/.omnisharp/1.34.15/omnisharp/.msbuild/Current/Bin/Roslyn
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in '/Users/apple/Documents/codidact/authentication'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.MSBuild.ProjectSystem
        Detecting projects in '/Users/apple/Documents/codidact/authentication/Codidact.Authentication.sln'.
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Application/Application.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in '/Users/apple/Documents/codidact/authentication'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /Users/apple/Documents/codidact/authentication/src/Application/Application.csproj
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.ImplementTypeWorkspaceOptionsProvider, Order: 110
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.EditorConfigWorkspaceOptionsProvider, Order: 200
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location '/Users/apple/Documents/codidact/authentication' on host 15521.
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/Users/apple/Documents/codidact/authentication/src/Application/Application.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/Users/apple/Documents/codidact/authentication/src/Application/Application.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: Application
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Domain/bin/Debug/netcoreapp3.1/Codidact.Authentication.Domain.dll'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: Domain
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: Infrastructure
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Application/bin/Debug/netcoreapp3.1/Codidact.Authentication.Application.dll'
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Domain/bin/Debug/netcoreapp3.1/Codidact.Authentication.Domain.dll'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: WebApp
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Application/bin/Debug/netcoreapp3.1/Codidact.Authentication.Application.dll'
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Domain/bin/Debug/netcoreapp3.1/Codidact.Authentication.Domain.dll'
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Infrastructure/bin/Debug/netcoreapp3.1/Codidact.Authentication.Infrastructure.dll'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: WebApp.Tests
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/WebApp/bin/Debug/netcoreapp3.1/Codidact.Authentication.WebApp.dll'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Application/Application.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Application/Application.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /Users/apple/Documents/codidact/authentication/src/Application/Application.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Application/Application.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Application/Application.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Application/Application.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/Users/apple/Documents/codidact/authentication/src/Application/Application.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/Users/apple/Documents/codidact/authentication/src/Domain/Domain.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/Users/apple/Documents/codidact/authentication/src/Infrastructure/Infrastructure.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/Users/apple/Documents/codidact/authentication/src/WebApp/WebApp.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/Users/apple/Documents/codidact/authentication/tests/WebApp.Tests/WebApp.Tests.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: Application
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Domain/bin/Debug/netcoreapp3.1/Codidact.Authentication.Domain.dll'
[info]: OmniSharp.OmniSharpWorkspace
        Adding analyzer reference: /Users/apple/.nuget/packages/microsoft.entityframeworkcore.analyzers/3.1.2/analyzers/dotnet/cs/Microsoft.EntityFrameworkCore.Analyzers.dll
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: Domain
[info]: OmniSharp.OmniSharpWorkspace
        Adding analyzer reference: /Users/apple/.nuget/packages/microsoft.entityframeworkcore.analyzers/3.1.2/analyzers/dotnet/cs/Microsoft.EntityFrameworkCore.Analyzers.dll
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: Infrastructure
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Application/bin/Debug/netcoreapp3.1/Codidact.Authentication.Application.dll'
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Domain/bin/Debug/netcoreapp3.1/Codidact.Authentication.Domain.dll'
[info]: OmniSharp.OmniSharpWorkspace
        Adding analyzer reference: /Users/apple/.nuget/packages/microsoft.entityframeworkcore.analyzers/3.1.2/analyzers/dotnet/cs/Microsoft.EntityFrameworkCore.Analyzers.dll
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: WebApp
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Application/bin/Debug/netcoreapp3.1/Codidact.Authentication.Application.dll'
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Domain/bin/Debug/netcoreapp3.1/Codidact.Authentication.Domain.dll'
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Infrastructure/bin/Debug/netcoreapp3.1/Codidact.Authentication.Infrastructure.dll'
[info]: OmniSharp.OmniSharpWorkspace
        Adding analyzer reference: /Users/apple/.nuget/packages/microsoft.codeanalysis.analyzers/2.9.3/analyzers/dotnet/cs/Microsoft.CodeAnalysis.Analyzers.dll
[info]: OmniSharp.OmniSharpWorkspace
        Adding analyzer reference: /Users/apple/.nuget/packages/microsoft.codeanalysis.analyzers/2.9.3/analyzers/dotnet/cs/Microsoft.CodeAnalysis.CSharp.Analyzers.dll
[info]: OmniSharp.OmniSharpWorkspace
        Adding analyzer reference: /Users/apple/.nuget/packages/microsoft.entityframeworkcore.analyzers/3.1.2/analyzers/dotnet/cs/Microsoft.EntityFrameworkCore.Analyzers.dll
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: WebApp.Tests
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Application/bin/Debug/netcoreapp3.1/Codidact.Authentication.Application.dll'
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Domain/bin/Debug/netcoreapp3.1/Codidact.Authentication.Domain.dll'
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/Infrastructure/bin/Debug/netcoreapp3.1/Codidact.Authentication.Infrastructure.dll'
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/Users/apple/Documents/codidact/authentication/src/WebApp/bin/Debug/netcoreapp3.1/Codidact.Authentication.WebApp.dll'
[info]: OmniSharp.OmniSharpWorkspace
        Adding analyzer reference: /Users/apple/.nuget/packages/microsoft.codeanalysis.analyzers/2.9.3/analyzers/dotnet/cs/Microsoft.CodeAnalysis.Analyzers.dll
[info]: OmniSharp.OmniSharpWorkspace
        Adding analyzer reference: /Users/apple/.nuget/packages/microsoft.codeanalysis.analyzers/2.9.3/analyzers/dotnet/cs/Microsoft.CodeAnalysis.CSharp.Analyzers.dll
[info]: OmniSharp.OmniSharpWorkspace
        Adding analyzer reference: /Users/apple/.nuget/packages/microsoft.entityframeworkcore.analyzers/3.1.2/analyzers/dotnet/cs/Microsoft.EntityFrameworkCore.Analyzers.dll
[info]: OmniSharp.OmniSharpWorkspace
        Adding analyzer reference: /Users/apple/.nuget/packages/xunit.analyzers/0.10.0/analyzers/dotnet/cs/xunit.analyzers.dll
[fail]: OmniSharp.Roslyn.CSharp.Services.Refactoring.V2.GetCodeActionsService
        Error computing refactorings for Microsoft.CodeAnalysis.CodeRefactorings.ExtractMethod.ExtractMethodCodeRefactoringProvider

At this point it might also be a good idea to post your full .vimrc?

My full .vimrc
" System vimrc file for MacVim
"
" Author:       Bjorn Winckler<EMAIL_ADDRESS>" Maintainer:   macvim-dev (https://github.com/macvim-dev)

set nocompatible

" The default for 'backspace' is very confusing to new users, so change it to a
" more sensible value.  Add "set backspace&" to your ~/.vimrc to reset it.
set backspace+=indent,eol,start

" Disable localized menus for now since only some items are translated (e.g.
" the entire MacVim menu is set up in a nib file which currently only is
" translated to English).
set langmenu=none

" Python2
" MacVim is configured by default to use the pre-installed System python2
" version. However, following code tries to find a Homebrew, MacPorts or
" an installation from python.org:
if exists("&pythondll") && exists("&pythonhome")
  if filereadable("/usr/local/Frameworks/Python.framework/Versions/2.7/Python")
    " Homebrew python 2.7
    set pythondll=/usr/local/Frameworks/Python.framework/Versions/2.7/Python
  elseif filereadable("/opt/local/Library/Frameworks/Python.framework/Versions/2.7/Python")
    " MacPorts python 2.7
    set pythondll=/opt/local/Library/Frameworks/Python.framework/Versions/2.7/Python
  elseif filereadable("/Library/Frameworks/Python.framework/Versions/2.7/Python")
    " https://www.python.org/downloads/mac-osx/
    set pythondll=/Library/Frameworks/Python.framework/Versions/2.7/Python
  endif
endif

" Python3
" MacVim is configured by default to use Homebrew python3 version
" If this cannot be found, following code tries to find a MacPorts
" or an installation from python.org:
if exists("&pythonthreedll") && exists("&pythonthreehome") &&
      \ !filereadable(&pythonthreedll)
  if filereadable("/opt/local/Library/Frameworks/Python.framework/Versions/3.7/Python")
    " MacPorts python 3.7
    set pythonthreedll=/opt/local/Library/Frameworks/Python.framework/Versions/3.7/Python
  elseif filereadable("/Library/Frameworks/Python.framework/Versions/3.7/Python")
    " https://www.python.org/downloads/mac-osx/
    set pythonthreedll=/Library/Frameworks/Python.framework/Versions/3.7/Python
  endif
endif

filetype off
syntax on
filetype plugin indent on
set modelines=0
set number
set ruler
set encoding=utf-8
set ttyfast
set termguicolors
set laststatus=2
set t_Co=256
set guifont=Operator\ Mono\ Medium:h18
set wrap!
set ts=4 sw=4
ru mswin.vim
set guicursor+=a:blinkon0

au VimEnter *  NERDTree
highlight Comment cterm=italic gui=italic
cd
cd documents/codidact/

call plug#begin('~/.vim/plugged')
Plug 'preservim/nerdtree'
Plug 'arcticicestudio/nord-vim'
Plug 'vim-airline/vim-airline'
Plug 'vim-airline/vim-airline-themes'
Plug 'ycm-core/YouCompleteMe'
Plug 'OmniSharp/omnisharp-vim'
Plug 'franbach/miramare'
Plug 'Shougo/vimproc.vim', {'do' : 'make'}
Plug 'dense-analysis/ale'
Plug 'Chiel92/vim-autoformat'
Plug 'junegunn/fzf'
Plug 'junegunn/fzf.vim'
Plug 'prettier/vim-prettier', { 'do': 'yarn install' }
call plug#end()

let g:airline_symbols = {}

let g:airline_powerline_fonts = 1
let g:airline#extensions#tabline#left_sep = ' '
let g:airline#extensions#tabline#left_alt_sep = '|'
let g:airline#extensions#tabline#formatter = 'unique_tail'
let g:airline_theme='bubblegum'
let g:airline#extensions#tabline#enabled = 1
let g:airline#extensions#tabline#show_buffers = 0
let g:airline#extensions#tabline#show_splits = 0
let g:airline#extensions#tabline#show_tabs = 1

let g:OmniSharp_server_stdio = 1
let g:OmniSharp_selector_ui = 'fzf'
let g:OmniSharp_server_use_mono = 1
let g:OmniSharp_highlight_types = 3
let g:OmniSharp_start_without_solution = 1
let g:OmniSharp_server_loading_timeout = 60
let g:OmniSharp_server_path = '/Users/apple/.vscode/extensions/ms-dotnettools.csharp-1.21.16/.omnisharp/1.34.15/omnisharp/OmniSharp.exe'

let g:ale_fix_on_save = 1
let g:ale_completion_enabled = 1
let g:ale_sign_error = '●'
let g:ale_sign_warning = '.'
let g:ale_linters = {
\ 'cs': ['OmniSharp']
\}

let g:formatdef_my_custom_cs = '"astyle --mode=cs --style=ansi -pcHs4"'
let g:formatters_cs = ['my_custom_cs']

let g:airline_left_sep = '⮀'
let g:airline_left_alt_sep = '⮁'
let g:airline_right_sep = '⮂'
let g:airline_right_alt_sep = '⮃'
let g:airline_symbols.branch = '⭠'
let g:airline_symbols.readonly = '⭤'
let g:airline_symbols.linenr = '⭡'

let g:prettier#autoformat_require_pragma = 0
let g:prettier#autoformat_config_present = 0
let g:prettier#config#use_tabs = 'false'
let g:prettier#config#tab_width = '4'

let g:miramare_enable_italic = 1

colorscheme miramare

Can you please try commenting out YouCompleteMe and try again?

ooh so it was that!!, it works now, thanks a lot (so sorry to waste your time over such a silly issue)

Oh phew! YCM runs its own OmniSharp-roslyn and conflicts with OmniSharp-vim. No idea why it is reporting errors but 🤷

Is there any way to resolve the conflict tho? I have lost autocomplete here 😄

Well don't worry, I switched to asyncomplete.vim works fine. Thanks a lot for your time :)

Yeah I would have suggested asyncomplete. If you prefer to use YCM then you really need to go all in with it, and use it instead of OmniSharp-vim.
Thanks a lot for your time
You're welcome ☺


ReplayingDecoderByteBuf#copy returns copy of underlying buffer, losing replay-ability

Expected behavior
ReplayingDecoderByteBuf#copy(int index, int length) should maintain the special replay-ability of the buffer, or the docs should note that the copy does not retain the replay behavior.
Actual behavior
If an in-bounds index + length is specified, the underlying buffer is copied and returned, leading to surprising errors in replaying decoders that use the copy.
Steps to reproduce
Minimal yet complete reproducer code (or URL to code)
class MyDecoder extends ReplayingDecoder<?> {

    final ExecutorService executor = new ThreadPoolExecutor(4,
                                                            10,
                                                            60,
                                                            TimeUnit.SECONDS,
                                                            new ArrayBlockingQueue<>(1000));
    @Override
    protected final void decode(ChannelHandlerContext ctx, ByteBuf in, List<Object> out) throws Exception {

        final ByteBuf copy = in.copy(in.readerIndex(), in.writerIndex() - in.readerIndex();

        executor.execute(() -> {

            try {
                decodeCommand(ctx.channel(), copy, data);
            } catch (Exception e) {
                log.error("Unable to decode data in separate thread" + LogHelper.toString(data), e);
            } finally {
                copy.release();
            }
        });
    }
}

Netty version
4.1.48.Final

I believe this is a wrong use. We must throw the exception in decode, otherwise the decoder will not work properly...

@eager I think what it does is correct... copy will just return a copy of the ByteBuf and it is not guaranteed that the buffer type is the same as before. This is generally true for ByteBuf.

we must throw the exception in decode

@carryxyh that make sense.

I think what it does is correct... copy will just return a copy of the ByteBuf and it is not guaranteed that the buffer type is the same as before.

@normanmaurer that also makes sense. Since ReplayingDecoderByteBuf has its special behavior, does it make sense to update the docs to note that the behavior won’t be present in the copy?

@eager I am happy to review any PR to improve docs etc. Please submit a PR if you think we should clarify.


Absolute coverage thresholds

Clear and concise description of the problem
As a developer using Vitest, I want a way to specify absolute coverage thresholds instead of percentage coverage thresholds. The benefit of absolute thresholds is that you can freeze the code coverage at a specific number of uncovered lines, which then ensures that test coverage must be considered for any new additions to the code.
For example, let's say I start working on a package that has 1000 lines, 750 of which are covered (75% coverage), so I set the coverage threshold to 75% to "preserve" this amount of coverage. I then add a new feature with 10 lines, 8 of which are covered. The new coverage percentage is 75.05%, so I pass coverage. However, if only 7 lines of the new feature are covered, then the new coverage percentage is 74.95%, and I fail. This feels a bit arbitrary - I've only enforced that new code additions must have as good of coverage as the existing code.
With absolute coverage thresholds, I would specify my coverage threshold as "250 uncovered lines." When adding a new feature with 10 lines, all 10 lines must be covered (or marked to be ignored in coverage).
In my organization, our approach to code coverage is to strive for 100% coverage unless there's a reasonable tradeoff (e.g. a particular is too hard to reproduce in testing to make it worthwhile, in which case we explicitly mark that case to be ignored). This is easy to do for code that already has 100% coverage. But for any legacy code that doesn't, we can't really implement this policy very well without absolute coverage thresholds.
We are currently migrating from jest (which supports this feature) to vitest. We are loving vitest but are sad to lose this important piece of functionality.
Suggested solution
Jest supports configuring a coverage threshold with a positive number, in which case its interpreted as a percentage, or a negative number, in which case its interpreted as an absolute threshold.
The advantage of this approach is that it doesn't add any new configuration options. The disadvantage is that it's not totally clear what's happening unless you read the docs.
I think it would also make sense to have a more explicit configuration option to use absolute or percentage thresholds in the coverage config. E.g. something like coverage.thresholdType: 'percentage' | 'absolute'.
I haven't yet looked into how to implement this in the code base, but I'd be happy to take the lead on researching and implementing the feature once its agreed that it would be a useful addition.
Alternative
No response
Additional context
Thank you for your time and consideration!
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

The disadvantage is that it's not totally clear what's happening unless you read the docs.

I think this is the reason why Vitest doesn't support it. And also nyc and c8 don't support it. But we can add it to Vitest just to be compatible with Jest.
I think using the negative numbers is fine, but if you can come up with better API we could add that too.

I haven't yet looked into how to implement this in the code base, but I'd be happy to take the lead on researching and implementing the feature once its agreed that it would be a useful addition.

All coverage threholds related logic is in packages/vitest/src/utils/coverage.ts. Comparison is done here, though I think we need to consider negative numbers in thresholds.autoUpdate related logic too. The summary.data[thresholdKey] might hold info about uncovered lines already.
https://github.com/vitest-dev/vitest/blob/2fb585aea696c27c31fa8f64e0d00940516ecc1c/packages/vitest/src/utils/coverage.ts#L339-L391
Example test case:
https://github.com/vitest-dev/vitest/blob/2fb585aea696c27c31fa8f64e0d00940516ecc1c/test/coverage-test/test/threshold-failure.test.ts#L1-L33

Thanks for the pointers @AriPerkkio - very helpful! I submitted a pull request here: https://github.com/vitest-dev/vitest/pull/7061.


The file name restrictions are incorrect

Either the file name restrictions are incorrectly documented or there is a bug in the wiki page rendering. When I named a page/folder "App Authoring", the page failed to render, and mentioned that it was probably due to title. When I renamed it to "AppAuthoring", it started to work. I gather from this that spaces are not allowed in page titles, which isn't listed in this documentation.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 361efecd-d973-82ed-1dd8-ca01afe12f5d
Version Independent ID: 629f3af2-8218-e53c-45c3-0e40c03f2273
Content: Wiki files, structure, and conventions - Azure DevOps
Content Source: docs/project/wiki/wiki-file-structure.md
Product: devops
Technology: devops-collab
GitHub Login: @chcomley
Microsoft Alias: chcomley

(It does mention that it's a convention to have dashes for spaces, but doesn't mention that that is a strict requirement)

@wygoodin  Thank you for the feedback, please consider becoming a contributor.
The documentation has been updated and is pending review.


Building error

I am getting errors:
# github.com/infobloxopen/atlas-contacts-app/pkg/pb pkg/pb/contacts.override.gorm.go:174:32: too many arguments in call to DefaultListContact         have ("context".Context, *"github.com/infobloxopen/atlas-contacts-app/vendor/github.com/jinzhu/gorm".DB, *ListContactRequest)         want ("context".Context, *"github.com/infobloxopen/atlas-contacts-app/vendor/github.com/jinzhu/gorm".DB)
when trying to run app server or building docker images.
I have noticed that if I don't execute protobuf target from Makefile then everything is ok.
Is it correct behaviour?

Hi @kunteynir, thanks for reporting this! We've seen this behavior a few other places in our projects, due to us making a breaking change in the Atlas app toolkit.
Sloppy on our part -- sorry if it got in your way. We should have this fixed soon, I believe and be able to get back to you on this issue once it is.


Polish the bundle out

You may find the updated bundle preview below.
Highlights of the changes:

Red Hat icon
Added description
Added operator.openshift.io/certmanager example

/lgtm


Typo in header "Search limitaitons"

"Search limitaitons" => "Search limitations"

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: be0bdbf7-3132-9007-6c6a-368c5bcb0f3d
Version Independent ID: 58118f61-f88f-24b9-b785-d8f9d8a1fefd
Content: Administer code, wiki, and work item search - Azure DevOps
Content Source: docs/project/search/administration.md
Product: devops
Technology: devops-collab
GitHub Login: @chcomley
Microsoft Alias: chcomley

Hi @jessehouwing, Thanks so much for pointing this typo out! I've just published the update. In the future, please consider becoming a contributor, we'd love it!


Jump to bookmark table shortcut

Description of Changes
Closes #1304 and #1307

New Version Info
Adds the 'gb' binding to jump to the bookmark table.

@alerque Hi, It is based on #1307.
I've made some clean-ups here and there and changed the shortcut to gb instead of b to prevent clashing with the back vim motion.
This implementation will jump to the bookmark table if it is already open, and will open it when it is closed.
Let me know whether you want this to be included in 7.1.0 or 7.2.0.


[Enhancement] Make initial sync blocking  before sync of all content and app workflow configs is complete

Feedback

App Configs (workflow data - profiles, registers, etc.) have its worker  - This is blocked at the moment
App Content (Questionnaires, StructureMaps et.al) have its worker - Not Blocked

Proposed Solution

Have a blocker on sync till 1 and 2 are complete

This also needs Design team input to share on how this will affect the user experience for the end users

This makes sense, does the sync have text to update the user on the process?
It seems reasonable to add text for the 3 stages of sync, but maybe that's too much info, @HenryRae @rowo please give input.
@f-odhiambo what's the argument for why to sequence these? Are elements of the UX operable when (1) and (2) are synced but initial data is note synced?


chore(main): release 1.2.3

:robot: I have created a release beep boop
1.2.3 (2024-10-18)
Bug Fixes

define validating workflow (4615f90)
whitespacing (ea82703)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.2.3
:sunflower:


setup.py should include pluginbase

https://github.com/ThreatResponse/aws_ir/blob/master/setup.py#L25
^^ This line above where setup.py includes requirements should include pluginbase.
New release has a bug:
(env) akrug-28119:incidents akrug$ aws_ir -b e-casebucket-1xt5mljpifmvs key-compromise --access-key-id AKIAINLHPIG64YJXPK5A
Traceback (most recent call last):
File "/Users/akrug/workspace/incidents/env/bin/aws_ir", line 7, in
from aws_ir.cli import cli
File "/Users/akrug/workspace/incidents/env/lib/python3.6/site-packages/aws_ir/cli.py", line 11, in
from aws_ir.libs import plugin
File "/Users/akrug/workspace/incidents/env/lib/python3.6/site-packages/aws_ir/libs/plugin.py", line 5, in
from pluginbase import PluginBase
ModuleNotFoundError: No module named 'pluginbase'

Hi, I tried reinstalling aws_ir today via pip, which has the 0.3.0 version still, so I ran into this again. Any ETA when you'll release a version that includes this fix? I'd like to stick to "official" releases for production use, if possible.


Minor typo in blog post

Just came across your Aug 24 post and it would appear it lacks a verb in the opening sentence:

We accidentally a whole hash function… but we had a good reason!

Maybe add "wrote" or "invented" ?

It's a meme. I considered fixing it, but it doesn't seem to hinder comprehension.

Hah, my bad. If it is a meme, got a URL for other uses?

Crikey. Never mind.  A quick Google search on "We accidentally a whole" leads to it, include to the Urban Dictionary.
My bad.  Learn something new every day.


fix for NUTCH-2911 contributed by prakharchaube

Fix for NUTCH-2911
Changes made : Added a wrapper try-finally block for FetcherRun.run() and called cleanup()

Thanks @prakharchaube, good catch. The compilation fails with Fetcher.java:440: error: unreported exception InterruptedException; must be caught or declared to be thrown - could you update the PR to catch the exception thrown by the cleanup method. Thanks!

@sebastian-nagel I have added a catch for InterruptedException, sorry for missing it. I know ideally, we should not catch InterruptedException and simply log it, but the cleanup() call will never throw it in the first place.
Let me know if there are any concerns around this. Thanks.

Hi @prakharchaube, after a second look (sorry about it), you're right.

ideally, we should not catch InterruptedException

Definitely. The overridden Mapper run method declares the InterruptedException to be thrown, so the overriding method should just throw it as well. What do you think?

Yes @sebastian-nagel I do feel that would be the best way to handle it, I noticed even job.waitForCompletion() throws InterruptedException so propagation is intentional, I will make the change and update, thanks.

Done @sebastian-nagel, please review. Thanks!


Branch pe d fixes (STILL FIXING, DONT MERGE)

Bugs fixed :

Incorrect version number , closes #188
Remove alphanumeric regex for TaskTitle and TaskDescription, closes #194

Codecov Report

Merging #195 (28b5771) into master (4bcd6cc) will not change coverage.
The diff coverage is 0.00%.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


feat(useLocalStorage): add remove method. (#229)

Description
Implemented remove method as requested in #229 ;
Reworked a bit implementation of the initialization of useState to make sure not to invoke localStorage.setItem() when localStorage.getItem(key) is null && InitialValue is undefined;
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as before)

Checklist

[x] Read the Contributing Guide
[x] Perform a code self-review
[x] Comment the code, particularly in hard-to-understand areas
[x] Add documentation
[x] Add hook's story at Storybook
[ ] Cover changes with tests
[x] Ensure the test suite passes (yarn test)
[ ] Provide 100% tests coverage
[x] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
[x] Make sure types are fine (yarn lint:types).

:tada: This PR is included in version 15.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ListView links do not work

I am not able to successfully link to another page with the ListView component. The URL is set correctly with the href tag, but no action is taken when a list item is clicked.

I've been stumped by this same issue also - the behaviour seems counterintuitive to me.
FWIW I tried kerwitz's code but it was throwing HTTP errors.  Then I tried Olton's code - while debugging it threw: "JavaScript runtime error: 'list' is undefined", but it does seem to work...

Mike, list is undefined because @olton called the argument _list not list. But still: the argument does not contain the anchor but its parent - so my version should work.
What kind of errors did you get?

I haven't been able to repro those HTTP errors - I guess something else was happening on my side.
Now with kerwitz's code I'm getting the "out-of-the-box" behaviour - the clicked entry just becomes "active" without following the URL.
Maybe I've built my DOM "wrong", but my list is an anchor, e.g.

Google

Hello,
I can not fix this problem please give more information about this solving this problem.


Add sub sampler resnet18

The goal of this PR is to add the SubSamplerResnet18 model which is a derivative of the resnet18 that we want to train on the SubSamplerDataSet of the PR #66

Hi @frgfm , Thanks for your remarks. It is indeed a good idea to generalize to any resnet. Let me know what you think of this new version


If the network connection is faster than the drive speed, memory fills up.

It seems like that when networking and processing are fast enough and the drive where the results are saved becomes the bottleneck, dask continues to download and process chunks without waiting for the disk. This fills up memory and crashes the process at some point.
Current "fix": reduce the number of workers when initiating sentle until memory does not fill up anymore.
Ideal fix: tell dask somehow to wait for disk I/O.

WHAT


Define configuration properties for random forest training with ranger

Specifically to set the desired ranger options:
Usage:
    ./OrbitAI_ranger [options]

Options:
    --help                        Print this help.
    --version                     Print version and citation information.
    --verbose                     Turn on verbose mode.
    --file FILE                   Filename of input data. Only numerical values are supported.
    --treetype TYPE               Set tree type to:
                                  TYPE = 1: Classification.
                                  TYPE = 3: Regression.
                                  TYPE = 5: Survival.
                                  (Default: 1)
    --probability                 Grow a Classification forest with probability estimation for the classes.
                                  Use in combination with --treetype 1.
    --depvarname NAME             Name of dependent variable. For survival trees this is the time variable.
    --statusvarname NAME          Name of status variable, only applicable for survival trees.
                                  Coding is 1 for event and 0 for censored.
    --ntree N                     Set number of trees to N.
                                  (Default: 500)
    --mtry N                      Number of variables to possibly split at in each node.
                                  (Default: sqrt(p) with p = number of independent variables)
    --targetpartitionsize N       Set minimal node size to N.
                                  For Classification and Regression growing is stopped if a node reaches a size smaller than N.
                                  For Survival growing is stopped if one child would reach a size smaller than N.
                                  This means nodes with size smaller N can occur for Classification and Regression.
                                  (Default: 1 for Classification, 5 for Regression, and 3 for Survival)
    --maxdepth N                  Set maximal tree depth to N.
                                  Set to 0 for unlimited depth. A value of 1 corresponds to tree stumps (1 split).
    --catvars V1,V2,..            Comma separated list of names of (unordered) categorical variables.
                                  Categorical variables must contain only positive integer values.
    --write                       Save forest to file <outprefix>.forest.
    --predict FILE                Load forest from FILE and predict with new data. The new data is expected in the exact same
                                  shape as the training data. If the outcome of your new dataset is unknown, add a dummy column.
    --predall                     Return a matrix with individual predictions for each tree instead of aggregated
                                  predictions for all trees (classification and regression only).
    --predictiontype TYPE         Set type of prediction to:
                                  TYPE = 1: Return predicted classes or values.
                                  TYPE = 2: Return terminal node IDs per tree for new observations.
                                  (Default: 1)
    --impmeasure TYPE             Set importance mode to:
                                  TYPE = 0: none.
                                  TYPE = 1: Node impurity: Gini for Classification, variance for Regression, sum of test statistic for Survival.
                                  TYPE = 2: Permutation importance, scaled by standard errors.
                                  TYPE = 3: Permutation importance, no scaling.
                                  TYPE = 5: Corrected node impurity: Bias-corrected version of node impurity importance.
                                  TYPE = 6: Local (casewise) permutation importance.
                                  (Default: 0)
    --noreplace                   Sample without replacement.
    --fraction X                  Fraction of observations to sample. Default is 1 for sampling with replacement
                                  and 0.632 for sampling without replacement.
    --splitrule RULE              Splitting rule:
                                  RULE = 1: Gini for Classification, variance for Regression, logrank for Survival.
                                  RULE = 2: AUC for Survival, not available for Classification and Regression.
                                  RULE = 3: AUC (ignore ties) for Survival, not available for Classification and Regression.
                                  RULE = 4: MAXSTAT for Survival and Regression, not available for Classification.
                                  RULE = 5: ExtraTrees for all tree types.
                                  RULE = 6: BETA for regression, only for (0,1) bounded outcomes.
                                  RULE = 7: Hellinger for Classification, not available for Regression and Survival.
                                  (Default: 1)
    --randomsplits N              Number of random splits to consider for each splitting variable (ExtraTrees splitrule only).
    --alpha VAL                   Significance threshold to allow splitting (MAXSTAT splitrule only).
    --minprop VAL                 Lower quantile of covariate distribtuion to be considered for splitting (MAXSTAT splitrule only).
    --caseweights FILE            Filename of case weights file.
    --holdout                     Hold-out mode. Hold-out all samples with case weight 0 and use these for variable
                                  importance and prediction error.
    --splitweights FILE           Filename of split select weights file.
    --alwayssplitvars V1,V2,..    Comma separated list of variable names to be always considered for splitting.
    --includevars V1,V2,..        Comma separated list of variable to include when training or predicting.
    --regcoef r1,r2,..            Comma separated list of regularization coefficients (one for all variables or one for each variable).
    --usedepth                    Use node depth for regularization.
    --skipoob                     Skip computation of OOB error.
    --nthreads N                  Set number of parallel threads to N.
                                  (Default: Number of CPUs available)
    --seed SEED                   Set random seed to SEED.
                                  (Default: No seed)
    --outprefix PREFIX            Prefix for output files.
    --memmode MODE                Set memory mode to:
                                  MODE = 0: double.
                                  MODE = 1: float.
                                  MODE = 2: char.
                                  (Default: 0)
    --savemem                     Use memory saving (but slower) splitting mode.

We should load as much of those parameters as possible from the app configuration file and only pass from the Java app the ones that are runtime depend like --file.

@TanguySoto agreed. So OK to leave it to you to build the OrbitAI_ranger command string that will be invoked from the NMF app?

Refer to new properties file:
https://github.com/georgeslabreche/opssat-orbitai/blob/main/nmf/space-app/conf/orbit_ai_v2.properties


CS9057 warning from Microsoft.CodeAnalysis.CSharp.CodeStyle in all projects

I'm seeing warning CS9057 in all the projects that build in net8.0, netstandard2.0 or net462:
The analyzer assembly 'C:\Program Files\dotnet\sdk\9.0.100-alpha.1.24068.28\Sdks\Microsoft.NET.Sdk\codestyle\cs\Microsoft.CodeAnalysis.CSharp.CodeStyle.dll' references version '<IP_ADDRESS>' of the compiler, which is newer than the currently running version '<IP_ADDRESS>'.

Do we supress it, for example, in the root Directory.Build.props <NoWarn> property, or is this something we need to address by forcing the usage of version <IP_ADDRESS> in projects building in any tfm lower than 9.0?
@ericstj @ViktorHofer

Where do you see those warnings? I just tried to reproduce on Codespaces when building with build.sh and no warnings were emitted. I also looked at https://github.com/dotnet/maintenance-packages/pull/36 which doesn't have those warnings in CI.
Is that warning only emitted inside VS? If yes, did you open vs with the -vs switch?

I didn't know -vs was available in maintenance-packages. I did not open it that way. I opened it using devenv .\MaintenancePackages.sln from the console.
I tried .\build.cmd -vs MaintenancePackages.sln, but I still see the failure in the Error output window.
I can confirm this only happens in VS. The warning shows up in the Error output window, and when building from VS, I see the warning being treated as error.
Note: I'm using Visual Studio 2022 Preview, not Int Preview. Does that matter?
I also downloaded the latest nightly 9.0 SDK and installed it globally, but that didn't do anything.

9.0.100-alpha.1.24068.28

IMO we should not be using 9.0 SDK in this repo.  We should be consuming the .NET 8 arcade instead, which should be on stable 8.0 SDK.

we should not be using 9.0 SDK in this repo

I suspect that's also the reason why $(NetMinimum) is showing up as net8.0 instead of net6.0.
I'll do the downgrade on Monday.

I suspect that's also the reason why $(NetMinimum) is showing up as net8.0 instead of net6.0.

Correct: https://github.com/dotnet/arcade/blob/abddd0bd5145578246dcadda264c7557f2a935a9/src/Microsoft.DotNet.Arcade.Sdk/tools/TargetFrameworkDefaults.props#L22

This should get fixed after merging https://github.com/dotnet/maintenance-packages/pull/41


An error occurred during installation. Distribution Name: 'Ubuntu' Error Code: 0x8007041d

Windows Version
Microsoft Windows [Version 10.0.22621.3958]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[ ] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps

Expected Behavior

Actual Behavior

Diagnostic Logs
No response
### Tasks

WslLogs-2024-08-16_22-17-20.zip

/logs


chore(main): release 0.16.2

:robot: I have created a release beep boop
0.16.2 (2024-04-11)
Bug Fixes

watch later pop invalid rounded corners (#505) (36960da)
moment card url not linking the video page

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/hakadao/BewlyBewly/releases/tag/v0.16.2 :sunflower:


Installing zef is not possible

As of beta 29, installing zef does not proceed.

Thankfully this actually turns out to be a false positive!


MC Eternal - Ender IO - Dark Steel Armor - Sound Looping\Distorted

Mod Version:
1.12.2-<IP_ADDRESS>
Forge Version:
<IP_ADDRESS>47
Description:
While playing MC Eternal I found that adding the "Padding" modifier to EnderIO's Dark Steel armor caused sounds in the game to loop and become distorted. This can be recreated by wearing the dark steel armor with the modifer applied and walking up to a water fall. The sound will be distorted and after walking away many of the normal sounds like footsteps will not play at all. Additionally while wearing the armor many normal sounds such as machine sounds will loop and become louder and louder. Restarting the game will clear the issue but only for a short time.

Did you just add the mod to a pack? N
Did it just start crashing, or has it always crashed? Not crashing
Did you update any other mods in your pack and it started crashing?  This includes Forge. No
If updating multiple mods did you update one by one or all at once?  To help narrow the problem down adding one by one is helpful. N/A
Is the modpack you are using available online somewhere?  If the crash is due to mod interaction having the pack available makes things much easier.  It is much harder to work these types of issues with a private kitchen sink pack containing 250 mods.

It should also be noted that the Padding modifier is supposed to muffle sounds so in hindsight makes sense that it may not mesh well.
From the EnderIO Wiki:
Dark Steel Upgrade "Padding"
Crafted with a Blank Upgrade and a piece of Wool
Upgrade for Dark Steel Items
Muffles nearby sound
Can be applied to:
Dark, Ender, and Stellar Helmets

Yeah - sound modifiers like this are hard to deal with.  With the way Forge integrates with the sound system, a mod can intercept a sound play request, cancel it, and replace it with a different sound.  When this happens to a DS initiated sound, DS thinks that the sound finished playing or failed submission.  If this is a looping sound effect DS could think it finished playing and then resubmit the sound.  Distortion comes in because there is a limit to the number of sounds MC sound engine can handle.  When this list gets full sounds can get choppy.

Thanks @OreCruncher, I was playing with this a bit further and I believe this is related to a crash I experience while going to "The Midnight." To reproduce this:

Start a new game and equip EnderIO's Dark Helmet with the "Padding" modifier equipped.
Set time to night.
Find one of the Midnight portals and go through the portal.
Within 30 seconds the game will freeze.

Here is one of the crash logs that would actually upload. Seems some of my others are too big to upload. https://paste.ee/p/BesGM
Thanks for your work on this mod. It brings a whole new level of detail to modded minecraft!

Caused by: java.lang.IndexOutOfBoundsException: readerIndex(4) + length(1) exceeds writerIndex(4): UnpooledSlicedByteBuf(ridx: 4, widx: 4, cap: 4/4, unwrapped: PooledUnsafeDirectByteBuf(ridx: 0, widx: 5, cap: 5))
    at io.netty.buffer.AbstractByteBuf.checkReadableBytes0(AbstractByteBuf.java:1396)
    at io.netty.buffer.AbstractByteBuf.readByte(AbstractByteBuf.java:687)
    at com.mushroom.midnight.common.entity.RiftBridge.handleState(RiftBridge.java:150)
    at com.mushroom.midnight.common.network.MessageBridgeState$Handler.lambda$onMessage$0(MessageBridgeState.java:47)
    at com.mushroom.midnight.client.ClientProxy.lambda$handleMessage$1(ClientProxy.java:39)
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at net.minecraft.util.Util.runTask(SourceFile:529)

I think the Midnight Portal mod has a problem handling some IO packets.


Fix issue with Bad state: No element

This issue happens when there is empty element. Using another PR #53 but with merge conflict resolved.

@kwiliodev There's a semicolon at line number 313.


Stata 17 Jupyter environment fails on build

Steps to Reproduce
Start a whole tale environment with Stata 17 Jupyter
Expected Results
The whole tale builds
Actual Results
There is a build error having to do with Dockerfile parse error line 184: Unknown flag: mount
Please let me know if I'm doing something wrong here! I'm not adding any files to the environment before running the tale.

Thanks for reporting this issue.  We just moved to new hosting infrastructure and it looks like I missed a configuration setting.   I'm testing now  and will update this issue when I've confirmed its working.

I've confirmed that I'm able to build and run a Stata 17/Jupyter environment. Let me know if you encounter any further issues.

Can confirm that it builds now, thank you!