Compiler deprecation warnings with VS2019 Version 16.10 and boost/make_shared.hpp

Hello Boost,
Apologies in advance if this turns out not to be a Boost issue but I'm out of ideas on what to do next.  Here's my setup:

Operating System : Windows 10 Enterprise 22H2
Compiler : Visual Studio 2019 Version 16.10, Compiler 19.29.30148 for x64
Boost : 1.77.0

I've been seeing odd behavior regarding deprecated APIs after including boost/make_shared.hpp when the -external:Wn and -external:I<path> compiler options are used. Here's a simple program to demonstrate:
#include <boost/shared_ptr.hpp>
#include <boost/make_shared.hpp>

// old way to mark a function as deprecated
[[deprecated ("Since 1.0.0")]] int DeprecatedA()
{
	return 0;
}

// new way to mark a function as deprecated (since C++14)
__declspec(deprecated("Since 1.0.1")) int DeprecatedB()
{
	return 0;
}

int main()
{
	DeprecatedA();
	DeprecatedB();
	return 0;
}

This code should output two compiler warnings (C4996) when compiled and it does providing I do not compile with these options:
-external:W0 -external:I"C:/ThirdParty/v3.0.0/boost-1.77.0/include/boost-1_77"
When these options are specified then the above program compiles without warning despite the deprecated functions not being part of boost.  If I comment out the #include <boost/make_shared.hpp> line then the compiler outputs deprecation errors.  Also if I do the following then the deprecation errors are output.
#include <boost/shared_ptr.hpp>
#pragma warning(push)
#include <boost/make_shared.hpp>
#pragma warning(pop)

Something isn't right but I'm not at all sure what.  I am suspicious of the VS compiler as it should be outputting warnings but actually outputs this despite the compiler option "Treat warnings as errors" being set to No (/WX-)
1>good.cpp
1>C:\Development\main\trials\pcc\deprecated_good\good.cpp(24,2): error C4996: 'DeprecatedA': Since 1.0.0
1>C:\Development\main\trials\pcc\deprecated_good\good.cpp(25,2): error C4996: 'DeprecatedB': Since 1.0.1
1>Done building project "deprecated_good.vcxproj" -- FAILED.
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

Any help, thoughts and/or suggestions would be appreciated.
Paul

I have just found the problem and it's with the compiler: See:
https://developercommunity.visualstudio.com/t/external:I-fails-to-restore-warning-sta/1533391?q=external+w0+warning


Fish should gain immunity to Voltaic Sea Grass

While funny, I often see mass hordes of fish dying in water because they don't know to avoid the sea grass. Perhaps fish could be given some kind of immunity to it to prevent the mass slaughter of fish in the future? Perhaps a tag could be used to decide if a fish mob is immune to it so support could also be easily added to fish from other mods as well.

Should work now!


Angular CLI timeout - even though it's actually running fine

I'm using the latest Microsoft.DotNet.Web.Spa.ProjectTemplates 2.0.0 that was published 6 days ago.
I did the following:

dotnet new --install Microsoft.DotNet.Web.Spa.ProjectTemplates
dotnet new angular
SET ASPNETCORE_Environment=Development
dotnet run

So far so good. I receive in the log:

info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[0]
User profile is available. Using 'C:\Users{{user}}\AppData\Local\ASP.NET\DataProtection-Keys' as key repository and Windows DPAPI to encrypt keys at rest.
info: Microsoft.AspNetCore.SpaServices[0]
Starting @angular/cli on port 34100...
Hosting environment: Development
Content root path: C:\repos\ngpoc
Now listening on: http://localhost:5000
Application started.

Ok, so I navigate to http://localhost:5000 and I receive this:

info: Microsoft.AspNetCore.Hosting.Internal.WebHost[1]
Request starting HTTP/1.1 GET http://localhost:5000/fetch-data
fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[0]
An unhandled exception has occurred while executing the request
System.TimeoutException: The Angular CLI process did not start listening for requests within the timeout period of 50 seconds. Check the log output for error information.
at Microsoft.AspNetCore.SpaServices.Extensions.Util.TaskTimeoutExtensions.d__1`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.SpaServices.Extensions.Proxy.SpaProxy.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Builder.SpaProxyingExtensions.<>c__DisplayClass2_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Builder.RouterMiddleware.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.d__7.MoveNext()
info: Microsoft.AspNetCore.Hosting.Internal.WebHost[2]
Request finished in 50161.8848ms 500 text/html; charset=utf-8
info: Microsoft.AspNetCore.Hosting.Internal.WebHost[1]
Request starting HTTP/1.1 GET http://localhost:5000/favicon.ico
info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[2]
Sending file. Request path: '/favicon.ico'. Physical path: 'C:\repos\ngpoc\wwwroot\favicon.ico'
info: Microsoft.AspNetCore.Hosting.Internal.WebHost[2]
Request finished in 8.5569ms 200 image/x-icon

I've seen the other post about changing the timeout and such, but the thing is it's not the timeout. I get the same error if I set the timeout to 600 seconds. It's like the cli just isn't seeing that angular is running. If I go to http://localhost:34100 like the original output states that ng serve is running on then everything works beautifully b/c it's already compiled and running - except of course the .net services b/c they are running on 5000.
It's simply as if the project isn't talking to the angular process.
If I run ng serve in a separate console and place spa.UseProxyToSpaDevelopmentServer("http://localhost:4200"); in Startup.cs the whole thing works fine.

I tried again several times and the problem existed each time.
I tried again on a different computer and it went through smooth as butter.
I tried again on the original computer but I installed AspNetCore 2.1-preview and used Visual Studio to create the solution and it's fine.

Are there any troubleshooting steps I can use to figure out why it won't work through the CLI?

I believe this has something to do with the network interfaces on the machine. I believe I'm seeing other symptoms of this as well as dotnet restore is timing out and that points to a bunch of closed "cannot repro" issues where people are mentioning VMware ethernet interfaces.
I am indeed doing it on a VMWare VM and while nuget restore works, dotnet restore does not. interestingly enough, if I disable the VMWare ethernet interfaces the http://localhost:5000 magically starts working and everything is fine.
As I posted at https://github.com/dotnet/cli/issues/1732 I was able to add nuget proxy configuration and magically the dotnet restore started working. Could this somehow be attempting to use a proxy even though both addresses are localhost?

@mcaden Did you ever get a legitimate solution to this? Out of the blue, I just started getting this same error (and when I was using the template a couple weeks ago, everything was fine). I'm not sure what changed.

+1. I'm seeing a similar error. Not sure what caused the ASP.NET Core -> Angular communication to stop working.

I worked around the issue simply by disabling the vmware network interfaces I had. Seems really odd that they would be an issue for this when they don't seem to hinder anything else I've ever done on the box over multiple years of development.
I also tried several boxes that were not VMs and they work fine with no changes. I'm working on one right now and all seems well.

Turns out the issue I saw was similar (unrelated networking interference). Thanks for the suggestion!

From the discussion, it seems that the underlying issue is a networking fault on the machine, which is unfortunately beyond our control, so I'll mark this closed.
If anyone is affected by this and doesn't have any way to fix their local networking, one alternative that might work for you is this: https://docs.microsoft.com/en-us/aspnet/core/spa/angular?tabs=visual-studio#run-ng-serve-independently


Update docs

Update docs before releasing the v2.3.0 documentation.
Address unaddressed tasks in #364:

[x] Update screenshots using plots from https://portal.nersc.gov/cfs/e3sm/zhang40/tutorials/run_v230_allsets/viewer/
[x] Add pre-processing example link

@chengzhuzhang This is ready for review. Relevant files are source/index.rst and source/input-data-requirement.rst. Relevant web pages are https://portal.nersc.gov/project/e3sm/forsyth/docs_2021_02_04/docs/html/ and https://portal.nersc.gov/project/e3sm/forsyth/docs_2021_02_04/docs/html/input-data-requirement.html.
Once this merges, I can release the new version of the documentation, at which point @tomvothecoder can start moving docs to the master branch.

Thanks! Please go ahead and merge.


add class property to module cmdlet

Hi
its possible to add class property  to import-module  and export-modulemember :
steps to reproduce (pseudo code)

PS> cat  test.psm1

class  test1 {  $p1 }
class  test2 {  $p2 }
export-moduleMember  -class test2

PS> import-module test.psm1

yes, its possible to use  the pragma using
using module test.psm1
but  with import-module its add more granularity

We would also need to add a ClassesToExport key to the module manifest to complete the pattern.
I think this should be done, but I'm not sure if there are logistical challenges with doing this.

We had another discussion about this, and the answer was, you must put your classes directly in the PSM1 file, not . source them in, and you must load with USING module, instead of import module and ... and .. and..
It's a mess, it needs cleaning up, it might be difficult but classes in modules should not be like Forest Gump's chocolates, you should ALWAYS know what you're going to get.
There is a risk that this breaks existing modules, (i.e. if 7.2 or 8.0 stops exporting classes from the PSM1 with Using) and the ideal would be that the if there is a new manifest entry it adds functionality without taking any away. (Unknown keys in the manifest are ignored, so it shouldn't reduce what is there for down-level users).
I have no idea of the practicalities but I'd call this highly desirable.

The popularity of "how to export a class in powershell v5 module" over on stackoverflow suggest that many people would like this functionality.  I have found that the workarounds aren't too bad though.  Implementing this wouldn't really enable encapsulating classes in modules as that is already (somewhat awkwardly) possible.  But this feature would make doing so more convenient.

Yeah, I've used the ScriptsToProcess approach myself in PSKoans. It works, right up until you need to unload and reload the module in the same session; it'll explode because there are already defined classes by those names. To work around that, I have my ScriptsToProcess handle it by checking if the type name already exists, and quietly preventing the classes from being re-defined.
It's definitely not ideal, and it'd be awesome if this were possible.

It works, right up until you need to unload and reload the module in the same session; it'll explode because there are already defined classes by those names.

Right.  It sounds like you're describing #2505 (and stackoverflow 42838107).
I expect PowerShell classes will continue to be expensive to support and painful to develop with.  Because of that I'm reluctant to recommend native PowerShell classes beyond their use with DSC; we already have full-blown C# classes for free.  In my own work I have found few scenarios where PowerShell classes turned out to be the right choice.
C# classes added during module loading with Add-Type are available everywhere in the PowerShell session via [Namespace.MyClass], so no export feature like this is required.  That strategy puts some strain on your module loading structure, but I have found the benefits of getting that right to be worth the effort.


Update Note on Supported Algorithms in [algorithm notes]

Description:
The current note in the algorithm notes mentions that several URI settings are not recognized by some authenticator apps. It should now be clarified that the Microsoft Authenticator app currently does not support certain algorithms. Therefore, it is recommended to use SHA1 as a fallback for compatibility with this app.
Tasks:

Update note text: Adjust the note text to accurately reflect the current support status of the Microsoft Authenticator app.
Add fallback method: Explicitly mention that SHA1 should be used as a fallback for compatibility with the Microsoft Authenticator app.

Current text:
Keep in mind that several URI settings are not (yet) recognized by all authenticators. Check [the Google Authenticator wiki](https://github.com/google/google-authenticator/wiki/Key-Uri-Format#parameters) for more info.

Proposed new text:
Please note that the Microsoft Authenticator app currently does not support certain algorithms. It is recommended to use SHA1 as a fallback for compatibility with Microsoft Authenticator.

Acceptance Criteria:

The note text is correctly updated to reflect the current support of the Microsoft Authenticator app.
The SHA1 fallback is clearly and understandably stated.

I don't see the point of this update. The note is for implementors of this library, not for end users. Further if we'd go down this route, we'd need to list every single 2FA application that might not support all of the settings, which might be all apps that are not "Google Authenticator".


Running scripts (.sc) that contain effect systems such as Cats and ZIO could use some specific support

Currently a simple ZIO program such as this:
//> using scala "3.2.2"
//> using lib "dev.zio::zio::2.0.9"

import zio._

object HelloApp extends ZIOAppDefault:
  def run = Console.printLine("Hello, World!")

Does not produce any output when run with scala-cli if it is in a '.sc' file, but works properly when it is in a '.scala' file. The behaviour can be expected, but can also surprise users. Perhaps scala-cli can provide some helpful hints when it encounters this, or work in such a way that it still runs the effects.

Seems we will not support this for now, closing this issue.


ISSUE-826 Sanitize mysql create_tables scripts

It still have potential issue with utf8mb4 so this might not an ideal, but this is better anyway.

@HeartSaVioR Already mentioned that in git commit message and user can always change the script as utf8mb4 is not a common case.

@satishd
Yeah great. I missed to see commit message.

Closes #826


Add extra check if both values are NA in bulk_upsert

Fixes #50 's pyarrrow compatibility problem.

Do we intend to release 0.7.1 immediately after this fix so that https://github.com/IAMconsortium/pyam/pull/820 can move forward?


xemu: 0.7.133 -> 0.7.134

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/xemu-project/xemu/releases.
meta.description for xemu is: Original Xbox emulator
meta.homepage for xemu is: https://xemu.app/
meta.changelog for xemu is: https://github.com/xemu-project/xemu/releases/tag/v0.7.134
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.7.134 with grep in /nix/store/icrq9cwcr1klkhfbqk740gij718klc0n-xemu-0.7.134
found 0.7.134 in filename of file in /nix/store/icrq9cwcr1klkhfbqk740gij718klc0n-xemu-0.7.134

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

xemu

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/icrq9cwcr1klkhfbqk740gij718klc0n-xemu-0.7.134 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A xemu https://github.com/r-ryantm/nixpkgs/archive/353b6a7e7dd0434c9257d6a739eb33540e0ff40f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/353b6a7e7dd0434c9257d6a739eb33540e0ff40f#xemu

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/icrq9cwcr1klkhfbqk740gij718klc0n-xemu-0.7.134
ls -la /nix/store/icrq9cwcr1klkhfbqk740gij718klc0n-xemu-0.7.134/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 2 packages built:

xemu
xemu.debug

Maintainer pings
cc @AndersonTorres for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Script Editor doesn't highlight GDScript (regression)

Godot version
Godot 4.0 Dev b4cea1077
System information
Windows 10, Nvidia GeForce GTX 1050, <IP_ADDRESS>71
Issue description
The code editor doesn't highlight syntax for GDScript, here's a image of it:

Steps to reproduce

Open a Script file
Observe.

Minimal reproduction project
HighlightingBug.zip

Duplicate of #51996


iOS: Order when request assetType:All is incorrect

🐛 Bug Report
When calling CameraRoll.getPhotos() in iOS with assetType: 'All' in the params the returned array is not ordered as if you are calling it with assetType: 'Photo' // or Video. When you call the function with assetType: All the assets are ordered with the oldest first. But if you call it with Photo or Video they are ordered with the most recent first (desired one)
Using assetType: 'All'
order: oldest first

Using assetType: 'Photos'
order: most recent first

To Reproduce

Create a new react native project (with react-native init)
Link the Camera Roll library
Add the permission keys in the Info.plist as described here from the README
call getPhotos with the following params:

CameraRoll.getPhotos({
    first: 50 // any number
    groupTypes: 'All',
    assetType: 'All',
});

call getPhotos with the following params:

CameraRoll.getPhotos({
    first: 50 // any number
    groupTypes: 'All',
    assetType: 'Photos', // or 'Videos'
});

Run react-native run-ios
Compare results 👀 .

Expected Behavior
I expect that the return array when querying for any kind of assetType (Photo, Video or All) would have the same order. Which is most recent first.
Environment
React Native Environment Info:
System:
OS: macOS 10.14.3
CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
Memory: 99.85 MB / 16.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 10.12.0 - /usr/local/bin/node
Yarn: 1.5.1 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
IDEs:
Android Studio: 3.1 AI-173.4819257
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.2 => 0.59.2
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1
react-native-create-library: 3.1.2
react-native-git-upgrade: 0.2.7
react-native-redux-boilerplate: 0.1.3
react-native-version: 2.6.6

It seems the issue is here:
https://github.com/react-native-community/react-native-cameraroll/blob/132af3166da29e9236f80da5367ce06b23b00a89/ios/RNCCameraRollManager.m#L64
If the default return is:
PHFetchOptions *const options = [PHFetchOptions new];
return option:

then it can be sort here:
https://github.com/react-native-community/react-native-cameraroll/blob/132af3166da29e9236f80da5367ce06b23b00a89/ios/RNCCameraRollManager.m#L204
I've create a PR for this: https://github.com/react-native-community/react-native-cameraroll/pull/28

Hi, @joseguerrerov. Can I get this ImageComposer component? Thanks.

@rpss2 what do you mean with ImageComposer ?

@joseguerrerov, this screen when selected image, where possible edit image, zoom and crop, etc.


Weights.yml

Oh huh ... this PR was only supposed to have the weights.yml update in it.
I'll fix this later ...

Something went wrong

Run git rebase -i HEAD~10 or something and delete the other commits manually and then force push.


Use the same variable

What is the purpose of this change? input and input_param are the same at that point in code, so using input instead of input_param makes no difference.

In my opinion, using the same variable can make the program easier to understand.


How to get access to the Kubernetes Dashboard?

From the previous question, the answer was:
You can get access to Kubernetes Dashboard via the UI in containers tab then advanced.
So where is the container tab?

Useful
Info

Versions
Rancher v2.0.0-alpha21 UI: v2.0.25

Access
local admin

Route
authenticated.cluster.index

I don't know where "the previous question" is, but it sounds like it was referring to the first preview release (<= alpha12).
The containers tab is currently called Workloads, when inside of a Project.
The dashboard is not deployed by default, because it does not work very well with RBAC.  You can use kubectl to deploy the yaml for it if you want.

oke, thanks!


master builds are failing

As noted in https://github.com/iterative/dvc.org/pull/2377#issuecomment-824484545 (and probably earlier), the build script stopped working at some point (first failed build) in master. This means we can't deploy anything to production. The error is
       [4/4] Building fresh packages...
       error /tmp/build_7f109913/node_modules/sharp: Command failed.
       Exit code: 1
       Command: (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)

CI tests are all passing though. This only happens with build and on prod, it seems.

Cc @rogermparent

stopped working at some point (first failed build

Actually that's on another branch (not merged yet). The first time it failed on master was this one, in case it helps (same error though).

This means we can't deploy anything to production

Or PR review apps

@julieg18 could you please give this one a try? it's a p0 for us.

It looks like the error may have something to do with the sharp module. Do you think upgrading packages that have the sharp module to a higher dependency could fix the build?

@julieg18 feel free to try it out and open a PR with a branch directly on this repo (not from a fork) so that an automatic deployment is triggered on our cloud. If the build works there it should work on prod.

@julieg18 feel free to do any experiments, package updates/downgrades, etc- don't worry about breaking something.

Looks like I don't have permission to push to the repo 🤔

@julieg18 you have it now!

FYI, sharp module is why I had to give up installing the site on mac M1. @rogermparent has said that some customization was applied to image generation code and we can't directly upgrade to higher versions. @julieg18
@shcheklein @jorgeorpinel

FYI, sharp module is why I had to give up installing the site on mac M1. @rogermparent has said that some customization was applied to image generation code and we can't directly upgrade to higher versions. @julieg18

That makes sense. Since I did get some errors on my pull request🤔

I pinned all our gatsby sharp-related plugins to an old version (quite old, now!) because our weird hand-rolled S3 caching mechanism depends on the simple public-dependent image caching that the gatsby image plugins used before the Jobs API V2 was introduced. For some reason, after that update the cache would always be invalid no matter what files we preserve.
The hand-rolled S3 cache script is in scripts/deploy-with-s3.js, which is what is used to invoke the site build in the heroku-postbuild npm script in package.json

From the looks of the script and what you tell here, a major upgrade may take too much time.
BTW, my local Ubuntu 20.04 installation also builds fine. ✅
@rogermparent

@rogermparent, so if I'm understanding correctly, upgrading the sharp package stops the master builds from failing, but will most likely break the caching? And instead of just upgrading the sharp package, we could upgrade Gatsby from 2 to 3?

@rogermparent, so if I'm understanding correctly, upgrading the sharp package stops the master builds from failing, but will most likely break the caching? And instead of just upgrading the sharp package, we could upgrade Gatsby from 2 to 3?

If you can get away with just upgrading sharp, our current packages still accept it, and if fixes things, that's a fine solution. However, if it involves upgrading gatsby-plugin*sharp it'll probably break caching.

The gatsby-*-sharp package did use the sharp package so I did upgrade that one when I was trying to fix the build. But since that probably breaks caching, looks like we'll need to try something else.

The gatsby-*-sharp package did use the sharp package so I did upgrade that one when I was trying to fix the build. But since that probably breaks caching, looks like we'll need to try something else.

We don't necessarily have to ditch it just yet, if you've fixed builds we can at least get an emergency patch in that makes things work while we fix caching.

Good to know, I haven't tried a local build yet but I suspect it'll work there too.

I was correct, builds succeed on my Linux box.


I want to hide a step like i have multiple steps v-step-1 to v-step-10 I want to hide particular 2-3 in between

  steps: [
    {
      target: "#v-step-0", // We're using document.querySelector() under the hood
      header: {
        title: "XXX....",
      },
      params: {
        placement: "right",
      },
      content: `xxx...`,
    },
    {
      target: "#v-step-1",
      header: {
        title: "XXX.....",
      },
      params: {
        placement: "right",
      },
      content:
        "XXX....",
    }

]

Hi @debayan-ghosh,
There is several solutions to this problem.
You can either:

Make your steps array reactive and remove the steps you want to hide, then readd it when you need them
Use the before/after hooks and redirect for example to step 4 from step 1

There is no option to hide a step because this can be handled by different ways and is not relevant for common use cases.

Hi Can you show me an example how to do it?

"Use the before/after hooks and redirect for example to step 4 from step 1"
how do you redirect?

When the next and prev called, Check the condition matched.
And then you can ignore steps that are matchec with condition.
I did like this.

    nextStepTour(currentStep) {
      console.log("next");
      if (currentStep == 0) {
        if (this.$attrs.has_profile) {
          this.$nextTick(() => {
            const tour = this.$tours["myTour"];
            tour.currentStep = currentStep + 2;
          });
        }
      }
    },
    previousStepTour(currentStep) {
      console.log("prev");
      if (currentStep == 2) {
        if (this.$attrs.has_profile) {
          this.$nextTick(() => {
            const tour = this.$tours["myTour"];
            tour.currentStep = currentStep - 2;
          });
        }
      }

My steps are changed whether the user has profile.


Issue and Pull Request Templates

Would help with organization and getting all the relevant info. Requires adding files issue_template.md and pull_request_template.md

Context: https://github.com/blog/2111-issue-and-pull-request-templates

Indeed, I have a pending change to add this (that we can iterate on)

Okay added one here: https://github.com/tensorflow/tensorflow/blob/master/ISSUE_TEMPLATE.md


client.v2.like() returns 403

Hi, I've been using node-twitter-api-v2 for the last week and has been working well 👍
But I'm currently running into a 403 error when trying to use await client.v2.like(myTwitterID, tweetID)
All arguments passed into the method are valid, and I'm using myTwitterID and this tweetID successfully in another method, but doesn't seem to work with await client.v2.like(myTwitterID, tweetID);
I hope I'm missing something obvious!
Docs here:
https://github.com/PLhery/node-twitter-api-v2/blob/master/doc/v2.md#Likeatweet

Hi!
I've quickly checked on my side, and it should work with those parameters.
I've two questions for you:

What's the content of the error?
Catch the error, and get e.toJSON():

try {
  await client.v2.like(...)
} catch (e) {
  console.log(e.toJSON().error)
}

What's your authentification method?

OAuth 1.0, OAuth2 (app-token), OAuth2 (user-context)?
If it's OAuth 1.0, are your sure your app have read/write permissions on the developer portal?
If it's OAuth2 with user-context, what's the token scope you've attributed?

Thanks @alkihis.  I added like.write, then re-authorised by app and everything works perfectly 👍  thank you for your help (I shouldn't try to code at 11pm).


vim-snippets snipmate like snippets does not expand iterpolation

I was able to set the path to the vim-snippets and load them like this:
require("luasnip.loaders.from_snipmate").load({
  paths = {
    vim.fn.stdpath('config') .. '/snippets',
  }
})

But the snippet "date", wich is:
snippet date
	`strftime("%Y-%m-%d")`

does not expand the date. What I am doing wrong?
If is not a feature yet, could it be someday?

You're doing nothing wrong, it just isn't supported yet.

If is not a feature yet, could it be someday?

definitely :D

soooooooooooooooooooooo, with the current master it should work automatically for snippets loaded via loaders.from_snipmate. ls.parser.parse_snipmate can be used otherwise.


🐛 biome migrate prettier command doesn't recognize overrides key.

Environment information
> biome rage

CLI:
  Version:                      1.5.3-nightly.69f9031
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v18.19.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "npm/10.2.5"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Workspace:
  Open Documents:               0

What happened?

Installed nightly release where biome migrate prettier command is added.
Ran the command.

> biome migrate prettier

.prettierrc:8:5 deserialize ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Found an unknown key `overrides`.

     6 │     "printWidth": 80,
     7 │     "tabWidth": 4,
   > 8 │     "overrides": [
       │     ^^^^^^^^^^^
     9 │         {
    10 │             "files": ["*.yml", "*.yaml", "*.json", "*.md"],

  ℹ Accepted keys

  - printWidth
  - useTabs
  - trailingComma
  - tabWidth
  - semi
  - singleQuote
  - bracketSpacing
  - bracketLine
  - quoteProps
  - jsxSingleQuote
  - arrowParens
  - endOfLine

migrate ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Migration has encountered an error: Could not deserialize the Prettier configuration file

Expected result
Ideally, until the overrides key is supported, it should print warning and perhaps ask if the user wants to proceed with ignored config or not.
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

Thank you for reporting. Sounds about right, we should not exit with an error if we can't recognize a key

Since biome also supports overrides field -with a slightly different syntax-, I think it can be mapped during this migration.
From what I see, overrides.*.files field from prettier config, can be mapped as overrides.*.includes. Rest of the configuration.


GraphQL depth analysis provides error "Variable 'id' has coerced Null value for NonNull type 'ID!'"

Description:
GraphQL depth analysis provides error "Variable 'id' has coerced Null value for NonNull type 'ID!'"
Steps to reproduce:

Follow the steps in GraphQL Depth/Complexity analysis to create a business plan named Platinum.

Create a GraphQL API (I used the endpoint https://snowtooth.moonhighway.com/). Make sure to attach the above-created business plan to this API.

Invoke the below mutation (along with the variables).
mutation($id: ID!, $status: LiftStatus!) {
   setLiftStatus(id: $id, status:$status) {
     id
     name
     status
   }
}

Variables:
{"id":"astra-express","status":"CLOSED"}

You will get an error as shown below.

The server will have the below logs.
[2021-11-17 13:40:24,479] ERROR - GraphQLQueryAnalysisHandler [Variable 'id' has coerced Null value for NonNull type 'ID!']

Now, empty the depth and complexity values of the Platinum plan and save it.

If you invoke the same mutation now, it will work.

The problem is in the complexity/depth validation flow it seems.
Affected Product Version:
Master
APIM 3.2.0
APIM 4.0.0

Close the issue as per above commit


Update Slides.gd

Change translatable_properties from String to Dictionary.
Please check if the PR fulfills these requirements:

[x] The commit message follows our guidelines.
For bug fixes and features:

[x] You tested the changes.
[ ] You updated the docs or changelog.

Related issue (if applicable): #118

Thanks!


first draft for ebs csi driver

providing some docs to start with ebs-csi-driver

Great to have this documented!
Lots of nitpicks regarding capitalization, where we are currently undergoing a global change in our docs to use sentence capitalization in all headlines. Also capitalizing Kubernetes vocabulary like "pod" is no longer desired.
I hope I could also help with clarity. :)

Hint: you can use Add suggestion to batch and then use one commit for many suggestions.

Nice Marian this is good feedback, much appreciated 🙂. I will address the rest and will ping you again.


Update expressroute-locations.md

I updated MainOne locations to include London, in addition to Amsterdam in the list of Connectivity through additional service providers. Kindly effect this change in the original article. Thank you

@Omojeje : Thanks for your contribution! The author(s) have been notified to review your proposed change.


docs: Add Java 7 support column

Jeff - is this the right way to add a column?

Need to do this from code. :(


Fix scan issues

The first issue is that if you exit the app while it's scanning and the open it again, the scanning from the previous session will still go on, and when you try to start scanning again you will get an error "Already scanning"
-The second thing you should fix is to use a StreamBuilder with the stream FlutterBlue.instance.scanResults, and display the results that comes out of there. See the progressor app or search through StackOverflow

Issues with third-party packages need to be reported to the developers of those packages, not the Flutter project.

Sorry, this was meant for another repo. Apologies for the inconvenience.


Phases for formatting, partitioning, mounting and provisioning

Problem
Related issue: harvester/harvester#1718
To prevent re-entry of critical sections in blockdevices reconcilation, introduce phases for those criticial operations, including

Partitioning (on disk)
Formatting (on partition)
Mounting (on partition with a filesystem)
Provisioning (on partition with a mounted filesystem)

Be aware of that when current phase is a verb-ing, blockdevice cannot perform any further operation. This is enforce in the reconcilation logic.

Changes

❗ Only identify WWN as GUID of a block device: For simplicity, can add more options in the future
❗ Remove NDM_AUTO_GPT_GENERATE related env and flag: Since we are going to identify WWN only, this flag is unnecessary.
❗ Remove Spec.Filesystem.MountPoint: Use Filesystem.Provisioned instead to determine whether a provision is needed. The mount point now is an implementation detail and not configuralble.
❗ Refactor the whole logic of blockdevice reconcilation: Basically, we use a simple state machine pattern as the source of truths to determine which phase the blockdevice is. Also, we're not rely on Status.DeviceStatus.FileSystem anymore since it might be quite outdated, we now consult the system directly.
💅🏾 Extract scan/filter logic out from blockdevice controller: Tidy up the mess inside blockdevice controller. The new Scanner struct can be reuse in udev as well.

Test Plan
KVM/libvirt env

Note: You can attach disks via either commandline or virt-manager GUI, but you need to attach it with SCSI/IDE controller. That's because virtual disk in libvirt cannot be attached with a WWN.

Create a harvester cluster
Create a disk (cmd: qemu-img create /path/to/disk.img 10G)
Attach the disk to a node (cmd: virsh attach-disk <vm-name> /path/to/disk.img sda --config --live --wwn 10000000c9b0513a)
Head to dashboard Hosts > Edit Config > Disks. Then select any disk/partition to provision it.
Verify the provision succeeds.
Unprovision the disk via command (UI is not ready yet): kubectl -n longnhorn edit bd. Then find the resource of the blockdevice then set spec.fileSystem.mountPoint = "".
Verify the disk is unprovisioned and unmounted.
Detach the disk (cmd: virsh detach-disk harv-0 sdd --config --live)
Verify the device is gone in both system and k8s blockdevice.

TODO

[ ] Dashboard UI needs updates

[ ] For unprovision operation, since spec.fileSystem.provisioned is removed. Please set spec.fileSystem.mountPoint = "" instead.
[ ] Multiple conditions are added. Please consult the changes if you want to display them: https://git.io/JyTQW. When there is any verb-ing condition is true. We should prevent user from update any spec in frontend.

[ ] Need to update CRD manifest in relevant NDM chart and bump a version

A glimpse of the new log messages:
time="2021-12-23T07:10:35Z" level=info msg="Start GPT partition for e9a03081906692ecbff85a9c761f3028"
time="2021-12-23T07:10:35Z" level=info msg="Await GPT partition for e9a03081906692ecbff85a9c761f3028"
time="2021-12-23T07:10:35Z" level=info msg="make gpt partition of device /dev/sdc"
time="2021-12-23T07:10:35Z" level=info msg="Finished GPT partitioning for e9a03081906692ecbff85a9c761f3028"
time="2021-12-23T07:10:35Z" level=info msg="Add new block device dd40a9cb0e38604e52fff9484eaa2a9e with device: /dev/sdc1"
time="2021-12-23T07:10:35Z" level=info msg="Start formatting for dd40a9cb0e38604e52fff9484eaa2a9e"
time="2021-12-23T07:10:35Z" level=info msg="make ext4 format of the device /dev/sdc1"
time="2021-12-23T07:10:35Z" level=info msg="Await formating for dd40a9cb0e38604e52fff9484eaa2a9e"
time="2021-12-23T07:10:35Z" level=info msg="Update existing block device status dd40a9cb0e38604e52fff9484eaa2a9e with devPath: /dev/sdc1"
time="2021-12-23T07:10:35Z" level=info msg="Await formating for dd40a9cb0e38604e52fff9484eaa2a9e"
time="2021-12-23T07:10:35Z" level=info msg="Finished formatting dd40a9cb0e38604e52fff9484eaa2a9e"
time="2021-12-23T07:10:35Z" level=info msg="Start mounting dd40a9cb0e38604e52fff9484eaa2a9e on /var/lib/harvester/extra-disks/e9a03081906692ecbff85a9c761f3028"
time="2021-12-23T07:10:35Z" level=info msg="Await mounting dd40a9cb0e38604e52fff9484eaa2a9e on /var/lib/harvester/extra-disks/e9a03081906692ecbff85a9c761f3028"
time="2021-12-23T07:10:35Z" level=info msg="Finished mounting dd40a9cb0e38604e52fff9484eaa2a9e"
time="2021-12-23T07:10:35Z" level=info msg="Start provisioning dd40a9cb0e38604e52fff9484eaa2a9e on /var/lib/harvester/extra-disks/e9a03081906692ecbff85a9c761f3028"
time="2021-12-23T07:10:35Z" level=info msg="Finished provisioning dd40a9cb0e38604e52fff9484eaa2a9e on /var/lib/harvester/extra-disks/e9a03081906692ecbff85a9c761f3028"

The mechanism like "state machine" is used to handle hardware processing state, a couple of consideration points:

A bunch of conditions are used, it is the limitation of condition.Cond, which can only express true/false. The alternative way is one condition variable with different values expressing different states.
As a general rule, the state machine needs assistant of timer to avoid suspending in a state due to error handling or some other thing.  This needs clear design specification to express state switching and to design test cases.

The mechanism like "state machine" is used to handle hardware processing state, a couple of consideration points:
1.  The alternative way is one condition variable with different values expressing different states.

2. As a general rule, the state machine needs assistant of timer to avoid suspending in a state due to error handling or some other thing.  This needs clear design specification to express state switching and to design test cases.

Thank you! The mechanism really needs a more proper design. I have no experience of coining a state machine in Golang. Do you have any useful references at hand?

The mechanism like "state machine" is used to handle hardware processing state, a couple of consideration points:
1.  The alternative way is one condition variable with different values expressing different states.

2. As a general rule, the state machine needs assistant of timer to avoid suspending in a state due to error handling or some other thing.  This needs clear design specification to express state switching and to design test cases.

Thank you! The mechanism really needs a more proper design. I have no experience of coining a state machine in Golang. Do you have any useful references at hand?

Two "state machine" can be referred:
TCP state machine (quite complex), BGP state machine, following article explains many details of BGP state machine:
http://net.cmed.us/Home/routing-theory/bgpv4/the-finite-state-machine

This is not a formal state machine diagram but I guess it can describe the gist.
Each "verb-ing" state trigger a side effect action. the transition would not proceed until the action is complete or timeout, .

draw.io source code
<mxfile host="app.diagrams.net" modified="2022-01-03T06:12:33.380Z" agent="5.0 (Macintosh)" etag="YJhOSquO9jm3DtMzuSCb" version="16.1.2" type="device"><diagram name="Page-1" id="58cdce13-f638-feb5-8d6f-7d28b1aa9fa0">7R1rk5s28Nfcx2R4+vExd5dLO5N0rr02bfpNMbKtBiMHy/Y5v74SCBmEMLLNQ3chmUmMEAL2vavd5ca9Wz1/iMF6+QkHMLxxrOD5xr2/cRzbm7j0PzZySEemk0k6sIhRwCcdB57QD8gHLT66RQHcFCYSjEOC1sXBGY4iOCOFMRDHeF+cNsdh8a5rsIClgacZCMujf6OALPmobVnHE79AtFjyW098fuIrmH1bxHgb8ftFOILpmRXIluFTN0sQ4H1uyH1/497FGJP01+r5DoYMrBnE0useKs6KR45hRHQuiO7efHa+b/9wdneTH3MM5xH4/MZ20mV2INxyWNzDHZrBPw9reI823/izk0MGqs0erUJA39K95ZfCmMDnyoeyxatS6oF4BUl8oFP4BRlwON3Yfnq4PyLBG/Epyxz8vQmfCDjiF2LlIwToDw6EcwDilwBSAgFD+Lry5TmNgq/ZdKsMlBO4qASVWwSVUwaVO1WBym8AVL//CkOy37+Zb/1/D7vn3ReAoIp2/oq+RXgflSCWcAhki9mUbvZLRODTGszY2T2VKHRsSVYhPw3iGZcQjkcP5ygM73CI42Qpd07/zCw6viEx/gZzZ96/G92ORuxMxmls2gyv0Iz/DsFXGN4Kls2uTZiW3ghH5AGsUMgg/BnGAYgAH+bPQ984Pc7d1Ur+sMcO0SKiYzOKZRgL9qhHu19BSpWUMClSwqRMCbajoISMkZonBLeeZ+gyVJjDIqYpotbsPIyCJwIILGNbQLca20Xaeu24d7NLOPI9lRxQIN9tC/nZwieRH1Btyw9xTJZ4gSMQvj+O5pDIwHmc8xHjNcfsf5CQA0cG2BJcJCVKQu+YIcCQEILNhuGdDT6gUFBbJQmdia0N3sYzeIoh+EQC4gUkGiKUAegk9mMYAoJ2RXOleUbWUH4nGXlD35i8MlYOUEzVOcJskGKeMVl77G33zc72uEQCjxSniAEARYtBs3ep2Z3M/+hPtU+ryYFifaCGDqnBdXqnBl9HQfxkyl4ELGqVvWuUss8WzuHyAaBw4OqWudoZm8bW7kTB1aOQJMbPjv5csJ8bFEBGvfM5i8BRAtnOZhAmdPHuhj1vesXXOLsgG6HPlFtGsfKHxz9TUKd6peo6iSopuIlEejIOGVLQDITv+IkVCoJUAsEN+sEjNAz7a4wikoDVv73x79laVOhsON2UyDUjuRxt86HWqEYiGmescPq9Lg1Fyt09SP4TYoO5HplWuAwbtaI+Y5R6UT81StS7ZSvOLOTlFHpLqMv8mlrUZThuDnX80kcmY3Kenidx9FSK06avxK/Kx/VrFnLl2Hj6yqWFEkoS73M5cXmeBnEN0b9mwwOmRP+ccrigoOCtDDZ09PuWbXXdhnBOjkeyWcBgTC+bA87N2bw7yg2IAtexfoP78uWbNZy9pdQDnw4bAldv55jyzgOOV4AQZtFayWIWielTHs2L9GanrRVtqyN5r9dhc2S7caOyZSqc0jx5Oa1Zpi/PvezCDnF0lVmm9QyxQ+ypcfEDjqHedgocTUw6jWNSz5qwvYbMEhHL7MgscUenNZPaqZ3zCIim54pj7akErSDeksG5VYVEbJlWFN6tpVA8fmuKxzhBZaYmyrisXn7Zrcgv+nrgkJvAab1SvLlyFo1rSbSSrtioKBKizxxq6lvtaXvjo27UnkCRRBdnqz0Rza1aqGW151h2L6T1jMg/7PK3Pj/6kjtz/8xXTg4O/KDgdRf9u5e6xdO8lLtKi3k13nlqfLxfocT0Sb3lZJPfgjuYUDXFs2PNligMKCzpzyBJDh2MGJURUwzNiGTMvPOsis205jx7Kgt4sGEquaSWu7NIpyHc7ViOaQju26yY6mKyJ2/anVxoVsgLee2ZFWoUlGXJsU7g8bhzK1Ffs8UCvmSkKaoFfNXG+aSJ8LcaLCoFK8GgrWqB0UlY1VcLKAsrxtO2tJE9KmcZfKKihxscIArov48x2qFNRaphjphKIuU2+cvO8EkfUZRZBroAHVcgqRLGVTyZB7KKHt1TmRz8bn8woogWIcyRv4RTT5EdqKoAcdzi3UBIba8IEHjLJP/mSnFR4d+pPN6S5XnEv5Y9OeQh6bDXpeSroN6OswvH5Yy0KqKpjtEONNMhzdh+/0RjnBHclpdzGof1QQxLO3tpbFYYwx6XC8z+ilZCeQws3ybLO64U2Oib5cUTdMvh7YUru2F/VztPfWxY1sBYlWFWsgseY5z6DoNtYIRtIFKWe7QNfppd3GuFQ7YBryEcDAuCOipPc9AO5xKAfhXT2KwyJqGtCsbhOlMGg4HYuYHYv1MoXJ2+KpoS34QuwTKSN0lG8uvaMm2KdKSIpq2qd+62qskyo1SmyT21K1WDiOXWZz9YHdXOjCS6Ebs+526rlRYaSwu1na1ja8XJ2xNUIKDOksjqSNM9PuJoscRxpL/sIMTyfo+qnrdbIWarAuk/uRDTT+Gy+hFio0tTDksLyUkGbQsxRSeBToVYDFd4B/NybB7j1SDJzrfkbQ17bNypKMsk1wtx7/uXc7rJbIJr25ZzE6/GxtKVc6WFZKuvbTnn1si5vopdE28zA1aykBWh8KTQe62Vr01JQlvut+GVJaGoPuokm9dxB0l4niT0dCWh25EkHE2LRDW+1OKbSEUmI69rSdhL85djkYmjX2VC6Sk+pFeN/exYXMYOjtclR32Up3RG66Zt33jlQO3QQ/qCTiJn566a1kPaMy7u2l7Z2ViTrTP7or6cofG461W49FVBTRmXQxvhFrm7/zbCE43KCIOs1W4r07Tbt/hON5apaCd4ZvlzY/UCnipTpxToe8iVqA4ZXn3bDAZ0p56YUeJqtJTRSAzXbeIhoiKGGBq2ssS5SmwMeaEmSI3+2x0LrVpDNSdbQQ0k0yLJuHI3lv41zVTl0wztxLroxHE2+ZSa+fTeToxKwT7sEnVXHhEiNbQrj67dIuKjGu24DbNbpjo9k82xW1tq66GN6Mw7fDFdwBy7xp9ueYPGHqvCqQZsVQ99ma/Rb8b0ZbZ9Mxxv431rwYj1Oqp5IXeljjIjgmuOGvL06+cb//yHWs28mmbNjqVV4tteCmm+UId3QnztSaMNOVulDxP1nf1u+8YJLjN1k2A6Dd3UeBveK6u0jCvsNsVF0ijSajwDSFOnyMG5iz9wZElarnXlVLPLYFDe7/GiNaDiN7/E4Fxp6TPpA0uKyLOjqoBoL+/XMkOdvZhYkfYXCazGlZqm/GqsCawsUVtP+1WV1cukOHzqrZk9ME/qqqCQRG2ldClfwe3HwuLZ2+Ig2cF4KzK5K5K3L7GsJTlwoVRSTzzP0L5WBFV/FaXxvtCnLaO23fZtdaON1+S213TNPkGb1Xuk8leoXcUeaafyxQwz5/xv1DYjNk73WsoLjmo+bNxycX3JGr7UhSslAck77RWWy9mfd3LU92n3805uhs9hc7850s+StDTK9zrqOiPatst9rq42v+lhjJmffpweg/XyEw4gm/E/</diagram></mxfile>

@johnliu55tw I think this is ready to review. Thanks!

I'm testing auto-provisioning 20 disks on KVM. 13 are added and the other 7 failed with error like this:
Failed to provision onto node harvmultidisk: Operation cannot be fulfilled on nodes.longhorn.io \"harvmultidisk\": the object has been modified; please apply your changes to the latest version and try again

I think it's because all those 20 disks are trying to modify the node.longhorn.io resource. A retry mechanism should solve this problem.

All review comment are addressed.

Add a few basic unit tests for state transition.
Remove mountPoint from spec in order to hide it as an implementation detail.
Complete the retry and timeout mechanism

New state machine diagram

draw.io XML
<mxfile host="app.diagrams.net" modified="2022-01-11T04:26:42.425Z" agent="5.0 (X11)" etag="gRtRtdG4QDSksM6krHdx" version="16.1.2" type="device"><diagram name="Page-1" id="58cdce13-f638-feb5-8d6f-7d28b1aa9fa0">[encoded data, 4488 characters]</diagram></mxfile>

Seems like NDM can't recover the disk from system rebooting. It just keeps trying to re-provision the disk onto Longhorn:
time="2022-01-12T08:08:02Z" level=info msg="Finished phase Unprovisioning" context=Effect device=f13387e74136b309cabbe51442ef02c3
time="2022-01-12T08:08:02Z" level=info msg="Start provisioning" context=Effect device=f13387e74136b309cabbe51442ef02c3
time="2022-01-12T08:08:02Z" level=info msg="Finish provisioning" context=Effect device=f13387e74136b309cabbe51442ef02c3
time="2022-01-12T08:08:02Z" level=info msg="Finished phase Provisioning" context=Effect device=f13387e74136b309cabbe51442ef02c3
time="2022-01-12T08:08:02Z" level=info msg="Start unprovisioning" context=Effect device=f13387e74136b309cabbe51442ef02c3
time="2022-01-12T08:08:02Z" level=info msg="Continue polling in phase Unprovisioning" context=Effect device=f13387e74136b309cabbe51442ef02c3
(repeat)

Because after a reboot, the partition would be unmounted, and seems like NDM doesn't know how to handle this in phase Provisioned.

Updated. Should be review-ready again. 🙇🏾

Add more uni tests for transitions
onCmdTimeout now can retry if updating blockdevice fails
Recover from "filesystem not mounted but is in phase Provisioned`

❗ Caution
There is a peril that NDM currently gets filesystem information from blockInfo.GetFileSystemInfoByDevPath. This device path is unstable after reboot. We need to seek the right partition by UUID. But I personally don't want to add more commits on this PR. Let's leave it to next one.

Fixed the CI issue by removing unwanted go:build. Thanks everyone.

in general, the design change is looking good to me, but have we tested the upgrade case? seems the CRD change is not handling its backward capability properly.

Haven't go through the full upgrade path, but has simulating an upgrade by 1) umounting a disk and update  manifest and then patch the image of the controller. The following scenarios are fine to me.

Attach a disk. And then upgrade: Some old conditions/statuses might left over. But as long as spec is in its initial state, the update won't affect anything.
Attach a disk. Then provision it via UI. And Then upgrade: The disk should remain provisioned. If the old and new mountpoints mismatch, NDM will unprovision and unmount the disk and start over to provision.
Attach a disk with partitions (partitioned manually). Then provision the part. And then upgrade: Act like the first but with a partition

close in favor of #27


:sparkles: Add Netlify logo on all builds

I have added the "Deploys by Netlify" logo at the bottom the Homepage of each build (and each language):

Vuepress
Docusaurus
Docsify
Production
GitHub

I also fix a typo in the README.md file of the Production build README.md file. I can make a different PR for this one if you want

Made with GitHub Codespace ❤

Dope! Thanks @bpetetot


[MINOR] improvement(UI): Changed package manager from yarn to pnpm

What changes were proposed in this pull request?
Changed package manager from yarn to pnpm.
Why are the changes needed?
I'm not sure if it's a problem with yarn in the gradle-node-plugin or a problem with the local gradle environment cache.
After switching Java versions, using yarn prompted an error, but using pnpm did not.
Coincidentally, the frontend can also switch to using pnpm.
Compared to yarn, pnpm has better performance and can save a lot of disk space.
Does this PR introduce any user-facing change?
N/A
How was this patch tested?
N/A

I think you should:

Find out the root cause of gradle build issue, instead of just using different building tools
This is not a minor issue, I think we should have more inputs.

@xunliu can you please shepherd this PR, thanks.


qpm install fails

C:\Users\cody\Downloads>qpm install com.github.benlau.quickflux
INFO: Package com.github.benlau.quickflux has a different license (APACHE_2_0) than it's dependant (NONE).
Installing<EMAIL_ADDRESS>QPM: 2016/10/24 14:13:12 ERROR: GetFileAttributesEx C:\Users\cody\Downloads\vendor\benlau-quickflux-38e3bda\tests\quickfluxunittests\qmltests\qpm.json: The system cannot find the file specified.

C:\Users\cody\Downloads>qpm --version

qpm is a tool for managing Qt dependencies

Usage:
        qpm COMMAND [args]

The currently supported commands are:

        verify                  Verifies the package PGP signature (experimental)
        init                    Initializes a new module in the current directory
        info                    Displays information about the specified package
        uninstall               Uninstalls a package
        publish                 Publishes a new module
        check                   Checks the package for common errors
        sign                    Creates a PGP signature for the package (experimental)
        ping                    Pings the server
        search                  Searches for packages containing the given string
        list                    Lists all packages in the registry
        install                 Installs a new package
        help                    Shows the help text for a command

<EMAIL_ADDRESS>

C:\Users\cody\Downloads>

I guess it is related to this bug : https://github.com/Cutehacks/qpm/issues/24
If the qpm.exe is not updated on qpm.io yet, I think you need to compile qpm by latest source code. In case you just need QuickFlux, you may consider to download the tar.gz from https://github.com/benlau/quickflux/releases or use git submodule

I was able to get it to work by adding the path to the quickflux.pri in the application's .pro file


Evaluate testtrain mode

Proposed changes:

A new evaluate mode that dynamically creates a test set from the training data set and then runs an evaluate. Discussed in issue #1625. Example syntax:

python rasa_nlu.evaluate.py --mode traintest --config nlu_config.yml --data training/ --pct 90 --cutoff 5

Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog

This one went stale, sorry for that. Files have moved on the master branch, so we can't merge this one anymore.


Query: Exception with nested Select

Hello,
the problem is when I want to make reusable Projections for select. I'll explain.
I have the following interface:
public interface ISelector<TModel>
        where TModel : class
    {
        Expression<Func<TModel, object>> Model { get; }
    }

And the folloing classes:
public class ItemSelector : ISelector<Item>
    {
        public System.Linq.Expressions.Expression<System.Func<Item, object>> Model
        {
            get
            {
                return item => new
                {
                    Name = item.Name,
                    Resources = item.Resources.AsQueryable().Select(new ItemResourceSelector().Model)
                };
            }
        }
    }

public class ItemResourceSelector : ISelector<ItemResource>
    {
        public System.Linq.Expressions.Expression<System.Func<ItemResource, object>> Model
        {
            get
            {
                return resource => new
                {
                    Name = resource.Resource.Name,
                    Amount = resource.Amount
                };
            }
        }
    }

Finally, I have the following Query:
 return DbContext.Items
                .Include(item => item.Resources.Select(resource => resource.Resource))
                .Select(new ItemSelector().Model);

It gives entity framework error 1025. The problem is when I Select the related property Resources, it requires a Func and not Expression. But since entity framework 6 it is possible to use AsQueryable in ICollection properties of an entity, and it works fine if you are using inside a filter method like Where, Any, etc.. But not when you are "Selecting".
I hope this is only a bug so I'm posting as an issue.

This doesn't seem like a very common scenario, so it's probably not critical for initial release of EF7. Assigning to @maumar to see if there are any quick wins we can do to unblock this. If it's more involved then we will deal with it post initial release.

Is this Include valid scenario which we would want to fix?

@fabiohvp We're not 100% what the intention was when this issue was filed, but in EF Core things have progressed a lot in the last two years. The Select expression inside Include is not supported in EF Core--instead use Include/ThenInclude syntax, as described in the docs. So closing this for now. If you believe there is still an issue with EF Core, then please re-open and provide more details. If this was supposed to be an issue on EF6, then please file a new issue on https://github.com/aspnet/EntityFramework6


Nested block is redundant.

Why this issue?
https://sonarcloud.io/project/issues?resolved=false&id=asyncapi_cli&open=AYnVPAwn2dO9nyWI8Jp5&tab=why
Where's the issue?
https://sonarcloud.io/project/issues?resolved=false&id=asyncapi_cli&open=AYnVPAwn2dO9nyWI8Jp5&tab=code

@Souvikns I have removed the redundant code. please merge this.


DOES NOTHING

PS C:\Users\damir> mountvol X: /s
PS C:\Users\damir>
PS C:\Users\damir> copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y
Copy-Item : A positional parameter cannot be found that accepts argument '/Y'.
At line:1 char:1

copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig. ...

  + CategoryInfo          : InvalidArgument: (:) [Copy-Item], ParameterBindingException
  + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.CopyItemCommand

PS C:\Users\damir>
PS C:\Users\damir> bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
Invalid command line switch: /encodedCommand
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.
PS C:\Users\damir>
PS C:\Users\damir> bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
The set command specified is not valid.
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.
PS C:\Users\damir>
PS C:\Users\damir> bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit.exe : The command parameter was already specified.
At line:1 char:1

bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d ...

  + CategoryInfo          : InvalidArgument: (:) [], ParameterBindingException
  + FullyQualifiedErrorId : ParameterSpecifiedAlready

PS C:\Users\damir>
PS C:\Users\damir> bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO
The set command specified is not valid.
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.
PS C:\Users\damir>
PS C:\Users\damir> bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
The set command specified is not valid.
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.
PS C:\Users\damir>
PS C:\Users\damir> mountvol X: /d

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

ID: 41c2cb44-269d-3334-019a-726eb5432f1c
Version Independent ID: 251024cc-b818-18c6-a112-4ac0276cb4b1
Content: Manage Windows Defender Credential Guard (Windows 10)
Content Source: windows/security/identity-protection/credential-guard/credential-guard-manage.md
Product: w10
GitHub Login: @brianlic-msft
Microsoft Alias: justinha

Absolute rubbish.  The poster should be ashamed of himself.
This "solution" has been posted around multiple sites for years, and hasn't worked in about as long.

Those commands are meant to be run in "An Elevated Command Prompt" (cmd) not Powershell. If anyone else has these issues please use cmd.

@cacodemon9000 : Please take note of what botmoto has commented above.
@e0i : Looks like this issue can be closed (unless you know of a reason to keep it open).

Please update the commands above to reflect the correct syntax and switches.  (i.e. mountvol’s depreciated /s)
From: Trond B. Krokli<EMAIL_ADDRESS>Sent: Saturday, May 11, 2019 12:32
To: MicrosoftDocs/windows-itpro-docs<EMAIL_ADDRESS>Cc: G.M.C<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-itpro-docs] DOES NOTHING (#1924)
@cacodemon9000 https://github.com/cacodemon9000  : Please take note of what botmoto has commented above.
@e0i https://github.com/e0i  : Looks like this issue can be closed (unless you know of a reason to keep it open).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/windows-itpro-docs/issues/1924#issuecomment-491525439 , or mute the thread https://github.com/notifications/unsubscribe-auth/AFLFZMZMSAOY5HTXGS7WL6DPU3YJ3ANCNFSM4F6VZ7OQ .  https://github.com/notifications/beacon/AFLFZM5QI6LXT52MODCXNBLPU3YJ3A5CNFSM4F6VZ7O2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVGBKPY.gif

I presume you mean deprecated -- but which version(s) are affected? I tested it on an updated Windows Server 2016 a couple of weeks ago and it seemed to work OK then.

Please have a look at issue ticket #3234 for a closely related discussion on this topic.

@cacodemon9000. I have an idea.   Copy the  secconfig.efi   to  C:\EFI\Microsoft\Boot\
and then boot the computer by using windows dvd  into windows RE mode.
Go to the command prompt ,  use diskpart, format the efi partition , assign drive letter .exit
use  bcdboot command  to copy required files to efi partition
exit and restart the windows

@cacodemon9000 : Please take note of what botmoto has commented above.
@e0i : Looks like this issue can be closed (unless you know of a reason to keep it open).

@officedocsbot close


Global: add global validators to settings

Changes

ValidateInstanceInContext split into maya and nuke plugin

added settings for each of them

context anatomy collector also stores task type of  context
start/stop timer plugins are using settings stored in context instead of loading them again
ValidateIntent is for all hosts by default and added profiles to filter validations (by default is plugin disabled)
ValidateVersion added active attribute to be able define if is activated by default

QUESTIONS

ValidateContainers - currently has settings in each host settings and not sure if should be added to global publish plugins settings and if yes than it will probably need profiles but at the same time should have optional (maybe) does it make sense to have both optional + active and profiles under that?
ValidateResources I actually don't know why are resources validated?

Task linked: PYPE-1332 Add Global validators to settings

missing ValidateVersion active attribute in setting schema

Fixed


Wireguard: Routes Not Added for Allowed IPs Outside of Tunnel Address Subnet on 24.1.2 and Above

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
In 24.1.2 and above, Wireguard does not add routes for IP addresses contained in peers' Allowed IPs that are outside the subnet(s) of the associated instances' Tunnel Address(es).
To Reproduce

Create a Wireguard instance with defined IPv4 and IPv6 tunnel addresses, e.g. <IP_ADDRESS>/24 fe80::2001:db8:1:1/64
Create one or more peers with Allowed IP entries containing addresses within the instance's tunnel addresses' subnets, e.g. <IP_ADDRESS> fe80::2001:db8:1:2 and one or more addresses outside of the instance's tunnel addresses' subnets, eg. <IP_ADDRESS> 2620:12a:2032:4::1

Routes that would be created to route traffic for <IP_ADDRESS> and 2620:12a:2032:4::1 to the resulting Wireguard interface, e.g. wg1, are not created.
Relevant log files
The following error lines observed in /var/log/wireguard/latest.log:
<35>1 2024-03-06T13:48:25-06:00 opnsense.example.com wireguard 9297 - [meta sequenceId="2"] /usr/local/opnsense/scripts/Wireguard/wg-service-control.php: The command '/sbin/route -q -n add -'inet' '/' -interface 'wg1'' returned exit code '68', the output was 'route: bad address:'
<35>1 2024-03-06T13:48:25-06:00 opnsense.example.com wireguard 9297 - [meta sequenceId="3"] /usr/local/opnsense/scripts/Wireguard/wg-service-control.php: The command '/sbin/route -q -n add -'inet6' '/' -interface 'wg1'' returned exit code '71', the output was 'route: : Name does not resolve'

Environment
OPNSense 24.1.2 and Above (amd64)

"<IP_ADDRESS>" isn't a valid allowed IP, so what are you actually inputting there?

Oh it's valid for whatever reason but it should have a subnet mask...

If you can confirm these work with /32 attached we can consider a migration for these single-IP entries, but OTOH if you have a tunnel address <IP_ADDRESS>/24 all of its addresses are routed automatically by the kernel.

Oh it's valid for whatever reason but it should have a subnet mask...even the help text says so.

You're right, and when the entries were made way back when they did not include a /32 or /128 for the subnet mask. Explicitly adding subnet masks caused the routes to be added.
Perhaps we can tweak the input checking for the Allowed IPs to ensure that a subnet mask is included?

Yep, but we have to migrate the "wrong" entries as well before tightening the validation for it.

I'm still curious why you need a <IP_ADDRESS>/24 and a <IP_ADDRESS>/32 to make things work. Both should be in the routing table?

Ok maybe I got hung up on things... you need the allowed IPs for the outside addresses <IP_ADDRESS>, inside addresses should be fine without "allowing" them. It's quite counter intuitive in the official WireGuard wording.

I'm still curious why you need a <IP_ADDRESS>/24 and a <IP_ADDRESS>/32 to make things work. Both should be in the routing table?

You are right, the /32 is redundant in this case.

Ok, thanks for confirming. Let me work on a migration for this tomorrow to get this ironed out rather sooner than later.
Cheers,
Franco


Can not disable Use pre-signed URLs for GCS Source Storage

When creating or editing a GCS Source Storage, disabling the Use pre-signed URLs does not work.
To Reproduce

Go to Project -> Setting -> Cloud Storage -> Add Source Storage -> GCS
Fill the form and disable the Use pre-signed URLs toggle button.
Save the form.
Click on the three dots and Edit.
Use pre-signed URLs is enabled.

Expected behavior
Use pre-signed URLs should be disabled.
Screenshots

Environment (please complete the following information):

Docker
Label Studio Version 1.0.2

Additional context
Value sent to backend when form is submitted with Use pre-signed URLs disabled:
{
  "project": "3",
  "bucket": "test",
  "regex_filter": ".*",
  "use_blob_urls": true,
  "presign_ttl": "1"
}

Value sent to backend when with the Use-pre-signed URLs enabled:
{
  "project": "3",
  "bucket": "test",
  "regex_filter": ".*",
  "use_blob_urls": true,
  "presign": "true",
  "presign_ttl": "1"
}

Seems like when the toggle button is disabled "presign": "false" is not sent. Might be a frontend regression.

I just tried this with 1.1.0 and issue still persists.


Standardisation of strings for disasters

We should check these at the end, it concerns several SDGs:

1.5 - By 2030, build the resilience of the poor and those in vulnerable situations and reduce their exposure and vulnerability to climate-related extreme events and other economic, social and environmental shocks and disasters
2.4 - By 2030, ensure sustainable food production systems and implement resilient agricultural practices that increase productivity and production, that help maintain ecosystems, that strengthen capacity for adaptation to climate change, extreme weather, drought, flooding and other disasters and that progressively improve land and soil quality.
11.5 - By 2030, significantly reduce the number of deaths and the number of people affected and substantially decrease the direct economic losses relative to global gross domestic product caused by disasters, including water-related disasters, with a focus on protecting the poor and people in vulnerable situations
13.1 - Strengthen resilience and adaptive capacity to climate-related hazards and natural disasters in all countries

Suggestion: We check the different strings, and make sure they are standardised as much as possible, but adapted when necessary (in light of the the target language or that a specific term doesn't work in that context, e.g. cytokine storm).

We should check what we have against resources to do with Sendai and UNDRR

https://www.preventionweb.net/sendai-framework/sendai-framework-at-a-glance
https://www.undrr.org/terminology
https://www.preventionweb.net/publication/hazard-definition-and-classification-review - appendix 6 has a list of disasters

SDG01: climate-related extreme events and other economic, social and environmental shocks and disasters
SDG02: climate change, extreme weather, drought, flooding and other disasters
SDG11: disasters, including water-related disasters
SDG13: climate-related hazards and natural disasters
I suggest to assume per default that disasters are defined as the outcomes of “natural”/climate made hazards.  this is what SENDAI mostly is concerned about.
In SDG1 include other economic, social  shocks and disasters.
In SDG2 include climate change itself, not only  hazards and disasters
  OR ("extreme$" NEAR/3 ("climat*" OR "weather" OR "precipitation" OR "rain" OR "snow" OR "temperature$" OR "storm$"))
  OR "drought$" OR "flood*" OR "cold spells"
  OR "tropical cyclone$" OR "typhoon$" OR "hurricane$" OR "tornado"
  OR "heatwave$" OR "heat-wave$" OR "wildfire*" OR "forest fire*" OR "wild-fire*" OR "forestfire*"
  OR "earthquake$" OR "volcanic activit*" OR "volcanic emission$" OR "volcanic eruption$"
  OR "landslide$" OR "rockslide$" OR "surface collapse$" OR "mud flow$"
  OR "land-slide$" OR "rock-slide$" OR "mud-flow$"
  OR "avalanch*"
  OR ("sea level" NEAR/3 ("chang*" OR "rising" OR "rise$"))

OR
((("natural" OR "anthropogenic" OR "environmental" OR "climat$")
NEAR/3 ("hazard*" OR "catastroph*" OR "disaster*"))
OR
only SDG2
("climate change" OR "climatic change$" OR "global warming" OR "changing climate")
only SDG1 or similar
                  OR (("volatil*" OR "unstable" OR "instability") NEAR/5 ("market$" OR "price$"))
                  OR "financial crash*" OR "economic downturn$"
                  OR "war" OR "wars"
                  OR (("volatil*" OR "unstable" OR "instability" OR "unrest") NEAR/5 ("political$" OR "civil"))
                  OR "outbreak$" OR "disease risk$" OR "pandemic$" OR "epidemic$"
                  )

Resolution:

The string for SDG1 and SDG2 can be alike (natural/climate/economic etc.)
the string for SDG 11 and 13 can be alike (only natural/climate).

Caroline will go through the links above and see if the string can have other terms add/more objective choices of terms. Selected terms are already taken from Sendai (subjective choices).

Used Murray, V. et al. (2021) Hazard Information Profiles: Supplement to UNDRR-ISC Hazard Definition & Classification Review: Technical Report: Geneva, Switzerland, United Nations Office for Disaster Risk Reduction; Paris, France, International Science Council. DOI: 10.24948/2021.05 (link).
Hazard =/= disaster. A number of hazards on this list do not seem to fit the description of a disaster; for example, "chlorine" is listed as a chemical hazard, but if research is about a chlorine-related disaster it would have to be used together with words such as hazard, catastrophe etc. Therefore some hazards from the list are included where we think they could cause "serious disruption of a community" even when used as a stand-alone term (e.g. tornado); others are included more generically with "disaster" terms (e.g. pesticides).
I have excluded biological disasters from "natural" disasters.
Natural disasters and climate-related hazards
General terms (extreme climate, and natural disasters), then Hydro-meteorological, then Geohazards (not already covered), then Environmental (subset that is related to climate).
  "extreme$" NEAR/3 ("climat*" OR "weather" OR "precipitation" OR "rain" OR "snow" OR "temperature$" OR "storm$" OR "wind$"))
  OR (("natural" OR "climat*") NEAR/3 ("hazard$" OR "catastrophe$" OR "disaster$"))
  OR "rogue wave$" OR "tsunami$" OR "tropical cyclone$" OR "typhoon$" OR "hurricane$" OR "tornado"
  OR "drought$" OR "flood*"
  OR "avalanche$" OR "landslide$" OR "land-slide$" OR "rockslide$" OR "rock-slide$" OR "rockfall$" OR "surface collapse$" OR "mudflow$" OR "mud-flow$"
  OR "cold spells" OR "cold wave$" OR "dzud$" OR "blizzard$" OR "heatwave$" OR "heat-wave$"
  OR "earthquake$" OR "volcanic activity" OR "volcanic emission$" OR "volcanic eruption$" OR "ash fall" OR "tephra fall"
  OR "wildfire*" OR "wild-fire*" OR "forest fire*" OR "forestfire*"
  OR ("sea level" NEAR/3 ("chang*" OR "rising" OR "rise$"))

Non-natural disasters and biological disasters
Disasters generally, plus environmental, chemical, biological, technological, and societal disasters. Economic is combined in phrases to prevent e.g. economic costs of disasters. Here we are considering war a disaster, it is on the list of hazards.
"disaster$" OR "catastrophe$"
OR (  ("anthropogenic"
         OR "environmental" OR "deforestation" OR "desertification" OR "degredation" OR "pollution" OR "erosion"
         OR "chemical" OR "heavy metal$" OR "pesticide$"
         OR "biological" OR "disease" OR "zoonotic"
         OR "technological" OR "radioactive" OR "nuclear" OR "cyber" OR "industrial" OR "construction" OR "transportation"
         )
         NEAR/3 ("hazard$" OR "catastrophe$" OR "disaster$")
      )
OR "outbreak$" OR "pandemic$" OR "epidemic$"
OR "war" OR "wars" OR "armed conflict$"
OR (("volatil*" OR "unstable" OR "instability" OR "unrest") NEAR/5 ("political$" OR "civil"))
OR "financial crash*" OR "financial shock$" OR "financial disaster$"
OR "economic downturn$" OR "economic shock$" OR "economic disaster$"

#UNSURE if should count:
OR (("volatil*" OR "unstable" OR "instability") NEAR/5 ("market$" OR "price$"))

Climate change (only SDG2)
 OR ("climate change" OR "climatic change$" OR "global warming" OR "changing climate")

[ ] 1.5 - CSA now updated https://github.com/SDGforskning/SDGstrings_wos/blob/main/SDG01_query_action_WoS.md#target-15
[ ] 2.4 - CSA
[ ] 11.5 - HMB/IG
[ ] 13.1 - CSA


403 error when running example

Hello.
Im trying to run the terraform on the examples folder, but Im getting the following error message: "Could not create work pool, unexpected error: status code 403 Forbidden".
My provider initialization looks like this:
provider "prefect" {
endpoint = "https://api.prefect.cloud/api"
api_key = "{{api-key}}"
account_id = "{{account-id}}"
workspace_id="{{workspace-id}}"
}
And using prefect, I'm able to create a work pool resource by sending a post request to https://api.prefect.cloud/api/accounts/{{api-key}}/workspaces/{{workspace-id}}/work_pools/ with the {{api-key}} as a bearer token, so everything seems fine on the backend...
Any thoughts on how to troubleshoot this?
Best regards,
Carlos Jourdan

Hey, thanks for the report, and for being an early adopter!
The provider is currently incomplete, and missing features that would make debugging easier (https://github.com/PrefectHQ/terraform-provider-prefect/issues/42). It's also missing automated tests (https://github.com/PrefectHQ/terraform-provider-prefect/issues/30) so it's possible that I broke this functionality without realizing it.
The only way to troubleshoot right now is to modify the source code to add logging, which is certainly not ideal. I'll look into this issue and get back to you.

Hi Johnathan, thanks for the reply. I have zero experience in Go, but still I gave it a shot and managed to hack my way through it.
What I found out is that calls like the one below in the internal\provider\resources\work_pool.go file yielded objects that had empty ApiKey strings, not "inheriting" from the api.PrefectClient object that was part of the resource object.
client, err := r.client.WorkPools(model.AccountID.ValueUUID(), model.WorkspaceID.ValueUUID())
So I patched things up by explicitly passing on the ApiKey as an aditional argument to the client factory methods, such as
client, err := r.client.WorkPools(model.AccountID.ValueUUID(), model.WorkspaceID.ValueUUID(), r.client.ApiKey())
With that out of the way, I've been working on exposing additional resources, such as deployments and flows. It's not pretty, but it works. If you're in any way interested I can share it.
Best regards
Carlos Jourdan

Thanks for the extra info @carlosjourdan 🤝
The API key is currently injected into the client here, and the logic for calculating it is here:
	// Extract the API Key from configuration or environment variable.
	var apiKey string
	if !config.APIKey.IsNull() {
		apiKey = config.APIKey.ValueString()
	} else if apiKeyEnvVar, ok := os.LookupEnv("PREFECT_API_KEY"); ok {
		apiKey = apiKeyEnvVar
	}

So if the API key isn't provided in the provider part of the Terraform config, it'll look for it from an environment variable.
That way, we don't need to inject it in the (many) client calls across the codebase.
We now have many tests running in CI, and tests we've run locally as well and they've all been working well - so I suspect whatever bug you hit in the past should be resolved by now.
I'm going to close this one for now, but if you find you're still able to replicate the error with the newest version of the code, please reach out and let us know.

With that out of the way, I've been working on exposing additional resources, such as deployments and flows. It's not pretty, but it works. If you're in any way interested I can share it.

Appreciate the offer for contribution 🤝 There are open PRs right now for Deployments and Flows, but if you have anything else we'd bee happy to take a look!


Questions

Questions, install the latest version of traccar 3.1, VPS, clean installation, before executing anything, change the lines for MySQL server as indicated by the manual, add an Android device for generating positions, but to check in the database no position stored in the "position" table, and my other question has traccar mobile version 3.1?

It looks like there is some problem with reverse geocoding. Try to disable it and see if it helps.

@Mikelord2  You can buy a good VPS server ( 1 x 2.4 Ghz CPU, 1GB Ram, 40 GB Storage, 1 Terabyte monthly Transfer) starting at EUR 1.99 by month at http://www.time4vps.eu/aff.php?aff=181 . If you buy this VPS server I can give you the Traccar server already installed on it using Ubuntu 14.04. IF you are interested please send me an e-mail.


Language: Fix small typos

This change fixes two small typos, one in http/basics.md and one in usingcurl/downloads/browsers.md.

Thanks!


DOF improvements

Possible improvements for DOF implementation here
Features:

[ ] WebGPU support. There is compilation issue with one shader currently due to glslang adding no longer supported keyword to the WGSL shader. The solution is to write a version of the shader directly in WGSL.
[ ] update CameraFrame script to expose this functionality to the Editor
[ ] physically based bloom, where instead of distance and range parameters, the bloom is controlled by camera parameters: aperture, fov)
[ ] blur red channel of CoC texture to allow near blur objects to have soft edges

Performance / quality:

[ ] make the near blur optional, for experiences where only the background needs to be blurred
[ ] when only a small amount of blur is used (less than about 3), it's more obvious the half res scene texture is used as a blur source. We could use high res at that point at a higher cost.
[ ] use compute shaders as described in links from the PR to generate tile min/max CoC textures and dispatch more appropriate (cheaper) blur shaders for individual tiles.
[ ] when TAA is used at the same time, the blurred background flickers due to TAA jitter. We could try to influence TAA's strength based on CoC texture - limit TAA in the more blurry regions. Can be slight perf win as well.
[ ] consider generation of fiew (2-3) mip levels of the scene texture (currently have half res only), and optimize the sampling algorithm to use lower mips for wider blurs, with less samples.

suggestion by @Maksims :  consider using radial distance from the camera instead of planar, to avoid DOF changing when camera rotates.
This can easily be done in RenderPassCoC, where depth buffer gets converted to near and far CoC values - we could reconstruct view position of the fragment with inverse projection matrix, get the distance if camera to view position vector and using this. We'd need to first convert the linear depth to non-linear depth, but I have that code already, used by TAA.


enhance Obscure hdfs's authentication's info for show backup's repository stmt

Proposed changes
Issue Number: close #xxx

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


[Bug] rust clients need maintenance

Before Creating the Bug Report

[X] I found a bug, not just asking a question, which should be created in GitHub Discussions.

[X] I have searched the GitHub Issues and GitHub Discussions  of this repository and believe that this is not a duplicate.

[X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Programming Language of the Client
Rust
Runtime Platform Environment
Nov 19 12:02:01.731 ERRO[/Users/never/.cargo/registry/src/mirrors.ustc.edu.cn-4affec411d11e50f/rocketmq-5.0.0/src/client.rs:182:33] send heartbeat failed: server return error: Server error at client.heartbeat, context: { code: UNRECOGNIZED_CLIENT_TYPE, message: cannot find client settings for this client } => server return an error, component: client
Nov 19 12:02:31.607 ERRO[/Users/never/.cargo/registry/src/mirrors.ustc.edu.cn-4affec411d11e50f/rocketmq-5.0.0/src/client.rs:182:33] send heartbeat failed: server return error: Server error at client.heartbeat, context: { code: UNRECOGNIZED_CLIENT_TYPE, message: cannot find client settings for this client } => server return an error, component: client
RocketMQ Version of the Client/Server
5.3.1
Run or Compiler Version
No response
Describe the Bug
rustc -V
rustc 1.82.0 (f6e511eec 2024-10-15)
Steps to Reproduce
just make connect with default rocketmq settings
What Did You Expect to See?
no error
What Did You See Instead?
Nov 19 12:02:01.731 ERRO[/Users/never/.cargo/registry/src/mirrors.ustc.edu.cn-4affec411d11e50f/rocketmq-5.0.0/src/client.rs:182:33] send heartbeat failed: server return error: Server error at client.heartbeat, context: { code: UNRECOGNIZED_CLIENT_TYPE, message: cannot find client settings for this client } => server return an error, component: client
Nov 19 12:02:31.607 ERRO[/Users/never/.cargo/registry/src/mirrors.ustc.edu.cn-4affec411d11e50f/rocketmq-5.0.0/src/client.rs:182:33] send heartbeat failed: server return error: Server error at client.heartbeat, context: { code: UNRECOGNIZED_CLIENT_TYPE, message: cannot find client settings for this client } => server return an error, component: client
Additional Context
No response

would anyone perform a publish on rust

would help publish a update of rust client @lizhanhui


Fix529 2

This pull request fixes the second issue found on #529
Bug:

A wrong foreign key has been set on the table columns. It creates a constraint between the column name and the datasource_name in the datasources table.

Fix:

Create a migration to change the foreign key to datasource_name in columns -> datasource_names in datasources.

Hi,
I noticed that the migrations fails on sqlite. The problem is linked to the fact that SQL Lite does not support alter tables and I have to use a batch alter instead:
with op.batch_alter_table('columns') as batch_op:
batch_op.drop_constraint('columns_ibfk_1', type_="foreignkey")
batch_op.create_foreign_key('columns_ibfk_1', 'datasources', ['datasource_name'], ['datasource_name'])
The problem with this approach is that the sqlite schema doesn't have a name on the foreign key so there's no way I could drop it.

@LAlbertalli since sqlite is the default db please add the batch context manager to keep caravel working out of the box.

@xrmx Please, read my full comment. This kind of migration is not supported in sqlite because the constraint as no name. Otherwise, I would have submitted it immediately. That's why I'm asking for the best approach.
There's a point to be made, though. Foreign keys are not on by default on sqlite, that's probably why none noticed the bug before. Could we modify the init migrations to have the correct foreign key and we conditionally skip the migration for sqlite? I don't like the idea because it will introduce an unpredictable behavior. On the other side, it is the only upgrade path I could foresee that doesn't require an overly complex setup.
I'm open to suggestion.

@LAlbertalli does this help? http://alembic.readthedocs.io/en/latest/batch.html#dropping-unnamed-or-named-foreign-key-constraints

@xrmx Yes, that was the same issue I found trying with the suggestion in the doc you linked.
Another bigger problem is that I'm naming directly the constraint, but that name seems to be autogenerated by MySQL. But I'm not sure the constraint name will be the same on PG that is the third supported database.
I need to do further research, this is why I was asking further suggestion from people more experienced than me in using SQLAlchemy/Alembic.

@xrmx Seems like it only works when you have created the foreign keys with naming_convention specified. But it's too late now, for those who has been using mysql, the foreign keys have been named according to the default name convention of MySQL. The only solution I have figured out so far is to try on every kind of databases and try to drop the key by trying through each of the default foreign key names.

@xrmx @x4base I see two options moving forward. Modifying the init migration to fix the error. I'm not happy with that but it should solve the issue for new install. People who are already using it, or they don't check foreign keys, or they have already fixed it.
The second option, that I actually like more, is to surround the migration with an exception handling code to skip sqlite and find the correct name for PGSQL.
To be honest, I will go for both actions (change init and use error handling) to cover all the possible issues.
Let me know what do you prefer. It will take me probably few days to provide the patch.
Bye
L.

I agree with droping the key by the pgsql. But i am concerned about whether we should cover more Sql dialects (e.g. mssql) that sqlalchemy supports or should we just assume that no one is using other dialects?

@x4base I was thinking of sqlite, MySQL, and pg because they are the databases listed in https://github.com/airbnb/caravel/blob/master/caravel/config.py#L35 as an example. But, yes, nothing forbid to use MS SQL or Oracle. If someone has ideas...

The last commit should work for every supported DB.
I've tested it against sqlite and partially tested against MySQL and it worked both upgrade and downgrade.
The "magic" is done by a function that uses the sqlalchemy reflection capability to detect the correct constraint name.

Coverage remained the same at 82.108% when pulling 7308cf6cb095dec000ced915e49afdd2976908ed on LAlbertalli:fix529-2 into 087c47a37e45bb9c2608bbb2279188b59547e449 on airbnb:master.

Coverage remained the same at 82.108% when pulling 7308cf6cb095dec000ced915e49afdd2976908ed on LAlbertalli:fix529-2 into 087c47a37e45bb9c2608bbb2279188b59547e449 on airbnb:master.

👍


Refactor CMakeList to work for all build types

This setup is based on: How_to_Build_your_own_MLIR_Dialect.pdf
# There are 3 build modes, one will be set to ON
#  - Standalone: Build MLIR as a part of StableHLO
#  - External: StableHLO built as an external LLVM project (XLA/MHLO uses this)
#  - Embedded: StableHLO built as a part of another MLIR project (torch-mlir uses this)
#
# If building as part of another project, let it handle the MLIR dependency.
# The dependent project might use a bundled version of MLIR instead of installing.

Tested using mlir-hlo repo. No changes to the EMBEDDED build so should not impact torch-mlir.

cc @qingyunqu -- I don't think this should change the torch-mlir STABLEHLO_BUILD_EMBEDDED workflow, but would be good to confirm if you have a moment to patch this in

cc @qingyunqu -- I don't think this should change the torch-mlir STABLEHLO_BUILD_EMBEDDED workflow, but would be good to confirm if you have a moment to patch this in

Ok, I will confirm this when update stablehlo in torch-mlir.


feat(polling): add ability to set a timeout for polling

closes #35

:tada: This PR is included in version 4.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Start-up Idea

I would like to add a startup idea

@Wangata Ya you can add this idea to the StartupIdeas/Idea.js file thanks.

Kindly assign me the issue


CMAQ will not work on macOS

Description
The existence of the following files permits building or even doing any git work on macOS:
UTIL/create_ebi/src_RXNSU/junit.f
UTIL/create_ebi/src_RXNSU/junit.F
UTIL/inline_phot_preproc/src/CSQY_DATA.f
UTIL/inline_phot_preproc/src/CSQY_DATA.F

It also breaks any build system that attempts to automatically update branches from the authoritative repositories, because there are always changes to these files that result in unresolvable conflicts. This is because macOS uses a pseudo case-sensitive filesystem and doesn't recognize that UTIL/create_ebi/src_RXNSU/junit.f and UTIL/create_ebi/src_RXNSU/junit.F are different files.
If the .f versions of the two files above are preprocessed from the .F files and were mistakenly added to the repository, then these should be removed.
Scope and Impact
See above
Solution
Remove the two .f files and do preprocessing on the fly (if a two-step approach = preprocessing+compiling is preferred, then the preprocessor must write to .tmp.f instead of .f, or another problem will be created).

@junwang-noaa @dusanjovic-noaa @briancurtis-noaa This will cause problems with the ufs-weather-model (it actually causes problems already if the ufs-weather-model is included in a bigger build system, for example as external package).

Please try the below two solutions.
For UTIL/create_ebi, I agree:

Removing the UTIL/create_ebi/src/junit.f is fine and preferable because the Makefile does not require changes.
Note that creating junit.o does not require FORTRAN preprocessing.

For UTIL/ inline_phot_preproc, try

Deleting UTIL/inline_phot_preproc/src/CSQY_DATA.F, UTIL/inline_phot_preproc/src/CSQY_DATA.f, UTIL/inline_phot_preproc/src/CSQY_DATA_gen.f and  UTIL/inline_phot_preproc/src/CSQY_DATA_old.f
Why? Building this utility does not use the source code files.

Please try the below two solutions.
For UTIL/create_ebi, I agree:

Removing the UTIL/create_ebi/src/junit.f is fine and preferable because the Makefile does not require changes.
Note that creating junit.o does not require FORTRAN preprocessing.

For UTIL/ inline_phot_preproc, try

Deleting UTIL/inline_phot_preproc/src/CSQY_DATA.F, UTIL/inline_phot_preproc/src/CSQY_DATA.f, UTIL/inline_phot_preproc/src/CSQY_DATA_gen.f and  UTIL/inline_phot_preproc/src/CSQY_DATA_old.f
Why? Building this utility does not use the source code files.

@bhutzell Thanks for the pointers, is this mean to be a solution that can be merged back into the repository?
I can always work around on my local machine, but the system has to work out of the box. For instance, after a recursive clone of the ufs-weather-model (where CMAQ is a nested submodule of), the user has to be able to compile the code without any manual intervention.

@climbfuji We are working to get this update merged into our v5.3.3+ branch.  I will let you know when it is merged and ready to be used.  The update will also be included in our next release, v5.4, this fall.

That sounds great, thanks a lot for doing this!

On Apr 20, 2022, at 8:13 AM, Kristen Foley @.***> wrote:
@climbfuji https://github.com/climbfuji We are working to get this update merged into our v5.3.3+ branch https://github.com/USEPA/CMAQ/tree/5.3.3+. I will let you know when it is merged and ready to be used. The update will also be included in our next release, v5.4, this fall.
—
Reply to this email directly, view it on GitHub https://github.com/USEPA/CMAQ/issues/169#issuecomment-1103983962, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB5C2RJTBQOBJ3ZF37LWARDVGAGKBANCNFSM5TFCOHYQ.
You are receiving this because you were mentioned.

This issue is now resolved in the code on the v5.3.3+ branch.  Tag: CMAQv<IP_ADDRESS>_7May2022

Thanks very much, @kmfoley !


php 8 support

Hi!
You have built a great package!
Could you add support for php 8?
Just updated laravel 8 app to php 8 but get this dependencies issues from composer
Problem 1
- shomisha/unusual-relationships 1.0.0 requires laravel/framework ~5.6 -> found laravel/framework[v5.6.0, ..., 5.8.x-dev] but it conflicts with your root composer.json require (^8.0).
- shomisha/unusual-relationships 1.0.1 requires php ~7.0 -> your php version (8.0.3) does not satisfy that requirement.
- Root composer.json requires shomisha/unusual-relationships ^1.0 -> satisfiable by shomisha/unusual-relationships[1.0.0, 1.0.1].

@svenssontobias Hi. Sorry for replying this late, for some reason I completely missed this issue.
Sure I can, I'll add it by the end of the week

@shomisha Would be super if you got time to add php 8 support.
Thx in advance!

Any update on PHP 8 support?


getSearchParams is not parsing correctly when using Vite

Hi,
When using Remix 2.2.0 using Vite, it seems that getSearchParams stopped parsing correctly the query params without throwing any errors.
It could be related to Request polyfill in vite adapater as mentionned here : https://github.com/remix-run/remix/issues/7819

Thanks for the report. I'll take a look.

This is weird. When I used the following code with the remix-params-helper, it returned an error. But when I copied the helper code directly into my project, it worked correctly.
// routes/test.$id.tsx
export async function loader({ request, params }: DataFunctionArgs) {
  const resultParams = getParams(params, z.object({ id: z.string() }))
  const resultSearchParams = getSearchParams(
    request,
    z.object({ q: z.string(), page: z.number().default(1) }),
  )
  return json({ resultParams, resultSearchParams })
}

export default function Component() {
  const loaderData = useLoaderData<typeof loader>()

  return (

      <Form>
        <input name="q" className="border" />
      </Form>

{JSON.stringify(loaderData, null, 2)}

  )
}

remix-params-helper package

inline

Thanks @kiliman for your quick answer. As you mentioned, I tried copying the helper directly in my codebase and everything work as expected. This is indeed pretty weird, I'll continue investigating and update here if I find something

I did some more investigation. It looks like I need to make a pure ESM package. By default it was loading the CJS version, and for some reason, this code was always returning false, so it wasn't parsing properly and always failing.
function parseParams(o, schema, key, value) {
    var _a;
    // find actual shape definition for this key
    let shape = schema;
    console.log('parseParams', shape instanceof zod_1.ZodObject)
    while (shape instanceof zod_1.ZodObject || shape instanceof zod_1.ZodEffects) {
        shape =
            shape instanceof zod_1.ZodObject
                ? shape.shape
                : shape instanceof zod_1.ZodEffects
                    ? shape._def.schema
                    : null;
        if (shape === null) {
            throw new Error(`Could not find shape for key ${key}`);
        }
    }
    // ...
}

I was about to send the same finding after debugging in node_modules, const def = shape[key]; is undefined and not processed. I'll use a local version in the meantime, thanks for taking the time @kiliman !

Sorry for recommending something different here. I needed a quick fix and started using Zodix.
The API is the same so it was an easy migration.

@mauscoelho I'm glad you found something that works for you.

It looks like I need to make a pure ESM package. By default it was loading the CJS version, and for some reason, this code was always returning false, so it wasn't parsing properly and always failing.

I think the issue is a dual package hazard (see https://nodejs.org/api/packages.html#dual-package-hazard) of zod dependency where user code loads esm version of zod (via import) but remix-params-helper loads cjs version (via require).
I was interested in this issue since this might be a general problem which others libraries might face.
For the specific case of remix-params-helper, it already includes esm version in the package, so enforcing vite to resolve esm version can be a quick workaround available on user side.
This can be achieved by the combination of ssr.noExternal and resolve.alias like this:
https://stackblitz.com/edit/remix-run-remix-cktyfl?file=vite.config.ts
export default defineConfig({
  plugins: [remix(), tsconfigPaths()],
  ssr: {
    noExternal: ['remix-params-helper'],
  },
  resolve: {
    alias: {
      'remix-params-helper': 'node_modules/remix-params-helper/dist/helper.js',
    },
  },
});

reveal screenshot

I'm not familiar with remix-params-helper myself so I might missing some scenarios not covered by this workaround, but I hope this still gives some ideas of the underlying issue!

+1 to this. an error is always returned. I'm trying to use this in my loader to parse queryParams for my API but just throws an error everytime.

I'll be publishing an updated package that works properly for both CJS and ESM imports.

Fixed in v0.5.0


Update allowedPackageJsonDependencies.txt

add @react-navigation/native @react-navigation/stack react-native-gesture-handler react-native-safe-area-context react-native-svg

Can you link the DefinitelyTyped PR(s) that require these?

@andrewbranch here is https://github.com/DefinitelyTyped/DefinitelyTyped/pull/49429

@andrewbranch hello bro. any problems?


Feature: sign the macOS binaries

Feature description
Ali created an Apple Developer account for us.
Whoever takes on this task, will need to get access to the account from him.

Related tool: https://github.com/anchore/quill


Store queries which select subset of attributes does not work in a HA deplyment

Description:
$Subject. This is happening because we are using deprecated construct when querying HARecordTableHandler
Affected Siddhi Version:
4.x.x
Steps to reproduce:
Run a store query on a table which selects only a partial set of attributes

Fixed in https://github.com/siddhi-io/siddhi/pull/1284 .