Custom Rule Command Based Help

Hi,
I'm currently trying to create a custom rule to check command based help.
I am doing this by checking for each keyword in the AST. But I cannot seem to make it work.
I am using the Version 1.18.3 of PSScriptAnalyzer.
My Rule is in a ps1. If I use Get-ScriptAnalyzerRule with the Customrulepath Param everything seems to be fine, but If I use it to test a script or a function without command based help there is no warning from ScriptAnalyzer.
Any pointers here?
My rule for the Synopsis looks like this for example:
<#
.SYNOPSIS
    Adds a .SYNOPSIS keyword in your comment-based help.
.DESCRIPTION
    Comment-based help is written as a series of comments. You can write comment-based help topics for end users to better understand your functions. Additionally, it’s better to explain the detail about how the function works.
    To fix a violation of this rule, add a .SYNOPSIS keyword in your comment-based help. You can get more details by running “Get-Help about_Comment_Based_Help” command in Windows PowerShell.
.EXAMPLE
    Measure-HelpNote -FunctionDefinitionAst $FunctionDefinitionAst
.INPUTS
    [System.Management.Automation.Language.FunctionDefinitionAst]
.OUTPUTS
    [Microsoft.Windows.Powershell.ScriptAnalyzer.Generic.DiagnosticRecord[]]
.NOTES
    Reference: Writing Help and Comments, Windows PowerShell Best Practices.
#>
function Measure-HelpSynopsis
{
    [CmdletBinding()]
    [OutputType([Microsoft.Windows.Powershell.ScriptAnalyzer.Generic.DiagnosticRecord[]])]
    Param
    (
        [Parameter(Mandatory = $true)]
        [ValidateNotNullOrEmpty()]
        [System.Management.Automation.Language.FunctionDefinitionAst]
        $FunctionDefinitionAst
    )

    Process
    {
        $results = @()

        try
        {
            #region Define predicates to find ASTs.

            # Finds CmdletBinding attribute.
            [ScriptBlock]$predicate = {

                param ([System.Management.Automation.Language.Ast]$Ast)

                [bool]$returnValue = $false

                if ($Ast -is [System.Management.Automation.Language.AttributeAst])
                {
                    [System.Management.Automation.Language.AttributeAst]$attrAst = $ast;
                    if ($attrAst.TypeName.Name -eq 'CmdletBinding')
                    {
                        $returnValue = $true
                    }
                }

                return $returnValue
            }

            #endregion

            # Return directly if function is not an advanced function.
            [System.Management.Automation.Language.AttributeAst[]]$attrAsts = $FunctionDefinitionAst.Find($predicate, $true)
            if ($FunctionDefinitionAst.IsWorkflow -or !$attrAsts)
            {
                return $results
            }

            if (!$FunctionDefinitionAst.GetHelpContent().Synopsis)
            {
                $result = New-Object `
                            -Typename "Microsoft.Windows.PowerShell.ScriptAnalyzer.Generic.DiagnosticRecord" `
                            -ArgumentList $Messages.MeasureHelpSynopsis,$FunctionDefinitionAst.Extent,$PSCmdlet.MyInvocation.InvocationName,Warning,$null

                $results += $result
            }

            return $results
        }
        catch
        {
            $PSCmdlet.ThrowTerminatingError($PSItem)
        }
    }
}

If you run your function without PSScriptAnalyzer, just by itself, on the AST of a script you've parsed, do you get any errors? I'm also surprised this works with such a specific input type, rather than requiring you to accept a generic System.Management.Automation.Language.Ast and you having to return nothing then

Hi @rjmholt
Thanks for your quick answer!
I have tried to use the function without the context of the Scriptanalyzer module and here are my results:
I use the following function to simulate an AST:
Function Test-Something {
<#
    .NOTES
    asdfjaklsfafasdf k
#>

[CmdletBinding()]
    Param(
        [Parameter(Mandatory=$true)]
        [string] $Word
    )
    Write-Host "This is a $Word"
}

I load that function in my console and then get the AST in a variable like this:
$CommandAST = (Get-Command -Name Test-Something).ScriptBlock.Ast

I then import the Scriptanalyzer module in order to have the type '[Microsoft.Windows.Powershell.ScriptAnalyzer.Generic.DiagnosticRecord]' available.
Next I load my rule function which is the following:
<#
.SYNOPSIS
    Adds a .SYNOPSIS keyword in your comment-based help.
.DESCRIPTION
    Comment-based help is written as a series of comments. You can write comment-based help topics for end users to better understand your functions. Additionally, it’s better to explain the detail about how the function works.
    To fix a violation of this rule, add a .SYNOPSIS keyword in your comment-based help. You can get more details by running “Get-Help about_Comment_Based_Help” command in Windows PowerShell.
.EXAMPLE
    Measure-HelpNote -FunctionDefinitionAst $FunctionDefinitionAst
.INPUTS
    [System.Management.Automation.Language.FunctionDefinitionAst]
.OUTPUTS
    [Microsoft.Windows.Powershell.ScriptAnalyzer.Generic.DiagnosticRecord[]]
.NOTES
    Reference: Writing Help and Comments, Windows PowerShell Best Practices.
#>
function Measure-HelpSynopsis
{
    [CmdletBinding()]
    [OutputType([Microsoft.Windows.Powershell.ScriptAnalyzer.Generic.DiagnosticRecord[]])]
    Param
    (
        [Parameter(Mandatory = $true)]
        [ValidateNotNullOrEmpty()]
        [System.Management.Automation.Language.FunctionDefinitionAst]
        $FunctionDefinitionAst
    )

    Process
    {
        $results = @()

        try
        {
            #region Define predicates to find ASTs.

            # Finds CmdletBinding attribute.
            [ScriptBlock]$predicate = {
                param ([System.Management.Automation.Language.Ast]$Ast)

                [bool]$returnValue = $false

                if ($Ast -is [System.Management.Automation.Language.AttributeAst])
                {
                    [System.Management.Automation.Language.AttributeAst]$attrAst = $ast;
                    if ($attrAst.TypeName.Name -eq 'CmdletBinding')
                    {
                        $returnValue = $true
                    }
                }

                return $returnValue
            }

            #endregion

            # Return directly if function is not an advanced function.
            [System.Management.Automation.Language.AttributeAst[]]$attrAsts = $FunctionDefinitionAst.Find($predicate, $true)
            if ($FunctionDefinitionAst.IsWorkflow -or !$attrAsts)
            {
                return $results
            }

            if (!$FunctionDefinitionAst.GetHelpContent().Synopsis)
            {
                $result = New-Object `
                            -Typename "Microsoft.Windows.PowerShell.ScriptAnalyzer.Generic.DiagnosticRecord" `
                            -ArgumentList $Messages.MeasureHelpSynopsis,$FunctionDefinitionAst.Extent,$PSCmdlet.MyInvocation.InvocationName,Warning,$null

                $results += $result
            }

            return $results
        }
        catch
        {
            $PSCmdlet.ThrowTerminatingError($PSItem)
        }
    }
}

And then I run my Function against the variable '$CommandAST':
Measure-HelpSynopsis -FunctionDefinitionAst $CommandAST

The Result of this being the following:
RuleName                            Severity     ScriptName Line  Message
--------                            --------     ---------- ----  -------
Measure-HelpSynopsis                Warning                 1

This seems fine to me... I guess the message doesn't get filled in cause I don't use the scriptanalyzer module but just the function, but this seems to be working as expected.
Can you reproduce this, or maybe see an error in this?

Hi,
Is there any information from me you would need to take another look at this?
I would be happy to provide more info if needed.
Cheers,
Kevin

@bateskevin thanks for trying that and providing more information, unfortunately we haven't had the capacity to dig deeper into where the issue would be occurring and likely wont in the immediate future since our focus is looking forward to PSScriptAnalyzer 2.0...looks like the next step would be to debug the issue in ScriptAnalyzer--which we may get to but I dont want to set expectations of that happening in the near future...thanks!

@SydneyhSmith I understand your plans to concentrate on the release of v2. However it is a bit disappointing to just be left behind with my issues here. Is there any documentation on how I can debug an Issue in PSScriptAnalyzer?

One thing you can try is running it with verbose:
> Invoke-ScriptAnalyzer -path .\ex.ps1 -CustomRulePath .\myrule.psm1 -Verbose
VERBOSE: Settings object could not be resolved.
VERBOSE: Checking module 'C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\myrule.psm1' ...
VERBOSE: Found Assembly: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\out\PSScriptAnalyzer\1.19.1\PSv7\Microsoft.PowerShell.CrossCompatibility.dll
VERBOSE: Loading Assembly:Microsoft.PowerShell.CrossCompatibility
VERBOSE: Found Assembly: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\out\PSScriptAnalyzer\1.19.1\PSv7\Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules.dll
VERBOSE: Loading Assembly:Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules
VERBOSE: Found Assembly: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\out\PSScriptAnalyzer\1.19.1\PSv7\Microsoft.Windows.PowerShell.ScriptAnalyzer.dll
VERBOSE: Loading Assembly:Microsoft.Windows.PowerShell.ScriptAnalyzer
VERBOSE: Found Assembly: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\out\PSScriptAnalyzer\1.19.1\PSv7\Microsoft.PowerShell.CrossCompatibility.dll
VERBOSE: Loading Assembly:Microsoft.PowerShell.CrossCompatibility
VERBOSE: Found Assembly: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\out\PSScriptAnalyzer\1.19.1\PSv7\Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules.dll
VERBOSE: Loading Assembly:Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules
VERBOSE: Found Assembly: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\out\PSScriptAnalyzer\1.19.1\PSv7\Microsoft.Windows.PowerShell.ScriptAnalyzer.dll
VERBOSE: Loading Assembly:Microsoft.Windows.PowerShell.ScriptAnalyzer
VERBOSE: Found Assembly: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\out\PSScriptAnalyzer\1.19.1\PSv7\Microsoft.PowerShell.CrossCompatibility.dll
VERBOSE: Loading Assembly:Microsoft.PowerShell.CrossCompatibility
VERBOSE: Found Assembly: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\out\PSScriptAnalyzer\1.19.1\PSv7\Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules.dll
VERBOSE: Loading Assembly:Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules
VERBOSE: Found Assembly: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\out\PSScriptAnalyzer\1.19.1\PSv7\Microsoft.Windows.PowerShell.ScriptAnalyzer.dll
VERBOSE: Loading Assembly:Microsoft.Windows.PowerShell.ScriptAnalyzer
VERBOSE: Found Assembly: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\out\PSScriptAnalyzer\1.19.1\PSv7\Microsoft.PowerShell.CrossCompatibility.dll
VERBOSE: Loading Assembly:Microsoft.PowerShell.CrossCompatibility
VERBOSE: Found Assembly: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\out\PSScriptAnalyzer\1.19.1\PSv7\Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules.dll
VERBOSE: Loading Assembly:Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules
VERBOSE: Found Assembly: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\out\PSScriptAnalyzer\1.19.1\PSv7\Microsoft.Windows.PowerShell.ScriptAnalyzer.dll
VERBOSE: Loading Assembly:Microsoft.Windows.PowerShell.ScriptAnalyzer
VERBOSE: Performing the operation "Analyzing path with Recurse=False" on target "C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\ex.ps1".
VERBOSE: Performing the operation "Analyzing file C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\ex.ps1" on target "C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\ex.ps1".
VERBOSE: Analyzing file: C:\Users\Robert Holt\Documents\Dev\Microsoft\PSScriptAnalyzer\ex.ps1
VERBOSE: Running myrule\Measure-HelpSynopsis rule.

PSScriptAnalyzer is an ordinary PowerShell binary module though, so with the module source and VSCode you can debug it by building from source, attaching a debugger and running it:

./build.ps1
ipmo ./out/PSScriptAnalyzer
attach VSCode debugger to the current PowerShell process (given by $PID)
Invoke-ScriptAnalyzer

Stepping through your function as originally given, the function is run but the message is empty, so it fails this check:
https://github.com/PowerShell/PSScriptAnalyzer/blob/c78f5a60c1f49a5e767286ff6323a2ec0788991a/Engine/ScriptAnalyzer.cs#L1287-L1294
That means no diagnostic is emitted.
I suspect this is due to you using $Messages.MeasureHelpSynopsis. PowerShell variables have dynamic, rather than lexical, scope. So defining that variable outside your function won't work at call time. Instead you need to either define it locally or use a $script: variable: $script:Messages.MeasureHelpSynopsis.

Hi @rjmholt,
Thanks a lot for your last comment! The $Message variable was the problem. The example you pasted worked for me aswell.


Visual indicator for saved comments

By this I mean some persistent thing to tell you whether a comment is saved or not.

Same as #315


Accession Id - Rest Endpoint to retrieve studies based on Gcst

As developer
I want an api endpoint
So that when I send a GET request, hateoas, paginated list of all studies associated to a given accessionId in the database is returned in JSON Format
Management Rules:
Rule 1: Endpoint - /v2/studies/{accessionId}/studies
Rule 2: HTTP Request Method - GET
Rule 3: HATEOAS, with filer, sorting, pagination, and sizing
Rule 4: Endpoint should accept filter, and sort parameters as in /studies?accession=...&page=0&size=20&sort=...
Rule 5: Search filter should be available for: accession, reported-trait, trait, background-trait, discovery-sample-number, replication-sample-number
Rule 6: Sort feature should be available for: discovery-sample-number, replication-sample-number, association-count, summary-statistics
Rule 7: Returned Study JSON entity must include: Study accession, Reported trait, Trait, Background trait, Discovery sample number and ancestry, Replication sample number and ancestry, Association count, and Summary statistics Availability
Acceptance Tests:
Given no parameter
When the front end sends a GET request to the endpoint
Hateoas compliant list of studies is returned in the specified JSON Format
Given sorting, pagination, and/or some search and filter parameters
When the front end sends a GET request to thesame endpoint
Hateoas compliant filtered list of studies satisfying the conditions in the url parameter must be returned


EventParser fails

It seems like the event parser is getting confused by my logs. Here is a snippet demonstrating the problem: https://gist.github.com/eyevz/5ec6bab673f4b2d5886bac32da6f3ce4

Taking a look now @eyevz. Would you mind checking if it works fine with the parser in anchor-ts?

Have not checked anchor-ts yet, need to finish something first. Just a note confirming that the event coder is fine, the problem is in event parser.


fix: set UWP min version to 10.0.10586.0

Do you want to request a feature or report a bug?
Bug
What is the current behavior?

In this you have the TargetPlatformVersion, but you also probably want to specify the TargetPlatformMinVersion. It defaults to 10.0.10240.0...and that version isn't even in support anymore :)

https://github.com/reactiveui/ReactiveUI/blob/ece4833e2712048851ac01e7b6285fd33681ebeb/src/Directory.build.targets#L10
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
See https://github.com/akavache/Akavache/issues/370
What is the expected behavior?
See https://github.com/akavache/Akavache/issues/370
What is the motivation / use case for changing the behavior?
See https://github.com/akavache/Akavache/issues/370

@ghuntley,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Coverage remained the same at 70.458% when pulling 53a7c0504809238f0bb64100d3be7ea2468b6dea on SetMinPlatformVer into b0739da6bb5dc20e46bec0d8bc26f36b75ff3973 on develop.

Fixes https://github.com/reactiveui/ReactiveUI/issues/1443


Question: TileGrid.tileSizes/resolutions

Thanks for the help earlier. My application has become more complex. I am attempting to set a range of TileGrid.tileSizes and TileGrid.resolutions, but I'm not sure what goes into those properties.
I have four levels of tiles:

1x1
6x4
12x8
24x24

Right now the default view is showing 1x1. As I zoom out, the large tiles should load.
Also, as I zoom in, I'd like to switch to another tile level, which is 1x1, but SVG instead of PNG. I'm not sure if multiple identical tileSizes are supported.
Currently the 1x1 is 860x860px and the 6x4 is 5160x3440px, etc. I expect I'll render those larger tiles at a size closer to their on-screen size.
Example: https://endquote.com/post/drawing_series/
Tiles: https://static.endquote.com/drawing_series/
Source: https://github.com/endquote/endquote-next/blob/master/public/posts/drawing_series/DrawingMap.jsx#L17

Went with Zoomify tiles instead.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_d4q2pt0cqm/clone/recipe/meta.yaml:22: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_d4q2pt0cqm/clone/recipe/meta.yaml:29: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_d4q2pt0cqm/clone/recipe/meta.yaml:29: missing_imports_or_run_test_py: Python packages require imports or a python test file in tests.
WARNING: /tmp/abs_d4q2pt0cqm/clone/recipe/meta.yaml:36: missing_description: The recipe is missing a description
ERROR: /tmp/abs_d4q2pt0cqm/clone/recipe/meta.yaml:36: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_d4q2pt0cqm/clone/recipe/meta.yaml:36: missing_dev_url: The recipe is missing a dev_url
Errors were found


Keyboard handlers within message kit

I have a chat view embedded with in my app hooked up to firebase. Works great. Thank you.
The issue I am having is the client wants the input for the chat to be about mid screen.
I have  hidden the input bar accessory because there seems to be no way to embed it in the mid screen view with the chat. It that is possible let me know.
Currently when the keyboard appears for my text field it covers the text field.
Is there anyway to turn off the keyboard handlers in MessageKit. I have my own and the are working it just the ones in MessageKit are taking precedence.
The attached is a mock of the issue. Actual app under NDA... but the its the same issue

Hey @LincolnDickerson
it is simple to hide keyboard
func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {
    if self.messageInputBar.inputTextView.becomeFirstResponder(){
        self.messageInputBar.inputTextView.resignFirstResponder()
    }
}

if you want hide keyboardHandler then self.messageInputBar.inputTextView.isHidden = true


personal_access_tokens_tokenable_type_tokenable_id_index

Laravel Version: 9.8.1
PHP Version: 8.0.13
Database Driver & Version: WAMP server using 10.6.5-MariaDB - mariadb.org binary distribution
& installation included Laravel Breeze

Description:
I am new user (front-end coder) trying to create my first migration using this tutorial: https://www.youtube.com/watch?v=MYyJ4PuL4pY
While following these steps almost exactly (except that I'm on WAMP and Windows), I encountered an issue in which migration fails at personal_access_tokens, ~minute 53 in video.
Along the way, I discovered that there are 2 migration files for this: one in \database\migrations and one in \vendor\laravel\sanctum\ \database\migrations.  It took me several hours to find this solution on codegrepper, which stopped the error, but I am unsure if it will cause me some other issue later:
//Update your /app/Providers/AppServiceProvider.php to contain:

use Illuminate\Support\Facades\Schema;

public function boot() {
    Schema::defaultStringLength(191);
}

Steps To Reproduce:

Create a very simple model, ie for 'listings'
Create a migration:  php artisan make:migration create_listings_table
Run php artisan migrate
Receive error about personal_access_tokens_table:  SQLSTATE[42S01]: Base table or view already exists
Run php artisan migrate:fresh
Receive new error:  SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes (SQL: alter table 'personal_access_tokens' add index 'personal_access_tokens_tokenable_type_tokenable_id_index'('tokenable_type', 'tokenable_id'))
After adding the solution above, I am finally able to create a new table.

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


Why I get check icon next to country

I press customCountry button which launches country list. For some strange issue I can see one country as already being checked... In some devices this country is in the middle of the list, and on some it is the first country.
Also if I remove countries from list or add some, it also affects country List and makes a single country checked. I would like to know why some countries become selected even without pressing them? It is definitively a bug which really creates problems for our use case... I would like to contribute for fixing this version.

The library sets a default country which is derived from the current region code.

Can I change that? Because it does not make sense.. Also If I removed that country, which was derived from current region code, from countryPicker countries array, then some random country will be checked.. It is strange behavior. Why it is not optional?

There's a default country because the library has to always show a country on the view when added as a subview. You may not find this very useful if you use the library as a standalone picker.

Oh ok... I will switch then for a different picker.. It is strange however that such functionality is not optional. This issue will be definitely addressed by other developers soon. It does not make sense, that current country should be checked. It can be the top in the list, but definitely not checked, because it confuses users.

Since you'll be using a different picker, I consider this issue resolved and will be closing it.

I would like to contribute and fix this strange behavior, but it seems you won't approve such changes. Am I clear?

I am very happy to review a PR with the fix.
How do you intend to approach the issue?

I would create an optional method similar to yours, which would apply tick icon or not initially :)
Overall I like your library and don't hesitate to use it in our production code as a shared library, which really improves this library popularity, but this initial tick icon does create problems for us

I don't understand what you mean by creating an optional method, could you kindly explain further?

:) I refered to a boolean(checkMarkEnabled) which would be set as either true or false, depending on the client needs. If checkMarkEnabled is set to false, then in the beggining no country is selected. Default is true, so it will not change functionality of the framework.
However, if someone would need to remove checkMark, then they could do that :) It is easy to do, I am just really busy with jobs and stuff... :(

Note: This feature is now available in version 3.0.2


React: refactor cards in line with Twig

See more details here in #447

This is a duplicate. Closing in favor of #470


Rename transaction

Hello,
We're using elastic on Android and for now every transactions are under something like GET, POST, etc.
I'd like to rename my transactions to GET my-service.be/data for example to make it easier to find.
Is it possible? If not, is it planned in a future release?
Thanks!

Hi @baudouxbenjamin . The names of the spans generated by this instrumentation should comply with the OpenTelemetry HTTP semantic conventions.
If you check that link, you'll see that the guidance for client http spans is:

HTTP client spans have no http.route attribute since client-side instrumentation is not generally aware of the “route”, and therefore HTTP client span names SHOULD be {method}.

So I don't think we have any real intention to change this. You can always put manual instrumentation around these call sites, if you'd like to get more details in the name.

I agree we should stick to the semconv, however, it does mention that we could add the HTTP route (if we knew what it was) though we don't know, so it makes sense we don't do it and I don't think OTel Android should try to make any "smart" decisions on what the HTTP route should look like.
Still, I think we could at least provide some APIs to allow users to add the route themselves, maybe in a similar fashion to what someone's suggested doing for screen names.

There has been some progress around this issue in the Java SIG and also here. I'm planning to add a config option for it soon.


Update version of chefspec used

Concerns:

Deprecate ChefSpec::Runner.new - you should specify if you want a SoloRunner or ServerRunner
Deprecate ChefSpec::Runner.define_runner_method in favor of ChefSpec.define_matcher

These are the two major changes that would require us to refactor our cookbook tests.

Excellent points @derekschultz.  Note that the first item you mention, in the latest version of chefspec he does provide a deprecation class, such that Runner.new will default to SoloRunner.new: https://github.com/sethvargo/chefspec/blob/dfb89e09e3a2685d036b389dff35a7624b4f6c77/lib/chefspec/deprecations.rb#L31

@derekschultz looks like your second item was addressed as well:
https://github.com/sethvargo/chefspec/blob/dfb89e09e3a2685d036b389dff35a7624b4f6c77/lib/chefspec/deprecations.rb#L26

@jtslear -- Interesting, thanks for pointing that out. I'd like to test this first: update the version in the gemspec locally, then test a cookbook by updating the Gemfile to be:
source 'https://rubygems.org'
#gem 'cookbook-development', :git => 'https://github.com/RallySoftware-cookbooks/cookbook-development'
gem 'cookbook-development', :path => '../cookbook-development

Then I'll be :+1:

The only thing I ask is that according to semver the major version number should be bumped...


Add draft page for microcosm-http

This is the draft for microcosm-http. A standard way to do AJAX across multiple platforms using Microcosm.
Probably the best doc to look at is the readme:
https://github.com/vigetlabs/microcosm/blob/75c582756ff7a6bfb686b61326a5b36bdde315a6/packages/microcosm-http/README.md

Codecov Report

Merging #412 into microcosm-layers will increase coverage by 2.97%.
The diff coverage is n/a.

@@                 Coverage Diff                  @@
##           microcosm-layers     #412      +/-   ##
====================================================
+ Coverage             81.91%   84.88%   +2.97%
====================================================
  Files                    45       45
  Lines                  1305     1297       -8
  Branches                244      241       -3
====================================================
+ Hits                   1069     1101      +32
+ Misses                  197      163      -34
+ Partials                 39       33       -6

Impacted Files
Coverage Δ

packages/microcosm/src/addons/action-form.js
100% <0%> (+100%)
:arrow_up:

Continue to review full report at Codecov.

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


add files without losing tags

Dell says fetch the item, send the item JSON back in with the post - see Dell's pysb package for an example

https://my.usgs.gov/stash/projects/SBE/repos/pysb/browse

:+1: :100:

see #74

@aappling-usgs what fxn in the python client should we look at?

I'm going to close this and continue discussion in #74 (reopen if I misunderstand and this is a separate issue)


[v1.3.0] Coinomics module

Closes: #40

nice

Awesome

nice

Great project

Good performance

Lfg 🫶

great indeed

great and exciting project to be part of it

How do I get the validator role??

Ok 👍

Excellent project

Wonderful project

🙌Great project 💚🌙


Missing headers in include/android/

run project and get some errors related to android/text
Showing All Errors Only
Undefined symbol: AndroidTextTextUtils_isEmptyWithJavaLangCharSequence
Undefined symbol: AndroidTextTextUtils_joinWithJavaLangCharSequence_withJavaLangIterable
Undefined symbol: AndroidUtilLog_dWithNSString_withNSString
It seems that some folders and headers are missing from the latest code
by using the "make -j8 dist" command, as compared to the j2objc-2.8.zip release.
The missing folders and headers are:
/include/android/os
/include/android/test
/include/android/text
/include/android/util
I'm wondering if you could help me resolve this issue.
Thank you for your help.

As a workaround, try copying the missing headers from 2.8 into a separate directory, then copying the lib/libandroid_util.a file to that directory, and include that directory in your project's include and lib paths. These files haven't changed since 2.8.

As a workaround, try copying the missing headers from 2.8 into a separate directory, then copying the lib/libandroid_util.a file to that directory, and include that directory in your project's include and lib paths. These files haven't changed since 2.8.

Thanks.
it works in iphone after copying the 2.8.zip libandroid_util.a &
related directories into the project, add lib & header search paths,
But it cannot run in simulator because of [arm64](ld: symbol(s) not found for architecture arm64).
could it be resolved?


Extend k_work_q_user_start() to include k_thread options argument

Hi all,
In a Zephyr application I am working on we have a module which employs the Zephyr v2.1.0 work_q feature to simplify thread management for an internal communications stack. We have recently begun development of features in our system which require floating point hardware support, in this case requiring all threads of our system to support K_FP_REGS as a k_thread option to prevent faults from occurring.
The issue I've come across is that the k_thread options for user mode work_qs as implemented in the current k_work_q_user_start() appear to be hard coded to K_USER | K_INHERIT_PERMS with no way to modify them outside of work_q.c. I would like to be able to modify the k_thread options provided at this step to include K_FP_REGS and I'm not sure this is something it's currently possible to do.
It is possible that I'm not aware of the preferred method of controlling these thread options. If there are expected ways to accomplish what I'm asking for please let me know and I will be happy to try them. In the absence of such a path I would like to provide the attached example as a simple solution to enable what I'm requesting.
work_q change example.txt
The new function k_work_q_user_start_ex() is simply a renamed and extended version of the original k_work_q_user_start(). The new version of the original function consumes this extended and renamed version using the original k_thread options. In this way existing consumers of this function will experience no change, while those looking to use the new arg field can do so. This is an example and by no means the only way this can be solved. Not included in this change is the additional prototype required in kernel.h.
Thank you for your time. If there are any questions or suggestions please let me know!
-Erik

@peter-mitsis  can you please look into this and see if that is still valid?


Object pickable grab feature without reparenting

The current implementation moves the grabbed object with the controller by reparenting it under the controller.
This is inconvenient since it makes objects disappear from the node tree so it is impossible to write simple code that depends on objects staying where they were created.
We can get this the same effect by creating a RemoteTransform node under the controller and pointing it to the object that has been grabbed.  (It's not possible to reuse the same RemoteTransform over and over again since it does not allow the remote_path value to be set to null.)

My testing shows the RemoteTransform works fine. You may wish to exclude the .import files as the changes were purely due to the gles3/gles2 project settings. The Viewport_2D_in_3D.tscn changes look to be a minor mismatch with the collision_layer settings between the top-level viewport and the StaticBody which the tool-script should have kept in sync.

Yup, agree with not having the .import files changes, those mostly relate to whether you open the project in 3.4.x or 3.5.

@goatchurchprime if you can change it so the .import files are not part of the PR I can merge this :)

@Malcolmnixon seeing you're doing the work on the ranged grab and making changes in this area at the moment, maybe you can combine @goatchurchprime change? Or maybe we should merge it and just undo the import file changes.
On the import file changes, I think we should try and stick to making sure the import file contents match what the current stable release of Godot expects. It's pretty unimpactful as it generally unintentional deviations from defaults now that Godot no longer saves the value of properties that haven't changed, but occasionally something unsupported by older versions sneaks in. Godot tents to ignore those but still....

I'm going to make the grab mechanic an enum as well - parenting, remote-transform, and possibly expanding to velocity tracking in a future pull request.
This is an area where things start to get interesting quickly because we're possibly going to need "grab-points" in the near future which might even have the ability to override the hand-pose (such as holding a gun) and if the object is velocity-tracked to prevent it from ghosting through walls, then we actually want the hand-model to stay with the object. As such we may expand this list of grab mechanics to include childinf the hand to the model, or remote-transforming the hand by the model.
Either way these features will take time to add, but I will include the chilling vs remote-transforming for now.

This capability has been added to the ranged-grab pull request. It now supports both Remote-Transform and Reparenting as the hold mechanic.

I shall close this than, thanks @Malcolmnixon and @goatchurchprime


Add netbox files

Adds netbox configuration items.

Sorry this has taken so long
First and most important thing, is there any reason this needs its own Postgres instance? If there's not then it should be using the shared one. It'll need to be on the docker network postgres_net to reach it. From the net box directory you can use ../postgresql/bin/mkdb.sh to create the database and credentials. This will also add a line to the .env file that will enable automatic database backups.
All the docker volumes should be bind mounts that expose the files in the host filesystem. If the files contain persistent state that goes in ../lib/netbox; if they're transient runtime state that's in ../run/netbox; logs go in ../log/netbox. Conf is fine the way it is.
All .env files should have a .env.example which can be checked into the repo. A user should be able to clone the repo and configure applications in it without modifying checked in files, so we need to get the .env files out of it and update .gitignore to keep them out of the repo.


About Support Text-Graph Used in Figure 6

@matanr Thanks for your valuable contributions.
Regarding Figure 6 in the paper, it is evident that CapeX performs exceptionally well across various levels of text and pose-graph abstractions. However, the input details are somewhat unclear. I am curious whether the text and pose-graphs utilized here are based on the entire body skeleton or just a segment of it. Could you provide some additional insights?

Furthermore, if the visualization script could also be provided, it would be greatly appreciated.
Best regards,

Thank you for your interest and positive feedback!
In each of the six examples, the input skeleton is drawn directly onto the output image. For instance:

In the leftmost horse image, the provided text-graph consists of a single node: animal (node 0) with no edges.

In the middle horse image, the provided text-graph is a graph with 7 nodes. The edges are visible in the image; for example, the head (node 0) is connected to the body (node 1).

I hope this explanation clarifies things.
Regarding the visualization script, have you tried using demo_text.py?

I think my question has been addressed.
Regarding the visualization script, I will look into using demo_text.py as you suggested.
Thank you very much for your detailed explanation and for taking the time to clarify my doubts.
Best regards,


Where causes code to be called twice

Take the code
class Foo {
  num { _num }
  construct new(num) {
    _num = num
    System.print("Creating foo")
  }
}

var bar = [1, 2].map{|x| Foo.new(x) }.where{|x| x.num > 0}.toList

If run, it prints "Creating foo" 4 times. Intuitively I expect it to call only 2 times, and I tested the same thing using C# linq and it is called 2 times.
Is this possible to fix with how WhereSequence works?
At the very least it's something to look out for in case your construction is resource intensive.

Interesting! Sequences are evaluated lazily, which seems to be involved.
If you resolve the map sequence first via toList it prints twice only, since the where is only on the list
var bar = [1, 2].map{|x| Foo.new(x) }.toList.where{|x| x.num > 0}.toList

This is to be expected, since the filtering done by where involve accessing
the value, in addition of the acces for flattening to list. Effectively it
doubles the access to the value, resulting in the effect you see.
You can either do an intermediate flattening as proposed (or any other form
of memoization), or if possible rearrange the order of map so that they
happens last in the chain.

I thought this was surprising too - as mhermier says it is because of the way WhereSequence calls iteratorValue on its 'upstream' sequence (at least) once to find a value that satisfies the filter and once to actually get the value (see below). Specifically iteratorValue calls back though the chain every time, in this case calling the map function on the way to the source list [1,2]
If you have two where clauses then it prints 'Creating foo' six times
var bar = [1, 2].
 map{|x| Foo.new(x) }.
 where{|x| x.num > 0}.
 where{|x| x.num < 10}.
 toList

An option would be to have WhereProtocol memoise the last result but assuming you don't want to change the code, would it be possible to make this a bit clearer in the iterator protocol docs?
Thanks!
https://github.com/wren-lang/wren/blob/c2a75f1eaf9b1ba1245d7533a723360863fb012d/src/vm/wren_core.wren#L168-L182


Added support for configuring route options with LinkGenerator

[Fixes #547] Link generation: Expose options to configure link generation at the call site and globally

https://github.com/aspnet/Routing/commit/5f1631ab46e415cadf3a12ceef6c6164a06ac275


Standardise neighbour/neighbor spelling

Description
Both spelling alternatives are used in various places, and it's a bit confusing especially if this happens for function names and parameters.
$ grep -ri --exclude-dir "__pycache__" "neighbor" stellargraph
stellargraph/core/graph.py:    def neighbors(
stellargraph/core/graph.py:        return self._graph.neighbors(
stellargraph/core/graph_networkx.py:    def neighbors(
stellargraph/core/graph_networkx.py:        return self.neighbors(node, include_edge_weight, edge_types)
stellargraph/core/graph_networkx.py:        return self.neighbors(node, include_edge_weight, edge_types)
stellargraph/layer/graph_attention.py:            # Linear combination with neighbors' features [YT: see Eq. 4]
stellargraph/layer/graph_attention.py:            # Linear combination with neighbors' features [YT: see Eq. 4]
stellargraph/layer/hinsage.py:        * input_neighbor_tree: A list of (node_type, [children]) tuples that specify the
stellargraph/layer/hinsage.py:            self.subtree_schema = kwargs["input_neighbor_tree"]
stellargraph/layer/hinsage.py:        neighbor_sizes = list(it.accumulate([1] + self.n_samples, op.mul))
stellargraph/layer/hinsage.py:                cnode: (neighbor_sizes[level], self.input_dims[stree[cnode][0]])
stellargraph/data/explorer.py:    def neighbors(self, node):
stellargraph/data/explorer.py:        return list(self.graph.neighbors(node))
stellargraph/data/explorer.py:            neighbours = self.neighbors(current_node)
stellargraph/data/explorer.py:                for neighbor in self.graph.neighbors(node):
stellargraph/data/explorer.py:                    for weight in self.graph.edge_weights(node, neighbor):
stellargraph/data/explorer.py:                                    weight, node, neighbor
stellargraph/data/explorer.py:                                    node, neighbor, weight
stellargraph/data/explorer.py:                                    node, neighbor, weight
stellargraph/data/explorer.py:                                node, neighbor, list(wts)
stellargraph/data/explorer.py:                neighbours = self.neighbors(node)
stellargraph/data/explorer.py:                        neighbours = self.neighbors(current_node)
stellargraph/data/explorer.py:                        neighbours = self.neighbors(current_node)
stellargraph/data/explorer.py:                        self.neighbors(cur_node) if cur_node is not None else []
stellargraph/data/edge_splitter.py:                            neighbours = list(nx.neighbors(self.g, v))
stellargraph/data/edge_splitter.py:                            neighbours = list(nx.neighbors(self.g, v))

vs
$ grep -ri --exclude-dir "__pycache__" "neighbour" stellargraph
stellargraph/core/graph.py:        Obtains the collection of neighbouring nodes connected
stellargraph/core/graph.py:            include_edge_weight (bool, default False): If True, each neighbour in the
stellargraph/core/graph.py:                via the provided edge types when collecting neighbours.
stellargraph/core/graph.py:            iterable: The neighbouring nodes.
stellargraph/core/graph.py:        Obtains the collection of neighbouring nodes with edges
stellargraph/core/graph.py:        neighbours are treated as both in-nodes and out-nodes.
stellargraph/core/graph.py:            include_edge_weight (bool, default False): If True, each neighbour in the
stellargraph/core/graph.py:                via the provided edge types when collecting neighbours.
stellargraph/core/graph.py:            iterable: The neighbouring in-nodes.
stellargraph/core/graph.py:        Obtains the collection of neighbouring nodes with edges
stellargraph/core/graph.py:        neighbours are treated as both in-nodes and out-nodes.
stellargraph/core/graph.py:            include_edge_weight (bool, default False): If True, each neighbour in the
stellargraph/core/graph.py:                via the provided edge types when collecting neighbours.
stellargraph/core/graph.py:            iterable: The neighbouring out-nodes.
stellargraph/core/graph_networkx.py:NeighbourWithWeight = namedtuple("NeighbourWithWeight", ["node", "weight"])
stellargraph/core/graph_networkx.py:        # 1. node ID of None (representing sampling for a missing neighbour)
stellargraph/core/graph_networkx.py:                return NeighbourWithWeight(
stellargraph/core/schema.py:        for neighbours up to n_hops away.
stellargraph/core/schema.py:            num_samples: A list of integers that are the number of neighbours
stellargraph/mapper/sequences.py:            batch_feats (list): Node features for nodes and neighbours sampled from a
stellargraph/mapper/sequences.py:            batch_feats (list): Node features for nodes and neighbours sampled from a
stellargraph/mapper/sequences.py:        sampler (UnsupersizedSampler):  An object that encapsulates the neighbourhood sampling of a graph.
stellargraph/mapper/sequences.py:            batch_feats<list>: Node features for nodes and neighbours sampled from a
stellargraph/mapper/sampled_node_generators.py:    DirectedBreadthFirstNeighbours,
stellargraph/mapper/sampled_node_generators.py:        Sample neighbours recursively from the head nodes, collect the features of the
stellargraph/mapper/sampled_node_generators.py:        # Resize features to (batch_size, n_neighbours, feature_size)
stellargraph/mapper/sampled_node_generators.py:        self.sampler = DirectedBreadthFirstNeighbours(
stellargraph/mapper/sampled_node_generators.py:        Sample neighbours recursively from the head nodes, collect the features of the
stellargraph/mapper/sampled_node_generators.py:        # Each 'slot' represents the list of nodes sampled from some neighbourhood, and will have a corresponding
stellargraph/mapper/sampled_node_generators.py:        Sample neighbours recursively from the head nodes, collect the features of the
stellargraph/mapper/sampled_node_generators.py:        # Resize features to (batch_size, n_neighbours, feature_size)
stellargraph/mapper/sampled_link_generators.py:        num_samples (list): List of number of neighbour node samples per GraphSAGE layer (hop) to take.
stellargraph/mapper/sampled_link_generators.py:        # The sampler used to generate random samples of neighbours
stellargraph/mapper/sampled_link_generators.py:        Sample neighbours recursively from the head nodes, collect the features of the
stellargraph/mapper/sampled_link_generators.py:        # Resize features to (batch_size, n_neighbours, feature_size)
stellargraph/mapper/sampled_link_generators.py:        num_samples (list): List of number of neighbour node samples per GraphSAGE layer (hop) to take.
stellargraph/mapper/sampled_link_generators.py:        # The sampler used to generate random samples of neighbours
stellargraph/mapper/sampled_link_generators.py:        # Resize features to (batch_size, n_neighbours, feature_size)
stellargraph/mapper/sampled_link_generators.py:        # Resize features to (batch_size, n_neighbours, feature_size)
stellargraph/mapper/sampled_link_generators.py:        Sample neighbours recursively from the head nodes, collect the features of the
stellargraph/layer/hinsage.py:            input_shape (list of list of int): Shape of input per neighbour type.
stellargraph/layer/hinsage.py:        # Weight matrix for each type of neighbour
stellargraph/layer/hinsage.py:        # If there are no neighbours (input_shape[x][2]) for an input
stellargraph/layer/hinsage.py:            - x[1+r]: tensors of neighbour features each of shape (n_batch, n_head, n_neighbour[r], n_feat[r])
stellargraph/layer/hinsage.py:            # The neighbour input tensors for relation r
stellargraph/layer/hinsage.py:            # If there are neighbours aggregate over them
stellargraph/layer/hinsage.py:        # Sum the contributions from all neighbour averages shape (n_batch, n_head, n_out_neigh)
stellargraph/layer/hinsage.py:        # Concatenate self + neighbour features, shape (n_batch, n_head, n_out)
stellargraph/layer/hinsage.py:        and 10 neighbours sampled at each layer using an existing :class:`StellarGraph` object `G`
stellargraph/layer/hinsage.py:        with hidden node sizes of 8 and 4 and 5 neighbours sampled at each layer::
stellargraph/layer/hinsage.py:        # Neighbourhood info per layer
stellargraph/layer/hinsage.py:                "n_samples, input_dim, multiplicity, and input_neighbour_tree must be specified."
stellargraph/layer/hinsage.py:        Function to evaluate the neighbourhood tree structure for every layer. The tree
stellargraph/layer/hinsage.py:            input_tree: Neighbourhood tree for the input batch
stellargraph/layer/hinsage.py:            List of neighbourhood trees
stellargraph/layer/hinsage.py:                # The shape of the head node is used for reshaping the neighbour inputs
stellargraph/layer/hinsage.py:                # Aplly dropout and reshape neighbours per node per layer
stellargraph/layer/hinsage.py:                # Apply aggregator to head node and reshaped neighbour nodes
stellargraph/layer/hinsage.py:        # Remove neighbourhood dimension from output tensors
stellargraph/layer/hinsage.py:        Returns the input shapes for the tensors of the supplied neighbourhood type tree
stellargraph/layer/hinsage.py:            the corresponding item in the neighbourhood type tree (self.subtree_schema)
stellargraph/layer/graphsage.py:                and neighbour features
stellargraph/layer/graphsage.py:        # If the neighbours are zero-dimensional for any of the shapes
stellargraph/layer/graphsage.py:                "There must be at least one input with a non-zero neighbourhood dimension"
stellargraph/layer/graphsage.py:        to sampled neighbourhoods, if required.
stellargraph/layer/graphsage.py:                and neighbour features
stellargraph/layer/graphsage.py:    def aggregate_neighbours(self, x_neigh, group_idx: int = 0):
stellargraph/layer/graphsage.py:        Override with a method to aggregate tensors over neighbourhood.
stellargraph/layer/graphsage.py:            x_neigh: The input tensor representing the sampled neighbour nodes.
stellargraph/layer/graphsage.py:            group_idx: Optional neighbourhood index used for multi-dimensional hops.
stellargraph/layer/graphsage.py:        # If a neighbourhood dimension exists for the group, aggregate over the neighbours
stellargraph/layer/graphsage.py:        Override with a method to aggregate tensors over the neighbourhood for each group.
stellargraph/layer/graphsage.py:            x_neigh (tf.Tensor): : The input tensor representing the sampled neighbour nodes.
stellargraph/layer/graphsage.py:        Mean aggregator for tensors over the neighbourhood for each group.
stellargraph/layer/graphsage.py:            x_group (tf.Tensor): : The input tensor representing the sampled neighbour nodes.
stellargraph/layer/graphsage.py:        Aggregates the group tensors by max-pooling of neighbours
stellargraph/layer/graphsage.py:            x_group (tf.Tensor): : The input tensor representing the sampled neighbour nodes.
stellargraph/layer/graphsage.py:            # Pass neighbour features through a dense layer with w_pool, b_pool
stellargraph/layer/graphsage.py:            # Take max of this tensor over neighbour dimension
stellargraph/layer/graphsage.py:        Aggregates the group tensors by mean-pooling of neighbours
stellargraph/layer/graphsage.py:            x_group (tf.Tensor): : The input tensor representing the sampled neighbour nodes.
stellargraph/layer/graphsage.py:            # Pass neighbour features through a dense layer with w_pool, b_pool
stellargraph/layer/graphsage.py:            # Take max of this tensor over neighbour dimension
stellargraph/layer/graphsage.py:                and neighbour features
stellargraph/layer/graphsage.py:        # If the neighbours are zero-dimensional for any of the shapes
stellargraph/layer/graphsage.py:          inputs (List[Tensor]): Tensors giving self and neighbour features
stellargraph/layer/graphsage.py:                x[k>0]: group Tensors for neighbourhood (batch_size, head size, neighbours, feature_size)
stellargraph/layer/graphsage.py:        # If a neighbourhood dimension exists for the group, aggregate over the neighbours
stellargraph/layer/graphsage.py:            # Group transform for self & neighbours
stellargraph/layer/graphsage.py:            # Concatenate self vector to neighbour vectors
stellargraph/layer/graphsage.py:            # Add self and neighbour attn and apply activation
stellargraph/layer/graphsage.py:            # Attn coefficients, softmax over the neighbours
stellargraph/layer/graphsage.py:            # Multiply attn coefficients by neighbours (and self) and aggregate
stellargraph/layer/graphsage.py:    Different neighbour node aggregators can also be specified with the ``aggregator``
stellargraph/layer/graphsage.py:        and 10 neighbours sampled at each layer using an existing :class:`StellarGraph` object `G`
stellargraph/layer/graphsage.py:        # Compute size of each sampled neighbourhood
stellargraph/layer/graphsage.py:        self._compute_neighbourhood_sizes()
stellargraph/layer/graphsage.py:                "Mismatched lengths: neighbourhood sample sizes {} versus layer sizes {}".format(
stellargraph/layer/graphsage.py:                "Mismatched lengths: neighbourhood sample sizes {} versus layer sizes {}".format(
stellargraph/layer/graphsage.py:    def _compute_neighbourhood_sizes(self):
stellargraph/layer/graphsage.py:        sampled at each neighbourhood.
stellargraph/layer/graphsage.py:        Each hop samples from the neighbours of the previous nodes.
stellargraph/layer/graphsage.py:        self.neighbourhood_sizes = [size_at(i) for i in range(self.max_hops + 1)]
stellargraph/layer/graphsage.py:                # Reshape neighbours per node per layer
stellargraph/layer/graphsage.py:                # Apply aggregator to head node and neighbour nodes
stellargraph/layer/graphsage.py:        # Remove neighbourhood dimension from output tensors of the stack
stellargraph/layer/graphsage.py:        # Create tensor inputs for neighbourhood sampling
stellargraph/layer/graphsage.py:            Input(shape=(s, self.input_feature_size)) for s in self.neighbourhood_sizes
stellargraph/layer/graphsage.py:    Different neighbour node aggregators can also be specified with the ``aggregator``
stellargraph/layer/graphsage.py:    def _compute_neighbourhood_sizes(self):
stellargraph/layer/graphsage.py:        sampled at each neighbourhood.
stellargraph/layer/graphsage.py:        This gives rise to a binary tree of directed neighbourhoods.
stellargraph/layer/graphsage.py:        self.neighbourhood_sizes = [1] + [
stellargraph/layer/graphsage.py:        def aggregate_neighbours(tree: List, stage: int):
stellargraph/layer/graphsage.py:                    self.neighbourhood_sizes[child_slot] // num_head_nodes
stellargraph/layer/graphsage.py:                    self.neighbourhood_sizes[child_slot] // num_head_nodes
stellargraph/layer/graphsage.py:                # aggregate neighbourhoods
stellargraph/layer/graphsage.py:            stage_tree = aggregate_neighbours(stage_tree, stage)
stellargraph/layer/graphsage.py:        # Remove neighbourhood dimension from output tensors of the stack
stellargraph/data/explorer.py:    "DirectedBreadthFirstNeighbours",
stellargraph/data/explorer.py:            # Create a dict of adjacency lists per edge type, for faster neighbour sampling from graph in SampledHeteroBFS:
stellargraph/data/explorer.py:    # For neighbourhood sampling
stellargraph/data/explorer.py:        err_msg = "The neighbourhood size must be a list of non-negative integers."
stellargraph/data/explorer.py:            self._raise_error("The neighbourhood size list should not be empty.")
stellargraph/data/explorer.py:            neighbours = self.neighbors(current_node)
stellargraph/data/explorer.py:            if not neighbours:
stellargraph/data/explorer.py:                # has neighbours, so pick one to walk to
stellargraph/data/explorer.py:                current_node = rs.choice(neighbours)
stellargraph/data/explorer.py:                neighbours = self.neighbors(node)
stellargraph/data/explorer.py:                previous_node_neighbours = neighbours
stellargraph/data/explorer.py:                    elif nn in previous_node_neighbours:  # d_tx = 1
stellargraph/data/explorer.py:                if neighbours:
stellargraph/data/explorer.py:                    current_node = rs.choice(neighbours)
stellargraph/data/explorer.py:                        neighbours = self.neighbors(current_node)
stellargraph/data/explorer.py:                        if not neighbours:
stellargraph/data/explorer.py:                        # select one of the neighbours using the
stellargraph/data/explorer.py:                                for nn in neighbours
stellargraph/data/explorer.py:                        previous_node_neighbours = neighbours
stellargraph/data/explorer.py:                        current_node = neighbours[choice]
stellargraph/data/explorer.py:                        neighbours = self.neighbors(current_node)
stellargraph/data/explorer.py:                        neighbours = [
stellargraph/data/explorer.py:                            for n_node in neighbours
stellargraph/data/explorer.py:                        if len(neighbours) == 0:
stellargraph/data/explorer.py:                            # if no neighbours of the required type as dictated by the metapath exist, then stop.
stellargraph/data/explorer.py:                        # select one of the neighbours uniformly at random
stellargraph/data/explorer.py:                            neighbours
stellargraph/data/explorer.py:            n_size: <list> The number of neighbouring nodes to expand at each depth of the walk. Sampling of
stellargraph/data/explorer.py:            neighbours with replacement is always used regardless of the node degree and number of neighbours
stellargraph/data/explorer.py:                q = deque()  # the queue of neighbours
stellargraph/data/explorer.py:                    depth = cur_depth + 1  # the depth of the neighbouring nodes
stellargraph/data/explorer.py:                    neighbours = (
stellargraph/data/explorer.py:                    if len(neighbours) == 0:
stellargraph/data/explorer.py:                        neighbours = [None] * n_size[cur_depth]
stellargraph/data/explorer.py:                        neighbours = [
stellargraph/data/explorer.py:                            rs.choice(neighbours) for _ in range(n_size[cur_depth])
stellargraph/data/explorer.py:                    q.extend((sampled_node, depth) for sampled_node in neighbours)
stellargraph/data/explorer.py:            n_size: <list> The number of neighbouring nodes to expand at each depth of the walk. Sampling of
stellargraph/data/explorer.py:            neighbours with replacement is always used regardless of the node degree and number of neighbours
stellargraph/data/explorer.py:                q = list()  # the queue of neighbours
stellargraph/data/explorer.py:                    depth = depth + 1  # the depth of the neighbouring nodes
stellargraph/data/explorer.py:                            # If there are no neighbours of this type then we return None
stellargraph/data/explorer.py:                            # In case of no neighbours of the current node for et, neigh_et == [None],
stellargraph/data/explorer.py:class DirectedBreadthFirstNeighbours(GraphWalk):
stellargraph/data/explorer.py:            A list of multi-hop neighbourhood samples. Each sample expresses multiple undirected walks, but the in-node
stellargraph/data/explorer.py:            neighbours and out-node neighbours are sampled separately. Each sample has the format:
stellargraph/data/explorer.py:        self._check_neighbourhood_sizes(in_size, out_size)
stellargraph/data/explorer.py:                q = list()  # the queue of neighbours
stellargraph/data/explorer.py:                    depth = cur_depth + 1  # the depth of the neighbouring nodes
stellargraph/data/explorer.py:                    neighbours = self._sample_neighbours(
stellargraph/data/explorer.py:                        [(sampled_node, depth, slot) for sampled_node in neighbours]
stellargraph/data/explorer.py:                    neighbours = self._sample_neighbours(
stellargraph/data/explorer.py:                        [(sampled_node, depth, slot) for sampled_node in neighbours]
stellargraph/data/explorer.py:                # finished multi-hop neighbourhood sampling
stellargraph/data/explorer.py:    def _sample_neighbours(self, rs, node, idx, size):
stellargraph/data/explorer.py:        from the directed neighbourhood of the given starting node.
stellargraph/data/explorer.py:        If the neighbourhood is empty, then the result will contain
stellargraph/data/explorer.py:                neighbourhood to be sampled: 0 => in-nodes;
stellargraph/data/explorer.py:            The fixed-length list of neighbouring nodes (or None values
stellargraph/data/explorer.py:            if the neighbourhood is empty).
stellargraph/data/explorer.py:            # Non-node, e.g. previously sampled from empty neighbourhood
stellargraph/data/explorer.py:        neighbours = list(
stellargraph/data/explorer.py:        if len(neighbours) == 0:
stellargraph/data/explorer.py:            # Sampling from empty neighbourhood
stellargraph/data/explorer.py:        return [rs.choice(neighbours) for _ in range(size)]
stellargraph/data/explorer.py:    def _check_neighbourhood_sizes(self, in_size, out_size):
stellargraph/data/explorer.py:            n_size: <list> The number of neighbouring nodes to expand at each depth of the walk.
stellargraph/data/explorer.py:                "The number of hops for the in and out neighbourhoods must be the same."
stellargraph/data/epgm.py:def node_neighbours(v, edges):
stellargraph/data/epgm.py:    """Returns a list of neighbours of vertex v"""
stellargraph/data/epgm.py:def node_neighbours_extended(v, nodes, edges):
stellargraph/data/epgm.py:    """Returns a list of neighbours of vertex v"""
stellargraph/data/epgm.py:            # create a graph as dict of lists in the format (node_id: [neighbour nodes])
stellargraph/data/epgm.py:                    # _ = [pool.apply_async(partial(node_neighbours, edges=edges), args=(v,),
stellargraph/data/epgm.py:                        partial(node_neighbours, edges=edges), nodes, chunksize
stellargraph/data/epgm.py:                        pool.map(partial(node_neighbours, edges=edges), nodes)
stellargraph/data/epgm.py:    #         data = data = partial(node_neighbours_extended, nodes=nodes, edges=edges)(v) # node_neighbours_extended(v, nodes, edges)
stellargraph/data/edge_splitter.py:             chosen to be from the former's local neighbourhood.
stellargraph/data/edge_splitter.py:        neighbourhood of randomly (uniformly) sampled source nodes at distances defined by the probabilities in probs.
stellargraph/data/edge_splitter.py:                        # target node for a negative edge sample. Otherwise add its neighbours to the stack, only
stellargraph/data/edge_splitter.py:                            neighbours = list(nx.neighbors(self.g, v))
stellargraph/data/edge_splitter.py:                            self._random.shuffle(neighbours)
stellargraph/data/edge_splitter.py:                            neighbours = [(k, dv + 1) for k in neighbours]
stellargraph/data/edge_splitter.py:                            nodes_stack.extend(neighbours)
stellargraph/data/edge_splitter.py:        neighbourhood of randomly (uniformly) sampled source nodes at distances defined by the probabilities in probs.
stellargraph/data/edge_splitter.py:                        # target node for a negative edge sample. Otherwise add its neighbours to the stack, only
stellargraph/data/edge_splitter.py:                            neighbours = list(nx.neighbors(self.g, v))
stellargraph/data/edge_splitter.py:                            self._random.shuffle(neighbours)
stellargraph/data/edge_splitter.py:                            neighbours = [(k, dv + 1) for k in neighbours]
stellargraph/data/edge_splitter.py:                            nodes_stack.extend(neighbours)

User Story
As a data scientist
I want to use Stellargraph methods that have a consistent way of spelling neighbour/neighbor
So that I can more easily remember them and encounter less errors from getting confused between the two.
Done Checklist

[ ] Produced code for required functionality
[ ] Tests written and coverage checked
[ ] Code review performed
[ ] Documentation on Google Docs  (if applicable)
[ ] Documentation in repo
[ ] Version number reflects new status
[ ] CHANGELOG.md updated
[ ] Team demo

Or why don't we have both

Vague update: With #1368 and #1583, we now spellcheck our documentation as en-AU:
https://github.com/stellargraph/stellargraph/blob/292ac3d96149788275b95842c272ea605e9588a4/docs/conf.py#L232-L235
This flags instances of various US spellings in the text, that are whitelisted:
https://github.com/stellargraph/stellargraph/blob/292ac3d96149788275b95842c272ea605e9588a4/docs/spelling_wordlist.txt#L219-L223
If we were to decide to switch to one or the other, we should switch the language and/or remove the whitelisting (as appropriate).
However, this doesn't/won't flag the spelling in functions and classes in the actual API, only in the description.


Comcam mcm sal

This will enable management of CCS SAL on comcam-mcm, as per https://jira.lsstcorp.org/browse/IT-2613

One small comment, I also added:

/etc/systemd/system/ocs-bridge-comcam-dev.service
/etc/systemd/system/mcm-comcam-dev.service

both of which point to /lsst/ccs/dev rather than prod, and also in the case of the first one have an extra env var set. It would be good to get these included into the puppet setupm but it might need some discussion,
We will need to merge this into the IT2753 branch to deploy it on comcam.

I have no objection to this but it would be great if we could eventually merge this module with https://github.com/lsst-it/puppet-sal2 so we do not have to support two modules that do essentially the same thing.

Although I believe it would be fine to merge this as-is, it may make sense to wait and include
https://github.com/lsst-it/puppet-ccs_sal/pull/4


WIP: Fixing core types to handle nexus files

Fixes #11.

Coverage decreased (-0.2%) to 79.077% when pulling dd2ef3243804360b37068e81594d90c9c08343f1 on types into 743b9b85f49fd7e3c14d574d0b994d528c81be53 on master.


Fixes #212: duplicate title in documentation

What this PR does / why we need it:
This PR fixes #212. There is a change of title in the file contribute_openebs_doc.rst .
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #212
Special notes for your reviewer:

@adsrc Thank you so much for your PR contribution! We would like to mention you in our tweets, thanking you for your contribution. Can you please send me your twitter handle on this mail ID<EMAIL_ADDRESS>?


Expose Navbar collapse property and actions

Makes collapsed property public, call onCollapse/onCollapsed and onExpand/onExpanded actions. Allows for more flexible customization, while the existing default behavior stays in place. Provides some primitives and a first step for a solution for #317

@srvance Thanks for reviewing!


Added Youtube-Clone

Closes: #591

Title : Youtube-Clone
Name: : Yamini Uppal
Idenitfy yourself: :  GSSOC Contributor

Describe the add-ons or changes you've made 📃
Added Youtube-Clone in Vanilla-JS folder.
How Has This Been Tested? ⚙

I have tested it by running on my local system.
Screenshots 📷

Type of change ☑

What sort of change have you made:

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.

Note to reviewers 📄

@Avdhesh-Varshney what changes are requested

@Avdhesh-Varshney Resolved the conflict ,kindly review


Opinions: Organizing large $stateProviders

Would like to get some insight into how others are organizing their medium to large sized application states.
For our app we're using named states to seperate out the defined sections, as such:

This leads to something like this for our $stateProvider config:
var headerView = {
  templateUrl: 'views/header/header.html',
  controller: 'HeaderCtrl'
};

var footerView = {
  templateUrl: 'views/footer/footer.html'
};

// if the URL doesn't match any of our defined URLS
$urlRouterProvider.otherwise("/");
$stateProvider
  .state('home', {
    url: '/',
    views: {
      'header': headerView,
      'content': {
        templateUrl: 'views/main.html',
        controller: 'MainCtrl',
      },
      'footer': footerView
    },
    resolve: {
      ....
    }
  })

This starts to get unwieldy when you have anymore than a few states with large resolves in each one. What are some strategies folks are using to keep things more organized? I've thought about creating separate modules for each state and child states - is that realistic?

My proposal is based on ES6 modules.
Long story short. Each state has a separate folder, for instance contacts/one/edit. In this folder I have the following files:

controller.js, controller.spec.js
state.js, state.spec.js
state.html

state.js holds the state definition object:
import controller from './edit.controller';
import template from './edit.state.html';

// State name is exported so we can use it in the corresponding test
export const name = 'contacts.one.edit';

export default {
  name,
  url: '/edit',
  template,
  controller,
  controllerAs: 'ctrl'
};

This configuration could be activated in the module's configuration block with $stateProvider.state(oneEditState)
Here you could find the complete example https://github.com/lucassus/angular-webpack-seed/tree/ce4e9b91ce9ed47ca74073d754b0cbacff8cb65f/src/app/contacts/one/edit


Visualise the escalator for k8s

Create a plotly graph rendering the "release support escalator" for Kubernetes - https://en.wikipedia.org/wiki/Kubernetes#Support

Progress sofar:

Progress sofar:

With descriptive text and an animation to show time passing:

This is now deployed to PWS at http://staying-up-to-date-explorable.cfapps.io/


[Bug]: HuggingFaceEmbedding constructor does not set normalize argument

Bug Description
The embeddings.HuggingFaceEmbedding class takes a normalize argument in its constructor. However, this argument is not being assigned to self.normalize, which is subsequently used elsewhere in the code. This oversight leads to unexpected behavior when the normalize parameter is specified, as it does not influence the embedding normalization as intended.
Version
0.9.5
Steps to Reproduce

Import the HuggingFaceEmbedding.
Instantiate an object of HuggingFaceEmbedding with the normalize parameter set to True or False.
Observe that the normalize setting does not affect the behavior of the object as expected.
To actually turn off normalization, one has to manually set model.normalize to False

import numpy as np
from llama_index.embeddings import HuggingFaceEmbedding

text = "Hello world!"
model_name = "intfloat/e5-small"

model = HuggingFaceEmbedding(model_name=model_name, normalize=True)
emb = model.get_text_embedding(text)
print(np.linalg.norm(emb))  # prints 1.0000000243400735

model = HuggingFaceEmbedding(model_name=model_name, normalize=False)
emb = model.get_text_embedding(text)
print(np.linalg.norm(emb))  # prints 1.0000000243400735, embeddings are normalized even with normalize=False

model.normalize = False  # manually set normalize=False
emb = model.get_text_embedding(text)
print(np.linalg.norm(emb))  # prints 4.065653431959362

Relevant Logs/Tracbacks
No response

@mihal09 found the culprit -- it was wrongly typed as str and so pydnatic was converting the boolean to a string... then if self.normalize: will always be true.
rip


Make sure no runtime errors if we have more than one $( in the WDL command

While reviewing the code today, part of #126 , I noted this line: https://github.com/common-workflow-lab/wdl-cwl-translator/blob/main/wdl2cwl/main_oop.py#L578
It doesn't handle if you have more than $( in the string. Looking at the spec, it doesn't say anything about how many $( we can have in a WDL command string. But this workflow has multiple: https://github.com/broadinstitute/viral-pipelines/blob/fa070138543df3b6353a17e1821419eb5bd6e87c/pipes/WDL/tasks/tasks_nextstrain.wdl#L486-L499

FYI: There is no $( in WDL (that is a BASH/shell construct). There is, however ${ and ~{
https://github.com/openwdl/wdl/blob/main/versions/1.1/SPEC.md#expression-placeholders-and-string-interpolation
True, all uses of $( in a WDL command section need escaping before being put a the CWL InitialWorkDirRequirement file contents section, so that they do not look like a CWL expression.

Thanks @mr-c ! Closed IDE and ran out of :coffee: power for the day. Will try to understand what's being replaced there, and whether the issue can happen or not (was going to use the label "bug?" because I didn't have time to confirm this bug).

The issue can totally happen, if there are two $( bash command substitutions in the same line of a WDL command, yes!
Good catch.


Fix Wrong Loinc Code for TNM-N Clinical

TNMc (clinical) Structure contains 201906-3, not 21906-3
see https://simplifier.net/oncology/TNMc/~json
{
  "id": "Observation.component:TNM-N.code.coding.code",
  "path": "Observation.component.code.coding.code",
  "fixedCode": "201906-3"
},

Yes the profiles are wrong. @MLambarki can you please confirm that?

Yes, the code is wrong ( "201906-3").
I have fixed it in the TNMc profile:
https://simplifier.net/oncology/TNMc/~xml
Thank you!


Kraken.com have not provider the frozen balance in their api

I saw two apis which about user account balance, TradeBalance and Balance.
So, how do I get the frozen balance?

Well, I ask the kraken IT support~The solution is as follows:

You'll need to use OpenOrders and for each open order, pull the pair, type, and volume to calculate funds allocated into trades for bids(sell orders), and to calculate volume at price for asks(buy orders) across for all open orders. I'm going to setup an internal request for this functionality to be added into our API (but it may take a while for those features to be added in, keep in mind). Hope this helps. Thank you for choosing Kraken and have an incredible day.

Kraken Client Engagement Team

大概就是要使用 OpenOrders  去统计一下有多少资产是被订单锁定的，然后会在后续提供接口，请耐心等候~


NO-ISSUE: adding openssh package to recert image in order to generate ssh keys in IBI process

NO-ISSUE: adding openssh package to recert image in order to generate ssh keys in IBI process

/test 4.14-images

/cc @fontivan
Steven, can you include this on our recert downstream images ?

/lgtm

/override e2e-aws-ovn-single-node-recert-serial
/override e2e-aws-ovn-single-node-recert-parallel
broken tests

/override e2e-aws-ovn-single-node-recert-serial
/override e2e-aws-ovn-single-node-recert-parallel

/approve

/override pull-ci-rh-ecosystem-edge-recert-main-e2e-aws-ovn-single-node-recert-parallel
/override pull-ci-rh-ecosystem-edge-recert-main-e2e-aws-ovn-single-node-recert-serial

Created https://issues.redhat.com/browse/MGMT-18091 to think whether about this is a good idea or not


Moor not working if windows app installed with MSIX installer

Describe the bug
A clear and concise description of what the bug is. Please briefly describe what behavior you expected, what behavior you saw, and how the bug can be reproduced.
MSIX is an installer for windows app to distribute on Windows Store as well as direct download. https://github.com/YehudaKremer/msix This is recommended by flutter docs. I tried it with packaging sqlite3.dll with it and some additional code as explained in moor docs.
void main() async {
  open.overrideFor(OperatingSystem.windows, _openOnWindows);
  final db = sqlite3.openInMemory();
  db.dispose();
  runApp(new MyApp());
}

DynamicLibrary _openOnWindows() {
  final script = File(Platform.script.toFilePath());
  final libraryNextToScript = File('${script.path}/sqlite3.dll');
  return DynamicLibrary.open(libraryNextToScript.path);
}

But after installing the app through MSIX, sqlite doesn't seems to work. It works when run directly by .exe file but not for the MSIX installed app.
Edit: I did some debug it gives:
SqliteException(14): bad parameter or other API misuse, bad parameter or other API misuse (code 21)

Unfortunately I can't help you with this. How you open sqlite3.dll on Windows is outside of the responsibility of moor, and I don't have any experience with msix.
You could check how additional dlls can be included with msix, maybe it is possible to ship sqlite3 along with your distributed app. It needs to include the VC runtime either way. It might also be possible to configure your Flutter build scripts on Windows to statically link sqlite3.


ML.NET v 1.5 Update based on dependabot dotnet/samples PRs

Updated the following tutorials based on dependabot dotnet/samples PRs:

File Type
File Name
Published Url

Content
docs/machine-learning/tutorials/github-issue-classification.md
https://review.docs.microsoft.com/en-us/dotnet/machine-learning/tutorials/github-issue-classification?branch=pr-en-us-18981

Content
docs/machine-learning/tutorials/image-classification.md
https://review.docs.microsoft.com/en-us/dotnet/machine-learning/tutorials/image-classification?branch=pr-en-us-18981

Content
docs/machine-learning/tutorials/image-classification-api-transfer-learning.md
https://review.docs.microsoft.com/en-us/dotnet/machine-learning/tutorials/image-classification-api-transfer-learning?branch=pr-en-us-18981

Content
docs/machine-learning/tutorials/iris-clustering.md
https://review.docs.microsoft.com/en-us/dotnet/machine-learning/tutorials/iris-clustering?branch=pr-en-us-18981

Content
docs/machine-learning/tutorials/movie-recommendation.md
https://review.docs.microsoft.com/en-us/dotnet/machine-learning/tutorials/movie-recommendation?branch=pr-en-us-18981

Content
docs/machine-learning/tutorials/object-detection-onnx.md
https://review.docs.microsoft.com/en-us/dotnet/machine-learning/tutorials/object-detection-onnx?branch=pr-en-us-18981

Content
docs/machine-learning/tutorials/predict-prices.md
https://review.docs.microsoft.com/en-us/dotnet/machine-learning/tutorials/predict-prices?branch=pr-en-us-18981

Content
docs/machine-learning/tutorials/sales-anomaly-detection.md
https://review.docs.microsoft.com/en-us/dotnet/machine-learning/tutorials/sales-anomaly-detection?branch=pr-en-us-18981

Content
docs/machine-learning/tutorials/sentiment-analysis.md
https://review.docs.microsoft.com/en-us/dotnet/machine-learning/tutorials/sentiment-analysis?branch=pr-en-us-18981

Content
docs/machine-learning/tutorials/text-classification-tf.md
https://review.docs.microsoft.com/en-us/dotnet/machine-learning/tutorials/text-classification-tf?branch=pr-en-us-18981

Content
docs/machine-learning/tutorials/time-series-demand-forecasting.md
https://review.docs.microsoft.com/en-us/dotnet/machine-learning/tutorials/time-series-demand-forecasting?branch=pr-en-us-18981

AB#1732831

@adegeo can I please get a review when you get a chance. Thanks!


Feature/testing

This PR brings in changes to fix testing on local systems via cloud-build-local and within Google Cloud Build through pull requests.

/gcbrun

/gcbrun


Manual for DataHUB?

Idea: Harmonize Knowledgebase content.
Derived from a response to #20: https://github.com/nfdi4plants/nfdi4plants.knowledgebase/issues/20#issuecomment-1360058411
Create Quickstart, Manual and maybe also developers docs for the tools with high user exposure


Handle computers with multiple processors

We were collecting the energy consumption of a single processor package.
This patch collects the energy consumption of each package and sum it
up to get the total energy consumption.
The code was based on the PAPI RAPL code [1][2].
[1] http://icl.cs.utk.edu/papi/
[2] http://gist.github.com/luisgabriel/f91656a6662e21a2ff9c

Still need to test on linuxapps02 to make sure it is working properly.

Will do.


Add extra toggles and information for xp globes

Adds toggles for all the information in xp globes
Adds xp/hr and actions information in xp globes

Before:

After:

Actions left was added in #1636 , so what this PR adds is xp/hr and toggles.
The developer seems to have given up though.

Closing as this is very old PR now and has a lot of merge conflicts, reopen if you want to re-implement it.


[vault-secrets-webhook] Construct full database connection in the one environment variable

Is your feature request related to a problem? Please describe.
I wanna build a connection to the database. I'm holding on vault as well HOST and DB info. I ended up with the following template:
postgresql://${vault:database/creds/database#username}:${vault:database/creds/database#password}@${vault:secret/data/database#HOST}:5432/${vault:secret/data/database#DB}

Unfotently that template creates 2 separate database user leases. I end up with connection string that uses username from first lease and password from the second leasone - as a result I can't connect to the database
Describe the solution you'd like
I guess we should track common paths like database/creds/database and make only one lease

Hi @arturkasperek, which version of Bank-Vaults are you using? There is a path caching fix in the most recent version of BV.

@bonifaido hi, my bank vault version is 1.15.0

Please try 1.15.1

Will try, thanks for the advise :)

@bonifaido the problem has not gone away  - I just tested that with ghcr.io/banzaicloud/vault-secrets-webhook:1.15.1

@bonifaido It's fixed - thank you :)

Cool stuff @arturkasperek , would you mind if I close (or you close) this issue? :)

Closed


[Ubuntu 16.04.1 + ZNC 1.6.3+deb1] SSL handshake timeouts

Nothing is shown on stderr. Connecting over separate, unencrypted port works fine, connecting over SSL port fails.
Let me know, what do you need to properly reproduce and debug this.

Run ZNC with the -D (debug) flag.

Absolutely nothing relevant shows neither on stdout, nor on stderr

And you are sure the port is open and not blocked by a firewall or behind NAT?

PORT      STATE SERVICE
31337/tcp open  Elite
And all ports are open on my IRC end. I did not mess with my firewall
config, so the port is still open.

PORT      STATE SERVICE
31337/tcp open  Elite
And all ports are open on my IRC end. I did not mess with my firewall
config, so the port is still open.
Results of openssl s_client ran from the localhost:
CONNECTED(00000003)
140367625135768:error:140790E5:SSL routines:ssl23_write:ssl handshake failure:s23_lib.c:177:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 305 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : 0000
    Session-ID:
    Session-ID-ctx:
    Master-Key:
    Key-Arg   : None
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time:<PHONE_NUMBER>
    Timeout   : 300 (sec)
    Verify return code: 0 (ok)
---

You wouldn't happen to be trying to connect over SSL at other plain text port would you?  I don't think ZNC supports SSL and plain text on the same port...

That's why I set up plaintext on another port, but, to satiate your
curiosity, connecting plaintext over not-working SSL port still failed.

Try the same port number over which you got a successful plain text connection. If znc --debug does not say anything, then the connection does not reach znc. It will print something for sure even before it actually accepts the connection.

Do I have to try SSL over it, or plaintext?

Either - it'll print something in either case, I believe

It was not a bug, the PEM file was wrong.


Remove Textured Voxels?

Over Christmas I'll rework the data structure. Should we remove textured voxels all together? Do we see a use case for them? Anyone?

I vote to maintain this feature, Voxel Shop is the unique that has it

As rubengc said it's the unique feature the voxelshop has, i also agree on keeping it. But if it get in the way, we may consider removing it cause exported mesh can easily be re-textured in most 3d editor.

But the texture on each voxel should be in the final optimized texture so, doing re-texturing in other 3D soft would not be so easy.

@funalab it is not the unique but yes one of the most interesting
This feature and layers has make me interest on this editor
A feature that really needs to be in voxel shop is a way to rendering, thats the unique thing that does voxel artists use another software (as Unity, or magica voxel) to get the last screenshot and share the final result

Renderer takes some time to implement so don't know what to say about that, but i also don't think simlu is against using magica for rendering. :D

MrTopom i was talking about the mesh as a whole   anything otherwise won't obviously be easy to do.

Still got some time to decide. It would just make things much easier when defining the data structure and supporting larger models...


Add some notes about restricting the CPU cores used by PV

I added a few "notes" in the install docs to point people to the ability to restrict which CPU cores are used. This is relevant on ARM big.LITTLE architectures, including Orange Pi 5.

FYI, I have a PR open to create a orange pi image with this flag set by default in the service file. Lgtm tho

Needs to be rebased

Done. Hopefully correctly (not a git wizard!).

Looks completely FUBAR

OK, I did not notice a link had changed. Should have tested my build ;-(. Done, and CI passes now.

I still see 103 files changed????

OK, I am mystified. I only touched 2 files. It looks like somehow it dragged into a bunch of other commits from mdurranni808 2 days ago. No idea how that is possible.
Maybe I will just kill this and then resubmit, but I can't right now (need to run).

Actually, snuck it in. See PR306. I did not bother with the note in the OPi page, because I don't know about the OPi 4.


impl(bigquery): Response field changes for Projects api

This PR implements the json field name changes for Project response object. It ensures the field names in the response are in accordance with the response body mentioned in the api docs.
No logic has been changes. Just the field names and corresponding unit tests.
This fixes the github issue https://github.com/googleapis/google-cloud-cpp/issues/12109

This change is

Let's finish the discussion on #12149 first.  It may need a GVC or some IM because I am sure there are tradeoffs that I missed.


fix microsoft/Phi-3-mini-4k-instruct crash in batch.slots[batch.slot_…

@Narsil

We can't fix it that way (The initial goal was the fix Phi3 and DeepSeek).
Seems like we just need to override the processor because the one defined on the hub is wrong. https://huggingface.co/microsoft/Phi-3-mini-4k-instruct/discussions/75/files


Issue403

@ryanbarrett1515 - so far so good!  need to prevent drag-n-drop into fixed category columns

first click of Wm Plot and Sort report throws a null pointer exception

I'm not getting any exceptions

nice ... I am merging;


How to access GPIO in kernel space?

Hi, very nice tutorial, but how can we access all-40 GPIO pins in kernel space?
Thanks.

There are two (or 3) methods, you can use userspace direct register access by directly writing to memory like with a microcontroller OR write to /sys/class/gpio. You can also try to get wriring pi to work for the jetson, however thats a python library. It is much "safer" to access the GPIOs through the kernel (with sys/class/gpio) than using a userspace program with direct register access. This is due to there being no locking method (that I am aware of) to prevent another program from clobbering your register settings. Alternatively you can also write a kernel module and driver and then access the driver's public functions through your userspace program. Hope this helps!


Several ideas - mostly appearance.

Is your feature request related to a problem? Please describe.
–
Describe the solution you'd like

Appearance:
1.1 Thinner image border (or none, if none then the thumbnail would need the round border ) and smaller corner radius. Perhaps slightly reduce font size of album title.

(see Google gallery attach/ for a good example).
1.2 In grid mode, ability to define number of columns.
1.3 In list mode there is way too much empty space between each item. Suggest to reduce size of thumbnail. Slightly increase album font size (1px or so)

(see Samsung gallery attach/ for a good example - good spacing, not too much empty space).
1.4 Perhaps add option for having the usual simple slide animation instead of current one, when swiping images.
Ability to define custom tiers (name and order).

Describe alternatives you've considered
—
Additional context
—

Do you know that you can resize the thumbnails by doing a pinch-to-zoom gesture? In effect changing the number of columns for "grid"/"list" view (but not exactly that in "mosaic" view).


GEOMESA-2006 Tools command for configuring age-off iterator

Additional option to configure based on ingest time
Extracted age-off classes into common parents for use with other back-ends

Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>note: stacks on top of #1671

need to update docs

updated docs

how hard do you think it would be to allow ageoff with table sharing on? My concern there is that we default to table sharing on. people ingest. then can't ageoff.

yeah you can force override it - for ingest time based age-off it would not really be a problem, but for attribute based age-off it would involve some more processing, as we'd have to check the simple feature type based on the table sharing prefix, then apply the right deserialization and attribute. not that big a deal, but for something that is running under every scan might not be desirable.
I think probably it's good to make sure the user really wants to apply the age-off to any shared feature types though - they might not realize that it will affect the shared features. by forcing them to explicitly override in a table sharing situation, we're at least making them consider it

it would probably be good to increase the info in the exception that gets thrown to warn about shared types and specify the override


Seperate configuration of tab size and indent size

VSCode Version:1.19.2
OS Version: Centos 7

I'd like to be able to configure tab size and indentation size separately. When reading a file I'd like a tab character to be displayed as 8 spaces, when pressing the tab key on the keyboard I'd like it to insert 4 spaces. At present in VS code tab size and indentation size is one setting.
This sort of thing is available in eclipse, for instance, so it must be something that others have previously deemed to be useful.

Let's track in #10339


Resolve an issue in Rails 5.1 with write_attribute

We were observing an infinite loop between xss_terminate and delocalize
when upgrading to 5.1 that showed the code jumping between two
overrides of write_attribute. delocalize overrides write_attribute using
alias_method_chain, while xss_terminate uses a plain method override.
I changed xss_terminate to also use alias_method_chain in the 5.1
branch only. This resolve the infinite loop between the two overrides.

@cmayor I rewrote this to use vanilla alias instead of alias_method_chain, which still works.

lgtm

fyi, the current xss_terminate gem is nothing like the original fork now.

[lockit v4.9.3] merged via Lockit CLI on 2020-04-23 15:48:26.822676 -0700 PDT m=+4.384095199


Simplify pkgconfig-update.sh

I'm sorry, I just couldn't look at all that overcomplicated mess.

Coverage decreased (-0.2%) to 94.466% when pulling ec37768a72df2d008b245613d4d5296ce57aa1b2 on pjanouch:master into 3df84f1cad3ae3d6b0a5086e358db3d56b32874c on openSUSE:master.


Add flake.nix

I merged this so that it works for @elsirion.
It doesn't work on my m1, though. I still get this error.
More detailed logs.

Thx :heart:


Warning database init ready

Hi,
I'm running pydbantic without alembic await Database.create("sqlite_string", tables=[Project, Comment]).
I'm getting WARNING database init - ready when I run the app.
Digging in pydbantic's code, it's coming from database.py:592, it seems like normal operation and my app is working perfectly.
Unless I missed something, shouldn't this log be changed to INFO or DEBUG ?
Thanks

Hello @Creadeyh , indeed this is meant as more of an INFO message. Happy to hear everything else is working well. Will update within next release


Query bucket to get schema in background and cache it

The goal of this issue is to enable more experimentation around schema exploration and query building experiences. Since the schema does not change often our assumption is that it is safe to cache it on a regular interval (maybe every 24hrs?). For users with high cardinality this query will be extremely slow, but we aim to create a good UX for most users before the power users.
import "influxdata/influxdb/v1"
from(bucket: "<foo>")
  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
  |> first()
  |> v1.fieldsAsCols()

Talk to @desa about the query here

[ ] Store the schema in a shape that is easy to navigate and display in a component like the query builder

Here is what the current iteration of the schema for the flows query builder should look like:
{
  [measurement]: {
    type: [measurement_type],
    fields: [ ...field_names],
    tags: {
      [tag_name]: [...tag_values as string[]],
      ...
    },
  },
 ...
}

what does measurement_type mean?

@desa I believe that's string | int etc. but might not be necessary since they are all strings

This should be done once this PR gets merged into the UI repo:
https://github.com/influxdata/ui/pull/32


Add Blog link to Value section

Add link to ebpf Blog, and change "Next steps" to "Send us feedback".

Merge to nightly (OS only)

Deploy preview for calico ready!
Built with commit 50f4a25f64f9d51567cc3f42d5fd39417afc0cf7
https://deploy-preview-3370--calico.netlify.com

Deploy preview for calico ready!
Built with commit 47d9c442c1040ed1deb63ac2d6a519e24af9a3ee
https://deploy-preview-3370--calico.netlify.com

Approve changes.


Use the server type for insert to cursor position

Problem

insertToCursorPosition message from ui-client is not using the server command type: https://github.com/aws/language-servers/blob/3cef4c0349258d7b3d65bd20ceca615d6acd86ad/chat-client/src/client/chat.ts#L105-L107 This is confusing as the other outgoing events follow the server types.
Please feel free to merge it if it looks good or close it if this PR is not correct.
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Synced up offline that it will be kept as chat-ui-types for now until insertToCursor can be handled on server side