[Bug]: Opensearch 1.2.0 Docker images do not trust Sectigo TLS certificates

Describe the bug
Using the Opensearch 1.2.0 docker images and adding a snapshot s3 repo that uses Sectigo TLS certificates gives an error:
sdk_client_exception: Unable to execute HTTP request: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
The CA-certs need to be updated I guess, common problem with these certificates that broke half the internet last year. In the meantime, can I do this myself? I'm unclear which keystore I should add the certificate to (or disable TLS validation?).
To reproduce
Connect to snapshot repo with Sectigo certs
Expected behavior
No error
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
K8S using 1.2.0 image
Additional context
No response
Relevant log output
{
  "error" : {
    "root_cause" : [
      {
        "type" : "repository_verification_exception",
        "reason" : "[CPS_POC_Elasticsearch] path  is not accessible on master node"
      }
    ],
    "type" : "repository_verification_exception",
    "reason" : "[CPS_POC_Elasticsearch] path  is not accessible on master node",
    "caused_by" : {
      "type" : "i_o_exception",
      "reason" : "Unable to upload object [tests-FhwupdrGSgmP0rQ2v3mfWA/master.dat] using a single upload",
      "caused_by" : {
        "type" : "sdk_client_exception",
        "reason" : "sdk_client_exception: Unable to execute HTTP request: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target",
        "caused_by" : {
          "type" : "i_o_exception",
          "reason" : "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target",
          "caused_by" : {
            "type" : "validator_exception",
            "reason" : "validator_exception: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target",
            "caused_by" : {
              "type" : "sun_cert_path_builder_exception",
              "reason" : "sun_cert_path_builder_exception: unable to find valid certification path to requested target"
            }
          }
        }
      }
    }
  },
  "status" : 500
}

@ict-one-nl  This issue doesn't look like a bug. The OpenSearch docker image is only missing specific trusted RootCA in /usr/share/opensearch/jdk/lib/security/cacerts keystore.
Your fix is valid.

This is a very common CA nowadays, major OS'es have updated their trusted CA's accordingly. Java apps are lagging behind, it would be nice to add this to the default docker image. Another option is to document this (also for less used CA's), but fixing it permanently in the image would be nicer

@ict-one-nl following up on this as this is an older one (sorry!): is this still an issue we should look into?

No problem! Ehmm.... We solved it buy adding it to the container ourselfs. Not ideal but it works.
Don't know if the intermediate certificate is embedded by default by now but otherwise it can be annoying: sectigo is a large ca


1.25.0 Candidate

Candidate changes for v1.25.0.

NOTE: As part of the changes in this PR which has been merged into this branch, we will need to run an accompanying script post-release to update existing user filters on prod. This script will be handled internally.


Feat:Creating error route and 404 error not found page

Describe the feature
Creating error route and 404 error not found page
Add ScreenShots
.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@mdazfar2 i want to work upon it


Addition of badge in Readme

I want to contribute to devFind by adding Github badge of star, fork, pull request , issues, etc in readme of the repository.

@SusheelThapa Assigned


Release rancher-turtles 0.5.0

This aligns with the 0.14.1 upstream turtles release - it also switches to the rancher registry CAPM3 images.  Images are updated to:
          image: registry.suse.com/rancher/cluster-api-provider-rke2-bootstrap:v0.9.0
          image: registry.suse.com/rancher/cluster-api-provider-rke2-controlplane:v0.9.0
          image: registry.suse.com/rancher/cluster-api-controller:v1.8.4
          image: registry.rancher.com/rancher/cluster-api-metal3-controller:v1.8.2
          image: registry.rancher.com/rancher/cluster-api-metal3-ipam-controller:v1.8.1
          image: registry.rancher.com/rancher/cluster-api-operator:v0.14.0
          image: registry.rancher.com/rancher/rancher/turtles:v0.14.1

Preview available for testing at https://hardys.github.io/charts/


bash_completion does not install

Install using
curl -sL https://download.getcarina.com/dvm/latest/install.sh | sh

You end up with this in .dvm/bash_completion

Not Found

The resource could not be found.

The latest tag does not include bash_completion?

Confirmed that. I'll get it fixed.

Whoops, meant to post after I fixed this. I've put the bash completion up manually and fixed our automation in #74.


feat(server): support upgrading to other protocols

The Http type learns a new method, bind_upgradable_connection, which returns a Future. This method behaves like bind_connection, except the Service supplied must return an UpgradableResponse containing either an HTTP Response or some information describing a protocol switch. If an Upgrade response is returned, the server task is shut down (without closing the underlying io) and this information is forwarded to the Future, along with the underlying io and any remaining buffered data that has already been read from it.
If the server task shuts down normally, the Future completes with a None output value. In the case of an error handling the connection, the error is also forwarded to the Future.
This allows for implementing servers with hyper that can upgrade their connections to different protocols, such as WebSockets, in response to client requests. Such protocols can be implemented outside of hyper itself. The API is designed to allow for potentially multiple upgrade paths out of an HTTP exchange, with the upgrade information attached to the UpgradableResponse::Upgrade signal determining which is used.
A companion crate implementing WebSocket upgrades can be found here, with sample code here.
Importantly, the code path for normal, non-upgradable connections is entirely untouched by this addition.

[x] The commit messages match the guidelines in https://github.com/hyperium/hyper/blob/master/CONTRIBUTING.md#git-commit-guidelines

This looks really impressive! I apologize I haven't had time to review it, I've been trying to wrap up changes to the http crate before RustConf. I'll take a look soon, I promise!

No problem, and thanks!

Hi again, have you had a chance to look at this since RustConf?

@spinda I'm so sorry, I don't have particularly good reasons other than forgetting. I'd like to look at this this week. I think upgrading protocols is necessary, and so hyper should definitely support it.
cc @carllerche

Thanks for taking a look! Not sure how much time I'm going to have over the next few days (ending an internship and moving back home). I'll address these comments as soon as I can.

I'd be especially interested in discussing the design before spending time writing code :D

I put more details of the proposal I suggested in #1323.

How's progress on this? Can I help?

is this now blocked on moving from tokio-proto?

The internal change to not use tokio-proto is already merged, just not on by default while bugs are still found. It should probably be easier to make upgrades work, however, because of this work.
I'd say the blocker for this feature is settling on an API to expose to a user.

I'm closing this due to inactivity. I recommend discussing the feature more in #1323.


Get-DbaRegServerGroup does not parse a group path

Verified issue does not already exist?
Yes
What error did you receive?
There are no errors returned, but nothing is returned when a group path uses a single backslash to separate the group names.
The desired group is returned when a group path uses a double backslash to separate group names.  I don't think this is expected.
Steps to Reproduce
# provide your command(s) executed pertaining to dbatools
# please include variable values (redacted or fake if needed) for reference

#Requires -Version '7.0'
#Requires -Module @{ ModuleName = 'DbaTools'; ModuleVersion = '1.1.9' } # Install-Module -Name dbatools
Add a "Test" group to CMS.  Add SubTest1 and SubTest2 groups to the Test group.
Get-DbaRegServerGroup SQLDBAPROD -Group 'Test' |
%{write-debug ("1. Test: Name = {0}" -f $.name) -debug}
Get-DbaRegServerGroup SQLDBAPROD -Group 'Test' |
Select-DbaObject -ExpandProperty ServerGroups |
%{write-debug ("2. Test|ServerGroups: Name = {0}" -f $.name) -debug}
Get-DbaRegServerGroup SQLDBAPROD -Group 'Test\SubTest1' |
%{write-debug ("3. Test\SubTest1: Name = {0}" -f $.name) -debug}
Get-DbaRegServerGroup SQLDBAPROD -Group 'Test\SubTest2' |
%{write-debug ("4. Test\SubTest2: Name = {0}" -f $.name) -debug}
Get-DbaRegServerGroup SQLDBAPROD -Group 'Test\SubTest1' |
%{write-debug ("5. Test\SubTest1: Name = {0}" -f $.name) -debug}
Get-DbaRegServerGroup SQLDBAPROD -Group 'Test\SubTest2' |
%{write-debug ("6. Test\SubTest2: Name = {0}" -f $.name) -debug}
Results:
DEBUG: 1. Test: Name = Test
DEBUG: 2. Test|ServerGroups: Name = SubTest1
DEBUG: 2. Test|ServerGroups: Name = SubTest2
DEBUG: 5. Test\SubTest1: Name = SubTest1
DEBUG: 6. Test\SubTest2: Name = SubTest2
Are you running the latest release?
Yes
Other details or mentions
I see regex \ escapes in the code which are required.  Then there's $split = $currentgroup.Split('\') that's not regex.  Just one little character....
What PowerShell host was used when producing this error
VS Code (integrated terminal)
PowerShell Host Version
Name                           Value

PSVersion                      7.1.3
PSEdition                      Core
GitCommitId                    7.1.3
OS                             Microsoft Windows 10.0.19041
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0
SQL Server Edition and Build number
Microsoft SQL Server 2019 (RTM-GDR) (KB4517790) - 15.0.2070.41 (X64)   Oct 28 2019 19:56:59   Copyright (C) 2019 Microsoft Corporation  Standard Edition (64-bit) on Windows Server 2019 Standard 10.0  (Build 17763: ) (Hypervisor)

Hi.  My double \ got escaped in the above.  I'll try escaping them.
Get-DbaRegServerGroup SQLDBAPROD -Group 'Test\\SubTest1' |
%{write-debug ("5. Test\\SubTest1: Name = {0}" -f $.name) -debug}
Get-DbaRegServerGroup SQLDBAPROD -Group 'Test\\SubTest2' |
%{write-debug ("6. Test\\SubTest2: Name = {0}" -f $.name) -debug}
I see regex \\ escapes in the code which are required. Then there's $split = $currentgroup.Split('\\') that's not regex. Just one little character....

That worked.  Sorry for the noise.  I'll try to edit the original test.

Thank you for the report! Sure enough, the original method works in Windows PS but not PS Core. I've submitted a fix 👍🏼


Alienfan-gui stops controlling CPU fan after computer sleeps or is plugged in

Been using this program for a few months now, I feel like this has been an issue for a while now. It's annoyed me to the point of posting it here as a bug, perhaps it is just user error but I doubt it as I've since reformatted the computer, updated the BIOS once again etc and redownloaded the program and the problem persists.
It seems like after a certain amount of time using the computer, or if I leave it to idle so it sleeps and then start using it again, or if I plug the computer in after using it on battery, the CPU fan just doesn't turn on anymore. I haven't been using anything GPU intensive so I do not have any results regarding the GPU fan, this is all in regards to the CPU fan. I have the fan curve set as a straight line (40 degree = 0% fan, 71 degrees = 100% fan), about as simple as it gets. The program will work after freshly starting the computer up, it will work if I close the program and reopen it, but after an indeterminant amount of time of the program being open (seems to be about a couple hours), or if the computer sleeps and then is awoken, or if the computer is plugged in from battery, it will still read the correct temperature from the sensors, but the fans will not turn on. Sometimes it will say that the fans are at some RPM (currently it says the CPU fan is at 3000 RPM), but the fans are not spinning whatsoever. Most times it just says the fans are at 0, which I suppose is accurate as they aren't spinning, but they SHOULD be in regards to the fan curve and the temperature of the CPU.
The simple fix is to just close and reopen the program or to restart the computer but one can probably understand how annoying that is to do every couple of hours, especially if you're in the middle of something.
I am using version <IP_ADDRESS>
The computer is a G15 5515, AMD Ryzen 7 5800H, 16 GB RAM, Nvidia 3060, Windows 11

Hmm... Interesting. In case temperatures updated, my procedure working correctly.
Where is red dot at fan curve window?
But seems like something wrong with BIOS - fan control is indirect, all m app doing is just a BIOS hint, not control fans directly. As well as RPM - i just read it from BIOS, so in case it reports 3000 i have no way to check it's true or not.
You can also have an issue with the fan in itself, it can be dusty and can't spin correctly at low speeds.
Try to set lower boost between 35 and 50 (5-10), this can prevent fan from stop by BIOS.

The red dot seems to be accurate, I have been checking with HWMonitor. It seems like everything about the program is working as you intended. I wasn't intending to insinuate that it was your program that was the problem, it seems like these laptop's BIOS are an issue for a lot of people looking through other complaints. It's just frustrating I suppose, and I understand it's not really something you can control or do anything about.
I appreciate you making this program nonetheless, it is certainly better than AWCC not starting the fans at all until ~80 degrees lol. I don't believe it's dust or anything physical as this laptop is rather new and I don't use it very often as is (partially because of these problems).
I have adjusted the fan curve as per your suggestion; hopefully that will rectify the problem, perhaps it is something as simple as the fans not being restarted by the BIOS and not letting them stop would indeed fix that.
Thank you for your reply, and for the program!

Ok.
Please open Administrator CMD, run alienfan-cli rpm and share me output (i'm interested in your systemID). I'll try to make override of this bug (it happened at some other systems as well, so we know how to do).
Also, as a small fix, try to use Alt+Ctrl+1 then Alt+Ctrl+0 then it happened (this change power modes). Did it help?


Animated tiles

Hi, is it possible to add animated tiles? I have multiple object types in my game with animations (flame, doors, and teleports). I wonder if it is possible or not. Thanks for the answer.

Hey, it should be no problem. It depends a bit on how you implement them because to my knowledge there is no out-of-the-box support in phaser tilemaps for that.
If you simply change the tile of the tilemap in regular intervals that should not be a problem.
You could also add animated sprites. Just be careful then with the z-index.

Hey, it should be no problem. It depends a bit on how you implement them because to my knowledge there is no out-of-the-box support in phaser tilemaps for that.
If you simply change the tile of the tilemap in regular intervals that should not be a problem.
You could also add animated sprites. Just be careful then with the z-index.

I implemented it using this approach https://medium.com/@junhongwang/tiled-generated-map-with-phaser-3-d2c16ffe75b6
Thanks for your awesome Grid engine, it is really a piece of diamond :)

Glad to hear it worked and that you like GridEngine! 👍


Automatically send batch request

Hi, first of all thank you @alberto-bottarini for creating the batch functionality.
In the discussion of #83 @jorgeborges said he would prefer the batch to be sent automatically after the 20 enqueued url's have been reached. Personally I like this approach so this is why i'm creating this pull request.
I've also added a hasEnqueuedUrls method. This method allows us to determine if any enqueued url's are still available before sending the response back to the client. If any are available then send the enqueued hits. We're using Laravel so I created a middleware to do exactly that for each response.
This way we don't have to worry about the limit.
It would be nice to have at least the hasEnqueuedUrls method added. I understand the philosophy behind the exception approach as well, if you decide to keep it that way than i will create something myself.
I coudn't get phpunit to work, i got the following error:

I'll check them again if they do not pass.

Coverage remained the same at 100.0% when pulling 58147737e6349436eb6d742684ae6d0f2de2333e on bsbip:automatic-queue into 6136c2f2ef159045402ef985843db0ad0f136125 on theiconic:master.

Thanks!
As I already said, I don't like this "magic" implementation.
I understand your needs but I would prefer control over automation.
We don't know any users needs. Maybe this automation could create some unwanted situation.

Thanks for the PR @RFreij.
To be honest, I don't have hard feelings on either approach. I would prefer the auto event flush just because that seems to make the library easier to use, but on the other hand, @alberto-bottarini did point out the rest of the library throws exceptions when it's used wrong (such as when not all required data for a hit is included in the Analytics object), so having it throw the Exception makes thing consistent.
Another approach would be to make this configurable, by default it doesn't auto send the batch, but if you call a method called enableAutoBatchHitSend or the like, then that activates the auto flush.
I think we can leave this one up to the community to decide, I'll create an issue, @ all the people who has contributed to the library, and depending on the number of votes using 👍 or 👎  we'll decide.

... or add a wrapper method called enqueOrSend<hit-type>() which also gets rid of any "magic".
PS: I want the hasEnqueuedUrls() method in this PR :)
PPS: last but not least, if this PR gets rejected there is still the possibility of extending the Analytics class:
<?php

use TheIconic\Tracking\GoogleAnalytics\Analytics;

class AnalyticsDriver extends Analytics
{
    protected $autoFlushEnabled = false;

    public function enableAutoFlush()
    {
        $this->autoFlushEnabled = true;

        return $this;
    }

    public function disableAutoFlush()
    {
        $this->autoFlushEnabled = false;

        return $this;
    }

    protected function enqueueHit($methodName)
    {
        if (count($this->enqueuedUrls) == 20 && $this->autoFlushEnabled) {
            $this->sendEnqueuedHits();
        }

        return parent::enqueueHit($methodName);
    }
}

... or add a wrapper method called enqueOrSend<hit-type>() which also gets rid of any "magic".
PS: I want the hasEnqueuedUrls() method in this PR :)
PPS: last but not least, if this PR gets rejected there is still the possibility of extending the Analytics class:
<?php

use TheIconic\Tracking\GoogleAnalytics\Analytics;

class AnalyticsDriver extends Analytics
{
    protected $autoFlushEnabled = false;

    public function enableAutoFlush()
    {
        $this->autoFlushEnabled = true;

        return $this;
    }

    public function disableAutoFlush()
    {
        $this->autoFlushEnabled = false;

        return $this;
    }

    protected function enqueueHit($methodName)
    {
        if (count($this->enqueuedUrls) == 20 && $this->autoFlushEnabled) {
            $this->sendEnqueuedHits();
        }

        return parent::enqueueHit($methodName);
    }
}


Misconceptions about the JavaScript Engine Switcher version 2.X

This is not an error, but an open appeal to React.NET's users.
Misconceptions about the JavaScript Engine Switcher version 2.X
Over the past six months, I often had to communicate with React.NET's users about errors, that occur due the JavaScript Engine Switcher. In 80 percent of cases, these were not errors, but just wrong usage of the library, which caused by misconceptions about how it works. In this post I will consider most part of these misconceptions.
MSIE
For correct working of the JavaScriptEngineSwitcher.Msie is enough, that the Internet Explorer is installed on a computer.
At the moment, most of the JS libraries are written in ECMAScript 5 (React is also one of them). Full support of the ECMAScript 5 standard are appeared only in the Internet Explorer 9, when was released a new JavaScript engine - Chakra.
If you run the React.NET with the JavaScriptEngineSwitcher.Msie on a computer on which installed the Internet Explorer 8 or below, then you will get an error like this:
Object doesn't support this property or method

Therefore, you should always use the JavaScriptEngineSwitcher.Msie only on computers on which installed the Internet Explorer 9+ or Microsoft Edge. Ideally, same version of browser should be installed on the development computer and production server.
If you do not have the opportunity to install a modern version of browser on the server, then start using the JavaScriptEngineSwitcher.ChakraCore.
V8

JavaScriptEngineSwitcher.V8 require msvcp120.dll and msvcr120.dll assemblies from the Visual C++ Redistributable Packages for Visual Studio 2013.
Since version 2.2.0 the  JavaScriptEngineSwitcher.V8's native assemblies require msvcp140.dll assembly from the Visual C++ Redistributable for Visual Studio 2015.

JavaScriptEngineSwitcher.V8 package no longer contains native assemblies, so in addition to it, you need to install the ClearScript.V8 package.
Indeed, since version 2.1.0, JavaScriptEngineSwitcher.V8 package does not contain native assemblies for Windows, but these assemblies have not gone anywhere, and were moved to separate packages: JavaScriptEngineSwitcher.V8.Native.win-x86 and JavaScriptEngineSwitcher.V8.Native.win-x64. Therefore, you do not need to install the ClearScript.V8 package, which has no relation to the JavaScript Engine Switcher. In general, usage of the ClearScript.V8 package together with the JavaScriptEngineSwitcher.V8 is causing errors.

After installation of the JavaScriptEngineSwitcher.V8.Native packages, native assemblies need to be manually copied to the application directory, because this is recommended by the authors of the ClearScript.
After installation of the packages don't need to do any additional actions, this is the main advantage of the JavaScriptEngineSwitcher.V8. Installation of native assemblies is performed by using the following tools:

For .NET 4.X applications and ASP.NET 4.X web applications are used a MSBuild scripts (for example, JavaScriptEngineSwitcher.V8.Native.win-x64.props).
For ASP.NET 4.X web sites are used a PowerShell scripts (for example, Install.ps1 and Uninstall.ps1).
For .NET Core applications and ASP.NET Core web applications are used a mechanism based on the runtimes directories and RIDs.

In .NET 4.X versions of the JavaScriptEngineSwitcher.V8 a native assemblies are loaded from non-standard directories. In this case, native assemblies are located in the x86 and x64 subdirectories of bin\[Debug|Release] directory (for web applications and sites just the bin directory).

For 64-bit Windows is enough to install only the JavaScriptEngineSwitcher.V8.Native.win-x64 package.
.NET applications, ASP.NET web applications and sites in 64-bit Windows  can run not only 64-bit processes, but also in 32-bit processes. For correct working of the JavaScriptEngineSwitcher.V8 in 32-bit process need to install the JavaScriptEngineSwitcher.V8.Native.win-x86 package. If you do not know in which process will run your application or web site, then install both packages.

ChakraCore

JavaScriptEngineSwitcher.ChakraCore for Windows require assemblies msvcp120.dll and msvcr120.dll from the Visual C++ Redistributable Packages for Visual Studio 2013.
Since version 2.1.0 the JavaScriptEngineSwitcher.ChakraCore's native assemblies require msvcp140.dll assembly from the Visual C++ Redistributable for Visual Studio 2015.

JavaScriptEngineSwitcher.ChakraCore package no longer contains native assemblies, so in addition to it, you need to install the Microsoft.ChakraCore package.
Indeed, since version 2.1.0,  JavaScriptEngineSwitcher.ChakraCore package does not contain native assemblies for Windows, but these assemblies have not gone anywhere, and were moved to separate packages: JavaScriptEngineSwitcher.ChakraCore.Native.win-x86 and JavaScriptEngineSwitcher.ChakraCore.Native.win-x64. Therefore, you do not need to install the Microsoft.ChakraCore package, which has no relation to the JavaScript Engine Switcher.
In addition to these two packages are also available three packages:

JavaScriptEngineSwitcher.ChakraCore.Native.win8-arm contains the native assemblies for Windows (ARM). Only compatible with .NET Core and .NET Framework 4.5.
JavaScriptEngineSwitcher.ChakraCore.Native.debian-x64 contains the native assemblies for Debian-based Linux (x64) (Debian, Ubuntu and Linux Mint). Only compatible with .NET Core.
JavaScriptEngineSwitcher.ChakraCore.Native.osx-x64 contains the native assemblies for OS X (x64). Only compatible with .NET Core.

If you use some other Linux distro, then you can build the ChakraCore assembly by using following instructions from official repository. Only instead of the latest version of ChakraCore's source code, you need to use a version, that is supported by the JavaScriptEngineSwitcher.ChakraCore.

After installation of the JavaScriptEngineSwitcher.ChakraCore.Native packages, native assemblies need to be manually copied to the bin directory.
After installation of the packages don't need to do any additional actions, this is the main advantage of the JavaScriptEngineSwitcher.Core. Installation of native assemblies is performed by using the following tools:

For .NET 4.X applications and ASP.NET 4.X web applications are used a MSBuild scripts (for example, JavaScriptEngineSwitcher.ChakraCore.Native.win-x64.props).
For ASP.NET 4.X web sites are used a PowerShell scripts (for example, Install.ps1 and Uninstall.ps1).
For .NET Core applications and ASP.NET Core web applications are used a mechanism based on the runtimes directories and RIDs.

In .NET 4.X versions of the JavaScriptEngineSwitcher.ChakraCore for native assemblies are overrided the default search paths. In this case, native assemblies are located in the x86, x64 and arm subdirectories of bin\[Debug|Release] directory (for web applications and sites just the bin directory).

For 64-bit Windows is enough to install only the JavaScriptEngineSwitcher.ChakraCore.Native.win-x64 package.
.NET applications, ASP.NET web applications and sites in 64-bit Windows  can run not only 64-bit processes, but also in 32-bit processes. For correct working of the JavaScriptEngineSwitcher.ChakraCore in 32-bit process need to install the JavaScriptEngineSwitcher.ChakraCore.Native.win-x86 package. If you do not know in which process will run your application or web site, then install both packages.

P.S.: To avoid such misconceptions in the future I recommend you to read fluently “Release Notes” sections of updated NuGet packages. In case, when problems have already occurred, read the CHANGELOG.md or “Releases” sections. Also do not forget about the documentation and issue tracker.

Hey @Taritsyn, thank you so much for the detailed post! This would be good content for the https://reactjs.net/ website 😃

The V8 package does not work with core 1.0 in VS2017.

@a40637francisco Yes, JavaScriptEngineSwitcher.V8 and JavaScriptEngineSwitcher.Jurassic does not support .NET Core, because .NET Core not supported by the original libraries.

Great read!
I'd like to ask though, is there a reason for not including both the x86 and x64 binaries with the v8 package?

@gunnim This is done in order to allow user can choose only what he really needs.
Advantages of this approach are more obvious when working with the JavaScriptEngineSwitcher.ChakraCore module and LibSass Host for .NET library.
In addition, there is another reason.

Hello, i have followed your instructions and installed the  JavaScriptEngineSwitcher.ChakraCore.Native.win-x86 and also set the chakraCore as my default engine in my app configuration (asp.net 4 , JsEnginerSwitcherCOnfig.cs and GLobal.asax.cs). However i still get the same unable to load one or more requested types.
One thing that was not clear in your above documentation is if i have to run the install script installps1 or if that is done as part of the package installation?
Any suggestions ?

Closing this mega-issue, but feel free to keep referencing it :)

ClearScript.V8 is now deprecated should instead use Microsoft.ClearScript


17-08 ChakraCore servicing release

Addresses the following:
CVE-2017-0228
CVE-2017-8634
CVE-2017-8635
CVE-2017-8636
CVE-2017-8637
CVE-2017-8638
CVE-2017-8640
CVE-2017-8641
CVE-2017-8645
CVE-2017-8646
CVE-2017-8647
CVE-2017-8655
CVE-2017-8656
CVE-2017-8657
CVE-2017-8658
CVE-2017-8659
CVE-2017-8670
CVE-2017-8671
CVE-2017-8672
CVE-2017-8674
Details:
[CVE-2017-8656] PreVisitCatch doesn't call SetIsCatch for all cases
The catch block has a var declaration with the same name as the destructured parameter. When we emit code for initializing vars we don't emit the initialization code for the symbol in the body as the catch param is not marked. The fix is to mark the destructured param as catch param.
Blind constants more aggressively in jitted code
Let RPC do handle marshalling for the JIT process
[CVE-2017-8647] Fix oop jit diff to check msvcrt instead of ucrt
[CVE-2017-8637] [CVE-2017-8659] Harden JIT process against bad input
[CVE-2017-8655] Prevent restoring inlinee frame with the wrong function object
Invalidate lastUsedSegment of an array at the right point
[CVE-2017-8638] Fix function object inline cache if function body got reparsed
[CVE-2017-8657] Postpone adding deferred top-level functions to the deferred function dictionary. Do this so that if byte code gen is interrupted or restarted, we are not left with orphaned functions in the dictionary that may be semi-initialized.
[CVE-2017-8658] Don't attempt to use deferred function stubs inside a formal argument list, as this leads to issues with arrow functions, nested functions, etc.
[CVE-2017-8635] Don't try to reuse property indexes on re-add of a deleted property if the object is non-extensible. Doing so exhausts the free indexes on repeated re-adds, which violates our assumption that a free index will always be available if a property has been deleted.
[CVE-2017-8671] Consider CallFlags_ExtraArg in Function.call implementation. Extra arg (for proxy, etc.) should not be a factor when copying/eliding arguments to delegate to the real target.
[CVE-2017-8674] Re-map function object types if AutoRestoreFunctionInfo has to restore FunctionInfo on failed re-parse/byte code gen.
[CVE-2017-8640] Mark the correct function node when we're detecting 'arguments' declaration that overrides the built-in declaration.
[CVE-2017-8670] Make sure we mark the correct function node when we're processing formal named 'arguments' in a destructured expression.
[CVE-2017-8672] Avoid passing JsNull as JsFunction*
In JavascriptStackWalker GetCaller we were sending out JsNull as a
JavascriptFunction* in the outparam. I checked all locations that
did a call to this function, and recursively as far as the outparam
escaped. Virtually all of the callers of the function or the other
functions that allowed escape of the outparam were safe, as checks
against the return value of GetCaller are near-ubiquitous. The one
callsite where this wasn't the case was in GlobalObject.cpp L#693,
which is in VEval. This location used the outparam without checks,
which meant that if a JsNull object were returned, we'd call other
functions which wouldn't necessarily be correct.
[CVE-2017-8645] Whitelist the type of functions allow to be asm.js module
[CVE-2017-8646] Correctly use PushPopFrameHelper in ProcessLinkFailedAsmJsModule.
No longer ignore arbitrary javascript code after a let
[CVE-2017-8641] Integer overflow in chakra!Js::GlobalObject
Integer overflow can happen in multiple cases of add-mult and allocate.
Fix by using UInt32Math::AddMul() to catch overflows.
[CVE-2017-8634] Type confusion in Concat due to IsConcatSpreadable
[CVE-2017-8636] Limiting args count to a certain limit. This limit will be enforced during the parser time. During the bytecode time we add so many extra args which actually overflowed the initial assumption.
[CVE-2017-0228]  We have attempted to fix the ReverseHelper case where the inline segment was swapped from head to bottom due to reverse loop below. However that fix was done for multi-segment scenario. The EnsureHeadStartsFromZero can also insert head segment in between if the segment's length is less than Array's length (look at the loop above), which will make the code vulnerable. Fixed that scenario by allocating the segment (for the single segment case) if the segment's length is less than array's length.

(Reviewed by the contributors offline.)


Clean warnings in make sw target

make sw target raises several warnings which should be cleaned.

Fixed in https://github.com/pulp-platform/snitch_cluster/pull/135.


cuda device __enter__ and __exit__

Description
Maybe I'm missing something, but the current context management implementation of device
https://github.com/cupy/cupy/blob/770ff2d295637ef6791b8f90c487749f586cc38a/cupy/cuda/device.pyx#L180
seems rather problematic. Essentially in __enter__ we put the new device to the top of the stack, and in __end__ we pop the stack and get it back, and then setDevice with it? Wouldn't this be an non-op? the actual previous device is one slot lower.
Also in any case, I find pytorch's implementation better:
https://pytorch.org/docs/stable/_modules/torch/cuda.html#device
This might also help fix some of your other issues #5943 and #5963
To Reproduce
No response
Installation
Built from GitHub source
Environment
No response
Additional Information
No response

After checking _ThreadLocalStack source code, I find this not a bug.


Add server arn output

Requesting to add server iam role arn output, in order to automate terragrunt/terraform dependency inputs.

LGTM


Fixed links, added few questions

Signed-off-by: shaishavgandhi05<EMAIL_ADDRESS>

Thanks again!

Happy to contribute :)


Ctrl-C in shared terminal session closes terminal with error instead of canceling the running command

Product and Version [VS/VSCode]: VS Code 1.23.1
OS Version [macOS/Windows]: Windows 10 + Linux/Debian
Live Share Extension Version: 0.3.198
Target Platform or Language [e.g. Node.js]: ---
Steps to Reproduce / Scenario:

Start Live Share session from Linux.
Join session on Windows.
Share a (read/write) terminal from Linux.
Join terminal session on Windows.
Start a long-running command (e.g. make).
On Windows side, press Ctrl-C in the terminal to cancel the command.
Instead of canceling the command, the shared terminal closes with the error message "The terminal process terminated with exit code:<PHONE_NUMBER>".
The command keeps running in the terminal and it's also possible to access the shared terminal session again and see the command running.

vsliveshare.zip

I tried to a command today tasklist so it listed a few tasks and then it stopped in between or what i dont know but i didnt reach the end of line so i couldnt type in the command. I tried to scroll down fully but i couldnt see the place where you type the next command and ctrl-c was closing the terminal.
For clarity:
I couldnt see the line below (the line that takes your command as input)
~(FolderName)> (The place where we type new commands)
I could only see some of the tasks listed from tasklist but couldnt see end of line and couldnt enter any new command .

+1 Please fix!  Or if someone has a temporary workaround, that would be great.

This issue has been resolved in the latest Live Share update.


Clean up schema descriptions

Public-Facing Changes
Updated descriptions for several schemas.
Description
Clean up from review of https://github.com/foxglove/message-schemas/pull/14

The source of truth is schemas.ts


Remove trigger key bug

There is a problem with removing (last?) key. The vob does not go to 0 key location, if u remove the key from last to first.
void SpacerApp::OnKeyRemove() - here is the function which removes mover's key.
I don't understand the reason.
Old Spacer (no bug) https://www.youtube.com/watch?v=AU7Uc14fS38
SpacerNET (bug) https://www.youtube.com/watch?v=e0T7bexbz_c

Fixed with some hardcode


Build failures: Cannot have parallel merges, automation token

[avocano] 855b084f-b212-4436-88d9-377a21c53c8f status: FAILURE
View Logs
I'm an automation. Googlers: go/avocano-admin-notifiers

Two PRs were merged close together:
https://github.com/GoogleCloudPlatform/avocano/runs/10934954330
and
https://github.com/GoogleCloudPlatform/avocano/runs/10934959958
The error message:
Error: Error acquiring the state lock

Because a build was already running.
TODO:

Work out if there's a way to only have one of these triggered builds running at once
Fix template template to show information about the failed trigger (trigger name, not trigger ID), for example
Update owner of token that publishes these triggers (working with @pattishin)

Workaround implemented: build failures are now posted to github issues via the glasnt-bot (rather than glasnt) account.
Should probably use a proper bot, pending internal processes.

 They can be re-tried if they fail. Failures are due to TF locks, only.


Regression during upgrade from 2.26.0-2 to 2.27.5

Affected code:
export { DecodedIdToken } from 'firebase-admin/lib/auth/token-verifier';

Error: Unable to resolve path to module 'firebase-admin/lib/auth/token-verifier'  import/no-unresolved
Versions before:
    "firebase-admin": "^11.5.0",
    "eslint-plugin-import"<EMAIL_ADDRESS>
Versions after:
    "firebase-admin": "^11.5.0",
    "eslint-plugin-import"<EMAIL_ADDRESS>

@galkin Thanks for report, after debugging, it is caused by https://github.com/import-js/eslint-plugin-import/commit/808d504bffe29286a885475a424562969e9d4879#commitcomment-107093802
And also, firebase-admin does not exports lib/auth/token-verifier in its package.json settings, so you should use export { DecodedIdToken } from 'firebase-admin/auth';, actually.

Answered as above.


Compilation error when using lifetime annotations with #[from]

Hi,
I’ve just run into an issue with thiserror. It may just be my inexperience with Rust’s lifetimes, though. The issue occurred when I was trying to use the #[from] attribute on an error that requires a lifetime specifier. I managed to create a minimal working example:
fn main() -> Result<(), Error<'static>> {
    Err(Error::SubError(SubError::Variant("some text")))
}

#[derive(Debug, thiserror::Error)]
enum Error<'a> {
    #[error("sub error")]
    SubError(#[from] SubError<'a>),
}

#[derive(Debug, thiserror::Error)]
enum SubError<'a> {
    #[error("variant: {0}")]
    Variant(&'a str),
}

This gives the following compilation error:
error[E0495]: cannot infer an appropriate lifetime due to conflicting requirements
 --> src/main.rs:5:17
  |
5 | #[derive(Debug, thiserror::Error)]
  |                 ^^^^^^^^^^^^^^^^
  |
note: first, the lifetime cannot outlive the lifetime `'a` as defined on the impl at 6:12...
 --> src/main.rs:6:12
  |
6 | enum Error<'a> {
  |            ^^
note: ...so that the types are compatible
 --> src/main.rs:5:17
  |
5 | #[derive(Debug, thiserror::Error)]
  |                 ^^^^^^^^^^^^^^^^
  = note: expected  `&Error<'_>`
             found  `&Error<'a>`
  = note: but, the lifetime must be valid for the static lifetime...
note: ...so that the type `SubError<'_>` will meet its required lifetime bounds
 --> src/main.rs:5:17
  |
5 | #[derive(Debug, thiserror::Error)]
  |                 ^^^^^^^^^^^^^^^^

error: aborting due to previous error

Any ideas as to how this could be solved?
Thanks for your work on anyhow and thiserror; IMHO they are the best the Rust ecosystem has to offer in terms of error handling :)

Hi @arzg, thanks for the report. I released 1.0.12 with a better error message for this case. This doesn't compile because Error::source always needs an inner error that is 'static, and an arbitrary lifetime 'a may not be long enough. You're free to still handwrite a From impl or use some other derive(From) macro to generate it, it just means the inner SubError won't be wired up as the source of the outer Error and thus a derive(Error) isn't the right macro to generate that From impl.
impl<'a> From<SubError<'a>> for Error<'a> {
    fn from(sub: SubError<'a>) -> Error<'a> {
        Error::SubError(sub)
    }
}

Thanks for the quick response and detail. I think what I’ll end up doing is allocate, since performance isn’t much of a concern in this scenario.


Pin working qemu image

New release yesterday broke: https://hub.docker.com/r/multiarch/qemu-user-static

Coverage: 99.323%. Remained the same when pulling 2d5837a1d63a0c88bafc16e370fb24dd56b2f13b on thetic:rereqemu into 28cbaa7f295fc39702fd0404ba760c1255c33d6c on cpputest:master.


Fuel tank strap pouch

https://cm-ss13.com/wiki/Marine_Equipment#Fuel_tank_strap_pouch

https://github.com/CM-14/CM-14/pull/762

It wasn't added by the #762
I remember + checked it, that i just commented its name there

It wasn't added by the #762 I remember + checked it, that i just commented its name there

Shoot. Uhh I'll let you handle the rest of these.. don't lose track!

Shoot. Uhh I'll let you handle the rest of these.. don't lose track!

i will not senpai 🫡


refactor(@angular/pwa): rename manifest.json to manifest.webmanifest

Using the webmanifest file extension makes it easier to target the web app manifest in server configs and apply the correct MIME type (see https://github.com/w3c/manifest/issues/689#issuecomment-402773032).

@alxhub WDYT of this change?

Alex gave his support offline. This will be released in the next minor as it's a file change.


Create pdeshmuk.yml

Hi @pdeshmuk so sorry I missed seeing this sooner ... I am not certain exactly why this request failed, but it does look like it has been working for others so there may be something that was fixed since you submitted this request, would you mind resubmitting the same request? I think it should work but if not let me know, the best ways to reach me are via vmware slack, vmware code slack, or linkedin message. Thanks!

Hi @pdeshmuk so sorry I missed seeing this sooner ... I am not certain exactly why this request failed, but it does look like it has been working for others so there may be something that was fixed since you submitted this request, would you mind resubmitting the same request? I think it should work but if not let me know, the best ways to reach me are via vmware slack, vmware code slack, or linkedin message. Thanks!


Merge CI matrix.os

taking examples from tree-sitter-bash

Closing, since it seems the example is deprecated.


Replace cross with cargo-zigbuild in CI

Closes #404

Opened issue in https://github.com/rust-cross/cargo-zigbuild/issues/271, the linker is unable to detect llvm tools

Will resolve ur review, when the cross tests passes

Now that we have compiling for armv7 and aarch64 working in CI and on linux (macos pending), without using cross at all, I think we can close this PR and forget both cross and zigbuild?


support for fully qualified names?

One thing that has come up in some of my work is that the rename options do not have a way to automatically include e.g. the full module path. Example:
struct A;
mod B {
struct A;
}

In this example the struct name for both B::A and A would be the same, unless it's somehow overriden. This becomes more of an issue when working with structs from e.g. different crates.
This is related to previously discussed issues:

https://github.com/serde-rs/serde/issues/1964
https://github.com/serde-rs/serde/issues/1636

but much more specific since it's just a case of needing crate/module unique identifiers.

I'd prefer not to build something dedicated to this into this crate, but either of the issues you linked is still a possibility so I'll close in favor of those.

I think where this is unique is in applying the rename to the base struct name, rather than a field-level rename (which doesn't work nicely for things like Vec).


Update docs on required node version

20+ is actually required, not 16. I also updated the warning in code with this other PR: https://github.com/microsoft/devicescript/pull/680

Thanks for taking the time to do a PR.


docs: added atomic design alternative docs

Background
I've decided to update Alternatives page on Atomic Design as I know that I could help on this.
Changelog

Updated Atomic Design section in Alternatives page in English and Russian.
Deleted WIP notification in Atomic Design section.

Написанную мною секцию проверил на LanguageTool и в Главреде.
По главреду, чистота - 8.7, читаемость - 8.8

Hi! Thank you for review. Yes, I agree, these names are better than from the WIP. As for a layer for business logic, I agree, that's what I meant, I clarified it


[FEATURE] Support C++23 tuple APIs

A bunch of the std library language around tuple has changed, I think specifically to support std::tuple proxy value/reference types for std::views::zip. Many of these changes are in p2321.
I ran into this in this example of using a kumi::tie as a reference tuple type for an SoA iterator, and trying to use std::ranges::sort on the range. https://godbolt.org/z/9bYb1oM8z.
Currently the first compiler error I run into is the following common_reference failure, which I guess requires specializing basic_common_reference, however there could be more problems hidden behind this one.
/opt/compiler-explorer/clang-16.0.0/bin/../include/c++/v1/__type_traits/common_reference.h:113:1: note: because substituted constraint expression is ill-formed: no type named 'type' in 'std::common_reference<kumi::tuple<unsigned int &, unsigned char &, unsigned int &> &&, kumi::tuple<unsigned int, unsigned char, unsigned int> &>'
using common_reference_t = typename common_reference<_Types...>::type;
^
1 error generated.

edit: punctuation

This is the code to add :
namespace std
{
  template< kumi::product_type TTuple,kumi::product_type UTuple
          , template<class> class TQual, template<class> class UQual
          , typename Indexer = std::make_index_sequence<kumi::size_v<TTuple>>
          >
  struct make_basic_common_ref;

  template< kumi::product_type TTuple,kumi::product_type UTuple
          , template<class> class TQual, template<class> class UQual
          , std::size_t... I
          >
  struct make_basic_common_ref<TTuple,UTuple,TQual,UQual
                              , std::index_sequence<I...>
                              >
  {
    using type = kumi::tuple<std::common_reference_t< TQual<std::tuple_element_t<I,TTuple>>
                                                    , UQual<std::tuple_element_t<I,UTuple>>
                                                    >...
                            >;
  };

  template< kumi::product_type TTuple,kumi::product_type UTuple
          , template<class> class TQual, template<class> class UQual >
  requires( kumi::size_v<TTuple> == kumi::size_v<UTuple>)
  struct basic_common_reference<TTuple, UTuple, TQual, UQual>
  : make_basic_common_ref<TTuple,UTuple,TQual,UQual>
  {};
}

but looks like kumi::tuple::operator= is missing some cases


onEnter has no store. How do I get store params from within onEnter?

There is no store in onEnter. Why? How to access it from there? Example below.
A store.
let store = {
    isAuth: false
}

Routes.
I want to check isAuth inside onEnter. But this is a Route instance, not a store. So how to access it?
<Provider store={store}>
    <Router history={browserHistory}>
        <Route path="" component={App}>
            <Route path="/"
                onEnter={(nextState, replace, cb) => {

                    // How to get either props or store here
                    if(this.props.isAuth == true) {
                    }
                    cb(null);
                }}>
                <Route component={AuthLayout}>
                </Route>
            </Route>
        </Route>
    </Router>
</Provider>

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux. Thanks!


Potential fix for Issue 230

What does this PR do?
VerifyWebhookSignature now returns an error if an *http.Request with an empty body is passed.
Where should the reviewer start?
Only a few lines were added to webhooks.go. Feel free to write new unit tests for VerifyWebhookSignature.
How should this be manually tested?
c.VerifyWebhookSignature should be passed an *http.Request  with an empty body.
Any background context you want to provide?
Issue #230

Added spaces :)


UI/UX:  Improve Pair Switching

"improve ux": make the pair easier to change, etc.

Done in release with new UI


Unable to add blocks

Hey
I'm sorry if I misunderstood something here, but shouldn't the add-block button be working here? This is a fresh install of WordPress, there are no plugins installed or anything.

Hello @grandeljay!
By default, all WordPress Core blocks are allowed only in posts. This is because we always develop custom blocks to be used on pages for most of the projects.
You may change this behaviour in the functions.php file: https://github.com/digitoimistodude/air-light/blob/master/functions.php#L129-L169
Going to close this issue, but please let me know if you have any further questions!


AUI-1903 Restyle add field button in Form Builder

Just started reviewing :) :octocat: Sent from GH.

The code lgtm, but something seems to be off with the css when using the form builder on a small screen, the position of the new buttons for adding fields feels weird. For example, if I add a new row at the bottom when on a small screen, this is what it looks like for me:

Closing since this was sent again as https://github.com/mairatma/alloy-ui/pull/219


Callback on Schedule before sending a mail

Hello there,
I'm thinking about using your implementation for our project, but - alas! - one feature seems to be missing. When scheduling mails I need a callback that get's called before the mail has actually been sent to decide whether I send this email or not (for these kind of "Long time no see!"-Mails). Is this some feature which is considered for one of the next releases? Otherwise I'm thinking about issuing a pull request!
Cheers!

@RyamBaCo thanks for writing.
This seems to be a duplicate of issue #22.
Unfortunately I have no time at the moment to work on the feature. If you want to open a PR I would love to review it. Don't forget to add unit tests.
Any contribution is welcome

Close duplicate due to inactivity


feat: redirect user to login when GET intervention/{id} requests are made with invalid token.

redirect user to login when GET intervention/{id} requests are made with invalid token.

** To Test **

[ ] Create or open an intervention that is assigned to your user account.
[ ] Review said intervention
[ ] logout
[ ] Move between pages
[ ] user should be prompted to login
[ ] On successful login, API call fetching data will be made

logged in
went to cost effectiveness and tried to fork intervention, api error
selected int ID 47, review, clicked through pages, save and close
logged out
navigated pages, no dialog when switching between pages


Spritesheet not generating

Hello,
it seems it's not possible to generate spritesheets.
I dropped a file "file[10,10].png" in assets and a spritesheet is not generated.
Looking at the code, it seems this portion is looking at the file extension:
var spritesheetData = gameAssets[i][0].match(/\[(-?[0-9],?)*]/);
I don't feel familiar with this part, can you confirm there's a problem with this?

Yeah there is a problem I just opened a pull request to fix that #36

Merged in #36, give it a go now and update issue accordingly. Thanks!


Issue populating world with OTG

I'm trying to populate the 1:1000 scale for a modded survival server. How did you configure OTG cause every time I try and play the maps with OTG loaded with biome mode set to FromImage no forest are loaded, Everything else works fine. I have checked biomes and it looks like all biomes are correct.

So I figured out that my issue was biome colors not matching. I spent the better part of a day looking at world painter and the OTG image provided trying to match all colors. Now i'm getting a "Exception preparing structure feature" error when I try to open the world. I looked at the log and the error is occurring when OTG is attempting to place a mine shaft.  Would it be possible for you to add your OTG world folder to the repository so that me and anyone else trying trying to populate a custom survival world wont have any issues.

Hey, what version of Minecraft and OTG do you use? Forge or spigot. Sounds more like an OTG bug. Have you installed any other mods/plugins? I can upload my OTG folder and do a little tutorial, but it will take some time.

I'm running the latest version of OTG for 1.12 with forge <IP_ADDRESS>36. I was getting this error in a test profile I created with no other mods. I will eventually be using the enigmatica 2 expert mod pack. I have gotten OTG working when creating other worlds. It was when i set all the biome colors that OTG started to give me that error. If you could upload your OTG folder that would be great cause I think my problem may be messed up biome colors since thats when the error started to occur.

Hello, I'm sorry the answer took a little longer. I have problems with Forge and OTG myself, but I can recommend "Painted Biomes". It's like the "fromImage" function of OTG as a stand-alone mod. I will upload the config file to GitHub. Just put the image (BiomeMap--k.png) in the folder "config\paintedbiomes\templates\dim0" and rename the image to "biomes.png" and replace the "paintedbiomes.cfg" file with the one I provided.

Thanks, Checked it this past weekend and everything works.


6/22 hangout slides

Is 6/22 yesterday slides available now? TQ!
And for the ROS kinetic version,
https://www.youtube.com/watch?v=GO_Du32Em9o
seems turtlebot3 already could run on it. I'll check.

Slides are here: https://storage.googleapis.com/cartographer-public-data/cartographer-open-house/170622/sildes.pdf
Yes, Cartographer runs on the turtlebot. Why did you doubt that? Tuning for the depth camera is harder as for the lasers though.

TQ!


Better help command

Description
A much nicer and more practical help command.
Also adds pagination to help manage large numbers of commands.

Testing
Tested on local copy of server (arch linux)

Checklist
Things need to be done before this Pull Request can be merged.

[x] Code is well-formatted and adheres to project style guidelines: cargo fmt
[x] Code does not produce any clippy warnings: cargo clippy
[x] All unit tests pass: cargo test

Looks very nice.
Good job @vyPal :+1:


passing data out of cntl and ioctl doesn't work

We currently don't support passing data out of fcntl and ioctl which results in the failure of any fcntl and ioctl that requires tha.t

fixed in #1930


Undefined union fix

Fixes #187

Codecov Report

Merging #188 into main will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #188   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           40        40
  Lines          706       706
  Branches       115       115
=========================================
  Hits           706       706

Impacted Files
Coverage Δ

packages/expect-type/src/index.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0eccf7c...ffafda0. Read the comment docs.


Caching and HMR problems from base project

I've been trying to start a new project based off this boilerplate since it incorporates a lot of technologies I'm interested in learning, like CSS modules and redux-saga. However, I'm having some issues out of the gate. To clarify: I'm reproducing this locally by cloning the latest version of the repo to date, running npm run setup, and npm start.
webpack dev middleware doesn't seem to want to load common.js
I get the feeling this is an error in my local environment somewhere, but it's worth mentioning to see if anyone has a solution. When I start the server and load up localhost:3000, I get an Unexpected token < error on common.js. Looking at the network tab, I see that common.js was a 200 (not cached, presumably), but did indeed serve up HTML. It's not quite the same as the page itself; it includes another data-dll script, reactBoilerplateDeps.dll.js, which I'm not sure of the purpose of. I also notice in the network tab that the page was loaded from a ServiceWorker... I've never seen that behavior before.
I can resolve this issue by performing a 'Hard Reload' (I already have cache disabled in dev tools; this seems to make no difference and no requests appear to be cached).
I just checked, this happens specifically in Chrome (not FF). Could be a Chrome bug? I'm running Ubuntu 16.04 LTS, Chrome 51.0.2704.103.
HMR does not work correctly
This is the more disruptive issue, although it's possible it's related to the first one. HMR doesn't seem to work at all. If I change any JSX or CSS, I get the same webpack error, [HMR] The following modules couldn't be hot updated: (Full reload needed) This is usually because the modules which have changed (and their parents) do not know how to hot reload themselves ....
HMR appears to not work in either FF or Chrome, same messages.
Side note in hope that it may be of use: sw.js fails to load with ERR_INSECURE_RESPONSE consistently after a few seconds each time. I also get an offline-plugin warning, but I assume this is intentional since the OfflinePlugin isn't loaded in the dev webpack config.
Let me know if the details aren't clear enough.

@a-type Hi Grant, did you try running the example app?

Clone the repo
npm install
npm start
Open localhost:3000

If that fails, what do you get when you run npm test?
In my experience, npm run setup leaves the project in a very incomplete state. There appear to be no concrete instructions yet on how to develop an app after npm run setup.
I have been more successful making copies of existing components and containers and modifying them to create new pages. The clean, highly modular architecture makes that easy.
For example,

Copy the containers/HomePage folder
Search and replace to create an new page.
Create route to your new page with npm run generate route
When the above works, continue modifying as needed.

In my experience, until you become more familiar with the project it's better not to npm run generate new components or containers.

HMR does not work correctly

I have found HRM to be 'quirky' in Chrome (Mac) but it's usable. Let's get you working with the example app and take it from there.
Welcome, -Glen

Thanks for replying @gihrig
All the issues I listed occurred while attempting to run the example app with the steps you listed. Tests all pass. I've made no modifications at all to the repo.

For reference, I have already worked on a few projects with React/Redux/HMR, and they all work correctly with the same setup and environment.

HMR appears to not work in either FF or Chrome, same messages.

@a-type here's something else to try in case you haven't. My experience with 'quirky HMR' is related to the project's offline-first configuration. This gets established when you load the page in production mode npm start:production, and to some degree even in development mode. As far as I can tell this data is never removed. I was even able to shutdown the server and access the app, just as advertized.
To clear cached data out of Chrome (51 Mac OS):

Open developer tools
Select Resources
Select and clear all data under Session Storage, Application Cache, Cache Storage and Service Workers
Close the tab (don't know why but it seems to be necessary sometimes)
Open localhost:3000

I don't use Firefox much, but for me, HMR has always worked as expected in FF.

Interesting... the service worker was from the app which I had previously begun to build off of react-boilerplate before circling back and trying to reproduce this issue with the default example app. Deleting the service workers seems to have fixed the initial load issue. HMR still isn't working, though.
I think the next step for me might be removing all of the offline configuration from webpack. I don't think that feature is a high priority for me.

Glad you're making progress.
Re:
HMR appears to not work in either FF or Chrome, same messages.

Side note in hope that it may be of use: sw.js fails to load with ERR_INSECURE_RESPONSE consistently after a few seconds each time.

I get that same message in the browser console every so often. I presume this will go away when the production mode project is loaded on a server that supports https, but I haven't gotten that far. Doesn't seem to affect HMR though.

Deleting the service workers seems to have fixed the initial load issue. HMR still isn't working, though.

What kind of components are you changing?
Currently, stateless function components cannot be hot reloaded, only ES6 class or React.createClass components can. This is a downside of the current way HMR works and nothing we can fix, though there is work being done to change this!

Hi @mxstbr, I'm not using function components. I'm currently reproducing this with only the example application from this repo, no changes or custom components whatsoever. I have tried modifying the App container JSX and CSS, but HMR always claims that these modules do not know how to reload themselves.

@a-type I see the same HMR failure with containers/App - this is a stateless function component as @mxstbr pointed out, HMR failure is expected.
Do you see the expected HMR on containers/HomePage, for example?
If so, and you want HMR for App, you could:
a) Make App an ES6 class component, as @jasoncyu linked above. Here's App specific code:
/* eslint-disable react/prefer-stateless-function */
class App extends React.Component {
  render() {
    return (

      {this.props.children}

  );
}

Or
b) Remove the visible components (the header) from containers/App and place those in their own components/Header. This is desirable if you have an app that doesn't need/want the same header components on every page.

Oh, wow, @gihrig, I feel very silly now! You're right, the HMR failure is expected. I hadn't realized that the functional-component rule would also apply to the CSS of the component, because I'm so used to working with independent SASS stylesheets which wouldn't depend on the component they're applied to. I imagine that using CSS modules makes the style reloading for App dependent on the App component itself, which cannot be reloaded.
Thanks for all your help, I'm glad I understand the source of the problem now, even though it was on my end (sorry!).
Can be closed as a non-issue.

Thanks @gihrig for helping resolve this, glad everything is clear now @a-type!


[release] v0.16.2

[x] Update changelog
[x] Change Hugo min version in theme.toml
[x] Change version

[x] /VERSION
[x] .seed-config.yaml
[x] /package.json
[x] /exampleSite/package.json
[x] /exampleSite/config.toml
[x] /exampleSite/config-dev.toml
[x] /exampleSite/content/docs/installation/content.md
[x] layouts/partials/head.html

[x] Create stable release branch vX.X (gets minor, non breaking updates)

[ ] Migrate various test/production sites to release branch
[ ] tag alpha, beta releases, if necessary

[ ] Fix/document remaining bugs/PRs
[ ] Test sites again
[ ] Rinse and repeat

[ ] Update docs to latest release branch
[ ] Create final tag
[ ] Create Github release
[ ] Release notes
[ ] Migrate starter repo

[ ] Update submodule
[ ] Update config.toml (with version and content changes)
[ ] Change Hugo version in netlify.toml

[ ] Test latest release with themes.gohugo.io script
[ ] Update stable demo branch master for themes.gohugo.io (gets all, also breaking updates)
[ ] Merge latest syna demo/page into about.okkur.org/syna/ (see syna/README for specifics)

Pushing this release to tomorrow as we are investigating a Hugo dependency issue #719

Ran into another Hugo dependency issue with ambiguity. Pushing release again to get this worked out.
Thanks for being patient with the release. Always happy for contributions and involvement.

Fixed a few issues and generated dev files again with the new changes. Hopefully it fixes everything. The ref issue is a bit weird. I'd appreciate it if you can investigate it further using the changes in PR.

Not sure, why it came up now. A bit annoying to have breaking changes it almost every version now. Anyway so far no other issue came up during more production website migrations. Will finish the migrations and further tests, before pushing the final tag. Still need a review on #720


chore: upgrade to relay 6

partly addresses #46 I deferred making the filesystem changes b/c it's not as straightforward as i'd like. The fs is cached, and stating early like this plugin does can poison the fs cache so that webpack thinks files don't exist when they do.

@jquense thanks! I'll publish a new version shortly with this in it


Windows support

Similarly to #26, it would be great to get Windows support. I assume since you welcomed PRs for FreeBSD, you might also welcome ones that add Windows support?
(Obviously, Windows being what it is, I expect this would require more work than FreeBSD... ;) ).

What are the missing bits given the existing PR?

Packages (maybe via chocolatey)?

Something like this is more likely:
https://gallery.technet.microsoft.com/scriptcenter/Script-to-get-installed-80cd3798
by the looks of it - digging through the registry should produce the most universal results for base system

I really can't recommend taking a dependency on anything written in VB. wmic probably has a longer deprecation horizon; VB is very legacy.

So it's either wmic or inline .NET doing the query. For MVP I would suggest just calling wmic subprocess and retrieving the results then allow someone with deeper Windows knowledge to build further.

Definitely wmic is the easiest bar, though won't detect portable apps installed via chocolatey. I'd say that's going to be an edge case for systems administration vs consumer users.

Re: supported - wmi dates back a decade or so at least. Probably fine for the set of likely user population of this library.

wmic should detect anything installed via an installer since that puts uninstaller registry entry. Packages like Docker could be both installed via an installer and chocolatey so there might be some edge cases with using them both.

Having come back to this, I'm now inclined to think that package should assert against package-manager installs only. If software is present on the machine, and the person wants to write tests to assert that, I bet they're almost certainly already aware of chocolatey.
And, @JackLeo is entirely correct, it's possible for a thing to be installed via chocolatey and other means, to completely separate places.
Is it reasonable to make one (initial) chocolatey implementation, and one wmic-based? I saw there's a --format argument to specify which flavour...?

I would be inclined to suggest more of a salt approach. package should check all default packaging methods. Any additional ones should be explicit.
Example:

package - https://docs.saltstack.com/en/latest/ref/states/all/salt.states.pkg.html
pip - https://docs.saltstack.com/en/latest/ref/states/all/salt.states.pip_state.html

I do agree that wmic is not necessarily a packaging mechanism and it might need to be exposed as an explicit check/utility, however, I do not agree that chocolatey could be considered a default method of install/packaging, equally I would not say brew is default one for mac purely based on the fact that is installed by the user and not shipped as part of the OS.

#349 should help with this.

#380 is trying to add a Windows binary to the releases.

is this still active?

Goss now provides community supported alpha binaries for windows as per- #585


Backport fix for https://github.com/pyinstaller/pyinstaller/issues/2985

Fixes #29

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Whenever possible python packages should use pip. See https://conda-forge.org/docs/meta.html#use-pip

@conda-forge-admin Please re-render!

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Superseded by #31, thanks @nehaljwani!


Print integral types as bit sizes instead of standard types

Hello !
Another idea for improvements:

As for now, integral types are shown as int, unsigned int, etc
An idea is to print them as uint8, int8, uint16, etc
This is because an int does represent the size of the integral only for the platform it currently run.
I think a lot of developers do not use standard types (int, char, ...) but typedefs types (uint32_t, uint8_t, ...) just like me!
I think this is just a matter of updating theses lines with proper types even if there could be a better more generic way:

If you agree to this feature and you are not available, it will be my pleasure to provide a PR!

Thank you for the feedback.
I might not have considered every aspect of it, but it sounds like a good idea to me!
I personally also prefer uint64_t over unsigned long.
Implementation-wise, I would suggest we introduce a helper macro:
#define DBG_MACRO_REGISTER_TYPE_NAME(type) \
  inline std::string get_type_name(type_tag<type>) { return #type; }

DBG_MACRO_REGISTER_TYPE_NAME(uint8_t);
DBG_MACRO_REGISTER_TYPE_NAME(uint16_t);
DBG_MACRO_REGISTER_TYPE_NAME(uint32_t);
DBG_MACRO_REGISTER_TYPE_NAME(uint64_t);
DBG_MACRO_REGISTER_TYPE_NAME(int8_t);
DBG_MACRO_REGISTER_TYPE_NAME(int16_t);
DBG_MACRO_REGISTER_TYPE_NAME(int32_t);
DBG_MACRO_REGISTER_TYPE_NAME(int64_t);
DBG_MACRO_REGISTER_TYPE_NAME(std::string);

A few tests need to be adapted, but I'm fine with replacing int => int32_t, unsigned short => uint16_t, etc.

The README also needs to be adapted.

This sounds like a good place to put in a new config option. Put an ifdef here to allow switching between using bits and standard types.
Ensures everyone is happy.

@sharkdp Good idea!
@DerekCresswell It's a good idea as it would not require any additional engineering!

I would try to avoid adding additional configuration flags. dbg.h is designed to work "out of the box". Adding another compile-time switch also increases the complexity of the code and the tests.
Instead, we could simply show both. Let's say a user prints an int and int ~ int32_t on his platform. We would then show something like
[tests.cpp:76 (main)] x = 42 (int ~ int32_t)

If !std::is_same<int, int32_t>::value on this platform, we would only show int.

I think there is no need to have a mandatory int == int32_t.
I do think we can run sizeof() in a constexpr context (to be confirmed). The exemple shown below doesn't use constexpr, but it would be great as it would not add any allocation management when combined with the power of templates. It would also not be hard to implement as constexpr and could adapt to all platform even non-standards ones with 7 bit per bytes. (Not sure that really exist).
We could not print _t suffix, to keep only the essential part: [u]int<size * 8>
    template <typename T>
    constexpr const get_type()
    {
        std::string type {}; // or something without dynamic memory management
        type.reserve(7); // max type size: uint128 -> 7 chars
        // std::is_unsigned or something like this
        // sizeof(T) * 8
    }

I think there is no need to have a mandatory int == int32_t.

you mean... even if sizeof(int) == 4, we could have std::is_same<int, int32_t>::value evaluate to false?

No, sorry. I meant that we can compute int32 at run-time or compile-time instead of forcing associations like int = int32_t !

I wouldn't force this association. I would test for it. Something like:
inline std::string get_type_name(type_tag<int>) {
  return (std::is_same<int, int32_t>::value) ? "int ~ int32_t" : "int";
}

And yes, this function could be constexpr if we can generally return a const char* instead of a string.

inline std::string get_type_name(type_tag<int>) {
  return std::is_same<int, int32_t>::value ? "int ~ int32_t" : "int";
}

I feel like with this implementation output for other class templates will be messy. For ex, outputs like these
[main.cc:21 (solve)] v = {} (std::vector<std::pair<int ~ int32_t, int ~ int32_t>>)

We could rather prefer bit size variant over the standard types when std::is_same_v<int, int32_t> evaluates to true and register all such associations using a macro as you suggested here. Something like
#define DBG_MACRO_REGISTER_TYPE_ASSOC(t_std, t_bit) \
  constexpr inline std::string get_type_name(type_tag<t_std>) { \
    return std::is_same<t_std, t_bit>::value ? #t_bit : #t_std; \
  }

I feel like with this implementation output for other class templates will be messy.

True

We could rather prefer bit size variant over the standard types when std::is_same_v<int, int32_t> evaluates to true and register all such associations using a macro as you suggested here.

Sounds good to me!


Update view-markdown-source selector

Fix selector
Match GitHub's tooltip style (position)

Test: https://github.com/sindresorhus/refined-github/blob/master/contributing.md
Before

After

Well, I should've converted it to draft because I just found a page where the problem still exists: https://github.com/kidonng/cherry/blob/master/Bookmarklets.md


Can not import glTF with blendshapes/morphs :(

I exported glTF files with blendshape/morph anims from Blender:
https://drive.google.com/file/d/1v7OWs7l3r-BD-tde7Gx4F_WqxzvcyJa7/view?usp=sharing
The files open fine and play anims in the glTF viewer: https://gltf-viewer.donmccurdy.com/
However, when importing the same files into UE4, I get this error:
Failed to import 'D:/games/quake/id1/progs/flame2blender.gltf'. Failed to create asset '/Game/Models/Quake1/flame2blender'.
Please see Output Log for details.
The Output Log shows no useful info:
LogFactory: FactoryCreateFile: StaticMesh with glTFFactory (0 1 D:/games/quake/id1/progs/flame2blender.gltf)
Error: Failed to parse the glTF file flame2blender
LogSlate: Window 'Message' being destroyed
Message dialog closed, result: Ok, title: Message, text: Failed to import 'D:/games/quake/id1/progs/flame2blender.gltf'. Failed to create asset '/Game/Models/Quake1/flame2blender'.
Please see Output Log for details.
LogAssetTools: Warning: Failed to import 'D:/games/quake/id1/progs/flame2blender.gltf'. Failed to create asset '/Game/Models/Quake1/flame2blender'.
Please see Output Log for details.

Sorry about that. The plugin doesn't support importing the morphs mesh for now.
I will implement that in the next version.

Sorry about that. The plugin doesn't support importing the morphs mesh for now.
I will implement that in the next version.

fixed aa3430d99f64aa1a50a0f8984db582778468fc09

And you can download the new version 2.0.5 from https://c4gio.itch.io/gltf-for-ue4.

@motorsep It supports the morph target.

@motorsep It supports the morph target.

OMG!! Awesome, thanks a bunch!


pre triggers don't have access to keywords on the first run

While playing around with the name idea discussed in #309, and first seeing how I liked the existing keys facility, I made the following script
require 'rufus-scheduler'

scheduler = Rufus::Scheduler.new

def scheduler.on_pre_trigger(job, t)
  puts "pretrigger: #{job[:name]}"
end

scheduler.every '1s' do |job|
  job[:name] = "the name"
  puts 'Hello... Rufus'
end

scheduler.join

which produces this output
➔ bundle exec ruby code.rb
pretrigger:
Hello... Rufus
pretrigger: the name
Hello... Rufus
pretrigger: the name
Hello... Rufus
pretrigger: the name
Hello... Rufus
pretrigger: the name
Hello... Rufus

Note that the first iteration doesn't have name assigned. I think this maybe indicates a bug?

Since the name is assigned in the trigger, I think it's totally normal it's not present before it's assigned.

Gotcha - in the light of day I realize I was thinking of them as "job attributes", but really they are "job-local variables" as the docs say.


Throw an error if Polymer is loaded twice

Whenever Polymer is somehow loaded twice, there is a cryptic error shown in the console:
Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': this name has already been used with this registry

This happens when two urls resolve to different versions of Polymer (for example relative and absolute url). The following is now shown in the console when running the new smoke test:

Feel free to bikeshed on the actual message. Maybe @arthurevans has suggestions for this?
Reference Issue
Fixes #4134

@TimvdLippe Are you able to add a unit test for this? Not sure how easy it is to get a second version of polymer actually loaded...

I am not sure if we can. You can run the smoke test to see how it works. It is really easy to make such mistakes (in this case just two link elements)

@kevinpschaaf Managed to write a unit test using an iframe.

I fixed the unit test, however it appears it is failing on Safari:
AssertionError: Error message should include "Polymer loaded twice": expected false to be true (http://localhost:8081/components/chai/chai.js:210)

Sadly I do not have a Safari machine, so I can not debug this issue. It is probably an incorrect error message that is posted :cry:

@sorvell Tests have now been fixed. PTAL

I am no longer pursuing this PR.


Converts to vitest from jest

Summary
This PR converts from using jest to a fully jest-compliant replacement: vitest. Vitest has a number of features that provide a superior experience with jest, including:

Lightweight and Fast: Vitest is designed to be lightweight and fast, with minimal overhead and dependencies. This can make it a good choice for small to medium-sized projects or for developers who prioritize speed and simplicity in their test suite.
Simpler Configuration: Vitest has a simpler configuration and fewer options than Jest, which can make it easier to set up and use for developers who are new to testing or who prefer a more minimalistic approach.
TypeScript Support: Vitest has built-in support for TypeScript without requiring any additional configuration, which can be a big advantage for TypeScript projects.
Familiar Syntax: Vitest uses a familiar syntax for writing tests that is similar to Mocha and Jasmine, making it easier for developers who are already familiar with those frameworks to get up and running quickly.
Easy Integration with Other Tools: Vitest integrates easily with other tools in the JavaScript ecosystem, such as webpack, Babel, and ESLint. This can make it a good choice for projects that use these tools and want to minimize the configuration required for their test suite.

This change makes using tests with TypeScript, and ultimately on to ESM, much easier than jest.
⚠ Also important to note: I've added the dependencies once, in the root package.json. One of the cool aspects of workspaces is our ability to share devDependencies across internal packages, making managing test dependencies much simpler.

LGTM


Remove event listener on sse stream closing

removes listener when sse request is closed

We will still see response terminated with an error with headers already sent since that is fastify warning if request closes before response but we cannot fix that.
resolves #1029

typescript error https://github.com/ChainSafe/lodestar/pull/1050/checks?check_run_id=806985906#step:8:313

file conflict, i think from the block api PR


Update create-column-encryption-key-transact-sql.md

Corrected "comprise", in line 73, to "compromise".

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

Looks good; thanks.


feat: toggle for iptables rules creation

Signed-off-by: Alexander Trost<EMAIL_ADDRESS>

Awesome!
Simple linting reviews and merge is super approved!
Thanks again! 🥳🤯


Dark / light mode theme

Hi!
I have made a suggestion for dark/light mode in your app.
Basically, I've just added the next-themes package,  and tried to make it look somewhat ok. Hope you like it, and if you want me to do some changes just let me know.

Thanks for the PR! I like the changes you've made. Can you:

Remove the Card layout from all the components (Send, Receive, Settings, etc)
Fix Toggle so it's visible in the settings page
Darken the input fields on light mode like you did with dark mode

Let me know when the changes are ready and I'll review.

Hey.
I'm glad you liked it. Sorry for the late reply, I've been travelling all
day.
I made some changes, you can have a look. Just let me know if you want
something different.
On Wed, 28 Dec 2022 at 19:10, vilm3r @.***> wrote:

Thanks for the PR! I like the changes you've made. Can you:

Remove the Card layout from all the components (Send, Receive,
Settings, etc)
Fix Toggle so it's visible in the settings page
Darken the input fields on light mode like you did with dark mode

Let me know when the changes are ready and I'll review.
—
Reply to this email directly, view it on GitHub
https://github.com/vilm3r/sendstr-web/pull/6#issuecomment-1366832573,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALR4OZDNJJKVIXQZQ77MF5DWPR7BDANCNFSM6AAAAAATKWA3YQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Vennlig hilsen/Best regards
Arne Lamo Pedersen**Mob: (+47) 97 64 33 55
P Please don't print this e-mail unless you really need to.

Hey, did you abandon the project? :)


switch the name and refs of course_template to base_ottr

Purpose/implementation Section
What changes are being implemented in this Pull Request?
I've been meaning to do this for awhile. I switched the name of course_template to base_ottr in dockerhub but need to update it everywhere else.
First we need to test that it actually runs appropriately. Note that the dockers for ottr are stored here now: https://github.com/jhudsl/ottr_docker

This is good! Merging!


range indicator "breaks" as calendar get wider

here is an example when in landscape mode:

Fixed by e654e10, will go out in the next minor release.


Changes required to allow successful execution of tap-postgres.

Changing type passed to parent in metrics/file to self.
Adding string version of linefeed instead of binary to fix issue with writing metrics.
Catching exception that can occur when state file is empty of not present in state/file.  Note this required an upgrade of smart-open in order to catch both cases.

Here's the config I used (based on this but with changes to tap).
tap_command: /home/rob/python-virtual-env/tap-postgres/bin/tap-postgres
tap_config_path: /home/rob/tap-postgres-config.json
tap_catalog_path: /home/rob/tap-postgres-properties.json
tap_state:
  type: file
  options:
    - s3://rob-singer-runner/taps/postgres_state.json
metrics:
  type: file
  options:
    - s3://rob-singer-runner/taps/postgres_metrics_last_run.json
pipe:
  type: file
  options:
    - s3://rob-singer-runner/taps/postgres_stream_last_run.json
    - w

@robmoore This looks good! Just one suggestion


forge(fix): dont give out error if artifact has no source on script

Motivation
If the artifact for whatever reason has no source (it should), we don't want to exit, because they're only necessary for the debugger.

Solution

also does this indicate that something's wrong the the artifacts or is this script related?
Given that source_file() returns an Option, I am assuming that there is a situation where artifacts have no source... But I don't know which tbh

We can add a warn! if it doesn't find one?

Is this related to the guy on Telegram that was getting "source not found"?
This makes sense - but worth us understanding why they got that error in the first place?

just a hunch but None is only returned if there's no id present in the Configurable artifacts, we only added this ~1-2 weeks ago so perhaps they updated forge build ran with old artifacts
https://github.com/gakonst/ethers-rs/blob/master/ethers-solc/src/artifact_output/configurable.rs#L87
I think should be ok to merge, but let's add a warn! trace to the else branch

Is this related to the guy on Telegram that was getting "source not found"?
This makes sense - but worth us understanding why they got that error in the first place?

The error I got was because the path I was using to get the artifacts was not correct. When changed to use path from project root, it worked fine.


[Backend Develpoment Python]: Flask Route

Description
Description
Routing  can be easily done using Flask which is micro-framework of Python.
Document / Video of  how routing can be done using Flask
Domain
Backend Dev (Python)
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

I would like to work on this.
/assign

/assign


add rpc-bootnode-1 bootnode to kusama

Current dependencies on/for this PR:

main

PR #121   👈

This stack of pull requests is managed by Graphite.


ACTION_ADVANCE etc. constants should be public

I am referring to these
Is there a reason they are not public? As it is now, we need to compare the action with strings, which isn't ideal for maintenance and refactoring.

They certainly could be, I don't see a problem with that. Happy to review a PR.


vulkano-shaders: Using #[derive(VulkanoShader)] with geometry shaders gives compile errors

When I tried to compile this code:
mod color_gs {
    #[derive(VulkanoShader)]
    #[ty = "geometry"]
    #[path = "assets/color.geom"]
    struct _Dummy;
}

I got this compile time error:
error[E0061]: this function takes 5 parameters but 4 parameters were supplied
   --> src\main.rs:571:14
    |
571 |     #[derive(VulkanoShader)]
    |              ^^^^^^^^^^^^^ expected 5 parameters

error: aborting due to previous error(s)

It's due to lack of argument with input primitive enum, which has to be passed to ShaderModule::geometry_shader_entry_point method.


Fixing unit tests related to events

Fixed unit tests in 'test_events'
Fixed unit tests in 'test_displayFreetime'
Fixed unit tests in 'test_shared_functions'
Minor changes to the str method in the Event class to cater above fixes.
Minor style fixes in test files.

Looks good to me. Thank you for doing this.

Looks good!


attempt to fix random tests::wantlist_cancellation errors

My suspects are either the enabled tracing_subscriber or the lock over SubscriptionRegistry taken in get_subscriptions; I've adjusted those and tightened the test's deadlines and wasn't able to trigger the issue while stress-testing. It might not suffice yet, but those changes won't hurt.

The Clone impl is not a restriction, is just an extra implementation available when the generics in Subscription implement Clone and I'd still enjoy that extra impl for future test purposes. I'll try to reproduce the issue some more using ASYNC_STD_THREAD_COUNT=1.

I suppose most of this PR is obviated by https://github.com/rs-ipfs/rust-ipfs/pull/299; I'd just salvage the impl<T: Clone, E: Clone> Clone for Subscription<T, E>, as it has been pretty useful in tests before.

the failure was connect_two_nodes_by_peer_id; unrelated

It's mostly for tests, where one could get a single subscription and inspect it without having to keep the Subscriptions lock open.
The test failure is unrelated, hence:
bors retry


Add support for Ember FastBoot

As per http://www.ember-fastboot.com/docs/addon-author-guide

Thanks @oskarrough!


Support python mirror

Download speed is very slow when installing, hoping to support the mirror image.
https://npm.taobao.org/mirrors/python/

I spent a whole night to install, but only download 30%
Estimated that the vast majority of Chinese users will encounter the same problem.
So, I push a PR #41 to support to download python from mirror.


[REQ] Handle secure registries

What kind of request is this?
New feature
What is your request or suggestion?
Handle secure registries in copa:

if image exists locally already, skip pulling the image
if pulling image, handle authentication: copa will need to know how to use the auth file locally to authenticate with the registry)

Does it not already handle this?
https://github.com/project-copacetic/copacetic/blob/fe06e35d19a24c66b95035e6b6faa2636cf5c2b5/pkg/buildkit/buildkit.go#L72-L82


Warning: NullBooleanField is deprecated in Django 3.1

Issue Summary
NullBooleanField is deprecated in Django 3.1. Running any manage.py command throughs a non-critical warning.
WARNINGS:
catalogue.ProductAttributeValue.value_boolean: (fields.W903) NullBooleanField is deprecated. Support for it (except in historical migrations) will be removed in Django 4.0.
	HINT: Use BooleanField(null=True) instead.

Suggested solution
The fix seems pretty straightforward
https://github.com/django-oscar/django-oscar/blob/master/src/oscar/apps/catalogue/abstract_models.py#L1043
-    value_boolean = models.NullBooleanField(_('Boolean'), blank=True, db_index=True)
+   value_boolean = models.BooleanField(_('Boolean'), blank=True, null=True, db_index=True)

But I am not sure of the impact to the migrations, etc. In my limited testing I have not yet been able to override and test this.
Technical details

Python version: Python 3.9.1
Django version: Version: 3.1.6
Oscar version: Version: 3.0

Hey @solarissmoke - just wondering if this has been included in an official release yet? I notice the new migration isn't in the repository for versions 3.0.1 and 3.0.2 and the non-critical warning still appears.
https://github.com/django-oscar/django-oscar/tree/3.0.2/src/oscar/apps/catalogue/migrations

Python 3.8.5
Django 3.1.9
Oscar 3.0.2

@ml394 it's part of 3.1 which is currently in beta.


Log Naming Conventions - Matrix Backend

Purpose
Currently, following the Application Factory Pattern we have developed Matrix Systems utilizing Blueprints. This allows us for each module contained in a respective blueprint to create logger instances which gives us the capability to provide context to any message send to our out.log file.
Due to the growth of the project our original naming convention (using the module) name has now lost context due to various modules contained in respective Blueprints having the same name. To solve this issue we should incorporate the Package Name as well as the Module Name within our logger instances.
End Behavior
As a Developer viewing the respective out.log files for my running instance of Matrix Systems. Each log message should contain the Package Name and Module Name for each respective message.

This work has been completed on 27/log-naming-conventions and is ready to be merged into develop.

Work has been merged into develop.


Schema generated against d8ccf4c169d03909a7a7a9be2bbe9afea0ad3a9f of pulumi-terraform-bridge

Sample schema generated without docs matching hack. Based on bridge @ d8ccf4c.

I have spot checked this PR. Generally it looks good!  I've found some description dropout but so far it looks like it's removing nonsensical descriptions so it is a net win.
aws.Lambda
> $schema Diff resources aws:lambda/function:Function
properties:
    arn:
        description:
            text: |+
                - Amazon Resource Name (ARN) of the Amazon EFS Access Point that provides access to the file system.
                + Amazon Resource Name (ARN) identifying your Lambda Function.

stateInputs:
    properties:
        arn:
            description:
                text: |+
                    - Amazon Resource Name (ARN) of the Amazon EFS Access Point that provides access to the file system.
                    + Amazon Resource Name (ARN) identifying your Lambda Function.

This is great --^ make AWS lambda page great again.
msk.Cluster
> $schema Diff resources aws:msk/cluster:Cluster
properties:
    arn:
        description:
            text: |+
                - Amazon Resource Name (ARN) of the MSK Configuration to use in the cluster.
                + Amazon Resource Name (ARN) of the MSK cluster.

stateInputs:
    properties:
        arn:
            description:
                text: |+
                    - Amazon Resource Name (ARN) of the MSK Configuration to use in the cluster.
                    + Amazon Resource Name (ARN) of the MSK cluster.

acm.Certificate
This one ended up losing descriptions entirely but it's much better than publishing nonsense. Can iterate from here.
> $schema Diff resources aws:acm/certificate:Certificate inputProperties
certificateAuthorityArn:
    description:
        rm:
            text: |
                ARN of an ACM PCA
certificateBody:
    description:
        rm:
            text: |
                Certificate's PEM-formatted public key
certificateChain:
    description:
        rm:
            text: |
                Certificate's PEM-formatted chain
                * Creating a private CA issued certificate
earlyRenewalDuration:
    description:
        rm:
            text: |
                Amount of time to start automatic renewal process before expiration.
                Has no effect if less than 60 days.
                Represented by either
                a subset of [RFC 3339 duration](https://www.rfc-editor.org/rfc/rfc3339) supporting years, months, and days (e.g....
                or a string such as `2160h`.

sagemaker.Model
This looks good:
> $schema Diff resources   aws:sagemaker/model:Model
inputProperties:
    tags:
        description:
            text: "\n- \n- The `primary_container` and `container` block both support:\n\n"
properties:
    tags:
        description:
            text: "\n- \n- The `primary_container` and `container` block both support:\n\n"
stateInputs:
    properties:
        tags:
            description:
                text: "\n- \n- The `primary_container` and `container` block both support:\n\n"

Closing as shipped via https://github.com/pulumi/pulumi-terraform-bridge/pull/1882. Next bridge release will pull this in.


replace coda with mina

Things I don't know if I should change or not:
https://github.com/MinaProtocol/mina/blob/022cbaaefa9b9b8a3e1464261c07f5f0104eaeb5/src/lib/hash_prefixes/hash_prefixes.ml#L23
https://github.com/MinaProtocol/mina/blob/022cbaaefa9b9b8a3e1464261c07f5f0104eaeb5/src/lib/gossip_net/libp2p.ml#L49
https://github.com/MinaProtocol/mina/blob/022cbaaefa9b9b8a3e1464261c07f5f0104eaeb5/src/lib/gossip_net/libp2p.ml#L325
Close #7762

I think src/lib/ppx_coda can be changed to ppx_mina, and then change all the dune files to use that (sed is helpful for that).

I think src/lib/ppx_coda can be changed to ppx_mina, and then change all the dune files to use that (sed is helpful for that).

And also change scripts/require-ppxs.py.


Added configuration setup to mapbox

Added configuration setup to make it clear that you should set up the public_token in services config.
I have seen some users having a hard time configuring API token for component. Not knowing how it should be configured. So thought of adding this part to mapbox component to make things clear.

Thanks!


Started to get a lot of crashes when looking up travel details

I managed to get the following stacktrace out of my phone:
02-24 11:16:43.960 E/AndroidRuntime(19198): FATAL EXCEPTION: main
02-24 11:16:43.960 E/AndroidRuntime(19198): Process: com.markupartist.sthlmtraveling, PID: 19198
02-24 11:16:43.960 E/AndroidRuntime(19198): java.lang.NullPointerException: Attempt to invoke virtual method 'int android.graphics.Bitmap.getWidth()' on a null object reference
02-24 11:16:43.960 E/AndroidRuntime(19198): 	at com.android.webview.chromium.Ap.getDefaultVideoPoster(WebViewContentsClientAdapter.java:578)
02-24 11:16:43.960 E/AndroidRuntime(19198): 	at org.chromium.android_webview.DefaultVideoPosterRequestHandler$$Lambda$0.run(Unknown Source:2)
02-24 11:16:43.960 E/AndroidRuntime(19198): 	at android.os.Handler.handleCallback(Handler.java:789)
02-24 11:16:43.960 E/AndroidRuntime(19198): 	at android.os.Handler.dispatchMessage(Handler.java:98)
02-24 11:16:43.960 E/AndroidRuntime(19198): 	at android.os.Looper.loop(Looper.java:164)
02-24 11:16:43.960 E/AndroidRuntime(19198): 	at android.app.ActivityThread.main(ActivityThread.java:6809)
02-24 11:16:43.960 E/AndroidRuntime(19198): 	at java.lang.reflect.Method.invoke(Native Method)
02-24 11:16:43.960 E/AndroidRuntime(19198): 	at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
02-24 11:16:43.960 E/AndroidRuntime(19198): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)
02-24 11:16:43.970<EMAIL_ADDRESS> 760): ProcessIbsCmd: Received IBS_SLEEP_IND: 0xFE
02-24 11:16:43.970<EMAIL_ADDRESS> 760): SerialClockVote: vote for UART CLK OFF
02-24 11:16:43.971 I/MediaCodec(19198): name: video/avc```

It seems to happen when the app is trying to show an ad.

It seems to have been related to a certain ad, since I only happened for a few minutes.
I am unable to recreated it now when I am trying to record the steps taken using vysor.

Thanks for the report. This crash is related to a bug in the library used for showing ads. It requires an update of the library to be resolved. I thought I blocked the ads that caused this, but apparently not. I've added additional filters on the ad backend but will roll out an update with the potential fix as well.
If this crash is still happening it's possible to turn off the ads through settings.
Thanks.

There's a new version rolling out now where the dependencies has been updated. This will hopefully resolve the issue. Thanks again for the stack!


Improve Algolia search

i did this all on the github online editor, doubtful it actually works

Whenever you deploy to a branch netfliy makes a preview branch. its pretty cool.
But, this calls gatsby build. gatsby build indexes the pages and sends to algolia. this slows down the build, but also uses up algolia operations.
So now, it only does the algolia indexing whenever it merges into master. That should save us some operations.