adding fixed property to parameterized

As per Alex's request, #94
You can now do something like
m = GPflow.gpr.GPR(X, Y, kern=GPflow.kernels.Matern32(1))
m.fixed  # is False
m.kern.lengthscales.fixed = True  # works as before
m.kern.fixed = True
m.kern.lengthscales.fixed  # still True
m.kern.variance.fixed # now True
m.likelihood.fixed # still False

Looks good. Thank you.


Bugfixes

Here's our current list of top 10 bugs from https://webtorrent.io/desktop/telemetry/:

Count
Example message
Status

2104
[object Object]
No idea, no stacktrace

632
[object HTMLVideoElement]
No idea, no stacktrace

359
Cannot read property 'getHostNode' of null
Happens after a React component throws an error in render(). Will go away by itself once we fix those errors, logged separately.

284
Failed to set the 'currentTime' property on 'HTMLMediaElement': The provided double value is non-finite.
Fixed in this PR

78
Cannot read property '0' of undefined
Fixed in this PR

62
Illegal wire type for field Message.Field...
Filed: https://github.com/thibauts/node-castv2/issues/35

59
torrent is destroyed
Bug in webtorrent.js, already filed

51
You can't connect to dlna when already connected to another device
Np. Comes from our own UI; should just use addError instead of throwing an uncaught exception.

48
val is not defined
Filed: https://github.com/thibauts/node-castv2/issues/36

47
Cannot read property 'message' of undefined
Bug in older version of WebTorrent, can't happen in the current telemetry.js

@feross

LGTM!

This is amazing. Telemetry is extremely usefu! It would have taken forever to fix these issues without this, waiting for issues to get filed.


Upgrade package references and react to corefx API changes

Mostly rename changes from bufferpool to memorypool, except here https://github.com/aspnet/KestrelHttpServer/pull/2212/files#diff-a8cc42c3f89e3b75135621f243f98896R34


Fixed file

Add the possibility to call always the same file whatever the url is.
It's useful to starting simple SAP software without getting mess with something like ngins.
Thank you!

not sure I fully understand, can you elaborate more with some concrete examples?

Yeah so, i got this SAP (Single Application Software). It has only a "index.html" file and nothing else.
The index.html file runs a js script who parse the url and provide the right informations.
For example:
example.com -> example.com/index.html
example.com/home -> example.com/index.html (parsing /home and finding right informations)
example.com/hub -> example.com/index.html (parsing /hub and finding right informations)
example.com/settings -> example.com/index.html (parsing /settings and finding right informations)
and so on
Right now, if i call example.com/home it just reply 404 because obviously that file dosen't exist, it's dynamically generated.

The best things is probably:
IF (url has an extension):
return the file requested
ELSE:
return index.html
END

#20 Here is a really basic, simple solution

@harshavardhana  May you publish a new version on docker hub?

@harshavardhana May you publish a new version on docker hub?

Soon @Sipioteo


fix(connector): show error component

Description
show appropriate error component based on response status
Why
error handling functionality is missing
Issue
#758
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines
[ ] I have performed IP checks for added or updated 3rd party libraries
[ ] I have created and linked IP issues or requested their creation by a committer
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally
[ ] I have added tests that prove my changes work
[ ] I have checked that new and existing tests pass locally with my changes
[ ] I have commented my code, particularly in hard-to-understand areas

Created new PR and change base to release branch


Update typings

Add typings for Args in useAsyncTask function.

Published: https://www.npmjs.com/package/react-hooks-async/v/3.6.1


[Feature Request] Make the root slash easier to click on

I really like using the inline title to navigate back to the upper folder or sibling files, but for me, the most important selection is the hardest. To select the root I'd have to aim at the measly forward slash at the start of the path. It'd be great if there was a name before it (maybe the vault's name) or just a bigger area to its left to make clicking on it smoother. Awesome work on the plugin!

Have you tried using the "Quick Explorer: Browse Vault" command?  You can set a hotkey for it, or use another plugin (such as Commander) to add a header button for it.

Oh that's a great idea! I used the DoubleShift plugin to assign it to double alt and now it's so easy to navigate the entire tree. I knew Quick Explorer had good keyboard support but I didn't know it was even faster than the mouse. Nice!

It's a bug - fixed in 0.2.8.  The "no file is open" view is not a standard FileView, that's what was throwing it off.  I didn't see the issue in 0.15.9 because on 0.15.9 there's no path in the view header, so there was no problem there.

Sorry for replying so late, but I think this bug is still there. Running the "Browse vault" command on a new tab doesn't do anything. That sort of makes sense because there is no address in the title bar on a new tab page.

It works fine for me on Obsidian 1.1.10, even with Hidden Frame or Native Frame mode, no tab headers, and Style Settings configured to hide Quick Explorer entirely.  It just cascades from the upper left of the display, as it's supposed to.

Ok I created a brand new vault to make sure. Here's what I did:

Installed Quick Explorer
Installed Styler and enabled Hide Quick Explorer
opened a new tab and tried the Browse vault command.
I guess you have it disabled?

I enabled it for the test (using the Style Settings plugin, not familiar with "Styler".  You didn't mention what Obsidian version you're using, either.

Yes, sorry, Style Settings plugin. Running version 1.1.9.
I looked at the console log and it seems like there's an error when running the Browse Vault command:
Uncaught TypeError: Cannot read properties of null (reading 'containerEl')
    at A.visibleCrumb (plugin:quick-explorer:1:33483)
    at A.folderMenu (plugin:quick-explorer:1:33710)
    at A.browseVault (plugin:quick-explorer:1:33776)
    at Object.callback (plugin:quick-explorer:1:36563)
    at XN (app.js:1:1502974)
    at t.onChooseItem (app.js:1:1836164)
    at t.onChooseSuggestion (app.js:1:1726362)
    at t.selectSuggestion (app.js:1:1725912)
    at e.useSelectedItem (app.js:1:1539277)
    at Object.func (app.js:1:1537992)

When clicking on the root slash in the inline title at the top:
Uncaught TypeError: Cannot read properties of undefined (reading 'file')
    at fe (plugin:quick-explorer:1:35265)
    at register.I.capture (plugin:quick-explorer:1:32056)
    at HTMLBodyElement.s (enhance.js:1:10270)
fe	@	plugin:quick-explorer:1
register.I.capture	@	plugin:quick-explorer:1
s	@	enhance.js:1

Do you have Quick Explorer 0.2.8?

No, it was 0.2.7. It just updated and finally works!
I'm so confused though, why would it wait an entire month to update? I press the check for updates button every day.
The newly created testvault also downloaded 0.2.7 just yesterday. But when I checked for updates today, both vaults updated.
Well, thanks for your help anyway! I'm still super confused why this happened haha


Open database in ADS

Working with the data teams to get this designed

Closing since this work isn't being continued any more.


Template is unlicensed

Please add the appropriate license for ease of use as a template.
From the GitHub guidance on licensing:

You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The Open Source Guide provides additional guidance on choosing the correct license for your project.

Thanks for the issue! I have added MIT License now


[Bug] SSL initialization errors when having TLS ports without TLS configs

Search before asking

[X] I searched in the issues and found nothing similar.

Read release policy

[X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version
4.0.0-preview.1
Minimal reproduce step
Configure a broker with TLS deactivated but TLS port defined.
What did you expect to see?
Nothing wrong (as in the previous version).
What did you see instead?
https://gist.githubusercontent.com/KannarFr/fa521bf61e92d8801a08d7505e9c9b2c/raw/0690469c7c05d93a91da92f3f4d7e3620c600157/gistfile1.txt
Anything else?
Set empty in TLS ports fixes the issue.
Probably related to https://github.com/apache/pulsar/blob/master/pip/pip-337.md.
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Could you provide your TLS config?
It looks like the tlsCertificateFilePath is missing.

@KannarFr Pulsar considers SSL enabled if the TLS ports are specified in the configuration. Prior to PIP-337, it would not load the SSL Context till the first incoming connection on the TLS port. This could lead to runtime errors and would mask the misconfiguration. Hence, the change was made to initialize the SSL Context at startup itself to fail fast in case of SSL mis-configuration issues.

PIP-337 improves the TLS feature, which can help you find the TLS config's error.

It is and it was missing, it just breaks current configurations with port activated but not other configuration keys.

tlsCertificateFilePath is required in the broker server.

@Apurva007 yup, this is my point, a breaking change. I have no problem with it, but it should be highlighted.

@KannarFr Makes sense. @lhotari / @nodece  is there a way we could highlight this via documentation or release notes?

@KannarFr Makes sense. @lhotari / @nodece is there a way we could highlight this via documentation or release notes?

@Apurva007 We don't currently have a proper process for release notes. In the meantime, you can add the content as a comment to this issue or reference for example a GitHub Gist url with the content. During the release of 4.0.0, I'll be looking closely to all issues labeled as release/blocker and ensure that I handle them.
As an improvement to the release notes, I've made a proposal a long time ago which would address this. While creating PRs, there should be a release notes staging directory where each PR that contributes to release notes would add a markdown file. During the release, these release notes files could be easily merged into the release notes. After 4.0.0, I'll make a PIP for this that we finally fix the problem we have with release notes and editorial content for it. The current PR naming helps with the changelog, but there's no way to handle the content management of written content for the release notes.

This is not a breaking change. In the old version, your broker starts fine, but the TLS port doesn't work.
In the new version, your broker starts failed, because you don't setup tlsCertificateFilePath in the broker.conf.


Rip out rethink readiness probe

See issue: https://github.com/pachyderm/pachyderm/issues/801
for more context


Is the s-value in ash intended to be compared to q-values?

By 9/22/17, reread the ash paper and weigh in on whether it is appropriate to interpret the s-values as q-values? Preliminary results on simulated data (from @stephaniehicks and @pkimes) show that it is very different than the other FDR benchmark methods.

@pkimes were just looking at the simulations in the ash vignette and noticed a few things that may help us determine what is going on:

When you set pi0 to 1 (all nulls) in the ash vignette, the lsfdr values and s-values get pushed toward 1
These simulations directly simulate the effect sizes and standard errors themselves (not the data points)
The input to ash is (1) the simulated beta plus random noise and (2) the ground truth standard errors

thanks, @kdkorthauer!
also, to give a little more context, @kdkorthauer was looking at this vignette:
https://github.com/stephens999/ashr/blob/master/vignettes/adaptive_shrinkage.Rmd
and she saw that ASH was performing "as expected" according to the sims in the vignette (vs. the behavior we were seeing in our simulations).
We're still trying to figure out why the vignette's simulations look so different...

I think the difference in the ash vignette simulations and our simulations was that our calculation of SE was assuming that pooled variance for the t-test is equal to the variance estimate ignoring group (see lines 47-48 here). If we replace that with the standard 2-sample t-test standard error, the lfsr and s-value no longer appear to be severely shrunk toward zero.
tldr: If we give ash underestimated values for SE, it is not able to properly shrink the effect size estimates and makes many false discoveries. I made a branch with the proposed SE estimate change and submitted a pull request.

Just re-ran my simulations, and things look a lot better. Thanks @kdkorthauer!

Great!
I didn't change the calculation of the sds - this is still computed ignoring group - which is used as the independent covariate in some of the other methods. I'm not sure if the other methods assume anything about the type of SD, other than it has to be independent under the null, or if changing it to a pooled calculation would make any difference, but something we should think about.

To be consistent, maybe we should change sds too.
I also just checked the papers, and IHW mentions: for the t-test, "the pooled sample variance was used as the covariate." It doesn't look like BL or FDRreg considered sample variance as an independent covariate.

did we ever do anything about this (i.e. changing the sds to match SE)?

I only changed the SE calculation since it was affecting the ash results.
I would lean toward keeping the SD calculation as it is in the du_ttest_sim function of the IHWpaper package since this seems like the covariate they recommend for use as an independent covariate. To be clear on the terminology here, this is an SD ignoring sample group (rather than a 'pooled' calculation which would combine the two within-group SDs).

Makes sense - unfortunate that the wrong wording is used in the IHW paper...


Does not compile for ARM devices: undefined: sers.Open

$ GOOS=linux GOARCH=arm GOARM=7 go build -o=vaisala.bin .
# github.com/soypat/cereal
../../../go/pkg/mod/github.com/soypat/cereal@v0.0.0-20230618213158-ce082d3b2e3e/cereal.go:160:18: undefined: sers.Open

Thanks, was able to compile like that. Just had to run sudo apt install gcc-arm-linux-gnueabi beforehand :ok_hand:


Remove switching to HOLD mode before arm and takeoff

This removes most of the workaround where we switch to HOLD before arming. This was mostly out of precaution but as discussed in #50 it can hopefully safely get dropped now.
This also includes some refactoring and cleanup of the action plugin.
For reviewing, please check the individual commits and messages.
Fixes #50, fixes #614, fixes #855.

Ignore appveyor, it's timing out in Debug. I'll remove that in another PR.


Tooltips get cutoff when used in horizontal table

Framework Version: 3.0.1
Flavor used: default
Operating System/Browser: Chrome/Mac OS
Code to reproduce: https://codepen.io/erikschierboom/pen/ZEEPWdw

Reproduce by hovering over the "Text #1.1", "Text #1.2", or "Text #2.1" texts inside the table.

Screenshots:

Bug description:

When using tooltips in a horizontal table, the tooltips are cutoff on the border of the table. I'd like for the tooltips to be displayed in their entirety.

Same issue here. I also tried to experiment with different z-index but hat no success.
Any update on this issue?


I found a strange problem in the latest edition.

Client B subscribes to a/cmd. I want Client A to send a message to the server. The server pushes the message from Client A to a/cmd, forwards it, and sends it directly to MqttServer_Application MessageReceived as if it would not receive the message. But I push the message through the button to subscribe to a/cmd, and I can send it successfully.
The following code cannot be forwarded to other clients.
private   void MqttServer_ApplicationMessageReceived(object sender, MqttApplicationMessageReceivedEventArgs e)
{
if (e.ClientId == null || e.ClientId == "")
{
return;
}
        mqttServer.PublishAsync(new MqttApplicationMessageBuilder().WithTopic(e.ApplicationMessage.Topic).WithPayload(e.ApplicationMessage.Payload).Build());

    }

The following code is OK. I think the two should be exactly the same. I don't know why.
private async void button1_Click(object sender, EventArgs e)
{
await  mqttServer.PublishAsync(new MqttApplicationMessageBuilder().WithTopic(textBox1.Text).WithPayload(textBox2.Text).Build());
    }

Hi,
they are not the same. Missing the async keyword leads to strange behavior. Please use the first way using ...GetAwaiter().GetResult() if you want to avoid async/await.
Best regards
Christian

I will close this issue by now. As @chkr1011 already told you, @bbhxwl: These are definitely not the same.


[Android] MainActivity has leaked IntentReceiver

🐛 Bug Report
It reports MainActivity has leaked IntentReceiver com.baseflow.geolocator.location.LocationServiceStatusReceiver, when exiting the app.
Expected behavior
Call unregisterReceiver() when exiting the app.
Reproduction steps

Checkout the example project
Build the example project
Run the example app
Exit the app

Error log in the console:
E/ActivityThread(17969): Activity com.baseflow.geolocator_example.MainActivity has leaked IntentReceiver com.baseflow.geolocator.location.LocationServiceStatusReceiver@10738ec that was originally registered here. Are you missing a call to unregisterReceiver()?
E/ActivityThread(17969): android.app.IntentReceiverLeaked: Activity com.baseflow.geolocator_example.MainActivity has leaked IntentReceiver com.baseflow.geolocator.location.LocationServiceStatusReceiver@10738ec that was originally registered here. Are you missing a call to unregisterReceiver()?
E/ActivityThread(17969): 	at android.app.LoadedApk$ReceiverDispatcher.<init>(LoadedApk.java:1717)
E/ActivityThread(17969): 	at android.app.LoadedApk.getReceiverDispatcher(LoadedApk.java:1494)
E/ActivityThread(17969): 	at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1757)
E/ActivityThread(17969): 	at android.app.ContextImpl.registerReceiver(ContextImpl.java:1723)
E/ActivityThread(17969): 	at android.app.ContextImpl.registerReceiver(ContextImpl.java:1711)
E/ActivityThread(17969): 	at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:724)
E/ActivityThread(17969): 	at com.baseflow.geolocator.LocationServiceHandlerImpl.onListen(LocationServiceHandlerImpl.java:57)
E/ActivityThread(17969): 	at io.flutter.plugin.common.EventChannel$IncomingStreamRequestHandler.onListen(EventChannel.java:218)
E/ActivityThread(17969): 	at io.flutter.plugin.common.EventChannel$IncomingStreamRequestHandler.onMessage(EventChannel.java:197)
E/ActivityThread(17969): 	at io.flutter.embedding.engine.dart.DartMessenger.invokeHandler(DartMessenger.java:178)
E/ActivityThread(17969): 	at io.flutter.embedding.engine.dart.DartMessenger.lambda$handleMessageFromDart$0$DartMessenger(DartMessenger.java:206)
E/ActivityThread(17969): 	at io.flutter.embedding.engine.dart.-$$Lambda$DartMessenger$6ZD1MYkhaLxyPjtoFDxe45u43DI.run(Unknown Source:12)
E/ActivityThread(17969): 	at android.os.Handler.handleCallback(Handler.java:938)
E/ActivityThread(17969): 	at android.os.Handler.dispatchMessage(Handler.java:99)
E/ActivityThread(17969): 	at android.os.Looper.loopOnce(Looper.java:201)
E/ActivityThread(17969): 	at android.os.Looper.loop(Looper.java:288)
E/ActivityThread(17969): 	at android.app.ActivityThread.main(ActivityThread.java:7839)
E/ActivityThread(17969): 	at java.lang.reflect.Method.invoke(Native Method)
E/ActivityThread(17969): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
E/ActivityThread(17969): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)
Application finished.

Configuration
Version: 8.0.0
Platform:

[ ] :iphone: iOS
[x] :robot: Android

Thanks for reporting your issue @hahastudio. I can't manage to reproduce your issue. Can you please provide me your flutter doctor -v and which device you're using?
I have an idea why this error occurs. In the stopListening method in the LocationServiceHandlerImpl class, the Receiver is never unregistered, when the app suddenly stops (The stopListening method is called when the application is de-attached from the FlutterEngine). The Receiver is only getting unregistered when manually cancelling the LocationServiceStatusStream in your code. When this issue is affecting the performance of your app, you can try forking the geolocator repo and changing the stopListening method yourself from:
void stopListening(){
        if(channel == null){
            return;
        }
        channel.setStreamHandler(null);
        channel = null;
    }

To:
void stopListening(){
        if(channel == null){
            return;
        }
        if(activity != null){
           activity.unregisterReceiver(this.receiver);
        }
        channel.setStreamHandler(null);
        channel = null;
    }

Another solution would be to cancel the LocationServiceStatusStream in f.e. your main.dart when the app is closed. You can realise this by making use of the Flutter Lifecycle events, such as onDestroy.
I'm not sure if this will do the trick, but you can always try. I can't discuss your issue with the main author of the geolocator plugin, since the holidays are coming. Let me know if this fixes your issue!

@florissmit1 thx for your reply!
Here is the output of flutter doctor -v:
[✓] Flutter (Channel stable, 2.8.1, on macOS 12.0.1 21A559 darwin-x64, locale zh-Hans-CN)
    • Flutter version 2.8.1 at /Users/hahastudio/Projects/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (7 天前), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0-rc1)
    • Android SDK at /Users/hahastudio/Library/Android/sdk
    • Platform android-31, build-tools 32.0.0-rc1
    • ANDROID_HOME = /Users/hahastudio/Library/Android/sdk
    • ANDROID_SDK_ROOT = /Users/hahastudio/Library/Android/sdk
    • Java binary at: /Library/Java/JavaVirtualMachines/adoptopenjdk-13.jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment AdoptOpenJDK (build 13.0.2+8)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

[✓] VS Code (version 1.63.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.29.0

[✓] Connected device (3 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 12 (API 31) (emulator)
    • macOS (desktop)              • macos         • darwin-x64     • macOS 12.0.1 21A559 darwin-x64
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 96.0.4664.110

• No issues found!

I tried to modify LocationServiceHandlerImpl in geo_android like you said, and it can resolve the issue.
But about canceling the LocationServiceStatusStream, I tried to dispose _serviceStatusStreamSubscription like _positionStreamSubscription in the example project, but it still throw the same exception.


fix: header alignment for Events page #626

Related Issue
Closes: #626
Describe the changes you've made ✍

Class "cp_textdiv" and "shop_textdiv" adjusted with an additional 10% width to fit the first header in one line.

The class above applies to clubs, events and shop pages which had this similar layout issue.
Screenshots (if any) 📸

Hi @IAmTamal,
in my opinion this is the simplest solution, only one thing bothers me: it is not consistent accross the website since the shop page has a class "shop_textdiv" with a width of 70%. it would be better to add 10% to this one as well. what do you think?

Okay, it is aligned now on the three pages.


"MSB4036: The "RazorGenerate" task was not found" when building Blazor client project

Problem
Unable to build a Blazor project based on the ASP.NET Core template: "Blazor (ASP.Net Core hosted)"
Error message
error MSB4036: The "RazorGenerate" task was not found. Check the following:

The name of the task in the project file is the same as the name of the task class.
The task class is "public" and implements the Microsoft.Build.Framework.ITask interface.
The task is correctly declared with  in the project file, or in the *.tasks files located in the "C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin" directory.

Complete build output
1>------ Rebuild All started: Project: BlazorTest.Shared, Configuration: Debug Any CPU ------
1>C:\Program Files\dotnet\sdk\3.0.100-preview3-010431\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(151,5): message NETSDK1057: You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
1>BlazorTest.Shared -> C:\Code\BlazorTest.Shared\bin\Debug\netstandard2.0\BlazorTest.Shared.dll
2>------ Rebuild All started: Project: BlazorTest.Client, Configuration: Debug Any CPU ------
2>C:\Program Files\dotnet\sdk\3.0.100-preview3-010431\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.Component.targets(93,5): error MSB4036: The "RazorGenerate" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin" directory.
2>Done building project "BlazorTest.Client.csproj" -- FAILED.
3>------ Rebuild All started: Project: BlazorTest.Server, Configuration: Debug Any CPU ------
3>CSC : error CS0006: Metadata file 'C:\Code\BlazorTest.Client\bin\Debug\netstandard2.0\BlazorTest.Client.dll' could not be found
3>Done building project "BlazorTest.Server.csproj" -- FAILED.
========== Rebuild All: 1 succeeded, 2 failed, 0 skipped ==========

Client project file
<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netstandard2.0</TargetFramework>
    <OutputType>Exe</OutputType>
    <RestoreAdditionalProjectSources>
      https://dotnet.myget.org/F/aspnetcore-dev/api/v3/index.json;
      https://dotnet.myget.org/F/blazor-dev/api/v3/index.json;
    </RestoreAdditionalProjectSources>
    <LangVersion>7.3</LangVersion>
    <RazorLangVersion>3.0</RazorLangVersion>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Blazor" Version="3.0.0-preview4-19216-03" />
    <PackageReference Include="Microsoft.AspNetCore.Blazor.Build" Version="3.0.0-preview4-19216-03" PrivateAssets="all" />
  </ItemGroup>
  <ItemGroup>
    <ProjectReference Include="..\BlazorTest.Shared\BlazorTest.Shared.csproj" />
  </ItemGroup>
</Project>

Comparing the project file with an older Blazor project which builds
In my older working Blazor project I can see references to these NuGet packages, in additions to the two Blazor packages.
Microsoft.AspNetCore.Components" Version="3.0.0-preview3-19153-02"
Microsoft.NETCore.Platforms" Version="3.0.0-preview3.19128.7"

Output from: Install-Package -Verbose
PM> $pkgs = Get-Package -ProjectName BlazorTest.Client
PM> $pkgs | %{"`n`n= = = = = START - Package: $_ = = = = = = "; Install-Package -Id $($_.Id) -Version $($_.Versions)    -ProjectName BlazorTest.Client -Verbose; "= = = = = STOP - Package: $_ = = = = = = `n`n";}

= = = = = START - Package: NuGet.PackageManagement.PowerShellCmdlets.PowerShellInstalledPackage = = = = = =
Running restore with 4 concurrent jobs.
Reading project file C:\Code\BlazorTest.Client\BlazorTest.Client.csproj.
Persisting no-op dg to C:\Code\BlazorTest.Client\obj\BlazorTest.Client.csproj.nuget.dgspec.json
Restoring packages for C:\Code\BlazorTest.Client\BlazorTest.Client.csproj...
Restoring packages for .NETStandard,Version=v2.0...
Resolving conflicts for .NETStandard,Version=v2.0...
Checking compatibility of packages on .NETStandard,Version=v2.0.
Checking compatibility for BlazorTest.Client 1.0.0 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Blazor.Build 3.0.0-preview4-19216-03 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Blazor 3.0.0-preview4-19216-03 with .NETStandard,Version=v2.0.
Checking compatibility for NETStandard.Library 2.0.3 with .NETStandard,Version=v2.0.
Checking compatibility for BlazorTest.Shared 1.0.0 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Blazor.Mono 0.10.0-preview-20190325.1 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Components.Browser 3.0.0-preview4-19216-03 with .NETStandard,Version=v2.0.
Checking compatibility for Mono.WebAssembly.Interop 3.0.0-preview4.19216.2 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.NETCore.Platforms 1.1.0 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Components 3.0.0-preview4-19216-03 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.Extensions.DependencyInjection 3.0.0-preview4.19216.2 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.JSInterop 3.0.0-preview4.19216.2 with .NETStandard,Version=v2.0.
Checking compatibility for System.ComponentModel.Annotations 4.6.0-preview4.19212.13 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.Extensions.DependencyInjection.Abstractions 3.0.0-preview4.19216.2 with .NETStandard,Version=v2.0.
All packages and projects are compatible with .NETStandard,Version=v2.0.
Installing NuGet package Microsoft.AspNetCore.Blazor.Build 3.0.0-preview4-19216-03.
Committing restore...
Assets file has not changed. Skipping assets file writing. Path: C:\Code\BlazorTest.Client\obj\project.assets.json
Writing cache file to disk. Path: C:\Code\BlazorTest.Client\obj\BlazorTest.Client.csproj.nuget.cache
Restore completed in 45.06 ms for C:\Code\BlazorTest.Client\BlazorTest.Client.csproj.
Running restore with 4 concurrent jobs.
Reading project file C:\Code\BlazorTest.Server\BlazorTest.Server.csproj.
The restore inputs for 'BlazorTest.Server' have not changed. No further actions are required to complete the restore.
Committing restore...
Assets file has not changed. Skipping assets file writing. Path: C:\Code\BlazorTest.Server\obj\project.assets.json
No-Op restore. The cache will not be updated. Path: C:\Code\BlazorTest.Server\obj\BlazorTest.Server.csproj.nuget.cache
Restore completed in 15.64 ms for C:\Code\BlazorTest.Server\BlazorTest.Server.csproj.

NuGet Config files used:
    C:\Users\xxxxx\AppData\Roaming\NuGet\NuGet.Config
    C:\Program Files (x86)\NuGet\Config\Microsoft.VisualStudio.Offline.config
    C:\Program Files (x86)\NuGet\Config\Xamarin.Offline.config

Feeds used:
    https://api.nuget.org/v3/index.json
    C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\
    https://dotnet.myget.org/F/aspnetcore-dev/api/v3/index.json
    https://dotnet.myget.org/F/blazor-dev/api/v3/index.json
Executing nuget actions took 76.96 ms
Time Elapsed: 00:00:01.4167282
= = = = = STOP - Package: NuGet.PackageManagement.PowerShellCmdlets.PowerShellInstalledPackage = = = = = =

= = = = = START - Package: NuGet.PackageManagement.PowerShellCmdlets.PowerShellInstalledPackage = = = = = =
Running restore with 4 concurrent jobs.
Reading project file C:\Code\BlazorTest.Client\BlazorTest.Client.csproj.
Persisting no-op dg to C:\Code\BlazorTest.Client\obj\BlazorTest.Client.csproj.nuget.dgspec.json
Restoring packages for C:\Code\BlazorTest.Client\BlazorTest.Client.csproj...
Restoring packages for .NETStandard,Version=v2.0...
Resolving conflicts for .NETStandard,Version=v2.0...
Checking compatibility of packages on .NETStandard,Version=v2.0.
Checking compatibility for BlazorTest.Client 1.0.0 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Blazor.Build 3.0.0-preview4-19216-03 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Blazor 3.0.0-preview4-19216-03 with .NETStandard,Version=v2.0.
Checking compatibility for NETStandard.Library 2.0.3 with .NETStandard,Version=v2.0.
Checking compatibility for BlazorTest.Shared 1.0.0 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Blazor.Mono 0.10.0-preview-20190325.1 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Components.Browser 3.0.0-preview4-19216-03 with .NETStandard,Version=v2.0.
Checking compatibility for Mono.WebAssembly.Interop 3.0.0-preview4.19216.2 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.NETCore.Platforms 1.1.0 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Components 3.0.0-preview4-19216-03 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.Extensions.DependencyInjection 3.0.0-preview4.19216.2 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.JSInterop 3.0.0-preview4.19216.2 with .NETStandard,Version=v2.0.
Checking compatibility for System.ComponentModel.Annotations 4.6.0-preview4.19212.13 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.Extensions.DependencyInjection.Abstractions 3.0.0-preview4.19216.2 with .NETStandard,Version=v2.0.
All packages and projects are compatible with .NETStandard,Version=v2.0.
Installing NuGet package Microsoft.AspNetCore.Blazor 3.0.0-preview4-19216-03.
Committing restore...
Assets file has not changed. Skipping assets file writing. Path: C:\Code\BlazorTest.Client\obj\project.assets.json
Writing cache file to disk. Path: C:\Code\BlazorTest.Client\obj\BlazorTest.Client.csproj.nuget.cache
Restore completed in 85.94 ms for C:\Code\BlazorTest.Client\BlazorTest.Client.csproj.
Running restore with 4 concurrent jobs.
Reading project file C:\Code\BlazorTest.Server\BlazorTest.Server.csproj.
The restore inputs for 'BlazorTest.Server' have not changed. No further actions are required to complete the restore.
Committing restore...
Assets file has not changed. Skipping assets file writing. Path: C:\Code\BlazorTest.Server\obj\project.assets.json
No-Op restore. The cache will not be updated. Path: C:\Code\BlazorTest.Server\obj\BlazorTest.Server.csproj.nuget.cache
Restore completed in 12.18 ms for C:\Code\BlazorTest.Server\BlazorTest.Server.csproj.

NuGet Config files used:
    C:\Users\xxxxx\AppData\Roaming\NuGet\NuGet.Config
    C:\Program Files (x86)\NuGet\Config\Microsoft.VisualStudio.Offline.config
    C:\Program Files (x86)\NuGet\Config\Xamarin.Offline.config

Feeds used:
    https://api.nuget.org/v3/index.json
    C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\
    https://dotnet.myget.org/F/aspnetcore-dev/api/v3/index.json
    https://dotnet.myget.org/F/blazor-dev/api/v3/index.json
Executing nuget actions took 71.66 ms
Time Elapsed: 00:00:01.4810819
= = = = = STOP - Package: NuGet.PackageManagement.PowerShellCmdlets.PowerShellInstalledPackage = = = = = =

= = = = = START - Package: NuGet.PackageManagement.PowerShellCmdlets.PowerShellInstalledPackage = = = = = =
Running restore with 4 concurrent jobs.
Reading project file C:\Code\BlazorTest.Client\BlazorTest.Client.csproj.
Persisting no-op dg to C:\Code\BlazorTest.Client\obj\BlazorTest.Client.csproj.nuget.dgspec.json
Restoring packages for C:\Code\BlazorTest.Client\BlazorTest.Client.csproj...
Restoring packages for .NETStandard,Version=v2.0...
Resolving conflicts for .NETStandard,Version=v2.0...
Checking compatibility of packages on .NETStandard,Version=v2.0.
Checking compatibility for BlazorTest.Client 1.0.0 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Blazor.Build 3.0.0-preview4-19216-03 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Blazor 3.0.0-preview4-19216-03 with .NETStandard,Version=v2.0.
Checking compatibility for NETStandard.Library 2.0.3 with .NETStandard,Version=v2.0.
Checking compatibility for BlazorTest.Shared 1.0.0 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Blazor.Mono 0.10.0-preview-20190325.1 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Components.Browser 3.0.0-preview4-19216-03 with .NETStandard,Version=v2.0.
Checking compatibility for Mono.WebAssembly.Interop 3.0.0-preview4.19216.2 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.NETCore.Platforms 1.1.0 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.AspNetCore.Components 3.0.0-preview4-19216-03 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.Extensions.DependencyInjection 3.0.0-preview4.19216.2 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.JSInterop 3.0.0-preview4.19216.2 with .NETStandard,Version=v2.0.
Checking compatibility for System.ComponentModel.Annotations 4.6.0-preview4.19212.13 with .NETStandard,Version=v2.0.
Checking compatibility for Microsoft.Extensions.DependencyInjection.Abstractions 3.0.0-preview4.19216.2 with .NETStandard,Version=v2.0.
All packages and projects are compatible with .NETStandard,Version=v2.0.
Installing NuGet package NETStandard.Library 2.0.3.
Committing restore...
Assets file has not changed. Skipping assets file writing. Path: C:\Code\BlazorTest.Client\obj\project.assets.json
Writing cache file to disk. Path: C:\Code\BlazorTest.Client\obj\BlazorTest.Client.csproj.nuget.cache
Restore completed in 60.6 ms for C:\Code\BlazorTest.Client\BlazorTest.Client.csproj.
Running restore with 4 concurrent jobs.
Reading project file C:\Code\BlazorTest.Server\BlazorTest.Server.csproj.
The restore inputs for 'BlazorTest.Server' have not changed. No further actions are required to complete the restore.
Committing restore...
Assets file has not changed. Skipping assets file writing. Path: C:\Code\BlazorTest.Server\obj\project.assets.json
No-Op restore. The cache will not be updated. Path: C:\Code\BlazorTest.Server\obj\BlazorTest.Server.csproj.nuget.cache
Restore completed in 12.31 ms for C:\Code\BlazorTest.Server\BlazorTest.Server.csproj.

NuGet Config files used:
    C:\Users\xxxxx\AppData\Roaming\NuGet\NuGet.Config
    C:\Program Files (x86)\NuGet\Config\Microsoft.VisualStudio.Offline.config
    C:\Program Files (x86)\NuGet\Config\Xamarin.Offline.config

Feeds used:
    https://api.nuget.org/v3/index.json
    C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\
    https://dotnet.myget.org/F/aspnetcore-dev/api/v3/index.json
    https://dotnet.myget.org/F/blazor-dev/api/v3/index.json
Executing nuget actions took 79.81 ms
Time Elapsed: 00:00:01.5362542
= = = = = STOP - Package: NuGet.PackageManagement.PowerShellCmdlets.PowerShellInstalledPackage = = = = = =

Visual Studio & Tooling version info
Microsoft Visual Studio Professional 2019 Preview
Version 16.1.0 Preview 2.0
VisualStudio.16.Preview/16.1.0-pre.2.0+28822.285
Microsoft .NET Framework
Version 4.7.03056

Installed Version: Professional

Visual C++ 2019   00435-60000-00000-AA166
Microsoft Visual C++ 2019

ADL Tools Service Provider   1.0
This package contains services used by Data Lake tools

Application Insights Tools for Visual Studio Package   9.0.20307.1
Application Insights Tools for Visual Studio

ASP.NET and Web Tools 2019   16.1.302.53887
ASP.NET and Web Tools 2019

ASP.NET Core Blazor Language Services   16.0.19216.03

ASP.NET Web Frameworks and Tools 2019   16.1.302.53887
For additional information, visit https://www.asp.net/

Azure App Service Tools v3.0.0   16.1.302.53887
Azure App Service Tools v3.0.0

Azure Data Lake Node   1.0
This package contains the Data Lake integration nodes for Server Explorer.

Azure Data Lake Tools for Visual Studio   2.3.8000.0
Microsoft Azure Data Lake Tools for Visual Studio

Azure Functions and Web Jobs Tools   16.1.302.53887
Azure Functions and Web Jobs Tools

Azure Stream Analytics Tools for Visual Studio   2.3.8000.0
Microsoft Azure Stream Analytics Tools for Visual Studio

C# Tools   3.1.0-beta2-19211-01+9d88fee4efb9f7ae4ae053d63b9f8b5b31217c90
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Common Azure Tools   1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

Cookiecutter   16.1.19098.1
Provides tools for finding, instantiating and customizing templates in cookiecutter format.

Dotfuscator Community Edition   <IP_ADDRESS>56-03f69f61d
PreEmptive Protection - Dotfuscator CE

Extensibility Message Bus   1.1.77 (master@24013d5)
Provides common messaging-based MEF services for loosely coupled Visual Studio extension components communication and integration.

Fabric.DiagnosticEvents   1.0
Fabric Diagnostic Events

ILSpy.AddIn   1.0
Integration of the ILSpy Decompiler into Visual Studio.

LineEndingsUnifierPackage Extension   1.0
LineEndingsUnifierPackage Visual Studio Extension Detailed Info

Microsoft Azure HDInsight Azure Node   2.3.8000.0
HDInsight Node under Azure Node

Microsoft Azure Hive Query Language Service   2.3.8000.0
Language service for Hive query

Microsoft Azure Service Fabric Tools for Visual Studio   2.5
Microsoft Azure Service Fabric Tools for Visual Studio

Microsoft Azure Stream Analytics Language Service   2.3.8000.0
Language service for Azure Stream Analytics

Microsoft Azure Stream Analytics Node   1.0
Azure Stream Analytics Node under Azure Node

Microsoft Azure Tools   2.9
Microsoft Azure Tools for Microsoft Visual Studio 0x10 - v<IP_ADDRESS>

Microsoft Continuous Delivery Tools for Visual Studio   0.4
Simplifying the configuration of Azure DevOps pipelines from within the Visual Studio IDE.

Microsoft JVM Debugger   1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

Microsoft Library Manager   1.0
Install client-side libraries easily to any web project

Microsoft MI-Based Debugger   1.0
Provides support for connecting Visual Studio to MI compatible debuggers

Microsoft Visual C++ Wizards   1.0
Microsoft Visual C++ Wizards

Microsoft Visual Studio Tools for Containers   1.1
Develop, run, validate your ASP.NET Core applications in the target environment. F5 your application directly into a container with debugging, or CTRL + F5 to edit & refresh your app without having to rebuild the container.

Microsoft Visual Studio VC Package   1.0
Microsoft Visual Studio VC Package

Mono Debugging for Visual Studio   16.1.1 (2473f22)
Support for debugging Mono processes with Visual Studio.

Node.js Tools   1.5.10326.1 Commit Hash:f12bb7408a1f644400cbb5ca43f601559ea6bec5
Adds support for developing and debugging Node.js apps in Visual Studio

NuGet Package Manager   5.1.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

Office Developer Tools for Visual Studio   16.0.28803.01
Microsoft Office Developer Tools for Visual Studio

ProjectServicesPackage Extension   1.0
ProjectServicesPackage Visual Studio Extension Detailed Info

Python   16.1.19098.1
Provides IntelliSense, projects, templates, debugging, interactive windows, and other support for Python developers.

Python - Conda support   16.1.19098.1
Conda support for Python projects.

Python - Django support   16.1.19098.1
Provides templates and integration for the Django web framework.

Python - IronPython support   16.1.19098.1
Provides templates and integration for IronPython-based projects.

Python - Profiling support   16.1.19098.1
Profiling support for Python projects.

ResourcePackage Extension   1.0
ResourcePackage Visual Studio Extension Detailed Info

ResourcePackage Extension   1.0
ResourcePackage Visual Studio Extension Detailed Info

SQL Server Data Tools   16.0.61904.17120
Microsoft SQL Server Data Tools

Syntax Visualizer   1.0
An extension for visualizing Roslyn SyntaxTrees.

Test Adapter for Boost.Test   1.0
Enables Visual Studio's testing tools with unit tests written for Boost.Test.  The use terms and Third Party Notices are available in the extension installation directory.

Test Adapter for Google Test   1.0
Enables Visual Studio's testing tools with unit tests written for Google Test.  The use terms and Third Party Notices are available in the extension installation directory.

ToolWindowHostedEditor   1.0
Hosting json editor into a tool window

TypeScript Tools   16.0.10411.2001
TypeScript Tools for Microsoft Visual Studio

Visual Basic Tools   3.1.0-beta2-19211-01+9d88fee4efb9f7ae4ae053d63b9f8b5b31217c90
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Visual F# Tools 10.4 for F# 4.6   <IP_ADDRESS>.  Commit Hash: 809f41207b74a1356208f11b8fa3a15233734050.
Microsoft Visual F# Tools 10.4 for F# 4.6

Visual Studio Code Debug Adapter Host Package   1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

Visual Studio Tools for Containers   1.0
Visual Studio Tools for Containers

Visual Studio Tools for Kubernetes   1.0
Visual Studio Tools for Kubernetes

VisualStudio.Mac   1.0
Mac Extension for Visual Studio

Workflow Manager Tools 1.0   1.0
This package contains the necessary Visual Studio integration components for Workflow Manager.

Xamarin   <IP_ADDRESS>8 (d16-1@3cff8c337)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin Designer   <IP_ADDRESS>4 (remotes/origin/d16-1@9b140252a)
Visual Studio extension to enable Xamarin Designer tools in Visual Studio.

Xamarin Templates   16.1.401 (72b3e35)
Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.

Xamarin.Android SDK   <IP_ADDRESS> (HEAD/f3f2aeb7a)
Xamarin.Android Reference Assemblies and MSBuild support.
    Mono: mono/mono/2018-08@bf4e8d2ae19
    Java.Interop: xamarin/java.interop/d16-1@5ddc3e3
    LibZipSharp: grendello/LibZipSharp/master@44de300
    LibZip: nih-at/libzip/rel-1-5-1@b95cf3f
    ProGuard: xamarin/proguard/master@905836d
    SQLite: xamarin/sqlite/3.27.1@8212a2d
    Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-1@acabd26

Xamarin.iOS and Xamarin.Mac SDK   <IP_ADDRESS> (a5f2633)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.

I'm experiencing the same issue with a Blazor Client-Side project, Using VS 2019 Version 16.1.0 Preview 2.0
Error MSB4036	The "RazorGenerate" task was not found. Check the following:
1.) The name of the task in the project file is the same as the name of the task class.
2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface.
3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin" directory.
BlazorTest C:\Program Files\dotnet\sdk\3.0.100-preview3-010431\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.Component.targets	93

From the csproj file:
<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>netstandard2.0</TargetFramework>
    <RestoreAdditionalProjectSources>
      https://dotnet.myget.org/F/aspnetcore-dev/api/v3/index.json;
      https://dotnet.myget.org/F/blazor-dev/api/v3/index.json;
    </RestoreAdditionalProjectSources>
    <LangVersion>7.3</LangVersion>
    <RazorLangVersion>3.0</RazorLangVersion>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Blazor" Version="3.0.0-preview4-19216-03" />
    <PackageReference Include="Microsoft.AspNetCore.Blazor.Build" Version="3.0.0-preview4-19216-03" PrivateAssets="all" />
    <PackageReference Include="Microsoft.AspNetCore.Blazor.DevServer" Version="3.0.0-preview4-19216-03" PrivateAssets="all" />
  </ItemGroup>

</Project>

Do you have the preview4 SDK installed: https://dotnet.microsoft.com/download/dotnet-core/3.0? The error message here:
C:\Program Files\dotnet\sdk\3.0.100-preview3-010431\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.Component.targets	93 makes me think you have a mismatched runtime and SDK.

Thanks pranavkm, I will take a look.

I also have the same problem in Visual Studio 2019 Enterprise 16.0.2

I also have the same problem in Visual Studio 2019 Enterprise 16.0.2

I reinstall "SDK 3.0.100-preview4-011223"  resolved problem。

Fixed by re-install of dotnet-sdk-3.0.100-preview4-011223
Thanks everyone.

This is not good!!
I spend a huge amount of time on this and it turns out that I need an update!

Nowhere in Visual studio there is any indication that anything needs updating.
Visual Studio show no indications of anything needing updating.
No NuGet packages indicate any need of anything needs to be updated
The manage Extension tool in Visual Studio does not indicate any need of anything needing updating.
Windows Update does indicate that anything needs to be updated.
The build process does not indicate that there is any mismatching between versions and that something needs to be updated.

Something gladly updated the templates for creating a new Blazor project but did not at the same time update dependants that are REQUIRED for that update to work!
Something is obviously wrong here, this state should never be allowed to happen under normal circumstances, and if it still happen there should be constraints in several places that make sure it is obvious what is the problem and what's needed to be done to make it working.

A nuget package that depend on specific build-tasks should check that those are available.
A template that depends on external components, whatever they might be, should check and make sure they exist and are of the correct version/build/platform and so on.
Under no circumstances should there be any way that a missing update does not show up clearly inside Visual Studio.

  This seems to be like a project targeting .NET 2 and the machine only has .NET 1 and you get an error message that a build task is missing?

Don't build systems that work, build systems that can't fail! On 2011-03-10, the guys at Fukushima thought they had a system that works, but the very next day they found out is sure could fail and overheat, while being built on the shore to the Pacific Ocean...


"asdf-make: Failed to GPG verification"

Describe the bug
An error is thrown when trying to install make v4.3
Steps to reproduce
asdf plugin add make
asdf install make 4.3

* Downloading make release 4.3...
asdf-make: Failed to GPG verification

Expected behavior
make 4.3 is installed
Screenshots
Additional context
Running on Mac

If use-keyboxd in gnupg conf (~/.gnupg/common.conf) is enabled, you will need to add the signature manually.
Please check the README for instructions on how to do this.
https://github.com/yacchi/asdf-make#import-gpg-public-key


Provide meta-information of properties

From @netopyr on June 16, 2016 8:38
We need to access some meta-information about Dolphin properties. For a start the owning bean and the property name would be sufficient.
Copied from original issue: canoo/dolphin-platform#198

Sounds good :)
I already created a similar API for the Garbage Collection. If we directly provide metadata for properties and lists I can use it in GC, too.


[1.10.2] [MO 0.5.0] [CMM 2.0.2] Custom Main Menu/Resource Loader/Matter Overdrive Conflict

Please see: https://github.com/simeonradivoev/MatterOverdrive/issues/623
I have this error: http://pastebin.com/raw/Lj4VVyAm when trying to load my textures with the 1.10.2 update for Matter Overdrive. Prior to adding their mod, all textures load fine. I'm hoping bringing this issue to both of your attention can help resolve it. Thank you for your time.
Full log: https://gist.githubusercontent.com/Alaberti/33b4222c4af6d7b1b9cd13e39e4e6e59/raw/253b7f4e006295c8bed60dcb26aae8a567cb58f7/Client%2520Log%2520for%2520CMM_MO%2520issue
Config: http://pastebin.com/raw/ysLmR6Gi

It looks like the Full Log doesn't contain the error you posted.

It looks like it's not posting to log, but I can see it in the client console and Latest.log, so here you go, a fresh run with the minimum mods needed to cause the issue:
Latest.log: http://pastebin.com/raw/G0b65eKJ
FML-Client-Latest.log: http://pastebin.com/raw/AL6APYr6
Recently nailed down that the issue happens with Journeymap 5.4.6, CMM, Resource Loader, and MO 0.5.0 (libraries notwithstanding).


JAVA SCRIPT

JavaScript
USER STORY
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
ACCEPTANCE CRITERIA
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I can see the four topics I learned listed along with a suggestion on what I should study first

learned the basics of JavaScript


Getting 2 Errors on Step 4.

I'm copying the code listed but I'm getting these errors when I run it.

Type 'AppDelegate' does not conform to protocol 'GIDSignInDelegate'
Invalid redeclaration of 'sign(_:didSignInFor:withError:)'

You've defined the sign(_:didSignInFor:withError:) method twice. Remove one of them and your errors should go away.

@morganchen12 Thanks! IT solved my  redeclaration error.


[CORE-16] [Bug] Uncolored stdout when using the --use-colors flag

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When running models via the CLI with the --use-colors flag, the output is still uncolored.
dbt --use-colors run --select <models>
Expected Behavior
I would expect the output to be colored.
Steps To Reproduce
Running dbt via the CLI, execute: dbt --use-colors run --select <models>
Relevant log output
No response
Environment
- OS: macOS BigSur 11.6.1
- Python: 3.9
- dbt: 1.0.0 (installed via dbt-bigquery)

What database are you using dbt with?
bigquery
Additional Context
I am running this in a Docker container via a shell script and the full command, including Docker commands, is:
docker run --rm \
  -e DBT_DEV_PROJECT=$DBT_DEV_PROJECT \
  -p 8080:8080 \
  -v $HOME/.config/:/root/.config \
  -v ${DBT_HOME}/dbt:/dbt \
  $target_image \
  "$@"

where the values passed ("$@") are dbt --use-colors run --select <models>
If I rebuild my image using dbt v0.21.0 then the same command results in colored output.

@jbonatakis Thanks for the report!
I'm seeing colorized output when I use dbt --use-colors run --select <models> locally, though I'm not running dbt via Docker.
There are two possibilities here:

The --use-colors flag / global config is not working properly within dbt-core
Your terminal is not displaying color-tagged fields as colorized

A few ways to dig into this:

In logs/dbt.log, do you see color tags such as [33mWARNING [0m], [ [32mOK [0m in 1.09s], [32mCompleted successfully [0m? Alternatively, if you add --log-format json to your command, and check the msg fields of the resulting CLI output, do you see the color tags there?
Could you try outputting explicitly color-tagged text in your terminal, e.g. echo -e '\033[32mThis is in green\033[0m'?

@jtcohen6 Thanks for the suggestions!

I ran echo -e '\033[32mThis is in green\033[0m' and it printed green.

I checked logs/dbt.log and it formats the color tags like this: [OK in 0.98s]

If I rebuild my image using v0.21.0 and run the same command I get colored output, but oddly enough there are no color tags in the dbt.log file.
Console (v0.21.0):

Log file (v0.21.0):

When I run v<IP_ADDRESS> with the --log-format json option, the output does include the color tags:
"\u001b[32mCompleted successfully\u001b[0m". Again, if I run that by itself in my console, I get green output
echo -e "\u001b[32mCompleted successfully\u001b[0m"

This seems like an encoding issue.
My Dockerfile is based on python:3.9-slim-bullseye (link to source Dockerfile), which itself is based off of debian:bullseye-slim

I've noticed something similar
dbt --use-colors run --profile dc_dbt_int_snowflake --target dev

You'll get color in the terminal
Whereas,
dbt --use-colors run --profile dc_dbt_int_snowflake --target dev | less

You'll get no color because it's not a tty?
The --use-colors flag doesn't make a difference in both of these examples.

In our case, we would like colors to be output even if we're piping to another program vs piping out into a terminal's output. The --use-colors should force colors to still be output.
Is this related to https://github.com/dbt-labs/dbt-core/pull/4379 and/or https://github.com/dbt-labs/dbt-core/issues/4354 ?

I haven't had a chance to dig further into this, but just want to drop a few quick notes:

It's quite likely that these changes are related to the rework of structured logging in v1
It sounds like we might not be using the right color tags for the system? What do you see if you cat logs/dbt.log?
In earlier versions of dbt (such as v0.21), logs/dbt.log only contained debug-level events, and excluded info-level logs that were printed to the CLI. Those tend to the be the only logs with color. That's why, in earlier versions, you won't see color tags in logs/dbt.log, but you should see them in v1
Colorizing logs is on by default, so in general the --use-colors flag is unnecessary. The flag is only needed to override if you've set DBT_USE_COLORS=False (env var) or use_colors: False (in profiles.yml). See docs on global configs: https://docs.getdbt.com/reference/global-configs

@nathaniel-may Sounds like we should add a spike for this to the list for #4441

I'm not seeing any colors escape codes in <dbt project>/logs/dbt.log

I get color output if I cat logs/dbt.log

It looks like docker's default shell does not understand 16-bit unicode-encoded escape sequences. Namely: \u001b, but it does understand ANSI namely: \033.
Reproduction
Open the docker cli and run the following two commands:
unicode: (no color, displays escape sequences)
echo -e "\u001b[32mCompleted successfully\u001b[0m"

ansi: (is green, no escape sequences)
echo -e "\033[32mCompleted successfully\033[0m"

Workaround
From your host machine (not the docker cli) you can run the following command which will open a new shell which does understand unicode escape sequences the way dbt v1.0.0 is emitting them:
% docker exec -it my-container env TERM=xterm-256color script -q -c "/bin/bash" /dev/null

Solution
Although unicode escape sequences are part of a good standard that has been around a very long time, they are unfortunately not supported by some modern and commonly used shells. For compatibility reasons we should revert to using the older ANSI encoding.


How much data from DL3DV did you use in your training

Hi, authors! Thanks for your great work!
How much data from DL3DV did you use in your training? Is it all data or a subset?
Thanks!!

Hi, thank you for your interest in our work, we use all DL3DV training data for training.


e2e: fix flaky test 47591

The test fails in CI and passes locally. The test modifies the pod resources under the deployment and do some checks on the new pod. The part that is causing the test to fail is that it doesn't wait "long enough" for the new pod to get created, causing the automation to pick an old pod, hence failing in later node name check.
Investigating it deeper, even with same oc client the test kept passing locally. Yet managed eventually to reproduce it by running it using an ssh connection to the cluster. Not clear about the root cause at the moment, but it seems that when the automation is connected to the cluster actually matters in terms of how quick the check can be, as via exporting the KC the test had no chance of failing, but via ssh the test continuously failed, possible indicator that ssh connection has a faster reaction than exporting KC.
To fix the flakiness, we add a waiting loop to guarantee we do not move further until the new pod's replicaset gets created.

/retest


Expand problem

HI Can I Expand different child from different group?
OR Can I lock specific item (cannot to expand) ?
Thank for your help~

Hi :)

Can I lock specific item (cannot to expand) ?

If you don't want to expand/collapse a group when touching the item, please implement the onCheckCanExpandOrCollapseGroup() method always returns false.

Can I Expand different child from different group?

Set on click listener to each item views and call the expandGroup() method on clicked.
RecyclerViewExpandableItemManager.expandGroup(int groupPosition)
RecyclerViewExpandableItemManager.collapseGroup(int groupPosition)

Related issues

Force expand/colapse #11

Thanks , it work for me

Hi :)
Can I lock specific item (cannot to expand) ?
If you don't want to expand/collapse a group when touching the item, please implement the onCheckCanExpandOrCollapseGroup() method always returns false.

Sorry
I still no idea for the usefulness and usage of
RecyclerViewExpandableItemManager.expandGroup(int groupPosition)
RecyclerViewExpandableItemManager.collapseGroup(int groupPosition)

In my project,
@Override
        public void onClick(View v) {
            if (mItemClickListener != null) {
                mItemClickListener.onItemClick(v, groupPosition);
            }
            RecyclerViewExpandableItemManager re = new RecyclerViewExpandableItemManager(null);
            Log.d("test", re.expandGroup(groupPosition)+"");
        }

how can i improve the code,
Thank you for your time

@k1589645 Hi. Need to use the RecyclerViewExpandableItemManager instance which is created in your Activity or in Fragment. Please refer the following demo code. Thanks.

https://github.com/h6ah4i/android-advancedrecyclerview/blob/0.8.7/example/src/main/java/com/h6ah4i/android/example/advrecyclerview/demo_e_add_remove/AddRemoveExpandableExampleAdapter.java#L121

It totally solve my problem.
Thank you for your share. It's a useful lib.


Add Gen.compose to allow imperative generator composition

What's in this pull request?
Swift's lack of implicit conformance and polyvariadic functions makes composing generators using map/zip or functional operators (<*> and <^>) cumbersome and/or infeasible for types with a large number of input parameters.  Further, manually gathering many generated values to create a new generator is not only vulnerable to losing entropy*, but also rife with duplicated calls to manually split the StdGen—not to mention making Gen(ungen:) public 🙈.
This change introduces GenComposer, which preserves entropy by encapsulating the logic of splitting the StdGen, as well as offering generic functions to remove even more boilerplate—especially for the default use case (T.arbitrary).
* As discussed in gitter preceding https://github.com/typelift/SwiftCheck/pull/164
Why merge this pull request?

Circumvents limitations of Swift's type system & performance problems with the type checker
Very small code footprint
Zero impact on build processes

What's worth discussing about this pull request?

Where the code lives (Modifiers.swift, Gen.swift, etc.)
API naming
Code (and comment) clarity
How/where to introduce Gen.compose in the documenation
Missing tests

What downsides are there to merging this pull request?

Yet another way to compose Gen instances (in addition to zip, flatMap, etc.)

Please let me know your thoughts on the above and I'd be happy to put in more time to document this properly in the README.

Alright, this does look good overall. I think that we need more documentation, especially in the readme, and then we can merge it.

@griotspeak added docs, but also ran into a puzzling case where the property for a test I added always wound up with a size of 0: https://github.com/bgerstle/SwiftCheck/blob/feature/gen-builder/Tests/SimpleSpec.swift#L203.  Might file a separate issue for this later.

iOS build failed on CI but passed locally. I've seen this many other times and have worked around it w/ simctl (5fd9e73). Could be extracted into a separate bash script and/or makefile goal, but should work well enough in the .travis.yml

I've seen this many other times
... and it's usually caused by the simulator timing out when launching

Do we have a sense of specifically why/how the timeout was triggered? I don't like that we have to do this when it seems like we should be able to make it work without fiddling with the yml

It's an (effectively hard-coded) 120s timeout when xcode tries to boot &
attach to the simulator. We can try to spend more time debugging by looking
at raw xcodebuild output, but this is the approach that I've seen a few
repos take when dealing with the issue on Travis.  Even tools like scan
from fastlane will handle this sort of thing for you
https://github.com/fastlane/fastlane/blob/master/scan/lib/scan/runner.rb#L18
.
On Mon, Jun 20, 2016 at 1:24 PM TJ Usiyan<EMAIL_ADDRESS>wrote:

Do we have a sense of specifically why/how the timeout was triggered? I
don't like that we have to do this when it seems like we should be able to
make it work without fiddling with the yml
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/typelift/SwiftCheck/pull/168#issuecomment-227210048,
or mute the thread
https://github.com/notifications/unsubscribe/AAbHOSECD9w7t3jjN7l4dbVCRE4MQ2OCks5qNszNgaJpZM4I5AXf
.

OK then. My residual reluctance is not so much about this PR so if you would be so kind as to add a note  about this reasoning to the yml, we can merge this thing.

@griotspeak i just remembered I didn't add anything to the tutorial playground. maybe I'll send something in a separate PR later


Update deployment walkthrough to allow configurable domain

Update the deployment walkthrough to allow "contoso.com" domain to be configurable.

new environment variable and cluster-stamp.json ARM variable that default to "contoso.com"
fixed sed command in the GitHub actions deployment option. missing pipes, "|", in the multi-line command
added kustomization to allow host on the workload ingress to be updated
tested using both option 1 and option 2 in the 05-aks-cluster.md instructions

Nice update. It feels like we're on the right track here. I've got a series of suggestions here to simplify even more. No need to have untracked file and duplicate all of the ingress configuration. Can even make the patch update process optional (but safe to run even if they don't see that message). What do ya think?

I like the suggestions. It reduces the ingress dup and still allows folks to customize. I'll add the changes, fix the merge conflict, and do another test run.

Sorry, just merged in @alfredoihernandez's PR on saving env variables -- which caused more merge conflicts.  I'll still review today.


SolidOS should create preferences file if missing

When I open the profile (https://ash.runi.ilabt.imec.be/profile/card#me) of a user (after logging in) I only see the following:

In previous versions we were able to edit the profile details of the user here, no?
When checking the console I see that some data is missing and I get the same error when clicking the + button on the left.
Error: Can't find a preferences file pointer in profile <https://ash.runi.ilabt.imec.be/profile/card>
However, https://ash.runi.ilabt.imec.be/profile/ works. I can see the Turtle file. So it might be more confusion on my part as what is expected to see at both locations. But when I try to save my changes I get the following error in the browser window
Error saving back: Error: Web error: 403 (User Unauthorized) on PUT of <https://ash.runi.ilabt.imec.be/profile/card>
while the first error is also shown in the console.

I experience this issue too, but in a slightly different setting. I managed to get right of this issue on my setting.
I registered a "new pod name" for my new solid server (pod). Say the server address is https://SERVER/, and pod name is foo.
Therefore, when visiting https://SERVER/, it seem to show things. After logging in, clicking the "add" button, I got the error message as you do:
(via loadPrefs) Error: Can't find a preference file pointer in profile  <https://SERVER/foo/profile/card>

But, when visiting https://SERVER/foo, and do the same thing, I no longer encounter this error.
For me, https://SERVER/ is the root directory (containing all users), and https://SERVER/foo is the pod that my new user actually resides. The permission issue may be the actual error.
But, same as you, my new user also doesn't have the preference file pointer. I looked at my account on a public solid server, and found this triple (which is missing from my own solid server):
@prefix space: <http://www.w3.org/ns/pim/space#>.
:me space:preferencesFile </settings/prefs.ttl>.

Maybe the root cause is incorrect initialization of new users? (But the error messages might worth be improving.)

@renyuneyun the original issue should have been closed.
you seem to run a CSS server where the pod name is /.

But, same as you, my new user also doesn't have the preference file pointer. I looked at my account on a public solid server, and found this triple (which is missing from my own solid server):

This is not a CSS error but a mashlib expectation. This should become a solid recommendation. There are on going discussions. See https://github.com/solid-profile

Actually, the recommendation will be that SolidOS (or any app depending on a preferences files) should create the preferences file if it doesn't exist.  So, this is a needed feature in mashlib,

@bourgeoa Thanks for the info. When posting the comment, I did not recognize that there is a difference (in the way it works) between CSS and the public solid servers (e.g. solidcommunity.net) (SolidOS?). I thought CSS is just the core module of SolidOS.
Maybe more explanation on CSS and SolidOS page would be helpful to newcomers.

@renyuneyun You should report them to solidos.

Thank you very much!

When moving to CSS this can be solved with "CSS supports this via a custom pod templates." (see this comment) and long-term SolidOS should create the file itself.

Was done with: https://github.com/SolidOS/solid-logic/pull/39


Fix intercom user_id

signin:1 Uncaught (in promise) {"type":"error.list","request_id":"b1oild14o597jp6a8hog","errors":[{"code":"conflict","message":"Multiple existing users match this email address<EMAIL_ADDRESS>- must be more specific using user_id"}]}
Add user_id here: https://github.com/VulcanJS/Vulcan/blob/ecf5c4c49e7bc7b8106fbf85d348751ae25073ed/packages/vulcan-events-intercom/lib/client/intercom-client.js#L16

I thought I fixed that? Doesn't work?
https://github.com/VulcanJS/Vulcan/blob/ecf5c4c49e7bc7b8106fbf85d348751ae25073ed/packages/vulcan-events-intercom/lib/client/intercom-client.js#L21

Somehow I missed that, thanks!


Option to let the LLM ready status get expired

Description

Add a new option expire_llm_is_ready_persistent_state to specify the expiration time to let the "LLM Ready" status, which is used in the response of /readiness API, in seconds. The default is -1 (= never expires). If the expiration occurs, the next /readiness API call will make a call against LLM again to check the status of LLM.
Type of change

[ ] Refactor
[X] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)
[ ] CI configuration change
[ ] Konflux configuration change

Related Tickets & Documents

Related Issue # AAP-35769
Closes # AAP-35769

Checklist before requesting a review

[X] I have performed a self-review of my code.
[X] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
Two new unit test cases are included in this PR.

How were the fix/results from this change verified? Please provide relevant screenshots or results.
Set expire_llm_is_ready_persistent_state to a small value, like 10 secs, call /readiness API, wait long enough and then make the second readiness API call to check LLM log to verify the API called the LLM as expected.

It is an extra dependency. It can be done with standard libs, but not as elegant.
WDYT @tisnik, worth of new dep?

That is not a problem, we can add this new dependency.

@onmete @tisnik If my understanding is correct, the original code was intentionally written not to enable caching if LLM was not ready yet. I did not want to change the behavior. With using a TTL cache, this will be changed. Is that OK?

Right, there is this condition too. The caching applies after the LLM is successfully pinged.
From our side (OLS), we decided that having this LLM check is the bare minimum (and maximum at the same time) we want to do in terms telling the LLM is ready.
There is a simple call that tells us if it can respond - just to catch networks issues, invalid credentials, ....
But besides that, we can't guarantee the 3rd party LLM is functional, we would have to pool it every moment to be able to tell it is not down (cost/perf) and check that the actual response text makes sense too.
Can you elaborate on your motivation for these changes? Maybe we can find some other solution to this.

Here's our motivation: We (Ansible Lightspeed team) hosts our own model server and would like to monitor its status. We also need to monitor the staus of the chatbot service itself. Unlike the use case with a third party LLM, we need to guarantee the availablilty of LLM and will send a PagerDuty aleart when the LLM (or chatbot service) is down. We want to use the /readiness endpoint to check the availability of both LLM and chatbot service, with keeping the current behavior which should be tailored for OLS. That's the reason that I wrote this PR to add a new option.

Here's our motivation: We (Ansible Lightspeed team) hosts our own model server and would like to monitor its status. We also need to monitor the staus of the chatbot service itself. Unlike the use case with a third party LLM, we need to guarantee the availablilty of LLM and will send a PagerDuty alert when the LLM (or chatbot service) is down. We want to use the /readiness endpoint to check the availability of both LLM and chatbot service, with keeping the current behavior which should be tailored for OLS. That's the reason that I wrote this PR to add a new option.

that actually makes sense. it sounds like we wanted to have both functionalities there, and thus the cfg.option makes sense. @onmete ?

Makes sense. Thanks!
BTW I'm not sure if you want another service to use the /readiness endpoint - nothing against it, just mind that the endpoint itself is pinged every 5-10 seconds by kubelet's readiness probe.
/lgtm

@onmete Thanks for the info.

BTW I'm not sure if you want another service to use the /readiness endpoint - nothing against it, just mind that the endpoint itself is pinged every 5-10 seconds by kubelet's readiness probe.

Currently our service status check call is configured to take place every 30 seconds, but I think it is still too short for checking the LLM status, which is expensive. Probably we will set the expire time to 180-300 secs.

@tisnik Would you approve this, if it looks good? Thanks!

/lgtm


Replace custom inset title bar (macOS)

In Atom 1.16 (currently Beta), there will be an option to use a custom inset title bar: https://github.com/atom/atom/pull/13616. It has a bit more padding around the traffic lights:

Not that useful, but it would be neat if the tool-bar would replace that title bar. Something like:

Not sure if it should be opt-in or opt-out or all the time a user would use a combination of: custom-inset title bar + full width top tool bar.
Anyways, I can try to make a PR in case there is interest.

I'd love to see this. Not sure if I'd use it forever, but it's a really neat feature.

Just saw this https://github.com/atom/atom/pull/13616#issuecomment-286416556 the other day and as funny as it looks initially, it might not be a bad idea. Could be a separate package that adds the 3 buttons and custom styles them.


Inverse yielding requires unexpected indentation

NOTE: The examples in this comment are not actually correct as I had not properly simplified the problem. Please see my correction in a follow-up comment.

/ only way that works
some-component-with-inverse-yield
  | foo
  else
  | bar

/ doesn't work (this is what I'd expect to work)
some-component-with-inverse-yield
  | foo
else
  | bar

/ doesn't work
some-component-with-inverse-yield
  | foo
  else
    | bar

The ones that don't work result in an error:

Uncaught Error: Assertion Failed: A helper named 'else' could not be found

Equivalent handlebars:
{{#some-component-with-inverse-yield}}
  foo
{{else}}
  bar
{{/some-component-with-inverse-yield}}

@SaladFork  can you confirm if this is still an issue?
I am seeing the following working:
some-component-with-inverse-yield
  |foo
else
  |bar

=>
{{#some-component-with-inverse-yield}}
  foo
{{else}}
  bar
{{/some-component-with-inverse-yield}}

Ah, my mistake. As posted you are correct. I've done some more research and the fail condition is when you switch to multi-line declarations with square brackets:
/ works
some-component-with-inverse-yield value=true
  | foo
else
  | bar

/ doesn't work
some-component-with-inverse-yield [
  value=true ]
  | foo
else
  | bar

/ works
some-component-with-inverse-yield [
  value=true ]
  | foo
  else
  | bar

#274 should resolve this


Adding Support For Binary Ninja

I've already laid everything out to add support for Binary Ninja to Flare Emu, but before I got too deep into it it occured to me that it'd be good to ask - there's no reason that doing so wouldn't be possible or feasible is there? I assume it was omitted due to simple lack of interest / perceived wide-spread usage not some unknown-to-me fundamental incompatibility.

@the-wondersmith this would be a most welcome and appreciated improvement! I haven't used Binary Ninja personally, but as long as you can implement all the methods when subclassing the AnalysisHelper class then it should be fine. Please reach out to me if you have any questions.

@jtbennett-fe  I have several questions I'd like to run by you as I work on this, but I don't think a GitHub issue is necessarily the correct place for it. If it's cool with you I grabbed a quick [temporary email](mailto<EMAIL_ADDRESS>so no one has to publicly post contact details. Would you email over and let me know the best way to get in touch with you?

@the-wondersmith email sent!


Efforts "Assigned to my organization" are not displayed to advisors in subordinate organizations

When creating an engagement report, the advisor must select one or more efforts.
One of the options in the efforts widget is "Assigned to my organization."  Only if an advisor is assigned to an organization with efforts is the widget populated.  Advisors in the subordinate organizations do not see the efforts in "Assigned to my organization."
Very few organizations have efforts.  The efforts are assigned at the parent organization where there aren't that many advisors.  For example, one parent advisor organization has 10 efforts and 12 subordinate organizations.  The parent advisor organization has eight advisors.  The subordinate organizations have 61 advisors.  The 61 advisors cannot see their parent organization's effort in the "Assigned to my organization" widget.

This was fixed recently


Update language server

ship:

v1.39.12
net6.0 based language-server (instead of net472/mono)
arm64 compatible language-server

https://github.com/sublimelsp/LSP-OmniSharp/pull/31#discussion_r1365442197
Does this break current user's workflow when they don't have .NET 6 installed? I asked this a long time ago, but, I don't know if there's still a concern to be honest.

It will break those, but mono has been deprecated long ago as well as .NET 4.7 on windows platform. Each recent Visual Studio ships .net6+ and it is an easy fix on Linux/MacOS as well. .NET 4.7 is also supported compile target on .net6+. So impact besides requiring .NET sdk should be rather low.

I tested this on Ubuntu and it now complains about a mono executable missing. I see there’s an OmniSharp file that, when given executable permissions, is executable. I want to have this minor issue fixed for Linux before making a release. I’ll do this myself but I do welcome PRs.


feat: Allow extra headers to be attached to requests

Because the target URL for requests made during range reads are constructed from the response URL, they lose credentials attached to the URL. This change allows extra headers to be attached to the requests so users can propagate important headers (such as authorization)
Usage looks roughly like this...
let req = client
    .head(url.clone())
    .build()?

// Copy authorization headers from the HEAD request to subsequent requests
let mut headers = HeaderMap::default();
if let Some(authorization) = req.headers().get("authorization") {
    headers.append("authorization", authorization.clone());
}

let mut reader =
    AsyncHttpRangeReader::from_head_response(client, response, headers)
        .await?;

An alternative option would be to copy authentication from the request URL to the response URL (as in https://github.com/astral-sh/uv/pull/1874 / uv-auth)
Note this is a breaking API change, I don't see an easy way around it e.g. a helper method like with_headers doesn't seem feasible with the way the type is designed.
Needed to resolve https://github.com/astral-sh/uv/issues/1709

Nvm CI I have to fix the workflow

Thanks for the quick merge and release — let me know if you want me to do more i.e. update the tests


Add sensitive info google drive link to vetting views

Description:
Vetting agents would like to digitally store documents with sensitive information.  The current google drive link is accessible by all using the software across the platform.
Acceptance criteria:

A new google drive link (in addition to the old one) should be present in the application view and the vetting worksheet view.
Adjust verbiage to old link from Google Drive to "Google Drive - Project"
Add "Google Drive - Vetting Only" as new link area
All link functionality should be similar to old Google Drive link
Add a note to the new link: "For storing vetting documents, including sensitive information. Only vetting agents have access to this link."
Adding a Vetting Only link in Application view should populate the link in both App view and Vetting Worksheet, and vice versa.

Notes:

This change will affect the database structure, but should not affect old data.

Completed by Mike and pushed to production.


Backport Check IP Services

Original pull request to master was #3037

These pull requests are all the code committed to master since 1 July 2016 that are for stuff that will work fine in the RELENG_2_3 branch on pfense 2.3.* and FreeBSD 10.3
#3062 #3063 #3064 #3065 #3066 #3067 #3068 #3069 #3070 #3071
I believe that these would all be useful to people running 2.3.* and particularly those on 32 bit systems like Alix who will not be able to upgrade to 2.4


Disable stealth options which block login iframe

Fixes https://github.com/itsjafer/schwab-api/issues/63
On the main page, the iframe that was used for logging in was being blocked by the default stealth options. I went through each option and found the culprits and disabled them. This allows the iframe to show up while still keeping the other stealth options that allow logging in.
Would love a review, or if you have other thoughts, please let me know @itsjafer, but this fixes it for me.

this fixed the problem for me as well (though I have to use firefox as webkit is giving a ValueError: Only supported browserType is 'firefox' on my mac)

hi @NelsonDane, just checking in -- is this change still necessary?

From my testing, I've found it is still necessary, and it has been working well for me and my users in my main project. It also seems to be the fix according to https://github.com/itsjafer/schwab-api/issues/63#issuecomment-2230067704, so I would welcome your thoughts/review :)

Thanks mate, that change was necessary indeed!
It's almost impossible to log in without it now.


HTMLZip version of the documentation is no longer generated.

Problem description / Steps to reproduce
Old versions (<=0.16.0) of readthedocs contain a single-page version of restic documentation, but after moving to version 2 of the .readthedocs.yaml file, htmlzip format is no longer generated.
Do you have any idea what may have caused this?
I am not entirely sure, but I think these lines should be added to .readthedocs.yaml to fix this:
# Build HTMLZip
formats:
  - htmlzip

Could you open a PR with the change? From what I can tell, it's the proper way to reenable the htmlzip format.

Done, but I think you should run something manually to create missed files for latest release.


⚠ Bofrost.fr has degraded performance

In cc714ab, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1534 ms

Resolved: Bofrost.fr performance has improved in cd79954 after 16 minutes.


Added Autoprefixer Host to HTML and CSS

HTML and CSS/Autoprefixer Host - https://github.com/Taritsyn/AutoprefixerHost
.NET wrapper around the Andrey Sitnik's Autoprefixer

Sorry, but the community hasn't rallied behind this project to get it included. Thanks for your contribution.


Cannot use 'Enter' to move between search results

Issue Type: Bug
Steps to reproduce:

Press Ctrl+f
Type a string to search that has occurrences in the current file.
Press Enter to move to subsequent search results.

Expected behavior - can move between string occurences using Enter and Shift+Enter
Actual behavior - pressing Enter doesn't accomplish the above, even though it did quite recently.
VS Code version: Code 1.54.1 (f30a9b73e8ffc278e71575118b6bf568f04587c8, 2021-03-04T22:38:31.419Z)
OS version: Windows_NT x64 10.0.21322
Extensions (8)

Extension
Author (truncated)
Version

vscode-flow-ide
gca
1.2.0

devinsights
Mic
2021.2.19-1

tdpcode
Mic
1.6.4

vscode-nmake-tools
Mic
2.0.200218004

cpptools
ms-
1.2.2

powershell
ms-
2021.2.2

debugger-for-chrome
msj
4.12.12

vscode-react-native
msj
1.4.1

A/B Experiments
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt875:30259475
vspre833:30267464
vsdfh931:30270786

Are you sure you don't have a conflicting keybinding?


[fix](tablet meta) stale rowset is not loaded while BE start

Proposed changes
Issue Number: close #xxx
stale rowset is missed after BE restart
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall