Update quickstart image version

containerssh releases v0.5.0 - jan 7, 2024
(https://github.com/ContainerSSH/ContainerSSH/releases/tag/v0.5.0)
update quickstart
docker yaml update / 0.4.1 -> v0.5.0
kubernetes yaml update / 0.4 -> v0.5.0
Please give a brief description of the change
quickstart example yaml file edit docker image version for releases v0.5.0

...
Are you the owner of the code or do you have permission of the owner?
yes
...
The code will be published under the MIT-0 license. Have you read and understood this license?
yes
...

it again later


fix(host): arm node failed get numa architecture use ghw lib

What this PR does / why we need it:

Does this PR need to be backport to the previous release branch?:
release/3.10

WARNING: failed to determine memory area for node: open /sys/devices/system/memory/block_size_bytes: no such file or directory
https://github.com/kata-containers/runtime/issues/796#issuecomment-425393743


Invisisble enemies

WIth a modpack i use sometimes at stage start(seemingly only stage 2 onward) enemies slowly start spawning invisible until every enemy is invis. when this starts happening it spams the below in console
[Error  : Unity Log] NullReferenceException: Object reference not set to an instance of an object Stack trace: (wrapper dynamic-method) RoR2.CharacterModel.DMD<RoR2.CharacterModel::UpdateMaterials>(RoR2.CharacterModel) (wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition.Trampoline<RoR2.CharacterModel::UpdateMaterials>?-1670684980(RoR2.CharacterModel) MysticsItems.Buffs.DasherDiscActive.CharacterModel_UpdateMaterials (On.RoR2.CharacterModel+orig_UpdateMaterials orig, RoR2.CharacterModel self) (at <e2fb81f04412435693c5b5c1bf94e5ab>:IL_0037) (wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition.Hook<RoR2.CharacterModel::UpdateMaterials>?1673049240(RoR2.CharacterModel) RoR2.CharacterModel.UpdateForCamera (RoR2.CameraRigController cameraRigController) (at <a149dbd7438a4e73b97d6600b3a2bbd4>:IL_014E) RoR2.CharacterModel.OnSceneCameraPreRender (RoR2.SceneCamera sceneCamera) (at <a149dbd7438a4e73b97d6600b3a2bbd4>:IL_003F) RoR2.SceneCamera.OnPreRender () (at <a149dbd7438a4e73b97d6600b3a2bbd4>:IL_0017)
the profile i use is 019216c6-e324-e3f6-cdac-c8d1bcbcd7f6 if you want to verify anything that could cause it incompatibility wise(i dont think so considering it also happened with a barebones version of the pack and i dont thing faster scrapper minimap etc could cause it)
here is the log output file(trimmed out 55 mb of that one error being spammed can upload full log if needed)
LogOutput.log

does this still happen with all updated mods


Invisible Prompt / Directory Upon Terminal Launch

VSCode Version:
Version: 1.39.2 (user setup)
Commit: 6ab598523be7a800d7f3eb4d92d7ab9a66069390
Date: 2019-10-15T15:35:18.241Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17763

OS Version:
Windows 10 Home
Version 1809
OS Build 17763.805

Steps to Reproduce:

open vsc (by any method)
open the terminal

Does this issue occur when all extensions are disabled?: Yes
This is the exact same issue as #57803 and #61172 which was supposedly resolved.

UPDATE: changing the shell to bash instead of powershell seems to be a fix.

The duplicate issue you linked tells you what the problem is https://github.com/microsoft/vscode/issues/57803#issuecomment-449495423


Reduce Tech Debt and bring up to HQRM standards - Fixes #28

The purpose of the PR is to reduce the significant technical debt of this resource. This is so that new features can be added to the resource safely (#25, #26, #27).
The logic of the module is mostly unchanged, but about 60% of the lines of code had one or more guidelines violations which needed to be fixed.
The PR focuses mainly on:

Improving code quality
Upgrading code to meet standards (include HQRM)
Completing unit and integration tests
Fixing bugs (the xCertReq resource could not work at all in most environments in the current state).

The details of the PR are:

Moved unit tests to correct folder structure.
Changed unit tests to use standard test templates.
Updated all resources to meet HQRM standards and style guidelines.
Added .gitignore file
Added .gitattributes file to force line endings to CRLF to allow unit tests to work.
xCertificateCommon:

Moved common code into new module MSFT_xCertificateCommon.
Added standard exception code.
Renamed common functions Validate-* to use acceptable verb Test-*.

xCertificateImport:

Fixed bug with Test-TargetResource incorrectly detecting change required.
Reworked unit tests for improved code coverage to meet HQRM standards.
Created Integration tests for both importing and removing an imported certificate.
Added descriptions to MOF file.
Removed default parameter values for parameters that are required or keys.
Added verbose messages.
Split message and error strings into localization string files.

xPfxImport:

Fixed bug with Test-TargetResource incorrectly detecting change required.
Reworked unit tests for improved code coverage to meet HQRM standards.
Created Integration tests for both importing and removing an imported certificate.
Added descriptions to MOF file.
Removed default parameter values for parameters that are required or keys.
Added verbose messages.
Split message and error strings into localization string files.

xCertReq:

Cleaned up descriptions in MOF file.
Fixed bugs generating certificate when credentials are specified.
Allowed output of certificate request when credentials are specified.
Split message and error strings into localization string files.
Created unit tests and integration tests.
Improved logging output to enable easier debugging.

xPDT:

Renamed to match standard module name format (MSFT_x).
Modified to meet 100 characters or less line length where possible.
Split message and error strings into localization string files.

The only element that does not have unit test coverage is the MSFT_xPDT support module. This should be added when possible.
I apologize for the size of this change but it was the only way I could feel confident that the module was mostly free of tech debt (except for the missing unit tests on the xPDT support module).
The features and fixes in #25, #26 and #27 will begin to be submitted once this PR has moved through.

This change is

Hi @PlagueHO, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

@kwirkykat - do you know if anyone is actively managing this resource module over there at MSFT? Looks like it hasn't been active for a while.

Reviewed 3 of 39 files at r3.
Review status: 3 of 36 files reviewed at latest revision, 18 unresolved discussions.

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 61 [r3] (raw file):

    Process
    {
        foreach ($p in $Path)

Please rename $p to something more descriptive (e.g. $singlePath, $individualPath, $certificatePath, etc.)

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 110 [r3] (raw file):

{
    [CmdletBinding()]
    param(

Parenthesis should be on next line

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 127 [r3] (raw file):

    {
        # Get a list of all Valid Hash types and lengths into an array
        $validHashes = [System.AppDomain]::CurrentDomain.GetAssemblies().GetTypes() |

As part of our new Best Practices document, we are asking that there only be at most one pipe in one line.
This is completely valid PowerShell, but to make the code easier to read/understand, can you please split these operations using variable assignment so that there is at most one pipe in one logical line of code?

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 173 [r3] (raw file):

} # end function Test-Thumbprint

function ThrowInvalidOperationError

Please update this function name to follow the Verb-Noun format with an approved PowerShell verb (e.g. New-InvalidOperationError)
Also, please add a help comment above this function.

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 190 [r3] (raw file):

    $exception = New-Object -TypeName System.InvalidOperationException `
        -ArgumentList $ErrorMessage;

Please remove the semicolons at the end of the lines of this function

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 197 [r3] (raw file):

} # end function ThrowInvalidOperationError

function ThrowInvalidArgumentError

Please update this function name to follow the Verb-Noun format with an approved PowerShell verb (e.g. New-InvalidArgumentError)
Also, please add a help comment above this function.

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 214 [r3] (raw file):

    $exception = New-Object -TypeName System.ArgumentException `
        -ArgumentList $ErrorMessage;

Please remove the semicolons at the end of the lines of this function

Comments from Reviewable

Reviewed 2 of 39 files at r3.
Review status: 5 of 36 files reviewed at latest revision, 22 unresolved discussions.

DSCResources/MSFT_xCertificateImport/MSFT_xCertificateImport.psm1, line 32 [r3] (raw file):

    param(
        [Parameter(Mandatory)]
        [ValidateScript( { $_ | Test-Thumbprint } )]

Where is the Test-Thumbprint function?

DSCResources/MSFT_xCertificateImport/MSFT_xCertificateImport.psm1, line 37 [r3] (raw file):

        [Parameter(Mandatory)]
        [ValidateScript( { $_ | Test-CertificatePath } )]

Where is the Test-CertificatePath function?

DSCResources/MSFT_xCertificateImport/MSFT_xCertificateImport.psm1, line 68 [r3] (raw file):

    if ((Test-Path $CertificateStore) -eq $false)
    {
        ThrowInvalidArgumentError `

Where is ThrowInvalidArgumentError defined for this file?

DSCResources/MSFT_xCertificateImport/en-us/MSFT_xCertificateImport.strings.psd1, line 10 [r3] (raw file):

CertificateStoreNotFoundError=Certificate Store '{0}' not found.

ImportingCertificateShould=Importing certificate '{0}' into '{1}'

There should be one space on each side of the '='.
Also, can you please indent the text inside the here-string once (@' ... '@)?

Comments from Reviewable

Thanks for the great review @kwirkykat - sorry about all the mistakes. I made all the changes to this module before your other feed back on my other HQRM submitted modules so hadn't learned from those mistakes yet. I've now completed a whole lot more changes on this resource based on the comments you and the others made on my other PR's. Hopefully there won't be too many more mistakes.
It probably would have been easier and quicker to rewrite this resource from scratch. :cry:
There was also a lot of unused code in the xPDT module (I've no idea where this module came from but it must have been harvested from somewhere else). I've removed the unused code as I didn't see the point in documenting a bunch of functions that weren't being used (like NetUse - can't figure out why this was even included ever???).
Also, as we are doing all this work making this resource meet all the HQRM guidelines, is it worth renaming all the components be HQRM naming (e.g. CertificateDsc)? Or should we wait?
BTW, awesome job on open sourcing PS and getting it on Linux!
I'm done - have a great weekend!

Review status: 5 of 36 files reviewed at latest revision, 22 unresolved discussions, some commit checks failed.

ReadMe.md, line 110 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> If Examples is now a 2-hash header, this should become a 3-hash header (###)

Done.

ReadMe.md, line 117 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Parenthesis should be on next line

Done.

ReadMe.md, line 121 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> This parenthesis has one extra indent

Done.

ReadMe.md, line 153 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> If Examples is now a 2-hash header, this should become a 3-hash header (###)

Done.

ReadMe.md, line 155 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> If Examples is now a 2-hash header, this should become a 4-hash header (####)

Done.

ReadMe.md, line 160 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Parenthesis should be on next line

Done.

ReadMe.md, line 185 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> If Examples is now a 2-hash header, this should become a 4-hash header (####)

Done.

ReadMe.md, line 190 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Parenthesis should be on next line

Done.

ReadMe.md, line 239 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> If Examples is now a 2-hash header, this should become a 3-hash header (###)

Done.

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 46 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Parenthesis should be on next line

Done.

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 50 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> This Parameter Attribute should all be on one line.

Done.

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 61 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Please rename $p to something more descriptive (e.g. $singlePath, $individualPath, $certificatePath, etc.)

Done.

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 110 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Parenthesis should be on next line

Done.

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 127 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> As part of our new [Best Practices document](https://github.com/PowerShell/DscResources/blob/master/BestPractices.md#use-variables-rather-than-extensive-piping), we are asking that there only be at most one pipe in one line.
> This is completely valid PowerShell, but to make the code easier to read/understand, can you please split these operations using variable assignment so that there is at most one pipe in one logical line of code?

Sounds like a pretty good practice to me. I'll remember it for next time :smile:  I've reworked this code so that it should be a lot easier to understand (hopefully).

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 173 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Please update this function name to follow the Verb-Noun format with an approved PowerShell verb (e.g. New-InvalidOperationError)
>
> Also, please add a help comment above this function.

Done.

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 190 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Please remove the semicolons at the end of the lines of this function

Done.

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 197 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Please update this function name to follow the Verb-Noun format with an approved PowerShell verb (e.g. New-InvalidArgumentError)
>
> Also, please add a help comment above this function.

Done.

DSCResources/MSFT_xCertificateCommon/MSFT_xCertificateCommon.psm1, line 214 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Please remove the semicolons at the end of the lines of this function

Done.

DSCResources/MSFT_xCertificateImport/MSFT_xCertificateImport.psm1, line 32 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Where is the Test-Thumbprint function?

It's in the MSFT_xCertificateCommon module. All other modules import this module.

DSCResources/MSFT_xCertificateImport/MSFT_xCertificateImport.psm1, line 37 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Where is the Test-CertificatePath function?

It's in the MSFT_xCertificateCommon module. All other modules import this module.

DSCResources/MSFT_xCertificateImport/MSFT_xCertificateImport.psm1, line 68 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Where is ThrowInvalidArgumentError defined for this file?

It's in the MSFT_xCertificateCommon module. All other modules import this module.

DSCResources/MSFT_xCertificateImport/en-us/MSFT_xCertificateImport.strings.psd1, line 10 [r3] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> There should be one space on each side of the '='.
> Also, can you please indent the text inside the here-string once (@' ... '@)?

Fixed (in all other files too). Sorry about that.

Comments from Reviewable

Hi @KwirkyKat - Is there anything you're waiting on from me for this one? My team would like to add some new resources and features to this repo (as per issues raised) but we're waiting for this PR to go through. No pressure :smile:

Review status: 5 of 36 files reviewed at latest revision, 22 unresolved discussions.

Comments from Reviewable

@PlagueHO The MSFT_xCertificateCommon.psm1 module is not a resource, so it shouldn't follow the resource naming format. Can you rename this module to just CertificateCommon.psm1 or CommonResourceHelper.psm1 or something along those lines without the MSFT_x at the beginning?
Same thing goes for the xPDT module (even though that was mis-named before this PR). Since you're "renaming" it anyway, can you please change the name to just PDT.psm1 or somthing similar without the MSFT_x at the beginning since it is not a resource module? By the way, what does PDT stand for here?
There's also a lot of function help comments that aren't indented properly, but I won't hold such a large PR for just that.
That's it. Just the module renames and one place where you probably need to nullify the output and then this is good to go.
I don't see any obvious breaking changes here. Is there anything in this PR you would consider to be a breaking change?

Reviewed 8 of 39 files at r3, 14 of 25 files at r4, 1 of 4 files at r5, 1 of 2 files at r6, 1 of 1 files at r7.
Review status: 28 of 36 files reviewed at latest revision, 6 unresolved discussions.

DSCResources/MSFT_xCertReq/MSFT_xCertReq.psm1, line 28 [r7] (raw file):

<#
    .SYNOPSIS
    Returns the current state of the certificate that may need to be requested.

Need an extra indent for everything under the help attributes

DSCResources/MSFT_xCertReq/MSFT_xCertReq.psm1, line 110 [r7] (raw file):

<#
    .SYNOPSIS
    Requests a new certificate based on the parameters provided.

Need an extra indent for everything under the help attributes

DSCResources/MSFT_xCertReq/MSFT_xCertReq.psm1, line 280 [r7] (raw file):

            # a timing issue in MSFT_xPDT (the process has often completed before the
            # process can be read in).
            Start-Win32Process `

Can you add a $null = at the beginning of this line in case it does happen to have output?

DSCResources/MSFT_xCertReq/MSFT_xCertReq.psm1, line 355 [r7] (raw file):

<#
    .SYNOPSIS
    Tests if a new certificate should be requested.

Need an extra indent for everything under the help attributes

DSCResources/MSFT_xPDT/MSFT_xPDT.psm1, line 26 [r7] (raw file):

<#
    .SYNOPSIS
    Extracts an array of arguments that were found in the Arguments list passed in.

Need an extra indent for everything under the help attributes

Examples/Sample_xPfxImport_IIS_WebSite.ps1, line 6 [r7] (raw file):

[PSCredential] $PfxPassword
[PSCredential] should be on its own line

Comments from Reviewable

Awesome! Thank you @KwirkyKat.
I've renamed the MSFT_xPDT and xCertificateCommon to PDT and CertificateCommon respectively and moved them up into the DSCResources folder (no need for their own folders).
As for the name PDT: I have no idea either what it means to be honest - I know it back to front now but couldn't figure out what it meant. I'm assuming the P means either Process or PInvoke. I think @mgreenegit wrote it so he could probably tell us? :smile:
I've fixed the function help comment indent and spacing too because I want to make sure everything is as close to the guidelines as possible, but I must have missed those. Thanks for pointing them out.
I also quickly changed the Parameter definition layout in the Readme.md to show make the Key/Required/Write more visible (adopting the same layout I tend to use now).
One final thing I did was remove the DSCResourceDesigner_CreateScript.ps1 out of the examples folder as I don't think it is helpful and doesn't actually work and is also no longer matches the current module structure.

Review status: 28 of 36 files reviewed at latest revision, 6 unresolved discussions.

DSCResources/MSFT_xCertReq/MSFT_xCertReq.psm1, line 28 [r7] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Need an extra indent for everything under the help attributes

Done.

DSCResources/MSFT_xCertReq/MSFT_xCertReq.psm1, line 110 [r7] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Need an extra indent for everything under the help attributes

Done.

DSCResources/MSFT_xCertReq/MSFT_xCertReq.psm1, line 280 [r7] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Can you add a $null = at the beginning of this line in case it does happen to have output?

Good thinking. Done. Also did the same for Wait-Win32ProcessEnd a few lines further on.

DSCResources/MSFT_xCertReq/MSFT_xCertReq.psm1, line 355 [r7] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Need an extra indent for everything under the help attributes

Done.

DSCResources/MSFT_xPDT/MSFT_xPDT.psm1, line 26 [r7] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> Need an extra indent for everything under the help attributes

Done.

Examples/Sample_xPfxImport_IIS_WebSite.ps1, line 6 [r7] (raw file):
Previously, kwirkykat (Katie Keim) wrote…
> > [PSCredential] $PfxPassword
> [PSCredential] should be on its own line

Done. And in the other Example and in the Readme.md

Comments from Reviewable

I've moved PDT and CertificateCommon modules back into their own folders (within DSCResources) because it then enables the standard unit test templates to test them.

Review status: 28 of 36 files reviewed at latest revision, 6 unresolved discussions.

Comments from Reviewable

Reviewed 2 of 44 files at r3, 17 of 17 files at r8.
Review status: all files reviewed at latest revision, 7 unresolved discussions.

DSCResources/MSFT_xCertReq/MSFT_xCertReq.psm1, line 282 at r8 (raw file):

$ENV:SystemRoot\System32\WindowsPowerShell\v1.0

Use $PSHOME instead

Examples/Sample_xPfxImport_MinimalUsage.ps1, line 26 at r8 (raw file):

Start-DscConfiguration -Wait -Force -Verbose -Path 'c:\Sample_xPfxImport_MinimalUsage'

# Validate results

Add a comment of what the output of this command should be

Comments from Reviewable

Added 2 minor comments. Other than that it looks OK.

Thanks @narrieta ! I really appreciate you reviewing this (and the other reviewers in the DSC team). I've covered off the changes.

Review status: 34 of 36 files reviewed at latest revision, 8 unresolved discussions.

DSCResources/MSFT_xCertReq/MSFT_xCertReq.psm1, line 282 at r8 (raw file):
Previously, narrieta (Norberto Arrieta) wrote…
> > $ENV:SystemRoot\System32\WindowsPowerShell\v1.0
>
> Use $PSHOME instead

Done.

Examples/Sample_xPfxImport_MinimalUsage.ps1, line 26 at r8 (raw file):
Previously, narrieta (Norberto Arrieta) wrote…
> Add a comment of what the output of this command should be

I added the comment but I also updated the example so that it was actually easier to use (by parameterizing the variables in the config). I also improved the test so that it would only return the thumbprint that should have been imported (makes it much easier if you have lots of certs on your test machine).

Comments from Reviewable

Reviewed 11 of 44 files at r3, 12 of 29 files at r4, 1 of 2 files at r6, 1 of 1 files at r7, 2 of 2 files at r9.
Review status: all files reviewed at latest revision, 5 unresolved discussions.

Comments from Reviewable

@PlagueHO Thank you for your contribution!


Add support for separate passphrase and encryption password for account creation (and decryption)

Issue
the api/wallet/create API method that takes WalletCreationRequest type, does currently not support separate passphrase and password for disk encryption.
The API Create method calls WalletManager.CreateWallet, which does support separation of passphrase and password. When passphrase is not supplied (which is it not in the API), the wallet manager will use the password for both mnemonic seed and disk encryption.
It would be nice to be able to have an advanced option to supply two different secrets to the wallet creation and decrypt methods.
Why support this?
Separating the two values, would allow API consumers to have wallets without mnemonic seeds (e.g. "" according to the standard). It is currently required to supply this value.
If the two values are separate, it would be possible to have a HD seed that consists of only the 12-word mnemonic, but still have a password to unlock the wallet. This would make disk storage secure with the password, but the HD seed wouldn't require a password.
This could be useful for scenarios with paper wallets, without having password.
Additionally it would be possible to have a much less secure wallet decrypt password, and a much better mnemonic seed extension. If someone keeps their computer safe, they could have a much simpler password for every day usage, but if they want to restore their accounts on a different device, they could then supply a more secure password.
It could even be possible to store the wallet password in secure storage on the device (with an auto-generated password, instead of user-provided), for example DPAPI on Windows and allow users to have a "remember me" capability.

I agree 100% and this is something we've talked about a lot.
The first step would be to separate the passphrase from the password.
To do that you can:

add a passphrase field where required, from wallet creation request objects (WalletCreationRequest and WalletRecoveryRequest) to the WalletController to the WalletManager
if there's no passphrase, use only the mnemonic to create the private key and use the password to encrypt it
if there's a passphrase, use it with the mnemonic to create the private key and use the password to encrypt it

@sondreb Do you know someone that think maybe they could do it? 👀

Closed with https://github.com/stratisproject/StratisBitcoinFullNode/pull/1914


Build: existsSync not found error

Help me please !!
In my github action, I am getting the error below when i am building.

node-version: 16.17.0
package manager: pnpm

I encountered the same issue while working locally, but I managed to fix it by changing the next.config.js file to next.config.mjs. However, my GitHub Action keeps failing. Does anyone know how to fix this bug?
documentation:build: unhandledRejection file:///home/runner/work/min5407-library/min5407-library/node_modules/.pnpm/nextra@2.4.1_ivamjty3az7dj3hhadhjniqtwe/node_modules/nextra/dist/file-system.mjs:2
documentation:build: import { findPagesDir, existsSync } from "next/dist/lib/find-pages-dir.js";
documentation:build:                        ^^^^^^^^^^
documentation:build: SyntaxError: Named export 'existsSync' not found. The requested module 'next/dist/lib/find-pages-dir.js' is a CommonJS module, which may not support all module.exports as named exports.
documentation:build: CommonJS modules can always be imported via the default export, for example using:
documentation:build:
documentation:build: import pkg from 'next/dist/lib/find-pages-dir.js';
documentation:build: const { findPagesDir, existsSync } = pkg;
documentation:build:
documentation:build:     at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
documentation:build:  ELIFECYCLE  Command failed with exit code 1.
documentation:build: ERROR: command finished with error: command (/home/runner/work/min5407-library/min5407-library/apps/documentation) pnpm run build exited (1)
@min5407/utils:build:  ELIFECYCLE  Command failed.
command (/home/runner/work/min5407-library/min5407-library/apps/documentation) pnpm run build exited (1)
 ERROR  run failed: command  exited (1)

 Tasks:    0 successful, 2 total
Cached:    0 cached, 2 total
  Time:    7.[92](https://github.com/Min5407/min5407-library/actions/runs/4772961912/jobs/8485757755#step:6:93)3s

Also seeing this. Builds were working fine 19 hours ago, but now all failing.

Also seeing the same. Deploying to Vercel
Detected Next.js version: 13.3.1
--
14:04:08.302 | Running "yarn run build"
14:04:08.469 | $ next build
14:04:08.984 | info  - Linting and checking validity of types...
14:04:10.993 | info  - Creating an optimized production build...
14:04:11.897 | unhandledRejection file:///vercel/path0/node_modules/nextra/dist/file-system.mjs:2
14:04:11.897 | import { findPagesDir, existsSync } from "next/dist/lib/find-pages-dir.js";
14:04:11.897 | ^^^^^^^^^^
14:04:11.898 | SyntaxError: Named export 'existsSync' not found. The requested module 'next/dist/lib/find-pages-dir.js' is a CommonJS module, which may not support all module.exports as named exports.
14:04:11.898 | CommonJS modules can always be imported via the default export, for example using:
14:04:11.898 |
14:04:11.898 | import pkg from 'next/dist/lib/find-pages-dir.js';
14:04:11.898 | const { findPagesDir, existsSync } = pkg;
14:04:11.898 |
14:04:11.898 | at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
14:04:11.916 | error Command failed with exit code 1.

Same here npm i<EMAIL_ADDRESS>solved it for now

This issue isn't resolved yet. It was a workaround. Please reopen it

The exports object and named exports are unanalyzable after<EMAIL_ADDRESS>due to the limitation of https://github.com/nodejs/cjs-module-lexer.
https://www.diffchecker.com/3CguFwYr/

This still persists. Just cloned the project and can't even run the demo...

which project did you clone? please be more precise. Do you use Nextra 3?

It's exact same issue as was reflected in this ticket:
SyntaxError: Named export 'existsSync' not found. The requested module 'next/dist/lib/find-pages-dir.js' is a CommonJS module, which may not support all module.exports as named exports.
I cloned https://github.com/shuding/nextra-docs-template

this template is outdated, update Nextra/Next.js version

What is outdated exactly? Here is what the template provides:
{
  "name": "nextra-docs-template",
  "version": "0.0.1",
  "description": "Nextra docs template",
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/shuding/nextra-docs-template.git"
  },
  "author": "Shu Ding<EMAIL_ADDRESS>  "license": "MIT",
  "bugs": {
    "url": "https://github.com/shuding/nextra-docs-template/issues"
  },
  "homepage": "https://github.com/shuding/nextra-docs-template#readme",
  "dependencies": {
    "next": "^14.2.15",
    "nextra": "latest",
    "nextra-theme-docs": "latest",
    "react": "^18.2.0",
    "react-dom": "^18.2.0"
  },
  "devDependencies": {
    "@types/node": "18.11.10",
    "typescript": "^4.9.3"
  }
}


run node on linux hosts only

The windows/ovn setup runs both windows nodes and linux nodes
Prevent kubernetes/openshift from trying to run the node on
a windows host.
Signed-off-by: Phil Cameron<EMAIL_ADDRESS>

@squeed @dcbw @rajatchopra PTAL
This change came from Glenn West

@rajatchopra @dcbw PTAL

@rajatchopra
Can you explain how "openshift.io/node-selector" is useful here?

This is just openshift specific. Will not affect kubernetes.
The pods launched under this namespace will be fixed to linux hosts only. We want to prevent any scheduling to happen on windows (because we do not build images for windows yet). This will include objects that do not specify the nodeSelector in the resource definitions. e.g. DeploymentConfig (openshift only concept).


Assigned Plan Printout changes

assigned.pdf

Waiting for SQL View updates to apply changes to the print out.


Normalize Connection parameters for sync

This needs Core 13.12.0

Changing this to be merged to Core's 13.12.0 PR


[inconsistency] Restoring Gravity as main metric in KPI section

Hello Orbit team 👋
I’m prepping interviews with your team (very happy about the opportunity!), and on re-reading the model I got blocked on this one line in the KPI section. As far as I can tell the calculation formula really corresponds to Gravity calculation (as explained in Measuring gravity) and doesn’t describe Presence. Plus I feel it’s consistent with Gravity being the main community-level KPI too.
From a quick git history digging, it seems this commit restored Gravity instead of Presence in a number of sections, so maybe this line here in this table was just missed!
And if the current version is actually ok then I’m obviously happy to know more about what I’m missing 💡
Thanks for reading 🙌
Nico

Thanks @nicoallgood! Well spotted, it does look like that commit missed the line in the table. Appreciate the contribution 🙏


Fix version to 0.0.1

Set version to 0.0.1
JIRA ticket(s)

GOVAPP-473

No sonar in this one?

No, I figured there was little point since the modules are already tested, scanned etc and the actual integration should be minimal I think. Happy to add it if you'd prefer.


Install fails

Doesn't recognize the command: "./vcpkg install assimp"
Environment

OS: W10
Compiler: shell

To Reproduce
git clone https://github.com/Microsoft/vcpkg.git
cd vcpkg
./bootstrap-vcpkg.sh
./vcpkg integrate install
./vcpkg install assimp

regarding

Doesn't recognize the command: "./vcpkg install assimp"

could you show the errors it shows?
also make sure you have the dir vcpkg\ports\assimp\  with the contents

@greenozon Thanks for postint this issue, could you please provide the erro log?

I guess we should ask @Fabi12345   as issue originator!

I guess we should ask @Fabi12345 as issue originator!

Sorry for this. 😅

I don't know where the relevant log file is located, there is so many of them. I tried one more thing since this error occurred, installing from visual studio and then it automatically installed a few more packages, it didn't throw an error this time, so I think its fine now, but haven't checked yet.

@Fabi12345  the vcpkg will print the path to all logs files in the screen
just follow those andd then either drag-n-drop into your 1st post or add using Details  GH command (press / then select Details and copy-paste the log file contents) - in this case you'll see the ">" sign that will collapse/expand - very handy feature!

Doesn't recognize the command: "./vcpkg install assimp"

Note that / is the separator for POSIX paths. Windows tolerates it in some places, but cmd still wants to see \.

When I opened this issue I used the normal Windows shell (cmd), and that just said it doesn't recognize the command "./vcpkg install assimp", thats all. Then I tried in Visual Studio Developer Powershell and that worked successfully.


luci-theme-material: add missing css cbi-section-error definitions

Add the missing error css class definitions.
Highlights the wrong inputs detected by the cbi validation function.

@feckert could you please add the new ".cbi-progressbar" stuff as well? Currently the overview page is a bit empty with material theme ... ;-)

@dibdot I'll take care of it next week.

I think the material and rosy themes need way more changes. Off the top of my head they need CSS for the progress bars, the modal overlays and not sure if the tooltip bubbles need fixing too.

Merged, thanks!


refactor: improving request validation and client methods.

add a nil check to the Validate() method
replace int64 with int in client methods and schemas
replace bool with *bool in requests to allow null values
update Patch() method (client) to handle different body types and perform validation
improve null check in ListOptionsProvider
move client schemas to the model package
add helper functions etc.

Codecov Report
Attention: Patch coverage is 0% with 221 lines in your changes are missing coverage. Please review.

Project coverage is 2.49%. Comparing base (c025a0d) to head (d65c099).

Files
Patch %
Lines

crowdin/crowdin.go
0.00%
33 Missing :warning:

crowdin/model/translations.go
0.00%
29 Missing :warning:

crowdin/model/source_files.go
0.00%
19 Missing :warning:

crowdin/model/source_strings.go
0.00%
18 Missing :warning:

crowdin/projects.go
0.00%
15 Missing :warning:

crowdin/model/string_translations.go
0.00%
14 Missing :warning:

crowdin/model/errors.go
0.00%
13 Missing :warning:

crowdin/model/projects.go
0.00%
12 Missing :warning:

crowdin/model/branches.go
0.00%
9 Missing :warning:

crowdin/source_files.go
0.00%
9 Missing :warning:

... and 12 more

Additional details and impacted files
@@           Coverage Diff            @@
##            main     #14      +/-   ##
========================================
- Coverage   2.63%   2.49%   -0.14%
========================================
  Files         22      23       +1
  Lines        990    1046      +56
========================================
  Hits          26      26
- Misses       962    1018      +56
  Partials       2       2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


return value from img.SaveAs() on completion

Hi TheQwertiest,
Currently calling this function will save the image asynchronously, so the script continue its execution.
Would it be possible to know when the image have been saved succesfully in order to execute a code right after completion?

I just managed to find a turnaround which is good enough:
img.SaveAs(filepath, "image/jpeg");
var WshShell = new ActiveXObject("WScript.Shell");
var FileSyst = new oFileSystObject();
var check_fileExist = setInterval(function(filepath) {
	if(FileSyst.FileExists(filepath)) {
		window.ClearInterval(check_fileExist);
		//do someting
	}

},30,filepath);

So I close this ticket

Actually this turnaround isn't so perfect... because the FileExists method return true if the image is in the process of beeing saved but not completely finished. I could add a random delay, but I would prefer something more robust and clean
Do you have an idea there ?

This method should block until it's done plus it already returns a boolean to indicate success or failure.

I'm trying to open the image using an external application directly after calling SaveAs, and I've got errors. But it's very possible that the errors come from something else then. (from an issue with this external application)

Yep, I've been able to reproduce the issue out of foobar, ok thanks marc2k3, closed (again)


Regular .NET Still Supported?

Hi. It appears Dossier no longer supports regular .NET (correct me if I'm wrong). I tried updating my nuget and it failed. Is there an updated non-core version still available or have you dropped support for it?

Ah, that was definitely not intentional. I'll look at getting that fixed up today. Thanks for the heads up!

No problem! Thanks!


Int8-inference on Tensor Core

I tried quantized YOLOv3 on Volta GPU.
But, it didn't seem to be run on Tensor Core.
CUDNN documentation in 2.8.2 recommends to use "CUDNN_DATA_INT8x32 " for Tensor Core operations.
https://docs.nvidia.com/deeplearning/sdk/cudnn-developer-guide/index.html
I think CUDNN support only "CUDNN_DATA_INT8x32 " to run on Tensor Core for INT-8.
Is this correct?

Thank you for your reply.
I tried on Tesla V100. So, I will try on Xavier.
Should I change only CUDNN_DATA_INT8x4 into CUDNN_DATA_INT8x32?

@daniel89710
I added fix, update your code from GitHub, and un-comment these 2 lines:

https://github.com/AlexeyAB/yolo2_light/blob/1f270bf1c1c04dde3fbc779dd0ce90f85490301a/src/yolov2_forward_network_gpu.cu#L604
https://github.com/AlexeyAB/yolo2_light/blob/1f270bf1c1c04dde3fbc779dd0ce90f85490301a/src/additionally.c#L1787

So for layers with channels multiple of 32 will be used Tensor Cores (Xavier), for layers with channels multiple of 4 will be used DP4A (Pascal and higher).
Also check that you use cuDNN >= 7.2

@AlexeyAB
Thank you for quick update.
I will check.

Hi, @AlexeyAB
I tried your codes on Xavier after update code and un-comment 2 lines.
However, I got a failure at checkCUDNN (transform_status) in yolo2_foward_newtork_gpu.cu :L626.
Error: 3 - CUDNN_STATUS_BAD_PARAM.
Do  you have any ideas?

@daniel89710 Hi,
This is very similar to a bug in cuDNN.
I tried cuDNN 7.3.1 for CUDA 10 + CUDA10 + MSVS2015 on Windows 7 x64.
And I even can't create any descriptor for CUDNN_DATA_INT8x32. It always returns (desc_status==CUDNN_STATUS_BAD_PARAM).
cudnnTensorDescriptor_t desc;

cudnnCreateTensorDescriptor(&desc);

cudnnStatus_t desc_status =
 cudnnSetTensor4dDescriptor(desc, CUDNN_TENSOR_NCHW_VECT_C, CUDNN_DATA_INT8x32, 128, 128, 3, 3);

@daniel89710
Also what acceleration do you get by using -quantized flag with default CUDNN_DATA_INT8x4 (without CUDNN_DATA_INT8x32) on Xavier / Volta / Turing compared to FP32 calculation (without -quantized flag) ?
There is written that we should use INT8x32 only to accelerate inference, but there is not written that this is mandatory condition to use Tensor Cores. It seems both INT8x4 and INT8x32 will use Tensor Cores, but INT8x32 will be faster: https://docs.nvidia.com/deeplearning/sdk/cudnn-developer-guide/index.html#tensor-ops-speedup-tips

CUDNN_DATA_INT8x32 to accelerate your convolution computation

@AlexeyAB
Sorry for late.
I tried to use -quantized flag on Xavier and I got a little speed down compared with no -quantized flag.
I think we cannot still use Tensor core in the case of using -quantized flag.
I checked whether this ran on Tensor core or not using nvprof.
But, that seems to be executed on only CUDA core without Tensor core.


Small changes to make it work on default PCP installation

Hi,
I know that this is WIP but this might be useful to others. I needed few changes to make flame graphs work on default PCP+Vector installation (unless I did compile&install it incorrectly in the first place :)). Also you might want to remove references to Netflix environment and S3 buckets :)

True. Was looking to share something with some people that were interested in Flamegraphs while we work on a better solution. Nothing sensitive, but should have cleaned it up a bit before publishing. Tks @tkowalcz !


Insert with empty association

Environment

Elixir version (elixir -v): 1.3.0-dev
Database and version: PostgreSQL 9.4
Ecto version (mix deps): master

Current behavior
defmodule Post do
  use Ecto.Schema
  import Ecto
  import Ecto.Changeset

  schema "posts" do
    field :title, :string
    field :body, :string

    has_many :comments, Comment
  end

  def changeset(post, params \\ %{}) do
    cast(post, params, ~w(title body))
    |> cast_assoc(:comments)
  end
end

defmodule Comment do
  use Ecto.Schema
  import Ecto.Changeset

  schema "comments" do
    field :body, :string

    belongs_to :post, Post
  end

  def changeset(comment, params \\ %{}) do
    cast(comment, params, ~w(body))
  end
end

When inserting with association data, everything is OK:
post = Post.changeset(%Post{}, %{title: "Post 1", comments: [%{body: "Comment 1"}]}) |> Repo.insert!
[%{body: "Comment 1"}] = post.comments

When inserting with empty association data, the association is marked as not loaded even though it's gonna be almost always empty [1]
post = Post.changeset(%Post{}, %{title: "Post 1", comments: []}) |> Repo.insert!
post.comments # => #Ecto.Association.NotLoaded<association :comments is not loaded>

Expected behavior
When inserting a new record, empty assoc should be loaded and empty:
post = Post.changeset(%Post{}, %{title: "Post 1", comments: []}) |> Repo.insert!
[] = post.comments

post = Post.changeset(%Post{}, %{title: "Post 1"}) |> Repo.insert!
[] = post.comments

[1] if there're no fk constraints, there could be a comment referencing newly created post, and having the association be [] could be considered incorrect, however the same could be said for 1st case I mentioned above when inserting new record with associations data.

Could someone verify if the expected behavior I proposed makes sense? If so, I'm happy to take a stab at implementing it at some point. Thanks!

Yes, it is.

Actually, let me clarify. The association should be marked as an empty list or nil ONLY IF it is marked as an empty list or nil BEFORE insertion. If it is NotLoaded before insertion, it should still be NotLoaded after insertion.

Thanks @josevalim. Sorry if it's a silly question, but what would be a concrete example where we want to keep NotLoaded after new record was just inserted?
Assuming FKs are correctly set (see footnote above, perhaps we can't make that assumption though? Or we would make it but also document it, perhaps?) when using has_one, has_many I think we can safely default to nil or [] even if the association wasn't explicitly specified when inserting - that's the 2nd code snippet in the expected behaviour.
For belongs_to, NotLoaded would make sense if user would e.g. cast author_id with a non-nil value. If the user would cast_assoc(:author) and wouldn't cast author_id we could sensibly load it as nil by default. If the user would allow to both cast author_id and cast_assoc then it would be a problem :)
I'm not sure what exactly needs to change to make this work and as you can probably see I was looking at this issue from the cast/cast_assoc perspective. Also, perhaps I'm making this unnecessarily complicated :) I'll start with proper handling for casting assoc with nil or [].

see footnote above, perhaps we can't make that assumption though? Or we would make it but also document it, perhaps?

That's my biggest concern. I would prefer to not do this assumption at this moment.

@josevalim :+1:

@josevalim damn, I was almost there (https://github.com/wojtekmach/ecto/commit/bdc9f12a1c6ee433cf1bac12797acebd7ab6a230) but definitely were missing a few pieces. Thanks for fixing it!


Update app-service-web-tutorial-custom-domain.md

Adds guidance on what to do when the IP is not resolved.
Changes the suggested DNS web client from one with user tracking, a popup and 4 moving ads to one with 1 less intrusive ad, no tracking and more information.
Fixes capitalization.

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

#sign-off

Thanks for the review. Publishing in this repository is suspended until Tuesday, March 2. Merging will resume Tuesday, and we'll merge this approved pull request at that time. Thanks.


Dates of validity for WMS layers COUNTRY=cambodia

This PR enables PRISM to add additional dates based on the validity parameter. On the calendar rendering event, the feature will add more dates on the dates Array object, and will add the correct value to be requested to the WMS server. For instance, for dates 2022-01-11 and 2022-01-21 and a validity parameter of 1. The calendar array will have dates 2022-01-10, 2022-01-11, 2022-01-12 and 2022-01-20, 2022-01-21 and 2022-01-22 respectively

@JorgeMartinezG I like the general direction and it seems to be working in the demo URL. However, I think we need to clean up the code a bit more to:

make it faster
make it more explicit (add comments, find more explicit names for the different variables)

@JorgeMartinezG & @ericboucher:
I'm testing locally. When I tried to load an initial layer (rainfall anomaly), the request fails: "Time dimension value '2022-08-28' not valid for this layer".
When I then load another layer (10-day rainfall), the layer loads with 2022-08-21, but the calendar shows multiple other dates available from the kobo layer. Selecting a non valid date for the current layer does nothing though:

@JorgeMartinezG & @ericboucher -  I'd like your thoughts on how this was implemented. I'm don't think the validity value should be enforced as  (+/-) days, but instead just (+) or (-) which should be part of the configuration. I.e., if it's valid for 5 days after the 'start' date, the validity value should be 5. If it's for 5 days leading up to the 'start' date, the validity value should be -5.
Also noting here that we should discuss how easily the WMS validity days concept can be applied to other layer types.

@wadhwamatic
We could do something simple and have 3 different cases:

5 both ways
-5 leading to
+5 after

For other layers, I think what @JorgeMartinezG implemented would work for as well. The issue at the moment seems to be around performance

That works @ericboucher. I don't think the +/- scenario exists at the moment, but good to have it for the future

@JorgeMartinezG - I don't know if it's just on my side, but the performance on this branch is very slow. Toggling on any layer is slugish.
I also wanted to test this on the kobo flood layer which has more test data available (see my commit). I loaded the 10-day rainfall layer, followed by kobo flood report. The screen blanks out and never renders again even though the network tool seems to show that requests were complete.


Prometheus deletion deletes a Secret not managed by Prometheus

What did you do?

Create a Secret named prometheus-foo with prometheus.yaml data key.
Create a Prometheus resource named foo omitting serviceMonitorSelector in the spec.
Verify prometheus is launched with the config file specified in step 1.
Delete the Prometheus object created in step 2. (kubectl delete prometheus foo)
Check if Secret from step 1 is still there (kubectl get secret prometheus-foo). It is not.

What did you expect to see?
5. Secret is not deleted when Prometheus resource is deleted.
What did you see instead? Under which circumstances?
5. Secret is deleted when Prometheus resource is deleted.
Environment
prometheus-operator: v0.8.2
k8s: 1.6
Context: #324

If the Secret is managed by the Prometheus Operator it has a label with that information, so at deletion we just need to check whether it is managed-by=prometheus-operator and only then delete it. Do you want to give it a shot @Bekt ?

If we can get an implementation down for this quickly I'm happy to include it in the v0.9.0 release which should be in the upcoming days.

I don't have much experience with testing in Go, so it's probably better for somebody else to pick this up. 😐

No worries, just want to encourage people and give them a chance :slightly_smiling_face: should be able to take care of this tomorrow.


Implement a pairwise comparison of two segments

In the comparison view, allows for a lightweight annotations of segment pairs with 'A<B', 'A>B' or 'A=B' label.
Changes proposed in the pull request:

Added PairwiseRanking model
Sending an annotation on a change of the select box using Ajax
Not using JQuery Slim to have Ajax supported

To do:

Showing proper error messages
Showing which segments already have annotations
Exporting the annotations
Optimizations

This PR is made on top of #25.
@AppraiseDev/core-team

@snukky: ModuleNotFoundError: No module named 'pylint_django' -- spurious issue or did you expect this to break?

No, I don't plan to merge this as it might have already diverged too much from the main branch, but I would like to keep this pull request as a draft for having a reminder. Most of the code from this can be re-used once we're back into this enhancement.


Added support for touchleave, mouseleave and pointerleave

If you touched down, then exited the touch area, the long press would still fire

Thanks you all!


Add WriteBatch and write_batch operations for atomic batch writes

Taking a crack at a WriteBatch API similar to RocksDB's. I opted to use a WriteBatch struct rather than an iterator of key-value pairs so that we could record deletes as well.
I believe this should "just work" since we hold a guard for the db state in each of these operations:

write batch
put
get (read guard only)
delete
WAL flush
memtable flush

I'm open to suggestions on the best way to test this.
Note that the WriteBatch has an unlimited size. This means that batch writes can exceed l0_sst_size_bytes (when WAL is disabled). It also means that WAL SSTs could get large if there's a large batch write.

An alternative implementation would be to create a new KVTable for each write batch. I think this would hold the lock for a much shorter time. But it could make SSTs smaller since active WAL and memtable KVTables would get frozen even if they are quite small.

The Pebble docs have a really good summary of their commit pipeline:
https://github.com/cockroachdb/pebble/blob/master/docs/rocksdb.md#commit-pipeline
I think we should mirror this. It does require a bunch of changes to this PR, which is fine. I'm thinking maybe an RFC is in order for this.

Noticing that @flaneur2020 is discussing WriteBatch in #260. Should have read that first. 😱 My bad. Reading now.

@criccomini  Oh, never mind, #260 did not intent to discuss things about the write path of WriteBatch.
it only intents to discuss the part related to transactions: each transaction may hold the changes in a write batch, and it should expose an iterator, which allows users inside a transaction to query what they've written in the transaction before the commit.
this makes the MVCC part of Transaction's work, and the read path in this MVCC will be: WriteBatch -> MemTable -> S0 -> other layers.

SGTM. Then I think the main thing to figure out here is the commit pipeline for batched writes.
Right now, I spawn on each batch write. But I don't think this will keep the batches serialized, though. I'm considering adopting the Pebble/LevelDB approach: using the lock to determine a leader to drain the current batches serially. This will also give us to have a place to update the current sequence number when we implement snapshot isolation.

i guess Pebble or Badger might be better references than LevelDB. having channels as a synchronization primitive could simplify lot of things when comparing to LevelDB's locked leader election approach.
my intuition suggests we could use a single tokio task for the commit pipeline with something like mpsc::Channel<CommitPipelineEntry>. Each write operation may associated with a CommitPipelineEntry which looks like:
struct CommitPipelineEntry {
    batch: WriteBatch,
    done: oneshot::Sender<()>,
}

each Write operations would enqueue a CommitPipelineEntry and await the rx of the entry.done oneshot channel. The commit pipeline task would signal entry.done once the write is considered durably flushed.
this approach might not be appropriate, just an random thought to my mind, only for reference :)

This PR now has some fairly substantial changes.

Uses Bytes instead of &[u8] for key/value pairs everywhere except the public API methods (they still use slices).
Adds a spawned thread that serially writes byte batches into the active WAL/memtable.
Lays groundwork to have put/delete also use the spawned thread by putting single kv pairs into a batch.
Lays groundwork to pass SlateDbErrors  all the way to the client for put/delete.

LMK what y'all think. No problem if this is too much change. LMK where to back off.

I want to call out a change I made in e19a784. While testing the wal_disabled feature with batches, I noticed I introduced a race condition. Now that batch writes happen in the write loop, the loop can call maybe_freeze_memtable before the write_with_opts is able to call await_durable. In such a case, maybe_freeze_memtable can send a signal to the memtable flusher to flush the memtable. In In doing so, the memtable gets flushed and the durable listeners are notified before the write_with_opts has started listening. Because we use notify_watchers, which is stateless, once the write_with_opts starts awaiting, it is blocked forever because the notification was sent before it could listen. I've changed to use tokio's watchers which are meant for this purpose.

I ran the code through the bencher as well. The put/get/delete code doesn't use the write batch pipeline yet, but I just wanted to make sure I didn't mess anything up. The bencher finished and looked OK.

LGTM. Could you add a comment explaining why we are doing the writes on a background task (I think the goal is reducing contention around putting the batch in the memtable)?

Added here: a364ea8
LMK if this makes sense @rodesai

LGTM!

Hi, I have a question regarding how WriteBatch ensures atomicity during writes. For example, if an exception occurs while retrieving key-value pairs from the WriteBatch to write into the Memtable, resulting in only some key-value pairs being written to the Memtable, how is atomicity guaranteed in this case?

你好，我有个问题，WriteBatch 在写入时如何保证原子性，比如从 WriteBatch 中取出键值对写入 Memtable 时发生异常，导致只有部分键值对写入 Memtable，这种情况下如何保证原子性？

Don't forget WAL

Hi, I have a question regarding how WriteBatch ensures atomicity during writes. For example, if an exception occurs while retrieving key-value pairs from the WriteBatch to write into the Memtable, resulting in only some key-value pairs being written to the Memtable, how is atomicity guaranteed in this case?

Don't forget WAL.

Hi, I have a question regarding how WriteBatch ensures atomicity during writes. For example, if an exception occurs while retrieving key-value pairs from the WriteBatch to write into the Memtable, resulting in only some key-value pairs being written to the Memtable, how is atomicity guaranteed in this case?

Good question! So, there are a few things here. All ops in a single batch are put into the same memtable. This is guaranteed by the guard that we take in batch_write.rs. That memtable is either successfully written to object storage, or it's not--the object store layer guarantees that. If the write fails, the entire memtable is lost. If it succeeds, all rows were written.
If an exception occurs while we're putting records into the memtable, we would need to raise a SlateDbError in write_batch. Can you give me an example of an error that could be triggered in the for loop in batch_write.rs's write_batch method? I can only think maybe an OOM or some hardware fault? I'm not sure how Rust/the OS handle those. In Java, the process would fall into a degraded state on OOM where some threads might be killed while others are alive, which could indeed risk having a partially batch-updated memtable written to object storage. Any idea how Rust behaves in such scenarios?

Hi, I have a question regarding how WriteBatch ensures atomicity during writes. For example, if an exception occurs while retrieving key-value pairs from the WriteBatch to write into the Memtable, resulting in only some key-value pairs being written to the Memtable, how is atomicity guaranteed in this case?

Good question! So, there are a few things here. All ops in a single batch are put into the same memtable. This is guaranteed by the guard that we take in batch_write.rs. That memtable is either successfully written to object storage, or it's not--the object store layer guarantees that. If the write fails, the entire memtable is lost. If it succeeds, all rows were written.
If an exception occurs while we're putting records into the memtable, we would need to raise a SlateDbError in write_batch. Can you give me an example of an error that could be triggered in the for loop in batch_write.rs's write_batch method? I can only think maybe an OOM or some hardware fault? I'm not sure how Rust/the OS handle those. In Java, the process would fall into a degraded state on OOM where some threads might be killed while others are alive, which could indeed risk having a partially batch-updated memtable written to object storage. Any idea how Rust behaves in such scenarios?

Thanks for your reply, but I don't quite understand the meaning of this sentence.

If the write fails, the entire memtable is lost.

If there are two WriteBatches, A and B, and A successfully writes to the MemTable but has not yet been flushed to disk, then if B only writes partially and an exception occurs, if we discard the MemTable, from the user's perspective, A should be considered successfully written, but the data would be unqueryable.

If there are two WriteBatches, A and B, and A successfully writes to the MemTable but has not yet been flushed to disk, then if B only writes partially and an exception occurs, if we discard the MemTable, from the user's perspective, A should be considered successfully written, but the data would be unqueryable.

We don't acknowledge a durable write until the memtable has been written to object storage. So, from the user's perspective, batch A will not be successfully written in the scenario you describe.

We don't acknowledge a durable write until the memtable has been written to object storage. So, from the user's perspective, batch A will not be successfully written in the scenario you describe.

If A was successfully written to the memTable without being flushed, then querying at that point would show that A exists. However, if an exception occurs while writing B and the memTable is discarded, then querying A afterward would indicate that A no longer exists. Is my understanding correct?

If A was successfully written to the memTable without being flushed, then querying at that point would show that A exists. However, if an exception occurs while writing B and the memTable is discarded, then querying A afterward would indicate that A no longer exists. Is my understanding correct?

It depends on the ReadLevel you pass to get_with_options. If you pass level Committed then querying A would not return anything as it has not been durably written to the db yet. If you pass level Uncommitted then it would work as you described.

It depends on the ReadLevel you pass to get_with_options. If you pass level Committed then querying A would not return anything as it has not been durably written to the db yet. If you pass level Uncommitted then it would work as you described.

I see, thank you very match.

Don't forget WAL.

Yes, I just realized it. When an exception occurs, we can simply let the process crash, and then recover from the WAL, without having to worry about the memtable.


How i can use motion ui animation on things while page scroll ?

I want to animate things while page scrolling is it possible or no ? I want to use this with foundation 6

Hey, sorry for the late response! Motion UI doesn't include this feature out of the box, but you can integrate it with WOW.js. I wrote a post on the Foundation Forum explaining how it works. Hope that helps! :)

Opening an issue to track adding WOW.js integration to the Motion UI documentation: #63


Restore inquiry auth modal

Per a conversation with @katarinabatina and @junybrum on Friday we discovered that when users created an account with facebook as part of the inquiry flow those inquiries weren't going through. Seeing that we've closed the GDPR test we decided to go ahead and revert back to the old register form.

Sure! This issue that inquires where the user created an account with facebook weren't going through. I'm pretty sure this has something to do with that facebook bug we were looking into last week. With regards to the inquiry flow/questionnaire we never supported account creation with facebook here in the first place so this goes back to using the old form.

Gooot it, thanks!


[Story] Add edit note

Epic: #18
Description
As a user I want to be able to edit notes and save them, so I can make changes and add new information.
Tasks

[x] Create update note function in note service.
[x] Create edit note page.

Created edit note as part of the notes feature implementation, see:
https://github.com/KinaUna/Examplium/tree/master/Documentation/Code/Notes


Deadcode in jvm-function-invoker

I happened to notice that JvmFunctionInvokerBuildpackError::CouldNotWriteLaunchToml is unused:
https://github.com/heroku/buildpacks-jvm/blob/1fd4e44152950657e65d94bb007c00f4fc6e09e9/buildpacks/jvm-function-invoker/src/error.rs#L20-L21
(There may be others)
This is presumably not being picked up by rustc/clippy since JvmFunctionInvokerBuildpackError and much of the rest of the buildpack uses pub rather than pub(crate), which means the lints don't call out deadcode (even though the crate is binary-only, and doesn't expose a library).
I would recommend moving to pub(crate) to catch these in the future.
cc @Malax

Ha, thanks for the report - I'll do a pass over the repo when I have some cycles :)


Fix csv generation in release script

Signed-off-by: Ruben Vargas Palma<EMAIL_ADDRESS>Fixes https://github.com/jaegertracing/jaeger-operator/issues/1237

A couple of things about this PR

When using the flat --make-manifests=false with --from-version  the operator-sdk generation tool uses the legacy path in order to find the manifest, in this case it was looking for deploy/olm-catalog/jaeger-operator/1.19.0/jaeger-operator.v1.19.0.clusterserviceversion.yaml but that file doesn't exist, so it enters into interactive mode (added on 1.18.0) , asking displayName and other operator metadata, after some timeout, the release script fails.

I removed the --from-version flag and assumed that the file deploy/olm-catalog/jaeger-operator/manifests/jaeger-operator.clusterserviceversion.yaml is the latest (belongs to 1.19.0), so I copied to deploy/olm-catalog/jaeger-operator/1.20.0/jaeger-operator.v1.20.0.clusterserviceversion.yaml  witch is the folder that the tool expected to see the manifest for that version when --make-manifests=false, and then ran the operator-sdk generate csv in in order to update the manifest with the latest changes.

I need to move the example folder outside deploy, so the Deployment resources won't be included in the manifest, this happens because now the tool scans the deploy folder, read all yaml and include the Deployment resources as part of the manifest, this was including tracegen, myapp, etc... This was due a breaking change that makes csv-config.yaml obsolete. https://github.com/operator-framework/operator-sdk/pull/2511 and https://github.com/operator-framework/operator-sdk/blob/v0.18.2/CHANGELOG.md#removed, before this change the tool only reads on folders specified on config file.

Finally I added an annotation to pkg/apis/jaegertracing/v1/jaeger_types.go , not sure why is this now required, if this is a regresion or something changed, I only found an issue related to this behavior: https://github.com/operator-framework/operator-sdk/issues/2575

@rubenvp8510 @jpkrohling Although it will have an impact, so not ideal, it may be better to have the general examples outside the deploy folder, just leaving a single minimal example CR under deploy/examples, to be used in the csv.

@jpkrohling @objectiser If move the examples folder is problematic, there is another solution, an argument to specify the deploy path.
       --deploy-dir string      Project relative path to root directory for operator manifests (Deployment and RBAC) (default "deploy")
We can move the manifest, roles and operator deployment to another place.

I think my vote would still be to move the examples, as better to use the default deploy folder. I think the deploy/examples folder was unfortunately used for two purposes, (1) to provide a single example per CRD (for the CSV), and (2) to provide user examples for various scenarios.
But will defer to @jpkrohling for the final decision.

Between moving the deployment artifacts elsewhere and moving the examples, I'd vote for moving the examples. Could we still at least have the directory there with a readme, pointing to the new place?

I think we would need the deploy/examples folder still there anyway, to include the single example CR that we want included for the Jaeger CRD - so probably the "simplest.yaml"?
Definitely would be good to have a readme also, to refer to other examples location.

We can include all Jaeger custom resources into deploy/examples folder,  but we cannot include deployments or other kind of resources like roles etc.. if we do it, those will be included in the manifest. S

@rubenvp8510 Currently the CSV only supports a single example per CRD. So if moving the examples, then it would be better to just have the simplest example in this deploy/examples folder. If they allow more examples in the future we can decide which ones to select.

This is what happens when the example folder is under depoy/
https://gist.github.com/rubenvp8510/e4a01ce75b7dd0e9c77a65092ea46302#file-csv-yaml-L833
You can see tracegen, myapp, elastic deployments included as part of the manifest,  and all crds as examples:
https://gist.github.com/rubenvp8510/e4a01ce75b7dd0e9c77a65092ea46302#file-csv-yaml-L5

@rubenvp8510 Yeah, so if you could move the current deploy/examples folder content to examples, and then move https://github.com/jaegertracing/jaeger-operator/blob/master/deploy/crds/jaeger-all-in-one-inmemory.yaml to deploy/examples folder with a readme - and then remove the other examples from the deploy/crds folder.
@jpkrohling is that ok with you?

Done.

@objectiser sounds like a plan!

@rubenvp8510 Sorry, but can you remove the jaeger-all-in-one-local-storage.yaml and jaeger-prod-elasticsearch.yaml from the /examples folder - I don't think these are necessary as covered by other examples.
@jpkrohling once that is done, were there any other outstanding comments from you, or can it be merged?

@objectiser Done!

were there any other outstanding comments from you, or can it be merged?

No, I think my concerns were addressed, but we'll only get certain that it works once we release. Perhaps @rubenvp8510 should be doing the next release? ;-)

@rubenvp8510 Thanks!


Upgrade CI tests to use Bazel 6

Bazel has just released version 6.2.0, and has been on version 6 since Dec 2022.
The CI tests currently use version 5.3.1, but they should probably be modified to run some (or all?) of the tests using the latest LTS Bazel version which is 6.2.0.
Note, I ran the tests with 6.0.0 on my local box, and ran into couple issues... mainly that the return value of str(label) has changed (see https://github.com/bazelbuild/bazel/issues/16196). This causes a few tests to fail... but should be straightforward to fix by not assuming output of str(label).

We don't run current tests on 6.x.x because some test code is not compatible yet. I want to test a few fixes, and cut Rules Scala release, then I guess .bazelversion can be updated.

OK, sounds good.  I'll post a PR once I get the CLA done.


Group - All 8 participants are shown in header on creating group

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue found when executing PR https://github.com/Expensify/App/pull/37907
Version Number: 1.4.50-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Go to https://staging.new.expensify.com/home
Tap fab ---- start chat
Add to group 8 participants with small user name
Tap create group

Expected Result:
When creating group with 8 participants, the group conversation header must display only 5 participants
Actual Result:
When creating group with 8 participants, the group conversation header displays all 8 participants
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub

We think that this bug might be related to #vip-vsp
CC @quinthar

@anmurali  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

cc @jbroma @deetergp as this was found during QAing of PR you have been involved at, thanks!

Proposal
Please re-state the problem that we are trying to solve in this issue.
All selected participants are displayed on the header (names)
What is the root cause of that problem?
The headerView  component display all the available 8 participants.
What changes do you think we should make in order to solve the problem?
We can limit the number of participants to 5 here
https://github.com/Expensify/App/blob/2979c4f750252ed7d45fc9fd1097ec3939b70dec/src/pages/home/HeaderView.tsx#L79

Proposal
Please re-state the problem that we are trying to solve in this issue.
Group - All 8 participants are shown in header on creating group
What is the root cause of that problem?
The root cause of the problem is here we are displaying all the participants personal details
https://github.com/Expensify/App/blob/54691988244d9c61e291b2162152d6bf52ad952f/src/pages/home/HeaderView.tsx#L79
and then in here :
https://github.com/Expensify/App/blob/54691988244d9c61e291b2162152d6bf52ad952f/src/pages/home/HeaderView.tsx#L81
we are displaying it
What changes do you think we should make in order to solve the problem?

We can limit it to just display 5 participants by doing this :
    const participantPersonalDetails = OptionsListUtils.getPersonalDetailsForAccountIDs(participants.slice(0, 6), personalDetails);

What alternative solutions did you explore? (Optional)
N/A
Result :
https://github.com/Expensify/App/assets/158435970/cee9ba7a-c21a-4d47-936e-3616cbe25fb3

@deetergp Before you mentioned the issue, I already had that solution.

Still sorting this one out on the original GH.

@deetergp I posted a comment here https://github.com/Expensify/App/pull/37907#issuecomment-1991219351 to explain how I think that the original GH is not solving the real issue

Proposal
Issue: This issue is being caused due to text overflowing in a given area.
Proposed Solution: We can extract the first five Usernames within the chat participants and only display their names. We may want to add a way to trunc the concatenated names if the text overflows.

@mountiny I am not sure whether we need to restrict to 5 here or not, Reason - Currently users can see all group users in the ellipsis tooltip if it overflows. Raised same point here

I think we want to keep only 5 members in the report name

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~018a4006af512d5d51

@dragnoir's proposal is straightforward and looks good to me for limiting participants for the report header.
🎀👀🎀 C+ reviewed

@dragnoir's proposal is straightforward and looks good to me for limiting participants for the report header.
🎀👀🎀 C+ reviewed

Hey @Pujan92 ! I Want to know why not my proposal

Hey @Pujan92 ! I want to know why not my proposal ?

@dragnoir is the first to propose and applying a limit to participantAccountIDs is enough, kind of similar to what we did here.

PR has been merged and is currently being tested on staging.


top,bottom ui area remove

hi.
I would like to remove the UI region in webview.
Is it possible?
Top, bottom safari ui area

Not possible to my knowledge.


Generate licenses?

Can the license text be used to generate licenses? It seems that the text actually contains not just the full license text but SPDX markup for matching purposes. Is there a parser for this markup that could be fed with user-provided settings?

Yes, but no idea how. This is just a module for getting the license text. I'm not involved with SPDX.
Maybe @kemitchell knows.

SPDX is working on more systematically formatted templates. I think they're pretty far  along, and that they're using an XML schema. It may be on GitHub now; you could check the mailing list archive for the latest.
If you need something lighter weight but less complete, you can have a look at what I've done with the licensor package and the jslicense org on GitHub.

Thanks for the swift response!
Actually this discussion helps me a fair bit I think: https://github.com/sindresorhus/spdx-license-list/issues/6#issuecomment-150606727
The only problem seems to be that some licenses aren't in template form (yet?), especially the more obscure licenses and variants.


Fix encoded jsonld SEO meta component

Closes #48

Great catch and fix! Thanks!

You're welcome :)
On Tue, Feb 16, 2021 at 3:48 PM Joost Jansky<EMAIL_ADDRESS>wrote:

Great catch and fix! Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/styxlab/next-cms-ghost/pull/51#issuecomment-779681839,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2IQLO2GKFOFDIZC4HBHC3S7IWNFANCNFSM4XV5FROQ
.


needextract seems broken with requirement containing need_parts

It throws on
  File "/usr/local/lib/python3.9/site-packages/sphinxcontrib/needs/layout.py", line 40, in create_need
    raise SphinxNeedLayoutException(f"Given need id {need_id} does not exist.")
sphinxcontrib.needs.layout.SphinxNeedLayoutException: Given need id 163 does not exist.

where 163 is the generated id of the parts.

Hi @adegroote,
From the error message above you can see, there is nothing to do with needextract.
The issue is you want to call function create_need(), which needs parameter need_id, but you passed a need_part id.
Be aware, need_part is not a need object. need_part id is not need_id.  You can't create need node for need_part.

Well, the "full" backtrace is
  File "/usr/local/lib/python3.9/site-packages/sphinx/cmd/build.py", line 294, in main
    return build_main(argv)
  File "/usr/local/lib/python3.9/site-packages/sphinx/cmd/build.py", line 280, in build_main
    app.build(args.force_all, filenames)
  File "/usr/local/lib/python3.9/site-packages/sphinx/application.py", line 344, in build
    self.builder.build_update()
  File "/usr/local/lib/python3.9/site-packages/sphinx/builders/__init__.py", line 294, in build_update
    self.build(to_build,
  File "/usr/local/lib/python3.9/site-packages/sphinx/builders/__init__.py", line 358, in build
    self.write(docnames, list(updated_docnames), method)
  File "/usr/local/lib/python3.9/site-packages/sphinx/builders/__init__.py", line 529, in write
    self._write_parallel(sorted(docnames),
  File "/usr/local/lib/python3.9/site-packages/sphinx/builders/__init__.py", line 566, in _write_parallel
    doctree = self.env.get_and_resolve_doctree(docname, self)
  File "/usr/local/lib/python3.9/site-packages/sphinx/environment/__init__.py", line 535, in get_and_resolve_doctree
    self.apply_post_transforms(doctree, docname)
  File "/usr/local/lib/python3.9/site-packages/sphinx/environment/__init__.py", line 586, in apply_post_transforms
    self.events.emit('doctree-resolved', doctree, docname)
  File "/usr/local/lib/python3.9/site-packages/sphinx/events.py", line 101, in emit
    results.append(listener.handler(self.app, *args))
  File "/usr/local/lib/python3.9/site-packages/sphinxcontrib/needs/directives/needextract.py", line 88, in process_needextract
    need_extract = create_need(
  File "/usr/local/lib/python3.9/site-packages/sphinxcontrib/needs/layout.py", line 40, in create_need
    raise SphinxNeedLayoutException(f"Given need id {need_id} does not exist.")
sphinxcontrib.needs.layout.SphinxNeedLayoutException: Given need id 163 does not exist

so it is definitively related to need_extract (but yes, sorry for the "shortned" backtrace

Sure, it can start from needextract, but when you follow the trace, you can see the real issue is function create_need().
Again, need_part id is not need_id. In you case, the message says: Given need id 163 does not exist. Surely 163 does not exist, it's a need_part id, not a need_id.

I'm somehow lost, as I don't have a reproducible example here. I have the feeling both of you have something different in mind ;)
So I guess the following does not work?
.. req:: Test me
   :id: REQ_001

   :np:`This is a  need part`

.. needextract:: REQ_001

Or is the scenario even more complex?

@danwos yes exactly. If you are not able to reproduce it, I would try to create an example on my side. The problem still exists in 1.0.1.

@adegroote No it's fine. Now we know what to look for and can reproduce it :)

@danwos well, I tried the example above, I don't see a problem and it works for me.
I still feel something not related to needextract went wrong. Based on the error message from @adegroote, it seems to me in layout.py function create_need() is the issue. Just my thoughts.

AS the content gets copied, also the need_part definition is copied.
So I guess during handling of this copy, something strange happens.
I agree, that this problem may exist in the layout.py file.
So we really need an example, which reproduces this error.
@adegroote Just to be sure, you really mean need_part not embedded needs?

The following example reproduces my issue:
.. need:: Foo Bar
   :id: FOO_00001
   :tags: foo, bar

    xxx
        - :np:`1 foo` foo bar

.. needextract::
   :tags: foo

Now I see the issue. The issue is coming from the definition of need_part.
For instance, in the example above, the need_part is defined like this: :np:1 foo foo bar. The issue is the content foo bar after :np:1 foo. Somehow the content makes the need_part doing something wired. I will look into the need_part, see how it handles the content there.
Thanks @adegroote for this unique use case.


⚠ Bofrost.at has degraded performance

In 2b83396, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1765 ms

Resolved: Bofrost.at performance has improved in 6f2f455 after 13 minutes.


[Feature] Contact Us form and hover effect on social media icon

Description
Adding Contact Us form with the input fields.
Display of pop-up message after submission of form .
Giving hover effect to the social media icon similar to their logo color.
Form must have the UI matches to the theme of website.
https://github.com/CSEdgeOfficial/learn.csedge.courses/assets/168854094/4679e1e3-1c0a-477e-808f-10b7ac7e0bad
Screenshots

Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSoC'24 contributor.
[X] I want to work on this issue.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

@CSEdgeOff , please assign this issue to me.

Hello Sir @CSEdgeOff please assign me this issue i want to work on it .. i will complete this as soon as possible for me

@TBorundia The sample video was not good actually if you improve that you can work on it

@TBorundia The sample video was not good actually if you improve that you can work on it

@Durgesh-Vaigandla
Yes Sir, I shall try my best to match the form with the theme of website and improve it.
You can also suggest if any necessary changes are required.
I want to work on this issue, please assign it to me under GSSoC'24.

@TBorundia The sample video was not good actually if you improve that you can work on it

@Durgesh-Vaigandla Yes Sir, I shall try my best to match the form with the theme of website and improve it. You can also suggest if any necessary changes are required. I want to work on this issue, please assign it to me under GSSoC'24.

@Durgesh-Vaigandla Sir, is this issue assigned to me ?
Should I start working on it?


More tests for QA upgrade UI job

test stopping os services page
test creating os database page

Related tests at https://github.com/SUSE-Cloud/cct/pull/73

Successfully built at https://ci.suse.de/view/Cloud/view/QA/job/cloud-mkphyscloud-qa-test-upgrade-ui/51/console


I am adding my contribution

https://ikittycode.github.io/flappy-bird

@iKittyCode This looks like a duplicate of #2851 which was merged so I'm closing the pull request. If I'm wrong let me know and I'd be happy to reopen it.


[UX Improvement] Add ? question mark icon for users to learn more

Describe the feature you would like to request
This request is based on closed beta testing feedback:
On the extension's landing page, before a user connects their wallet, allow the user to learn more about:

what a "Wallet address or payment pointer" is, and
what a "Public key" is (that's if we keep the term "public key")

Describe the solution you would like
On the extension's landing page, before a user connects their wallet, add a "learn more" hyperlink or the question mark icon to the right side of the:

"Public key" text OR the text "Copy the public key below and paste it into your wallet"
"Wallet address or payment pointer" text

such that when a user clicks on the icon or hyperlink, they get redirected to documentation, launched in a separate tab, to learn more about a public key, wallet addresses or payment pointers.
Additional context
Suggesting the locations highlighted in the attached image.

Isn't this going to get sorted by adding the post-install how to page?

Isn't this going to get sorted by adding the post-install how to page?

Okay cool, I'm happy to park this one 👍🏾

This one can be closed, right?

Agreed to cancel this issue on 11 Sept 2024.


Add instructions to download from Hugging Face Hub

Hi there :hugs: In collaboration with Google, we added the gemma.pytorch files to the Hugging Face Hub. This PR adds instructions to manually or programmatically download the models.

Great! Looking good!


[material-ui][Slider] Fix customized iOS demo to use updated official colors

[x] I have followed (at least) the PR section of the contributing guide.

I removed the unnecessary condition which was returning the same value, regardless if the condition is true or false.
👉  https://deploy-preview-39813--material-ui.netlify.app/material-ui/react-slider/#customization

Since it's the IOSSlider demo, maybe we should use the latest official colors? The latest guidelines have distinct palettes for different color modes CC @zanivan

Hey @Super-Kenil thanks for the submission!
I wonder if we shouldn't use this chance to update the visual to look more like the current iOS version:

Since it's the IOSSlider demo, maybe we should use the latest official colors? The latest guidelines have distinct palettes for different color modes CC @zanivan

I wonder if we shouldn't use this chance to update the visual to look more like the

I think I can make it look the current version, just like you mentioned. I will update it and commit.
But I am still facing issues related to passing one of the checks of Argos
Because I am not sure what I am supposed to do about it.
I have attached images below, please let me know @zanivan or @mj12albert

I think I can make it look the current version, just like you mentioned. I will update it and commit.

👍👍👍
@Super-Kenil Don't worry about the argos check! Sometimes it can be very flaky, it can literally be the very last thing we deal with for this PR 😬

I know this is not the right place @mj12albert @zanivan , but I am trying to contribute to the docs, and I am facing issue when I started the dev server on my machine, I tried to fix it myself, but I surely am missing something. This is my first time contributing anywhere, so any help would be appreciated. Checkout the attached image, it shows the error I am getting.

@mj12albert Then I will try again with latest version of yarn today, and make changes, thanks for letting me know about yarn thing.

@Super-Kenil Any updates on this?

@ZeeshanTamboli , I have been busy lately with my new nextjs project, which I will be finishing up in soon, So. I will be updating the design very soon

The iOS slider has been updated to latest design just like @zanivan mentioned

@mj12albert can you tell me, exactly which yarn version are you using, cause I have been facing issues while installing dependencies after updating to yarn latest like you mentioned with the following guide .
If possible then guide me as well, although the design has be done, and the PR is ready to get merged, but I can help in future too if at least I will be able to install the dependencies.


Test execution keeps blinking/reloading

This issue is related to https://github.com/DevExpress/testcafe/issues/3437
What is your Test Scenario?
We're using TestCafe to run UI tests against our website. Since our website is designed to behave responsively, we are running the tests against the Chrome browser in desktop and mobile devices (chrome:emulation:device=iphone X).
What is the Current behavior?
On running our tests against the desktop device, the tests are executed properly but when the execution is on a mobile device, there is constant flickering/blinking/reloading in the browser. Due to which we are blocked from executing tests in mobile devices.
What is the Expected behavior?
The test execution should happen without any flickering/blinking issues.
const url = `${env.qa}/web/abcd/`;

fixture`Running Tests for /web/abcd`
  .meta('runTest', 'sanity')
  .page(url);

console.log(url);

env.qa = "https://www.google.com"
Steps to Reproduce:

Go to my website ...
Execute this command...
See the error...

Your Environment details:

testcafe version: 1.10.1
node.js version: 14.4.0
command-line arguments:  testcafe 'chrome:emulation:device=iphone X' ./tests/ --window-size=375,812 --skip-js-errors --test-meta runTest=sanity --page-load-timeout 30000 -s path=./screenshots/,takeOnFails=true
browser name and version: chrome

https://user-images.githubusercontent.com/25933070/105165023-d46c5680-5b3b-11eb-88fc-5e1a9703d5eb.mov

@sharath2106
Hello,
I cannot reproduce the issue with this information. Could you please share a complete test file and specify your operating system version?

@sharath2106
Hello,
I cannot reproduce the issue with this information. Could you please share a complete test file and specify your operating system version?

Unfortunately, I'm not supposed to share the actual source code. let me find another way and get back to you.

Unfortunately, I'm not supposed to share the actual source code. let me find another way and get back to you.

Hey @sharath2106 did you ever find a fix for this? Definitely seeing the exact same thing happening to me when using chrome device emulation.

Hey @sharath2106 did you ever find a fix for this? I got the same issue with mac m1 with chrome device emulation with last version of testcafe. I need to continue restarting VS Code


manualPagination causes useEffect loop Cycle

useEffect seems to be stuck in a loop even with the most basic samples provided.
https://codesandbox.io/s/vigorous-sky-beu8n?file=/src/App.js
Steps To Reproduce (required)
Steps to reproduce the behavior:

Go to link above and un comment line 93
save sanbox
infinite loop occurs

Expected behavior (Recommended)
The code provided as reference to support fetching external data should not cause infinite loop.
Desktop (please complete the following information):

OS: [iOS]
Browser [Brave]
Version [1.12]

Additional context
I am getting a better understanding of react hooks and I could be doing something very incorrect. But I can't see how I am causing the infinite loop. Unless the dependencies pageIndex and pageSize are actually changing.

What's happening is you're re-creating the Table component on every render, so React runs cleanup on the old hook, and runs the hook again, since it's now rendering a new instance. Either move it outside of your render function, or memoize it.
For example: https://codesandbox.io/s/focused-ride-zpdo2?file=/src/App.js

What's happening is you're re-creating the Table component on every render, so React runs cleanup on the old hook, and runs the hook again, since it's now rendering a new instance. Either move it outside of your render function, or memoize it.
For example: https://codesandbox.io/s/focused-ride-zpdo2?file=/src/App.js
@Vezarino
Thank you very much. I understand what you are saying now. I need to go back and review the examples. I believe they are in this form and can cause the problem for a new person.


Removing <U+FEFF> from proto files

Removing U+FEFF from proto files, which causes issues on other languages when importing the proto files, like elixir

Thanks!


Fixup outdated nix

peras-quickcheck seems to be gone.
update iogx, haskell.nix
rename deltaq.cabal to delta-q.cabal to align with package name (seems to throw haskell.nix off otherwise 😞 )
add bin output to fankenAgda, which more recent nixpkgs expect to exist, and point to the default output.

Seems the change failed the CI because of permissions issues: the build user does not have the right to write in the nix filesystem
https://github.com/input-output-hk/peras-design/actions/runs/11378368175/job/31654025286?pr=245#step:4:641


[workflows] reuse lint with action

reuse lint failed because it complained about the headers in the submodules (HighFive) not being compliant, see e.g. here.
Per default, submodules are skipped with reuse lint, so I am not entirely sure why this happens. Maybe it is because of the way the checkout actions pulls things?
In any case, using the reuse action it seems to work. Their docs use a newer version of checkout, and with this combo it works (but I didn't check v2 of the checkout action, which we were using so far).

ping @timokoch, this seems to work


Create CountingSort.cpp

#6  #97  Adding a CPP implementation of CountingSort

@rrishabh145 Sorry but we alerady have a counting sort algorithm


response slave id does not match request

Im not sure if this is an issue with the library or an issue with my modbus device.
I have a raspberry pi with a USB modbus dongle and a ventilation system which i fetch temperatures from modbus registers.
I make the connection like this and then fetch registers every 30 second after that.
func (m *Modbus) Connect() error {
	// Modbus RTU/ASCII
	handler := modbus.NewRTUClientHandler("/dev/ttyUSB0")
	handler.BaudRate = 9600
	handler.DataBits = 8
	handler.Parity = "N"
	handler.StopBits = 2
	handler.SlaveId = 1
	handler.Timeout = 5 * time.Second
	//handler.Logger = log.New(os.Stdout, "test: ", log.LstdFlags)
	m.handler = handler
	if err := handler.Connect(); err != nil {
		return err
	}

	m.client = modbus.NewClient(handler)
	return nil
}

It works fine for a few days then i start getting below errors.
I restart my app and its fine again.
Im thinking of only checking for error and then making the connection again. But this might be a library issue?
2015/07/20 20:31:18 modbus: response slave id '241' does not match request '1'
2015/07/20 20:31:18 modbus: response slave id '35' does not match request '1'
2015/07/20 20:31:18 modbus: response slave id '249' does not match request '1'
2015/07/20 20:31:18 modbus: response slave id '241' does not match request '1'
2015/07/20 20:31:18 modbus: response slave id '143' does not match request '1'
2015/07/20 20:31:19 modbus: response slave id '69' does not match request '1'
2015/07/20 20:31:48 modbus: response slave id '180' does not match request '1'
2015/07/20 20:31:48 modbus: response slave id '48' does not match request '1'
2015/07/20 20:31:48 modbus: response slave id '241' does not match request '1'
2015/07/20 20:31:48 modbus: response slave id '143' does not match request '1'
2015/07/20 20:31:48 modbus: response slave id '154' does not match request '1'
2015/07/20 20:31:49 modbus: response slave id '117' does not match request '1'

@jonaz Sorry for late response. Do you see any other errors before:
015/07/20 20:31:18 modbus: response slave id '241' does not match request '1'

It would be great if you have request/response logged somewhere so I can take a look.


Exec Steps Concurrent in task (task support DAG)

Feature request
I would exec a tekton task with multi concurrent steps, but it seems cannot support this; (I know the pipeline can handle this feature, but I think it is too heavy to move workspace in different pod);
Use case

In my user case, I hope that the scan step and image build step can execute concurrent.  And at last I need a job to collect the scan and build result.

@lugeng I think you might be interested by TEP-0044: Decouple Task Composition from Scheduling.
/cc @bobcatfish

PipelineRun in a Pod, running of Tasks in parallel perfect meet our need !

Hey just wanted to add a use case that I think is not met by being able to run pipelines on a single pod.
I have a single task that generates documentation in a repository. It's a single task because it is the one unit of reusable logic with a single output (a directory of html files).
However, my repository is made up of many python packages, and the documentation site is built by combining some top level documentation pages (a mkdocs site built from markdown files in a /docs folder) with the API documentation of each of the packages, generated by sphinx.
In order to generate API docs, I need to install the development environment for each of the python packages, individually, and then run my documentation command that handles running the appropriate sphinx process everywhere.
This all has to happen in the same Task because there are dependencies between some of these steps, but installing the development environment is a bit slow and should happen in parallel across all the packages in my repository. Right now, I am doing this in a single Step that runs multiple threads of my pipenv install --dev command. But this results in very confusing error logs when one out of the ~15 pipenv commands fails. If we want to get to the point where a Step is a single command, then I need to be able to have these 15 Steps run in parallel.
The output of my Task is a single html directory which I can bundle into a docker image in another task, but it doesn't make sense to have the pipenv install commands be their own Tasks just for the sake of parallelization. They don't represent a reusable unit of work that would be useful anywhere else.
It looks a little like this:

It's worth pointing out that I really cannot run mkdocs or sphinx without all of my packages having been initialized. So there is no way to generate docs for pkg A above without having done pipenv install on all 3 packages. This is what makes turning them into multiple Tasks impossible. Docs belong to my repository (a project), not the individual components (a python package).


Blacklist?

Is there way to use the manual whitelist to simulate forcing a node off the whitelist. For draining a node that is going down or into maintenance?

Yes - if you put a manual event to critical for a node, it will force that node off the whitelist. You can set a ttl for the event and it will come back after that time.

For more details check out the POST documentation at
https://github.com/twosigma/satellite/tree/master/satellite-master#post-whitelisthosthosteventevent
particularly

state is either ok or critical. ok will turn on the host, critical will turn off the host

If there's something that's unclear in the documentation, let us know and we'll fix it!

Thanks! I missed the docs in the master and slave dirs.

Is there a way that we could make them more obvious from the front page?
On Tue, Nov 24, 2015 at 1:05 AM Barry Kaplan<EMAIL_ADDRESS>wrote:

Closed #41 https://github.com/twosigma/satellite/issues/41.
—
Reply to this email directly or view it on GitHub
https://github.com/twosigma/satellite/issues/41#event-472913369.

Sure, maybe like Cook's subproject summary. But I would also add links to the subproject readme's.